Re: Resolutions to comments on LSB-FHS-TS_SPEC_V1.0
- To: "Theodore Y. Ts'o" <tytso@MIT.EDU>
- Cc: "H. Peter Anvin" <email@example.com>, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com
- Subject: Re: Resolutions to comments on LSB-FHS-TS_SPEC_V1.0
- From: Florian La Roche <firstname.lastname@example.org>
- Date: Thu, 21 Jan 1999 08:44:45 +0100
- Message-id: <19990121084445.B6544@knorke.saar.de>
- In-reply-to: <199901200842.DAA17379@dcl>; from Theodore Y. Ts'o on Wed, Jan 20, 1999 at 03:42:46AM -0500
- References: <199901200819.AAA11535@cesium.transmeta.com> <199901200842.DAA17379@dcl>
> I agree. I also don't think it's a big deal. What's important is that
> all of the MUA's get compiled so that they look for the mail spool in
> /var/mail. If /var/mail is a symlink to /var/spool/mail, or /u3/mail,
> or something else --- that's fine.
Adding that symlink can be done easily by the admin of a machine. Why
do you already want to do it on the distribution level?
I'd either want the standard to move everything to /var/mail and
abandom /var/spool/mail or to keep with /var/spool/mail.
The move to /var/mail would take some time for the Linux community until
it is finished. The end result would be that (just like now with /var/mail)
some admins will add a link from /var/spool/mail to the new /var/mail to
be compatible with old Linux systems or DEC machines.
So the move to /var/mail will get us some confusion in the Linux community
and at the end we will have the same situation as now: some admins will
have to add a compatibility symlink. We achieved nothing...
Please think about it and stay with /var/spool/mail.
Florian La Roche