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.
I'm a total Linux newb with an installation of Slackware 10.2, kernel release 2.4.31 on a Sony VAIO laptop. So far so good. A lot of things are working, though I'm sure a lot of things are not working as they should.
When I boot, a lot of text scrolls by quickly on the screen, with occasional pauses. Not all of the messages are favourable: this or that failed to load, something loaded in read-only mode, but it all scrolls by too quickly to make a note. Is there a way to capture this boot text so that I can use it diagnostically? Or is there another systematic way to identify these problems?
dmesg will not show you all the stuff that scrolls by at boot. I do not know specifically about you distro, but for Debian I simply edited the file /etc/default/bootlogd and added the line "BOOTLOGD_ENABLE=Yes". After booting, I can then find all the boot messages in the file /var/log/boot
Also, in general it's OK for a few things to fail at boot time (e.g. probes of hardware you don't have). Usually what I do is look for things that aren't working and then go back to the boot messages and try to figure out why. The dmesg command mentioned above shows output from the kernel. If the failures occur after init (the first process that is responsible for starting all the other processes) and are caused by non-kernel programs, you'll need something like bootlogd. I don't have that installed by default on my Slack 10.2 system so you may need to go download it from linux-packages.net or build it from source and then add a line starting it in /etc/rc.d/rc.S (probably towards the beginning) as this script is executed towards the beginning of things.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.