Re: ifupdown writes to /etc... a bug?
This one time, at band camp, Thomas Hood wrote:
>Are there any objections to symlinking /var/run to /run
>(unless /var/run is already a rw, persistent, and non-network-
>mounted directory)?
>
>Advantages:
> * One path /var/run to all runtime state files -- no need to
> attend to how early in the boot sequence the file is used
> * No need to move files currently in /var/run to /run
> * No need to amend FHS
You don't need to.
Programs that stick stuff into a /run that lives on the root partition or is
available before /var/run is will just continue to use /run throughout their
lifetime.
Programs that use /var/run will continue to use /var/run throughout their
lifetime.
Symlinking /var/run to /run is too much effort for no gain, IMHO.
If you really need to have a single location for runtime state files, use
plasticfs! Coming soon to a Debian mirror near you!
--
jaq@debian.org http://people.debian.org/~jaq
Reply to: