[SOLVED] I want to review the boot-time info that's going to the console?
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.
Location: Aimlessly adrift on a sea of documentation, searching for a rock to finally wreck upon
Distribution: Originally: Slackware 3.1; Now Slackware 13.37
Posts: 41
Rep:
I want to review the boot-time info that's going to the console?
I'd really like to be able to examine all the information that flys off the top of my terminal when my system boots (off of fd0, the only way I've done it, so far):
review of "similar threads" yields nothing;
seemingly not a man pages item;
have not found any how-to's that cover this;
the daemons for logging are third-to-the-last before logon prompt (and still displayed, the ONLY reason I know THAT);
seems like it should be a compile-time sw-switch settng (sub-optimal since I'm still not comfortable with compiling kernels);
but I was hoping it's already being captured in some log file somewhere that I'm as yet unaware exists.
I do realize that if I had a printing console, this would be unnecessary.
The "dmesg" command is your friend!
[code]man dmesg[code]To review what has whizzed by the screen on boot-up, just type "dmesg|more". Note that depending on the Linux distribution we're talking about, you might have a "dmesg" logfile in /var/adm or /var/log already.
If you don't, just add "dmesg | tee -a /path/to/a/logfile-`date +%Y_%m_%d-%H%M`" to your rc.local script (it's in /etc somewhere).
Good luck!
P.S: Are you really running "Slackware 3.x" or "Slackware 2.x"? Why?
Location: Aimlessly adrift on a sea of documentation, searching for a rock to finally wreck upon
Distribution: Originally: Slackware 3.1; Now Slackware 13.37
Posts: 41
Original Poster
Rep:
Xeleema,
GENIUS you are! so much obliged
Answering "Why Slackware 3.1.0 (uses linux kenrnel 2.0.0)?" is probably a longer story than you want to hear, but the readers digest version is that
I started there in 1995 and never got out of 1st gear. And that primarily because I lacked network capability.
A lot has to do with trying to solve the kind of thing I just learned with your help, which include:
probing issues on two pci devices that happened right at the top of the boot, and was never able to capture before!
The only two PCI boards I have are a serial port card that I used before I had a NIC, plus now the NIC (as of just this last year).
Since I really have never used the serial port card, I can probably chuck it and just work on solving the NIC issue.
Ironically this same "vintage" no-rev-Pentium iron running Win95 adopted the NIC, right out of the box, connecting with my current dsl service provier.
I'll probably still be "stuck in the mud" for a while because I don't think I can get this rev of Slackware to work with my DSL/DHCP.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.