Comments on: A bevy of fixes for V in Perl http://jfxpt.com/2020/a-bevy-of-fixes-for-v-in-perl/ The search for invariants Sat, 07 Mar 2026 22:17:24 +0000 http://polimedia.us hourly 1 By: The simplest way yet to fetch Bitcoin code « Fixpoint http://jfxpt.com/2020/a-bevy-of-fixes-for-v-in-perl/#comment-2376 The simplest way yet to fetch Bitcoin code « Fixpoint Fri, 21 Apr 2023 14:14:31 +0000 http://fixpoint.welshcomputing.com/?p=125#comment-2376 [...] Because "tree" is always used as the press directory name, you'll need to delete any conflicting one first or else the script will halt before trying to press. (This avoids the risk of clobbering uncommitted local changes and follows the behavior of the old v.pl.) [...] [...] Because "tree" is always used as the press directory name, you'll need to delete any conflicting one first or else the script will halt before trying to press. (This avoids the risk of clobbering uncommitted local changes and follows the behavior of the old v.pl.) [...]

]]> By: Jacob Welsh http://jfxpt.com/2020/a-bevy-of-fixes-for-v-in-perl/#comment-314 Jacob Welsh Tue, 21 Jul 2020 20:58:52 +0000 http://fixpoint.welshcomputing.com/?p=125#comment-314 There's two good finds in here: first, that a binary .pdf ended up in the kernel genesis despite <a href="http://bvt-trace.net/2019/09/linux-kernel-genesis-and-early-entropy-users/?b=However,&e=separately:#select" rel="nofollow">efforts to separate those</a>; second, that busybox patch doesn't support the \ directive to suppress a final newline, which phf's pure-Ada "vpatch" deliberately supports. There's two good finds in here: first, that a binary .pdf ended up in the kernel genesis despite efforts to separate those; second, that busybox patch doesn't support the \ directive to suppress a final newline, which phf's pure-Ada "vpatch" deliberately supports.

]]> By: Robinson Dorion http://jfxpt.com/2020/a-bevy-of-fixes-for-v-in-perl/#comment-313 Robinson Dorion Tue, 21 Jul 2020 20:26:00 +0000 http://fixpoint.welshcomputing.com/?p=125#comment-313 Not sure if this is a problem with v.pl+keksum, but I'll report it here first. I attempted to press <a href="http://bvt-trace.net/2019/12/keccak-hashing-for-kernel-rng/" rel="nofollow">bvt's kernel</a> using v.pl+keksum pressed to v_keksum_busybox_r2.vpatch on a Gales Linux system with 4 GB RAM and got the following error : time v.pl p linux-keccak-rng patches/linux-keccak-rng.vpatch Hunk 1 FAILED 0/1. +%PDF-1.4 +% +5 0 obj +<</Length 6 0 R/Filter /FlateDecode>> +stream +xQo#+$Q"EoIp7#}Avq#_j>`/#|i7}C/_o26#S#9# :k#5Chkvxe#)@S4" +(DQ }4 5 #C z1Q1xcs=D!uCFd(}h/[)u%8i)=AMCwx +BQ7Cs=}Z[xM!p# !#-XR-GF=$ZklGS>pH8M1.*($Z<1yB5w-s 3a #QLu#yCKE)6aM="M=tC=*zHXeSlM=$ZDU6h#C"zHXeSAfPCD6M=: c!C([D%&mb(1wk5~}>TDH=a#0zWPhbr>@Ch3<s%3yqhOaQ&HF@",kX"<7G&.fn.K9 ys#}I~=5yvc/#;o4#v|kS>r ux<K1wkS}7+="}@HHHEb?F}oUD"cxkDjHeP#" R{{{J{h{=xH[oLEbbb +y*7*D1sj HMB~<o#Y(%@CHZEr5(KZ@#="rHVK$+S#k$Hh/[q[#Z4cBbES:^X#P#Y#fwC ]#AgbYtvhle<DjmG%G>Rq8t#Ag8 +<Amxo@'Sf\P;N +=qjU 20q@#8$)PNlKAPB[%UuJP=>JXR 8*X*J p +R p#=PKE)TPQ +TUB, +@D!#0Q +m)TQ +TUB@kt + +U[T:PQ +TU2 ~RX&tQ'S + e8/ +eJa _B2Po`BF;/)P9<nUN)8:RU +Tx@8*<D +O,(K}#4" +(ObfC(9#Z#dD IQ#XQ-4@r=HmDjKb'b(VZE2?D*?D*?E"?D*?D*?D*?D*?yh##H#@C(q8TD*<"G_8S9kr@rP$r@jaZCxkT-(!f4#9wuc +Yg2NNpdD8NJP$C8#p<#"aX1(V<"HDQMczhvh>4LQ.Kqs#i8#r2X//JRFq(eZe)S Ai^y`cc#}_xo?~l_n<#cn%I#Ono__^|q=~}}9^4~!G_]XPrqIGq.]s~-i#=\_#g|zw:=}{vwW_w^~>;mzr#|q#rkw}se%c"`P?o:;oU0Utuq0endstream +endobj +6 0 obj +2760 +endobj +4 0 obj +<</Type/Page/MediaBox [0 0 566 600] +/Parent 3 0 R +/Resources<</ProcSet[/PDF /Text] +/ExtGState 10 0 R +/Font 11 0 R +>> +/Contents 5 0 R +>> +endobj +3 0 obj +<< /Type /Pages /Kids [ +4 0 R +] /Count 1 +>> +endobj +1 0 obj +<</Type /Catalog /Pages 3 0 R +/Metadata 13 0 R +>> +endobj +7 0 obj +<</Type/ExtGState +/OPM 1>>endobj +10 0 obj +<</R7 +7 0 R>> +endobj +11 0 obj +<</R8 +8 0 R>> +endobj +8 0 obj +<</BaseFont/SEXXTC+Helvetica/FontDescriptor 9 0 R/Type/Font +/FirstChar 32/LastChar 118/Widths[ +278 0 0 0 0 0 0 0 333 333 0 0 278 0 278 278 +0 0 556 0 556 0 0 0 0 0 278 0 0 0 0 0 +0 667 667 722 722 667 611 778 0 278 0 0 556 833 722 778 +667 778 722 667 611 0 667 0 0 0 0 0 0 0 0 556 +0 556 556 0 556 556 278 556 0 222 0 0 222 833 556 556 +556 0 333 500 278 556 500] +/Encoding/WinAnsiEncoding/Subtype/Type1>> +endobj +9 0 obj +<</Type/FontDescriptor/FontName/SEXXTC+Helvetica/FontBBox[-22 -218 762 741]/Flags 4 +/Ascent 741 +/CapHeight 741 +/Descent -218 +/ItalicAngle 0 +/StemV 114 +/MissingWidth 278 +/CharSet(/A/B/C/D/E/F/G/I/L/M/N/O/P/Q/R/S/T/V/a/b/colon/comma/d/e/f/four/g/i/l/m/n/o/p/parenleft/parenright/period/r/s/slash/space/t/two/u/underscore/v)/FontFile3 12 0 R>> +endobj +12 0 obj +<</Filter/FlateDecode +/Subtype/Type1C/Length 2959>>stream +xViTW> Q$ +(l*qbL4n[4 f&#9#~Un~ y#y ##&V$9De#c K¡dgy)#G;dd-KM$#>\\:Q*95'=1kTU##)RgO_,:gNhnzOgGf& gf1A;3L03D3!'31 3s 3`1&11gXf File: linux-keccak-rng/linux/sound/usb/bcd2000/Makefile Expected: 11ec3e836f217e10f3289a126e70e63fa2f412851e4623f7aab83900154343b4f1a0947a35f8625ee80d7418225cd51c67f5f9d6783615c2a49a027dfbb9c005 Actual: c55f5d100907f966f8164e14f60f84df238840059fd0ea980759814631a950671f45bbadec595651c44ae66e63752a226d574d86e54ee2912b67ec86f6d0b44a Pressed file hash did not match expected! 290m32.45s real 288m57.91s user 1m10.72s system Manually verifying the downloaded signature and vpatch appears the file was not corrupted prior/during transmisssion. gpg --verify linux-genesis.vpatch.bvt.sig linux-genesis.vpatch gpg: Signature made Mon Sep 2 19:35:59 2019 UTC using RSA key ID 4B962B68 Primary key fingerprint: 6CF3 EFF8 92A7 F23E 7E79 8E5E BA6B 8C05 4B96 2B68 I'll note that on line 22400605 of linux-genesis.vpatch I'm seeing a peculiar "\ No newline at end of file". This is where it attempts to press the file it failed on, i.e. linux/sound/usb/bcd2000/Makefile. Please let me know if you have any insight to what went wrong here or if there is further information I can provide. Not sure if this is a problem with v.pl+keksum, but I'll report it here first.

