Re: lp0 on fire

On Sat, Jun 16, 2001 at 10:41:07AM +0100, Colin Watson wrote: > Do let the FAQ maintainer know, then. According to the feedback section, > his address is Robert Kiesling <[EMAIL PROTECTED]>. I'll wait for 2.4.7 :/ -- John Lenton ([EMAIL PROTECTED]) -- Random fortune: It is through symbols that m

Re: lp0 on fire

John R Lenton <[EMAIL PROTECTED]> wrote: >On Fri, Jun 15, 2001 at 05:13:13PM +0100, Colin Watson wrote: >>In newer kernels this message reads lp1 reported invalid error status >>(on fire, eh?). > >that should read 'older newer kernels' or something. It means >2.2.x. (in 2.4.x people returne

Re: lp0 on fire

On Fri, Jun 15, 2001 at 05:13:13PM +0100, Colin Watson wrote: >In newer kernels this message reads lp1 reported invalid error status >(on fire, eh?). that should read 'older newer kernels' or something. It means 2.2.x. (in 2.4.x people returned to sanity and put it back) -- John Lenton (

Re: lp0 on fire

David Raeker-Jordan <[EMAIL PROTECTED]> wrote: >I was printing a rather large label job from a local debian machine to a >remote debian machine that has an old dot matrix printer attached to it. >After about 10 minutes of printing to the remote printer, the message "lp0 >on fire" popped up on the r

Re: lp0 on fire

On Fri, 15 Jun 2001 11:51:57 EDT, David wrote: > I was printing a rather large label job from a local debian machine to a > remote debian machine that has an old dot matrix printer attached to it. > After about 10 minutes of printing to the remote printer, the message "lp0 > on fire" popped up on

Re: lp0 on fire

* David Raeker-Jordan ([EMAIL PROTECTED]) spake thusly: > I was printing a rather large label job from a local debian machine to a > remote debian machine that has an old dot matrix printer attached to it. > After about 10 minutes of printing to the remote printer, the message "lp0 > on fire" poppe