linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vassilis Virvilis <vasvir@iit.demokritos.gr>
To: linux-hotplug@vger.kernel.org
Subject: Re: udevd "got lost" after moving /dev
Date: Thu, 02 Feb 2006 13:25:24 +0000	[thread overview]
Message-ID: <43E20844.2080803@iit.demokritos.gr> (raw)
In-Reply-To: <cfb54190601310429n35d835afi10c445627b168444@mail.gmail.com>

Kay Sievers wrote:

> Don't run the daemon from initramfs on the real root. You should kill it
> before leaving initramfs and start the real one. Ususally you also want
> to replay all events in the real root, cause there could be different
> rules and different tools available than in initramfs.
> 
> Kay
> 

Wouldn' do this the trick?

mount -o bind /dev /root/dev;
where /root is mounted the "real" root device
just before releasing control to the "real" init

exec run-init ${rootmnt} ${init} "$@";

     .bill


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x103432&bid#0486&dat\x121642
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2006-02-02 13:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-31 12:29 udevd "got lost" after moving /dev Hai Zaar
2006-01-31 14:33 ` Kay Sievers
2006-01-31 14:47 ` Hai Zaar
2006-01-31 15:29 ` Scott James Remnant
2006-01-31 16:36 ` Hai Zaar
2006-02-02 13:25 ` Vassilis Virvilis [this message]
2006-02-02 13:34 ` Kay Sievers
2006-02-02 18:12 ` Vassilis Virvilis

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=43E20844.2080803@iit.demokritos.gr \
    --to=vasvir@iit.demokritos.gr \
    --cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).