Very Computer

Hello:

Well, I've read the FAQs for netatalk, printing, etc. etc. etc.
and have my appletalk laserwriter working just fine using /dev/null
as the lp printcap entry.  BUT, when I mknod /var/spool/laser/null
with what seems like all the correct directory permissions and
ownerships (similar to /dev/null) all I get from lpq is

        "waiting for lp to become ready (offline?)".

I've tried various combinations of major/minor arguments to mknod
with no difference.

What does it take to bring a null device to life????

I've spent so much time beating my head against the wall I'm ready
to give up and ask for help.

If you could email me I'd be glad to post the correct answer(s) when
all is well in null-ville.

This is for iNTEL based Linux, Redhat 4.1 updated to 4.2 and still
this persists.  Seems like it's an omission on my part more than a
kernel/system bug.

Thanks!

Neal Sedell

--

Quote:> Well, I've read the FAQs for netatalk, printing, etc. etc. etc.
> and have my appletalk laserwriter working just fine using /dev/null
> as the lp printcap entry.  BUT, when I mknod /var/spool/laser/null
> with what seems like all the correct directory permissions and
> ownerships (similar to /dev/null) all I get from lpq is

mknod /var/spool/laser/null c 1 3
chmod 666 /var/spool/laser/null

Correct?

Aa.