search for: notrunc

...lock=507 (7ec00) transaction=15980522 Now lets say i want to go back in time on this, using the program can help me do that. If i wanted to go back in time to tgx 15980450... bash-3.00# /tmp/findUberBlock /dev/dsk/c0t1d0 -t 15980450 dd if=/dev/zero of=/dev/dsk/c0t1d0 bs=1k oseek=180 count=1 conv=notrunc dd if=/dev/zero of=/dev/dsk/c0t1d0 bs=1k oseek=181 count=1 conv=notrunc dd if=/dev/zero of=/dev/dsk/c0t1d0 bs=1k oseek=182 count=1 conv=notrunc dd if=/dev/zero of=/dev/dsk/c0t1d0 bs=1k oseek=183 count=1 conv=notrunc dd if=/dev/zero of=/dev/dsk/c0t1d0 bs=1k oseek=184 count=1 conv=notrunc dd if=/dev/...

....080d65b 100644 --- a/diag/mbr/README +++ b/diag/mbr/README @@ -7,9 +7,9 @@ handoff.bin Show the data that the BIOS/MBR hands off to an MBR/VBR. Writing out an MBR is straight forward (it is assumed below that /dev/hda is the target raw device and /dev/hda1 is the target partition): - dd conv=notrunc bs=440 count=1 if=mbr.bin of=/dev/hda + dd conv=notrunc bs=440 count=1 if=handoff.bin of=/dev/hda Writing a VBR to match Syslinux requires more work as it must have a jump and be offset into the partition: echo -en "\0353\0130\0220" |dd conv=notrunc bs=1 count=3 of=/dev/hda1 - d...

...unt=1 seek=$((0x`cat /proc/kallsyms|grep sys_vmsplice | awk {'print $1'}`)) 2)# echo -e '\xc3' | dd of=/dev/kmem bs=1 count=1 seek=$((0x`awk '/sys_vmsplice/ { print $1; }' /proc/kallsyms`)) my try: # # printf "\xC3" | dd bs=1 count=1 of=/dev/kmem conv=notrunc \ seek=$((0x`sed -n '/vmsplice$/{s; .*;;p;q}' /boot/S*p-$(uname -r) | tee /dev/stderr`)) ffffffff802cc20f dd: invalid number `-2144550385' # # dash -c 'printf "\xC3" | dd bs=1 count=1 of=/dev/kmem conv=notrunc \ seek=$((0x`sed -n "/vmsplice$/{s; .*;;p;q}" /...

...,8 @@ features): nbdkit eval \ config='ln -sf "$(realpath "$3")" $tmpdir/file' \ get_size='stat -Lc %s $tmpdir/file' \ - pread='dd if=$tmpdir/file skip=$4 count=$3 iflag=count_bytes,skip_bytes' \ - pwrite='dd of=$tmpdir/file seek=$4 conv=notrunc oflag=seek_bytes' \ + pread='dd bs=1 if=$tmpdir/file skip=$4 count=$3' \ + pwrite='dd bs=1 of=$tmpdir/file seek=$4 conv=notrunc' \ file=disk.img =head1 PARAMETERS diff --git a/plugins/sh/nbdkit-sh-plugin.pod b/plugins/sh/nbdkit-sh-plugin.pod index 07d90b57..70741139 10...

Hi, > The ISO will boot successfully (when chainloaded from grub) on 2 and > 3, but not on 5 and 6. Did you try with a boot loader other than GRUB ? Afaik, the MBRs of newly bought USB sticks often contain code which hops on the MBR code of the partition that is marked by the boot flag. At least one could exclude that your problem is in a GRUB peculiarity. Have a nice day :) Thomas

Hi @all! I have two questions: - First, am I right that the chance of getting the same 32-bit rolling checksum is 1/2^16 and to get the same 128-bit MD5 Hash is 1/2^127? - Finally I want two know if it is possible to change an amount of blocks manually? e.g. I made a 100 MB file with "dd if=/dev/zero of=/home/test.xyz bs=1M count=100" and know I want to change, lets say, 10 blocks of

