public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Phillip Susi <psusi@cfl.rr.com>
To: John Richard Moser <nigelenki@comcast.net>
Cc: Jeff Bailey <jbailey@ubuntu.com>,
	linux-kernel@vger.kernel.org,
	ubuntu-devel <ubuntu-devel@lists.ubuntu.com>
Subject: Re: Keep initrd tasks running?
Date: Wed, 19 Oct 2005 14:52:30 -0400	[thread overview]
Message-ID: <435695EE.4090704@cfl.rr.com> (raw)
In-Reply-To: <4355C9F3.40004@comcast.net>

I thought that the key difference between initrd and initramfs is that 
initrd uses pivot_root, initramfs does not.  From what I have read, some 
consider pivit_root to be an ugly hack, so initramfs was made in such a 
way that you don't pivot.  Is this incorrect?

The whole reason that pivot was made was to allow the initrd filesystem 
to be moved and the real root mounted, all while processes ( at least 
init, because it can't exit ) continued to execute, maintaining their 
open files on the initrd filesystem.  Just instead of those files being 
in / they got moved to /initrd.

Under that system it is possible to leave things running, but I thought 
that with initramfs, init actually exited and the kernel unmounted the 
initramfs, and mounted the real root and ran the real init.

John Richard Moser wrote:
> 
> AFAIK it's pivoted and then umounted, which frees it.  This doesn't mean
> it has to be freed..  . .
> 
> 

  reply	other threads:[~2005-10-19 18:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-18 19:13 Keep initrd tasks running? John Richard Moser
2005-10-18 19:29 ` Jeff Bailey
2005-10-18 19:38   ` John Richard Moser
2005-10-18 21:43     ` Jeff Bailey
2005-10-19  3:35   ` Phillip Susi
2005-10-19  4:22     ` John Richard Moser
2005-10-19 18:52       ` Phillip Susi [this message]
2005-10-23 20:40         ` Matt Zimmerman
2005-10-23 20:38       ` Matt Zimmerman
2005-10-18 19:37 ` linux-os (Dick Johnson)
2005-10-19 11:07 ` Denis Vlasenko

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=435695EE.4090704@cfl.rr.com \
    --to=psusi@cfl.rr.com \
    --cc=jbailey@ubuntu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nigelenki@comcast.net \
    --cc=ubuntu-devel@lists.ubuntu.com \
    /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