From: Arnd Bergmann <arnd@arndb.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev_db must be in a ramfs
Date: Sat, 06 Mar 2004 13:25:22 +0000 [thread overview]
Message-ID: <200403061425.23300.arnd@arndb.de> (raw)
In-Reply-To: <32794.65.172.181.6.1078443718.squirrel@secure.cgi101.com>
On Friday 05 March 2004 01:11, Ken Brush wrote:
> So, I tried another place /foo.
> Same thing
>
> Until I placed a mount -t ramfs none /foo entry in the udev startup script.
>
> So, thinking about it now. /tmp could've been a problem with the db being
> lost when /tmp is mounted (i.e. it was created and then a mount over the
> top of it.)
Note that you have to use ramfs for udev_root anyway if you want udev
to work properly, so the database by default ends up in the correct
place as long as udev_db points to a file below udev_root.
Arnd <><
-------------------------------------------------------
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
prev parent reply other threads:[~2004-03-06 13:25 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
2004-03-05 0:11 ` Ken Brush
2004-03-05 0:22 ` Ken Brush
2004-03-06 13:25 ` Arnd Bergmann [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=200403061425.23300.arnd@arndb.de \
--to=arnd@arndb.de \
--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).