Date: Tue, 23 May 2000 20:55:02 -0700 From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com> To: Mohit Aron <aron@cs.rice.edu> Cc: protozoa@locutus.ghs.ssd.k12.wa.us (Dan Feldman), freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD kernel as a replacement for Linux kernel Message-ID: <24142.959140502@localhost> In-Reply-To: Your message of "Tue, 23 May 2000 22:48:10 CDT." <200005240348.WAA09825@noel.cs.rice.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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 majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?24142.959140502>