[solved] what is going to happen now that eudev is not going to be mantained?
 

change to udev, xudev, mdev?

Well, from:

https://gitweb.gentoo.org/proj/eudev...276ef9cb6f5dc6

Well, well, well...

Looks like the Gentoo Team wasn't "the pillar of fighting against Poettering's dictatorship and for freedom of choice on init systems" how many believed and some even evangelized in the past, BUT they had a very pragmatic reason - that that systemd does not worked in the past with that MUSL thing.

Secondly, looks like the anti-systemd movement is more and more a lost cause... even Gentoo goes full systemd and we are the last major Linux distribution who does not ship it.

Maybe is time to reconsider the goods hidden in this particular repository bellow?

https://github.com/Dlackware/systemd

After all, the particular software from the mentioned repository replaces (e)udev with great success. ;)

Or we fork Udev into SlackDev :)

When the Slackware and its community maintained its own complex software projects written in C/C++, to do it again?

Please, show me an example! :D

I for one, probably the most complex software made for Slackware that I've seen was that ALICE/YALI while Slackware 12.2 times. It was a set of graphical system tools made in Qt3 and containing even an installer and a partition manager like GParted.

Did you heard about it? Probably not, because from what I seen, the community wasn't interested on those graphical tools. They was not even interested to preserve the code. :p

That's WHY permit me to strongly doubt that Slackware will fork eudev and will be able to follow the systemd code for the foreseeable future. Let's hope that someone else will do it.

Gentoo will still use Open-rc just with udev instead of eudev,they will use both inits Open-rc and systemd

Let's hope that this will happen. But I doubt it that their solution will be systemd-free. Maybe they found a way to run UDEV from systemd in stand-alone mode? ;)

In fact, the UDEV is abbandonware since long years, because its maintainer - Kay Sievers is a founder of systemd and merged it on systemd.

Then, the EUDEV is/was the UDEV code extracted from systemd, where it is actively maintained.

IF the EUDEV is abandoned, the single maintained code of UDEV will be on systemd. :p

I really like that now wlroots doesnt depend on elogind they changed to seatd, just as flatpack first versions depended on systemd for long time ago that s not the case.

There's another way, to use a "systemd-shim" just like MX-Linux

The systemd-shim which as originally on Debian, then abandoned, but somehow still maintained by MX-Linux, permits to run the systemd services under a SysV init system.

https://packages.debian.org/stretch/systemd-shim

This means the adoption of systemd (and removal of eudev and elogind), but still to have the ability to use SysV init system, with the option to user to chose eventually booting on full systemd mode.

Also, the systemd-shim is a much smaller piece of software, and I guess less prone to be influenced by the changes from systemd. Then probably simpler to maintain by a programmer.

I'm probably putting out a minority opinion here, but if the simplest and easiest-to-maintain option (for Patrick, not necessarily for sysadmins, as that's a different discussion) is to adopt systemd, I say go for it. The Slackware team doesn't have the manpower to maintain complex software projects that have been deprecated by upstream.

I really hope that Slackware will not adopt systemd. if is not broken don't fix it.
i dont understand some users, if they like systemd so much there are others distros to choose, Debian, Fedora, etc
Also there is one user that seems to speak for everyone, he likes to say we this and we that likes to be rude with others users. Systemd choice is not up to you!!! if you like systemd so much why dont you create your own distro?
Also if a small distro like Artix linux can change their device manager why Slackware cant?
systemd is not the solution.
https://github.com/illiliti/libudev-zero

That's it? The MDEV of BusyBox with a custom library slapped on top of it? :o

How low is your stack regarding Slackware? Just that it does not ship systemd, not matters if follows the Apocalypse?

I am neither pro or anti systemd on Slackware (heck, I even struggled long time to tame elogind) but I cannot NOT observe that the systemd adoption will leave without work those few fundamentalists who hangs on the Slackware community, probably shunning away many good people.

So, I sincere believe now that the best way to heal the community and to make it grown is to adopt systemd.

I know, I know, probably you will quit in a rowdy way, and so will do some others, BUT you and them will be replaced by hundreds if not thousands new Slackware users. ;)

Obviously I can only speculate but it has been my perception that Slackware as it has existed from the beginning only adopts major technologies as necessary...


From the 14.2 changelog:
PulseAudio was the boogeyman for quite a while (not entirely undeserving of the reputation mind you), but there came a point where working around the decisions of upstream became impractical.

I don't believe this will be any different. If somebody else steps up to maintain eudev or fork and keeps the quality high, I could see us simply sticking with that.

Slackware lacking systemd likely has much more to do with keeping things simple than it does being part of some anti-redhat/systemd/Lennart crusade... if somebody wants a distro where that's a core philosophy then Devuan might be the ticket.

Personally I don't care if Slackware adopts systemd or not, all I care is that it remains a fully functional and stable operating system.

No, they will not be replaced by hundred or thousands of users, this hundred or thousands of users will still use Debian or Arch, why should they choose Slackware with systemd when others distros with systemd offers the same and in an easier way for example dependency resolution?. (i dont want automatic dependency resolution)
Still dont get why do you use Slackware when its seems you dont like how it is. It seems you want Slackware to be just a generic systemd distro. Whats next do you want pacman or apt to get packages Mr Pipewire?

Frankly, I barely care one way or the other. The init system is not the only reason I choose to use Slackware; actually, it's pretty far down the list. So if Patrick decides to switch to systemd, I'm sure it will be done well and just work, so it's okay with me. The same applies no matter what the course of action ends up being.

i care so in the case Slackware goes systemd i will delete my Slackaware partitions although i can change the init to runit or s6, and go where systemd is out of the question, Void linux, or Artix.