World: r3wp

Unrelated thing: "The Linux framebuffer (fbdev) is a graphic hardware-independent 
abstraction layer to show graphics on a computer monitor, typically 
on the console. The word framebuffer means a part of video memory 
containing a current video frame, and the Linux framebuffer means 
\u201caccess method to the framebuffer under the Linux kernel\u201d, 
without relying on system-specific libraries such as SVGALib or another 
user space software." http://en.wikipedia.org/wiki/Linux_framebuffer

More DRI info: "Wayland display server, hosted by freedesktop.org 
and developed by several X.Org developers, both addresses criticisms 
of X by replacing it completely and works directly with the hardware 
via DRI. It is planned for Wayland to eventually replace X in Ubuntu[10] 
and Fedora,[11] the two most popular Linux distributions.[12] Wayland 
handles backward compatibility with X by optionally running an X.org 
server as a client, which can be rootless (having one Wayland window 
per X client).[13]"  http://en.wikipedia.org/wiki/X_Window_System

And more DRI and DirectFB: "Other competitors attempt to avoid the 
overhead of X by working directly with the hardware. Such projects 
include DirectFB. The Direct Rendering Infrastructure (DRI), which 
aims to provide a reliable kernel-level interface to the framebuffer, 
may make these efforts redundant.[14]" (same article)

So this clears all issues for me.

Faster DEs: "Q: How much faster is fluxbox compared with XFCE? A: 
Fluxbox will certainly load much faster after the login screen, and 
will consume probably 1/2 to 1/3 of the RAM that xfce will, but if 
you have lots of RAM you probably won't notice much speed difference 
after the loading process. However, if you only have 256MB of RAM 
fluxbox is the way to go..." http://forums.linuxmint.com/viewtopic.php?f=142&t=30599
(Untested by me)

gnewsense:

aptitude search dri|grep DRI

p   driconf                         - DRI configuration applet   
               

p   libgl1-mesa-dri-dbg             - Debugging symbols for the Mesa 
DRI modules

p   x11proto-xf86dri-dev            - X11 DRI extension wire protocol

with my nvidia card: :( driconf 
Xlib:  extension "XFree86-DRI" missing on display ":0.0".
Screen "0" is not direct rendering capable.

nouveau.freedesktop.org nvidia drivers wiki doesn't include the word 
DRI :(((

Ah. It includes a DRM word.

Fine :)

DirectFB looks outdated to me. It seems to support only old graphic 
cards.

My latest gnewsense 2.3 doesn't include DRI.

So it seems I need to build my own CLFS cross-lfs.org ... Though 
I didn't search for Linux distros supporting DRI.\

DRI links: http://dri.freedesktop.org/wiki/Links--- includes OSes, 
Linux distros, cards supporting DRI

AltME. I installed RHEL-based 64-bit Linux. And yum shows no 32-bit 
emulation libs. Anyone knows is it possible to set up RHEL64 for 
32-bit altme? The disto is ScientificLinux http://scientificlinux.org

As far as I know, DRI requires 3D support. DirectFB supports 2D hardware 
and drivers. It can be combined with OpenGL

It's quite possible that the OpenGL combination requires DRI

It seems 3D is optional at DRI.

Not sure.

REBOL Folks. How to fix a font in REBOL editor---it's unreadable!!! 
http://s017.radikal.ru/i401/1202/f0/b05d8abc5412.png

???

lsb_release -a;uname -a
No LSB modules are available.
Distributor ID:	gNewSense
Description:	gNewSense GNU/Linux 2.3 (deltah)
Release:	2.3
Codename:	deltah

Linux greenmeadow 2.6.24-30-generic #1 SMP Thu Jan 12 02:39:14 UTC 
2012 i686 GNU/Linux
Ok

sudo apt-get install xfonts-100dpi xfonts-75dpi
[sudo] password for gouslar: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
xfonts-100dpi is already the newest version.
xfonts-75dpi is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Ok

It's completely impossible to work with such a renderer of an editor.

I'll try to install R3---maybe it's more OK.

I recommend using an external editor. R2's internal editor is not 
very good.

R3 does not have an internal editor.

I'd be happy to attach an external editor to [Edit] Button in R2 
or R3.

I usually do it the other way around. Find a favorite editor and 
attach R2 or R3 to it.

That all is imperfect. OK.