The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.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] Re: What do you currently use for your primary OS at home?
Date: Fri, 8 Mar 2024 08:28:07 -0700	[thread overview]
Message-ID: <CANCZdfqsqddpdNmSiA3va5Rw_e2NAR=0=ThjysCg+SwncFq1uQ@mail.gmail.com> (raw)
In-Reply-To: <20240308034259.GS2252@mcvoy.com>

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

On Thu, Mar 7, 2024 at 8:43 PM Larry McVoy <lm@mcvoy.com> 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:
> > > What about Linux is too bloated, in your opinion? Is it the kernel
> > > itself, or the programs that often go with it? If it's the former,
> > > OpenBSD may be a good choice. If it's the latter, I would look into a
> > > minimal distribution (e.g. Alpine, Void, arguably Arch) paired with a
> > > tiling window manager (e.g. Sway, dwm).
> > >
> > > -Ben
> >
> > The bloated part? IMHO I would say systemd, pulseaudio, NetworkManager,
> > KDE, GNOME, Cinnamon. ??Even though Cinnamon is the desktop I use. ??My
> > wife's laptop finally died ie. Windows got so crudded up with stuff
> > that Outlook couldn't send mail and I just refused to try and fix it.
> > ??I gave her my old PC with Debian and configured Cinnamon to look like
> > Windows 7. ??All she does with it is web and email so all I really had
> > to do was setup Firefox and Evolution and tell her it was Windows.
> >
> > As far as the kernel goes, I rebuilt the stock kernel that Debian uses
> > just for kicks. ??It took 25 minutes on a 16-thread system with SSD
> > storage, source tree plus build output occupies 26G, pretty bloaty. ??I
> > just refreshed most of my infrastructure and in the process switched
> > from xfs/LVM to ZFS so it may be time to make the switch back to
> > FreeBSD if I retain enough muscle memory.
>
> So I'm a SunOS guy, got there just after SunOS 4.0, contributed to 4.1,
> really contributed to 4.1.1 and 4.1.3.  I loved SunOS.
>
> 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), FreeBSD is stuck in the 1980s.  Raise your hand
> if you have installed FreeBSD in the last 20 years.  That "UI"
> for partitioning the disks, so arcane.  The whole install experience
> is _awful_.
>

We must be using different installers. The defaults just work.

But so what. Even if it was awful, it's the first 5 minutes of your
experience... People don't use the installer, and with the VM images
there's even less need to day to fixate on it.

And to be fair, it isn't from the 80s. In the 80s, you booted a tape
and got. stuck with whatever partitioning the disk driver had. In the 90s
you used a calculator to figure out the labels to put on the drives
as we started to get a diversity of disks. In the 2000s, everything was
still text based, like FreeBSD's installer, but helped you partition things.
It wasn't until the 2010s that the installers started to become graphical
on a wide-spread basis.

But try installing ZFS root. FreeBSD's installer just does the right thing
setting it up. For Liunx, despite it's "awesome" graphics experience, I
had 6 pages of instructions from the OpenZFS web site to do it. So while
it looks nicer, for sure, there's still some UX issues to overcome.


> 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.
>

FreeBSD's installer doesn't need a mouse... And Linux installers
have been hit or miss on this issue over the years (mostly a hit,
but not always)...

And despite all the pro-Linux Netcraft propaganda, FreeBSD is
not dying.


> I'd love it if BSD had kept up but it has not.  Linux is way better.
> Yeah, all the bloat is annoying but we are not running on 64KB PDP-lls.
> L1 is that size, L2 and L3 are bigger.  Main memory is many orders of
> magnitude bigger, I'm typing this on a 32GB memory laptop.  It's fine.
>

What's that? I can't hear you over the 800Gbps of traffic we're able
to generate with FreeBSD but not Linux...  In all fairness, Linux does
a better job at moving lots of packets...

My daily driver is MacOS for work. And FreeBSD laptop for personal. There
are problems
with FreeBSD (I'm looking at you wifi), but it works great. The Graphics
issues
have been solved, by and large.

Warner

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

  parent reply	other threads:[~2024-03-08 15:28 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-07  6:47 [TUHS] " 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 [this message]
2024-03-08 23:18       ` [TUHS] FreeBSD kernel not OK? (was: What do you currently use for your primary OS at home?) Greg 'groggy' Lehey
2024-03-08 23:43         ` [TUHS] " 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
2024-03-07 19:41 [TUHS] " Douglas McIlroy
2024-03-08 16:09 ` [TUHS] " John Cowan
2024-03-09 10:07   ` Wesley Parish

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='CANCZdfqsqddpdNmSiA3va5Rw_e2NAR=0=ThjysCg+SwncFq1uQ@mail.gmail.com' \
    --to=imp@bsdimp.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).