From owner-freebsd-hackers Mon Nov 9 16:02:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA10085 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 16:02:53 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA10080 for ; Mon, 9 Nov 1998 16:02:52 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.8.8) id QAA11726; Mon, 9 Nov 1998 16:06:32 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199811100006.QAA11726@troutmask.apl.washington.edu> Subject: Re: linux software installation and uname In-Reply-To: <199811092317.QAA08648@mt.sri.com> from Nate Williams at "Nov 9, 1998 4:17:28 pm" To: nate@mt.sri.com (Nate Williams) Date: Mon, 9 Nov 1998 16:06:32 -0800 (PST) Cc: nate@mt.sri.com, jkh@time.cdrom.com, crossd@cs.rpi.edu, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Nate Williams: > > > > I'm suggesting a change to uname(1) not uname(3). Binaries are > > unaffected by setting an ALT_UNAME environmental variable. > > No, but in order to get the 'correct' behavior, I have to know which OS > I need emulated so I can set the environment variable correctly. > > So, if I want to run SCO's Informix which uses uname (it does, BTW), I > have to set 'ALT_UNAME' to "SCO". Then, I want to run StarOffice, so I > have set 'ALT_UNAME' to "Linux", then I want to run the JDK, so I have > to set 'ALT_UNAME' to "Solaris", or was it the Linux version that I was > running? I don't remember if it was the Solaris version, or the Linux > version? I must be confused by your objection. Do Informix, StarOffice, and JDK use popen() to call uname(1) instead of uname(3)? I assume uname(3) will be resolved from the /compat/linux/usr/lib/libc.so.5 library. > > The point is that it's *NOT* transparent to the users, so the solution > isn't any better than the initial problem, but it adds more bloat and > more 'magic' solutions that are no better than editing shells scripts. It's fairly difficult to edit a shell script on a CDROM. Note, it is not a simple matter to copy the shell script to a temporary directory and change linux to FreeBSD. Some vendors expect the script to be executed from a particular directory in their CDROM hierarchy. I can change uname(1) with 4 lines, or I can fix UNIONFS. -- 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