cvs commit: hints boot-cd_easy.txt xfree86-superhint.txt
timothy at linuxfromscratch.org
timothy at linuxfromscratch.org
Mon Dec 16 17:27:33 PST 2002
timothy 02/12/16 20:27:33
Modified: . boot-cd_easy.txt xfree86-superhint.txt
Updates by author.
Revision Changes Path
1.10 +1 -1 hints/boot-cd_easy.txt
RCS file: /home/cvsroot/hints/boot-cd_easy.txt,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- boot-cd_easy.txt 22 Nov 2002 14:05:38 -0000 1.9
+++ boot-cd_easy.txt 17 Dec 2002 01:27:33 -0000 1.10
@@ -584,6 +584,6 @@
Christian Hesse <mail at earthworm.de>
Special thanks for bug reports and help to:
- ??????? <oneyed at gmx.de>
+ David Maus <oneyed at gmx.de>
1.2 +38 -16 hints/xfree86-superhint.txt
RCS file: /home/cvsroot/hints/xfree86-superhint.txt,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- xfree86-superhint.txt 16 Dec 2002 03:15:19 -0000 1.1
+++ xfree86-superhint.txt 17 Dec 2002 01:27:33 -0000 1.2
@@ -1,11 +1,6 @@
LFS VERSION: 4.0+
-AUTHOR: Sam Halliday <fommil AT yahoo DOT ie>
- Dave Ayers <fogey AT mindspring DOT com>
- Luke Guest <laguest AT nebulas DOT demon DOT co DOT uk>
- Marc Heerdink <marc AT koelkast DOT net>
+AUTHORS: Sam Halliday <fommil AT yahoo DOT ie>
This hint covers the building and initial configuration of an XFree86
@@ -18,6 +13,9 @@
xfree86_42.txt, xfree86_4.2.0_dri.txt, nvidia_glx and dri.txt. For that
reason, credits are due to
Matthias Benkmann <m DOT s DOT b AT gmx DOT net>
+ Marc Heerdink <marc AT koelkast DOT net>
+ Dave Ayers <fogey AT mindspring DOT com>
+ Luke Guest <laguest AT nebulas DOT demon DOT co DOT uk>
Ryan Strayer <rstrayer AT kc DOT rr DOT com>
manaveru <manaveru AT manaveru DOT net>
Sergey Ostrovsky <sostrovsky AT snip DOT net>
@@ -30,6 +28,9 @@
0.02 suggestions by Matthias Benkmann.
0.03 suggestions by Marc Heerdink.
0.04 building of glut added, more from Matthias Benkmann.
+0.05 changed AUTHOR section by request of older maintainers,
+ notes on Dagmar's concise hint which compiles freetype,
+ other small fixes.
@@ -92,6 +93,13 @@
appears in several sections; standard DRI, bleeding edge DRI, bad news about
voodoo cards and finally setting up NVidia cards.
+LFS'ers may also choose to use the xfree-freetype hint which compiles
+freetype and zlib serperately. My personal experience has been that
+the internal XFree86-4.2.1 version of Freetype2 works just fine and
+we specifically tell X to compile dynamically linked to the zlib we
+install in LFS. Beware of using other LFS x-hints as they are mostly
@@ -114,7 +122,8 @@
modules you require if you are sure about your choice. If your card is not
supported under DRI (graphics acceleration), then you should say NO to
BuildXF86DRI and BuildXF86DRM. Please note this is a C header file not a
-bash script, so the # are not comments but the /* comments */ are.
+bash script, so the # are not comments but the /* comments */ are. Please
+READ this setup file before typing it in blindly.
cat > config/cf/host.def << "EOF"
/* LFS HINT XFree86-4.2.1 0.01 */
@@ -127,7 +136,13 @@
#define HasMMXSupport NO /* Any i586 or above */
#define HasKatmaiSupport NO /* PIII SSE instuctions */
#define Has3DNowSupport NO /* AMD instructions */
-#define XInputDrivers mouse void
+#define XInputDrivers /*
+ We omit compiling rarely used input devices.
+ If you do have a non-standard input device,
+ browse config/cf/xfree86.cf for a complete
+ mouse void
#define XF86CardDrivers /* build all drivers available */
mga glint nv tga s3 s3virge sis rendition
neomagic i740 tdfx savage cirrus vmware
@@ -161,7 +176,11 @@
compile continues, and problems only manifest themselves in the make install.
This is quite annoying as it may lead to an old 'working' X being overwritten
by a new 'broken' one. For that reason I suggest anyone with an X install
-present already, make a backup of /usr/X11R6 at this stage.
+present already, make a backup of /usr/X11R6 at this stage. You could also run
+ grep error xcompile.std*
+to see if there are any early signs of things going wrong.
Once that is all done, type
@@ -170,7 +189,7 @@
-I reccomend you look at the hint on man pages, since default man pages are
+I recommend you look at the hint on man pages, since default man pages are
uncompressed. Unfortunately it is not as simple as typing 'gzip -9 *' to
compress the pages as there are symbolic links to consider also.
@@ -303,8 +322,11 @@
The best way to utilise fonts under XFree86 is with a font server, which
handles all the font aliases and matching instead of the actual X server
-itself. This server should be started in the initscripts, and it is left
-to your own discression as to when to load the font server.
+itself. The font server is however, an extra overhead on your system, but
+for todays machines, it is a negligable amount... the memory and CPU usage
+on my machine never amounts to more than 0.1% and 0%. This server should
+be started in the initscripts, and it is left to your own discression as
+to when to load the font server.
cat > /etc/rc.d/init.d/xfs << "EOF"
@@ -532,7 +554,7 @@
dropped. I found this out the hard way!
-NVIDIA ACCELERATED GRAPHICS (recomended for NVidia cards)
+NVIDIA ACCELERATED GRAPHICS (recommended... only for NVidia cards)
NVidia has never released open sourced code for their 'unified' driver. If you
@@ -578,12 +600,12 @@
If you 'startx' and X locks at startup you'll need to edit os-registry.c and
-heck the comments near lines that start something like '#if 0'.
+check the comments near lines that start something like '#if 0'.
-If 3D acceleration just is not working, you probably have some mesa libs lying
+If 3D acceleration is just not working, you probably have some Mesa libs lying
around in /usr/lib. Remove the following files /usr/lib/libMesa*
/usr/X11R6/lib/libMesa* and reinstall the GLX module. If you have 3D apps that
-require Mesa libs, you can simply create symlinks to GLX lib (libGL.so.1). You
+require Mesa, you can simply create symlinks to GLX lib (libGL.so.1). You
also need to remove /usr/X11R6/lib/libGL.so.1.2 and symlink it to
Unsubscribe: send email to listar at linuxfromscratch.org
and put 'unsubscribe hints' in the subject header of the message
More information about the hints