From: Jason Lunz <lunz@falooley.org>
To: Josef Sipek <jsipek@fsl.cs.sunysb.edu>
Cc: unionfs@fsl.cs.sunysb.edu, linux-fsdevel@vger.kernel.org
Subject: Re: Unionfs in -mm
Date: Tue, 16 Jan 2007 18:03:28 -0500 [thread overview]
Message-ID: <20070116230327.GA3826@knob.reflex> (raw)
In-Reply-To: <20070113064804.GA24389@filer.fsl.cs.sunysb.edu>
On Sat, Jan 13, 2007 at 01:48:04AM -0500, Josef Sipek wrote:
> > The root filesystem is a union of a ro squashfs and a rw tmpfs.
> > The initramfs sets it up something like this:
> >
> > mkdir /os
> > mount -r -t squashfs /dev/ram0 /os
> >
> > mkdir /cow
> > mount -t tmpfs -o mode=0755 tmpfs /cow
> >
> > mount -w -o dirs=/cow=rw:/os=ro -t unionfs unionfs /root
>
> From the names of the mountpoint I assume you chroot, pivot_root, etc.
> Right?
yes. I'm using debian etch initramfs-tools. After the above mount
sequence, the unionfs becomes root via:
mkdir ${rootmnt}/cow ${rootmnt}/os
mount -n -o move /cow ${rootmnt}/cow
mount -n -o move /os ${rootmnt}/os
mount -n -o move /dev $rootmnt/dev
mount -n -o move /sys ${rootmnt}/sys
mount -n -o move /proc ${rootmnt}/proc
followed by using klibc's run-init, which does the pivot_root/chroot/etc
in C:
exec run-init ${rootmnt} ${init} "$@" <${rootmnt}/dev/console >${rootmnt}/dev/console
> Does the problem manifest itself when you mount proc on /root/proc?
well, it _is_ mounted there. Do you mean mounting it there without using
-o move? I'd have to modify the non-templated part of mkinitramfs to do
that but I could try it.
> Thanks for trying the code,
thanks for writing it. fyi, I've had better results with aufs - you
may want to check that out. I'll keep an eye on unionfs as well.
Jason
next prev parent reply other threads:[~2007-01-16 23:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070109004456.GA7954@filer.fsl.cs.sunysb.edu>
2007-01-09 20:08 ` Unionfs in -mm Jason Lunz
2007-01-13 6:48 ` Josef Sipek
2007-01-16 23:03 ` Jason Lunz [this message]
2007-01-17 0:28 ` [Unionfs] " Jan Engelhardt
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=20070116230327.GA3826@knob.reflex \
--to=lunz@falooley.org \
--cc=jsipek@fsl.cs.sunysb.edu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=unionfs@fsl.cs.sunysb.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.