Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - jeffreyC

Pages: [1] 2 3 4
VSIDO News & Announcements / Re: The end of the VSIDO era
« on: March 09, 2021, 03:02:52 PM »
You should take a look at the gazelle-installer, that is what MX-Linux and antiX use.

They looked at the calamares installer and (when they looked at it) it required a lot of KDE dependencies which made the ISO much bigger for no gain in function.

VSIDO Discussions / Re: Gotta love Debian now
« on: December 11, 2016, 10:52:28 PM »
^ It sure seems that way to me...

But it is awfully easy to blame systemd for debian bullshit.. they are after all partners

What has me wondering is that one of the many, many things systemd has taken over is network discovery and when you changed the network settings is when the trouble started.
Having PID 1 aka systemd responsible for the whole OS is what makes me think that when one part fails or does not work as it is programmed to expect then the whole OS is more likely to fail.

VSIDO Discussions / Re: Gotta love Debian now
« on: December 10, 2016, 08:22:13 PM »
Is this part of the joys of systemd uber alles?

VSIDO Discussions / Re: What every Linux user should study and know
« on: November 04, 2016, 05:28:49 AM »
Nice find, VastOne.  It would be even nicer if it was in PDF format.  Maybe I can work on creating one and sharing.  ;)

Don't know if you got one but here is one:

I've Got a Life / Re: Just retired, now what?
« on: November 28, 2014, 09:30:43 AM »
The Buick 215 was not a high production engine and has been out of production for over 50 years, not a good thing for a budget friendly build.

If weight is that much of a concern would a V6 possibly be a better choice?
Also smaller to fit the engine bay easier.

VSIDO Discussions / Re: Runit vs systemd placeholder
« on: November 26, 2014, 05:20:05 AM »
A comment on Distrowatch draws a parallel between Windows svchost and systemd, noting also that both present a large "attack surface".

Making all Linux distros the same "under the hood" would also increase vulnerability in some ways I would think.

I've Got a Life / Re: Just retired, now what?
« on: November 26, 2014, 05:17:10 AM »
Maybe a Ford 302 Windsor aka 5.0?
Smallest and lightest of the common V8s.
Common = retired budget friendly.
They have some very good 5 speeds for them too.

(Gearhead for decades, long before I went to computers)

VSIDO Discussions / Re: To all who really (not) like Gnome...
« on: November 23, 2014, 10:36:56 PM »
The party that has already had the name in use is very nearly always the winner, 17 years is pretty much established and I would be amazed if they lost to Groupon.

VSIDO Discussions / Re: To all who really (not) like Gnome...
« on: November 16, 2014, 03:38:51 AM »
Don't see why they would need that kind of money for this, as soon as any competent judge saw that there was a trademark that existed for over a decade Groupon would get thoroughly chewed out for lack of due diligence.
No long drawn out court case required.

Considering the Gnome3 efforts to "protect the brand" by preventing theming Gnome3, I see this as a case of crying wolf.

VSIDO Discussions / Re: SpaceFM replacement
« on: October 26, 2014, 07:51:25 AM »
As long as it's NOT rox-filer, I've tried that in puppy where it was the standard for years, it does not work at all like I expect a file manager to work.

But really it does not make much difference as long as it is not tied in too tightly to the whole, like Nautilus was to Gnome. (yeah, I know they've replaced that, shows how long since I've used Gnome)

Simple to apt-get/aptitude/Synaptic whatever is wanted.

VSIDO Discussions / Re: Runit vs systemd placeholder
« on: October 20, 2014, 11:23:32 AM »
Looks like it is not as set in stone as thought, round two of voting?:

Artwork & Screenshots / Re: October 2014 Screenshots
« on: October 16, 2014, 02:10:39 AM »
Remembering keybindings ???
That's probably why CrunchBang has a list on the desktop via the conky.

WM Designs and Discussions / Re: Fluxbox Styles
« on: October 13, 2014, 08:42:14 AM »
I have a question about gtk themes and security.

First you gotta understand that I worked for years in government, where we were pounded left and right about social engineering and proper IT security and communicating to the public, etc, so that our magic fairy dust knowledge would be protected. So, I naturally became even more cautious than I am naturally. Second, you gotta understand that I hate the grey gtk theme. Ugh, give me glorious black, charcoal, midnight, just bring down the lights. I used to use tawan's gtk-carbon theme (, which is almost perfection to me, back when I only surfed casually and did no personal financial, or any truly private junk on my linux system. Just a toy. But now, with my understanding of linux increasing (partially from using linux both at home AND work), I am more inclined to make the move completely. But that means it has to be more secure, so that I can do banking and stock market speculation etc.

The xbm and png files used to skin windows are jpg files with root permissions, right? So, how am I supposed to feel regarding someone's generic gtk theme I downloaded from boxlook or DeviantArt or whatnot? Image files can contain code other than just the image itself. Shouldn't I be cautious about this?
Much of the malware in image files takes advantage of Windows file naming convention where the file extension type is not shown i.e. anything.jpg.exe will usually be shown by Windows as anything.jpg.
Windows will run .exe files, Linux can sometimes through WINE otherwise they are simply files.

Remember that this is open source which means that the underlying code is always available for you to read.

Themes and styles are often in the root file system, this is not automatically the same as executable.
They can also be placed in the home partition, which does not have root permissions however those themes and styles will only be available for the users of that /home.

Check the file properties/permissions if the execute bit is not enabled no danger.
You are not the first with such concerns, see here:

VSIDO Discussions / Re: Runit vs systemd placeholder
« on: October 12, 2014, 09:57:19 PM »
With everything that will be run directly by systemd the only thing remaining on the to-do list is to change the name from Linux or GNU/Linux to systemdOS

VSIDO Discussions / Re: VSIDO systemd and upstart discussion
« on: October 12, 2014, 05:25:29 AM »
Things I'm reading have me increasingly concerned about systemd;
Seems that it is planned to take over package management, and become the underlying process for the terminal.

WhatDaFuq does an init system need to get involved in doing all that for?

The end result will be that ALL Linux distros will become the same.

Aren't these devs employed by the same company that employs the Gnome3 devs who work so diligently to eliminate all deviation from "the brand" and talk of creating the GnomeOS.
Interestingly Gnome3 has systemd as a dependency.

Edit: this was written before I read statmonkey's post about systemd taking over how the file system works:

Pages: [1] 2 3 4