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.
How can I access the messages I get on startup once I've logged in?
I mean after the little grub screen where I choose my kernel, all those nice messages that scroll past telling me which things are starting and which things have failed. Usually they go by so fast I can't read them (and no, hitting pause on my keyboard doesn't work) but I'm sure they must get stored somewhere. I've looked around in /var/log but I don't really know what these messages would be called.
Why not just read the file that's already present (if it is present on whatever system you are running)? /var/log/dmesg and while you're there, there's more of the same type stuff in /var/log/messages if your system produces that file too. (they also can be found in /var/adm)
Syg00, what is "something like bootlog"? Does that mean /var/log/bootlog? Also, Grapefruitgirl, what is "the same type stuff"? Is that just a copy of the startup messages or other messages entirely? I'm not trying to be pedantic, I'm just a bit dense.
I tried dmesg and got a TON of messages. I mean, my terminal was scrolling for about five minutes. Guess that's why you suggested printing to a text file. Is there anyway to just get the errors, not the things that went right?
PS: Love the username, Kilgore. Vonnegut's my favorite author.
Well, on my system, /var/log/dmesg and /var/log/messages contain about 98% the same information. The files of the same name in /var/adm/ also contain the identical information.
As is often enough (I'm new to linux also) I could be off-track here, but I thought *MOST* linuxes produce these same files during bootup.
Getting *just* the errors might be more trouble than it's worth, but the bootup can be tweaked in various ways to lessen the amount of junk that is outputted. Such things as debug levels from drivers and kernel components can usually be configured to me more or less verbose.