Re: printk, klogd
Jon Tombs (jon@bart.us.es)
Thu, 29 Jun 1995 13:27:51 +0200 (MET DST)
Tor Arntsen said:
>
> >> The problem with all these issues is that when the kernel is pooping
> >> out from underneath you there is probably no REALLY good place to
> >> dump output.
> >
> >Stop the interrupts and write directly to video memory, all printer
> >ports, all serial ports, and the first sector in the floppy drive.
> >You can then send the oops message (not all the numbers) out the PC
> >speaker via morse code. If you can return to real mode or CRC check
> >the disk drivers, write to the diagnostic cylinder of the hard drive.
>
> I don't need the rest but I like the morse code idea! :-)
But change the readme to include a morse code refresh course, or we will get
even more confused users in this list...
General unix pratice is to dump output to the swap device, on startup, before
swapon you check if there is a crash dump, and if so copy it somewhere safe.
Jon.