2 ms·
Do the same for X! Well.. a layered addition maybe. I've always felt it's bringing swags of stuff which never gets used. A non accelerated fb or vesa binding wo
by ggm 9mo ago
Do the same for X! Well.. a layered addition maybe. I've always felt it's bringing swags of stuff which never gets used. A non accelerated fb or vesa binding would do for a lot of things.
I liked this piece a lot. Nice write up of how you explored the space.
- vermaden 9mo agoThank You :) > Do the same for X! I kinda did ... but for RAM usage and not disk space. Details here: - https://vermaden.wordpress.com/2026/01/18/200-mb-ram-freebsd-desktop/ https://vermaden.wordpress.com/2026/01/18/200-mb-ram-freebsd...
- yjftsjthsd-h 9mo ago> What I really loved is that XLibre X11 packages DOES NOT CONFLICT with Xorg packages. You just install xlibre instead of xorg and everything works … even better then with Xorg How do you control which one is used? I was expecting xlibreinit or something, but the rest of the post appears to just run xinit like normal with nothing that I noticed that would select an X implementation
- vermaden 9mo agoWhat I expected - that if I would want to install Openbox - then Xorg will be forced. I typed: # pkg install xlibre ... and X11 XLibre implementation installed and Openbox installed properly and 'xorg' packages was not forced. The binaries of XLibre still have the same old 'Xorg' names like 'Xorg' is the server binary name (not 'XLibre') and xinit(1) is still xinit(1) ... But if you already have 'xorg' package installed and you would like to install 'xlibre' package then there would be conflicts as they install file into the same places - and often with the same names. Hope that helps.
- yjftsjthsd-h 9mo agoOh, I see. I would have described that as that the packages did conflict - that one replaces the other - but that other packages accept either implementation. Either way you phrase it, thanks for clarifying