I attempted to press bvt's kernel using v.pl+keksum pressed to v_keksum_busybox_r2.vpatch on a Gales Linux system with 4 GB RAM and got the following error :

time v.pl p linux-keccak-rng patches/linux-keccak-rng.vpatch

Hunk 1 FAILED 0/1.
+%PDF-1.4
+%
+5 0 obj
+<</Length 6 0 R/Filter /FlateDecode>>
+stream
+xQo#+$Q"EoIp7#}Avq#_j>`/#|i7}C/_o26#S#9# :k#5Chkvxe#)@S4"
+(DQ
}4
5
#C z1Q1xcs=D!uCFd(}h/[)u%8i)=AMCwx
+BQ7Cs=}Z[xM!p# !#-XR-GF=$ZklGS>pH8M1.*($Z<1yB5w-s
3a
#QLu#yCKE)6aM="M=tC=*zHXeSlM=$ZDU6h#C"zHXeSAfPCD6M=:
c!C([D%&mb(1wk5~}>TDH=a#0zWPhbr>@Ch3<s%3yqhOaQ&HF@",kX"<7G&.fn.K9
ys#}I~=5yvc/#;o4#v|kS>r
ux<K1wkS}7+="}@HHHEb?F}oUD"cxkDjHeP#" R{{{J{h{=xH[oLEbbb
+y*7*D1sj
HMB~<o#Y(%@CHZEr5(KZ@#="rHVK$+S#k$Hh/[q[#Z4cBbES:^X#P#Y#fwC ]#AgbYtvhle<DjmG%G>Rq8t#Ag8
+<Amxo@'Sf\P;N
+=qjU
20q@#8$)PNlKAPB[%UuJP=>JXR
8*X*J p
+R
p#=PKE)TPQ
+TUB,
+@D!#0Q
+m)TQ
+TUB@kt
+
+U[T:PQ
+TU2
~RX&tQ'S
+
e8/
+eJa
_B2Po`BF;/)P9<nUN)8:RU
+Tx@8*<D
+O,(K}#4"
+(ObfC(9#Z#dD
IQ#XQ-4@r=HmDjKb'b(VZE2?D*?D*?E"?D*?D*?D*?D*?yh##H#@C(q8TD*<"G_8S9kr@rP$r@jaZCxkT-(!f4#9wuc
+Yg2NNpdD8NJP$C8#p<#"aX1(V<"HDQMczhvh>4LQ.Kqs#i8#r2X//JRFq(eZe)S Ai^y`cc#}_xo?~l_n<#cn%I#Ono__^|q=~}}9^4~!G_]XPrqIGq.]s~-i#=\_#g|zw:=}{vwW_w^~>;mzr#|q#rkw}se%c"`P?o:;oU0Utuq0endstream
+endobj
+6 0 obj
+2760
+endobj
+4 0 obj
+<</Type/Page/MediaBox [0 0 566 600]
+/Parent 3 0 R
+/Resources<</ProcSet[/PDF /Text]
+/ExtGState 10 0 R
+/Font 11 0 R
+>>
+/Contents 5 0 R
+>>
+endobj
+3 0 obj
+<< /Type /Pages /Kids [
+4 0 R
+] /Count 1
+>>
+endobj
+1 0 obj
+<</Type /Catalog /Pages 3 0 R
+/Metadata 13 0 R
+>>
+endobj
+7 0 obj
+<</Type/ExtGState
+/OPM 1>>endobj
+10 0 obj
+<</R7
+7 0 R>>
+endobj
+11 0 obj
+<</R8
+8 0 R>>
+endobj
+8 0 obj
+<</BaseFont/SEXXTC+Helvetica/FontDescriptor 9 0 R/Type/Font
+/FirstChar 32/LastChar 118/Widths[
+278 0 0 0 0 0 0 0 333 333 0 0 278 0 278 278
+0 0 556 0 556 0 0 0 0 0 278 0 0 0 0 0
+0 667 667 722 722 667 611 778 0 278 0 0 556 833 722 778
+667 778 722 667 611 0 667 0 0 0 0 0 0 0 0 556
+0 556 556 0 556 556 278 556 0 222 0 0 222 833 556 556
+556 0 333 500 278 556 500]
+/Encoding/WinAnsiEncoding/Subtype/Type1>>
+endobj
+9 0 obj
+<</Type/FontDescriptor/FontName/SEXXTC+Helvetica/FontBBox[-22 -218 762 741]/Flags 4
+/Ascent 741
+/CapHeight 741
+/Descent -218
+/ItalicAngle 0
+/StemV 114
+/MissingWidth 278
+/CharSet(/A/B/C/D/E/F/G/I/L/M/N/O/P/Q/R/S/T/V/a/b/colon/comma/d/e/f/four/g/i/l/m/n/o/p/parenleft/parenright/period/r/s/slash/space/t/two/u/underscore/v)/FontFile3 12 0 R>>
+endobj
+12 0 obj
+<</Filter/FlateDecode
+/Subtype/Type1C/Length 2959>>stream
+xViTW> Q$

+(l*qbL4n[4
f&#9#~Un~ y#y
##&V$9De#c K¡dgy)#G;dd-KM$#>\\:Q*95'=1kTU##)RgO_,:gNhnzOgGf&
gf1A;3L03D3!'31
3s
3`1&11gXf

File: linux-keccak-rng/linux/sound/usb/bcd2000/Makefile
Expected: 11ec3e836f217e10f3289a126e70e63fa2f412851e4623f7aab83900154343b4f1a0947a35f8625ee80d7418225cd51c67f5f9d6783615c2a49a027dfbb9c005
Actual: c55f5d100907f966f8164e14f60f84df238840059fd0ea980759814631a950671f45bbadec595651c44ae66e63752a226d574d86e54ee2912b67ec86f6d0b44a
Pressed file hash did not match expected!
290m32.45s real 288m57.91s user 1m10.72s system

Manually verifying the downloaded signature and vpatch appears the file was not corrupted prior/during transmisssion.
gpg --verify linux-genesis.vpatch.bvt.sig linux-genesis.vpatch
gpg: Signature made Mon Sep 2 19:35:59 2019 UTC using RSA key ID 4B962B68
Primary key fingerprint: 6CF3 EFF8 92A7 F23E 7E79 8E5E BA6B 8C05 4B96 2B68

I'll note that on line 22400605 of linux-genesis.vpatch I'm seeing a peculiar "\ No newline at end of file". This is where it attempts to press the file it failed on, i.e. linux/sound/usb/bcd2000/Makefile.

Please let me know if you have any insight to what went wrong here or if there is further information I can provide.

]]> By: GBW-NODE : Gales Bitcoin Wallet Node verified acquisition, build, install and run in 21ish short, simple steps. « Dorion Mode http://jfxpt.com/2020/a-bevy-of-fixes-for-v-in-perl/#comment-295 GBW-NODE : Gales Bitcoin Wallet Node verified acquisition, build, install and run in 21ish short, simple steps. « Dorion Mode Wed, 01 Jul 2020 17:32:57 +0000 http://fixpoint.welshcomputing.com/?p=125#comment-295 [...] V. I used Jacob's V in Perl with keksum starter kit. [...] [...] V. I used Jacob's V in Perl with keksum starter kit. [...]

]]> By: Jacob Welsh http://jfxpt.com/2020/a-bevy-of-fixes-for-v-in-perl/#comment-292 Jacob Welsh Mon, 29 Jun 2020 01:36:38 +0000 http://fixpoint.welshcomputing.com/?p=125#comment-292 Ah, I'd noticed and figured it was something like that; thanks for filling in. Either way I found it odd that the help/version commands would require having (part of) the setup in place. Ah, I'd noticed and figured it was something like that; thanks for filling in. Either way I found it odd that the help/version commands would require having (part of) the setup in place.

]]> By: Diana Coman http://jfxpt.com/2020/a-bevy-of-fixes-for-v-in-perl/#comment-291 Diana Coman Sun, 28 Jun 2020 08:07:03 +0000 http://fixpoint.welshcomputing.com/?p=125#comment-291 <blockquote> You can't demand I already know how to use a program in order to view its documentation! Well I mean, you can, but... you know what I mean?! </blockquote> In fairness, v.pl came with a very nice and quite detailed manual that was a separate text file so yes, to read before you run the code, certainly. A bit older school perhaps but not really a fault for that. If I recall correctly, when I made the <a href="http://ossasepia.com/2019/11/10/v-tree-and-v-starter-v2/" rel="nofollow">v-tree</a> for it all, I was faced with the choice of either going through all that doc and update everything to reflect the latest version or ditch it and keep instead only the runtime help that seemed to me quite clear enough for the job and certainly more likely to be kept up to date as well.

You can't demand I already know how to use a program in order to view its documentation! Well I mean, you can, but... you know what I mean?!

In fairness, v.pl came with a very nice and quite detailed manual that was a separate text file so yes, to read before you run the code, certainly. A bit older school perhaps but not really a fault for that. If I recall correctly, when I made the v-tree for it all, I was faced with the choice of either going through all that doc and update everything to reflect the latest version or ditch it and keep instead only the runtime help that seemed to me quite clear enough for the job and certainly more likely to be kept up to date as well.

]]>