From: Eric Weigle <ehw@lanl.gov>
To: "Joseph D. Wagner" <wagnerjd@prodigy.net>
Cc: "'Nicholas Berry'" <nikberry@med.umich.edu>,
wa1hco@adelphia.net, shanehelms@eircom.net, EdV@macrolink.com,
linux-kernel@vger.kernel.org
Subject: Re: is KERNEL developement finished, yet ???
Date: Thu, 5 Dec 2002 08:44:41 -0700 [thread overview]
Message-ID: <20021205154441.GO10934@lanl.gov> (raw)
In-Reply-To: <000401c29c71$5fb52620$43833841@joe>
[-- Attachment #1: Type: text/plain, Size: 1108 bytes --]
>>>Unix (and Linux) developers are far too concerned with clinging to the
>>>30-year-old outdated POSIX standard, which creates numerous problems when
>>>trying to advance new features.
>>Er, 16-year-old maybe?
>Wow! I thought I really knew what I was talking about, but you've really
>convinced me to see things you're way!
>[snip]
"In early 1985, the /usr/group committee was merged with the newly formed
IEEE POSIX Working Group (POSIX stands for Portable Operating Systems
for Computing Environments) and the /usr/group standard was adopted as a
first draft."
UN*Xen were around for 15 years before anybody was brave (or stupid :)
enough to really standardize. The first drafts of these standards are only
16-18 years old.
http://www.acm.org/crossroads/xrds1-3/unix-standards.html
--
------------------------------------------------------------
Eric H. Weigle -- http://public.lanl.gov/ehw/
"They that can give up essential liberty to obtain a little
temporary safety deserve neither" -- Benjamin Franklin
------------------------------------------------------------
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-12-05 15:38 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <sdef2367.029@mail-02.med.umich.edu>
2002-12-05 15:17 ` is KERNEL developement finished, yet ??? Joseph D. Wagner
2002-12-05 15:38 ` Dave Jones
2002-12-05 15:44 ` Eric Weigle [this message]
[not found] <sdef301b.011@mail-01.med.umich.edu>
2002-12-05 16:36 ` Joseph D. Wagner
2002-12-06 3:29 ` Keith Adamson
2002-12-05 14:58 Nicholas Berry
-- strict thread matches above, loose matches on Subject: below --
2002-12-05 2:00 Ed Vance
2002-12-05 12:24 ` Shane Helms
2002-12-05 12:54 ` Joseph D. Wagner
2002-12-05 13:15 ` Andreas Schwab
2002-12-05 18:07 ` Linus Torvalds
2002-12-05 19:52 ` Shane Helms
2002-12-05 20:03 ` Linus Torvalds
2002-12-07 20:34 ` Kai Henningsen
2002-12-05 18:09 ` Alan Cox
2002-12-05 17:47 ` yodaiken
2002-12-05 19:08 ` John Bradford
2002-12-06 6:15 ` Joseph D. Wagner
2002-12-06 6:30 ` John Alvord
2002-12-06 9:48 ` Alvaro Lopes
2002-12-07 20:43 ` Kai Henningsen
2002-12-07 20:39 ` Kai Henningsen
2002-12-09 14:08 ` Jesse Pollard
2002-12-10 0:26 ` H. Peter Anvin
2002-12-05 14:33 ` Mikael Pettersson
2002-12-03 13:03 cs driver SANTHOSH K
2002-12-04 15:26 ` is KERNEL developement finished, yet ??? Shane Helms
2002-12-04 17:01 ` Joseph D. Wagner
2002-12-04 18:38 ` Alan Cox
2002-12-04 18:07 ` Richard B. Tilley (Brad)
2002-12-04 18:21 ` Richard B. Johnson
2002-12-04 18:39 ` Erik Andersen
2002-12-05 16:59 ` Bill Davidsen
2002-12-05 0:27 ` jeff millar
2002-12-05 23:55 ` Frank van Maarseveen
2002-12-06 0:24 ` Shane Helms
2002-12-06 3:00 ` jeff millar
2002-12-06 3:36 ` Miles Bader
2002-12-06 8:55 ` Helge Hafting
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=20021205154441.GO10934@lanl.gov \
--to=ehw@lanl.gov \
--cc=EdV@macrolink.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nikberry@med.umich.edu \
--cc=shanehelms@eircom.net \
--cc=wa1hco@adelphia.net \
--cc=wagnerjd@prodigy.net \
/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