similar to: mkbootdisk error????

I'm trying to make a bootdisk in my CentOS server and I got this error.. any ideas? [root at server:~]$ rpm -qa kernel kernel-2.6.9-5.0.3.EL [root at server:~]$ mkbootdisk 2.6.9-5.0.3.EL --device /dev/fd0 Insert a disk in /dev/fd0. Any information on the disk will be lost. Press <Enter> to continue or ^C to abort: cp: writing `/tmp/mkbootdisk.d20227/initrd.img': No space left on

4.1 x86_64 doesn't contain a mkbootdisk rpm Then, How do I make a bootdisk easily ? (I know how to use grub to make the bootdisk.) But any other easier method ? Thx !

First, I thanks you all for your answers. Step by step what I did. 1. Install from CD1 CentOS mkisofs-2.01.1-5.i386.rpm 2. create the file /tmp/2.6.9-5.0.3.EL.iso 3. run mkbootdisk --device /tmp/2.6.9-5.0.3.EL.iso --iso 2.6.9-5.0.3.EL 4. Burn this ISO image to a CD. That's it!! regards, israel

Hi, we are the developers of an alternative to mkisofs: program xorriso from libburnia-project.org . The current development cycle is about support for creating bootable CDs, DVDs, BDs. So we look for testers and for advise about ISOLINUX specifics. The example from the ISOLINUX wiki is supposed to work if you replace "mkisofs" by "xorriso -as mkisofs". I.e: xorriso -as

i tried to make a bootable CD with isolinux,but met some problem. the error is as follows. i don't know what cause the problem. anyone met the same problem? thanks for help. ===================================================================================== mkisofs 1.13 (i686-pc-linux-gnu) Scanning . Scanning ./boot Scanning ./isolinux Scanning ./isolinux/help Excluded by match:

On 05/03/2016 12:27 AM, Geert Stappers via Syslinux wrote: > On Mon, May 02, 2016 at 11:21:13PM -0400, John Lewis via Syslinux wrote: >> I was trying to follow this tutorial >> https://help.ubuntu.com/community/LiveCDCustomizationFromScratch. i got >> confused with the part about Create an isolinux.cfg file. >> >> The show stopper for me was the mkisofs because the

Hi, I am not sure if this is an isolinux problem or an mkisofs problem. I have been using isolinux for a year now without any problems. This week, it began to fail. The only difference is that the CD has a few more files on it than before (1026 files, 327 MB). mkisofs was creating the image alphabetically, and the isolinux directory was at the very end. I then tried using the -sort parameter

There seems to be several problems in this kickstart cd document. I guess this was copied from RedHat''s documentation. Can someone please direct me or my comments to the right person? http://www.centos.org/docs/5/html/Installation_Guide-en-US/ch02s04.html#s2-steps-make-cd this command (in the documentation) needs a space in it: cp -r

Hello, I have a simple shell script that I use to generate an iso installer depending on the release version that I want. The thing is that I extract isolinux and menu.c32 from the syslinux rpm of the latest redhat release. The reason I am doing it this way is because of the This is what does it: copymenu32() { # $ cat /local/kickstart/templates/os-updates.txt # RedHat-5.8|20120425

CentOS Errata and Bugfix Advisory 2012:0403 Upstream details at : https://rhn.redhat.com/errata/RHBA-2012-0403.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 5b2edeab8b2bf0340e5762057737c072f9da512510b27c92e8ba68058b0a9784 mkbootdisk-1.5.5-3.el6.i686.rpm x86_64:

Hello, I want to modify isolinux.cfg of a given, bootable iso (of Linux CentOs installation) according to my needs. The things is : I copy the contents of that iso to a different directory. I modify the isolinux.cfg according to my needs. Then what? I had of course googled for it. I had tried afterwards: mkisofs -o centos1.iso -b isolinux/isolinux.bin -no-emul-boot -boot-load-size 4 -boot-i But

On 11/24/2013 09:56 AM, Ady wrote: >> The very early code that emits this message is *identical* between >> Syslinux 4 and Syslinux 6. The biggest difference is the size of >> isolinux.bin, so it is possible that that might be the source of the >> problem. >> >> -hpa > > I wonder if isolinux.bin should be limited to max. 16 sectors (of > 2KiB

I'm having a problem booting Slackware 10.1 boot CD's as well as an isolinux image of my own. The system is a VIA Epia M10000 and the drive is an AOpen ISU-8424E CD/DVD writer. If I use a Toshiba CD-RW/DVD-ROM Drive SD-R2612 in place of the AOpen DVD writer, the cd boots fine and everything works as expected. What's the best course for further debugging of this problem? The only

I am using the following command below to create a boot floppy file. Am I not doing the correct thing? mkbootdisk --device bootfloppy.img 2.6.9-34.0.1.EL cp: writing `/tmp/mkbootdisk.Jb5537/vmlinuz': No space left on device cp: writing `/tmp/mkbootdisk.Jb5537/initrd.img': No space left on device cat: write error: No space left on device cat: write error: No space left on device Jerry

i have file on CENTOS 4.6 and I tried to delete it failed. I have been tried following way but NOT work: rm -i * rm --filename rm \--filename rm "\--filename" rm '\--filename' any ideal? ___________________________________________________ ??????? ? ???????????????? http://messenger.yahoo.com.tw/

I have tried to use isolinux 2.05, and I am running into a problem where it will not boot. I have previously used version 1.66, and the older version works just fine. Changing nothing except dropping the new version in does not work. Below is all of the relevant info, I believe. This occurs on multiple machines with different BIOS. I am currently in process of doing a binary search to find the

Hello, I'm Jacques living in France. I have a problem when I use isolinux. I'm working on a multiboot cdrom so I make many "mkisofs" for testing. The problem is that when I modify the "isolinux.cfg" file and then build my image with mkisofs it's the previous configuration of my "isolinux.cfg" which appears on my screen (I run the .iso file with qemu...)

Hi, i think i found a suspect in lzo/prepcore.c and it would indeed be a wrong range of checksumming (speculative congratulations to Ady). Looking at http://repo.or.cz/syslinux.git/blob/0d82b71304d596d80f3c4520f9dcf90048ca50b7:/lzo/prepcore.c it seems that this change in line 374 could yield correct checksums: unsigned int ptr; - for (ptr = 64; ptr < offset; ptr += 4) +

> As stated earlier, the next version of xorriso will have > sort weight 2 for El Torito boot images by default. > But it will not harm to explicitely use --sort-weight > options with old and new versions of xorriso. FWIW, mkisofs is supposed to assign a +2 sort weight by default to the eltorito boot image and +1 to the boot catalog, at least when no sort file is provided. I

Could someone help me get the syntax for `genisoimage' and/or `xorriso' correct? Apparently it is not in many linux distros so below my little HOWTO shows how to compile it. ( which adds tons of crap that can go wrong) mkdir -p ISO_root/isolinux cp /usr/lib/syslinux/[i,m,v]* ISO_root/isolinux cat > ISO_root/isolinux/isolinux.cfg << EOF UI menu.c32 label isolinuxtests EOF # Most