Re: Boot log

On Sun, 25 Mar 2007, in the Usenet newsgroup comp.os.linux.setup, in article
<eu5uc5$am5$1@xxxxxxxxxxxxxx>, Don Phillipson wrote:

How can I save to a text file what the screen displays on booting?

You may not be able to.

This first-time installation of Xandros = Debian generates on boot at
least 50 commands and confirmations, a couple of which are "not found."

Boot scripts are run by a shell - in Linux this is typically bash, and
like all shells there are one input and two places for outputs to go.
One is "standard output" (a.k.a. stdout) and by default this is the
console though it's normally directed at something else - perhaps a
file. The _other_ output is "standard error" (a.k.a. stderr) and
this is directed to the console/terminal where the command is being
run. This content _can_ be redirected to a file, but this is rarely
the case in bootscripts.

It would be convenient to see a record in case any should/could be
fixed.

Depends on how your system is booting. If you are booting to some
GUI login, you _may_ be able to pause the screen during boot (try
pressing the left Ctrl and S key at the same time). You _may_ also
be able to scroll back through the frame buffer if BEFORE YOU LOG IN
you press the left Ctrl and PageUp keys.

"not found" sounds as if your boot scripts are missing a PATH
statement, or are calling for stuff in the wrong place (highly
unlikely), or it's trying to run stuff that isn't installed. A way
of checking this is to look through the boot scripts themselves
(they are written in what passes for English). Start at /etc/inittab
and see where the path leads.

Old guy
.