From: John Richard Moser <nigelenki@comcast.net>
To: Phillip Susi <psusi@cfl.rr.com>
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 00:22:11 -0400 [thread overview]
Message-ID: <4355C9F3.40004@comcast.net> (raw)
In-Reply-To: <4355BEF4.8000800@cfl.rr.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Phillip Susi wrote:
> I am confused. I thought that once the initramfs init execs the real
> init, the initramfs is freed. It can't be freed if there are processes
> that still have open files there, so that would seem to prevent any
> processes being started in the initramfs and continuing after the real
> system is booted.
>
AFAIK it's pivoted and then umounted, which frees it. This doesn't mean
it has to be freed.. . .
> Jeff Bailey wrote:
>
>> This is much more easily supported in Breezy. usplash is started at the
>> top of the initramfs (from the init-top hook) and lives until we start
>> gdm.
>>
>> The biggest constraint is that you don't have write access to the target
>> root filesystem (since it's mounted readonly). However, /dev is a tmpfs
>> that is move mounted to the new root system. If you need to have
>> sockets open or store data, you can use that. usplash does this for its
>> socket.
>>
>> Note that the initramfs startup sequence isn't at all similar to the old
>> initrd startups. It should be easy for you to cleanly add what you want
>> under /etc/mkinitramfs/scripts and not have to modify the
>> initramfs-tools package. /usr/share/doc/initramfs-tools/HACKING
>> contains some starter information.
>>
>> Hope this helps!
>>
>> Tks,
>> Jeff Bailey
>>
>>
>>
>>
>>
>>
>>
>
>
- --
All content of all messages exchanged herein are left in the
Public Domain, unless otherwise explicitly stated.
Creative brains are a valuable, limited resource. They shouldn't be
wasted on re-inventing the wheel when there are so many fascinating
new problems waiting out there.
-- Eric Steven Raymond
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFDVcnzhDd4aOud5P8RAmk/AJ48RK9V5CrJeNXu/ORxuNa3I/+jrACeOkUl
z2l1tNTWm6dtjysddaZ81co=
=7GLq
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2005-10-19 4:24 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 [this message]
2005-10-19 18:52 ` Phillip Susi
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=4355C9F3.40004@comcast.net \
--to=nigelenki@comcast.net \
--cc=jbailey@ubuntu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=psusi@cfl.rr.com \
--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