Re: Bug#33993: general: Should log all the boot messages

2000-08-21 Thread Miquel van Smoorenburg
In article <[EMAIL PROTECTED]>, Colin Watson <[EMAIL PROTECTED]> wrote: >Decklin Foster <[EMAIL PROTECTED]>, [EMAIL PROTECTED] wrote: >>Cesar Eduardo Barros <[EMAIL PROTECTED]> writes: >>> There are too many boot messages, and they sometimes scroll too >>> fast. It would be nice to log all the outp

Re: Bug#33993: general: Should log all the boot messages

2000-08-21 Thread Jordi Mallach
On Fri, Aug 18, 2000 at 12:28:58AM +0200, Peter Palfrader wrote: > dmesg only is for kernel messages. The entire userland (like starting > daemons etc.) is not covered by it. IIRC a few months ago someone > had a patch agains init (or something else) that would log the > entire startup. I don't kno

Bug#33993: general: Should log all the boot messages

2000-08-18 Thread Richard Kaszeta
Decklin Foster writes ("Bug#33993: general: Should log all the boot messages"): >Cesar Eduardo Barros <[EMAIL PROTECTED]> writes: > >> Package: general >> Version: N/A >> Severity: wishlist >> >> There are too many boot messages, and they somet

Re: Bug#33993: general: Should log all the boot messages

2000-08-18 Thread Paul Slootman
On Fri 18 Aug 2000, Branden Robinson wrote: > On Fri, Aug 18, 2000 at 10:20:48AM +0200, Paul Slootman wrote: > > On Thu 17 Aug 2000, Colin Watson wrote: > > > > > > (I usually recommend Ctrl-S (stop output) and Ctrl-Q (restart output).) > > > > Or shift-PageUp > > Of course, if you run a display

Re: Bug#33993: general: Should log all the boot messages

2000-08-18 Thread Branden Robinson
On Fri, Aug 18, 2000 at 10:20:48AM +0200, Paul Slootman wrote: > On Thu 17 Aug 2000, Colin Watson wrote: > > > > dmesg doesn't log the output from init.d scripts. > > > > (I usually recommend Ctrl-S (stop output) and Ctrl-Q (restart output).) > > Or shift-PageUp Of course, if you run a display

Re: Bug#33993: general: Should log all the boot messages

2000-08-18 Thread Paul Slootman
On Thu 17 Aug 2000, Colin Watson wrote: > > dmesg doesn't log the output from init.d scripts. > > (I usually recommend Ctrl-S (stop output) and Ctrl-Q (restart output).) Or shift-PageUp However, sometimes I have wished that the init.d messages were in fact logged somewhere. E.g. after a day you

Bug#33993: general: Should log all the boot messages

2000-08-17 Thread Peter Palfrader
On Thu, 17 Aug 2000, Decklin Foster wrote: > Cesar Eduardo Barros <[EMAIL PROTECTED]> writes: > > > Package: general > > Version: N/A > > Severity: wishlist > > > > There are too many boot messages, and they sometimes scroll too > > fast. It would be nice to log all the output from the boot scri

Re: Bug#33993: general: Should log all the boot messages

2000-08-17 Thread Colin Watson
Decklin Foster <[EMAIL PROTECTED]>, [EMAIL PROTECTED] wrote: >Cesar Eduardo Barros <[EMAIL PROTECTED]> writes: >> There are too many boot messages, and they sometimes scroll too >> fast. It would be nice to log all the output from the boot scripts. > >Huh? does dmesg not do what you want? dmesg do

Bug#33993: general: Should log all the boot messages

2000-08-17 Thread Decklin Foster
Cesar Eduardo Barros <[EMAIL PROTECTED]> writes: > Package: general > Version: N/A > Severity: wishlist > > There are too many boot messages, and they sometimes scroll too > fast. It would be nice to log all the output from the boot scripts. Huh? does dmesg not do what you want? -- There is no