Re: Resolutions to comments on LSB-FHS-TS_SPEC_V1.0
- To: firstname.lastname@example.org (H. Peter Anvin)
- Cc: email@example.com, tytso@MIT.EDU, 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, firstname.lastname@example.org
- Subject: Re: Resolutions to comments on LSB-FHS-TS_SPEC_V1.0
- From: "H. Peter Anvin" <email@example.com>
- Date: Wed, 20 Jan 1999 23:53:32 -0800 (PST)
- Message-id: <199901210753.XAA25754@cesium.transmeta.com>
- In-reply-to: <199901210750.XAA25715@cesium.transmeta.com> from "H. Peter Anvin" at "Jan 20, 99 11:50:58 pm"
> > Please think about it and stay with /var/spool/mail.
Right now, /var/mail and /var/spool/mail both suffer the same problem:
whichever is used, some people need to use the other, hence it is a
*requirement* that both can be used by programs.
Given that, it is better to use /var/mail, because the mail inbox
directory is *not* a spool (a daemon transshipment point -- the mail
*spool* is /var/spool/mqueue.) Putting it under /var/spool causes
disk space management problems.