Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have been using Linux full time since 2004. I feel I am a competent user but I don't really understand how it works very well. I think diving a little further in would make me a better programmer and user.
I know some people read and build linux-from-scratch. I was wondering about another approach.
If I read up more on the bootstrapping sequence and typed:
ps -aux
and I factored out things like the shell I had to run this in and bash but I studied each process that was started on a newly booted system, would I have a good idea of what is keeping it up and running, offering services? As a side note, I understand that several of the ps results are instances of the same program, for example getty.
The best way to find out what gets started at boot is probably to work through the init scripts (assuming you are using sysvinit). That's what I did when I started. Read the script in one console, have man pages showing in another and just work out what each script does.
Also notice that some of the threads (whose names always begin with "k") are kernel threads.
These "threads" are part of the kernel, and they execute in kernel space under a very special set of rules. This facility allows portions of the kernel to be independently dispatched, with all the advantages that "being a thread" offers, while still remaining "part of the kernel." For instance, a kernel thread can initiate an I/O operation and then wait for that operation to complete, much like a user-land thread can do.
Last edited by sundialsvcs; 03-21-2017 at 03:47 PM.
Best wishes; ENJOY studying! p.s. try a '3-piece 7MB' mll! VBoxes?
p.p.s. I ran across a SINGLE free sample chapter .pdf of a [RHCE] book I liked at my local library, on the boot process, GRUB, systemd here. Of course, there's tons 'on the net'; try adding 'wiki' to your web-searches, to get great tutorial articles!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.