Date: Thu, 12 Nov 1998 07:49:57 -0800 (PST) From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: joelh@gnu.org (Joel Ray Holveck) Cc: dfr@nlsystems.com, sos@freebsd.dk, n@nectar.com, nate@mt.sri.com, kkennawa@physics.adelaide.edu.au, dnelson@emsphone.com, rivers@dignus.com, hackers@FreeBSD.ORG Subject: Re: linux software installation and uname Message-ID: <199811121549.HAA05341@troutmask.apl.washington.edu> In-Reply-To: <86n25xih5w.fsf@detlev.UUCP> from Joel Ray Holveck at "Nov 12, 1998 0: 0:59 am"
next in thread | previous in thread | raw e-mail | index | archive | help
According to Joel Ray Holveck:
> >> I have yet to hear of any solutions that don't require a hack to the
> >> install procedure (eg, setting an environment variable). Unless
> >> somebody comes up with an idea that would magically detect what
> >> environment a given script wants, 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 /. This is easy to implement,
> >> keeps the core of FreeBSD pure, and paves the way for future
> >> similarities.
> > What about install scripts that reside on cdroms? You can't magically
> > edit a cdrom install script unless unionfs works.
>
> I'm not talking about editing a script. I'm talking about:
>
> PATH=/compat/linux/bin:/compat/linux/usr/bin:${PATH} ; make install
>
Echo: What about install scripts that reside on cdroms? You can't magically
edit a cdrom install script unless unionfs works.
#! /bin/sh
PATH=/cdrom:/foo:/bar
export PATH
...
rest of script
--
Steve
finger kargl@troutmask.apl.washington.edu
http://troutmask.apl.washington.edu/~clesceri/kargl.html
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?199811121549.HAA05341>