From: Gregg Levine <gregg.drwho8@gmail.com>
To: tuhs@tuhs.org
Subject: [TUHS] Re: FreeBSD kernel not OK?
Date: Sat, 9 Mar 2024 10:34:39 -0500 [thread overview]
Message-ID: <CAC5iaNHW-riQYPqetApEYKkJM0qLOWjFBOCiBrgJcNYQRm=FnA@mail.gmail.com> (raw)
In-Reply-To: <2aed1bdf-b55d-4e79-ac18-a261b60d870f@skogtun.org>
Hello!
I agree with the other fellow. I've run Slackware Linux, their 11.0
release on an older Dell and it did not need that pest. I've also used
KDE on it. And I've gotten Slackware 14.1 and Slackware 14.2 to work
on an older Dell laptop, both apply.
-----
Gregg C Levine gregg.drwho8@gmail.com
"This signature fought the Time Wars, time and again."
On Sat, Mar 9, 2024 at 4:53 AM Harald Arnesen via TUHS <tuhs@tuhs.org> wrote:
>
> Michael Huff [09/03/2024 00.57]:
>
> > I thought most desktops (specifically Xfce, GNOME, KDE) required Wayland
> > and SystemD these days? Wouldn't that rule out *BSD?
>
> Not true at all. I run Xfce on Devuan Linux, Void Linux and FreeBSD -
> all without systemd. The two Linuxes are distributions that deliberately
> won't let you use Substance D, as I like to call it.
>
> I haven't Wayland installed either.
> --
> Hilsen Harald
>
next prev parent reply other threads:[~2024-03-09 15:35 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 ` [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 [this message]
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='CAC5iaNHW-riQYPqetApEYKkJM0qLOWjFBOCiBrgJcNYQRm=FnA@mail.gmail.com' \
--to=gregg.drwho8@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).