IssueRaiser

When you boot Linux, the init system loads the drivers you need, turns on your network connection, fires up the necessary system service ...

When you boot Linux, the init system loads the drivers you need, turns on your network connection, fires up the necessary system service and then loads the desktop. Without an init system, you have no way to do anything. Actually I'm pretty sure it's udev that handles module loading these days (which isn't related to the functions of init(8) and process management, even if it's part of systemd now), or alternately one can use the kmod tools manually. This is a misleading interpretation in general. The init system (though really the process manager) starts the services to enable all these things. The simplest form is just a synchronous tool that exec()s binaries.

Posted by vezzy-fnord on May 5, 2015, 2:28 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.6,500 issues0 comments

hackernews (Network)

When you boot Linux, the init system loads the drivers you need, turns on your network connection, fires up the necessary system service ...

vezzy-fnordMay 5, 2015, 2:28 PM

When you boot Linux, the init system loads the drivers you need, turns on your network connection, fires up the necessary system service and then loads the desktop. Without an init system, you have no way to do anything. Actually I'm pretty sure it's udev that handles module loading these days (which isn't related to the functions of init(8) and process management, even if it's part of systemd now), or alternately one can use the kmod tools manually. This is a misleading interpretation in general. The init system (though really the process manager) starts the services to enable all these things. The simplest form is just a synchronous tool that exec()s binaries.

Comments (0)

No comments yet. Start the discussion.

Comment on this issue