On Fri, 2003-02-07 at 05:58, D. Wollmann wrote:
> On Thursday 06 February 2003 21:49, Collins Richey wrote:
> > On Thu, 06 Feb 2003 23:17:58 +0000
> >
> > Andy Arbon <[EMAIL PROTECTED]> wrote:
> > > -----BEGIN PGP SIGNED MESSAGE-----
> > > Hash: SHA1
> > >
> > > [EMAIL PROTECTED] wrote:
> > > |>(sidenote: Is the output produced on boot captured anywhere? I think
> > > |>Redhat gives you a /var/log/boot.log.. does Gentoo have an
> > > |
> > > |equivalent?)
> > > |         dmesg
> > >
> > > Thanks for the suggestion, but that's not quite what I was after...
> > > That~ seems to be messages from the kernel during bootup, whereas I
> > > was after the output from the entire boot process - basically
> > > everything you see go past onscreen as the system starts up.
> >
> > I, too, would love to see this feature.  For example, my ALSA sound card
> > module produces error messages when loading, but nothing is captured in
> > DMESG.  The sound card works just fine in spite of the error messages,
> > so I haven't pursued the matter.  It would be nice if all the boot
> > scripts had a debugging option that would append what goes to the
> > console to a file.
> 
> 
> # echo '/bin/dmesg -s 65536 > /var/log/dmesg' >> /etc/conf.d/local.start
> 


ah for heavens sake, not the kernellog the initlog!

Sorry, but this is a feature I've been missing to. =)

Can you in bash script redirect output to two files? i.e. stdout to
stdout AND boot.log, stderr to boot.log? And would this caputre the
output of scriptes executed from this script?

Hmm I will do some testing, I will post a patch later.


/John

--
[EMAIL PROTECTED] mailing list

Reply via email to