Re: /run/, resolvconf and read-only root
On Mon, 5 May 2003 19:37:23 -0400, Theodore Ts'o wrote:
>> but things look
>> different to the admin of a system with a read-only boot medium.
>> Have you ever had your root filesystem mounted read-only for
> Red herring. Having a root filesystem mounted for read-only for
> maintenance is only needed when you need to check the filesystem for
Sorry, I was also thinking of workstations run from a CD-ROM
and a ramdisk, and other situations like that.
On Tue, 2003-05-06 at 01:40, Theodore Ts'o wrote:
> This assumes that all programs that touch a particular file (for
> example /etc/resolv.conf) are under your control --- that is, they are
> part of Debian. If some particular program is part of a third-party
> shell script which is distributed by an ISP, or part of some binary
> program which (example: AT&T Managed Tunnel Services), then by moving
> /etc/resolv.conf to some other directory and leaving a symlink behind,
> you may potentially be breaking these programs.
Any software that adheres to Debian policy (e.g., 11.7.4) won't
break if /etc/resolv.conf is replaced by a symlink.
Recall, too, that we are talking about an optional package here.
An admin with unfixable ill behaved software can simply remove
the optional package.
> And, no you may not call it a bug in those programs or shell scripts,
> because you don't get to dictate how software outside of Debian (but
> which a Debian user might want to use) is written.
If you are saying that no change may be made to the Debian
system that could possibly break some conceivable third party
program, no matter how ill behaved, then you are saying that
no change can be made to the Debian system, period.
Thomas Hood <email@example.com>