From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev_db must be in a ramfs
Date: Fri, 05 Mar 2004 00:04:30 +0000 [thread overview]
Message-ID: <1078445069.1760.16.camel@pim> (raw)
In-Reply-To: <32794.65.172.181.6.1078443718.squirrel@secure.cgi101.com>
On Fri, 2004-03-05 at 00:41, Ken Brush wrote:
> So, I ran a few tests on location of the tdb database (config file:
> udev_db variable). And was only able to put in a ramfs location for it.
>
> So my main question is: Is this a bug or a feature? If it's a feature,
> I'll just submit a patch for the documentation to prevent people from
> trying to put it on a non-ramfs area. If it's a bug, then I would work on
> fixing it. :)
No, it's neither a bug nor a feature. :)
I'm able to place the db wherever I want on the filesystem.
udev doesn't know anything about ramfs, it works on any filesytem.
What is your problem exactly?
thanks,
Kay
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&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:[~2004-03-05 0:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-04 23:41 udev_db must be in a ramfs Ken Brush
2004-03-05 0:04 ` Kay Sievers [this message]
2004-03-05 0:11 ` Ken Brush
2004-03-05 0:22 ` Ken Brush
2004-03-06 13:25 ` Arnd Bergmann
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=1078445069.1760.16.camel@pim \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.