#xfree86 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #xfree86, aggregated by home.social.
-
Red Hat 1.1 Mother's Day + 0.1 on 86Box with Socket 8 [1995]
#RedHat #TechNews #TechUpdates #Retrocomputing #XFree86 #Computers #ComputerHistory #RedHat1 #RedHat1_1
-
Red Hat 1.1 Mother's Day + 0.1 on 86Box with Socket 8 [1995]
#RedHat #TechNews #TechUpdates #Retrocomputing #XFree86 #Computers #ComputerHistory #RedHat1 #RedHat1_1
-
Red Hat 1.1 Mother's Day + 0.1 on 86Box with Socket 8 [1995]
#RedHat #TechNews #TechUpdates #Retrocomputing #XFree86 #Computers #ComputerHistory #RedHat1 #RedHat1_1
-
Red Hat 1.1 Mother's Day + 0.1 on 86Box with Socket 8 [1995]
#RedHat #TechNews #TechUpdates #Retrocomputing #XFree86 #Computers #ComputerHistory #RedHat1 #RedHat1_1
-
Red Hat 1.1 Mother's Day + 0.1 on 86Box with Socket 8 [1995]
#RedHat #TechNews #TechUpdates #Retrocomputing #XFree86 #Computers #ComputerHistory #RedHat1 #RedHat1_1
-
Based Xlibre Developer Drops XWayland Support
-
@jameshowell Thank you! It was weird thinking back to that. Do you remember the XFree86 server that was built to run in low memory situations? Was it called Xtiny or something? #xwindows #xfree86
-
@jameshowell Thank you! It was weird thinking back to that. Do you remember the XFree86 server that was built to run in low memory situations? Was it called Xtiny or something? #xwindows #xfree86
-
@jameshowell Thank you! It was weird thinking back to that. Do you remember the XFree86 server that was built to run in low memory situations? Was it called Xtiny or something? #xwindows #xfree86
-
@jameshowell Thank you! It was weird thinking back to that. Do you remember the XFree86 server that was built to run in low memory situations? Was it called Xtiny or something? #xwindows #xfree86
-
@jameshowell Thank you! It was weird thinking back to that. Do you remember the XFree86 server that was built to run in low memory situations? Was it called Xtiny or something? #xwindows #xfree86
-
#Wayback 0.1 has been released (#Wayland / #WaylandCompositor / #XServer / #XorgServer / #XOrg / #X / #XFree86 / #XWindowSystem / #X11 / #DisplayServer / #WindowServer / #WindowManager / #FreeDesktop) https://wayback.freedesktop.org/
-
#Wayback 0.1 has been released (#Wayland / #WaylandCompositor / #XServer / #XorgServer / #XOrg / #X / #XFree86 / #XWindowSystem / #X11 / #DisplayServer / #WindowServer / #WindowManager / #FreeDesktop) https://wayback.freedesktop.org/
-
#Wayback 0.1 has been released (#Wayland / #WaylandCompositor / #XServer / #XorgServer / #XOrg / #X / #XFree86 / #XWindowSystem / #X11 / #DisplayServer / #WindowServer / #WindowManager / #FreeDesktop) https://wayback.freedesktop.org/
-
#XLibre 25.0.0.5 has been released (#XServer / #XorgServer / #XOrg / #X / #XFree86 / #XWindowSystem / #X11 / #DisplayServer / #WindowServer / #WindowManager) https://x.org/
-
#XLibre 25.0.0.5 has been released (#XServer / #XorgServer / #XOrg / #X / #XFree86 / #XWindowSystem / #X11 / #DisplayServer / #WindowServer / #WindowManager) https://x.org/
-
#XLibre 25.0.0.5 has been released (#XServer / #XorgServer / #XOrg / #X / #XFree86 / #XWindowSystem / #X11 / #DisplayServer / #WindowServer / #WindowManager) https://x.org/
-
#XLibre 25.0.0.5 has been released (#XServer / #XorgServer / #XOrg / #X / #XFree86 / #XWindowSystem / #X11 / #DisplayServer / #WindowServer / #WindowManager) https://x.org/
-
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.
-
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.
-
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.
-
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.
-
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.
-
3000-Abo-Spezial: Mein allererstes Linux von 1995/6 jetzt auch in BUNT!
https://tube.tchncs.de/videos/watch/dc2e1b49-9708-4ad2-be27-463156c65563
-
3000-Abo-Spezial: Mein allererstes Linux von 1995/6 jetzt auch in BUNT!
https://tube.tchncs.de/videos/watch/dc2e1b49-9708-4ad2-be27-463156c65563
-
3000-Abo-Spezial: Mein allererstes Linux von 1995/6 jetzt auch in BUNT!
https://tube.tchncs.de/videos/watch/dc2e1b49-9708-4ad2-be27-463156c65563
-
3000-Abo-Spezial: Mein allererstes Linux von 1995/6 jetzt auch in BUNT!
https://tube.tchncs.de/videos/watch/dc2e1b49-9708-4ad2-be27-463156c65563
-
3000-Abo-Spezial: Mein allererstes Linux von 1995/6 jetzt auch in BUNT!
-
Iconography of the X Window System: The Boot Stipple
https://matttproud.com/blog/posts/x-window-system-boot-stipple.html
#XWindow #X11 #XFree86 #Wayland -
ちょっと何をおっしゃっているのか理解できないのですが #XFree86
"SVGA サーバー対応の汎用 VGA ドライバーを（8bppの320x200固定で）サポートし ました"
XFree86[TM] 3.1.1 のためのREADME https://xjman.dsl.gr.jp/XF311/XF86RMj.html -
@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. -
@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. -
@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. -
@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
-
そんなもん要らんわ、と言われそうだけど、 #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
-
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
-
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
-
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
-
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.
-
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.
-
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.
-
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.
-
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
-
@taylorlorenz Must be copyright infringement. This looks like the #xwindow logo #unix #xorg #xfree86
-
@taylorlorenz Must be copyright infringement. This looks like the #xwindow logo #unix #xorg #xfree86
