[448] in athena10
Re: Login chroot design for Athena 10
daemon@ATHENA.MIT.EDU (Quentin Smith)
Tue Aug 19 13:44:52 2008
Date: Tue, 19 Aug 2008 13:44:07 -0400 (EDT)
From: Quentin Smith <quentin@MIT.EDU>
To: Greg Hudson <ghudson@mit.edu>
cc: athena10@mit.edu
In-Reply-To: <1219167711.12433.267.camel@error-messages.mit.edu>
Message-ID: <Pine.LNX.4.64L.0808191343230.11949@vinegar-pot.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
On Tue, 19 Aug 2008, Greg Hudson wrote:
> On Tue, 2008-08-19 at 13:35 -0400, Quentin Smith wrote:
>> LVM does not support snapshots of snapshots. However, how about this
>> layout of snapshots:
>>
>> * root-master is the long-term master volume
>> * root is created on boot as a snapshot of root-master
>>
>> This would preserve the ability to return to a clean state by rebooting
>> the machine (without the lengthy verification of every package that's
>> installed), while saving most of the maintenance headache of using
>> chroots. To perform an update, we can just remount / as root-master and
>> perform a regular update, or alternately, we can perform the update in
>> place and then turn root into root-master.
>
> Can we reasonably expect to remount / without putting the system through
> horrible trauma?
I think remounting / is less likely to put the system through trauma than
performing updates inside a chroot is...
--Quentin
