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

Norikatsu Shigemura nork at FreeBSD.org
Sat Aug 6 09:22:55 GMT 2005


On Sat, 06 Aug 2005 01:59:57 -0700
Colin Percival <cperciva at freebsd.org> wrote:
> Portsnap keeps a compressed snapshot of the ports tree, requiring
> roughly 50MB and 13000 inodes.  The "natural" place for this to go
> would be in /var/db/, but I suspect that this would cause problems
> for many users, particularly when it comes to the number of inodes.
> 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.

	Cvsup (/usr/share/examples/cvsup/ports-supfile) put
	/var/db/sup.  So portsnap should put on /var/db.
	At least, we should be able to 'mount -ro /usr'.

	/var/db/portsnap causes a problem to users,
	ln -s /usr/portsnap /var/db/portnap.


More information about the freebsd-arch mailing list