Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Init systems are quite important for those that have to manage servers, typically sysadmins.
The location or function of init scripts is not why there's so much noise surrounding the adoptation of systemd. Calling systemd an "init system" is at best misleading, because it does an awful lot more than init ever did, and is continually absorbing and attempting to deprecate various system components that have little or nothing to do with the init process.
For instance, neither hotplug/udev nor syslogd have ever been part of init, but systemd has incorporated the former and is attempting to replace the latter. This has obvious implications for anyone depending on the functionality of those subsystems.
so what is the big fuss? why would a poor init system steer people away from a distro they have used for years.
can it really be this important? i mean how many times a day are you going to reconfigure start-up services etc...i dont understand this.
The problem that some people have with systemd is not its init part, it is the additions to it. While systemd started out as an init system it now is a system of building blocks for a complete Linux OS, it provides, besides the init part, services for logging, network setup, bootloading, session management, time/timezone settings, ..., basically anything that is needed to build a basic OS to build up from.
I will not go any further with that, if you want to have more information why people are opposed to systemd just go ahead and read one of the systemd threads on this forum, but be aware that you will see a lot of FUD, so better fact check extensively.
Thanks for all the reviews...busy watching a video on systemd on youtube...interesting...its 50 min long.
if you want to know what an init does, read the Slackware rc.S and rc.M in /etc/rc.d/
(in that order, /etc/inittab and "man inittab" explain why)
watching a presentation about systemd wont teach you anything about how a system initializes