X Might Be Ready For IPV6
makapuf writes "According to linuxtoday, the X Consortium has published enhancement proposals to let X and IPV6 interoperate. This is surely a relief for the masses here that longed for X support for IPV6. Or the contrary? The proposal can be found here."
Maybe not FP... :)
Well... next one.
Once they add IPv6 support, maybe then they will fix the flaw in xfs that causes X to segfault on my computer all the time.
../sysdeps/generic/memcpy.c:55 /usr/X11R6/lib/libXfont.so.1e s () from /usr/X11R6/lib/libXfont.so.1 /usr/X11R6/lib/libXfont.so.1e () from /usr/X11R6/lib/libXfont.so.1 /usr/X11R6/lib/libXfont.so.1
Stack backtrace:
memcpy (dstpp=0xbfffe1a8, srcpp=0x84a0c08, len=1024) at
FTGetEnglishName () from
FreeTypeAddProperti
FreeTypeLoadXFont () from
FreeTypeOpenScalabl
FontFileOpenFont () from
do_open_font ()
OpenFont ()
ProcOpenBitmapFont ()
Dispatch ()
main ()
Hint: the srcpp buffer contains a name of a font and the buffer allocation is shorter than 1024 bytes-- thus causing the segfault.
Of those posts recommending the replacement of X, approximately one-half will mention the Windowing System Formerly Known as Berlin, one-quarter will babble aimlessly about the Linux framebuffer, and the remainder will offer no alternative, but merely observe that network transparency is unnecessary, giving their lack of need for this feature as the reason (e.g. "ive never neieded 2 use xwindows over the network, y would any1 ellse!!??").
Just becuase some PC technician at "The Wiz" can't see the sense in ipv6 doesn't mean Nortel networks and Lucent don't have a use for it.
That's likely where IPv6 will be relegated, and even there, 128 bits is arguably a big, fat waste.
What it will not become is an end-to-end addressing scheme as originally designed, it's just not the best solution or even close to it.
Have you got your LWN subscription yet?
That sounds worse than the first one.
If that's all you need, go play with DirectFB. It's even 3D accelerated if set up correctly, and has GNOME working.