9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Sam <sah@softcardsystems.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] UN to fund linux for the 3rd world
Date: Thu,  2 Sep 2004 10:11:57 -0500	[thread overview]
Message-ID: <Pine.LNX.4.60.0409020918590.7729@athena> (raw)
In-Reply-To: <200409020940.i829e219008666@skeeve.com>

> And the Linux dists come with *tons* of day-to-day useful software that
> I would have to go out and find and build were I running a commercial
> Unix system.

FreeBSD has linux binary compatibility.  Most of that "useful"
software is in the ports collection.

My affection for bsd over linux is two-fold.  Firstly, the
kernel is a mess.  If you've ever been on the linux kernel
mailing list for even a day you see that "development" is
nothing more than a thousand cooks tweaking concoctions to
throw into the stew.  You'll never see a 'design and
implementation' book for linux because you can't exposit
*how* the code works as there's almost no design.

This is my experience with the 2.4 kernel.  FreeBSD isn't
much better in places, but there are sweet spots.  I haven't
even cracked OpenBSD yet, which according to Geoff is
the cleanest of the lot.

Second, linux developers really want an ignorant user base.
The entire userland approach is to obfuscate hypothetical
complexity behind a new program and a dizzying array of
switches.  The ports collection is a simple example:

% cd /usr/ports/astro/sunclock
% make install
... (downloads and builds program)
% (done)

Compare that to the rpm -Uv -waitdoihaveallthedependencies
or even gentoo's attempted photocopy of the ports system
"portage" where you do everything behind an emerge program.
They take the learning curve out of one place, put it
in another, and call it an improvement because they have
something to put on sourceforge.  blech.

Both in the kernel and userland linux is all about
"doing things to you" instead of "doing things for you."

And every time I find a "new" program that won't write its
output to stdout I puke all over my desk.  Right after
flushing my TLBs a hundred times for good measure.

Sam


  parent reply	other threads:[~2004-09-02 15:11 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-02  9:40 Aharon Robbins
2004-09-02  9:44 ` Dick Davies
2004-09-02 10:11 ` lucio
2004-09-02 10:52   ` George Michaelson
2004-09-02 11:21     ` lucio
2004-09-02 18:32       ` Jack Johnson
2004-09-02 22:58         ` Adrian Tritschler
2004-09-02 15:11 ` Sam [this message]
2004-09-02 19:51   ` boyd, rounin
2004-09-02 22:06 ` geoff
2004-09-03  2:33 ` Dan Cross
     [not found] <Pine.LNX.4.44.0409031316170.22793-100000@maxroach.lanl.gov>
2004-09-03 19:53 ` Charles Forsyth
2004-09-03 21:11   ` dvd
2004-09-03 20:48 ` dvd
2004-09-03 20:52   ` ron minnich
2004-09-03 21:15     ` dvd
  -- strict thread matches above, loose matches on Subject: below --
2004-09-02 10:37 Aharon Robbins
2004-09-02 11:10 ` lucio
2004-09-02 18:54   ` dvd
2004-09-02 19:20     ` Boris Maryshev
2004-09-02 21:40     ` Charles Forsyth
2004-09-02 21:55       ` Boris Maryshev
2004-09-03  5:20       ` dvd
2004-09-03  6:22         ` lucio
2004-09-03  7:49         ` Charles Forsyth
2004-09-03 17:48           ` Jack Johnson
2004-09-03 17:52             ` ron minnich
2004-09-03 18:22               ` dvd
2004-09-01 14:48 boyd, rounin
2004-09-01 17:57 ` Jack Johnson
2004-09-01 17:59   ` boyd, rounin
2004-09-01 20:39     ` Tim Newsham
2004-09-01 21:16       ` boyd, rounin
2004-09-01 21:45         ` C H Forsyth
2004-09-02  3:24           ` Dan Cross
2004-09-02  3:31             ` George Michaelson
2004-09-02  4:24               ` Dan Cross
2004-09-02  5:15                 ` Jeff Sickel
2004-09-02  5:38                   ` andrey mirtchovski
2004-09-02  6:24                     ` Zigor Salvador
2004-09-03  2:10                   ` Dan Cross
2004-09-02 19:27                 ` boyd, rounin
2004-09-02 20:38                   ` Charles Forsyth
2004-09-02 22:44                     ` Adrian Tritschler
2004-09-03  3:00                   ` Dan Cross
2004-09-03  3:01                     ` boyd, rounin
2004-09-02  5:03               ` Skip Tavakkolian
2004-09-02  5:13                 ` George Michaelson
2004-09-02  9:10             ` Dick Davies
2004-09-03  2:13               ` Dan Cross
2004-09-03  2:38                 ` George Michaelson
2004-09-05  0:30                 ` Dick Davies
2004-09-05  0:31                   ` boyd, rounin
2004-09-05  1:11                   ` Jack Johnson
2004-09-05  2:50                     ` boyd, rounin
2004-09-02 14:26             ` ron minnich
2004-09-02 21:48               ` Wes Kussmaul
2004-09-02 22:09                 ` andrey mirtchovski
2004-09-03  0:21                   ` Wes Kussmaul
2004-09-03  0:40                     ` andrey mirtchovski
2004-09-03  4:39                   ` Jack Johnson
2004-09-03  2:53               ` Dan Cross

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=Pine.LNX.4.60.0409020918590.7729@athena \
    --to=sah@softcardsystems.com \
    --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).