Website tells users to switch to Slackware in protest of systemd
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.
who designed a versatile and robust init system,
who wrote excellent documentation and manuals,
who took part in numerous presentations to explain basic concepts,
who devotes his time to answer technical questions on numerous forums,
who wrote Pulseaudio, which solved quite nasty problems with Alsa,
who wrote Avahi, which just works good
k so
versatile and robust init system ?
depends on your view; i would say it is less flexible then slackwares BSD stile sysvinit
robust is also discussable since it's devs don't even care about debugging
also almost all, if not all, of that "revolutionary advanced" "init" stuff is done by other programs or the kernel
he didn't make shit (afaik not even console-kit, that is also a dubious thing)
who didn't explain shit on he's 0pointer blog ?
i didn't get wtf he meant with socket activation till i read a couple ppl discussing it here (it's useless bdw)
who devotes time to delete posts he doesn't like ?
pulseaudio is pure crap
it uses "secret rabbit code" sample rate library (libsamplerate) that uses floating point for no real benefit and is thus slow
(funny that it is based on a much faster "resample" library from stanford)
it also adds more latency that makes no f..ing sense... my guess it is he's "very complicated" latency-timing mechanism (can't remember what he called it; from what i understand it's something about as complex as a simple game engine loop)
edit: just to add; only assembly optimizations i found was for converting int to float, and that was not written by him nor is it in any way complicated
and real time DSP needs assembly optimizations, it is one of those things that benefit a lot from it
also, a sound server can "tune" itself at run time
and yet he blames distros and users for bad default configuration, like "PA is the best, it's your fault it's not working great"
avahi... i don't use it
this one actually sounds useful to a normal linux user surrounded by mac's and windows (and is, like many things he made, a straight up clone from osx)
so ye, if you really "need" socket activation then go ahead
id like to hear some sane reasoning on it, but that has not happened so far
And just so you actually learn something Mr. Sheep... This is Skarnet's s6... It's a fully custom to distribution init and service management system that is possibly the best stand-alone init and service management solution out there, but implementing it is total hellfire and brimstone of an effort.
I'll take both the praise and the criticism. But please, if making s6 work was hellfire and brimstone for you, write to me and explain exactly what you found difficult and why; what could be made easier or better. I'm absolutely willing to make s6 easier to use, but I need the feedback. I see people trying to use or package s6 and complaining on forums (not only this one), and not even asking me for help, or subscribing to the mailing-list. Upstream is reachable. Talk to me.
People haven't heard of s6 for the simple reason that I'm a busy man and my free time is better spent designing and coding software than advertising it. Time spent bullying distributions into adopting a piece of software is time not spent making said software better. But I'm realizing more and more that distributions are obviously more sensitive to public relations than to technical merit, so I'll definitely do some more PR in the future.
I'll take both the praise and the criticism. But please, if making s6 work was hellfire and brimstone for you, write to me and explain exactly what you found difficult and why; what could be made easier or better. I'm absolutely willing to make s6 easier to use, but I need the feedback. I see people trying to use or package s6 and complaining on forums (not only this one), and not even asking me for help, or subscribing to the mailing-list. Upstream is reachable. Talk to me.
People haven't heard of s6 for the simple reason that I'm a busy man and my free time is better spent designing and coding software than advertising it. Time spent bullying distributions into adopting a piece of software is time not spent making said software better. But I'm realizing more and more that distributions are obviously more sensitive to public relations than to technical merit, so I'll definitely do some more PR in the future.
Thank you for and good luck with the future of the s6-suite. We may be looking to you fairly soon as a choice of init depending on how well Runit rolls off the line. Hell, we might even do it just to offer yet another choice, but that's best saved for another topic. Maybe "hellfire and brimstone" is just my best analogy of attempting what John F. Kennedy said in his infamous speech, "We do these things not because they are easy, but because they are hard." But trust me Skarnet, your work, even if by a small number, is being looked at heavily with promise and interest.
However, even seeing upstream jumping in to say "SOMETHING" actually speaks volumes that someone actually is listening and wants to help downstream. If more developers were like yourself, I doubt we'd have as many issues as we have. A hat tip to your efforts sir.
Quote:
Originally Posted by hendrickxm
The future is looking good. There is eudev available, the init scripts still work, systemd is ported and I see projects like openrc and runit coming soon.
Runit will move faster to non-LFS when we get more scripts written to start and stop services as well as log them. Dare I say it, but until we get a full set of working scripts written it won't be moving as fast, but yes, Runit does work.
I may sometime soon, see if the Runit team is willing and able, to take a chance on Skarnet's s6-suite and see if we can't do an FHS stylized port of s6 to LFS and then see about branching it out.
And yes, the future does look promising as long as there's a willingness to make it promising.
And ssl779... this single quote of yours:
Quote:
Originally Posted by ssl779
Then you wold become a hero - like L.P. for example
All credibility you had went out the window with that statement. And I would never want to be a hero. If I ever did anything a simple thank you and "If I ever meet you, I'll buy you a beer or a shot of Jack Daniels" is all I'd ever want from anyone. I'm no hero, neither is anyone here... and I'm fairly certain on an educated guess... nobody here wants to be a hero on any level. If that man is any resemblance of what a hero is to you... in the words of Obi-Wan Kenobi, "Then you are lost!"
Did you happen to actually look at any of those on that page?
Many of them are legacy and written by someone other than LP, and seeing all those sd*<crap> and systemd*<crap> just makes me cringe that anyone can think all of that is somehow good for a system. It's a nightmare gone wild for any sysadmin.
Quote:
Originally Posted by ssl779
What?
Yes, chinese food is healthy and delicious (hope this information helps you with init systems).
Never mind...that one flew past you too quickly.
Quote:
Originally Posted by ssl779
Maybe it's a problem with your attitude?
So the many are wrong and the one (him) is right? Neat how you do that.
Quote:
Originally Posted by ssl779
Now I can hear sound from Firefox, Skype and videoplayes *simultaneously*.
I don't believe you *couldn't* with alsa. For one with the resume you claim to have, you couldn't get alsa to work okay for you?
Quote:
Originally Posted by ssl779
Not a single one, not on my PC's, not on embedded devices for which I build distros.
What I did wrong?
Ah, not on *your* PC's, but if anyone else uses that excuse it's pathetic, right? And all the problems pulseaudio brought to so many others...what did they do wrong?
Quote:
Originally Posted by ssl779
(as for Avahi - I don't use it on my PC's, but it works like a charm on embedded devices).
Yet you need to try and flaunt it as something good for someone somewhere, just not *you*.
Quote:
Originally Posted by ssl779
Looks to me like he's chatting hard on forums about a decent init system.
So he's lying about the work he's doing? Give me a break. That was lame of you and you know it.
Quote:
Originally Posted by ssl779
Designed hardware, software and embedded linux distros for instruments used in renewable energy industry
and biomedical applications around the world. I am proud of my contribution to human civilization.
C'mon. Show us, don't just say it. I can say I won two Pulitzer prizes but until I actually showed it I'm sure you and everyone else would be pretty skeptical.
The abundance of systemd threads simply shows that people are not unanimous, there are strong feelings on both sides, and that means there is a real issue, worthy of being discussed.
It is hard to not have strong feelings regarding systemd, one way or the other. I simply believe that pro-systemd people have strong positive feelings towards systemd because they see what it's doing right - as in better than sysvinit - and disregard what it's doing wrong because they don't know anything better.
Advertising a better alternative (hint hint: s6), making it well-known, and explaining where and how it is better, is the single most important thing anti-systemd people can do now. Opposition without a suitable contender is a waste of time; opposition with a suitable contender is progress.
I'll take both the praise and the criticism. But please, if making s6 work was hellfire and brimstone for you, write to me and explain exactly what you found difficult and why; what could be made easier or better. I'm absolutely willing to make s6 easier to use, but I need the feedback. I see people trying to use or package s6 and complaining on forums (not only this one), and not even asking me for help, or subscribing to the mailing-list. Upstream is reachable. Talk to me.
People haven't heard of s6 for the simple reason that I'm a busy man and my free time is better spent designing and coding software than advertising it. Time spent bullying distributions into adopting a piece of software is time not spent making said software better. But I'm realizing more and more that distributions are obviously more sensitive to public relations than to technical merit, so I'll definitely do some more PR in the future.
Heh heh...maybe one day when I get closer to figuring things like installing a new init system out, I'll start actually trying to do it. For now, I've got enough troubles just trying to learn to make my own bash scripts. But you *are* right about needing to hear from the people who try or do 'use' it. That *is* the only way you'll know what's happening with your stuff. When I get to where I'll start trying that kind of thing with my system, I'll be sure to let you know.
I too though would like to thank you for what you've done, as I do PV (and many others) when something happens or comes out or whatever that I like and I can use and am happy with.
All systemd threads turn out this way but for some reason I feel the need to watch these slow motion train wrecks.
You don't think something like this that can and is influencing linux as a whole is important enough for people to discuss why or why it shouldn't be implemented? That, to me, is like burying ones head in the sand and saying to yourself over and over 'Someone else will take care of the problem'.
You don't think something like this that can and is influencing linux as a whole is important enough for people to discuss why or why it shouldn't be implemented? That, to me, is like burying ones head in the sand and saying to yourself over and over 'Someone else will take care of the problem'.
There is nothing actually being discussed the usual people are saying to the same things that have been said many times in many threads and many mailing lists. Nothing new is going on here that's why I called it a slow motion train wreck. Everyone has taken sides and now all that's happening is people are talking poorly aimed shots at one another.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.