From: Marc Donner <marc.donner@gmail.com>
To: arnold@skeeve.com
Cc: jeffryrabramson@gmail.com, tuhs@tuhs.org
Subject: [TUHS] Re: What do you currently use for your primary OS at home?
Date: Thu, 7 Mar 2024 06:04:25 -0500 [thread overview]
Message-ID: <CALQ0xCAUAsO9Kk1cDFwMAar4szxvSz+FTaSJyymD2UpNC6ntUA@mail.gmail.com> (raw)
In-Reply-To: <202403070909.42799vAR003680@freefriends.org>
[-- Attachment #1: Type: text/plain, Size: 1508 bytes --]
For day-to-day (email, web, blah blah) I keep a relatively current MacOS
box. In addition I keep a ‘toy data center’ - a set of four NUC machines
running Ubuntu on which I keep my various system management projects and
development projects. They are all headless, so I have a small hdmi
display I plug in when I need to do release upgrades and other tasks that
require a ‘console’.
=====
nygeek.net
mindthegapdialogs.com/home <https://www.mindthegapdialogs.com/home>
On Thu, Mar 7, 2024 at 4:10 AM <arnold@skeeve.com> wrote:
> "Jeffry R. Abramson" <jeffryrabramson@gmail.com> wrote:
>
> > Thinking of looking for something simpler and was just wondering what
> > do other old timers use for their primary home computing needs?
>
> I run Ubuntu Mate. All the nice features of Ubuntu, plus a more
> normal UI and everything just works. In particular it handles
> current hardware (laptops, wifi, etc) fine, as well as knowing about
> network printers, generally without problems. I work with a bunch
> of terminal windows with Bash and gvim for editing, evince for viewing
> PDFs and a web browser.
>
> If you want a more do-it-yourself kind of feel, you might try some
> variant of Plan 9; the 9front fork is the most actively developed.
> Plan 9 has ben on my to-do list for a few decades now; maybe once
> I retire I'll actually get to it. :-) Be forewarned that there's
> a learning curve there, Plan 9 is most definitely NOT Unix.
>
> HTH,
>
> Arnold
>
[-- Attachment #2: Type: text/html, Size: 2210 bytes --]
next prev parent reply other threads:[~2024-03-07 11:04 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 [this message]
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
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=CALQ0xCAUAsO9Kk1cDFwMAar4szxvSz+FTaSJyymD2UpNC6ntUA@mail.gmail.com \
--to=marc.donner@gmail.com \
--cc=arnold@skeeve.com \
--cc=jeffryrabramson@gmail.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).