[8251] in athena10
Re: [Debathena] #462: Run the entire cluster environment in a chroot
daemon@ATHENA.MIT.EDU (Debathena Trac)
Mon Aug 15 17:12:25 2011
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
From: "Debathena Trac" <debathena@MIT.EDU>
Cc: debathena@mit.edu
To: geofft@mit.edu, broder@mit.edu, jdreed@mit.edu
Date: Mon, 15 Aug 2011 21:12:16 -0000
Reply-To:
Message-ID: <052.9144feeb90f8ba7c5eca44040b78af54@mit.edu>
In-Reply-To: <043.9549a3700e74483532dc683e0320cbbe@mit.edu>
Content-Transfer-Encoding: 8bit
#462: Run the entire cluster environment in a chroot-------------------------+--------------------------------------------------
Reporter: geofft | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: The Distant Future
Component: -- | Keywords:
See_also: |
-------------------------+--------------------------------------------------
Comment(by geofft):
So the interesting problem here is how to take updates without doing so in
a chroot.
I can think of two general classes of solution here:
* Run schroot inside the initrd and use that as the "real" root (which
should work very smoothly, and is generally desirable). If you're at the
login screen and decide you want to take updates, reboot yourself with a
kernel command-line parameter. If the initrd detects this parameter, don't
run schroot or start up the desktop, just boot to `athena-auto-update &&
reboot`.
* Don't start up the desktop automatically, instead boot to a screensaver
via Plymouth or somesuch. If a user wakes up the computer, then schroot
and start up the desktop from inside it, which should take about two
seconds these days. Otherwise, the screensaver periodically checks for
updates.
-- Ticket URL: <http://debathena.mit.edu/trac/ticket/462#comment:3>Debathena <http://debathena.mit.edu/>MIT Debathena Project
