linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phillip Susi <psusi@cfl.rr.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Run udev at start of boot
Date: Mon, 29 Oct 2007 20:26:53 +0000	[thread overview]
Message-ID: <4726420D.2030800@cfl.rr.com> (raw)
In-Reply-To: <e1d5030b0710270249l196bdc4cr21ebedb0858d9747@mail.gmail.com>

Midhun A wrote:
> Hi All,
> 
>    I have compiled udev 116 for my ARM system and put in the required
> scripts in /etc/init.d/rcS script. As this script is executed at the
> end boot, my devices get created at the end of boot. I would like to
> have the devices be created at the start of boot - as it happens in
> most Linux systems. How do I do that?

Depends on how your system is booting.  IIRC, Ubuntu uses an initramfs 
to boot up, then chains into the real root.  Udev is started early on in 
the initramfs init script so it can enumerate the hardware, then is 
killed off just before the chroot to the real root and then init starts 
up the copy in the real root.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
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

  reply	other threads:[~2007-10-29 20:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-27  9:49 Run udev at start of boot Midhun A
2007-10-29 20:26 ` Phillip Susi [this message]
2007-11-01 17:37 ` Midhun A
2007-11-01 18:50 ` Greg KH

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=4726420D.2030800@cfl.rr.com \
    --to=psusi@cfl.rr.com \
    --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).