Reaction score: 116
If you list all the current services you will see things like "network","network.em0", "network.wlan0", and more. These "network.<device>" services can be started/stopped/restarted individually *without* touching any other network devices and helping to ensure stable network connectivity on servers and such even when making configuration changes to particular devices. This is a ton better than the old way of completely tearing down and rebuilding the networking stack just because you wanted to change a static IP on one device.
ifconfig_em0="inet 10.10.10.100 netmask 255.255.255.0"then
#ifconfig em0 down | upfor that particular interface. That is not tearing down a network stack. I believe this applies to the
systemd? This daemon supervisory role you talk about, sounds a lot like what
systemdis said to do. The difference, if I understand it right, is that the OpenRC project has a narrower scope, respecting the Unix philosophy. May you kindly answer this one, if you are informed on it.
Reaction score: 10
Reaction score: 373
Who reboots their laptop every day?
Reaction score: 333
Reaction score: 653
I already hate it. Smells a lot like Linux. No, thanks, I like the current RC. I also see no benefit if a system boots faster.