mirror of https://github.com/tLDP/LDP
updated
This commit is contained in:
gferg
parent
f23c56ec53
commit
2f7c21a337
|
|
@ -666,14 +666,9 @@ Topics of Current Interest.</title>
|
|||
Should I Upgrade to the 2.4.0 Kernel? Now?
|
||||
</title>
|
||||
<para>
|
||||
``It's ready.''
|
||||
</para>
|
||||
<para>
|
||||
With those two resounding, immortal words, which rank with ``Nuts!''
|
||||
and ``Damn the torpedoes!'' in the domain of histrionics, Linus
|
||||
Torvalds released brand-new kernel version 2.4.0, product of countless
|
||||
hours of coding, testing, and re-coding, by dogged kernel hackers, to
|
||||
the public.
|
||||
The kernel 2.4 source code, the product of countless hours of
|
||||
coding, testing, and re-coding, by dogged kernel hackers, is
|
||||
being upgraded with patches and bug fixes.
|
||||
</para>
|
||||
<para>
|
||||
Among the new kernel's features are: support for the IBM S/390, the
|
||||
|
|
@ -681,7 +676,8 @@ Logical Volume Manager, NFS Version 3 servers, PCMCIA CardBus devices,
|
|||
USB peripherals, the Device File System, 64 GB of RAM (yes, that's
|
||||
memory, not disk space), Itanium and MMX processors, drivers for many
|
||||
additional hardware devices, greater maximum file sizes, and vastly
|
||||
improved Symmetric Multiprocessing capabilities.
|
||||
improved Symmetric Multiprocessing capabilities, at least for
|
||||
certain processors.
|
||||
</para>
|
||||
<para>
|
||||
The changes are more significant for non-i386 platforms, although
|
||||
|
|
@ -691,8 +687,8 @@ and stumble over the incompatibilities—of the new kernel as well.
|
|||
<para>
|
||||
If there's a compelling reason to upgrade, the source code is
|
||||
available, in the tar archive:
|
||||
<filename>linux-2.4.0.tar.gz</filename>, in all of the usual
|
||||
places. (Refer to: ``<xref
|
||||
<filename>linux-2.4.</filename><emphasis>x</emphasis><filename>.tar.gz</filename>, in all
|
||||
of the usual places. (Refer to: ``<xref
|
||||
linkend="where-can-i-get-the-latest-kernel-version"
|
||||
endterm="where-can-i-get-the-latest-kernel-version">,'' below.) It
|
||||
will likely be several months at least before the commercial vendors
|
||||
|
|
@ -822,8 +818,8 @@ Where Can I Get the Latest Kernel Version?</title>
|
|||
<para>
|
||||
Make that versions. The 2.0 series kernels are still available for
|
||||
older machines. The latest production kernel series is 2.2.x. The
|
||||
updates to this kernel are bug fixes. The prerelease versions
|
||||
of the 2.4 kernel are also on-line there.
|
||||
updates to this kernel are bug fixes. The new 2.4 kernel sources are
|
||||
also on-line.
|
||||
</para>
|
||||
<para>
|
||||
The Web page at
|
||||
|
|
@ -845,7 +841,7 @@ file.
|
|||
</para>
|
||||
<para>
|
||||
Follow the instructions in any of the standard references to compile
|
||||
the 2.2 kernel, as you would with any other custom kernel. The
|
||||
the kernel, as you would with any other custom kernel. The
|
||||
<filename>Documentation</filename> subdirectory contains information
|
||||
by the authors of various subsystems and drivers, and much of that
|
||||
information is not documented elsewhere.
|
||||
|
|
@ -4205,7 +4201,7 @@ something like that. Get a recent version.
|
|||
<title id="lilo-boot-kernel-image">
|
||||
How Do I Get LILO to Boot the Kernel Image?</title>
|
||||
<para>
|
||||
>From kernel versions 1.1.80 on, the compressed kernel image, which is
|
||||
From kernel versions 1.1.80 on, the compressed kernel image, which is
|
||||
what LILO needs to find, is in <filename>arch/i386/boot/zImage</filename>, or
|
||||
<filename>arch/i386/boot/bzImage</filename> when it is built,
|
||||
and is normally stored in the
|
||||
|
|
@ -4819,16 +4815,17 @@ also archived at <ulink url="ftp://rtfm.mit.edu/pub/usenet/">
|
|||
|
||||
<sect2 label="8.8">
|
||||
<title id="sendmail-pause">
|
||||
How Do I Prevent Sendmail from Pausing for Up to a Minute at
|
||||
Each Command?
|
||||
How Do I Prevent <application>sendmail</application> from Pausing for
|
||||
Up to a Minute at Each Command?
|
||||
</title>
|
||||
<para>
|
||||
Make sure that Sendmail can resolve your hostname to a valid (i.e.,
|
||||
parsable) domain address. If you are not connected to the Internet,
|
||||
or have a dial-up connection with dynamic IP addressing, add the fully
|
||||
qualified domain name to the <literal>/etc/hosts</literal> file,
|
||||
<emphasis>in addition</emphasis> to the base host name; e.g., if the
|
||||
host name is ``<literal>bilbo</literal>'' and the domain is
|
||||
Make sure that <application>sendmail</application> can resolve your
|
||||
hostname to a valid (i.e., parsable) domain address. If you are not
|
||||
connected to the Internet, or have a dial-up connection with dynamic
|
||||
IP addressing, add the fully qualified domain name to the
|
||||
<literal>/etc/hosts</literal> file, <emphasis>in addition</emphasis>
|
||||
to the base host name; e.g., if the host name is
|
||||
``<literal>bilbo</literal>'' and the domain is
|
||||
``<literal>bag-end.com</literal>:''
|
||||
</para>
|
||||
<para>
|
||||
|
|
@ -4849,6 +4846,30 @@ And make sure that either the <literal>/etc/host.conf</literal> or <literal>
|
|||
<literal>/etc/hosts</literal>, because many programs depend on it for
|
||||
internal message-passing.
|
||||
</para>
|
||||
<para>
|
||||
<application>Sendmail</application> takes many factors into account
|
||||
when resolving domain addresses. These factors, collectively, are
|
||||
known as, ``rulesets,'' in <application>sendmail</application> jargon.
|
||||
The program does <emphasis>not</emphasis> require that a domain
|
||||
address be canonical, or even appear to be canonical. In the example
|
||||
above, ``<literal>bilbo.</literal>'' (note the period) would work just
|
||||
as well as ``<literal>bilbo.bag-end.com</literal>.'' This and other
|
||||
modifications apply mainly to recent versions.
|
||||
</para>
|
||||
<para>
|
||||
Prior to version 8.7, <application>sendmail</application> required
|
||||
that the FQDN appear first in the <filename>/etc/hosts</filename>
|
||||
entry.
|
||||
</para>
|
||||
<para>
|
||||
Finally, <literal>FEATURE</literal> configuration macro options like
|
||||
<literal>nodns</literal>, <literal>always_add_domain</literal>, and
|
||||
<literal>nocanonify</literal>, control how
|
||||
<application>sendmail</application> interprets host names.
|
||||
</para>
|
||||
<para>
|
||||
[Chris Karakas]
|
||||
</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 label="8.9">
|
||||
|
|
@ -7365,3 +7386,4 @@ as educators and learners.
|
|||
</sect2>
|
||||
</sect1>
|
||||
</article>
|
||||
|
||||
|
|
|
|||
|
|
@ -19,8 +19,8 @@
|
|||
|
||||
<revhistory>
|
||||
<revision>
|
||||
<revnumber>v1.6</revnumber>
|
||||
<date>2001-01-17</date>
|
||||
<revnumber>v1.7</revnumber>
|
||||
<date>2001-01-21</date>
|
||||
<authorinitials>rbe</authorinitials>
|
||||
</revision>
|
||||
</revhistory>
|
||||
|
|
@ -198,13 +198,13 @@
|
|||
OpenGL man pages, you have to get them yourself.
|
||||
<itemizedlist>
|
||||
<listitem><para>mangl.tar.Z</para></listitem>
|
||||
<listitem><para>manglx.tar.Z</para></listitem>
|
||||
<listitem><para>manglu.tar.Z</para></listitem>
|
||||
<listitem><para>manglx.tar.Z (don't need this one)</para></listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<ulink url="ftp://ftp.sgi.com/sgi/opengl-from-sgigate/doc/">ftp://ftp.sgi.com/sgi/opengl-from-sgigate/doc/</ulink>
|
||||
<ulink url="ftp://ftp.sgi.com/sgi/opengl/doc/">ftp://ftp.sgi.com/sgi/opengl/doc/</ulink>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
|
|
@ -315,12 +315,12 @@
|
|||
<title>NVIDIA drivers (Mesa libGL replacement)</title>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem><para>NVIDIA_kernel-0.9-5.tar.gz</para></listitem>
|
||||
<listitem><para>NVIDIA_GLX-0.9-5.tar.gz</para></listitem>
|
||||
<listitem><para>NVIDIA_kernel-0.9-6.tar.gz</para></listitem>
|
||||
<listitem><para>NVIDIA_GLX-0.9-6.tar.gz</para></listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para>
|
||||
Note that XFree86 4.0.1, and later, is required with 0.9-5.
|
||||
Note that XFree86 4.0.1, and later, is required with 0.9-6.
|
||||
If you have XFree86 4.0.0, then you'll have to download the older 0.9-4 version.
|
||||
</para>
|
||||
|
||||
|
|
@ -328,6 +328,13 @@
|
|||
<ulink url="http://www.nvidia.com/">http://www.nvidia.com/</ulink>
|
||||
</para>
|
||||
|
||||
<tip>
|
||||
<para>
|
||||
See the updated faq at Nvidia.com while you are downloading.
|
||||
It may have some important information not in this HOWTO.
|
||||
</para>
|
||||
</tip>
|
||||
|
||||
<para>
|
||||
These make a kernel driver: /lib/modules/2.2.16/video/NVdriver
|
||||
and libGL.so and libGLcore.so files that go into /usr/lib/ to replace
|
||||
|
|
@ -358,6 +365,13 @@
|
|||
</screen>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Java2 1.3.0 FCS can also be used and it includes the JavaPlugin. If you use it, you
|
||||
don't have to get JavaPlugin-1.2.2-FCS. Installation of this Plugin is different
|
||||
and you'll have to see it's docs. Installation of Java2 1.3.0 itself, and Java3D, is
|
||||
the same as with Java2 1.2.2.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The Java 3D media extension contains many 3D demo programs/applets and takes advantage of the
|
||||
OpenGL hardware acceleration on the system. The Java 3D API uses the OpenGL API or, on Windows,
|
||||
|
|
@ -380,13 +394,19 @@
|
|||
|
||||
<para>
|
||||
If you have a version of XFree86 installed already, you may want to move it
|
||||
or delete it:
|
||||
or delete it. However, installing over an existing X is generally OK and
|
||||
preserves any programs or libraries you might have installed into the X
|
||||
directories (not that you should really do that):
|
||||
<screen>
|
||||
|
||||
cd /usr
|
||||
mv X11R6 X11R6-old
|
||||
cd /etc
|
||||
mv X11 X11-old
|
||||
|
||||
-- you may have an X directory in /var also
|
||||
cd /var
|
||||
mv X11R6 X11R6-old
|
||||
</screen>
|
||||
</para>
|
||||
|
||||
|
|
@ -434,6 +454,11 @@
|
|||
|
||||
cd /usr/src/release
|
||||
cd doctools
|
||||
|
||||
-- Having this variable set confuses the sgml docs build.
|
||||
-- With it unset, the build uses the proper defaults.
|
||||
unset $SGML_CATALOG_FILES
|
||||
|
||||
make
|
||||
make install
|
||||
cd ..
|
||||
|
|
@ -442,6 +467,16 @@
|
|||
-- add the following two lines to host.def:
|
||||
-- #define HasSgmlFmt YES
|
||||
-- #define BuildAllDocs YES
|
||||
-- See the README file in doctools.
|
||||
|
||||
-- Note: doctools installs the perl program sgmlfmt to
|
||||
-- /usr/local/bin. It looks for the perl executable
|
||||
-- at /usr/local/bin/perl. If perl is installed
|
||||
-- on your system at /usr/bin/perl, then it will not
|
||||
-- find perl and the sgml docs build will fail!
|
||||
-- Make a symlink if needed (or edit the script):
|
||||
cd /usr/local/bin
|
||||
ln -s /usr/bin/perl perl
|
||||
|
||||
cd /usr/src/release/xc
|
||||
make World
|
||||
|
|
@ -458,7 +493,7 @@
|
|||
ln -s ../X11R6/include/X11 X11
|
||||
ln -s ../X11R6/include/bitmaps bitmaps
|
||||
cd ..
|
||||
ls -s X11R6 X11
|
||||
ln -s X11R6 X11
|
||||
</screen>
|
||||
</para>
|
||||
|
||||
|
|
@ -475,19 +510,13 @@
|
|||
cd /usr/src/release/xc/doc/hardcopy
|
||||
cp -r GL /usr/X11R6/lib/X11/doc/html
|
||||
</screen>
|
||||
You might notice broken symlinks in /usr/X11R6/lib/X11/doc/html. This seems to be a bug in
|
||||
the XFree86 build/install. The manindex3.html file is also corrupted. The broken symlinks
|
||||
can simply be deleted.
|
||||
The index.html file in the docs points to manindex5x.html, but the filename may
|
||||
actually be manindex5.html. Just make a symlink to fix it:
|
||||
<screen>
|
||||
|
||||
cd /usr/X11R6/lib/X11/doc/html
|
||||
rm *3x.html
|
||||
|
||||
-- if you want to play with mass renaming files, you can
|
||||
-- use a command like the following:
|
||||
for afile in *3.html; do export afile; mv "$afile" "`awk 'BEGIN {print gensub("3.html","3x.html","G",ENVIRON["afile"]) }'`"; done;
|
||||
ln -s manindex5.html manindex5x.html
|
||||
</screen>
|
||||
Hopefully this HTML doc problem will be fixed soon!
|
||||
</para>
|
||||
|
||||
<para>
|
||||
|
|
@ -575,9 +604,9 @@
|
|||
rm libGL.*
|
||||
|
||||
cd /usr/src
|
||||
tar -xvzf NVIDIA_kernel-0.9-5.tar.gz
|
||||
tar -xvzf NVIDIA_GLX-0.9-5.tar.gz
|
||||
cd NVIDIA_kernel-0.9-5
|
||||
tar -xvzf NVIDIA_kernel-0.9-6.tar.gz
|
||||
tar -xvzf NVIDIA_GLX-0.9-6.tar.gz
|
||||
cd NVIDIA_kernel-0.9-6
|
||||
</screen>
|
||||
<tip>
|
||||
<para>
|
||||
|
|
@ -593,28 +622,32 @@
|
|||
<screen>
|
||||
make
|
||||
cd ..
|
||||
cd NVIDIA_GLX-0.9-5
|
||||
cd NVIDIA_GLX-0.9-6
|
||||
make
|
||||
ldconfig
|
||||
cd
|
||||
-- make a basic X config file
|
||||
xf86config
|
||||
follow the prompts and fill in the information it asks for
|
||||
|
||||
-- Make a basic XF86Config file using the "nv" driver:
|
||||
cd /etc/X11
|
||||
You must edit XF86Config and set the following:
|
||||
xf86config
|
||||
-- Follow the prompts and fill in the information xf86config asks for.
|
||||
-- Select the Nvidia GeForce or appropriate name.
|
||||
-- You can test X with this XF86Config file, or continue for OpenGL:
|
||||
|
||||
-- You must edit XF86Config and set the following:
|
||||
vi XF86Config
|
||||
Load "glx"
|
||||
Replace 'driver "nv"' with 'driver "nvidia"'
|
||||
Put "1600x1200" first (or your preferred screen resolution)
|
||||
Copy ttf fonts from Windows into a font directory and add a font path.
|
||||
Use ttmkfdir (check freshmeat.net) to a fonts.dir file.
|
||||
A good place to keep your own fonts is /usr/local/share/fonts ...
|
||||
|
||||
-- Nvidia drivers do NOT use the dri module - don't load it.
|
||||
|
||||
-- you may like to edit /etc/X11/xinit/xinitrc to have it "startkde"
|
||||
-- You may like to edit /etc/X11/xinit/xinitrc to have run "startkde"
|
||||
-- or "gnome-session" instead of twm.
|
||||
|
||||
-- note, /usr/include/GL should be a symlink to /usr/X11R6/include/GL
|
||||
-- Note: /usr/include/GL should be a symlink to /usr/X11R6/include/GL
|
||||
</screen>
|
||||
</para>
|
||||
|
||||
|
|
@ -649,7 +682,7 @@
|
|||
-- where you want it to live:
|
||||
cd /usr/local
|
||||
tar -xvzf qt-x11-2.2.3.tar.gz
|
||||
ls -s qt-2.2.3 qt
|
||||
ln -s qt-2.2.3 qt
|
||||
cd qt
|
||||
</screen>
|
||||
</para>
|
||||
|
|
@ -894,6 +927,12 @@
|
|||
</screen>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
If you experience trouble with Java, you can try deleting ~/.java and related files in
|
||||
your home directory, then try again. These files left over from a prior Java installation
|
||||
can cause problems.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
If all works well, you should have a complete Java Developement and Runtime Environment for
|
||||
both normal apps and high-performance 3D apps.
|
||||
|
|
|
|||
Loading…
Reference in New Issue