Re: 2.4.19: drivers/usb/printer.c usblpX on fire

From: Bill Davidsen (davidsen@tmr.com)
Date: Mon Aug 12 2002 - 21:53:25 EST

Next message: Bill Davidsen: "Re: 2.4.19 and 2.4.20-pre1 don't boot"
Previous message: Andrew Morton: "Re: [patch 1/21] random fixes"
In reply to: Pete de Zwart: "Re: 2.4.19: drivers/usb/printer.c usblpX on fire"
Next in thread: Alan Cox: "Re: 2.4.19: drivers/usb/printer.c usblpX on fire"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Sat, 10 Aug 2002, Pete de Zwart wrote:

> Around about 1010h 09/08/2002, Samuel Flory emitted the following wisdom:
> > The printer on fire message is the traditional Un*x error message for
> > unknown error on a printer.
>
> What I don't understand is why the misleading message is sent
> instead of the printer driver stating that it has received an unknown printer
> error code and printing the code number.

See the paragraph you quoted.

-- bill davidsen <davidsen@tmr.com> CTO, TMR Associates, Inc Doing interesting things with little computers since 1979.

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Next message: Bill Davidsen: "Re: 2.4.19 and 2.4.20-pre1 don't boot"
Previous message: Andrew Morton: "Re: [patch 1/21] random fixes"
In reply to: Pete de Zwart: "Re: 2.4.19: drivers/usb/printer.c usblpX on fire"
Next in thread: Alan Cox: "Re: 2.4.19: drivers/usb/printer.c usblpX on fire"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Thu Aug 15 2002 - 22:00:30 EST