I am trying to make a bootable cd for an updated version of the kernel (2.6.10-1.12) on a machine running Fedora Core 2. This machine dual boots with Win XP and I have never been able to get dual boot to work on it. So I use a bootable CD for Linux and allow the ntloader to just do its thing for Win XP.
But, when I try to use mkbootdisk to create the iso image for the new bootable cd I always get an error. Command and typical output looks like this:
Code:
mkbootdisk --iso --verbose --device bootcd.iso 2.6.10-1.9_FC2
Installing isolinux... done
Copying /boot/vmlinuz-2.6.10-1.9_FC2... done.
Copying /boot/initrd-2.6.10-1.9_FC2.img... done.
Configuring bootloader... done.
Unknown file type (unallocated) /tmp/mkbootdisk.XG2317/.. - ignoring and continuing.
I have executed this command several times in the past with exactly these options. I know that I am using the same options because I wrote a script to make the iso image, use cdrecord to blank a rewritable cd and then use cdrecord to burn the iso image to the cd.
For some reason I do not understand, I now always get the error shown above when making the bootable iso image.
Indeed no file is being written into the /tmp directory. The first time that I ran the command I did an ls /tmp and saw files with similar names but different hash characters after the dot. I probably should have done an ls -l after that and looked at the creation dates, but being root, I deleted all the files in /tmp that I could (that included all of the mkbootdisk.* files), and reran the command. No new Mkbootdisk.* files showed up in the /tmp directory.
The problem is not permissions on the /tmp directory,
Code:
ls: ls: No such file or directory
/:
total 300
/* Several lines deleted for brevity */
drwxrwxrwt 13 root root 63488 Feb 3 21:05 tmp
/* Several lines deleted for brevity */
So, the /tmp directory is owned by root:root, and all users have read, write, and execute permissions. Although non-root users may only remove their own files from the directory. In any case, root is attempting to use the mkbootdisk command above.
Nor is the problem a full /tmp partition, as evidenced by the df command,
Code:
df /tmp
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/hdb8 497829 8340 463787 2% /tmp
I would be eternally grateful if anyone could shed some light on this problem.