Hi:
Two scripts (mkbd.fails and mkbd.works) are attached to this message. The only
difference between them is in how syslinux.cfg (on a RedHat boot image) is
replaced.
mkbd.fails: syslinux.cfg is replaced via "mv -f". vmlinuz can't be
found.
mkbd.works: syslinux.cfg is replaced via "cp". vmlinuz is found.
The only difference I can see between these two methods is that "mv
-f" has the
potential to change the layout of the FAT whereas "cp" ensures that
the layout
of the FAT doesn't change. This, in turn, implies that there's a
defficiency in
how syslinux searches the FAT for vmlinuz.
N.B.: This problem is manifested when applying mkbd to the RH7.3 boot.img but
not when applying it to the RH7.2 boot.img.
--
Dave Mielke | 2213 Fox Crescent | I believe that the Bible is the
Phone: 1-613-726-0014 | Ottawa, Ontario | Word of God. Please contact me
EMail: dave at mielke.cc | Canada K2A 1H7 | if you're concerned about
Hell.
http://familyradio.com
-------------- next part --------------
#!/bin/sh
set -e
# Make local mount points
mkdir -p mnt1 mnt2
# Work on a copy of bootdisk image
cp -f boot.img myboot.img
mount myboot.img mnt1 -o loop -t msdos
# Modify syslinux.cfg
cat >cfg <<EOF
label brltty
kernel vmlinuz
append root=/dev/fd0 load_ramdisk=1 prompt_ramdisk=1 lang= text devfs=nomount
ramdisk_size=7168
EOF
cat mnt1/syslinux.cfg |sed 's/default linux/default brltty/' >>cfg
mv -f cfg mnt1/syslinux.cfg
umount mnt1
-------------- next part --------------
#!/bin/sh
set -e
# Make local mount points
mkdir -p mnt1 mnt2
# Work on a copy of bootdisk image
cp -f boot.img myboot.img
mount myboot.img mnt1 -o loop -t msdos
# Modify syslinux.cfg
cat >cfg <<EOF
label brltty
kernel vmlinuz
append root=/dev/fd0 load_ramdisk=1 prompt_ramdisk=1 lang= text devfs=nomount
ramdisk_size=7168
EOF
cat mnt1/syslinux.cfg |sed 's/default linux/default brltty/' >>cfg
cp cfg mnt1/syslinux.cfg
umount mnt1