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!
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.
Quick question : How do I "recall" what info has been contained in the "boot script"? I am having "issues" with a couple of things at the moment, and I need to be able to read what scripts are being passed with booting my system.
You have the whole startup sequence in /etc/rc.d/. After kernel boot, it checks in /etc/inittab what to do, and in Slack's case it'll be running /etc/rc.d/rc.S. When this script is finished, it's "Going multiuser..." and this is the /etc/rc.d/rc.M script. Take a look in /etc/rc.d, it's quite educational
Sorry, but I was wnting to know how do I go about reviewing all the scripts that run prior to login. You know, those commands that go rushing by so quickly, and if you are looking to troubleshoot a problem one would imagine that "stuff" is pretty important.
Sorry if what I was asking help with was mistaken for what I might have thought was "Boot Script".
Originally posted by justaguynsrq Sorry, but I was wnting to know how do I go about reviewing all the scripts that run prior to login. You know, those commands that go rushing by so quickly, and if you are looking to troubleshoot a problem one would imagine that "stuff" is pretty important.
Sorry if what I was asking help with was mistaken for what I might have thought was "Boot Script".
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
What mightymouse says is good advice.
