From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev questions
Date: Sun, 17 Jul 2005 18:49:17 +0000 [thread overview]
Message-ID: <20050717184917.GA25218@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.60.0507171252510.21434@pc1lin.fred.org>
On Sun, Jul 17, 2005 at 01:24:11PM -0400, F. Heitkamp wrote:
>
> I am trying to get udev working. I am using Linux kernel 2.6.12.2. I
> have a sort of my own "Linux from scratch" distro based on Debian. I am
> trying to get udev version 0.63 working.
>
> The most pressing question concerns the order and way the configuration
> files get read. I grepped through the sources but it is difficult to see
> which and which order the files get read. I've noticed on the fully
> Debian alternate set up on the same machine that there are "rules" files
> in the /etc/udev directory, but only one or so rules file in the rules.d
> directory. Can someone explain to me the hierarchy of the configuation
> files, which are essential, and what order they get read?
/etc/udev/udev.conf is the main config file. The rules file (or the
rules file directory) is specified in that file.
That's it :)
thanks,
greg k-h
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id\x16492&op=click
_______________________________________________
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
next prev parent reply other threads:[~2005-07-17 18:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-17 17:24 udev questions F. Heitkamp
2005-07-17 18:49 ` Greg KH [this message]
2009-05-21 7:46 ` Alan Jenkins
2009-05-21 10:21 ` Alan Jenkins
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=20050717184917.GA25218@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).