The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: wobblygong@gmail.com (Wesley Parish)
Subject: [TUHS] Windows Notepad to support Unix line endings
Date: Fri, 11 May 2018 11:13:35 +1200	[thread overview]
Message-ID: <CACNPpeYHcUd4uRw9Xrw4pcJksEv1e6v0WGFX6Pf82NieWQxAcg@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2Og3sa9quiBezk4H939LwKFQpwD2sPWkVijPkXZYPjPAg@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2136 bytes --]

That was the impression I got from the various Unix and UNIX(TM)
documents that Groklaw discussed during The SCO Group's Foot-In-Mouth
case against Linux, IBM and The Rest Of The World.

Wesley Parish

On 5/11/18, Clem Cole <clemc at ccc.com> wrote:
> below...
>
> On Thu, May 10, 2018 at 5:09 PM, Dave Horsfall <dave at horsfall.org> wrote:
>
>> LINUX Is Not UniX.
>
>
> A few thoughts ...
> 1.) Be careful - the US courts have said that *UNIX is not a code base or
> any one implementation - it's a set of ideas​.*  That is the whole basis of
> the BSDi case and why in the end AT&T lost.  It WAS their ideas, but it
> just can not be a trade secret.  If AT&T had been able to claim it as a
> trade secret, Linux, Minix, Coherent *et al *would have been in violation
> too (which is why it was so silly to sue them).
> 2.) I believe that Linux is the current popular implementation of UNIX.
>  Yes it hurts my fingers by some of the changes, but it looks, smells and
> quacks like duck.   Linux uses the AT&T IP -- the published ideas.  All of
> us on this list, just like Linus, are 'mentally contaminated' by Ken and
> Dennis's core idea.   That's the basic fact and it not going away.
> 3.) Claiming LINUX Is Not UniX is like saying FORTRAN95 is not FORTRAN
> because its not like F2, F4, F77 etc...   I'd like to point out that in
> fact, modern FTN compilers can pretty much accept the old code - which
> pretty darned amazing (and thankfully I'm not a compiler writer).    But
> for guys like me in the HPC business, FORTRAN is still useful, as it pays
> our salary.   The thing we have to remember is that the target matured, and
> moved on.  It aint quite like it was and there is no going back.
>
> I think that's the point and Ted and Larry have suggested so many times.
>  Linux took the token from AT&T, BSD, Solaris, *etc*... and moved it.  Some
> of us, myself included, find many of the changes gratuitous and a PITA, but
> that is the price of progress. I remember that a lot of people at AT&T
> thought the BSD changes were gratuitous too.   So Linux is the 3rd path of
> the UNIX heritage.
>
> Clem
> ᐧ
> ᐧ
>


  parent reply	other threads:[~2018-05-10 23:13 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-09 20:15 Robert Diamond
2018-05-09 21:54 ` Grant Taylor
2018-05-09 21:57   ` David Arnold
2018-05-09 22:23     ` Grant Taylor
2018-05-09 23:08       ` Nemo
2018-05-09 23:10         ` Nemo
2018-05-09 23:28         ` Grant Taylor
2018-05-10 13:34           ` Nemo
2018-05-10 15:24             ` Grant Taylor
2018-05-11  2:16       ` David Arnold
2018-05-11  2:21         ` Grant Taylor
2018-05-09 22:30   ` Arthur Krewat
2018-05-09 22:54     ` Larry McVoy
2018-05-10 21:09     ` Dave Horsfall
2018-05-10 21:21       ` arnold
2018-05-10 21:47       ` Harald Arnesen
2018-05-10 21:49       ` Clem Cole
2018-05-10 22:59         ` Grant Taylor
2018-05-11  0:35           ` Warner Losh
2018-05-11  1:29           ` Theodore Y. Ts'o
2018-05-11 13:09             ` Clem Cole
2018-05-10 23:13         ` Wesley Parish [this message]
2018-05-09 22:41   ` Tim Bradshaw
2018-05-10  0:32 Norman Wilson
2018-05-10  1:10 ` Grant Taylor
2018-05-12 11:51 Rudi Blom

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=CACNPpeYHcUd4uRw9Xrw4pcJksEv1e6v0WGFX6Pf82NieWQxAcg@mail.gmail.com \
    --to=wobblygong@gmail.com \
    /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).