@mirabilos @ska @navi 1/ running it as daily driver. The main problem is that you're kinda forced to run elogind, and that user services should be tested / integrated more. I do not have any energy to get user services e.g. for pipewire upstreamed. There's also the issue that some packages ship sysvinit scripts, and you have to use those over the a shorter, concise openRC one. I think diversions could fix that,

@mirabilos @navi @ska /2
might need to talk to a fellow DD about it.

I also want to create a minimal installation script with mmdebstrap, so I don't need to manually purge systemd and reinstall openRC.

@mirabilos @navi @ska

Unfortunately most heavily favour systemd, and even a (hidden) option in the installer is likely not happening.

@navi @ska @mirabilos well, some maintainers even dropped them without any comment, thus breaking things. Will openRC then prefer the ones in /etc/rc? Then I can start rewriting all of them.

@navi @ska @mirabilos great :) I honestly believe openRC + seatd is the future. udev is ok, but the rest of the systemd operating system can die for all I care.

@mirabilos @navi @ska I wouldn't think so. A major issue would be getting those scripts upstreamed and then shipped in Debian

@navi currently sysvinit scripts in Debian are shipped in /etc/init.d so if /etc/rc has a higher priority then this is great since "pure" openRC scripts can be used over sysvinit ones.

@navi my concern is mostly having a place for native init scripts they can live in while not conflicting with the sysvinit ones. In Debian a package must not ship the same file under the same path.

@navi right. Well, once this change lands, I hope I can dedicate some time to write native init services for openRC for a minimal install (cron, ssh, boot stuff,...)