linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Frédéric L. W. Meunier" <1@pervalidus.net>
Cc: linux-kernel@vger.kernel.org, linux-hotplug-devel@lists.sourceforge.net
Subject: Re: HOWTO use udev to manage /dev
Date: Thu, 19 Feb 2004 23:07:49 +0000	[thread overview]
Message-ID: <20040219230749.GA15848@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0402191918440.688@pervalidus.dyndns.org>

On Thu, Feb 19, 2004 at 07:22:30PM -0300, Frédéric L. W. Meunier wrote:
> On Thu, 19 Feb 2004, Greg KH wrote:
> 
> >  - modify the rc.sysinit script to call the start_udev script as one of
> >    the first things that it does, but after /proc and /sys are mounted.
> >    I did this with the latest Fedora startup scripts with the patch at
> >    the end of this file.
> >
> >  - make sure the /etc/udev/udev.conf file lists the udev_root as /dev.
> >    It should contain the following line in order to work properly.
> > 	udev_root="/dev/"
> >
> >  - reboot into a 2.6 kernel and watch udev create all of the initial
> >    device nodes in /dev
> >
> >
> > If anyone has any problems with this, please let me, and the
> > linux-hotplug-devel@lists.sourceforge.net mailing list know.
> 
> Unless I'm missing something, it doesn't seem to work if you
> don't have /dev/null before it gets mounted.

Did you build udev using glibc or klibc?  I used klibc and it worked
just fine, as udev and udevd does not need /dev/null to work, unlike
programs built against glibc.

As for needing the fb nodes, you should probably just add them to the
start_udev script in the section that we add the other needed symlinks
to /dev until the kernel starts exporting those sysfs entries (hopefully
any day now...)

thanks,

greg k-h


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&opÌk
_______________________________________________
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:[~2004-02-19 23:07 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-19 18:59 [ANNOUNCE] udev 018 release Greg KH
2004-02-19 19:13 ` Greg KH
2004-02-20 12:48   ` Michael Buesch
2004-02-20 23:56     ` Greg KH
2004-02-19 19:16 ` HOWTO use udev to manage /dev Greg KH
2004-02-19 19:36   ` James Simmons
2004-02-19 19:46     ` Greg KH
2004-02-19 20:21   ` James Simmons
2004-02-19 20:28     ` Greg KH
2004-02-20  0:52     ` Andries Brouwer
2004-02-20 23:57       ` Greg KH
2004-02-19 21:35   ` James Simmons
2004-02-19 22:22   ` Frédéric L. W. Meunier
2004-02-19 22:25     ` Frédéric L. W. Meunier
2004-02-19 23:07     ` Greg KH [this message]
2004-02-19 23:46       ` Frédéric L. W. Meunier
2004-02-19 23:56         ` Greg KH
2004-02-20  0:51           ` Frédéric L. W. Meunier
2004-02-20  1:09             ` Frédéric L. W. Meunier
2004-02-20  1:54             ` Greg KH
2004-02-20  2:28               ` Frédéric L. W. Meunier
2004-02-20  7:44                 ` Frédéric L. W. Meunier
2004-02-21 17:42   ` Marco d'Itri
2004-02-22  0:30   ` Frédéric L. W. Meunier
2004-02-21 17:20 ` [ANNOUNCE] udev 018 release Prakash K. Cheemplavam
2004-02-24  1:49   ` 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=20040219230749.GA15848@kroah.com \
    --to=greg@kroah.com \
    --cc=1@pervalidus.net \
    --cc=linux-hotplug-devel@lists.sourceforge.net \
    --cc=linux-kernel@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).