> But seriously, I think the problem can be fixed with a more transparent
> interface for Linux programs. Rather than requiring Linux libraries to be put
> in /compat/linux, it would be much easier if everything could be put in
> /usr/lib. Which probably means having the SAME interface as Linux.
That would also result in a highly undesirable mish-mash of binaries
in one's /usr/lib, nor do I see the real advantage since the linux
compatability shim will look in /compat/linux/usr/lib first anyway.
Perhaps we should go just a bit further with that approach and make
things _write_ into that hierarchy first as well, e.g. if you run
/compat/linux/bin/bash and then install something with rpm, it will
install (as far as it's concerned) into /usr/bin, /usr/lib, etc. but
really be chrooted into the /compat/linux hierarchy and only affect
things there.
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
