public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Thierry Carrez <koon@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] GNAP 1.7 Release (Gentoo Network APpliance)
Date: Tue, 31 May 2005 20:57:15 +0200	[thread overview]
Message-ID: <429CB38B.8080709@gentoo.org> (raw)
In-Reply-To: <1117557486.14290.263.camel@cgianelloni.nuvox.net>

Chris Gianelloni wrote:

>>R/W overlay
>>It is now possible to specify the name of a partition from which to
>>overlay files at boot-time, allowing to write configuration changes back
>>to a floppy or a specific CF partition for example.
> 
> Just curious, but what did you do to do this?  I'm going to guess
> there's some boot-time option to mount a unionfs, no?  Is this something
> we can extend to genkernel to allow us to have configurable LiveCD
> releases, or is it something that is GNAP-specific?

Oh no. I just found out about unionfs very recently, thanks to solar.

The current implementation is completely manual (and asynchronous) : the
contents of the partition is overlaid over the live filesystem at boot,
and you can remount the partition later on to save modified files. The
idea is to backup some /etc and /var things that you want to keep over a
reboot.

What is GNAP-specific, though, is the idea to add a tarball to a LiveCD
and have an init script overlay files over the filesystem at boot. This
allows user-level customization of the LiveCD configuration files in
seconds. The "R/W overlay" feature is just there to avoid burning a new
LiveCD whenever you change a conf file.

-- 
Koon
-- 
gentoo-dev@gentoo.org mailing list


      reply	other threads:[~2005-05-31 18:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-31 15:04 [gentoo-dev] GNAP 1.7 Release (Gentoo Network APpliance) Thierry Carrez
2005-05-31 16:38 ` Chris Gianelloni
2005-05-31 18:57   ` Thierry Carrez [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=429CB38B.8080709@gentoo.org \
    --to=koon@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox