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
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
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
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
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
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
6 matches
Mail list logo
