From: Mark Cannon <random.bits@rogers.com>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org
Subject: Re: Use of directories to hold root?
Date: Sun, 12 Aug 2007 15:39:48 -0400 [thread overview]
Message-ID: <200708121539.48332.random.bits@rogers.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0708111753510.3101@fbirervta.pbzchgretzou.qr>
On Saturday 11 August 2007, Jan Engelhardt wrote:
>
> On Aug 10 2007 17:08, H. Peter Anvin wrote:
> >Jan Engelhardt wrote:
> >> On Aug 10 2007 17:24, Mark Cannon wrote:
> >>> You pass the kernel the root option to specify the root partition.
> >>> Is there a way to identify a directory in that partition that holds the
> >>> root or something equivalent to this?
> >>
> >> No, but you can use pivot_root.
> >
> >Or better yet, use an initramfs with MS_MOVE; same as you would with the
> >"normal" use of initramfs.
>
> mount --move /foo /
> => error
>
> What did I miss?
>
>
>
> Jan
Thank you for the prompt replies. I have looked int pivot_root and
with my limited knowledge it looks like I could do this in the linuxrc
during start up. I believe the new kernel 2.6.21 is independent of the
root tree, so right after it mounts the old root /dev/sda3, it then can
pivot-root to /ker2621.
This can quickly be tested in the lab. I already use chroot for tests. Was
unaware of pivot_root.
I am not sure I understand initramfs with MS_MOVE concept. I will look into
it. Any pointers for documentation?
Again, thank you for the help.
Mark Cannon
next prev parent reply other threads:[~2007-08-12 19:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-10 21:24 Use of directories to hold root? Mark Cannon
2007-08-10 21:33 ` Jan Engelhardt
2007-08-11 0:08 ` H. Peter Anvin
2007-08-11 15:55 ` Jan Engelhardt
2007-08-11 16:07 ` Al Viro
2007-08-12 19:39 ` Mark Cannon [this message]
2007-08-12 19:49 ` Jan Engelhardt
2007-08-12 20:23 ` Al Viro
2007-08-12 20:55 ` Jan Engelhardt
2007-08-12 20:57 ` H. Peter Anvin
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=200708121539.48332.random.bits@rogers.com \
--to=random.bits@rogers.com \
--cc=hpa@zytor.com \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.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