[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#270311: marked as done (djtools: hpset cannot use any other device instead of /dev/lp1)

Your message dated Mon, 12 Dec 2011 21:10:53 +0100
with message-id <4EE65FCD.5090305@debian.org>
and subject line Re: hpset cannot use any other device instead of /dev/lp1
has caused the Debian Bug report #270311,
regarding djtools: hpset cannot use any other device instead of /dev/lp1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
270311: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=270311
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: djtools
Version: 1.2.5
Severity: normal

I'm using this program to control my HP Deskjet 670C. Unfortunately,
there is no commandline parameter, environment setting or whatsoever
mentioned in the docs how to use any different device than /dev/lp1. My
printer is connected to /dev/lp0.
The (very ugly) solution I came up with was to delete the device-node
lp1 and instead make it a symlink to lp0. This works, but is quite ugly.

Thanks in advance,

Floris Kruisselbrink

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8floris-20040827
Locale: LANG=C, LC_CTYPE=C

Versions of packages djtools depends on:
ii  libc6                  2.3.2.ds1-13      GNU C Library: Shared libraries an
ii  libgcc1                1:3.4.1-4sarge1   GCC support library
ii  libpaper1              1.1.14-0.4        Library for handling paper charact
ii  libstdc++5             1:3.3.4-6sarge1.2 The GNU Standard C++ Library v3

-- no debconf information

--- End Message ---
--- Begin Message --- 
Quoting from djscript.README:


Where djscript's output goes
============================

  djscript writes its output directly onto /dev/lp1 by default. To redirect
  djscript's output use option `-P<filename>' where <filename> is the name
  of the file to be printed to. Remember that any old contents of <filename>
  will be overwritten and thus lost. To make djscript write it's output to
  the standard output stream, use `-P-'.

  Using option `-P:<cmd>' pipes djscript's output into the command <cmd>.
  This is equivalent to `-P- | <cmd>'.

  Currently there are no features in djscript that allow connecting to a
  printer daemon like `lpd'. If it turns out that this is a severe drawback
  it has to be fixed. But I read about filter scripts in NEWS that several
  people use in connection with their customized printcap entries. I guess
  that it is no major problem to call djscript from somwhere there and pipe
  its output to the appropriate tools and thus to achieve the wanted.

  Examples:
        djscript file1
        djscript -Pprintfile file2
        djscript -P- file3 | cat /dev/lp1
        djscript -P:lpr file4

--- End Message ---
Reply to: