From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Hotplug events vs proc - timing
Date: Thu, 03 Jun 2004 16:54:55 +0000 [thread overview]
Message-ID: <20040603165455.GB4105@kroah.com> (raw)
In-Reply-To: <40BCD9C6.1040909@cornell.edu>
On Wed, Jun 02, 2004 at 05:19:19PM -0600, Ivan Gyurdiev wrote:
> >Yes, good point, you should update the fstab after the device node is
> >created. You can learn of that by putting your script in the
> >/etc/dev.d/ directory tree.
>
> FC2 does not use udev. I'd like to use udev, but I understand there are
> early userspace issues to resolve. Last time I tried it did not work
> well for me, since init wouldn't start.
I use udev on FC2 just fine. See the README notes on how to do this in
the udev tarball. FC2 also ships a udev rpm, which you can use not to
manage your /dev, but to handle the /etc/dev.d notification only if you
wish.
Good luck,
greg k-h
-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
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
prev parent reply other threads:[~2004-06-03 16:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-01 19:32 Hotplug events vs proc - timing Ivan Gyurdiev
2004-06-02 17:20 ` Greg KH
2004-06-02 17:36 ` Bill Nottingham
2004-06-02 17:41 ` Greg KH
2004-06-02 17:57 ` Marcelo Ricardo Leitner
2004-06-02 18:05 ` Greg KH
2004-06-02 23:19 ` Ivan Gyurdiev
2004-06-03 8:30 ` Harald Hoyer
2004-06-03 16:54 ` Greg KH [this message]
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=20040603165455.GB4105@kroah.com \
--to=greg@kroah.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).