9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lyndon Nerenberg <lyndon@orthanc.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: configure misery
Date: Sun, 16 Nov 2003 15:38:01 -0700	[thread overview]
Message-ID: <2147483647.1068997081@[192.168.42.6]> (raw)
In-Reply-To: <E1ALUjM-0006XR-Ba@t40.swtch.com>

--On Sunday, November 16, 2003 4:46 PM -0500 Russ Cox <rsc@swtch.com>
wrote:

> I'm not aware that any of the other BSDs are itching to
> get rid of all their GNU software. Judging from the CVS and other
> logs, it appears that FreeBSD switched to BWK awk mainly because gawk
> had problems on the Sparc64.

FreeBSD would like to replace GPL code with BSD licensed code, *when it
it practical to do so*. The (well, a) main reason for this is to make
life easier for the embedded systems folks, who need to worry about GPL
taint requiring them make their proprietary source available. There's
much less zealotry about this in the FreeBSD camp vs. the OpenBSD
folks. The reasons for replacing awk, in no particular order, were:
size of the gawk code, license, and compatibility with traditional awk.
The mailing lists describe the reasoning better than CVS does.

> Finally (and this is more directed at Lyndon's post than yours) not
> all GNU software is crap.  Some of it is quite good, and I believe
> that gawk and groff are examples of this.

I wasn't (necessarily) implying that. My biggest concern with GNU code
(and this is not a GPL issue) is the massive feature-itis in the
traditional UNIX tools. It's fine for GNU tools to grow new features if
that's what they want, but when those tools are shipped as replacements
for the traditional UNIX ones, we start seeing lots of portability
problems. gawk is one example of this. When it's installed and invoked
as awk it doesn't disable the GNU extensions. This results in awk
scripts that rely on gawk-specific features, and in most cases the
script author doesn't even realize this is happening. bash masquerading
as sh is another culprit here. I've spent a lot of time over the years
fixing portability bugs in software that was developed on GNUish
systems, but had to run on traditional UNIX or POSIX environments. The
only real fix for this is for the world to acknowledge that Linux just
ain't UNIX, and let's all stop pretending it is.

--lyndon



  parent reply	other threads:[~2003-11-16 22:38 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-16  8:04 Aharon Robbins
2003-11-16  8:37 ` Geoff Collyer
2003-11-16 14:46   ` Charles Forsyth
2003-11-16  9:53 ` Bruce Ellis
2003-11-16 19:11 ` Lyndon Nerenberg
2003-11-16 19:32   ` andrey mirtchovski
2003-11-16 21:43     ` Dan Cross
2003-11-16 23:37       ` Lyndon Nerenberg
2003-11-17  0:04         ` mirtchov
2003-11-17  0:04           ` boyd, rounin
2003-11-17  3:18         ` Dan Cross
2003-11-17  3:28           ` boyd, rounin
2003-11-16 21:46     ` Russ Cox
2003-11-16 22:24       ` mirtchov
2003-11-16 22:47         ` Russ Cox
2003-11-17  0:38         ` Mike Haertel
2003-11-16 22:38       ` Lyndon Nerenberg [this message]
2003-11-16 22:41         ` boyd, rounin
2003-11-18 12:54         ` Aharon Robbins
2003-11-18 14:11           ` Russ Cox
2003-11-18 14:55             ` Joel Salomon
2003-11-17  0:24       ` Enache Adrian
2003-11-17 12:16         ` Aharon Robbins
2003-11-17 23:16           ` Taj Khattra
2003-11-16 19:58   ` boyd, rounin
2003-11-17  0:30     ` [9fans] mmap (was configure misery) Geoff Collyer
2003-11-17  0:29       ` boyd, rounin
2003-11-17 12:25   ` [9fans] Re: configure misery Aharon Robbins
2003-11-17  0:42 ` John Stalker
2003-11-17 12:28   ` Aharon Robbins
2003-11-17 12:42     ` Lucio De Re
2003-11-17 12:53       ` Lucio De Re
2003-11-17 13:43         ` Aharon Robbins
2003-11-17 15:06           ` mirtchov
2003-11-17 15:35           ` David Presotto
2003-11-17 16:31       ` John Stalker
2003-11-17 17:19         ` Aharon Robbins
2004-01-30 15:30 [9fans] Re: [hangar18-general] Frustration Jim Choate
2004-02-03 17:11 ` [9fans] Re: configure misery rog
2004-02-04 16:48   ` Jim Choate
2004-02-03  3:49 Li Yi
2004-02-03 11:30 ` Aharon Robbins
2004-02-03 13:32   ` a
2004-02-03 15:34     ` Jim Choate
2004-02-03 16:29       ` a
2004-02-03 14:18   ` andrey mirtchovski
2004-02-03 15:36     ` Jim Choate
2004-02-03 16:32       ` boyd, rounin
2004-02-03 16:42         ` Jim Choate
2004-02-03 23:53       ` David Presotto
2004-02-04  8:13     ` Aharon Robbins
2004-02-03 15:33   ` Jim Choate
2004-02-03 16:27     ` a
2004-02-03 16:44       ` Jim Choate
2004-02-03 16:53         ` andrey mirtchovski
2004-02-04 16:45           ` Jim Choate
2004-02-03 17:01         ` Wes Kussmaul
2004-02-04 17:47 Spamm Trapp

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='2147483647.1068997081@[192.168.42.6]' \
    --to=lyndon@orthanc.ca \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).