From: Alexis <flexibeast@gmail.com>
To: tuhs@tuhs.org
Subject: [TUHS] Re: FreeBSD kernel not OK?
Date: Sat, 09 Mar 2024 11:16:33 +1100 [thread overview]
Message-ID: <87r0gkp8da.fsf@gmail.com> (raw)
In-Reply-To: <CAFwmL86sdCGcb90JAnUYxdFrMdDjXimDZf_u7MZ9dNd1nHrr-Q@mail.gmail.com> (Michael Huff's message of "Fri, 8 Mar 2024 14:57:57 -0900")
Michael Huff <mphuff@gmail.com> writes:
> I thought most desktops (specifically Xfce, GNOME, KDE) required
> Wayland and SystemD these days? Wouldn't that rule out *BSD?
i'm not a user of any of those three myself, but as far as i'm
aware, none of those three currently require Wayland. But GNOME is
certainly pushing people towards use of Mutter (the GNOME Wayland
compositor), while:
> It is not clear yet which Xfce release will target a complete
> Xfce Wayland transition (or if such a transition will happen at
> all). Below is a list of larger tasks which would need to be
> done in some way for such a transition to occur.
-- https://wiki.xfce.org/releng/wayland_roadmap
In terms of Wayland on *BSDs, there's active work being done to
get the Wayland ecosystem working on OpenBSD:
"Towards running a Wayland Compositor on OpenBSD"
--
https://www.openbsd.org/papers/eurobsdcon2023-matthieu-wayland-openbsd.pdf
The author of that talk, Matthieu Herrb, is an X dev:
https://www.x.org/wiki/MatthieuHerrb/
Alexis.
next prev parent reply other threads:[~2024-03-09 0:16 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 ` Alexis [this message]
2024-03-09 17:25 ` [TUHS] Re: FreeBSD kernel not OK? 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=87r0gkp8da.fsf@gmail.com \
--to=flexibeast@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).