16:31 <farkuhar> SiFuh_: following through on a boast about BSD-style init scripts ... can you imagine the CRUX rc.conf looking more like this? https://0x0.st/84Z9.conf

16:32 <SiFuh_> We don't modify that farkuhar. That's the defaults.

16:33 <SiFuh_> farkuhar: https://dpaste.com/7MQYMK9A9.txt Try this example.

16:34 <farkuhar> Notice how many daemons are provided by OpenBSD "base". The startup sequence doesn't have to be managed by hand for the daemons in "base", they only need to be enabled or disabled by setting the corresponding *_flags. The only equivalent of the CRUX array SERVICES is the string pkg_scripts, which specifies daemons installed from packages.

16:45 <farkuhar> I'm reviewing the Configuration chapter of the CRUX Handbook, to see what would need to be changed if we consolidated the network settings in rc.conf (currently users are told to edit /etc/rc.d/{net,wpa_supplicant} in-place). The network configuration subsection could be shortened significantly, if we didn't have to provide full examples of modified /etc/rc.d/net

16:48 <farkuhar> Those examples of modified /etc/rc.d/net could be replaced by one- or two-line snippets meant for a purely declarative config file, which users like ppetrov^ would be less hesitant to customize.