InitNG is one of the most often mentioned possible init replacements. Since it is available as a package in Fedora Extras it can be easily tested. Running on Fedora Core 6 it shows quite some bugs – but impressive speed improvements. In the meantime, a wiki page to bring Upstart to Fedora has been created and filled with first information.
After the IBM summary of Upstart and InitNG I got curious about possible improvements – and started playing around. First I played a bit with Upstart because their concept convinced me most. However, I wasn’t able to bring it up and running because I’m not fit enough on some init basics.
However, I set up a wiki page at the Upstart wiki. Hopefully others will join and solve the problem currently existing.
While playing around I noticed that InitNG is part of Fedora Extras. Therefore I gave it a try, and was pleased by the result! There was a minor bug preventing the system to totally come up, but that was easy to fix.
Still, some things are not working like they should: NetworkManager was not started by default and the virtual terminals were all not set to the system local. Still, the bootchart result is impressive:
These less than 35 seconds look a bit different from the 90 seconds I have with the traditional init system. However, comparing these numbers keep in mind that first at leats the NetworkManager stuff is missing, and that second other services might not have been started – I haven’t checked that completely yet. Still, I think even if one or two services are missing the number will not increase by 60 seconds. As you can see parallel starting of services already shows results.
If someone is interested in testing InitNG: of course the
service handling is different to the old init system. So here are the most important information:
- showing all possible services:
- adding service “NetworkManager” to the runlevel “default”:
ng-update add daemon/NetworkManager default
- removing service “NetworkManager” from the runlevel “default”:
ng-update del daemon/NetworkManager default
- start the service “NetworkManager”:
ngc -u daemon/NetworkManager
- stop the service “NetworkManager”:
ngc -d daemon/NetworkManager
- restart the service “NetworkManager”:
ngc -r daemon/NetworkManager
- see a list of running processes:
- reboot system:
- stop system:
Btw., ngc means “next generation control”, that’s probably easier to remember.
Don’t forget to fix the above mentioned bug until new packages are available, in other cases the system wouldn’t start.
In general, I’m very pleased to see InitNG is such a good state. I hope that I can also test Upstart soon.