From: Steve Nickolas <usotsuki@buric.co>
To: tuhs@tuhs.org
Subject: [TUHS] Re: What do you currently use for your primary OS at home?
Date: Thu, 7 Mar 2024 09:38:15 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.21.2403070934380.7554@sd-119843.dedibox.fr> (raw)
In-Reply-To: <9eb334edeb7568193000f8755704af7799169b17.camel@gmail.com>
On Thu, 7 Mar 2024, Jeffry R. Abramson wrote:
> I've been using some variant of Linux (currently Debian 12) as my
> primary OS for daily activities (email, web, programming, photo
> editing, etc.) for the past twenty years or so. Prior to that it was
> FreeBSD for nearly ten years after short stints with Minix and Linux
> when they first came out. At the time (early/mid 90's), I was working
> for Bell Labs and had a ready supply of SCSI drives salvaged from
> retired equipment. I bought a Seagate ST-01A ISA SCSI controller for
> whatever 386/486 I owned at the time and installed Slackware floppy by
> floppy.
My current daily driver is Debian 11 (because I don't have the room for a
distro upgrade). Went back and forth between Debian and Windows since
about 2005.
I'd thought of trying to do my own rewrite of SVR4/4.2 for kicks, but I
don't think I'd be able to daily-drive it and I wanted to start with an
existing kernel - and getting started has proven to be about a pain.
(I've proposed both Linux, with clang and musl, and NetBSD, with clang and
its own libc, as the starting points.)
> When I upgraded to a Pentium PC for home, Micron P90 I think, I
> installed a PCI SCSI controller (Tekram DC-390 equipped with an
> NCR53c8xx chip) to make use of my stash of drives. Under Linux it was
> never entirely stable. I asked on Usenet and someone suggested trying
> the other SCSI driver. This was the ncr driver that had been ported
> from FreeBSD. My stability problems went away and I decided to take a
> closer look at FreeBSD. It reminded me of SunOS from the good old pre-
> System V era along with the version of Unix I had used in grad school
> in the late 70's/early 80's so I switched.
No wonder, really, given the common ancestry.
> I eventually reverted back to Linux because it was clear that the user
> community was getting much larger, I was using it professionally at
> work and there was just a larger range of applications available.
> Lately, I find myself getting tired of the bloat and how big and messy
> and complicated it has all gotten. Thinking of looking for something
> simpler and was just wondering what do other old timers use for their
> primary home computing needs?
I think they've all gotten bloaty anymore.
-uso.
next prev parent reply other threads:[~2024-03-07 14:37 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
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 [this message]
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=alpine.DEB.2.21.2403070934380.7554@sd-119843.dedibox.fr \
--to=usotsuki@buric.co \
--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).