From: viro@parcelfarce.linux.theplanet.co.uk
To: Andrey Borzenkov <arvidjaar@mail.ru>
Cc: Chris Friesen <cfriesen@nortelnetworks.com>,
"Kevin P. Fleming" <kpfleming@backtobasicsmgmt.com>,
Jeff Garzik <jgarzik@pobox.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Is initramfs freed after kernel is booted?
Date: Mon, 17 Nov 2003 19:15:13 +0000 [thread overview]
Message-ID: <20031117191513.GA24159@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <200311172133.59839.arvidjaar@mail.ru>
On Mon, Nov 17, 2003 at 09:33:59PM +0300, Andrey Borzenkov wrote:
> On Monday 17 November 2003 21:03, viro@parcelfarce.linux.theplanet.co.uk
> wrote:
> > On Mon, Nov 17, 2003 at 12:50:34PM -0500, Chris Friesen wrote:
> > > viro@parcelfarce.linux.theplanet.co.uk wrote:
> > > >On Mon, Nov 17, 2003 at 11:06:48AM -0500, Chris Friesen wrote:
> > > >>Anyone know why it overmounts rather than pivots?
> > > >
> > > >Because amount of extra code you lose that way takes more memory than
> > > >empty roots takes.
> > > >
> > > >Remove whatever files you don't need and be done with that.
> > >
> > > How do you remove files from the old rootfs after the new one has been
> > > mounted on top of it?
> >
> > You do that before ;-)
>
> would the following work?
>
> pivot_root . /initramfs
> cd /initramfs && rm -rf *
No. pivot_root() will not move the absolute root of tree elsewhere.
> ?? doing it before is rather hard ... you apparently still need something to
> execute your mounts :)
You do, but you can trivially call unlink() on the executable itself. It
will be freed after it does exec() of final /sbin/init...
Alternatively, you could
mkdir /root
mount final root on /root
chdir("/root");
mount("/", "initramfs", NULL, MS_BIND, NULL);
mount(".", "/", NULL, MS_MOVE, NULL);
chroot(".");
execve("/sbin/init", ...)
and have init scripts do rm -rf /initramfs/*; umount /initramfs
next prev parent reply other threads:[~2003-11-17 19:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-16 17:09 Andrey Borzenkov
2003-11-16 19:51 ` Jeff Garzik
2003-11-17 14:39 ` Chris Friesen
2003-11-17 15:36 ` "Andrey Borzenkov"
2003-11-17 15:39 ` Chris Friesen
2003-11-17 15:46 ` Jeff Garzik
2003-11-17 18:32 ` Bryan O'Sullivan
2003-11-17 15:47 ` Kevin P. Fleming
2003-11-17 16:06 ` Chris Friesen
2003-11-17 16:25 ` Erik Mouw
2003-11-17 17:25 ` viro
2003-11-17 17:47 ` viro
2003-11-17 17:50 ` Chris Friesen
2003-11-17 18:03 ` viro
2003-11-17 18:33 ` Andrey Borzenkov
2003-11-17 19:15 ` viro [this message]
2003-11-19 14:19 ` Olaf Hering
2003-11-19 15:07 ` Hannes Reinecke
2003-11-25 18:26 ` Manuel Estrada Sainz
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=20031117191513.GA24159@parcelfarce.linux.theplanet.co.uk \
--to=viro@parcelfarce.linux.theplanet.co.uk \
--cc=arvidjaar@mail.ru \
--cc=cfriesen@nortelnetworks.com \
--cc=jgarzik@pobox.com \
--cc=kpfleming@backtobasicsmgmt.com \
--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
Powered by JetHome