SlackwareThis Forum is for the discussion of Slackware Linux.
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.
None that I know of. When I need to do something like that, I set the host up to use a serial console, then attach another computer running some serial terminal software such as C-Kermit or minicom (or on a Windows host, hyperterm). Then you can see all of the console output, scrolling back as necessary to see the earliest messages. Requires having a bootloader that can use a serial console for the most complete results.
Distribution: Slint64-14.2 on Lenovo Thinkpad W520
You can see very early messages if you append kernel parameter "earlyprintk=vga" or "earlyprintk=serial[,ttySn[,baudrate]]", for instance, to the command line at boot time.
kernel and driver developpers can also use "ddebug_query= [KNL,DYNAMIC_DEBUG]"
See /usr/src/linux/Documentation/kernel-pameters.txt and /usr/src/linux/Documentation/dynamic-debug-howto.txt to know more.
Small tip: when a program displays data on the screen faster than you can read it, you can stop its execution with Ctrl+s and resume it with Ctrl+q
This is a reminiscence of controlling the flow of data on a communication line (e.g. RS232 serial) sending the "XOFF" (or "Transmit off) and XON (or Transmit on) signals, which was useful when the receiver couldn't process the data as fast as they were sent, see this page.
For the records this reminds me that this kind of software flow control have been used for connections between industrial terminals and a mini computer at the super high speed of 1200 bits per second in a project of which I was in charge 33 years ago...
Last edited by Didier Spaier; 07-27-2013 at 03:09 PM.