From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: Unionfs (was: Re: [gentoo-catalyst] Keeping a test environment using catalyst)
Date: Wed, 25 May 2005 14:47:49 -0400 [thread overview]
Message-ID: <1117046870.14290.181.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <vpdr8y23ry2f.fsf@lemming.engeast.baynetworks.com>
[-- Attachment #1: Type: text/plain, Size: 2579 bytes --]
On Wed, 2005-05-25 at 13:54 -0400, Paul Smith wrote:
> %% Chris Gianelloni <wolf31o2@gentoo.org> writes:
>
> cg> I'm just curious why this needs to be done within the initrd, at
> cg> all. I guess it could be, but I could also see it working outside
> cg> the initrd.
>
> If you do it after initrd, you'll have to be very, very careful.
> "Outside" the initrd you've invoked the real init, and it's starting to
> bring up the system. If you haven't already set up the unionfs before
> that, you better be darn sure you do it immediately... if not you will
> have applications coming up with the wrong configs, failing because they
> can't write to /etc and/or /var, etc.
That's a good point. I was just thinking that by holding off until a
bit later, it allows us to have our full module list, rather than the
limited subset provided in the initrd.
Essentially, anything that we can use to boot a CD from, we can use as a
unionfs device. This would include IDE/SCSI/SATA/USB/Firewire devices.
> cg> Anyway, if we were to do it, we would allow for mounting a USB key
> cg> or other such device. Most likely, it would be via a
> cg> unionfs=/dev/$blah option, that would mount that device, along
> cg> with the CD, as a unionfs.
>
> Yes. I have this working right now, although it just uses a ramdisk
> today. Obviously using my current method, in order to use a keydisk or
> maybe even a file on a FAT partition which contains an ext2 partition
> and is mounted as a loop FS, you would need to add smarts to the initrd
> (linuxrc) to detect the hardware and mount those partitions.
Right. This would take more logic in the initrd.
> cg> One thing I probably would *not* do is make the entire CD a
> cg> unionfs, as I just think it would be a waste of energy and would
> cg> make troubleshooting much harder.
>
> I'm not sure what you mean by "not make the entire CD a unionfs"...? Do
> you just mean that some root directories would not link to the unionfs
> but instead would go to the cdrom? Or...?
Correct. I don't really see a point in having the entire CD be
writable. I can understand it for configuration directories and such,
but nobody really needs to write to /bin or /usr on a CD.
> cg> Things like /var, /etc, /root, and /home would definitely be cool
> cg> to not only be writable, but also survivable from a reboot.
>
> Yes, that's the ultimate goal of course.
--
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-05-25 18:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-10 18:34 [gentoo-catalyst] Keeping a test environment using catalyst Paul Smith
2005-05-10 20:06 ` Chris Gianelloni
2005-05-10 20:56 ` Paul Smith
2005-05-10 21:02 ` Robert Paskowitz
2005-05-11 0:23 ` Paul Smith
2005-05-11 0:36 ` Robert Paskowitz
2005-05-11 12:59 ` Chris Gianelloni
2005-05-11 1:13 ` [gentoo-catalyst] C++ programs Paul Smith
2005-05-11 13:01 ` Chris Gianelloni
2005-05-11 12:55 ` [gentoo-catalyst] Keeping a test environment using catalyst Chris Gianelloni
2005-05-11 16:39 ` Paul Smith
2005-05-11 17:33 ` Chris Gianelloni
2005-05-11 18:39 ` Paul Smith
2005-05-12 14:57 ` Chris Gianelloni
2005-05-12 16:39 ` Paul Smith
2005-05-12 17:41 ` Chris Gianelloni
2005-05-19 15:37 ` Unionfs (was: Re: [gentoo-catalyst] Keeping a test environment using catalyst) Paul Smith
2005-05-25 17:33 ` Chris Gianelloni
2005-05-25 17:54 ` Paul Smith
2005-05-25 18:47 ` Chris Gianelloni [this message]
2005-05-25 19:29 ` Paul Smith
2005-05-25 19:35 ` Paul Smith
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=1117046870.14290.181.camel@cgianelloni.nuvox.net \
--to=wolf31o2@gentoo.org \
--cc=gentoo-catalyst@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