...s the same and is not to be altered by copying in the # SYSLINUX boot sector. BSCOPYSTART=11 BSCOPYLEN=51 # xpread(dev_fd, sectbuf, 512, offset); # memcpy(bootsect+bsCopyStart, sectbuf+bsCopyStart, bsCopyLen); # xpwrite(dev_fd, bootsect, 512, offset); $DD if=$IMAGE of=$TEMP bs=512 count=1 $DD conv=notrunc if=ldlinux.bss of=$IMAGE bs=512 count=1 $DD conv=notrunc if=$TEMP of=$IMAGE bs=1 seek=$BSCOPYSTART skip=$BSCOPYSTART count=$BSCOPYLEN rm $TEMP grep -v "#TEMP" $MTOOLSRC > $MTOOLSRC.NEW mv $MTOOLSRC.NEW $MTOOLSRC -- Seth David Schoen <schoen at loyalty.org> | Reading is a right...

Is there a way to find the holes in sparse files, other than assuming contiguous blocks of zeroes are holes? Thanks, Sean

To reproduce the bug: # mount -o nodatacow /dev/sda7 /mnt/ # dd if=/dev/zero of=/mnt/tmp bs=4K count=1 1+0 records in 1+0 records out 4096 bytes (4.1 kB) copied, 0.000136115 s, 30.1 MB/s # dd if=/dev/zero of=/mnt/tmp bs=4K count=1 conv=notrunc oflag=direct dd: writing `/mnt/tmp'': Input/output error 1+0 records in 0+0 records out btrfs_ordered_update_i_size() may return 1, but btrfs_endio_direct_write() mistakenly takes it as an error. Signed-off-by: Li Zefan <lizf@cn.fujitsu.com> --- fs/btrfs/inode.c | 3 +-- 1...

...n-8.7.0-i386-DVD-1.iso. I can boot these with qemu. But where > shall I insert this creation of mine. Just overwrite the first 432 bytes of the ISO. Make a backup of the original bytes, so you can restore it later. dd bs=1 count=432 if=debian-8.7.1-i386-xfce-CD-1.iso of=mbr.backup dd conv=notrunc bs=1 count=432 if=your_test_mbr \ of=debian-8.7.1-i386-xfce-CD-1.iso To restore the original MBR code: dd conv=notrunc bs=1 count=432 if=mbr.backup \ of=debian-8.7.1-i386-xfce-CD-1.iso Have a nice day :) Thomas

...und with offset computed with sect1ptr0, sect1ptr1) to the extlinux configuration change between reboot without calling extlinux. I have backup the Ext4 partition boot sector between each reboot with this command: dd if=/dev/sda2 of=$VERSION_DIR/boot/syslinux/bootsector.bak ibs=60928 count=1 conv=notrunc The file comparison show an unwanted change of the sector address of the configuration folder (at the offset sect1ptr0=11A and sect1ptr1=120) If I call again extlinux -i with the wanted configuration folder, as the first time, all the following reboots finally use the wanted linux image. How to p...

