Jerry McBride wrote:
Yes that would be possible. But since the OP's kernel doesn't even boot up,
it's not an option.
He was asking how to see the previous dmesg output this would do it on
future boot ups...
He was trying to update the kernel. Since it didn't boot up, he was looking for
Ian Brandt wrote:
Is it possible to get the dmesg for the boot prior to the current one?
No it isn't. dmesg shows the ring buffer contents of the running kernel.
I'm trying to remotely upgrade from the 2.4 to 2.6 kernel. I followed
the migration guide, but I got something wrong because my
On Sunday 16 October 2005 18:25, Ian Brandt wrote:
Hi,
Is it possible to get the dmesg for the boot prior to the current one?
No. Once the kernel reboots, the dmesg data is lost. Unless ofcourse you put
this in /etc/conf.d/local.start:
#!/bin/bash
# /etc/conf.d/local.start
/bin/dmesg
Jerry McBride wrote:
No. Once the kernel reboots, the dmesg data is lost. Unless ofcourse you put
this in /etc/conf.d/local.start:
#!/bin/bash
# /etc/conf.d/local.start
/bin/dmesg /var/log/dmesg
Then you will at the least have a log of the current dmesg, which could be
rotated.
Yes that
Jerry McBride wrote:
No. Once the kernel reboots, the dmesg data is lost. Unless ofcourse you put
this in /etc/conf.d/local.start:
#!/bin/bash
# /etc/conf.d/local.start
/bin/dmesg /var/log/dmesg
FYI, the bootmisc init script already does this for you, or at least it
does with the ~x86
Richard Fish wrote:
Jerry McBride wrote:
FYI, the bootmisc init script already does this for you, or at least it
does with the ~x86 baselayout. Just rc-update -a bootmisc boot if it
isn't already turned on.
Also, syslog-ng will dump the kernel log to /var/log/messages when it
starts up.
On Monday 17 October 2005 13:18, Christoph Gysin wrote:
Jerry McBride wrote:
No. Once the kernel reboots, the dmesg data is lost. Unless ofcourse you
put this in /etc/conf.d/local.start:
#!/bin/bash
# /etc/conf.d/local.start
/bin/dmesg /var/log/dmesg
Then you will at the least
On Monday 17 October 2005 14:18, Richard Fish wrote:
Jerry McBride wrote:
No. Once the kernel reboots, the dmesg data is lost. Unless ofcourse you
put this in /etc/conf.d/local.start:
#!/bin/bash
# /etc/conf.d/local.start
/bin/dmesg /var/log/dmesg
FYI, the bootmisc init script already
Jerry McBride wrote:
On Monday 17 October 2005 14:18, Richard Fish wrote:
Jerry McBride wrote:
No. Once the kernel reboots, the dmesg data is lost. Unless ofcourse you
put this in /etc/conf.d/local.start:
#!/bin/bash
# /etc/conf.d/local.start
/bin/dmesg /var/log/dmesg
FYI,
Hi,
Is it possible to get the dmesg for the boot prior to the current one?
I'm trying to remotely upgrade from the 2.4 to 2.6 kernel. I followed
the migration guide, but I got something wrong because my server
didn't come back up after reboot. Fortunately I used lilo -R to boot
to the 2.6
10 matches
Mail list logo
