[6462] in Release_7.7_team
Re: Login chroots
daemon@ATHENA.MIT.EDU (Anders Kaseorg)
Fri Oct 9 15:25:21 2009
Date: Fri, 9 Oct 2009 15:25:13 -0400 (EDT)
From: Anders Kaseorg <andersk@MIT.EDU>
To: Geoffrey Thomas <geofft@mit.edu>
cc: ghudson@mit.edu, release-team@mit.edu
In-Reply-To: <alpine.DEB.1.10.0910091511550.13456@dr-wily.mit.edu>
Message-ID: <alpine.DEB.2.00.0910091517180.8245@dr-wily.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=UTF-8
X-Spam-Flag: NO
X-Spam-Score: 0.00
Content-Transfer-Encoding: 8bit
On Fri, 9 Oct 2009, Geoffrey Thomas wrote:
> Isn't this what policy-rc.d is for?
No. (And I’m sure we’ve had this conversation before, but:) It is a
supported operation to use policy-rc.d within the Debian installer to
install a non-running system. It may be useful for certain operations
within chroots that run an empty or carefully restricted set of daemons.
It is neither supported nor useful as a way to arbitrarily cancel or delay
daemon restarting while upgrading a full running system.
Consider a udev upgrade, for example, and you’ll quickly realize that
you’re wishing you weren’t.
Anders
