Hi all,

I'm running Slackware 9, and I'm trying to get my HP Laserjet 5M
working either via network or parallel.

I generally run Fluxbox, but I went into KDE and ran the GUI Printer
config to setup the printer via network. All went through fine, but
no test page.

So... back in Fluxbox, I removed /etc/printcap and removed the CUPS
file for the printer (in /etc/cups/ppd). Now I ran apsfilter and went
through the setup process for Parallel (/dev/lp0). Test page printed
great, but I'm getting:

Printer 'lp_comproom@localhost' - cannot open connection - No such
file or directory
Make sure the remote host supports the LPD protocol

I was getting the same thing with CUPS when configured to work via
network. Printer does work, and in Red Hat 9 all was dandy... but now
that I'm in Slackware, won't go.

Here's /etc/printcap:

lp_comproom|lj5mono;r=600x600;q=medium;c=gray;p=le tter;m=auto:\
:lp=/dev/lp0:\
:if=/etc/apsfilter/basedir/bin/apsfilter:\
:sd=/var/spool/lpd/lp_comproom:\
:lf=/var/spool/lpd/lp_comproom/log:\
:af=/var/spool/lpd/lp_comproom/acct:\
:mx#0:\
:sh:

lsmod does have 'lp' running:
lp 6752 0 (autoclean)

And /proc/devices has '6 lp' listed.

After reading other folks posts, I verified that /usr/bin/lpr is
pointing to lpr-lprng instead of cups:
lrwxrwxrwx 1 root root 9 Nov 24 11:36 lpr ->
lpr-lprng*

So, what do I try next?
I tried lpc reread and everything.

Thanks for any advice...

Alex.

On Thu, 08 Jan 2004 13:32:07 -0800, Alex wrote:

> Hi all,
>
> I'm running Slackware 9, and I'm trying to get my HP Laserjet 5M
> working either via network or parallel.
>
> I generally run Fluxbox, but I went into KDE and ran the GUI Printer
> config to setup the printer via network. All went through fine, but
> no test page.

Don't trust gui's, when you don't have to :-)

>
> So... back in Fluxbox, I removed /etc/printcap and removed the CUPS
> file for the printer (in /etc/cups/ppd). Now I ran apsfilter and went
> through the setup process for Parallel (/dev/lp0). Test page printed
> great, but I'm getting:
>
> Printer 'lp_comproom@localhost' - cannot open connection - No such
> file or directory
> Make sure the remote host supports the LPD protocol
>
> I was getting the same thing with CUPS when configured to work via
> network. Printer does work, and in Red Hat 9 all was dandy... but now
> that I'm in Slackware, won't go.
>
> Here's /etc/printcap:
>
> lp_comproom|lj5mono;r=600x600;q=medium;c=gray;p=le tter;m=auto:\
> :lp=/dev/lp0:\
> :if=/etc/apsfilter/basedir/bin/apsfilter:\
> :sd=/var/spool/lpd/lp_comproom:\
> :lf=/var/spool/lpd/lp_comproom/log:\
> :af=/var/spool/lpd/lp_comproom/acct:\
> :mx#0:\
> :sh:

Nothing too unusual there....

>
> lsmod does have 'lp' running:
> lp 6752 0 (autoclean)
>
> And /proc/devices has '6 lp' listed.
>
> After reading other folks posts, I verified that /usr/bin/lpr is
> pointing to lpr-lprng instead of cups:
> lrwxrwxrwx 1 root root 9 Nov 24 11:36 lpr ->
> lpr-lprng*
>
> So, what do I try next?
> I tried lpc reread and everything.
>
> Thanks for any advice...
>

So jobs print, but then you get the error ?
What is the output from :
$ lpc status
and
$ lpstat


--
- Matt -

alex@totallynerd.com (Alex) writes:
>
> After reading other folks posts, I verified that /usr/bin/lpr is
> pointing to lpr-lprng instead of cups:
> lrwxrwxrwx 1 root root 9 Nov 24 11:36 lpr ->
> lpr-lprng*
>
> So, what do I try next?
> I tried lpc reread and everything.

But lpc is also a CUPS program, isn't it? In addition to switching all
the various /usr/bin/lp*'s from CUPS to LPRng, you also have to do
likewise for /usr/sbin/lpc. In general, you don't want to mix CUPS and
LPRng. If switching from one to the other, I think I would just
reinstall the whole package and let it clobber whatever it needs to.
You could use the init scripts to start and stop lpd. So I think
something like

$ /etc/rc.d/rc.cups stop
$ chmod -x /etc/rc.d/rc.cups
$ installpkg lprng-3.8.22-i486-1.tgz # or whatever version you like
$ chmod +x /etc/rc.d/rc.lprng
$ /etc/rc.d/rc.lprng start

should switch you pretty thoroughly from CUPS to LPRng.

I hope this helps,

Tim

Alex wrote:
>
> So, what do I try next?
> I tried lpc reread and everything.
>
> Thanks for any advice...
>
> Alex.

You may -- may -- need to remove both packages (CUPS and LPRng) then
reinstall whichever one you want.

However, try this first. Here are two scripts that will set things
appropriately for either LPRng or CUPS (pick one, execute it logged in
as root):

First, to set up CUPS:

#!/bin/ksh
cd /usr/bin
rm lp lp-lprng lpq lpr lprm lpstat
ln -s lpstat-cups lpstat
ln -s lprm-cups lprm
ln -s lpr-cups lpr
ln -s lpq-cups lpq
ln -s lp-cups lp

Second, to set up LPRng:

