I know dmesg will show the boot info. But I would like to understand more
of what is being spit out at me. :-)

Where is a good place to find out what the different things mean?
I don't feel like building LFS, I tried it once and just don't have the
patience or time. I have the time to study, just don't want the family PC
down for that long.

TYIA
--
dw

[ Post a follow-up to this message ]

In article <pan.2005.05.27.01.48.01.186472@netscape.net>,
linxlvr@netscape.net says...
> I know dmesg will show the boot info. But I would like to understand more
> of what is being spit out at me. :-)
>
> Where is a good place to find out what the different things mean?
> I don't feel like building LFS, I tried it once and just don't have the
> patience or time. I have the time to study, just don't want the family PC
> down for that long.
>
> TYIA
>

I would do a few things with the dmesg messages.  First step through
them using the less command and get a sense of how things are staged
when the linux system boots.  For some reason, I've always been
interested in how the scsi devices get id'ed.  I have a server with
nothing but scsi stuff like a disk drive, tape drive, cdrw.  I always
read how the device gets identified by the kernel.

Another interesting point is how all the network services get turned on
and in what order.  Look for how your eth0 turns on.  See how sendmail
or whatever runs.

Finally, since I run linux on a laptop, I am always looking for how the
acpi stuff is working and what pcmcia reports when the system boots.

These are just a few of my points that I find interesting.  I bet if you
step through all of it, you'll find a lot of interesting data points
from which to do google searches of things 

--
Michael Perry | do or do not. There is no try. -Master Yoda
mperry@lnxpowered.org | http://www.lnxpowered.org

[ Post a follow-up to this message ]

if you type

dmesg | more you can scroll through the output.

if you type

dmesg > filename

it sticks the output in a file (in this case filename) open with your
favorite editor, or print and just read through it,  If you want to
understand whats going on, some things are obvious (such as refereces to
hardware, even though the information associated with these may need
looking up),  where so mark these off,  then look things up

so doing a search for any of the data listed should come up with
something,  try using www.google.com/linux,

Best of luck,  better still print the output out and keep a record of
anything you learn relating to this,  large lever arch files, a set of
dividers and a pad of A4 paper, is very useful for the linux newbie.

Paul


Michael Perry wrote:
> In article <pan.2005.05.27.01.48.01.186472@netscape.net>,
> linxlvr@netscape.net says...
> 
>
>
> I would do a few things with the dmesg messages.  First step through
> them using the less command and get a sense of how things are staged
> when the linux system boots.  For some reason, I've always been
> interested in how the scsi devices get id'ed.  I have a server with
> nothing but scsi stuff like a disk drive, tape drive, cdrw.  I always
> read how the device gets identified by the kernel.
>
> Another interesting point is how all the network services get turned on
> and in what order.  Look for how your eth0 turns on.  See how sendmail
> or whatever runs.
>
> Finally, since I run linux on a laptop, I am always looking for how the
> acpi stuff is working and what pcmcia reports when the system boots.
>
> These are just a few of my points that I find interesting.  I bet if you
> step through all of it, you'll find a lot of interesting data points
> from which to do google searches of things 
>

[ Post a follow-up to this message ]