United States (change)
Shortcuts: Downloads Fedora Red Hat Network
Important Red Hat, Inc. is not releasing security upgrades specific for this version of Red Hat Linux anymore. Users of Red Hat Linux 4.0 should upgrade to either Red Hat Linux 4.2 or Red Hat Linux 5.1, and apply the errata updates from ftp.redhat.com/pub/redhat/updates/.
The following are known problems with Red Hat Linux 4.0 on multiple platforms. Updates are available for FTP from:
Please note that newer versions of some of these packages may be available in the same location; any new versions which are made available will fix all of the bugs older versions did, so you can use the latest version with no problems.
We are no longer seperating the errata into general and platform specific
errata If you are unsure whether an errata update is for your system, the
following information should help:
Intel and Intel-based platform specific rpms will have the i386 extension,
Sparc rpms will have the sparc extension, and rpms for the Alpha systems
will have the alpha extension. This extension is before .rpm. For example:
foo.1.2-3.i386.rpm would be for the Intel systems
foo.1.2-3.sparc.rpm would be for Sparc systems
foo.1.2-3.alpha.rpm would be for Alpha systems
Updated: 04-Oct-1996
Problem:
Solution:
Updated: 04-Oct-1996
Problem:
Note:
rpm -ev rdate
Solution:
Updated: 15-Oct-1996
Problem:
Solution:
Updated: 15-Oct-1996
Problem:
Solution:
Updated: 15-Oct-1996
Problem:
Solution:
Updated: 16-Oct-1996
Problem:
Solution:
Updated: 18-Oct-1996
Problem:
Solution:
Versions of Red Hat Linux earlier than 2.0 cannot be upgraded in place; a complete reinstallation is necessary.
Updated: 18-Oct-1996
Problem:
Solution:
Updated: 18-Oct-1996
Problem:
Note:
chmod 0644 /etc/resolv.conf
Solution:
Updated: 18-Oct-1996
Problem:
Solution:
Updated: 21-Oct-1996
Problem:
Solution:
Updated: 21-Oct-1996
Problem:
Solution:
Updated: 21-Oct-1996
Problem:
Solution:
Updated: 21-Oct-1996
Problem:
Solution:
Updated: 22-Oct-1996
Problem:
Solution:
touch /var/log/wtmp
Updated: 23-Oct-1996
Problem:
Correction:
controller_type=type base_address=shmemaddr irq=irqwhere:
type is 1 for Seagate, or 2 for Future Domain;
shmemaddr is the address of the shared memory segment (for example, 0xCA000);
and irq is the number of the IRQ line.
Updated: 23-Oct-1996
Problem:
Solution:
Updated: 23-Oct-1996
Problem:
Solution:
Updated: 23-Oct-1996
Problem:
Solution:
Updated: 23-Oct-1996
Problem:
Solution:
Updated: 25-Oct-1996
Problem:
Solution:
Updated: 25-Oct-1996
Problem:
Solution:
Updated: 25-Oct-1996
Problem:
Solution:
Updated: 25-Oct-1996
Problem:
Solution:
Updated: 25-Oct-1996
Problem:
Solution:
Updated: 28-Oct-1996
Problem:
Solution:
Updated: 31-Oct-1996
Problem:
Solution:
rpm --qf '%{POSTIN}' $(rpm -q --whatrequires pamconfig) | sh -xUpdated: 19-Nov-1996
Problem:
Solution:
Updated: 19-Nov-1996
Problem:
Solution:
Updated: 19-Nov-1996
Problem:
Solution:
Updated: 25-Nov-1996
Problem:
Solution:
chmod u-s /usr/X11R6/bin/SuperProbe
Updated: 18-Dec-1996
Problem:
Note:
Solution:
Updated: 18-Dec-1996
Problem:
Solution:
Updated: 18-Dec-1996
Problem:
Solution:
Updated: 18-Dec-1996
Problem:
Solution:
Updated: 20-Dec-1996
Problem:
Note:
Correction:
rm -rf /lib/modules/2.0.18-old
mv /lib/modules/2.0.18 /lib/modules/2.0.18-old(This is the step that was omitted)
cp /usr/src/linux/arch/i386/boot/zImage /boot/vmlinuz-2.0.18-custom
ln -sf vmlinuz-2.0.18-custom /boot/vmlinuz
gzip -9 /usr/src/linux/vmlinux
cp /usr/src/linux/vmlinux.gz /boot/vmlinux-2.0.18-custom.gz
ln -sf vmlinux-2.0.18-custom.gz /boot/vmlinux.gz
Updated: 20-Dec-1996
Problem:
Correction:
Updated: 22-Jan-1997
Problem:
Note:
to read:HOSTNAME=localhost
HOSTNAME=localhost.localdomain
Solution:
Updated: 28-Jan-1997
Problem:
Solution:
First, you need to choose one boot image:
boot1542.img.gz Adaptec 1542 adaptors that need parameters
boot1740.img.gz Adaptec 1740/1742 adaptors
bootaic7xxx.img.gz Adaptec 2740, 2840, 2940, 3940, and friends
bootaic7xxx-alt.img.gz Alternate aic7xxx driver if the normal one fails
boot2940au.img.gz Adaptec 2940AU adaptor
bootadvansys.img.gz All supported Advansys adaptors
bootFlashPoint.img.gz *Beta-test* BusLogic FlashPoint adaptors
booteata_dma.img.gz DPT EATA-DMA adaptors
boot53c8xx.img.gz NCR/Symbios 53c8xx adaptor
bootpas16.img.gz ProAudioSpectrum 16 SCSI
bootultrastor24.img.gz UltraStor 24F adaptor
bootwd7000.img.gz Western Digital 7000 FASST adapters
These boot images are all available from ftp://ftp.redhat.com/pub/redhat/updates/4.0/i386/images/scsi/.
The boot image bootaic7xxx-alt.img.gz is built with the aic7xxx driver from the linux-2.0.12 kernel. Some aic7xxx cards which do not work with the current aic7xxx driver worked with the old one, so if the new one does not work for you, you can try the old one.
The boot image boot2940au.img.gz is built with the aic7xxx driver and the pci driver from the Linux-2.0.27 kernel. The Adaptec AHA-2940AU has a different programming interface than earlier 2940 cards, and requires a new driver. We hope this version works, but we don't have a 2940AU to test it with, and so we can't be sure. See README.2940au.
The Adaptec 1542 driver is not affected by the bug, but the 1542 driver cannot take command-line arguments when it is compiled as a module. Normally, it needs no arguments, but if you need to pass it arguments, you will need to use this boot disk.
The BusLogic driver is not affected by the bug; however, this BETA-test update provides FlashPoint support, and needs to be installed in the same way as the other drivers here. (FlashPoint adaptors are not supported by the standard kernel.) This is a BETA-quality driver.
Use these steps to take advantage of the correct boot image for you:
where "sd??" is the root partition (/) on which you installed Linux.linux root=/dev/sd?? load_ramdisk=0 prompt_ramdisk=0
mount -t ext2 /dev/fd0 /mnt/floppy
cp /mnt/floppy/vmlinuz /boot/vmlinuz
/sbin/lilo
/sbin/shutdown -r now
At this point, you should have a working Linux system.
Updated: 17-Feb-1997
Problem:
Note:
Solution:
Updated: 03-Mar-1997
Problem:
Note:
If you don't use the --ignorearch option, rpm will complain that the package is for the incorrect architecture.rpm -Uvh --ignorearch imap-4.1.BETA-3.alpha.rpm
Solution:
Updated: 23-Mar-1997
Problem:
Note:
Because the Alpha package was built using a recent version of rpm, Linux/Alpha users need to upgrade using the following command:
If you don't use the --ignorearch option, rpm will complain that the package is for the incorrect architecture.rpm -Uvh --ignorearch cmu-snmp-3.3-1.alpha.rpm
Solution:
Updated: 01-Apr-1997
Problem:
Note:
rm -f /etc/.pwd.lock
This enables system administrators to relax password security on their systems.passwd password required /lib/security/pam_unix_passwd.so strict=false
rpm --nodeps
Solution:
If you are upgrading from a version of PAM earlier than pam-0.50-20, remove all the entries for login, rsh, rlogin, and rexec from /etc/pam.conf. You can use the following script to do so; simply cut and paste:rpm -q pam
#!/bin/sh
gawk 'BEGIN {RS="\n\n+"}
$0 ~ / login authorization/ { next }
$0 ~ / rlogin authorization/ { next }
$0 ~ / rsh authorization/ { next }
$0 ~ / rexec authorization/ { next }
{ print ; printf "\n" }' < /etc/pam.conf > /tmp/pam.conf
cat /tmp/pam.conf > /etc/pam.conf
rm /tmp/pam.conf
Or, simply remove the equivalent entries by hand using your
favorite text editor.
Updated: 02-Apr-1997
Problem:
Note:
If you don't use the --ignorearch option, rpm will complain that the package is for the incorrect architecture.rpm -Uvh --ignorearch inn-1.5.1-6.alpha.rpm
Solution:
Updated: 09-Apr-1997
Problem:
Solution:
Updated: 24-Apr-1997
Problem:
Note:
If you don't use the --ignorearch option, rpm will complain that the package is for the incorrect architecture.rpm -Uvh --ignorearch perl-5.003-8.alpha.rpm
Solution:
Updated: 28-Apr-1997
Problem:
Note:
If you don't use the --ignorearch option, rpm will complain that the package is for the incorrect architecture.rpm -Uvh --ignorearch metamail-2.7-7.alpha.rpm
Solution:
Updated: 15-May-1997
Problem:
Note:
If you don't use the --ignorearch option, rpm will complain that the package is for the incorrect architecture.rpm -Uvh --ignorearch elm-2.4.25-8.alpha.rpm
Solution:
Updated: 29-May-1997
Problem:
Applications which are dynamically linked may be fixed by upgrading to the X...-libs package appropriate for your architecture.
If you have any statically linked setuid X programs you must recompile them against the new libX11.a contained in the X...-devel package for your architecture. Red Hat Linux does not include any statically linked X applications, so this only a problem if you've hand installed statically linked setuid applications (we don't know of any applications likely to be installed in this configuration).
Applications which are dynamically linked may be fixed by upgrading to the X...-libs X package appropriate for your architecture.
If you have any statically linked setuid X programs you must recompile them against the new libX11.a contained in the X...-devel package for your architecture. Red Hat Linux does not include any statically linked X applications so this only a problem if you've hand installed statically linked setuid applications (we don't know of any applications likely to be installed in this configuration).
Note:
Solution:
Updated: 27-Jun-1997
Problem:
Solution:
Updated: 18-Jul-1997
Problem:
Solution:
Updated: 21-Jul-1997
Problem:
Note:
If you don't use the --ignorearch option, rpm will complain that the package is for the incorrect architecture.rpm -Uvh --ignorearch bind-4.9.6-1.alpha.rpm
Solution:
The install program will prompt you to install other operating systems to be bootable from SILO. Unfortunately, this option is broken and should not be used.
Fix: You should only setup SILO to boot Linux. If you need to boot SunOS or Solaris, you can add support for that after installing and booting your system for the first time. See /usr/doc/silo-0.6.5-1/README for details on how to modify /etc/silo.conf for booting Solaris and SunOS.
You may still be able to boot SunOS by issuing the following at the SILO boot: prompt:
boot: /boot/old.bYou should still be able to boot Solaris using the PROM prompt. To get out of SILO type:
boot: halt
If you are doing a CD-ROM install without a floppy (ie you put the CD in the local drive and did a boot cdrom from the PROM prompt) you will not be able to install across multiple partitions.
Fix: You must use one large partition to hold everything. This is due to a bug in the install program. Because it is burnt on the CD, there is no way to fix it until we go to a new release.
You can install to multiple partitions if you boot via
the floppy or if you do an NFS install. It even works if you do an
NFS rooted install from the CD-ROM mounted on an NFS server.
The kernel as shipped with Red Hat Linux/SPARC 4.0 can not share the
mouse device between programs. The gpm package as installed
will start gpm at boot time. You can not start X until you kill gpm.
Fix: Kill gpm using the following command:
The kernel as shipped with Red Hat Linux/SPARC 4.0 can not handle
IPX networking properly. If your machine is connected to a network
where IPX traffic exists, Linux will load the IPX module, and your
machine will enventually crash.
Fix: Remove the offending module so that it cannot load,
using the following command:
Note: IPX networking works properly on Red Hat Linux/SPARC 4.0
with the most recent kernel-sparc fix
/etc/rc.d/init.d/gpm stop
You can then start gpm again when you aren't running X by:
/etc/rc.d/init.d/gpm start
If you would like to remove gpm from the startup scripts so that it
does not start at boot time, but you would still like to
be able to start it when you wish, simply do:
rm -f /etc/rc.d/rc?.d/S*gpm
Then start and stop gpm with the above commands when you need to
use it. If you would like to remove gpm entirely and never use it,
first stop it and then run:
rpm -e gpm
rmmod ipx
rm -f /lib/modules/2.0.18/misc/ipx.o
Then add the following line to /etc/conf.modules:
alias net-pf-4 off
Finally, restart kerneld:
killall kerneld
/sbin/kerneld
23-Oct-1996