search for: l213

Until Syslinux 3.86, isolinux.bin contained a checksum that was calculated by 'core/checksumiso.pl'. The checksum is related to the patching of the boot info table. During May 2009, a commit by Peter deleted the checksumiso.pl file. The commit is: core: LZO compress the PM part of the core repo.or.cz/syslinux.git/commit/0d82b71304d596d80f3c4520f9dcf90048ca50b7 And so, since

...nce it punts the decision to the caller and it won't break existing API users. To add new opt arguments, add them to the second list (currently [] for luks_open). See for example: https://github.com/libguestfs/libguestfs/blob/a754cd43078e43f1a2b5d10e54b684c70c5525d7/generator/actions_core.ml#L213 Because the existing API does not have optional arguments you must add ‘once_had_no_optargs = true’ so that the generator adds the backwards compatibility API. > 3) As it is right now, lsblk is called for every crypto_LUKS device to > see if a corresponding mapping had been created. I *thin...

...el "kaboom" if not matching. So where did the checksum 0x09e675b8 in Sid's installed isolinux.bin come from ? The source code sets it to 4-byte value 0xdeadbeef See the comments from http://repo.or.cz/syslinux.git/blob/f1aa00224b23e2b4c71f204c1417c7b6e5ea8e51:/core/isolinux.asm#l213 up to line 220. So i assume that checksumming still is applied somehow during building of isolinux.bin. In the diff of core/Makefile i see a new program ../lzo/prepcore applied. In its source, one can see the Boot Info Table checksum calculation: http://repo.or.cz/syslinux.git/blob/0d82b71304d5...

Allow `launch` call to accept an optional argument, called `blocksize`. Example: $ guestfish --listen -a raw.img $ guestfish --remote -- launch blocksize:4096 The actual qemu command is: [...] -device virtio-scsi-ccw,id=scsi -drive file=raw.img,cache=writeback,id=hd0,if=none -device scsi-hd,drive=hd0,physical_block_size=4096,logical_block_size=4096 [...] Signed-off-by: Tuan Hoang

...> > So where did the checksum 0x09e675b8 in Sid's installed isolinux.bin come > from ? > > The source code sets it to 4-byte value > 0xdeadbeef > See the comments from > http://repo.or.cz/syslinux.git/blob/f1aa00224b23e2b4c71f204c1417c7b6e5ea8e51:/core/isolinux.asm#l213 > up to line 220. > > So i assume that checksumming still is applied somehow during building of > isolinux.bin. > > In the diff of core/Makefile i see a new program ../lzo/prepcore applied. > In its source, one can see the Boot Info Table checksum calculation: > http://r...

The following patch attempts to implement sparsification of LUKS-encrypted partitions. It uses lsblk to pair the underlying LUKS block device with its mapped name. Also, --allow-discards was added by default to luks_open(). There are several potential issues that I can think of: 1) If and entire device is encrypted (not just one of more partitions), the lsblk trick might not work. 2) The

With the ATI bug I was hitting earlier fixed, only my btrfs partition continues to show high cpu usage for some operations. Rsync, git pull, git checkout and svn up are typicall operations which trigger the high cpu usage. As an example, this perf report is from using git checkout to change to a new branch; the change needed to checkout 208 files out of about 1600 total files. du(1) reports

...xor <4 x i16> %I129, %I34 %FC210 = uitofp <8 x i8> zeroinitializer to <8 x double> %Sl211 = select i1 %E74, i16 %Tr93, i16 %E19 %Cmp212 = icmp ugt i32 %Se, %E38 br i1 %Cmp212, label %CF243, label %CF273 CF273: ; preds = %CF243 %L213 = load i32, i32* %PC78 store i8 %L168, i8* %0 %E214 = extractelement <2 x i32> %Shuff113, i32 1 %Shuff215 = shufflevector <4 x i16> %Shuff128, <4 x i16> %I137, <4 x i32> <i32 6, i32 0, i32 2, i32 4> %I216 = insertelement <2 x i1> %Shuff20, i1 %Cmp30, i32...