Date: 12 Nov 1998 16:04:23 -0600 From: Joel Ray Holveck <joelh@gnu.org> To: Jamie Bowden <jamie@itribe.net> Cc: hackers@FreeBSD.ORG Subject: Re: linux software installation and uname Message-ID: <8667ckr2jc.fsf@detlev.UUCP> In-Reply-To: Jamie Bowden's message of "Thu, 12 Nov 1998 08:14:51 -0500 (EST)" References: <Pine.SGI.3.96.981112081216.966O-100000@animaniacs.itribe.net>
next in thread | previous in thread | raw e-mail | index | archive | help
>>>> I would recommend putting a Linux >>>> uname in /copmat/linux where it belongs, and the install procedure's >>>> PATH can have /compat/linux ahead of /. >>> chroot /compat/linux ; install >> Not unless you have a complete minimal tree under /compat/linux. > Someone asked for a solution that didn't require corrupting the base > FreeBSD installation or source tree with compatability issues. I am well > aware of the technical necessities of a chrooted environment, but it does > give you a clean way to handle special cases like this. If we assume a complete minimal tree under /compat/linux, then it follows that there exists a /compat/linux/bin/uname. Adding it to the $PATH before running the install script is sufficient. (This would replace the chroot step, so considerations about r/o media do not create a distinction between these proposals.) Therefore, it seems that the requirements for my proposal are a subset of the requirements of yours. If you do a lot of Linux work, then having a complete /compat/linux is probably a good thing. Personally, I don't, so I would prefer to only add a uname. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped 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?8667ckr2jc.fsf>