you can mount the root device to another linux system.
take out the root hard disk from that system and
connect it to an existing system then mount it. you
can check the logs from there. logs where the system
is stopping or maybe clues why it is rebooting. i use
this method when a system is compromised, and needed
to check logs. if im in your situation too, that is
what i will do. but of course, thats me.
if you dont have another linux system, you can try to
boot 'rescue' from the MDK8 CD1. i havent tried to
mount a system from it but based on documents, it can.
anyway, the dmesg records what happened during the
last boot up as well as other messages while the
system is running. and yes, it is overwritten during
bootup. the messages file have those logs you can find
in dmesg. messages file is not overwritten after boot
up. it is only overwritten depending on the scheduled
rotation of your logs.
the boot.log is more into the services that were
started up, modules loaded etc while booting up. and
the kernel logs are more specific to the kernel
activities which i think will me of more interest to
you in your situation.
just trying to help ...
--- Bill Beauchemin <[EMAIL PROTECTED]> wrote:
> How do I mount ther root device to another system
> and what will this do for
> me? I looked at all the logs and the one I want is
> dmesg. The only problem is
> that as soon as it reboots it overwrites it with new
> data from the good
> bootup.
>
>
> On Thursday 26 July 2001 00:18, you wrote:
> > if you can mount the root device to another
> system,
> > you can look at several logs in /var/log
> >
> > check for boot.log, dmesg, and /var/log/kernel/*
> >
>
>
>
__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
