================================
 Reference Notes for Redhat 9.0
================================

Redhat 9.0 has some issues out of the box that are not commonly seen
from a distribution, and in order to save time for customers, we are
going to document the problems we encountered.  Fortunately, these
problems are documented, as well as the solutions, but we are going to
list them all here for consistency.

Issue (Resolved)
----------------
FTP installations of Redhat require an update image from Redhat.
Refer to the following URL for information and a fix:

http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=88884

Issue (Resolved)
----------------
Redhat has decided to not maintain the /usr/src/linux softlink.
Instead, they have created a /usr/src/linux-2.4 link.  Other
distributions still maintain the first style of link, thus our
Makefile is going to stay that way.  If you find the module will not
compile, you can edit the Makefile to reflect this change, (add the
-2.4) or create the soft link in the /usr/src directory.

Issue (Resolved)
----------------
The default state of the kernel source for Redhat 9.0 is unstable, and
in an indeterminate state.  If someone attempts a kernel compile it
will error out.  The solution is to issue a `make mrproper` in the
kernel source directory to clean out this problem.  Then, remaking the
configuration using `make menuconfig` and then immediately quitting
saving the changes will create the correct .config file, and allow for
module compilation.

Issue (Resolved)
----------------
Another "feature" of Redhat 9.0 is the addition of a "custom" tag to
all versions of the kernel compiled with their source tree.  This
causes modules that are compiled using their source not to install
because of a "different revision" error in the kernel.  Modules can be
forced to install, which really has no problem considering they have
been built for the same version of the kernel.  It is simply another
Redhat created issue.  If you choose to not rebuild the kernel, and
wish to pursue the forcing of modules, you can edit the load script
for seaio and add a --force option to the insmod command.

These are the issues that I found.  If there are more, please feel
free to contact us, and we will resolve them and add them to the list.
Email us at support@sealevel.com.

Thanks!

Sealevel Systems
