Date: Mon, 9 Nov 1998 15:16:12 -0800 (PST) From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: nate@mt.sri.com (Nate Williams) Cc: nate@mt.sri.com, jkh@time.cdrom.com, crossd@cs.rpi.edu, hackers@FreeBSD.ORG Subject: Re: linux software installation and uname Message-ID: <199811092316.PAA11509@troutmask.apl.washington.edu> In-Reply-To: <199811092004.NAA06080@mt.sri.com> from Nate Williams at "Nov 9, 1998 1: 4: 7 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
According to Nate Williams: > > > > I think the correct thing to do here is simply give uname(1) some > > > > truly switchable behavior, as Steve's second patch did. > > > > > > The user then has to be aware of the 'LINUX_EMULATION' environment > > > variable, which is non-intuitive. The /compat/linux script is a much > > > better solution since it doesn't require any magic environment > > > knowledge that must be modified if you run binaries from multiple > > > 'emulated' OS's. > > > > > > > You're assuming the vendor supplied script will pick up the script > > in /compat/linux. That, is not the case for the Portland Group > > script: > > You didn't answer the question. What if I have multiple binaries from > different OS's on the system. The user has to be aware of the 'magic' > environment variable and have it switch between them. Once we're on > that path, we're no better off than we are now. > I'm suggesting a change to uname(1) not uname(3). Binaries are unaffected by setting an ALT_UNAME environmental variable. Shell scripts are a different beast, and so you would have to protect binaries called from within a shell: #! /bin/sh setenv ALT_UNAME Linux a_linux_binary unsetenv ALT_UNAME .... setenv ALT_UNAME FooOS a_FooOS binary unsetenv ALT_UNAME Although I doubt that there are many (if any) shell scripts that mix binaries from different OS emulations, I suppose its a possibility. -- 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?199811092316.PAA11509>