Re: Resolutions to comments on LSB-FHS-TS_SPEC_V1.0
Unnamed sources report that Alan Cox said:
> > but I haven't heard any technical reasons besides, "Moving spool
> > directories is hard". When I and others have pointed out that moving
> > the spool directory isn't required; just a symlink, I have heard dead
> > silence. So the lack of technical discussion, but just a stony-silence
> > "No!" is rather disappointing as far as I'm concerned.
> One simple one - I want my mail on the spool disk. Its in the grows
> randomly, mostly crap, doesnt cause hassle if it fills for a while
No argument here.
> I have no problem with a "both paths must one work one or more may be a
> symlink". At that point however the FHS should mandate one which may be a
> symlink only. Right now everyone uses /var/spool/mail whats the technical
> reason for using /var/mail that is good enough to justify the change ?
Compatibility with other *NIXs? So, for example, I set up my $500 Linux
box to be a mail spool for a heterogeneous network of Sun, AIX, HP-UX,
yada, yada - their stuff wants /var/mail (can't actually say about AIX,
> While this is an open list, non-committee members are asked to lurk quietly.
So much for lurking quietly.
Informix on Linux FAQ - http://www.xmission.com/~kwall/iolfaq.html
Spanish Translation - http://www.xmission.com/~kwall/iolfaqsp.html