On Sun, Feb 20, 2000 at 01:47:30PM -0800, Jordan K. Hubbard wrote:
>
> You miss the point entirely.
Possibly.
> For others that's anywhere but since /usr is a comparatively small,
> read-only partition which they share amongst multiple boxes and they
> want the compat stuff to go in /usr/local/share/compat or something.
> The symlink gives you that flexibility and the fact that sysinstall
So they make /usr/compat be a symlink to where ever. As they may do for
/usr/X11R6. Buy why not reduce the complexity for the 90% case?
If we really imagine people wanting to put the compat bits elsewhere,
then we should make the location a knob in /etc/rc.conf and a sysctl to
tell the linux and osf1 image activators where to find the compat bits.
> I should also point out that making it a non-symlink would also
> completely break the linux_base port (for one) on those systems where
> /usr (and hence /usr/compat) is a read-only volume.
How did those read-only volumes get populated? How was the initial
install done? Build worlds? I don't see where installing compat bits is
any different.
> Ports aren't even technically supposed to touch anything outside of
> /usr/local,
A mistake, but that's too far gone to fix. [should have been /usr/pkg]
--
-- David ([EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
