Re: boot images/logos/splashes (yet another idea)
Fri, 15 May 1998 12:57:28 -0500 (CDT)

From: "Phil's Kernel Account" <>

On Fri, 15 May 1998, Geert Uytterhoeven wrote:

#> As long as we don't use IBM's idea for AIX to show some 3-digit numbers
#> on the LEDs to indicate the progress and possible errorcodes.
#> "Hello, support ? My RS/6000 got stuck at number 204."
#> Eh? Why not, at least as an add-on?
#> I work on the IBM SP Support Line.
#> Those numbers are a *godsend* to us, though I'd like to get boot
#> messages like Linux uses as well. The combination would be wonderful.
#Yeah, our most popular number is `200'. But without the manual, it's very
#difficult to find out that the machine just wants someone to find the key and
#turn the lock.

Ours is '888'. Shalon should know this one; boot disk unavailable. Happens
every few months. We had to call IBM tech the first time because we
weren't getting ANYTHING, and were totally clueless. It's not in the
manual, either. (Our RAID5 stack's internal controller died.)

Actually, flashing '888' means "*CRASH*BANG*I'M DEAD*". ;)
It's bad to see that before it hits software....

#And now the kernel source maintenance problem: how to impose unique numbers to
#kernel messages with the least labor?

Simple! Categorize! :)

ie; Disk errors are '8xx,' video errors are '1xx,' kernel errors are
'2xx,' and so on. :)

I like the device number based scheme someon proposed.

Shalon Wood

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to