For the record, I have had RH boxes find lp on different /dev 's depending
on kernel / distro (on the same box). lpd also seems to make a
difference. If it is working on /dev/lp1 and I upgrade (kernel or lpd) and
it stops, I switch it to /dev/lp0 and the problem corrects. I cannot
figure out why this keeps changing. It does stay stable until the next
time I upgrade one or the other.
My understanding is that /dev/printer should be a sym link to /dev/lpx. I
would do
ls -la | grep /dev/printer
and see what it returns. If it returns
/dev/printer blah blah > /dev/lp1
or something to that effect, make a new link to /dev/lp0. Or, do what I
do, skip /dev/printer and go straight for the device in your printcap.
fixing a 0 or 1 in printcap is easier (IMHO) than resetting the sym link
in /dev.
On Thu, 23 Dec 1999, Jules Bean wrote:
> On Tue, 21 Dec 1999, Michael J. Flynn wrote:
> > I recently updated my RH 6.0 server to RH 6.1 and the printing was
> > broken. I look around for some answers on various FAQs about netatalk on
> > the net and found a solution. Since I was able to get the printing to
> > work again, I tend to think this is more of a lpr problem. Does anyone
> > have any ideas why I had to make this change? Are there settings I can
> > change in lpr so I can have the papd entry go back to it's original
> > entry? Thanks in advance for any tips.
>
> AFAICT, the problem seems to be that lpd no longer listens on
> /dev/printer, which is where papd sends its control messages. I am unable
> to work out why or when this change happened :-)
Sean...
Everything you know is wrong,
Just forget the words and sing along. --Weird Al
===========================================================================
RIMBoy.com... Coming soon to a browser near you.
===========================================================================
Through the server, over the router, off the firewall... Nothing but 'Net!
