An issue exists with the IA32 20100925 Install/Rescue disk.
The provided SMP kernel is configured to boot only on CPUs
that support the PAE instruction set.
Sorry.
This was not intentional.
The next Install/Rescue image should again
be possible to install on i586 and i686 CPUs
that lack PAE instructions.



Please do all installations with the 20100925 Install/Rescue
images if a newer image is not available for download.
Bug reports are not accepted
and fixes are not provided
Install/Rescue images
that are older than the most recent release.

A very minor known issue exists on the
version 20100925 Install/Rescue disks.

After installation is complete
and on the first boot the init-script
/etc/init.d/loadkeys will attempt to
run the loadkeys program during sysinit,
but loadkeys will not be present on the
initramfs because it will reside as
/usr/bin/loadkeys on the root filesystem.
Logging in and running /etc/init.d/loadkeys start
will accomplish loading a keyboard mapping
after logging in.

On the first update of the installed box
or soon after kbd will recast and have
loadkeys installed as /bin/loadkeys

The above issue is not significant and
will not prevent installation.
It was merely a mistake discovered too late
that lacks sufficient gravity to delay the
release of new Install/Rescue images by another day or two.



A known issue exists on the
version 20100529 Install/Rescue disks.

Updating LVM2 to version 2.02.73 can cause partitions
not part of logical volumes to become locked when
/etc/init.d/vgchange executes during sysinit during boot.
If this happens then file systems will not check
and the locked partitions will not mount.
Provided that that a box was not installed using
logical volumes
then the temporary solution is to boot with kernel parameter
rdinit=/bin/bash
Then remove the symbolic link in /etc/rc.d/rcS.d
that executes vgchange.
Then execute exec /init
After the box boots
then execute
chmod 600 /etc/init.d/vgchange.

Another solution that might work is to update to
LVM2 version 2.02.74


If running the menu driven installer
then please boot with floppy disk disabled in BIOS/CMOS
or after booting log in as root and first run:

sed -i 's:fd\[0-9\]\$:fd[0-9]:' /sbin/sinstall

The above command fixes the sed command
which removes floppy disk device nodes
from the block devices discovered in /dev

Alternatively,

# rm /dev/fd*

Will probably also work.

Sorry for the inconvenience.