The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Adam Thornton <athornton@gmail.com>
To: "Theodore Y. Ts'o" <tytso@mit.edu>,
	The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] [COFF] 386BSD released
Date: Thu, 15 Jul 2021 12:49:07 -0700	[thread overview]
Message-ID: <CAP2nic0qY4HrFTUYj0qwr=eney-re6Gn2O=0S23d6jwvOL_O+g@mail.gmail.com> (raw)
In-Reply-To: <YPCNnL4TLkLWqmFa@mit.edu>

[-- Attachment #1: Type: text/plain, Size: 1317 bytes --]

The thing which Linux has managed to achieve, however, is the fact
> that there is a large and diverse base of corporate contributions.
> That to me is what makes the Linux model so interesting, and has been
> a reason for its long-term sustainability.
>
>
Although from a somewhat different perspective, it's also why the Linux
kernel syscall interface is so unruly, right?

You've got your...some number in the small dozens of common syscalls, which
are already present for the most part in v6 or v7.  These are the ones I,
at least, think of when I think of the Unix manual, section 2.

And then you've got all the other calls added in by (usually) this database
vendor or that storage vendor or the other display adapter vendor to make
their stuff work more efficiently.

And obviously there's a tradeoff there.  Elegance departs, and you've
probably introduced some security risk because these syscalls are not
nearly as well-exercised as the common ones, but on the other hand you have
these large companies paying to work on the kernel, and you have them
supporting their product on Linux systems because the system can be bent
into accommodating them more easily, and it will run better there than on
OSes where they don't get to introduce features that benefit their
products, which further drives adoption.

[-- Attachment #2: Type: text/html, Size: 1681 bytes --]

  reply	other threads:[~2021-07-15 19:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-15  2:21 [TUHS] " Douglas McIlroy
2021-07-15  2:41 ` Adam Thornton
2021-07-15 15:07 ` Clem Cole
2021-07-15 19:33   ` [TUHS] [COFF] " Theodore Y. Ts'o
2021-07-15 19:49     ` Adam Thornton [this message]
2021-07-15 20:29       ` Andy Kosela
2021-07-16  2:22       ` Theodore Y. Ts'o
2021-07-15 20:30     ` Clem Cole
2021-07-16  1:58       ` Theodore Y. Ts'o
2021-07-16  2:14         ` George Michaelson
2021-07-15 23:02     ` joe mcguckin
  -- strict thread matches above, loose matches on Subject: below --
2021-07-13 22:28 [TUHS] " Dave Horsfall
2021-07-14  7:54 ` Michael Kjörling
2021-07-14  8:19   ` Angus Robinson
2021-07-14 15:01     ` Clem Cole
2021-07-14 17:40       ` [TUHS] [COFF] " Theodore Y. Ts'o
2021-07-14 17:50         ` Larry McVoy
2021-07-14 18:28         ` Clem Cole

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='CAP2nic0qY4HrFTUYj0qwr=eney-re6Gn2O=0S23d6jwvOL_O+g@mail.gmail.com' \
    --to=athornton@gmail.com \
    --cc=tuhs@tuhs.org \
    --cc=tytso@mit.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).