public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Richard Moser <nigelenki@comcast.net>
To: linux-kernel@vger.kernel.org,
	ubuntu-devel <ubuntu-devel@lists.ubuntu.com>
Subject: Keep initrd tasks running?
Date: Tue, 18 Oct 2005 15:13:16 -0400	[thread overview]
Message-ID: <4355494C.5090707@comcast.net> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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:


 - kernel boot
 - initrd loaded
 - linuxrc executes
 - /bin/mydaemon runs
 - mount rootfs
 - pivot_root
 - exec /sbin/init (PID=1; linuxrc and sh is replaced)
 - mydaemon keeps running, reparented under init, uninterrupted


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 actually has a useful application)
- --
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

iD8DBQFDVUlKhDd4aOud5P8RAuTeAJ9z7F+aeLZgnHzuzyviSXhJG/d5egCcCoxs
GpD7wLP+ZngCsYFLGsmEXb0=
=w6xA
-----END PGP SIGNATURE-----

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

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-18 19:13 John Richard Moser [this message]
2005-10-18 19:29 ` Keep initrd tasks running? 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
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=4355494C.5090707@comcast.net \
    --to=nigelenki@comcast.net \
    --cc=linux-kernel@vger.kernel.org \
    --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