On Fri 01 Mar 2019 at 12:34:45 +, mick crane wrote:
> On 2019-03-01 12:24, Brian wrote:
> > On Fri 01 Mar 2019 at 12:21:05 +, Brian wrote:
> >
> > > On Fri 01 Mar 2019 at 12:09:16 +, mick crane wrote:
> > >
> > > > On 2019-03-01 11:49, Brian wrote:
> > > >
> > > > > > on client PC
>
On Fri 01 Mar 2019 at 12:26:23 +, mick crane wrote:
> On 2019-03-01 12:16, Brian wrote:
> > On Fri 01 Mar 2019 at 12:09:16 +, mick crane wrote:
> >
> > > On 2019-03-01 11:49, Brian wrote:
> > >
> > > > > "systemctl start lpd.service"
> > > >
> > > > Eh? You would have to explain. For a s
On 2019-03-01 12:24, Brian wrote:
On Fri 01 Mar 2019 at 12:21:05 +, Brian wrote:
On Fri 01 Mar 2019 at 12:09:16 +, mick crane wrote:
> On 2019-03-01 11:49, Brian wrote:
>
> > > on client PC
> > > $ lpstat -t
> > > scheduler is running
> > > system default destination: HP_LaserJet_4000_
On 2019-03-01 12:16, Brian wrote:
On Fri 01 Mar 2019 at 12:09:16 +, mick crane wrote:
On 2019-03-01 11:49, Brian wrote:
> > "systemctl start lpd.service"
>
> Eh? You would have to explain. For a start, the service file does not
> seem to exist in Debian.
clutching at straws
Which packag
On Fri 01 Mar 2019 at 12:21:05 +, Brian wrote:
> On Fri 01 Mar 2019 at 12:09:16 +, mick crane wrote:
>
> > On 2019-03-01 11:49, Brian wrote:
> >
> > > > on client PC
> > > > $ lpstat -t
> > > > scheduler is running
> > > > system default destination: HP_LaserJet_4000_Series
> > > > devic
On Fri 01 Mar 2019 at 12:09:16 +, mick crane wrote:
> On 2019-03-01 11:49, Brian wrote:
>
> > > on client PC
> > > $ lpstat -t
> > > scheduler is running
> > > system default destination: HP_LaserJet_4000_Series
> > > device for HP_LaserJet_4000_Series: socket://10.0.0.108
> >
> > This is no
On Fri 01 Mar 2019 at 12:09:16 +, mick crane wrote:
> On 2019-03-01 11:49, Brian wrote:
>
> > > "systemctl start lpd.service"
> >
> > Eh? You would have to explain. For a start, the service file does not
> > seem to exist in Debian.
>
> clutching at straws
Which package is lpd.service in?
On 2019-03-01 11:49, Brian wrote:
on client PC
$ lpstat -t
scheduler is running
system default destination: HP_LaserJet_4000_Series
device for HP_LaserJet_4000_Series: socket://10.0.0.108
This is not a connection to the server. socket://... indicates a direct
connection to the printer.
with
On Fri 01 Mar 2019 at 11:55:20 +, Brian wrote:
> On Fri 01 Mar 2019 at 12:43:58 +0100, Nicolas George wrote:
>
> > Brian (12019-03-01):
> > > If installing the cups-bsd package was the solution, why didn't the use
> > > of lpr give a file not found error?
> >
> > Probably because of this, th
Brian (12019-03-01):
> I doubt it. This simply says that cups cannot exist on the same system
> if either the lpr or lprng *packages* is installed.
And therefore, if one of these packages was previously installed, as
mick just told us, and provided the lpr command, it was removed to make
way for t
On 2019-03-01 11:42, Brian wrote:
On Fri 01 Mar 2019 at 11:35:18 +, mick crane wrote:
On 2019-03-01 11:15, Curt wrote:
> I believe the lpr that works with cups is the one provided by cups-bsd.
>
success !
ta ever so much
If installing the cups-bsd package was the solution, why didn't the
On Fri 01 Mar 2019 at 12:43:58 +0100, Nicolas George wrote:
> Brian (12019-03-01):
> > If installing the cups-bsd package was the solution, why didn't the use
> > of lpr give a file not found error?
>
> Probably because of this, that caused the removal of packages:
>
> Conflicts: lpr, lprng
I d
On Fri 01 Mar 2019 at 09:58:08 +, mick crane wrote:
> On 2019-02-28 18:59, mick crane wrote:
> > hello
> > is buster
> > I can print from command line with
> > "lp filename"
> > but not with "lpr filename"
> > when printing from terminal the font is a bit big and uses too much
> > paper.
> > a
Brian (12019-03-01):
> If installing the cups-bsd package was the solution, why didn't the use
> of lpr give a file not found error?
Probably because of this, that caused the removal of packages:
Conflicts: lpr, lprng
Regards,
--
Nicolas George
signature.asc
Description: PGP signature
On Fri 01 Mar 2019 at 11:35:18 +, mick crane wrote:
> On 2019-03-01 11:15, Curt wrote:
>
> > I believe the lpr that works with cups is the one provided by cups-bsd.
> >
> success !
> ta ever so much
If installing the cups-bsd package was the solution, why didn't the use
of lpr give a file n
On 2019-03-01 11:15, Curt wrote:
I believe the lpr that works with cups is the one provided by cups-bsd.
success !
ta ever so much
--
Key ID4BFEBB31
On 2019-03-01, mick crane wrote:
> On 2019-02-28 18:59, mick crane wrote:
>> hello
>> is buster
>> I can print from command line with
>> "lp filename"
>> but not with "lpr filename"
>> when printing from terminal the font is a bit big and uses too much
>> paper.
>> apparently "enscript -FCourier1
mick crane (12019-02-28):
> Can try to get lpr to work
Leaving something that does not work is rarely a good idea.
You neglected to give some very important information, in particular
which packages provides the various commands you are trying to use and
their respective versions.
Regards,
--
$ enscript -d filename
lpr: test: unknown printer
sorry that is a typing error, the actual file was called "test".
tried the printer name after "-d" but put this here because shows
enscript is using lpr
--
Key ID4BFEBB31
On 2019-02-28 18:59, mick crane wrote:
hello
is buster
I can print from command line with
"lp filename"
but not with "lpr filename"
when printing from terminal the font is a bit big and uses too much
paper.
apparently "enscript -FCourier10 filename" for example is supposed to
work but that send
hello
is buster
I can print from command line with
"lp filename"
but not with "lpr filename"
when printing from terminal the font is a bit big and uses too much
paper.
apparently "enscript -FCourier10 filename" for example is supposed to
work but that sends it to lpr which doesn't.
Can try to ge
21 matches
Mail list logo
