From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev problems
Date: Mon, 18 Apr 2005 21:36:54 +0000 [thread overview]
Message-ID: <1113860214.25762.12.camel@localhost.localdomain> (raw)
In-Reply-To: <200403071315.02925.michal@cihar.com>
On Mon, 2005-04-18 at 15:27 -0600, clemens@dwf.com wrote:
> > On Mon, Apr 18, 2005 at 12:13:38PM -0600, clemens@dwf.com wrote:
> OK, sorry, a few lines got truncated off my original message when I
> posted it. The original started with:
> OK, Im having problems, and Im sure its UDEV that is doing the deed.
>
> [Fedora 2 and the latest udev ]
>
> First, is it legal to say
>
> udev_root="/dev/"
> udev_db="/dev/.udev.tdb
This is valid, sure. But that alone is not what you need to have it
working as you expect.
> If not, there should be a BIG sign on the /udev.conf page saying not to
> do this.
>
> If it is legal, ...
>
> So, back to the original question. IS THIS LEGAL?
>
> And, as I said there, Fedora2 + the most recently released udev.
You may investigate how Red Hat integrates udev into its distribution
instead of making your own experiments:
ftp://download.fedora.redhat.com/pub/fedora/linux/core/development/i386/Fedora/RPMS/udev-056-2.i386.rpm
The system needs a lot of tweaking to work reliable with udev. It's not
a simple download and install on an old system.
Good luck,
Kay
-------------------------------------------------------
This SF.Net email is sponsored by: New Crystal Reports XI.
Version 11 adds new functionality designed to reduce time involved in
creating, integrating, and deploying reporting solutions. Free runtime info,
new features, or free trial, at: http://www.businessobjects.com/devxi/728
_______________________________________________
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-04-18 21:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-07 12:15 udev problems Michal Čihař
2004-03-07 12:29 ` Kay Sievers
2004-03-07 12:47 ` Michal Čihař
2004-03-07 13:10 ` Michal Čihař
2004-03-07 13:44 ` Kay Sievers
2004-03-07 13:49 ` Michal Čihař
2004-03-07 14:05 ` Kay Sievers
2004-03-07 14:16 ` Kay Sievers
2004-03-07 14:20 ` Michal Čihař
2004-03-07 14:28 ` Kay Sievers
2004-03-07 14:30 ` Michal Čihař
2004-03-07 14:41 ` Kay Sievers
2004-03-07 14:43 ` Michal Čihař
2004-03-07 15:11 ` Michal Čihař
2004-03-07 15:28 ` Michal Čihař
2004-03-07 15:46 ` Michal Čihař
2005-04-18 18:13 ` clemens
2005-04-18 20:49 ` Greg KH
2005-04-18 21:02 ` David Zeuthen
2005-04-18 21:12 ` Greg KH
2005-04-18 21:27 ` clemens
2005-04-18 21:36 ` Kay Sievers [this message]
2005-04-19 7:36 ` clemens
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=1113860214.25762.12.camel@localhost.localdomain \
--to=kay.sievers@vrfy.org \
--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).