Re: OT: Re: The worst error message in history belongs to... BIND9!
On Thu, Jul 05, 2007 at 04:46:52PM +0100, John Murphy wrote: Wasn't there, once upon a time, an error message in FreeBSD which reported 'This doesn't look like Kansas, Toto'? I remember seeing that error message somewhere, but do not remember where or if it was in FreeBSD. jerry Seem to recall it occurring when I deleted the directory I was 'in'. I may have imagined it though! -- John. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OT: Re: The worst error message in history belongs to... BIND9!
Jerry McAllister wrote: On Thu, Jul 05, 2007 at 04:46:52PM +0100, John Murphy wrote: Wasn't there, once upon a time, an error message in FreeBSD which reported 'This doesn't look like Kansas, Toto'? I remember seeing that error message somewhere, but do not remember where or if it was in FreeBSD. It's a fortune. Whether it has also ever been an error message I cannot say, but not in 5.4 unless it's well hidden. Gee, Toto, I don't think we are in Kansas anymore. find /usr/src -type f -print0 | xargs -0 egrep -l Kansas --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OT: Re: The worst error message in history belongs to... BIND9!
Alex Zbyslaw wrote: Jerry McAllister wrote: On Thu, Jul 05, 2007 at 04:46:52PM +0100, John Murphy wrote: Wasn't there, once upon a time, an error message in FreeBSD which reported 'This doesn't look like Kansas, Toto'? I remember seeing that error message somewhere, but do not remember where or if it was in FreeBSD. It's a fortune. Whether it has also ever been an error message I cannot say, but not in 5.4 unless it's well hidden. Gee, Toto, I don't think we are in Kansas anymore. find /usr/src -type f -print0 | xargs -0 egrep -l Kansas Seems it was replaced in 2000 with unable to return to working directory. http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/pkg_install/delete/perform.c.diff?r1=1.20;r2=1.21 -- John. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OT: Re: The worst error message in history belongs to... BIND9!
[EMAIL PROTECTED] wrote: Favourite worst written error message in history: Keyboard not found. Press F1 to continue. I have always loved this one!! Who made that up!? Someone at IBM. That's what the original IBM PC, PC-AT, and (presumably) PC-XT displayed if the keyboard was dead or not plugged in. It was probably a case of modular code: any problem in POST would display a message and return a fail status, and the generic code would append Press F1 to continue. and wait. Not a bad idea at all -- certainly better than blindly trying to boot the machine without giving the operator a chance to decide what to do about the problem -- but this particular combination does have a chicken- egg aspect :( ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] This still happened on my fairly recent ASUS p4s8x Pentium 4 motherboard. I think you could make almost any motherboard yield that error, even these days. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: OT: Re: The worst error message in history belongs to... BIND9!
Anything you have actually seen is fair game. Ted -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of doug Sent: Wednesday, July 04, 2007 12:19 PM To: freebsd-questions@freebsd.org Subject: Re: OT: Re: The worst error message in history belongs to... BIND9! How far do we get to go back in time? From the first online fortran compiler: ugh1 and ugh2. In fairness these were conditions that were not supposed to happen, but somehow they always do. In more recent times I always liked, invalid page fault this perhaps as late as win98. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OT: Re: The worst error message in history belongs to... BIND9!
Wasn't there, once upon a time, an error message in FreeBSD which reported 'This doesn't look like Kansas, Toto'? Seem to recall it occurring when I deleted the directory I was 'in'. I may have imagined it though! -- John. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OT: Re: The worst error message in history belongs to... BIND9!
How far do we get to go back in time? From the first online fortran compiler: ugh1 and ugh2. In fairness these were conditions that were not supposed to happen, but somehow they always do. In more recent times I always liked, invalid page fault this perhaps as late as win98. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OT: Re: The worst error message in history belongs to... BIND9!
Andrea Venturoli wrote: Robert Huff wrote: =?iso-8859-1?Q?Kyrre_Nyg=E5rd?= writes: It has to be the worst written error message in history. Not even close. I commend to you the Amiga's BSOD: Software Guru Meditation Number very long string of hex digits Well, there's always Windows' Insufficient Memory, which usually means anything but memory being full :-) Unable to delete file: not enough free space available. Fatal error: the operation completed successfully -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net [EMAIL PROTECTED] Furry Peace! - http://www.fur.com/peace/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OT: Re: The worst error message in history belongs to... BIND9!
On Wed, 4 Jul 2007, CyberLeo Kitsana wrote: Andrea Venturoli wrote: Robert Huff wrote: =?iso-8859-1?Q?Kyrre_Nyg=E5rd?= writes: It has to be the worst written error message in history. Not even close. I commend to you the Amiga's BSOD: Software Guru Meditation Number very long string of hex digits Well, there's always Windows' Insufficient Memory, which usually means anything but memory being full :-) Unable to delete file: not enough free space available. Fatal error: the operation completed successfully -- IBM: keyboard no present, press F1 to continue. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OT: Re: The worst error message in history belongs to... BIND9!
Eduardo Viruena Silva wrote: On Wed, 4 Jul 2007, CyberLeo Kitsana wrote: Andrea Venturoli wrote: Robert Huff wrote: =?iso-8859-1?Q?Kyrre_Nyg=E5rd?= writes: It has to be the worst written error message in history. Not even close. I commend to you the Amiga's BSOD: Software Guru Meditation Number very long string of hex digits Well, there's always Windows' Insufficient Memory, which usually means anything but memory being full :-) Unable to delete file: not enough free space available. Fatal error: the operation completed successfully -- IBM: keyboard no present, press F1 to continue. Perhaps this has been mentioned before from Unix, I don't know: Bad Magic Number -- Tim Daneliuk [EMAIL PROTECTED] PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OT: Re: The worst error message in history belongs to... BIND9!
On Thu, May 31, 2007 at 02:53:44PM +0200, Andrea Venturoli wrote: Robert Huff wrote: =?iso-8859-1?Q?Kyrre_Nyg=E5rd?= writes: It has to be the worst written error message in history. Not even close. I commend to you the Amiga's BSOD: Software Guru Meditation Number very long string of hex digits Well, there's always Windows' Insufficient Memory, which usually means anything but memory being full :-) To continue with the tortured construction ... Favourite worst written error message in history: Keyboard not found. Press F1 to continue. Or how about favourite most useless man page entry: The notion of errors is ill defined. Come to think of it, that last one is almost poetic, isn't it? In a Zen sort of way. Anyone recall which manpage it's from? -- George Still working on figuring what PC Load Letter means ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OT: Re: The worst error message in history belongs to... BIND9!
On 5/31/07, George [EMAIL PROTECTED] wrote: Or how about favourite most useless man page entry: The notion of errors is ill defined. Come to think of it, that last one is almost poetic, isn't it? In a Zen sort of way. Anyone recall which manpage it's from? grep says netstat(1). In the Bugs section, which seems like a good place for that information. - Bob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OT: Re: The worst error message in history belongs to... BIND9!
On 5/31/07, Bob Johnson [EMAIL PROTECTED] wrote: On 5/31/07, George [EMAIL PROTECTED] wrote: Or how about favourite most useless man page entry: The notion of errors is ill defined. Come to think of it, that last one is almost poetic, isn't it? In a Zen sort of way. Anyone recall which manpage it's from? grep says netstat(1). In the Bugs section, which seems like a good place for that information. - Bob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OT: Re: The worst error message in history belongs to... BIND9!
On Thu, 31 May 2007 06:56:51 -0700 George [EMAIL PROTECTED] wrote: Favourite worst written error message in history: Keyboard not found. Press F1 to continue. I have always loved this one!! Who made that up!? Rico ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OT: Re: The worst error message in history belongs to... BIND9!
On Thu, 31 May 2007 12:02:26 -0400 Bob Johnson [EMAIL PROTECTED] wrote: On 5/31/07, George [EMAIL PROTECTED] wrote: Or how about favourite most useless man page entry: The notion of errors is ill defined. Come to think of it, that last one is almost poetic, isn't it? In a Zen sort of way. Anyone recall which manpage it's from? grep says netstat(1). In the Bugs section, which seems like a good place for that information. - Bob Not actually one of the worst error messages, per se, but one I found most amusing the first time I saw it: Running procmail's mailstat program without any arguments yields the following: Most people don't type their own logfiles; but, what do I care? :-) -- Conrad J. Sabatier [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OT: Re: The worst error message in history belongs to... BIND9!
Favourite worst written error message in history: Keyboard not found. Press F1 to continue. I have always loved this one!! Who made that up!? Someone at IBM. That's what the original IBM PC, PC-AT, and (presumably) PC-XT displayed if the keyboard was dead or not plugged in. It was probably a case of modular code: any problem in POST would display a message and return a fail status, and the generic code would append Press F1 to continue. and wait. Not a bad idea at all -- certainly better than blindly trying to boot the machine without giving the operator a chance to decide what to do about the problem -- but this particular combination does have a chicken- egg aspect :( ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
