Re: Tracking boot messages

2011-01-17 Thread Tom H
On Mon, Jan 17, 2011 at 11:43 AM, Stephen Powell wrote: > On Mon, 17 Jan 2011 11:02:15 -0500 (EST), frank thyes wrote: >> On Mon, 2011-01-17 at 10:53 -0500, Stephen Powell wrote: >>> Hello, list.  I am trying to find a way to track boot messages.  I know >>> about >>> things like >>> >>>    dmesg

Re: Tracking boot messages

2011-01-17 Thread Camaleón
On Mon, 17 Jan 2011 13:03:27 -0700, Bob Proulx wrote: > T o n g wrote: >> Camaleón wrote: >> > What I can't see is why this logging facility is not enabled by >> > default. I also think it should be kept in a unique file, instead to >> > be split in "/ var/log/dmesg" and "/var/log/boot", IMO it wo

Re: Tracking boot messages

2011-01-17 Thread Bob Proulx
T o n g wrote: > Camaleón wrote: > > What I can't see is why this logging facility is not enabled by default. > > I also think it should be kept in a unique file, instead to be split in > > "/ var/log/dmesg" and "/var/log/boot", IMO it would be easier to read, > > interpret and debug... > > Strong

Re: Tracking boot messages

2011-01-17 Thread Pascal Hambourg
Stephen Powell a écrit : > >> Set BOOTLOGD_ENABLE=YES and examine /var/log/boot or dmesg after >> rebooting. > > Hmm. Well, that helps. dmesg still does not contain the message from > console-setup Of course not. dmesg displays only kernel messages. This is completely different from messages di

Re: Tracking boot messages

2011-01-17 Thread T o n g
On Mon, 17 Jan 2011 16:34:21 +, Camaleón wrote: > What I can't see is why this logging facility is not enabled by default. > I also think it should be kept in a unique file, instead to be split in > "/ var/log/dmesg" and "/var/log/boot", IMO it would be easier to read, > interpret and debug...

Re: Tracking boot messages

2011-01-17 Thread Frank
Connect a serial cable to your console port and use minicom on you laptop to save the output ;) Frank Von meinem iPhone gesendet Am 17.01.2011 um 17:43 schrieb Stephen Powell : > On Mon, 17 Jan 2011 11:02:15 -0500 (EST), frank thyes wrote: >> On Mon, 2011-01-17 at 10:53 -0500, Stephen Powell w

Re: Tracking boot messages

2011-01-17 Thread Stephen Powell
On Mon, 17 Jan 2011 11:02:15 -0500 (EST), frank thyes wrote: > On Mon, 2011-01-17 at 10:53 -0500, Stephen Powell wrote: >> Hello, list. I am trying to find a way to track boot messages. I know about >> things like >> >>dmesg|less >> >> and >> >>less /var/log/syslog >> >> but they don'

Re: Tracking boot messages

2011-01-17 Thread Tom H
On Mon, Jan 17, 2011 at 10:53 AM, Stephen Powell wrote: > > Hello, list.  I am trying to find a way to track boot messages.  I know about > things like > >   dmesg|less > > and > >   less /var/log/syslog > > but they don't cover everything.  For example, /etc/init.d/console-setup > issues a messag

Re: Tracking boot messages

2011-01-17 Thread Camaleón
On Mon, 17 Jan 2011 10:53:51 -0500, Stephen Powell wrote: > Hello, list. I am trying to find a way to track boot messages. I know > about things like > >dmesg|less > > and > >less /var/log/syslog > > but they don't cover everything. For example, /etc/init.d/console-setup > issues a

Re: Tracking boot messages

2011-01-17 Thread Pascal Hambourg
Hello, Stephen Powell a écrit : > Hello, list. I am trying to find a way to track boot messages. I know about > things like > >dmesg|less > > and > >less /var/log/syslog > > but they don't cover everything. For example, /etc/init.d/console-setup > issues a message during boot that g

Re: Tracking boot messages

2011-01-17 Thread frank thyes
On Mon, 2011-01-17 at 10:53 -0500, Stephen Powell wrote: > Hello, list. I am trying to find a way to track boot messages. I know about > things like > >dmesg|less > > and > >less /var/log/syslog > > but they don't cover everything. For example, /etc/init.d/console-setup > issues a me