The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Greg 'groggy' Lehey" <grog@lemis.com>
To: Larry McVoy <lm@mcvoy.com>
Cc: "Jeffry R. Abramson" <jeffryrabramson@gmail.com>,
	Ben Kallus <benjamin.p.kallus.gr@dartmouth.edu>,
	"tuhs@tuhs.org" <tuhs@tuhs.org>
Subject: [TUHS] FreeBSD kernel not OK? (was: What do you currently use for your primary OS at home?)
Date: Sat, 9 Mar 2024 10:18:00 +1100	[thread overview]
Message-ID: <ZeucqFofhHM1g7hN@hydra.lemis.com> (raw)
In-Reply-To: <20240308034259.GS2252@mcvoy.com>

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

On Thursday,  7 March 2024 at 19:42:59 -0800, Larry McVoy wrote:
> On Thu, Mar 07, 2024 at 08:15:43PM -0500, Jeffry R. Abramson wrote:
>> On Thu, 2024-03-07 at 13:08 +0000, Ben Kallus wrote:
>
> FreeBSD and me got reconnected when Netflix wanted to hire me a
> while back.  While the kernel may be OK (it's not, ask me how I
> know, I walked the code)

OK, I'm asking.  I've been there too, and I don't see any obvious and
serious deficiencies.

> FreeBSD is stuck in the 1980s.  Raise your hand if you have
> installed FreeBSD in the last 20 years.

/me raises.

> That "UI" for partitioning the disks, so arcane.  The whole install
> experience is _awful_.

Agreed, some of the installation tools could do with improvement.  But
how often do you install FreeBSD?  As I have already noted, I've been
using it for 25 years or so, and in the early days I held classes on
installing FreeBSD.  By about 2000 they seemed a little pointless.  In
general, once it's there, it's there.  You seem to be emphasizing the
wrong part of the system.

> SunOS was a bug fixed BSD, so I really loved BSD.  But BSD is so
> dead it is not even funny.  Linux is light years ahead.  Here is an
> example from more than 20 years ago.  I was installing RedHat Linux
> and the machine I was installing on didn't have a mouse.  The
> installer was graphical and it was just easier to tab through the
> options than go find a mouse.

Again, installation.  How about *using* the system?  And why should
you need a *mouse* to install software?

Greg
--
Sent from my desktop computer.
Finger grog@lemis.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  parent reply	other threads:[~2024-03-08 23:18 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-07  6:47 [TUHS] What do you currently use for your primary OS at home? Jeffry R. Abramson
2024-03-07  9:09 ` [TUHS] " arnold
2024-03-07 11:04   ` Marc Donner
2024-03-07 13:08 ` Ben Kallus
2024-03-07 13:16   ` Ralph Corderoy
2024-03-08  1:15   ` Jeffry R. Abramson
2024-03-08  3:42     ` Larry McVoy
2024-03-08  3:57       ` Luther Johnson
2024-03-08  3:58         ` Luther Johnson
2024-03-08  6:28       ` Dave Horsfall
2024-03-08 11:23         ` Steve Nickolas
2024-03-08 14:42         ` Larry McVoy
2024-03-08 15:01           ` Marc Donner
2024-03-08 15:36             ` Clem Cole
2024-03-08 15:42               ` Larry McVoy
2024-03-08 15:45                 ` Warner Losh
2024-03-08 15:50                   ` Will Senn
2024-03-08 15:28       ` Warner Losh
2024-03-08 23:18       ` Greg 'groggy' Lehey [this message]
2024-03-08 23:43         ` [TUHS] Re: FreeBSD kernel not OK? (was: What do you currently use for your primary OS at home?) Will Senn
2024-03-08 23:50           ` John Floren via TUHS
2024-03-08 23:57             ` Michael Huff
2024-03-09  0:16               ` [TUHS] Re: FreeBSD kernel not OK? Alexis
2024-03-09 17:25                 ` Theodore Ts'o
2024-03-09  9:53               ` Harald Arnesen via TUHS
2024-03-09 15:34                 ` Gregg Levine
2024-03-08 23:45         ` [TUHS] Re: FreeBSD kernel not OK? (was: What do you currently use for your primary OS at home?) segaloco via TUHS
2024-03-07 13:31 ` [TUHS] Re: What do you currently use for your primary OS at home? Brantley Coile
2024-03-07 14:23 ` Larry McVoy
2024-03-07 14:45   ` Michael Usher via TUHS
2024-03-07 14:38 ` Steve Nickolas
2024-03-07 15:40 ` Clem Cole
2024-03-07 15:56   ` Thomas Kellar
2024-03-07 16:12   ` Marc Rochkind
2024-03-07 16:33     ` ron minnich
2024-03-07 18:32       ` Marc Rochkind
2024-03-07 16:03 ` Jim Capp
2024-03-07 20:25 ` Dave Horsfall
2024-03-07 21:21 ` Adam Thornton
2024-03-07 22:25   ` Luther Johnson
2024-03-07 22:20 ` Åke Nordin
2024-03-07 22:32 ` Mike Markowski
2024-03-07 23:58   ` Will Senn
2024-03-08 16:23 ` Stuff Received

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=ZeucqFofhHM1g7hN@hydra.lemis.com \
    --to=grog@lemis.com \
    --cc=benjamin.p.kallus.gr@dartmouth.edu \
    --cc=jeffryrabramson@gmail.com \
    --cc=lm@mcvoy.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).