Lenz Grimmer
Hi,
On 24 Jan 2000, Bud Rogers wrote:
I fully agree with this. I don't want the distribution doing anything in /usr/local. That is where I put stuff I've installed myself. My understanding of the FHS is that a distribution should not put ANYTHING in /usr/local.
This is correct, and we unfortunately violate the FHS in this respect.
How about /var/http and /var/ftp? Would that fit with FHS? If not, how about in /usr/share? I guess for a long time the convention on ftp was /home/ftp. I never really understood the logic of that.
And this is the big problem. Since FHS and LSB do not seem to address this issue in the foreseeable future, it looks like we will simply have to get the apache and ftp maintainers of the other distributions on one table. Maybe we can find a consensus. We are not reluctant to make this change, but we want to make sure, that we only have to change it _once_ more. We have been flamed enough in the past about moving everything around from release to release :) As long as there has been no agreement about this, the current location is unlikely to change.
Hi Lenz,
I can sympathize with your (that is SuSE's) situation. I read through the
FHS again and it really is not obvious where ftp/http data files should go.
Both my ideas are plausible candidates, I think, but neither clearly fits
the FHS as written. The /var heirarchy was created so that /usr could be
mounted read-only, which would make /usr/share/ftp/incoming a problem. Yet
the standard seems to describe /var as a place for variable temporary data
like /var/run, /var/lock, /var/spool, which sounds much too ephemeral for
something like an enduring ftp archive. Still, /var/something seems the
most likely place to me.
Certainly there should be a consensus. And it would be better for everyone
if that consensus applied across all distributions. I guess under the
circumstances, /usr/local/httpd is as good a wrong place as any. :}
--
Bud Rogers