From: Jeff Bailey <jbailey@ubuntu.com>
To: John Richard Moser <nigelenki@comcast.net>
Cc: linux-kernel@vger.kernel.org,
ubuntu-devel <ubuntu-devel@lists.ubuntu.com>
Subject: Re: Keep initrd tasks running?
Date: Tue, 18 Oct 2005 15:29:19 -0400 [thread overview]
Message-ID: <1129663759.18784.98.camel@localhost.localdomain> (raw)
In-Reply-To: <4355494C.5090707@comcast.net>
Le mardi 18 octobre 2005 à 15:13 -0400, John Richard Moser a écrit :
> I have no idea who's the best to ask for this.
>
> I want to start a task in an initrd and have it stay running after init
> is started. Pretty much:
> What's the feasibility of this without the system balking and vomiting
> chunks everywhere? I'm pretty sure 'exec /sbin/init' from linuxrc
> (PID=1) will replace the process image of sh (linuxrc) with init,
> keeping PID=1; but I'm worried this may terminate children too. Haven't
> tried.
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
next prev parent reply other threads:[~2005-10-18 19:36 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 [this message]
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
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=1129663759.18784.98.camel@localhost.localdomain \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.