[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-hotplug
Subject:    Re: [ANNOUNCE] udev 125 release
From:       md () Linux ! IT (Marco d'Itri)
Date:       2008-07-29 2:10:53
Message-ID: 20080729021053.GA5157 () bongo ! bofh ! it
[Download RAW message or body]

On Jul 29, David VomLehn <dvomlehn@cisco.com> wrote:

>> Also, they can be edited manually while /var data cannot.
> I don't know of any problems with editing /var data manually, but your 
It's one of the basic rules which have always defined /var. From FHS 2.3:

/var/lib : Variable state information

Purpose

This hierarchy holds state information pertaining to an application or the
system. State information is data that programs modify while they run, and that
pertains to one specific host. Users must never need to modify files in /var/
lib to configure a package's operation.

> Note that embedded systems are not the only case where read-only root 
> filesystems may arise. They are also used when your root filesystem is on 
> a CDROM or DVD, or when you have a read-only root filesystem so you can 
> network-mount it on multiple nodes. These cases influenced the Filesystem 
> Hierarchy Standard people to make /etc read-only. So, I think  that using 
> /etc for "on-the-fly" generated udev rules is an issue in a number of 
> situations.
Live CDs do not really need persistent status and in my experience
both these and embedded systems tend to use lots of special-purpose
hacks anyway.
The generated rules *are* a configuration file and there are endless
generated configuration files in /etc (tipically they are generated
once at install time, but on most systems the same applies to udev too).

If you have a R/O /etc an no human administrator which can edit system
files then just copy the rules files from /dev/.udev/rules.d/ to /var
and restore them at the next boot before udevtrigger is run.

> need for this feature, but is it possible that you wouldn't need to 
> generate rules *on-the-fly* until after mounting /var? If that were the 
> case, you could still put the generated rules there.
It does not matter when they are generated but when they are used,
e.g. they may be needed to NFS-mount /var.
At least on Debian systems, networking is started before even local
file systems are mounted.

-- 
ciao,
Marco
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
[prev in list] [next in list] [prev in thread] [next in thread]