Your message dated Mon, 27 Jan 2025 02:10:55 +0100
with message-id <[email protected]>
and subject line Re: Bug#305951: Can't be fixed...
has caused the Debian Bug report #305951,
regarding lpr: fails to start on read-only root
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 [email protected]
immediately.)
--
305951: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=305951
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: lpr
Version: 1:2003.09.23-7S
Severity: normal
lpd fails to start on a read-only root filesystem system because
it cannot create /dev/printer socket. There are two possible ways
to fix this bug:
1. To change the default location of the control socket, for example,
to /var/run/printer, which is used in NetBSD.
2. Add a new option for lpd that will allow to specify different
location for this socket. In this case, anyone who uses a read-only
filesystem will able to specify different location for this socket
and make /dev/printer as a symbol link to this location.
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.11.6
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Versions of packages lpr depends on:
ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an
ii netbase 4.21 Basic TCP/IP networking system
-- no debconf information
--- End Message ---
--- Begin Message ---
On Sun, May 01, 2005 at 05:55:05PM -0500, Adam M wrote:
> tag 305951 + wontfix
Read-only /dev is completely unsupported and unnecessary nowadays,
don't need to keep track of this on an individual-package level.
--- End Message ---
