I far prefer open-rc over systemd, but I've seen a lot, lately, of releases that _rely_ on systemd. People seem to think it's the standard, so that's what people target, instead of trying to make stuff that's init-agnostic. Perhaps that's what's driving it - the things that Gentoo supports in open-rc land are extra work for someone (which I highly appreciate), but at the end of the day, that's often the tightest constraint on a distro: maintainers. It's often just about "who is going to do the work?", followed by "can we make the experience as good as we have it with systemd?". It's a tall order, I think.
I literally switched to Gentoo from some deb-based distro (I forget which: I cut my teeth on debian, used it for years, then internet was fast enough to use something that updates more regularly, so I switched to ubuntu - also, from my home country! - and variants thereafter - some closer to ubuntu (kubuntu, mint), some further away (LMDE), but always deb-based. When systemd just landed, I had so much crap with it - machine would stall at shutdown, services would just die, and where the hell are my logs? (didn't know about journalctl, and anyway, why can't I just have text logs by default?)). At the time, they were the _only_ distro with first-class support that was considered "ready". Devuan was forming, but I had had enough with Poettering's droppings (pulseaudio also died on me - frequently: enough that I wrote a watchdog script for it).
The amount of time it took Devuan to do the switch is indicative of the effort, imo.
"where are my logs!!!" lol, exactly. they make a complex binary for to read logs. Its droppings all the way down with ppring. Annoying that he was working on some legit hanging fruit, but going about it in the worst ways.
Same, I landed on gentoo after trying devuan for some projects and finding out that at the time, the devuan repos were stale in certain areas and packages were not built with options i needed.
At the time I was on a journey coming from BSD to linux to take advantage of all the krazy new kernel features.
Prior I would use debian stable for "serious biz", but BSD for anything personal. Then systemd became a thing, and i sorta underestimated how everyone surrendered they pid1 so quickly to this huge complex doit-all software. I figured almost every distro would have its own init, like package managers.
Is devuan better at repos now?
What are the issues with supporting init-freedom? The most common, sensible sounding complaint I hear, is per-package management work.
Can't a script just translate the per-package configurations over to other inits?
With all this AI assisted development, shouldn't this be easy?
I understand that over the years systemd has gotten its hooks deep into the system. Whatever special features it has, can possibly be implemented using something else or just sacrificed.
At the very least i would like NixOS to support a basic base install with init-freedom.
The most common software without experience issues.
Can even using those maintained scripts as a working example of init-freedom for other package maintainers
I use Gentoo, with open-rc, so hear me out:
I far prefer open-rc over systemd, but I've seen a lot, lately, of releases that _rely_ on systemd. People seem to think it's the standard, so that's what people target, instead of trying to make stuff that's init-agnostic. Perhaps that's what's driving it - the things that Gentoo supports in open-rc land are extra work for someone (which I highly appreciate), but at the end of the day, that's often the tightest constraint on a distro: maintainers. It's often just about "who is going to do the work?", followed by "can we make the experience as good as we have it with systemd?". It's a tall order, I think.
I literally switched to Gentoo from some deb-based distro (I forget which: I cut my teeth on debian, used it for years, then internet was fast enough to use something that updates more regularly, so I switched to ubuntu - also, from my home country! - and variants thereafter - some closer to ubuntu (kubuntu, mint), some further away (LMDE), but always deb-based. When systemd just landed, I had so much crap with it - machine would stall at shutdown, services would just die, and where the hell are my logs? (didn't know about journalctl, and anyway, why can't I just have text logs by default?)). At the time, they were the _only_ distro with first-class support that was considered "ready". Devuan was forming, but I had had enough with Poettering's droppings (pulseaudio also died on me - frequently: enough that I wrote a watchdog script for it).
The amount of time it took Devuan to do the switch is indicative of the effort, imo.
"where are my logs!!!" lol, exactly. they make a complex binary for to read logs. Its droppings all the way down with ppring. Annoying that he was working on some legit hanging fruit, but going about it in the worst ways.
Same, I landed on gentoo after trying devuan for some projects and finding out that at the time, the devuan repos were stale in certain areas and packages were not built with options i needed. At the time I was on a journey coming from BSD to linux to take advantage of all the krazy new kernel features. Prior I would use debian stable for "serious biz", but BSD for anything personal. Then systemd became a thing, and i sorta underestimated how everyone surrendered they pid1 so quickly to this huge complex doit-all software. I figured almost every distro would have its own init, like package managers.
Is devuan better at repos now?
What are the issues with supporting init-freedom? The most common, sensible sounding complaint I hear, is per-package management work. Can't a script just translate the per-package configurations over to other inits? With all this AI assisted development, shouldn't this be easy? I understand that over the years systemd has gotten its hooks deep into the system. Whatever special features it has, can possibly be implemented using something else or just sacrificed.
At the very least i would like NixOS to support a basic base install with init-freedom. The most common software without experience issues. Can even using those maintained scripts as a working example of init-freedom for other package maintainers