similar to: [PATCH 00/05] Mending for mkdiskimage

--- 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,

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

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

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

On 07/10/2014 12:18 PM, Geert Stappers wrote: >> >> 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. > There

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.

On 07/11/2014 12:33 AM, Thomas Schmitt wrote: > Technical side note: > It turned out that the lseek(2) function of NetBSD does not work > with SEEK_END as expected from the manual. libburn had to resort > to a binary search with try-and-error to determine device sizes. > I did not check perl's sysseek() whether it suffers from the > lseek(2) shortcomming, but i would expect

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

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, 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,

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 (

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,

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

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

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

On Mon, Jun 17, 2013 at 10:29 AM, Jeffrey Walton <noloader at gmail.com> wrote: > > > First is to ensure dead-writes are not removed. For example, a > function that zeroizes or wipes memory is subject to removal during > optimization. I often have to look at program's disassembly to ensure > the memset is not removed by the optimizer. > Appropriate use of `volatile`

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

Hallo, Mattias, Du meintest am 28.01.14: >> 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. > Probably not. But a left over backup GPT at the end of a "disk" (hard > disk, thumb drive, SSD, eMMC) now confuses some UEFI

On Mon, Jun 17, 2013 at 6:23 PM, Sean Silva <silvas at purdue.edu> wrote: > On Mon, Jun 17, 2013 at 10:29 AM, Jeffrey Walton <noloader at gmail.com> wrote: >> First is to ensure dead-writes are not removed. For example, a >> function that zeroizes or wipes memory is subject to removal during >> optimization. I often have to look at program's disassembly to