SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
How do you start a SSH server using named pipes on the first attempt of a connection?
This is undesirable. The services a server needs to deliver is known ahead of time, and it is very prudent to make sure all of those services are functioning properly before it (re-)enters production use.
The traditional model is the correct one: All necessary services are started, their health ascertained, and then the server added to the work pool.
I think we need to look at the the attempt to portray systemd opponents as backward, resistant to change etc in light of the above. The main benefits of systemd are to redhat and its backers who also benefit from a crippled linux.
I'm actually now more interested in the "harder to hack" scenario because we still have an under/undocumented API within systemd to the point nobody but the systemd devs knows what it truly does. To me, that should raise some alarms before anything else. I'm no "anti-government tinfoil hatter" but I do value my privacy and the NSA doesn't need to know what they don't need to know, and I, for one, would actually like to know if my system has a backdoor.
As far as reliability goes, the standard model has been nearly 100% reliable and BSD uses a nearly identical design. No question anyone should prefer stability over performance, unless you're doing testing or evaluations.
Distribution: slack 7.1 till latest and -current, LFS
Posts: 368
Rep:
@ReaperX7: (see this as a funny post)
I have an old black and white TV for you if you want. (read traditional UNIX)
Or a 32" Color TV (read SysVinit)
I just bought a new Full HD color TV (read systemd without all options)
I did not buy a 4K OLED 3D curved TV (read systemd with all options)
All of them do the same job (show things on my screen)
You can have coffee, if you like (traditional UNIX).
You can also have espresso (sysvinit + traditional userland infrastructure).
Or you can have a double pumpkin latte soymilk decaf with a shot of caramel and green food dye (systemd).
The green dye may or may not be toxic; anyone complaining of intestinal bleeding will be dismissed as "against change" ;-)
I'm actually now more interested in the "harder to hack" scenario because we still have an under/undocumented API within systemd to the point nobody but the systemd devs knows what it truly does.
The source code is freely available for every one willing to read it and figure out what it truly does.
There is no attitude shift. There is only a bunch of wannabe geeks who believe that installing Linux and administrating a primitive setup makes them experts.
I have an old black and white TV for you if you want. (read traditional UNIX)
Or a 32" Color TV (read SysVinit)
I just bought a new Full HD color TV (read systemd without all options)
I did not buy a 4K OLED 3D curved TV (read systemd with all options)
All of them do the same job (show things on my screen)
There is no attitude shift. There is only a bunch of wannabe geeks who believe that installing Linux and administrating a primitive setup makes them experts.
Cheers
So if you're so smart, why don't you take the systemd code and document it yourself if you think you're more of an expert than the so-called by your terms, wannabe geeks. If you want to preach the cynicism of Free Software and want to thump the Open Source Bible, then by all means show us what you know and prove yourself to be not another wannabe yourself or hold off on the empty rhetoric and end this charade.
Not all of us are coders proficient in C, and developers and wannabe developers thumping that claim is getting old and tiring. Many of us are damn sick of developers with torn in their ass attitudes touting "It's open source, so if you want it, code it yourself." But just because we don't code in C doesn't mean they are better on any level than someone who isn't.
It's like my signature says. Nobody cares about the code language. However, People like us so called "wannabes" care about the quality of the code, not the quantity.
There is no attitude shift. There is only a bunch of wannabe geeks who believe that installing Linux and administrating a primitive setup makes them experts.
Cheers
In other words; complex is better than simple.
Actually, with any machine simple is better than complex. The more complex a machine is, the more things there are that can go wrong. That is why, whether guns or spacecraft, the simple machines are used dependably for many years with few or no changes, while the complex ones are frequently replaced with newer designs. Claiming simple OS designs are inferior to complicated ones is not a convincing argument in itself.
Last edited by Randicus Draco Albus; 02-16-2015 at 10:47 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.