on Fri, Dec 14, 2001 at 04:50:04PM -0500, David Teague ([EMAIL PROTECTED])
wrote:
> On Wed, 12 Dec 2001, Karsten M. Self wrote:
>
> > on Tue, Dec 11, 2001 at 11:59:37PM -0500, Stan Brown ([EMAIL PROTECTED])
> > wrote:
> > > I need to be able to capture the start up messages issued when my
> > >
Karsten
How do I 'boot single'?
I managed to miss Brenda's message. Would you send me a string to
use to search the archives (once they are posted on debian.org)
Finally what FM do I R to find out some of these things. I like
to just read the manuals -- when I have time. It's final exam time,
a
DvB <[EMAIL PROTECTED]> writes:
> "Stan Brown" <[EMAIL PROTECTED]> writes:
>
> > I need to be able to capture the start up messages issued when my woody
> > system boots.
> >
> > dmesg only gives me up to the point control is transfered from the kernel,
> > and I'm seeing erros after that, that
on Tue, Dec 11, 2001 at 11:59:37PM -0500, Stan Brown ([EMAIL PROTECTED]) wrote:
> I need to be able to capture the start up messages issued when my woody
> system boots.
>
> dmesg only gives me up to the point control is transfered from the kernel,
> and I'm seeing erros after that, that flash by
I have always thought that Debian should take a trick from Redhat
i.e. the initscripts are executed in such a way that the standard
output and error go to something called boot.log -- e2fsck seems to
have been an exception, but it would really be nice if Debian did this
as well.
On 12 Dec 2001, Mi
sorry if this is out-of-sequence, and i can't verify it since my
systems have been up too long, but try adding this
local7.* /var/log/boot.log
to you syslog.conf, then kill -HUP the process and see if it works.
--
martin; (greetings from the heart of the
On Tue, 2001-12-11 at 23:53, Marc Wilson wrote:
> On Wed, Dec 12, 2001 at 12:35:46AM -0500, Jeremy Gaddis wrote:
> > > How can I do this?
> >
> > $ less /var/log/dmesg
>
> Same problem, only contains kernel messages. Those produced during init
> ain't there. :(
Check your /var/log/syslog
--mik
On Wed, Dec 12, 2001 at 12:35:46AM -0500, Jeremy Gaddis wrote:
> > How can I do this?
>
> $ less /var/log/dmesg
Same problem, only contains kernel messages. Those produced during init
ain't there. :(
--
Marc Wilson
[EMAIL PROTECTED]
[EMAIL PROTECTED]
pgpMRKHknLE3s.pgp
Description: PGP signa
On Tue, 11 Dec 2001, Stan Brown wrote:
> I need to be able to capture the start up messages issued when my woody
> system boots.
>
> dmesg only gives me up to the point control is transfered from the kernel,
> and I'm seeing erros after that, that flash by to quickly to read.
>
> How can I do this
Quoting Stan Brown <[EMAIL PROTECTED]>:
> I need to be able to capture the start up messages issued when my woody
> system boots.
>
> dmesg only gives me up to the point control is transfered from the
> kernel,
> and I'm seeing erros after that, that flash by to quickly to read.
I am not sure
"Stan Brown" <[EMAIL PROTECTED]> writes:
> I need to be able to capture the start up messages issued when my woody
> system boots.
>
> dmesg only gives me up to the point control is transfered from the kernel,
> and I'm seeing erros after that, that flash by to quickly to read.
>
> How can I do
I need to be able to capture the start up messages issued when my woody
system boots.
dmesg only gives me up to the point control is transfered from the kernel,
and I'm seeing erros after that, that flash by to quickly to read.
How can I do this?
--
Stan Brown [EMAIL PROTECTED]
12 matches
Mail list logo
