Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
Trust-wise, I absolutely agree with you. BSDs look to be saner systems in a lot of ways. Strong philosophical differences, but I am truly glad that they exist.
You could also run Slackware (or Salix) which is the closest to Unix while still being Linux.
I've been on Slackware for a while now. It is all the way nice. But even venerable Slackware might have to choose between no software, or undesirable software.
Distribution: Slackware/Salix while testing others
Posts: 1,718
Rep:
Quote:
Originally Posted by Fat_Elvis
I've been on Slackware for a while now. It is all the way nice. But even venerable Slackware might have to choose between no software, or undesirable software.
unlikely, most of those systemd hard dependencies are put there by the distro maintainers.....PV and Slack team are very much against adding it. They are very familiar with avoiding unnecessary software that other distro. are quick to adopt.
unlikely, most of those systemd hard dependencies are put there by the distro maintainers.....PV and Slack team are very much against adding it. They are very familiar with avoiding unnecessary software that other distro. are quick to adopt.
Slackware is basically dictated by the main boss, if he decides that SystemD will be, it will be.
Ok. I don't want to read to the bottom of that page, but it seems to boil down to "we're going with the flow." I could care less about the others, but for a distro as respectable as Debian, I think that was a bit weak.
True, but in all fairness, I believe the Slackware team is working very hard to stay the course despite overwhelming pressure from all sides.
Honorable mentions of Gentoo and LfS. I'm not aware of any other distros over on this side of the divide.
Ok. I don't want to read to the bottom of that page, but it seems to boil down to "we're going with the flow." I could care less about the others, but for a distro as respectable as Debian, I think that was a bit weak.
I think that it would be good for Linux that Slackware goes too for SystemD.
Debian argues that most distro i.e. fedora,... use SystemD. This is their argument. So they use SystemD.
I would be good that Slackware go for SystemD too since all Linux distributions must have something in common. SystemD will define Linux entity.
BSD is UNIX and if you want Linux, it is Linux and has nothing to do with UNIX.
...would be good that Slackware go for SystemD too since all Linux distributions must have something in common...
The kernel is all that they need to have in common; if all distributions go systemd there will be fewer Linux (and more BSD) users*.
For the record, I don't hate systemd, and if it were small enough in scope that its replacement in a distribution were trivially easy I would almost certainly still be a systemd user. But, since it can't be easily replaced if things go pear shaped, I really can't trust it.
*Not a made up statistic, I just conducted a poll (with a sample size of 1).
I would be good that Slackware go for SystemD too since all Linux distributions must have something in common. SystemD will define Linux entity.
BSD is UNIX and if you want Linux, it is Linux and has nothing to do with UNIX.
The last part of your post is unclear.
If the point here is to see Linux fall and all glory to BSD, I would point out that if you are happy with your distribution the way it is, a large influx of users might be the last thing you want.
If the point here is to see Linux fall and all glory to BSD, I would point out that if you are happy with your distribution the way it is, a large influx of users might be the last thing you want.
OK. Linux and BSD are luckily there for everyone, great OS, best of all time.
SystemD is a problem currently for the Linux community.
Clearly there aren't just all in favor of SysD, just looking at the poll results on LQ.
The core issues for me are:
- there is no specification of what it actually is. So it keeps gobbling up parts which have no business with pid 1 at all.
- the whole mentality regarding bugs or general code quality.
- documentation? Where can I find documentation on it?
- bloatware. Bad idea for something which manages pid 1.
So far we've had 27 answers and the best anyone can come up with is "it's contrary to the spirit of Unix" or anecdotal complaints. When I hear some-one screaming that it bricked their computer, then I'll worry. If we avoided all change in Linux, we'd still use Lilo, have to do all configuration by editing scripts, and lack proper package management. Oh, that would be Slackware, wouldn't it?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
systemd blocks netflix :D
