>| >> So is that why the old IBM mainframes tagged every system
>| >> message with a unique identifier?
>| > Oh and everybody should have a 2000 page translation table on paper?
>| Come on. You know these "SYS3175: Das Program hat eine illegale Instruktion
>| ausgeführt und wird deshalb beendet." messages, ANY IBM programmer will be
>| able to backtrack the message by using the SYS number.
> Relatively poor example; as in Linux, that is printed by the "shell"
> (PMSHELL.EXE in this case) in user mode and is therefore subject to
Sure. OK. Take NT. "OS Loader 4.00 ... Drücken Sie JETZT die Leertaste, um
die letzte funktionierende Konfiguration ..." etc.
> translation, just as bash can choose to internationalize the equivalent
> Linux message ("Segmentation violation"). It's the stuff recorded by klogd
ACK, but why stop there? We could perhaps avoid the issue for the moment by
just adding a logo screen capability for LILO (or the kernel itself) by
default, like MS hiding the text mode interface. (I did this some time and
it worked like a charm, but as I don't boot my machine this often nowadays
it's just not worth it any more.)
>| What do you need a 2000 page translation table for then?
> Have you ever seen what an OS/2 error message during the early boot stages
> looks like? ("OS/2 !! 01425" or similar. Linux's messages are rarely so
Yes, I have. So what?
If we copy, we don't have to copy everything. We can still pick and choose.
--
_ciao, Jens_______________________________ http://www.pinguin.conetix.de
cat /dev/boiler/water | tea | sieve > /cup
mount -t hdev /dev/human/mouth01 /mouth ; cat /cup >/mouth/gulp
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/