From: Amit D Chaudhary <amit@muppetlabs.com>
To: Werner Almesberger <Werner.Almesberger@epfl.ch>
Cc: lermen@fgan.de, linux-kernel@vger.kernel.org
Subject: Re: /linuxrc query
Date: Thu, 22 Mar 2001 23:00:43 -0800 [thread overview]
Message-ID: <3ABAF49B.9080109@muppetlabs.com> (raw)
In-Reply-To: <3ABAEED2.6020708@muppetlabs.com> <20010323075107.Q3932@almesberger.net>
Hi,
Thanks for the response. PSB,
Werner Almesberger wrote:
> Amit D Chaudhary wrote:
>
> No, you would continue using the file descriptors which are already
> open, i.e. on /dev/console on the old root.
So, makes sense. And the child process that follow will use now the new fd's.
>> Also, why chroot, why not call init directly?
>
>
> To make sure the root of the current process is indeed changed.
> pivot_root currently forces a chroot on all processes (except the
> ones that have explicitly moved out of /) in order to move all the
> kernel threads too, but this is not a nice solution. Once a better
> solution is implemented for the kernel threads, we might drop the
> forced chroot, and then the explicit chroot here becomes important.
So, it is not a requirement currently but it is useful to have the script not
dependent on the current pivot_root implementation.
> You can run them later, e.g. /etc/rc.d/rc.local
> Or, if you needs the space immediately, make "what-follows" a
> script than first frees them, and then exec's init.
Sure will put in a script that does it. I had left it in /linuxrc as I thought
that's what initrd.txt suggested one to do. But other information in the
initrd.txt mentions otherwise, hence the query here.
I am assuming umount and thereby blockdev after pivot_script and before "chroot
. init ..." don't make sense as files(dev/console among others) are\might still
be in use.
Best Regards
Amit
next prev parent reply other threads:[~2001-03-23 7:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-23 6:36 /linuxrc query Amit D Chaudhary
2001-03-23 6:51 ` Werner Almesberger
2001-03-23 7:00 ` Amit D Chaudhary [this message]
2001-03-23 11:18 ` Werner Almesberger
2001-03-23 17:46 ` Amit D Chaudhary
2001-03-23 7:07 ` Amit D Chaudhary
2001-03-23 11:24 ` Werner Almesberger
2001-03-23 14:07 ` David Woodhouse
2001-03-23 18:00 ` RAMFS, CRAMFS and JFFS2(was Re: /linuxrc query) Amit D Chaudhary
2001-03-23 19:37 ` David Woodhouse
2001-03-23 20:25 ` CRAMFS Bjorn Wesen
2001-03-23 22:01 ` CRAMFS Amit D Chaudhary
[not found] <985356959.24859@whiskey.enposte.net>
2001-03-24 7:33 ` /linuxrc query Stuart Lynne
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=3ABAF49B.9080109@muppetlabs.com \
--to=amit@muppetlabs.com \
--cc=Werner.Almesberger@epfl.ch \
--cc=lermen@fgan.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