Miles Fidelman wrote:
> Ooops. I guess I wasn't as clear as I could have been.
>
> Editing /etc/default/bootlod to set
> BOOTLOGD_ENABLE=yes
>
> Works like a charm.
>
> Miles
Thanks for clarifying that for me ;-)
Regards
__
Do You Yahoo!?
Tire
Ooops. I guess I wasn't as clear as I could have been.
Editing /etc/default/bootlod to set
BOOTLOGD_ENABLE=yes
Works like a charm.
Miles
Willie Wonka wrote:
[ apologies for the long time since replying ]
Miles Fidelman wrote:
Willie Wonka wrote:
Mumia W. wrote:
AFAIK, that's not the way
Florian Kulzer wrote:
> > I'll echo the question about where to find that out other than a helpful
> > reply on this list.
>
> A manpage does not always include specific info about how things are set
> up in Debian, unfortunately. (You can file a wishlist bug asking the
> package maintainer to i
[ apologies for the long time since replying ]
Miles Fidelman wrote:
> Willie Wonka wrote:
> > Mumia W. wrote:
> >> AFAIK, that's not the way you enable boot-logging. Just edit
> >> /etc/default/bootlogd.
> >>
> >
> > It did not take affect after a warm (re)boot -- so I'll try your suggestion
-
On Sat, Jul 22, 2006 at 15:15:40 -0400, Miles Fidelman wrote:
> Willie Wonka wrote:
> >Mumia W. wrote:
> >>AFAIK, that's not the way you enable boot-logging. Just edit
> >>/etc/default/bootlogd.
> >>
> >
> >It did not take affect after a warm (re)boot -- so I'll try your
> >suggestion -
> >but why
Willie Wonka wrote:
Mumia W. wrote:
AFAIK, that's not the way you enable boot-logging. Just edit
/etc/default/bootlogd.
It did not take affect after a warm (re)boot -- so I'll try your suggestion -
but why wouldn't the man page say how to enable it? Or where should I look for
that kind of inf
Mumia W. wrote:
> AFAIK, that's not the way you enable boot-logging. Just edit
> /etc/default/bootlogd.
>
It did not take affect after a warm (re)boot -- so I'll try your suggestion -
but why wouldn't the man page say how to enable it? Or where should I look for
that kind of info instead?
I'm _
On 07/21/2006 09:31 AM, Willie Wonka wrote:
[...]
So I drop to a VT/VC (ctrl-alt-f2) and login as root;
then rerun above command '/sbin/bootlogd -lps'
and it *seems* to have taken affect -- but i guess i won't know for sure until
I reboot...well here goes ;-)
Regards
AFAIK, that's not the wa
Wulfy wrote:
> man bootlogd it's part of the sysvinit package... :)
>
> [EMAIL PROTECTED]:~$ dpkg -S bootlogd
> sysvinit: /sbin/bootlogd
> initscripts: /etc/init.d/bootlogd
> initscripts: /etc/init.d/stop-bootlogd
> initscripts: /etc/default/bootlogd
> sysvinit: /usr/share/man/man8/bootlogd.8.g
Miles Fidelman wrote:
> Wulfy wrote:
> > Miles Fidelman wrote:
> >> Gabriel Parrondo wrote:
> >>> El jue, 20-07-2006 a las 22:09 -0400, Miles Fidelman escribió:
> and it turns out that it sure looks like the messages I'm trying to
> capture are generated too early in the startup process
Gabriel Parrondo wrote:
> El jue, 20-07-2006 a las 22:09 -0400, Miles Fidelman escribió:
> > and it turns out that it sure looks like the messages I'm trying to
> > capture are generated too early in the startup process to hit the log
> > files - guess I have to connect my laptop to the serial p
I've just upgraded my kernel from bf-2.4 to 2.4.18-1-686. I'm getting a few
funny messages on bootup:
/etc/mtab: no such file or directory
modporbe: cannot locate module *
/etc/modules.conf is newer than /lib/modules/modules.dep
The relevant part of my /etc/lilo.conf:
image = /vmlinuz
On Thu, Jan 09, 2003 at 01:06:43PM -0800, Daniel L. Miller wrote:
> Thank you all for the dmesg tip.
>
> Following is a copy of my startup. Can anyone give me a tip on any
> potential problems or inefficiencies noted here - in particular the
> messages regarding my USB setup.
>
> IPX Portions Cop
On Thu, 9 Jan 2003 15:42:58 -0500
"Michael P. Soulier" <[EMAIL PROTECTED]> wrote:
| On 09/01/03 Daniel L. Miller did speaketh:
|
| > How can I log all the messages generated during boot? The stuff that
| > talks about the peripherals detected, driver loading, etc.
|
| man dmesg
|
| Mik
Thank you all for the dmesg tip.
Following is a copy of my startup. Can anyone give me a tip on any
potential problems or inefficiencies noted here - in particular the
messages regarding my USB setup.
Linux version 2.4.18-bf2.4 (root@zombie) (gcc version 2.95.4 20011002
(Debian prerelease)) #1 S
On 09/01/03 Daniel L. Miller did speaketh:
> How can I log all the messages generated during boot? The stuff that
> talks about the peripherals detected, driver loading, etc.
man dmesg
Mike
--
Michael P. Soulier <[EMAIL PROTECTED]>, GnuPG pub key: 5BC8BE08
"...the word HACK is used as
Once your system is up log in as root and execute "dmesg"
Also see if your system has a /var/log/dmesg, this file is written at
boot time but future messages are not appended.
Thus spake Daniel L. Miller ([EMAIL PROTECTED]):
> How can I log all the messages generated during boot? The stuff th
How can I log all the messages generated during boot? The stuff that
talks about the peripherals detected, driver loading, etc.
Daniel
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
18 matches
Mail list logo
