Re: Changing boot.img

[Michael Fratoni <mfratoni tuxfan homeip net>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 30 May 2002 07:39 am, Chapman, Matt wrote:

> I have done the following.  Opened up the boot.img from cd1 by the
> following command:
>
> mount -o loop boot.img /home/matt/temp
>
> Then I cd to that dir and changed the text in the *.msg file.  Then
> umount /home/matt/temp
>
> I then do a syslinux (new version) to the boot.img file to update it to
> the new sysimage...
>
> I then burn my cd with the appropriate commands.  When I boot my cd I
> get my changed text but then it says "missing or corrupt kernel"  Now
> before you ask... I did not touch the initrd.img or the vmlinuz file at
> all!
>
> Any ideas?  Am I mounting it wrong.

If all you have done is modify the *.msg files, there should be no need to 
run syslinux.

When creating bootable images, I generally format the disk (must be a dos 
file system) then run syslinux, then add the remaining files.

Here is a snip from a script I use to create a boot disk:
mformat a: || {
    echo "Error formatting the floppy disk, exiting."
    exit
}
echo "Running syslinux."
syslinux -s /dev/fd0 || {
    echo "Error running syslinux, exiting."
    exit
}
echo "Copying files."
mcopy base_files/syslinux.cfg a:
mcopy base_files/boot.msg a:

echo "Copying rootfs.gz."
mcopy rootfs.gz a:

echo "Copying the kernel."
mcopy base_files/vmlinuz-rule a:vmlinuz


- -- 
- -Michael

pgp key:  http://www.tuxfan.homeip.net:8080/gpgkey.txt
Red Hat Linux 7.2 in 8M of RAM: http://www.rule-project.org/
- --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iEYEARECAAYFAjz220AACgkQn/07WoAb/SuXDgCghzIe/eAl++Mthy+VGl0NYl3i
z3sAoJ+OFsrcgrRDnj2DxQwMmycHjC0L
=V2vV
-----END PGP SIGNATURE-----