> > I feel that we are relying too much on base-files for no particular > > reason. In fact, I don't see any benefit of having /run in base-files > > at this point. > > The main need for this is debootstrap. There's two possible ways > initscripts can handle the migration: > > 1) Normal system > - on installation, bind mount /var/run to /run, /var/lock to /run/lock > - on reboot, set up /run as a tmpfs and convert the original locations > to symlinks > 2) Chroot or other virtual environment > - the above isn't possible (no scripts run on startup etc.) > - on installation, symlink /run → /var/run and > /run/lock (/var/run/lock) → /var/lock
You seem to imply that we should migrate each and every file at once. We could just declare /var/run obsolete and not make any bind mount or symlink. The use of /var/run then would just fade away over time, like it happened with the /usr/doc transition. AFAIK (please correct me if I'm wrong), this is not like /var/mail where email clients look at a single place. Packages putting things in /var/run will look for them in /var/run, and packages putting things in /run will look for them in /run. But even if we want symlinks or bind mounts: I made a mistake in base-files 2.1.18 when I added /dev/pts (this was more than 10 years ago, but there are a lot of similarities). Things became too tricky because /dev was a virtual filesystem. I had to remove it in 2.1.20 with urgency=high, but since then it is clear to me that this kind of things are better handled by whatever package is actually populating those directories. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