...NTNEW mount -o loop $OLDIMAGE $MNTOLD cp -r $MNTOLD/* $MNTNEW umount $MNTNEW umount $MNTOLD rmdir $MNTNEW rmdir $MNTOLD # Create the boot sector of the new image # copy the first 512 bytes from the OLD image except the bytes 11 through 61 (inclusive) dd if=$OLDIMAGE of=$NEWIMAGE bs=1 count=10 conv=notrunc dd if=$OLDIMAGE of=$NEWIMAGE bs=1 skip=61 seek=61 conv=notrunc count=451 # Print the details echo "Your floppy image is in $NEWIMAGE. When using it in iso/pxelinux, dont forget to add" echo "\"floppy c=$CYLINDERS s=$SECTORS h=$HEADS\" to the argument of memdisk" ----...

...jpg Build log can be found in http://www.syslinux.org/archives/2013-July/020452.html After I installed the self-compiled syslinux version, I run this commands: # cd /boot/extlinux # rm -rf *.c32 # extlinux --upgrade /boot/extlinux # cp -n /usr/share/syslinux/*.c32 /boot/extlinux # dd bs=440 conv=notrunc count=1 if=/usr/share/syslinux/gptmbr.bin of=/dev/sda # reboot (/boot/extlinux/extlinux.conf is untouched) ...but this seems not to be related to syslinux-5.11-pre8. syslinux-5.10 from source (=the tarball you provide) does work. I also tried syslinux-5.10 from git - same error. So there must...

...to do with Syslinux, but I still want to ask a question regarding Syslinux to be sure there are variations as result of installing Syslinux to a USB drive in Windows vs Linux. In Linux I do it this way(using version 4.03): sgdisk ?zap /dev/$DISKPARTITION syslinux -i /dev/${DISKPARTITION}1 dd conv=notrunc bs=440 if=/usr/lib/syslinux/mbr.bin of=/dev/$DISKPARTITION parted /dev/$DISKPARTITION set 1 boot on In Windows I do it this way(having only the exe file at the executing location, same version): syslinux.exe -f -m -a X: Are these two ways exactly equivalent, or are there any differences in the r...

...buf->fd, + (unsigned long long)buf->dev_bytenr, + (__u8)buf->data[0], + (__u8)buf->data[1], + (__u8)buf->data[2], + (__u8)buf->data[3]); + fprintf(stderr, "printf \"\\x%02x\\x%02x\\x%02x\\x%02x\" | dd of=(fd %i) bs=1c seek=%llu conv=notrunc count=4\n", + (__u8)result[0], + (__u8)result[1], + (__u8)result[2], + (__u8)result[3], + buf->fd, + (unsigned long long)buf->dev_bytenr); + } free(result); return 1; } @@ -165,6 +181,31 @@ static int verify_parent_transid(struct extent_io_tree...

Thomas Schmitt wrote: > So if we had a MBR which prints the content of the first 512 read bytes > we could tell whether they are block aligned and from which block they > come. Ok. I'll try. Is it the isohdppx or isohdpfx (or both) that is relevant? Meanwhile I have a hacked isohdppx.bin that prints: G if GPT M if MBR <nothing> if no partition info E if EBIOS C if not EBIOS

...3.0.3 installed with yum on Centos 5.1. I''am facing an issue trying to resize the disk image of a centos 4.5 VM. The VM disk size is 50Go and i need to add 150Go. I tried two methods so far : -------------1st method----------------------- dd if=/dev/zero of=<image file> bs=1M conv=notrunc count=1 seek=2500 * losetup /dev/loop0 <image file> * e2fsck -f /dev/loop0 * resize2fs /dev/loop0 * e2fsck -f /dev/loop0 * losetup -d /dev/loop0 ------------- End 1st method----------------------- -------------2nd method----------------------- dd if=/dev/zero of=/tmp/temp_expand bs=1024k co...

...make boot, and not about ISOs made with isohybrid options --partok -ctrlhd0 --forcehd0. > which would be the step-by-step instructions for users of other > isohybrid images? Copy at most 432 bytes to the start of USB stick or ISO image file: iso=/dev/sdc or iso=image.iso dd conv=notrunc if=isohdpfx.bin.170324 bs=1 count=432 of="$iso" > Would they differ according to some/any parameter? We do not yet have downloadable binaries of the other five isohdp* variants as listed in http://www.syslinux.org/wiki/index.php?title=Isohybrid#MBR_selection with --partok -ctrlh...

...ucture is causing it to look in the wrong spot. Thomas Schmitt wrote: > What happens if you use a partition editor to delete all MBR partitions > from the ISO image before you put it into the partition on disk ? > (An alternative to using a partition editor is > dd if=/dev/zero conv=notrunc bs=1 count=64 seek=446 of=...iso > ) I followed these steps on two of the test ISO's I am using (debian netinst and clonezilla). md5sum confirms the ISO's to be different after the "dd" I then wrote this ISO's to both primary and logical partitions: In both cases the imag...

...13 AH 41, derived from the new code would instruct isolinux.bin to use C/H/S addressing, too. I just tested this replacement by locating the "jc" instruction by its neighbor "cmpw $0xaa55, %bx" at byte 88 and changing it to "jmp": echo -n $'\xeb' | dd conv=notrunc bs=1 seek=88 count=1 of="$iso" It still boots in qemu to the first graphical Debian menu. The "ISOLINUX 6.03 ..." messages vanishes too fast for my eyes. So i damage the ISO to prevent booting the Debian payload. For that purpose i obtain the 2048-block address of isolinux.cfg...