#!/bin/ksh
cd /usr/bin
rm lp lp-lprng lpq lpr lprm lpstat
ln -s lpstat-lprng lpstat
ln -s lprm-lprng lprm
ln -s lpr-lprng lpr
ln -s lpq-lprng lpq
ln -s lpr lp-lprng
ln -s lp-lprng lp

Matt Payton wrote:

> Don't trust gui's, when you don't have to :-)

oh bollocks, Mandrake's gui CUPS configuration for printers both local
and network during install is a flawless piece of work. It gives me
choice and control, which is what I expect of Slack actually.

beldar <beldar@meepzor.com> says...
>
>Matt Payton wrote:
>
>> Don't trust gui's, when you don't have to :-)
>
>oh bollocks, Mandrake's gui CUPS configuration for printers both local
>and network during install is a flawless piece of work. It gives me
>choice and control, which is what I expect of Slack actually.

Although there is a perception that GUI-based configuration programs
are inferior, they don't have to be. It's just that making a
GIU-based configuration program that doesn't suck is harder than
making a console-based configuration program that doesn't suck,
and making a console-based configuration program that doesn't
suck is harder than making a textfile-based configuration program
that doesn't suck. A good human interface designer (a skill set
that s very rare among good coders) can make an excellent configuration
program using any of the above techniques.



--
Guy Macon, Electronics Engineer & Project Manager for hire.
Remember Doc Brown from the _Back to the Future_ movies? Do you
have an "impossible" engineering project that only someone like
Doc Brown can solve? My resume is at http://www.guymacon.com/

On Fri, 09 Jan 2004 02:26:48 +0000, beldar wrote:

> Matt Payton wrote:
>
>> Don't trust gui's, when you don't have to :-)
>
> oh bollocks, Mandrake's gui CUPS configuration for printers both local
> and network during install is a flawless piece of work. It gives me
> choice and control, which is what I expect of Slack actually.

Hmm...The OP is using Slack, not Mandrake. I was replying to the request
for help with LPRng, not CUPS. What exactly does your reply have to do
with any of that ? Do you have any advice for the OP, or do you offer any
other help ? What's that ??? Don't know where he should click ? Oh
well, guess it must be slack's fault, not the wiz-bang gui that did who
knows what to the config files.

I *never* said don't use a gui, or gui's can't get the job done. I simply
said, don't trust them, which in this case seems to be good advice...Even
though it was half joking, which should have been obvious.

Anyway, rather than start some useless flame war, I'll just gracefully
ignore you, rather than waste any more of my time, or of anyone else's
who's actually interested in helping someone.

--
- Matt -

In alt.os.linux.slackware Guy Macon <http://www.guymacon.com> wrote:

> Although there is a perception that GUI-based configuration
> programs are inferior, they don't have to be.

The perception is that gui based programs are better. That
perception is fueled by the fact that they usually are.

> It's just that making a GIU-based configuration program that
> doesn't suck is harder than making a console-based configuration
> program that doesn't suck, and making a console-based
> configuration program that doesn't suck is harder than making a
> textfile-based configuration program that doesn't suck.

As if you would know anything about it.

> A good human interface designer (a skill set that s very rare
> among good coders) can make an excellent configuration program
> using any of the above techniques.

Nonsense. The quality of code, the output of which you can see is
a reflection of the quality of code, the output of which you cannot
see. A sloppy programmer is a sloppy programmer. Linux,
unfortunately, has more than its fair share of moronic coders. The
popularity of trash "languages" such as perl and bash testifies to
the truth of this.

cordially, as always,

rm

In alt.os.linux.slackware Matt Payton <mattpayton@hotmail.com> wrote:

> Hmm...The OP is using Slack, not Mandrake. I was replying to the
> request for help with LPRng, not CUPS. What exactly does your
> reply have to do with any of that ? Do you have any advice for
> the OP, or do you offer any other help ? What's that ??? Don't
> know where he should click ? Oh well, guess it must be slack's
> fault, not the wiz-bang gui that did who knows what to the config
> files.

Actually the user knows what was done to the config files by the
gui. The config files were made to work.

> I *never* said don't use a gui, or gui's can't get the job done.
> I simply said, don't trust them, which in this case seems to be
> good advice...Even though it was half joking, which should have
> been obvious.

Half joking? The type of user interface does not in any way lead
one to any reasonable conclusions about the quality of algorithms
used in the program.

> Anyway, rather than start some useless flame war, I'll just
> gracefully ignore you, rather than waste any more of my time, or
> of anyone else's who's actually interested in helping someone.

While you would characterize your contribution to this thread as
the start of a "useless flamewar," more responsible and
knowledgeable users would characterize your contribution as
misinformation.

Please stop posting.

cordially, as always,

rm

On Fri, 09 Jan 2004 07:43:07 GMT, <rlm@ktx.justlinux.ca> <rlm@ktx.justlinux.ca> wrote:
>
>
> popularity of trash "languages" such as perl and bash testifies to
> the truth of this.
>
> cordially, as always,
>
> rm

Bash, a high-level language of immense practical use is not a "trash language"
and should never be mentioned in the same sentence as Perl, which IS a
"trash language".

I suppose you want everyone to write simple programs in C and then compile
them instead of just whipping out a file in bash and being done with it.

And no more commandline scripts, because we'll all have to write anything
but simple commands and options in C and compile them before running....

Hmmmmm....The creator's and maintainers of every Linux Distro in existence
obviously disagree with you, (try even booting one of them without the
bash scripts)

My good man, you are now on my "be very careful about this fellow's advice"
list.

That's a score of 13 in my newsreader's menu.

AC