> You add a symlink from /usr to something, then when a configure script > tries to detect /usr it finds it and then starts making all sorts of other > assumptions. For what it's worth, I can't recall that I've seen a configure script do that. If I understand what you mean. I can't think of any real problems with /usr -> /boot/system, but it seems sort of misleading. I mean, if /boot/system really is conceived as more or less the equivalent of /usr on UNIX, then I guess it's fair, but ... is that really what you want to say? or would it worth the trouble to set up a path that really specifically leads to /boot/system/bin/env and makes the intention less ambiguous. Like mkdir -p /boot/usr/bin ln -s /boot/system/bin/env /boot/usr/bin/ ln -s /boot/usr / That makes it pretty clear why there's a /usr, and if nothing else it might mean slightly fewer requests for /usr/include, etc. Donn