From: Will Senn <will.senn@gmail.com>
To: segaloco <segaloco@protonmail.com>, Andrew Lynch <lynchaj@yahoo.com>
Cc: TUHS Main List <tuhs@tuhs.org>
Subject: [TUHS] Re: most direct Unix descendant
Date: Wed, 5 Jun 2024 12:51:19 -0500 [thread overview]
Message-ID: <fe741856-0274-4a25-98b8-8823aad90d00@gmail.com> (raw)
In-Reply-To: <nQ2RmROKyKxZyHyYlq2KnSv3QXnzrOGYEzbnLgUlEQmH8E6mgGAgQVeqS37AHvsik7YKLWrF9X9X0kgDKpSk5LYnYEMdnrXFy6NXPjqIsXA=@protonmail.com>
On 6/5/24 12:34 PM, segaloco via TUHS wrote:
> On Wednesday, June 5th, 2024 at 3:17 AM, Andrew Lynch via TUHS <tuhs@tuhs.org> wrote:
>
>> Hi
>>
>> Out of curiosity, what would be considered the most direct descendent of Unix available today?
>>
>> ...
>>
>> Thanks, Andrew Lynch
> snip
> Given this, my humble opinion (which again this sort of thing I believe is largely a philosophical matter of opinion...) is that the BSD line captures the spirit of Research UNIX much more than System V does, while System V retains much more of the source code lineage of what most folks would consider a "pure" UNIX. Of course all of this too is predicated on treating V7 (really 32V...) as that central point of divergence.
When I saw this thread appear, I was of two minds about it, but this
lines up with where my thoughts were headed. I've done a lot of delving
into the v6/v7 environments over the last 10 years or so and it feels
much closer in kinship to BSD derivatives than to SysV... source code
lineages aside. Also, I get more mileage out of my BSD books and docs
than those treating SysV. I'd vote for *BSD as sticking closest to the
unix way, if there is still such a thing... I say this as I just typed
'kldload linux64' into freebsd's terminal so I could run sublime
alongside nvi... sometimes I wish I was a purist, but I'm way too fond
of experimentation :).
Will
next prev parent reply other threads:[~2024-06-05 17:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1324869037.1755756.1717582639424.ref@mail.yahoo.com>
2024-06-05 10:17 ` [TUHS] " Andrew Lynch via TUHS
2024-06-05 10:51 ` [TUHS] " Andrew Warkentin
2024-06-05 13:46 ` Andrew Lynch via TUHS
2024-06-05 17:34 ` segaloco via TUHS
2024-06-05 17:51 ` Will Senn [this message]
2024-06-05 18:02 ` ron minnich
2024-06-05 23:07 ` Andrew Warkentin
2024-06-05 18:22 ` Jeffrey Joshua Rollin
2024-06-05 18:41 ` Warner Losh
2024-06-05 19:17 ` Jeffrey Joshua Rollin
2024-06-06 9:55 ` Ralph Corderoy
2024-06-06 19:49 ` Steffen Nurpmeso
2024-06-09 8:00 ` Ed Bradford
2024-06-30 11:05 ` [TUHS] syscalls, records in pipe [was: Re: most direct Unix descendant] Tomasz Rola via TUHS
2024-06-30 11:11 ` [TUHS] " Tomasz Rola via TUHS
2024-06-09 11:34 [TUHS] Re: most direct Unix descendant Douglas McIlroy
2024-06-09 11:59 ` A. P. Garcia
2024-06-09 12:31 ` Ralph Corderoy
2024-06-09 14:06 ` A. P. Garcia
2024-06-10 5:13 ` Ed Bradford
2024-06-10 5:25 ` G. Branden Robinson
2024-06-10 8:39 ` Dave Horsfall
2024-06-10 9:36 ` Marc Donner
2024-06-10 19:40 ` Steffen Nurpmeso
2024-06-10 20:09 ` Marc Donner
2024-06-10 20:19 ` Steffen Nurpmeso
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=fe741856-0274-4a25-98b8-8823aad90d00@gmail.com \
--to=will.senn@gmail.com \
--cc=lynchaj@yahoo.com \
--cc=segaloco@protonmail.com \
--cc=tuhs@tuhs.org \
/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).