/usr/portsnap vs. /var/db/portsnap

[Simon L. Nielsen]

On 2005.08.06 02:58:52 -0700, Colin Percival wrote:
> Simon L. Nielsen wrote:
> > On 2005.08.06 01:59:57 -0700, Colin Percival wrote:
> >>Is this a reasonable excuse for violating hier(7) and putting the
> >>compressed snapshot into /usr/portsnap?  For reference, the port keeps
> >>the snapshot in /usr/local/portsnap.
> > 
> > Wouldn't it make sense to put in on /var, and if people do not have
> > enough space there, they can just symlink the portsnap directory to a
> > location that has enough space?
> 
> Probably... I'm just worried about inexperienced FreeBSD users who would
> see an error message about /var being full and not know what to do about
> it.

I don't really think that is a big problem, especially if the default
/var size is increased so it doesn't happen to total novices using
default install.

If it turns out the be a problem, I think it would be better to have
portsnap warn the users when /var runs full e.g. with a URL to the FAQ
that describes how to work around the problem.

Anyway, that's just my 0.02 $LOCAL_CURRENCY.

-- 
Simon L. Nielsen
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-arch/attachments/20050807/c31471b7/attachment.bin