Originally posted by Ibidem
View Post
Being able to start/stop services based on hardware events seems to be a pretty handy thing. (Why the heck does ubuntu on a desktop still bring up the battery monitoring service? Or bluetooth, when you have no Bluetooth adapters connected?)
Interestingly enough the hotplug executable is considered the child of PID 1 when created.
Originally posted by Ibidem
View Post
Originally posted by Ibidem
View Post
X was modular to maintainability issues, and to make it possible to use some parts of x in an embedded system. No X is being pulled into different projects and slowly being killed. However at the time it make sense to smash as of this common and vital functionality together.
Originally posted by Ibidem
View Post
Originally posted by Ibidem
View Post
There is an fsck service, which does essentially the same thing as the fsck init script.
If anything I'd imagine if there was it's own copy, it would be a straightfoward fork that could be passed arguments via a socket, rather than needing some sort of shell. I can't imagine why they'd need or want to touch the functional logic of it.
Leave a comment: