From: Larry McVoy <lm@mcvoy.com>
To: Warner Losh <imp@bsdimp.com>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: AIX moved into maintainance mode
Date: Thu, 19 Jan 2023 07:23:57 -0800 [thread overview]
Message-ID: <20230119152357.GB626@mcvoy.com> (raw)
In-Reply-To: <CANCZdfqwEaKtfAyjE+2eQtEsKOjn0xtXgx-6KT_V0WgGC3YDGg@mail.gmail.com>
On Thu, Jan 19, 2023 at 08:20:16AM -0700, Warner Losh wrote:
> On Thu, Jan 19, 2023 at 8:04 AM Larry McVoy <lm@mcvoy.com> wrote:
>
> > I had already been using Linux for a while by then I believe. I used
> > it before it had networking.
> >
> > Pretty early on I got to be friends with Linus and was really impressed
> > with his leadership. That's what sold me on Linux, he was the thing
> > that was missing in the BSD world. If someone like him had appeared
> > and unified the BSD world I think we'd all be running BSD.
> >
>
> By the time even 4.3BSD was released, there were dozens of people that
> could work on the kernel at a high level of skill. There was no one person
> who created it who could have the gravitas to pull that off. Let alone a
> decade later when it was freed up, by then there were hundreds. The
> dynamics of the situation were quite different: Linus always was in charge
> because he wrote the whole thing... BSD was a victim of it's own success
> in the 80s and 90s in a way...
Linus was in charge because he started it. At least 30 years ago I said
"He's good programmer, a good architect, and a good manager. I've never
seen that in one person before".
He most certainly did not write the whole thing but he decided what went
in when. He's quite good at that.
next prev parent reply other threads:[~2023-01-19 15:24 UTC|newest]
Thread overview: 101+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 9:43 [TUHS] " arnold
2023-01-18 14:46 ` [TUHS] " Phil Budne
2023-01-18 14:55 ` Ralph Corderoy
2023-01-19 14:42 ` Liam Proven
2023-01-19 15:04 ` Warner Losh
2023-01-19 15:15 ` Liam Proven
2023-01-18 15:13 ` arnold
2023-01-18 15:14 ` Larry McVoy
2023-01-18 16:10 ` segaloco via TUHS
2023-01-18 16:19 ` Stuff Received
2023-01-18 16:19 ` Larry McVoy
2023-01-18 16:27 ` [TUHS] Maintenance mode on AIX Ron Natalie
2023-01-18 16:38 ` [TUHS] " Larry McVoy
2023-01-18 16:59 ` Clem Cole
2023-01-18 17:08 ` segaloco via TUHS
2023-01-18 17:21 ` Will Senn
2023-01-18 19:50 ` David Barto
2023-01-19 14:25 ` Liam Proven
2023-01-18 20:34 ` Arno Griffioen via TUHS
2023-01-18 20:50 ` Brad Spencer
2023-01-18 16:36 ` [TUHS] Re: AIX moved into maintainance mode Will Senn
2023-01-18 16:42 ` Larry McVoy
2023-01-18 16:57 ` Will Senn
2023-01-18 17:16 ` Larry McVoy
2023-01-18 17:25 ` Will Senn
2023-01-18 21:09 ` segaloco via TUHS
2023-01-18 21:18 ` Kevin Bowling
2023-01-19 1:13 ` Joseph Holsten
2023-01-19 15:04 ` Liam Proven
2023-01-18 19:25 ` Dave Horsfall
2023-01-19 15:02 ` Liam Proven
2023-01-19 15:12 ` arnold
2023-01-19 17:46 ` Steffen Nurpmeso
2023-01-19 18:24 ` Doug McIntyre
2023-01-19 19:44 ` Chet Ramey
2023-01-20 13:09 ` Liam Proven
2023-01-20 14:37 ` Harald Arnesen
2023-01-18 16:48 ` segaloco via TUHS
2023-01-19 0:54 ` Adam Thornton
2023-01-19 1:09 ` Larry McVoy
2023-01-20 18:38 ` Theodore Ts'o
2023-01-20 18:57 ` Dan Cross
2023-01-20 19:48 ` John Cowan
2023-01-20 20:04 ` Dan Cross
2023-01-20 19:08 ` Kevin Bowling
2023-01-19 1:17 ` Marc Donner
2023-01-19 1:26 ` Joseph Holsten
2023-01-20 15:53 ` Marc Donner
2023-01-19 14:45 ` Liam Proven
2023-01-19 15:05 ` Dan Cross
2023-01-19 16:59 ` Bakul Shah
2023-01-19 19:33 ` [TUHS] The death of general purpose computers, was - " Will Senn
2023-01-19 20:09 ` [TUHS] " segaloco via TUHS
2023-01-19 20:59 ` Rich Morin
2023-01-19 21:11 ` segaloco via TUHS
2023-01-20 13:30 ` Liam Proven
2023-01-20 15:51 ` segaloco via TUHS
2023-01-20 15:56 ` Rich Morin
2023-01-20 16:24 ` segaloco via TUHS
2023-01-20 18:21 ` G. Branden Robinson
2023-01-20 18:33 ` segaloco via TUHS
2023-01-18 18:58 ` [TUHS] " Steve Nickolas
2023-01-19 8:02 ` arnold
2023-01-19 15:04 ` Larry McVoy
2023-01-19 15:20 ` Warner Losh
2023-01-19 15:23 ` Larry McVoy [this message]
2023-01-19 16:40 ` Dan Cross
2023-01-19 16:58 ` Warner Losh
2023-01-19 23:16 ` Theodore Ts'o
2023-01-20 0:37 ` Warner Losh
2023-01-20 1:22 ` Steve Nickolas
2023-01-19 17:02 ` Steve Nickolas
2023-01-19 17:19 ` Adam Thornton
2023-01-19 18:22 ` segaloco via TUHS
2023-01-19 19:07 ` Kevin Bowling
2023-01-19 21:08 ` Joseph Holsten
2023-01-19 20:01 ` [TUHS] The era of general purpose computing (Re: " Bakul Shah
2023-01-19 22:23 ` [TUHS] " Luther Johnson
2023-01-20 1:10 ` John Cowan
2023-01-20 1:15 ` Luther Johnson
2023-01-21 18:12 ` arnold
2023-01-21 18:43 ` Luther Johnson
2023-01-19 22:29 ` Rich Salz
2023-01-19 22:39 ` Luther Johnson
2023-01-19 22:41 ` Luther Johnson
2023-01-19 22:40 ` Jon Steinhart
2023-01-19 23:24 ` segaloco via TUHS
2023-01-19 23:44 ` Rich Salz
2023-01-19 23:51 ` segaloco via TUHS
2023-01-20 0:20 ` [TUHS] owner maintenance (Re: " Charles H Sauer (he/him)
2023-01-20 0:36 ` [TUHS] " Larry McVoy
2023-01-20 0:47 ` [TUHS] " Yeechang Lee
2023-01-20 0:55 ` George Michaelson
2023-01-20 1:05 ` Rich Salz
2023-01-20 1:10 ` George Michaelson
2023-01-20 2:27 ` Dan Cross
2023-01-18 21:20 ` [TUHS] " Theodore Ts'o
2023-01-18 21:27 ` Kevin Bowling
2023-01-19 2:17 ` Jim Carpenter
2023-01-19 21:15 ` Will Senn
2023-01-19 21:34 ` Drew Diver
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=20230119152357.GB626@mcvoy.com \
--to=lm@mcvoy.com \
--cc=imp@bsdimp.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).