On Sun, 25 Jul 1999, Joseph Carter wrote: > [...] My suggestion is > that we do not move /var/spool/mail on existing systems and instead simply > create a symlink from /var/mail and call it good. /var/mail should be the > directory on a new system, though the compatibility symlink should be > created (not maintained by any package) > > This allows the move to /var/mail to happen without seriously hindering > backward compatibility and allows us to continue to use software which > doesn't use /var/mail as long as we like. It also doesn't interfere with > the element of least surprise for a sysadmin who has /var/spool/mail > mounted as a partition.
I like this approach, that we keep /var/spool/mail for old systems. but move to /var/mail for new systems. If we agree on this, a possible plan would be: potato: Packages reference /var/spool/mail internally. base-files creates a symlink /var/mail -> /var/spool/mail potato+1: Packages reference /var/mail internally. * base-files creates /var/mail as a real directory and symlinks /var/spool/mail to /var/mail when it is installed by scratch by the boot-floppies script that creates the base system. * If upgrading from a previous version, do nothing. This way, people would be free to move /var/spool/mail/* to /var/mail/* at their discretion, but this is never done automatically by the system. Thanks. -- "2ffb5fb15ff66b92fabc4ffb2768df38" (a truly random sig)
