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.
My main system is slackware64, but I have kept a .deb distro to install those packages which just are not worth the effort installing in slackware.
That 'spare' system was Debian, despite it's use of systemd. But I want to come over from 'the dark side' if possible, because I do not want systemd either. Does Devuan have a comparable repo? Are debian packages installable in most cases, or is that a non-starter?
Last edited by business_kid; 04-03-2024 at 01:32 PM.
It of course has its own repositories, but they work by being layered on top of Debian and have substitutes for only the systemd-infected packages. Everything else is otherwise as-is from the normal Debian repositories via the Devuan ones.
that is completely nonsense. Why on earth do you need to care about systemd on a spare system, which is only used to test something "which just are not worth the effort installing in slackware". In most cases it is completely irrelevant (if you have systemd based OS or not), because those packages do not depend on it.
And because of your attitude you will never use anything which really depend on it.
that is completely nonsense. Why on earth do you need to care about systemd on a spare system, which is only used to test something "which just are not worth the effort installing in slackware". In most cases it is completely irrelevant (if you have systemd based OS or not), because those packages do not depend on it.
And because of your attitude you will never use anything which really depend on it.
Removal of systemd is highly relevant due to how it is metastasizing upstream through many of Debian's packages.
And that is in turn relevant because it introduces (unnecessary) complexity which is the cause of (unnecessary) security problems.
There are almost an infinite number of examples resulting from added complexity. However, if you need a recent one, just look at how Debian's unnecessary systemd dependency which they added to OpenSSH was used by a compromised package, xz, to add a backdoor to OpenSSH.
There is a lot to unpack with the xz compromise, including whether projects should be dropped unless there are a minimum number of vetted, active developers. However, at the end of the day an unnecessary systemd dependency opened the way for a backdoor in systemd-using distros.
that is definitely a different issue, a special case, not a general problem with systemd. And also not about any package "which just are not worth the effort installing in slackware".
that is completely nonsense. Why on earth do you need to care about systemd on a spare system, which is only used to test something "which just are not worth the effort installing in slackware". In most cases it is completely irrelevant (if you have systemd based OS or not), because those packages do not depend on it.
And because of your attitude you will never use anything which really depend on it.
Understandable, if frank. The main things I want in a second system are things like Kicad, fpga packages or similar. If I had to start there, the 'second system' could easily become my first system for months on end. Hence, the caution.
Yes, I know the xz backdoor involving systemd and that liblzma was actually somewhat unnecessary as a dependency of Systemd. But if some professional outfit were putting years into building themselves a unique-to-them backdoor, do you really think they'd only watch the one project?
Last edited by business_kid; 04-04-2024 at 06:51 AM.
Yes, I know the xz backdoor involving systemd and that lib was actually somewhat unnecessary. But if some professional outfit were putting years into building themselves a unique-to-them backdoor, do you really think they'd only watch the one project?
No, definitely not. They may have a non-systemd based target too. Or more. This is not the first case when officially released packages were infected, and it certainly won't be the last.
Resistance may be futile, but the borg-like assimilation of non-init functions that the systemd crowd continues to practice will be resisted by some, regardless...
Resistance may be futile, but the borg-like assimilation of non-init functions that the systemd crowd continues to practice will be resisted by some, regardless...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.