3 ms·
My favorite remains BSD style (rc.conf+rc.d/) init - which for some reason receives no mention here. Arch Linux used to have it too, but then inexplicably dumpe
by sdfjkl 14y ago
My favorite remains BSD style (rc.conf+rc.d/) init - which for some reason receives no mention here. Arch Linux used to have it too, but then inexplicably dumped it.
http://www.freebsd.org/cgi/man.cgi?query=rc&sektion=8 http://www.freebsd.org/cgi/man.cgi?query=rc&sektion=...
- naner 14y agoInexplicably? They didn't want to fight against upstream. You'd have to maintain your own scripts for every daemon you supported if you didn't use systemd. Also other software like udev is getting sucked into systemd as well. Arch is a small distro and doesn't have the development power to customize everything.
- antihero 14y agoBecause having long bash scripts and every process implementing it's own daemonisation in weird and wonderful ways is redundant and inconsistent, and makes making something a daemon frustrating.
- Sssnake 14y ago>Because having long bash scripts Has nothing to do with BSD style init? No part of the system should be either long or bash. >it's own daemonisation in weird and wonderful ways is redundant and inconsistent Calling daemon() is not that hard. >and makes making something a daemon frustrating That doesn't even make sense. People writing shitty software that should be a daemon but isn't makes that "frustrating".