Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 6644 - lpd configuring does not work
lpd configuring does not work
Product: Red Hat Linux
Classification: Retired
Component: linuxconf (Show other bugs)
All Linux
high Severity medium
: ---
: ---
Assigned To: Michael K. Johnson
Depends On:
  Show dependency treegraph
Reported: 1999-11-02 08:31 EST by joachim
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-12-15 16:01:31 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description joachim 1999-11-02 08:31:49 EST
if I want to start the configuration tool for the lpd, the
following output is produced:

[root@godzilla /root]# lpdconf
Dieses Programm kann nicht umbenannt werden.
Sein urspr|nglicher Name ist linuxconf.

And in the linuxconf-program there is no appearance of any
lpd-specific stuff. I remember in redhat 6.0 one could
configure a printer at install time, in 6.1 not.
It would be very nice to re-enable this feature and fix the
bug of "lpdconf".

greez jschlosser
Comment 1 Michael K. Johnson 1999-11-18 13:18:59 EST
linuxconf does not (yet?) support our printtool functionality.
Have you tried running printtool?
Comment 2 jack 1999-11-30 11:28:59 EST
The symlink lpdconf -> linuxconf was a wish. I will remove this from the
packaging. There was also an old xconf -> linuxconf symlink. Another wish.
This one is funny because Linuxconf really started as an X configurator
back in 1994. It turned out differently and today, does not handle that
area at all.
Comment 3 Michael K. Johnson 1999-12-02 14:09:59 EST
These will both be fixed in our next errata release from Red Hat,
as well.
Comment 4 Michael K. Johnson 1999-12-15 16:01:59 EST
1.16r10-2 released

Note You need to log in before you can comment on or make changes to this bug.