linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: md@Linux.IT (Marco d'Itri)
To: linux-hotplug@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 125 release
Date: Tue, 29 Jul 2008 02:10:53 +0000	[thread overview]
Message-ID: <20080729021053.GA5157@bongo.bofh.it> (raw)
In-Reply-To: <1216627334.7816.12.camel@linux.site>

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

      parent reply	other threads:[~2008-07-29  2:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-21  8:02 [ANNOUNCE] udev 125 release Kay Sievers
2008-07-21  9:05 ` Marco d'Itri
2008-07-21 10:56 ` Matthias Schwarzott
2008-07-21 11:14 ` Kay Sievers
2008-07-21 11:19 ` Kay Sievers
2008-07-21 15:47 ` David Zeuthen
2008-07-22  0:06 ` David Zeuthen
2008-07-22  7:57 ` Kay Sievers
2008-07-22 13:15 ` Doug Goldstein
2008-07-28 23:08 ` David VomLehn
2008-07-28 23:32 ` Marco d'Itri
2008-07-29  1:53 ` David VomLehn
2008-07-29  2:10 ` Marco d'Itri [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=20080729021053.GA5157@bongo.bofh.it \
    --to=md@linux.it \
    --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).