Re: Bug#42052: [PROPOSAL] /var/mail and /var/spool/mail

[Daniel Quinlan <quinlan@transmeta.com>]

Joseph Carter <knghtbrd@debian.org> writes:

> I propose that we create a safe migration path between /var/spool/mail and
> /var/mail.
> 
> The base-files package should implement the following:
>   * If /var/mail does not exist but /var/spool/mail does (standard
>     configuration today), a symlink /var/mail -> /var/spool/mail should be
>     created.

Are there any cases where you can do a move?  Maybe the user should be
given the option of moving the directory (or mount point).  Yes, there
is a small window where sendmail must be shutdown, but I think it may
be acceptable to many users.  Anyway, I thought I'd ask.

Maybe advanced sysadmins can just do it themselves.  Please make sure
that a self-move is also possible since it will happen.

>   3.1.3 The system mail spool
> 
>    While the FHS mandates the mail spool be accessable as /var/mail, it is
>    important to retain compatibility with older packages and locally
>    compiled programs.  Packages using the mail spool should use /var/mail
>    and declare dependency on base-files (>= #BASEFILESVER#).

This is actually not a violation of FHS 2.1 pre-draft #2.  It also
implies the idea of retaining compatibility with older packages
contradicts FHS.  Therefore, I'd suggest something like:

    The FHS mandates the mail spool be accessible as /var/mail.  In
    order to guarantee compatibility with older packages and locally
    compiled programs, packages using the mail spool should use
    /var/mail and declare dependency on base-files (>= #BASEFILESVER#).

Otherwise, I like the proposal very much.

Dan