Based Xlibre Developer Drops XWayland Support
#XFree86
El wey que hizo el #fork de #X11 es confirmado neonazi:
https://mas.to/@libreleah/114669835981358887
No sé ustedes, pero tomando en cuenta que a mí X11 va rotísimo en mi compu, y ahora viendo que el único fork aparentemente viable es mantenido y auspiciado por un neonazi, siento que tengo aún más razones para promover a favor de #Wayland, por más que les arda a los antis.
Загадка от Жака Фреско
#xorg #xfree86 #xf86 #modesetting #legacy
3000-Abo-Spezial: Mein allererstes Linux von 1995/6 jetzt auch in BUNT!
https://tube.tchncs.de/videos/watch/dc2e1b49-9708-4ad2-be27-463156c65563
@jhx Makes sense to me 😉 I guess I couldn't really fall for that because I started exploring "alternative" x86-PC operating systems in a time before internet at home was a common thing, let alone with a speed suitable for downloading larger software distributions 😁 (plus getting some "Linux distribution" to work correctly on your machine was a lot more work, e.g. no way to do this without manually editing a monolithic config file for #XFree86 if you wanted a GUI). So you were thinking twice before "starting over" 😅
I started with some old #SUSE, because that came bundled on a 💿(!) with some magazine. Soon I wasn't happy how its "yast" tool fought over changing all sorts of config files etc ...
Also found #Debian first on some magazine disc (2.1 "slink") and managed to install this as a server offering a few services. For the desktop, I tried #Mandrake for a while, back then it was one of the few with largely working and sane auto-configurations... but as #Debian just felt better (simple and powerful management tools you could understand, so they didn't interfer with your manual configurations), I finally got that on the desktop as well. Stayed with that for a *long* time until it grew in complexity and I had hard to solve issues (also related to #systemd when it was first introduced in Debian), so looking for alternative, I figured it was time to say goodbye to Linux. Tried #FreeBSD and this worked awesome for me! For some software, you need Linux, and when I do, Debian is still my choice...
In general, I developed a habit of never changing stuff "just for the sake of it", only when I can name things I'm unhappy with. So for example, I use neomutt instead of mutt now (lots of added features I like that were only available as unofficial patches for mutt), but when people tell my I should try neovim, I just ask myself, why? After all, I'm perfectly happy with vim.
So I also never tried #wayland so far, because I see no need for my usecase, as #Xorg works perfectly fine for me. Currently even experimenting with programming #X11 "directly" (using #xcb) instead of using some UI toolkit. 🙈 Of course, in C only -- there's little you *can't* do in that veteran language 😎
ちょっと何をおっしゃっているのか理解できないのですが #XFree86
"SVGA サーバー対応の汎用 VGA ドライバーを（8bppの320x200固定で）サポートし ました"
XFree86[TM] 3.1.1 のためのREADME https://xjman.dsl.gr.jp/XF311/XF86RMj.html
Just discovered #myfirstdistro and here's mine: #Suse #Linux 6.0 - It happened at a second-hand shop for hard- and software; between Data Becker and MS Frontpage boxes there was a copy of Suse. The back-cover had a screenshot of what looked very similar to Chigago shell, just a little different. It was #KDE 2. That was when I first realised that there are obviously other systems to operate PCs. I bought that box for 5 Deutsche Mark. 🙃 One week later I managed to successfully start #XFree86 😅
@pgpkeys #gnupg was always a trainwreck and the community was always super hostile to end users.
Maybe it's time to move on with life to something else?
#xfree86 played stupid games leading to purge of toxic project management when crowds moved under #xorg umbrella.
Perhaps we need a similar drama in #openpgp #gnupg community to get something better.
#XFree86 のバージョンによってまた変わってくる?
"Xの4.1xにしたぐらいから ATOKSE のkinput2が起動しなくなった
だれかこの意味教えてください。 "
初心者もＯＫ！ FreeBSD質問スレッド その５ http://mimizun.com/log/2ch/unix/996828056/866
そんなもん要らんわ、と言われそうだけど、 #TurboLinux 6.0 に付属する、太古の #XFree86 で #QEMU のcirrusグラフィックスを利用するために参考にしたのはこのページです
Cirrus チップセットユーザ向けの情報 https://xjman.dsl.gr.jp/xf86_3/cirrus.html
Wow!
“Wayland Isn't Going To Save The Linux Desktop” [2022], ‘Dudemanguy’ (https://dudemanguy.github.io/blog/posts/2022-06-10-wayland-xorg/wayland-xorg.html).
Via HN: https://news.ycombinator.com/item?id=38508311
On Lobsters: https://lobste.rs/s/ycuhxy/wayland_isn_t_going_save_linux_desktop
Plamo #Linux で使われている #XFree86 4.3.0における #xf86config の使い方が書いてあった
http://plamo.linet.gr.jp/~kmoue/plamo/3.3/xf86config_430.html
When I was 14, I grappled with configuring #xfree86. Mostly modelines so my CRT monitor didn’t explode. I definitely remember making music from incorrect modeline settings though!
At this was, GUIs and WMs worked great. Why? Because XFree86 had its own graphics rendering engine. This was a core part of its design. You could, if you wanted, rely on the XServer (via Xlib) to render window borders, etc. This is how it were possible to write fvwm as a MWM/CDE clone.
I know the decentralised network model doesn’t scale, but that’s separate in design to the graphics rendering which was possible.
Then came #xorg, an improvement over #xfree86, the core principles unchanged.
With #wayland, all of these considerations are abandoned. Compositors are supposed to implement everything themselves. OK. wlroots might help. But for server side rendering, there’s nothing. The xlib drawing routines don’t exist. I’ve checked libcairo, it doesn’t even come close to xlib.
So now what? Every wayland composer will just look the same. There’s no way without significant effort on my part to augment libcairo to have a hope in hell for a FVWM wayland compositor.
How the hell is wayland an improvement on the Xorg design? It’s not. Wlroots shouldn’t exist. It does so because it forces compositors to need to do the same thing. As a result the aesthetic and behaviour will be the same.
Progress? I call bullshit on the whole thing.
@taylorlorenz Must be copyright infringement. This looks like the #xwindow logo #unix #xorg #xfree86
There was no greater joy than #XFree86 starting, twm opening a terminal, and glxgears being buttery smooth. When I hear people complain about modern #Linux GPU drivers, I want to scream.
Umm. Google, why the hell are you giving me what looks like 20 year old instructions? From what I gather, configuring touch screens on a multi-monitor setup in linux is apparently a highly obscure and niche idea so not something with a lot of documentation (not to mention it just can't be done on wayland unless you're using Swift). And, it's definitely cool that Google now gives you an indication of why a result has been returned. What concerns me, though, is that they don't consider the age of the result at all.
According to archive.org, that page hasn't been significantly updated since 2006 when the "touchcal" link was updated to sourceforge. Before that was 2004, again updating the touchcal link, and then 2002 when the document was created.
Google's second result is 21 years old.
I suspect XFree86 drove a lot of would-be desktop Linux users to macOS, especially after the Apple + Intel era began.
`XFree86 -configure` was pure insanity.
Client Info
Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst