similar to: mkdiskimage question (another one?)

Sorry to bother you, but i want to use your genious memdisk feture, but i am not able to create a hdimage that is compatible with memdisk (see ML postings). I am not a Linux newbie, i maintain a project at [1], so i cannot be too stupid in making the image. I really tried it for some weeks to create such an image, i am not able to get a working image. It would be nice if you can send me a step

Hi, I don't know if that is intentional or a bug: ---<snip>--- DEFAULT 1 DISPLAY /isolinux/txt/message.txt PROMPT 1 F1 /isolinux/txt/about.txt F2 /isolinux/txt/message.txt ---<snap>--- if i boot into the system and press F2 i get about.txt. then i press F2 and get message.txt again. If i then press F1 again i do not get as expected the about.txt file, i just get another boot:

--- utils/mkdiskimage.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/utils/mkdiskimage.in b/utils/mkdiskimage.in index 533193a..a95a077 100644 --- a/utils/mkdiskimage.in +++ b/utils/mkdiskimage.in @@ -218,7 +218,7 @@ $totalsize = $c*$h*$s; $tracks = $c*$h; # If -s is given, try to simply use truncate... -unless ($opt{'s'} && truncate(OUTPUT,

I was trying to setup dsl (damn small linux) to boot off a usb drive. I found my BIOS wasn't booting from it when using a USB-HDD mode so I found a page for using SYSLINUX to set it up in USB-ZIP mode (http://syslinux.zytor.com/usbkey.php). I made a mistake and (doing exactly what the page warned against not doing) used the mkdiskimage command on the wrong drive (a 230Gb NTFS external

utils/mkdiskimage.in: With option -s: Avoid zeroizing the partition even if truncate() failed. --- utils/mkdiskimage_patched_01.in 2014-01-30 20:43:02.000000000 +0100 +++ utils/mkdiskimage.in 2014-01-30 20:45:09.000000000 +0100 @@ -217,8 +217,11 @@ print OUTPUT "\x55\xaa"; $totalsize = $c*$h*$s; $tracks = $c*$h; -# If -s is given, try to simply use truncate... -unless

Sorry for the delay, I should not send email on an holiday week-end. I'll try to answer all the questions by explaining what does work for me right now, and what I'd like to do. I have a script to create the a USB stick or an ISO image. The boot media contains many DOS images, and I use versamenu to select one of them. If my DOS image is smaller than 8megs, everything is working fine as

