Hi!
<offtopic>
I am back to GGI. I restored my superblock, but then I realized, that the
inode-table is also corrupted. So I bought a new harddisk installed a new
SuSE Linux 7.2 (Kernel 2.4.4, XF86 4.03) and made a full copy of my
/home-partition by 'dd if=/dev/hda9 of=./mirror.hda9'. Fortunately, mails
and the non-committed GGI code is stored in ASCII, so I restored them by
cut-and-paste. :)
</offtopic>
I run GGI usually on X-target, because fbdev doesn't support my card (ok,
I have still to recheck, if 2.4 supports it). The svgalib-driver is not
stable enough.
BTW: Is the svgalib-target ready again? It got frame-support just one week
before code freeze. This change works for me using the svgalib-vga-driver,
but it crashs, when using svgalib-rage-driver. IIRC, the frame-support is
not finished. We should either finish or readd it after final release.
Opinions?
Now, when I run GGI on X (XF86 4.0.3) it is very very slow. Have I found a
locking bug in the X-target or in XF86? Xlib-target works fine for me.
Thayne: You can commit your build environment patches, but I don't know,
if we should really add a contrib-directory in each lib holding rpm
generation stuff.
Folk: Should we add them in tools/dist/rpm (this directory was originally
intendend to hold rpm generation stuff) or in a contrib-directory in each
lib?
CU,
Christoph Egger
E-Mail: [EMAIL PROTECTED]
