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.
Just my 2 cents on the subject, I recently switched about a month ago to Slackware from using Debian for 15 years. When systemd entered my system I was a bit leery. Then it was forced as my init after a dist-upgrade and I had issues with booting, media files, and more. I never had an issue booting with sysvinit, after systemd it would take 5-10 boots just to log in. I'm not on a bleeding edge PC, this is a 2008 Dell Inspiron 1520 laptop. Just playing media files in VLC would make the kernel panic.
IMO systemd is a complete fail and I will not use a OS that has it. I believe that PV has the best intentions for Slackware, and I hope that he doesn't adopt systemd. I don't want to have to switch to *BSD. Although they do have a "true-UNIX" desktop environment in the works. I have played with FreeBSD, and it wasn't any harder to learn than any Linux distros I have played with.
I keep a watch on the bug reports at Debian. The amount of bugs in systemd has only gone up since I left. As of this post there are 196, up from 180 when I first left. https://bugs.debian.org/cgi-bin/pkgr...d;dist=testing
And that's only the systemd bugs, that doesn't include the dozens of binaries that are included with it.
I believe that Pottering's 15 minutes of fame will come to an end, and systemd will be recognized for the POS that it is. I wouldn't be so offended by it if it were just a init and I didn't have to have it forced as my init. But it has entered the realm of Windows svchost, and that just opens up a whole world of problems.
<tin foil hat=gets put on>
Secretly, I believe that it is a situation that has received pressure from certain 3 letter agencies to build backdoors into OSs. If not built in, easier to get into with malicious code.
</tin foil hat>
so the debian guys where not able to provide a smooth upgrade path in the testing part of their dist,
and that's the problem of sytemd?
following this logic it is no wonder that the next paragraph needs tin foil hat tags.
I did not think that this thread could become even more obscure, but obviously we are not done.
Actually after a dist-upgrade and the first fail of systemd on my PC, I did a clean install of "Jessie" (8.0 testing) from iso/dvd with systemd, and still had the same fails. After that I did a clean install of 7.6 "Wheezy", blocked systemd from installing, installed shims and got to a point where I couldn't update/upgrade anymore. Therefore, init is no longer a choice, but it is required that you use systemd in order to run Debian.
I don't agree with the way that things have been progressing in the Debian scene for some time now. Prob starting with them deciding that Gnome is the default DE for Debian.
I may try out Devuan, but I don't think that I would be switching to it unless/until they could provide KDE.
Actually after a dist-upgrade and the first fail of systemd on my PC, I did a clean install of "Jessie" (8.0 testing) from iso/dvd with systemd,
At this point there is no such thing as Debian 8.0, there is only Debian 7 and the Oldstable/LTS, Testing and Unstable branches. The name speaks for itself, Testing is exactly that, a branch in development that is not considered stable yet and expected to have bugs. The proper reaction to a bug in Testing is to report it, so that it can be fixed.
Debian are trying to implement systemd while attempting to keep it optional, that was never going to end well. It's like sitting on the fence while juggling running chain-saws: it's far more likely to end up being armless rather than harmless!
'systemd' is intended to be a 'platform'; if you're going to implement systemd then IMO you have to embrace it completely. My gut tells me that it will suffer no rivals and half measures are just going to end badly.
My gut also tells me that full measures are also going to end badly, but I'm starting to feel a little like Cassandra on that one, so I've given up trying to convince people -- lest I end up being raped whilst clinging to a statue of Dennis Ritchie!
For any platform to work the system must be completely redesigned around it within its own branch. LFS learned this, Arch learned this, Fedora was rebuilt around it.
Systemd is a completely different platform while sysvinit/runit/s6 is based on the traditional platform. You can't have your pie and cake with systemd. You have to pick.
Systemd is a completely different platform while sysvinit/runit/s6 is based on the traditional platform. You can't have your pie and cake with systemd. You have to pick.
Since I keep hearing this, I would really appreciate to hear the reasoning behind it.
Making this a "yes vs no" question, do you agree that both just work in debian?
This sounds as if you're suggesting that we've already failed.
Why?
Both systemd and all previous boot/init/whatever-crap are working just fine in Debian.
The initial implementation is only part of the story; the fat lady is still singing and Lennart and co aren't done yet with their grand design. Maybe it turns out I'm wrong. Only time will tell.
...said the guy with 31 posts that has been here for 2 months. Stay classy, man.
So says the not-too-classy-or-intelligent remark about post count being what makes and breaks ideas, opinions, and truths. Quit kissing his ass, he's a grown man and can handle himself.
You should look at Didier's support of Slackware prior to opening your piehole.
I'm all for people shoving their feet into their mouths up to the knee, but that's painful to watch.
So, people should revere and kowtow to those who "support" Slackware. Damn anyone with a differeing opinion on what or how that 'supporter' says or does anything. Right? Because we don't want anyone to start crying that they do this and do that for Slackware and everyone should STFU and not say or do anything that might make them mad. Right?
You might want to also take your lips off his rear end too before they get chapped.
Last edited by green_vein; 01-23-2015 at 10:24 AM.
So says the not-too-classy-or-intelligent remark about post count being what makes and breaks ideas, opinions, and truths. Quit kissing his ass, he's a grown man and can handle himself.
Don't be a jerk. Think of a forum as a collection of like-minded friends. You have just joined this group of friends. What great "ideas, opinions, and truths" have you revealed and brought to the table? None, really. Is it therefore appropriate to come off as a smart-ass, know-it-all a**hole? Probably not. I'm not kissing anybody's ass, boy. Just show some basic respect, or STFU and GTFO.
No matter who you are or who you're talking to this is not appropriate.
If you can't handle a post like you should call in a moderator.
Please do not do that again.
---------- Post added 23-01-15 at 11:57 ----------
...that said,
Quote:
Originally Posted by green_vein
Maybe you should pay this site to let you be a Slackware forums sheriff.
He may not.
I'm the only Sheriff in town.
Now you try and fit in, you hear?
Else I'll be telling you to get your Pinto and ride on out of here.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.