utils/mkdiskimage.in: New option -S to sync zeroizing after each cylinder and to issue pacifier messages. --- utils/mkdiskimage_patched_03.in 2014-01-30 20:54:27.000000000 +0100 +++ utils/mkdiskimage.in 2014-01-30 20:59:19.000000000 +0100 @@ -139,6 +139,7 @@ if ( $file eq '' || $c < 1 || $h < 1 || print STDERR " -4 use partition entry 4 (standard for

Hi, I did found the problem, a combination of 2 factor. 1- I taught that I did install the latest syslinux, but in fact it was the 3.36 version. 2- Thank to kevin Connelly, he point me to a problem he got with mkdosfs command. The default FAT16 do not work, but the FAT12 do. By adding -F12 to the mkdosfs command fix the problem. The default F16 do seem to work for <8M floppy image. Thank you

utils/mkdiskimage.in: Option -s caused freshly created image files to be too small by a factor of 512. --- utils/mkdiskimage_orig.in 2014-01-23 12:23:34.000000000 +0100 +++ utils/mkdiskimage.in 2014-01-30 20:35:13.000000000 +0100 @@ -218,7 +218,7 @@ $totalsize = $c*$h*$s; $tracks = $c*$h; # If -s is given, try to simply use truncate... -unless ($opt{'s'} && truncate(OUTPUT,

utils/mkdiskimage.in: Replaced the partly linux-specific file size determination by a sysseek() experiment. --- utils/mkdiskimage_patched_02.in 2014-01-30 20:49:46.000000000 +0100 +++ utils/mkdiskimage.in 2014-01-30 20:50:59.000000000 +0100 @@ -19,6 +19,7 @@ use bytes; use integer; use Fcntl; +use Fcntl qw(:seek); use Errno; use Cwd; use IO::Handle; # For flush() @@ -116,15 +117,8 @@ if (

Hi, i too played with mkdiskimage in order to get more Linux examples. When i applied it to a real 2 GB stick with write speed 4 MB/s i had enough time to add some pacifier code to the big zeroizer loop. (-s does not prevent zeroizing on block device. Probably because truncate() fails.) My pacifier is combined with what Perl advised me when i tried "fsync(OUTPUT);". Of course this

Hi, this is the diff which i consider a halfways reasonable solution for the following problems with mkdiskimage: 1. Ignoring option -s if the target file is not suitable for truncate(). 2. Miscalculation of truncate() size by a factor of 512. 3. The storage capacity of device files can only be measured for Linux block devices. 4. Long time of silent work when slow devices (e.g. USB

Hi, me: > > [mkdiskimage] -s does not prevent zeroizing on block device. Probably > > because truncate() fails. hpa: > Yes, we should probably fix that. The tool was originally designed for > images, not for hardware devices, and it doesn't make much sense to zero > the whole hardware device like that. Maybe for privacy reasons ? But indeed: -s should skip zeroizing,

Hi, I'm trying to make a USB-ZIP bootable filesystem on my USBkey, which is 2GB. The problem is that "mkdiskimage -4 /dev/sda 0 64 32" fails due to the large size. The number of sectors is 4005888/(64*32) = 1956, which is more than the maximum 1024. Is there any way around this or is it just not possible to make this USBkey look like a Zip drive? Regards, Ole Jacob

I have had a problem with mkdiskimage for quite a while. It seems to always exit with the syntax messages. I'm not really familiar enough with Perl to figure out exactly what it's checking for there that it determines is incorrect, but, my guess would have to be that it doesn't like the letter. Eg, I think the last time it suceeded I was running it on sda, but, not I'm typically

> It is based on > http://git.kernel.org/cgit/boot/syslinux/syslinux.git/tree/utils/mkdiskimage.in?id=syslinux-6.03-pre1 Just a thought (FWIW). Perhaps it could be useful to base it on the syslinux4-xx branch: http://git.zytor.com/?p=syslinux/syslinux.git;a=tree;h=refs/heads/sysl inux-4.xx;hb=syslinux-4.xx http://git.zytor.com/?p=syslinux/syslinux.git;a=blob_plain;f=utils/mkd

On 01/23/2014 08:47 AM, Thomas Schmitt wrote: > Hi, > > i too played with mkdiskimage in order to get more Linux examples. > > When i applied it to a real 2 GB stick with write speed 4 MB/s > i had enough time to add some pacifier code to the big zeroizer > loop. (-s does not prevent zeroizing on block device. Probably > because truncate() fails.) > Yes, we should

Op 2014-01-30 om 21:54 schreef Thomas Schmitt: > Hi, > > following is a series of patches derived from my proposed diff. > Based on syslinux-6.03-pre1, but should also apply down to 4.xx. > > I hope to have imitated the changelog style sufficiently. > Mine are a bit longer than usual with patches in the archive, i fear. Yes, they are long. > Instructions for the future

Hi, me: > >> I hope to have imitated the changelog style sufficiently. > >> Mine are a bit longer than usual with patches in the archive, i fear. Geert Stappers: > > Yes, they are long. H. Peter Anvin: > There seems to be no patch descriptions at all, which would really help > long-term maintainability. It is a mid-term while ago since i proposed these patches.

Hi Maybe HPA or Murali could help me with this one, or anyone who got the following working. I spend numerous hours reading the list and googling without success. I'd like to create a bootable USB stick and CDROM that will do the following. I will have a menu, from which I could pick a specific dos image (not partition). The dos images could have up to 20Megs in size. The goal is to have