From owner-freebsd-hackers Mon Nov 9 09:42:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA28348 for freebsd-hackers-outgoing; Mon, 9 Nov 1998 09:42:58 -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 JAA28341 for ; Mon, 9 Nov 1998 09:42:57 -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 JAA10366; Mon, 9 Nov 1998 09:46:42 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199811091746.JAA10366@troutmask.apl.washington.edu> Subject: Re: linux software installation and uname In-Reply-To: <199811091713.KAA04612@mt.sri.com> from Nate Williams at "Nov 9, 1998 10:13:22 am" To: nate@mt.sri.com (Nate Williams) Date: Mon, 9 Nov 1998 09:46:42 -0800 (PST) Cc: 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've recently installed the Portland Groups's Fortran 90 > > for Linux on my system (it works!). However, during the > > installation from the cdrom, a install script is executed > > that contains a test involving "uname -s" to ensure the > > installation is on a system running Linux. Of course, > > "uname -s" on a FreeBSD system returns "FreeBSD" instead > > of the expected "Linux". Thus, I had to alter uname(1) > > to report "Linux" to install the software. > > Actually, you didn't. Stick a uname in the appropriate /compat/linux > directory and it will be called (and return Linux) which doesn't bloat > FreeBSD's code with Linux-centric bits. > > This can be done as a simple shell script or as complex as you'd like. > First, I generally agree with your anti-bloat sentiments. Sure, I have the capability to write the script or C program, and stuff it into /usr/compat/linux/usr/bin, but this isn't a general solution for Jane Doe user. She wants/needs to run linux software, and she may not have the know-how to work around this problem. Neither ports/emulator/linux_lib nor ports/devel/linux_devel supply a uname(1). I am not claiming that my suggested solution is the best solution. But, we can't ignore the problem exists. At this point time, the Portland Group has no intention of supporting a native FreeBSD version of their software. I suspect other commerical vendors will have a similar attitude (particularly if they know about FreeBSD's linux emulation). -- 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