On Mon, 2003-07-28 at 13:35, Marco d'Itri wrote: > On Jul 28, Thomas Hood <[EMAIL PROTECTED]> wrote: > >or are being moved to /var/run/ . The problem with using /var/ > >is that some people mount /var/ over the network. Yet in the > >end we really want to remove these files from /etc/. If /run/ > >is not made available then these files will need to be > >eliminated entirely or else stored in /var/run/, and users > >that mount /var/ over the network will have to do something > >tricky to preserve these files when /var/ is mounted. Another > > As it has been explained, users who at the same time have a ro / and > mount /var over the network can create /run and the needed symlinks.
Yes, that is one of the tricky things that they can do. If that is the solution that Debian is going to recommend to people who mount / readonly and /var/ over a network, then it follows that the "difficult" files (i.e., those files that need to be written before /var/ is mounted) should continue to be written to their /etc/ location, but in such a way that this location can be a symlink. If not writing to /etc/ at run time becomes standard practice in Debian then these locations can be symlinked into /var/run/ on standard systems and into /run/ on network-/var/ systems. The creation of /run/ and the shifting of the appropriate symlinks could indeed be implemented in a handy package for this class of user. -- Thomas
