Congratulations!

[Valid RSS] This is a valid RSS feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

Source: http://www.lemis.com/grog/diary.xml.php?topics=c

  1. <?xml version='1.0' encoding='UTF-8' ?>
  2. <rss version="2.0"
  3.    xmlns:atom="http://www.w3.org/2005/Atom"
  4.    xmlns:dc="http://purl.org/dc/elements/1.1/"
  5.    xmlns:sy="http://purl.org/rss/1.0/modules/syndication/">
  6.  
  7. <channel>
  8. <title>Greg's diary</title>
  9. <link>http://www.lemis.com/grog/diary.php</link>
  10. <atom:link href="http://www.lemis.com/grog/diary.xml.php"
  11. rel="self" type="application/rss+xml" />
  12. <description>Greg Lehey's online diary</description>
  13. <dc:creator />
  14. <dc:date>2024-07-26T13:06:59+10:00</dc:date>
  15. <dc:rights>Copyright 2015, 2016, 2017, 2018 Greg Lehey</dc:rights>
  16. <!-- for Emacs, this is a -*- mode: fundamental; coding: utf-8 -*- document -->
  17. <!-- temporary file, entries for last 7 days of previous month, used for RSS version -->
  18.                  
  19. <!-- topic ko not selected
  20.      <p>
  21. <a href="http://www.lemis.com/grog/recipes/huevos-a-la-tigre.php">Huevos a la tigre</a> for breakfast today.
  22. It's really a kind of omelette.  Or is it?  Not after my once-non-stick frying pan had its
  23. way:
  24.      </p>
  25.  
  26.            
  27.      <p>
  28.      </p>
  29.      
  30. End deselected topic ko (Huevos a la tigre: omelette?) -->
  31.  
  32.            
  33. <item>
  34. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2024.php#D-20240625-000815</guid>
  35. <link>http://www.lemis.com/grog/diary-jun2024.php?topics=c#D-20240625-000815</link>
  36. <category>technology</category>
  37. <category>general</category>
  38. <category>opinion</category>
  39. <title>Mobile phone power consumption</title>
  40.  <description>
  41.    <![CDATA[
  42.    <div align="justify">
  43.      <p>
  44. I've been playing more than usual with <i>albo.lemis.com</i>, my new <a href="https://m.gsmarena.com/xiaomi_redmi_note_13-12776.php">Xiaomi Redmi Note 13</a> mobile
  45. phone.  And the power consumption differs markedly from <i>hirse.lemis.com</i>, my old
  46. <a href="https://m.gsmarena.com/xiaomi_redmi_9t-10670.php">Redmi 9T</a>.  And it
  47. shows in the power consumption.  Here first <i>albo</i>, then <i>hirse</i>:
  48.      </p>
  49.  
  50.        <a id="Photo-0" name="Photo-0"
  51.          href="diary-jun2024.php?dirdate=20240624&amp;imagesizes=2&amp;topics=c#Photo-0">
  52.          <img alt="This should be albo-power-consumption-detail.jpeg.  Is it missing?" border="0" id="Photo_0"
  53.               title="Photo albo-power-consumption-detail.jpeg.  Click to redisplay larger version of image."
  54.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20240624/small/albo-power-consumption-detail.jpeg"
  55.               width="252" height="268"
  56.           /></a>
  57.        <a id="Photo-1" name="Photo-1"
  58.          href="diary-jun2024.php?dirdate=20240624&amp;imagesizes=12&amp;topics=c#Photo-1">
  59.          <img alt="This should be hirse-power-consumption-detail.jpeg.  Is it missing?" border="0" id="Photo_1"
  60.               title="Photo hirse-power-consumption-detail.jpeg.  Click to redisplay larger version of image."
  61.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20240624/small/hirse-power-consumption-detail.jpeg"
  62.               width="255" height="265"
  63.           /></a>
  64.  
  65.      <p>
  66. Is the Note 13 really that much hungrier than the 9T?  Or is it just that I have been using
  67. it more?
  68.      </p>
  69.      </div>
  70.    ]]>
  71.  </description>
  72.  <dc:creator>Greg Lehey</dc:creator>
  73.  <dc:date>2024-06-25T00:08:15+00:00</dc:date>
  74. </item>
  75.  
  76.            
  77. <item>
  78. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2024.php#D-20240625-002518</guid>
  79. <link>http://www.lemis.com/grog/diary-jun2024.php?topics=c#D-20240625-002518</link>
  80. <category>technology</category>
  81. <category>opinion</category>
  82. <title>Understanding Microsoft issues with VirtualBox</title>
  83.  <description>
  84.    <![CDATA[
  85.    <div align="justify">
  86.      <p>
  87. <a href="http://www.lemis.com/grog/diary-jun2024.php?subtitle=Ubuntu%20again&amp;article=D-20240623-021811#D-20240623-021811">Saturday's installation</a> of <a href="https://en.wikipedia.org/wiki/Ubuntu">Ubuntu</a> confirmed that there wasn't much wrong with the <a href="https://en.wikipedia.org/wiki/VirtualBox">VirtualBox</a> network configuration
  88. on <i>hydra</i>.  OK, what's the issue with Microsoft?  Spent some time investigating.
  89.      </p>
  90.  
  91.      <p>
  92. First, can it be that the VMs didn't like the host configuration changing under their
  93. running image?  Rebooted <i>despise</i>.  No improvement.  OK, for the fun of it, try the
  94. “troubleshooter”, which has never shot any trouble for me.  But this time it came up and
  95. said “done!”, specifically “restored default gateway”.  That's nonsense, of course: I was
  96. trying (and failing) to <i>ping</i> the default gateway.  But of course I tried again
  97. anyway.  And it worked!  Fixed, but with the wrong explanation.
  98.      </p>
  99.  
  100.      <p>
  101. OK, on to <i>disaster</i>, the other clone, almost exactly the same configuration bar the
  102. memory size.  This time I didn't reboot.  And though it claimed to have fixed the problem,
  103. this time it didn't.  OK, reboot.  And yes, it tried to fix it again, but set up <a href="https://en.wikipedia.org/wiki/DHCP">DHCP</a>.  Maybe that's what it did before, and I
  104. didn't find it because I was looking for <i>disaster</i>, not <i>dhcp-242</i>.  But after
  105. configuring the interface on the Microsoft side to the correct IP address, I wasn't able to
  106. ping <i>eureka</i>.  Run the troubleshooter again.  “Ethernet 2” (there is no “Ethernet 1”)
  107. didn't have a valid IP configuration, whatever that means.  It fixed it.  At some
  108. asynchronous point I had connectivity again.
  109.      </p>
  110.  
  111.        <a id="Photo-2" name="Photo-2"
  112.          href="diary-jun2024.php?dirdate=20240624&amp;imagesizes=112&amp;topics=c#Photo-2">
  113.          <img alt="This should be Microsoft-diagnostics.png.  Is it missing?" border="0" id="Photo_2"
  114.               title="Photo Microsoft-diagnostics.png.  Click to redisplay larger version of image."
  115.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20240624/small/Microsoft-diagnostics.png"
  116.               width="532" height="371.20257234727"
  117.           /></a>
  118.  
  119.      <p>
  120. While pondering that, discovered that I could no longer contact <i>despise</i>.  Another
  121. fix, then ran a <i>ping</i> from <i>eureka</i> for both VMs.  That was instructive.  After
  122. about 3 minutes, I got:
  123.      </p>
  124.  
  125.      <blockquote class="fullwidth">
  126. <div style="text-align:left">
  127.  <tt>
  128. 64 bytes from 192.109.197.168: icmp_seq=177 ttl=128 time=0.313 ms
  129. <br />64 bytes from 192.109.197.168: icmp_seq=178 ttl=128 time=0.302 ms
  130. <br />64 bytes from 192.109.197.168: icmp_seq=179 ttl=128 time=0.258 ms
  131. <br />64 bytes from 192.109.197.168: icmp_seq=196 ttl=128 time=13397.802 ms
  132. <br />64 bytes from 192.109.197.168: icmp_seq=197 ttl=128 time=12396.873 ms
  133. <br />64 bytes from 192.109.197.168: icmp_seq=198 ttl=128 time=11393.059 ms
  134. <br />64 bytes from 192.109.197.168: icmp_seq=199 ttl=128 time=10389.815 ms
  135. <br />64 bytes from 192.109.197.168: icmp_seq=200 ttl=128 time=9388.793 ms
  136. <br />64 bytes from 192.109.197.168: icmp_seq=201 ttl=128 time=8387.910 ms
  137. <br />64 bytes from 192.109.197.168: icmp_seq=202 ttl=128 time=7386.827 ms
  138. <br />64 bytes from 192.109.197.168: icmp_seq=203 ttl=128 time=6385.940 ms
  139. <br />64 bytes from 192.109.197.168: icmp_seq=204 ttl=128 time=5384.064 ms
  140. <br />64 bytes from 192.109.197.168: icmp_seq=205 ttl=128 time=4382.936 ms
  141. <br />64 bytes from 192.109.197.168: icmp_seq=206 ttl=128 time=3380.054 ms
  142. <br />64 bytes from 192.109.197.168: icmp_seq=207 ttl=128 time=2377.515 ms
  143. <br />64 bytes from 192.109.197.168: icmp_seq=208 ttl=128 time=1375.960 ms
  144. <br />64 bytes from 192.109.197.168: icmp_seq=209 ttl=128 time=373.828 ms
  145. <br />
  146.  </tt>
  147. </div>
  148. </blockquote>
  149.  
  150.      <p>
  151. And then nothing.  The ping times are interesting: they're at one second intervals, so
  152. basically the response to ICMP sequences 196 to 209 all happened at the same time (24 ms
  153. between all of them).  And it was preceded by 17 dropped packets.
  154.      </p>
  155.  
  156.      <p>
  157. Does this happen with <i>despise</i> too?  At first I thought that it didn't, but after a
  158. good 2 hours I had:
  159.      </p>
  160.  
  161.      <blockquote class="fullwidth">
  162. <div style="text-align:left">
  163.  <tt>
  164. 64 bytes from 192.109.197.170: icmp_seq=8018 ttl=128 time=0.603 ms
  165. <br />64 bytes from 192.109.197.170: icmp_seq=8031 ttl=128 time=18192.978 ms
  166. <br />64 bytes from 192.109.197.170: icmp_seq=8032 ttl=128 time=17193.275 ms
  167. <br />64 bytes from 192.109.197.170: icmp_seq=8033 ttl=128 time=16193.338 ms
  168. <br />64 bytes from 192.109.197.170: icmp_seq=8034 ttl=128 time=15186.715 ms
  169. <br />64 bytes from 192.109.197.170: icmp_seq=8035 ttl=128 time=14128.738 ms
  170. <br />64 bytes from 192.109.197.170: icmp_seq=8036 ttl=128 time=13121.802 ms
  171. <br />64 bytes from 192.109.197.170: icmp_seq=8037 ttl=128 time=12120.614 ms
  172. <br />64 bytes from 192.109.197.170: icmp_seq=8038 ttl=128 time=11118.807 ms
  173. <br />64 bytes from 192.109.197.170: icmp_seq=8039 ttl=128 time=10117.802 ms
  174. <br />64 bytes from 192.109.197.170: icmp_seq=8040 ttl=128 time=9113.875 ms
  175. <br />64 bytes from 192.109.197.170: icmp_seq=8041 ttl=128 time=8050.493 ms
  176. <br />64 bytes from 192.109.197.170: icmp_seq=8042 ttl=128 time=7047.142 ms
  177. <br />64 bytes from 192.109.197.170: icmp_seq=8043 ttl=128 time=6046.126 ms
  178. <br />64 bytes from 192.109.197.170: icmp_seq=8044 ttl=128 time=5044.124 ms
  179. <br />64 bytes from 192.109.197.170: icmp_seq=8045 ttl=128 time=4030.953 ms
  180. <br />64 bytes from 192.109.197.170: icmp_seq=8046 ttl=128 time=3029.581 ms
  181. <br />64 bytes from 192.109.197.170: icmp_seq=8047 ttl=128 time=2023.347 ms
  182. <br />64 bytes from 192.109.197.170: icmp_seq=8048 ttl=128 time=1014.190 ms
  183. <br />
  184.  </tt>
  185. </div>
  186. </blockquote>
  187.  
  188.      <p>
  189. Here the response times are not quite as close, but clearly it's the same syndrome.
  190.      </p>
  191.  
  192.      <p>
  193. So: my best bet now is that there's really something wrong with Microsoft on VirtualBox, and
  194. it's probably related to the hangs that I had with the old network card, which never had any
  195. issues except with this combination.  Whose fault is it?  Microsoft?  VirtualBox?
  196. <a href="https://www.freebsd.org/">FreeBSD</a> (the interface with VirtualBox)?
  197. Time to try other alternatives.
  198.      </p>
  199.      </div>
  200.    ]]>
  201.  </description>
  202.  <dc:creator>Greg Lehey</dc:creator>
  203.  <dc:date>2024-06-25T00:25:18+00:00</dc:date>
  204. </item>
  205.  
  206.                  
  207. <!-- topic k not selected
  208.      <p>
  209. We occasionally eat Moroccan <a href="https://en.wikipedia.org/wiki/Preserved_lemon">preserved lemons</a>, but they've been out of fashion for a number of years, and we're
  210. running out.
  211.      </p>
  212.  
  213.      <p>
  214. But why buy them?  It can't be that difficult to make them ourselves.  Spent some time
  215. reading recipes, noting that all US-based recipes want sugar, and no other ones do.  And
  216. some want various spices.  <a href="https://www.taste.com.au/recipes/preserved-lemons-2/48d75c21-16ce-411e-a289-4817a688e317">This one</a> suggests freezing the lemons after preparation, and then thawing them again,
  217. to speed up the maturation process.  But <a href="https://tasteofmaroc.com/how-to-make-preserved-lemons/">How to Make Moroccan Preserved
  218. Lemons</a> looked most authentic.  No sugar, of course.  No spices.  Just lemons and salt:
  219.      </p>
  220.  
  221.      <div align="left">
  222.      </div>
  223.  
  224.      <p>
  225. Now to wait a month or so.
  226.      </p>
  227.      
  228. End deselected topic k (Preserved lemons) -->
  229.  
  230.            
  231. <item>
  232. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2024.php#D-20240626-012332</guid>
  233. <link>http://www.lemis.com/grog/diary-jun2024.php?topics=c#D-20240626-012332</link>
  234. <category>technology</category>
  235. <category>opinion</category>
  236. <title>More Microsoft on VirtualBox investigation</title>
  237.  <description>
  238.    <![CDATA[
  239.    <div align="justify">
  240.      <p>
  241. What's wrong with the networking on <i>disaster.lemis.com</i> and <i>despise.lemis.com</i>,
  242. my Microsoft 10 virtual machines running under <a href="https://en.wikipedia.org/wiki/VirtualBox">VirtualBox</a>.  Is it the hardware?  Is it
  243. <a href="https://www.freebsd.org/">FreeBSD</a>?  Is it VirtualBox?  Is it Microsoft?
  244.      </p>
  245.  
  246.      <p>
  247. For the fun of it, asked <a href="https://bard.google.com/">Bard</a>, which came up
  248. with <a href="https://gemini.google.com/app/b6b55e4813befcc0">this answer</a>,
  249. referring to <a href="https://forums.virtualbox.org/viewtopic.php?t=104409">a forum
  250. post</a> that didn't quite address my issues, but it gave me some ideas to follow on.
  251. <a href="https://forums.virtualbox.org/viewtopic.php?t=101111">This post</a> is
  252. interesting because it refers to the same network hardware that I have.  <a href="https://forums.virtualbox.org/viewtopic.php?p=492732&amp;sid=90045a90fc729eeb128ec27e20632059#p492732">This incomplete post</a> seems to indicate that a different network adapter might solve
  253. the problem.  But if so, I have two problems.  Certainly we have  different symptoms now.
  254. Previously the entire system would hang, and only under load, while now it seems to be only
  255. the Microsoft guest, and it does it at random.  <a href="https://forums.virtualbox.org/viewtopic.php?p=491062#p491062">This post</a>, in the
  256. same thread, suggests setting “Paravirtualization Interface” to “Hyper-V”.  Tried that, with
  257. the convenient result that it hung very quickly, saving me time.
  258.      </p>
  259.  
  260.      <p>
  261. What is it doing in this time?  Tried a <i>tcpdump</i>, which showed me continuous
  262.      </p>
  263.  
  264.      <blockquote class="fullwidth">
  265. <div style="text-align:left">
  266.  <tt>
  267. 12:15:37.799085 ARP, Request who&#45;has eureka.lemis.com tell despise.lemis.com, length 46
  268. <br />12:15:37.799087 ARP, Request who&#45;has eureka.lemis.com tell despise.lemis.com, length 28
  269. <br />12:15:37.799213 ARP, Reply eureka.lemis.com is&#45;at bc:5f:f4:c9:9b:bf (oui Unknown), length 46
  270. <br />
  271.  </tt>
  272. </div>
  273. </blockquote>
  274.  
  275.      <p>
  276. For some reason there are always two <a href="https://en.wikipedia.org/wiki/Address_Resolution_Protocol">ARP</a> requests, a pair per second.  So it seems that the response was not getting through.
  277.      </p>
  278.  
  279.      <p>
  280. And then there's a number of these in the <i>/var/log/messages</i>:
  281.      </p>
  282.  
  283.      <blockquote class="fullwidth">
  284. <div style="text-align:left">
  285.  <tt>
  286. Jun 25 12:40:47 hydra kernel: vboxdrv: XXXXXXXXXXXXXXXX VMMR0.r0
  287. <br />Jun 25 12:40:47 hydra syslogd: sendto: Network is down
  288. <br />Jun 25 12:40:47 hydra kernel: vboxdrv: XXXXXXXXXXXXXXXX VBoxDDR0.r0
  289. <br />Jun 25 12:40:47 hydra syslogd: sendto: Network is down
  290. <br />Jun 25 12:40:47 hydra kernel: VMMR0InitVM: eflags=40246 fKernelFeatures=0x2 (SUPKERNELFEATURES_SMAP=1)
  291. <br />Jun 25 12:40:47 hydra syslogd: sendto: Network is down
  292. <br />Jun 25 12:40:47 hydra syslogd: last message repeated 2 times
  293. <br />
  294.  </tt>
  295. </div>
  296. </blockquote>
  297.  
  298.      <p>
  299. Somehow messages with <tt>XXX</tt> in them (for FreeBSD, 3 <tt>X</tt>s are enough) suggests
  300. debug output.  And the “network is down” messages from <i>syslogd</i> suggest that there's
  301. something wrong.  Are the XXXs related?  The interspersed promiscuous mode messages suggest that
  302. it's happening while I'm looking at the network.  I'll keep an eye
  303. on <i>/var/log/messages</i>  from now on.
  304.      </p>
  305.  
  306.      <p>
  307. And then there's another issue  that may or may not be related: noise in the audio output,
  308. another thing that I should investigate.  It seems to be related to the virtual machines,
  309. though it may just be related to the load on the host machine.
  310.      </p>
  311.      </div>
  312.    ]]>
  313.  </description>
  314.  <dc:creator>Greg Lehey</dc:creator>
  315.  <dc:date>2024-06-26T01:23:32+00:00</dc:date>
  316. </item>
  317.  
  318.            
  319. <item>
  320. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2024.php#D-20240626-015402</guid>
  321. <link>http://www.lemis.com/grog/diary-jun2024.php?topics=c#D-20240626-015402</link>
  322. <category>technology</category>
  323. <category>opinion</category>
  324. <title>fvwm3: progress</title>
  325.  <description>
  326.    <![CDATA[
  327.    <div align="justify">
  328.      <p>
  329. Somehow I still can't make much sense of the required syntax for the <a href="https://www.fvwm.org/"><i>fvwm3</i></a> configuration file.  There seems to be a
  330. disconnect between the (relatively copious) documentation and my understanding.  So time for
  331. some experimentation.  Made these changes (inter alia) in the configuration file:
  332.      </p>
  333.  
  334.      <blockquote class="fullwidth">
  335. <div style="text-align:left">
  336.  <tt>
  337. +Colorset 21 fg black, bg yellow
  338. <br />
  339. <br />&#45;Style "xterm&#45;r" &nbsp; &nbsp; Icon xterm.xpm,Color yellow/black,IconBox &nbsp;&#45;40 300 &#45;1 &#45;140
  340. <br />+Style "xterm&#45;r" &nbsp; &nbsp; Icon xterm.xpm,Colorset 21,IconBox &nbsp;&#45;40 300 &#45;1 &#45;140
  341. <br />
  342.  </tt>
  343. </div>
  344. </blockquote>
  345.  
  346.      <p>
  347. Success!  Well, sort of.  Now these windows have <i>icons</i> that have a yellow background
  348. and a black foreground, which proves to be the opposite of what I wanted.  That's easy
  349. enough to fix, but I still need to find out how to highlight the windows themselves.  Still,
  350. the first step of progress.
  351.      </p>
  352.      </div>
  353.    ]]>
  354.  </description>
  355.  <dc:creator>Greg Lehey</dc:creator>
  356.  <dc:date>2024-06-26T01:54:02+00:00</dc:date>
  357. </item>
  358.  
  359.                  
  360. <!-- topic ko not selected
  361.      <p>
  362. Another attempt at <a href="http://www.lemis.com/grog/recipes/Beijing-fried-sauce-noodles.php">Beijing “Fried
  363. Sauce” Noodles</a> today.  Somehow I'm still not happy with the results.  Today I tried,
  364. basing on the recipe of <a href="http://www.lemis.com/grog/diary-jun2024.php?subtitle=Beijing%20sauce%20noodles%20again&amp;article=D-20240611-004415#D-20240611-004415">10 June 2024</a>:
  365.      </p>
  366.  
  367.      <ul>
  368.        <li class="fullwidth">
  369.          <div class="listitemwidth">
  370.            Double the quantities of the spices.
  371.          </div>
  372.        </li>
  373.  
  374.        <li class="fullwidth">
  375.          <div class="listitemwidth">
  376.            Add more bean paste.
  377.          </div>
  378.        </li>
  379.  
  380.        <li class="fullwidth">
  381.          <div class="listitemwidth">
  382.            Omit the wine.
  383.          </div>
  384.        </li>
  385.  
  386.        <li class="fullwidth">
  387.          <div class="listitemwidth">
  388.            Fry the noodles in the sauce.
  389.          </div>
  390.        </li>
  391.  
  392.        <li class="fullwidth">
  393.          <div class="listitemwidth">
  394.            Add crushed garlic.
  395.          </div>
  396.        </li>
  397.      </ul>
  398.  
  399.      <p>
  400. The result?  Probably too much star anise.  The noodles were much better after being fried.
  401. And for some reason, the quantity was too much.  Somehow I still have issues.
  402.      </p>
  403.      
  404. End deselected topic ko (Beijing “fried sauce” noodles again) -->
  405.  
  406.            
  407. <item>
  408. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2024.php#D-20240627-023122</guid>
  409. <link>http://www.lemis.com/grog/diary-jun2024.php?topics=c#D-20240627-023122</link>
  410. <category>technology</category>
  411. <category>opinion</category>
  412. <title>More disaster</title>
  413.  <description>
  414.    <![CDATA[
  415.    <div align="justify">
  416.      <p>
  417. So why are my Microsoft virtual machines getting network hangs?  An obvious thing to try
  418. would be to upgrade <a href="https://en.wikipedia.org/wiki/VirtualBox">VirtualBox</a>.  That went smoothly, but it caused problems with <a href="https://en.wikipedia.org/wiki/Qt">Qt</a> that were more difficult to resolve.
  419.      </p>
  420.  
  421.      <p>
  422. On restarting (this time <i>disaster.lemis.com</i>) I had to recover the net configuration
  423. again, after which things ran smoothly.  How long?  Set up a <i>ping</i> to record the time
  424. and stop when there was a failure.  It was still running when I went to bed.  Solved?  I
  425. don't trust it.
  426.      </p>
  427.      </div>
  428.    ]]>
  429.  </description>
  430.  <dc:creator>Greg Lehey</dc:creator>
  431.  <dc:date>2024-06-27T02:31:22+00:00</dc:date>
  432. </item>
  433.  
  434.            
  435. <!-- topic ko not selected
  436.      <p>
  437. Yesterday <a href="http://www.lemis.com/yvonne/">Yvonne</a> cooked a variation on <a href="http://www.lemis.com/grog/recipes/linsensuppe.php">Linsensuppe</a>, enough to freeze multiple servings.  But
  438. how big should they be?  I thought 500 to 600 g, Yvonne thought 600 to 700.  So I prepared
  439. 700 g portions for freezing and kept one for tonight.
  440.      </p>
  441.  
  442.      <p>
  443. Surprise: 700 g isn't enough.  800 g next time?
  444.      </p>
  445.      
  446. End deselected topic ko (Linsensuppe: quantities?) -->
  447.  
  448.                  
  449. <!-- topic ko not selected
  450.      <p>
  451. Somehow I have ended up with a second packet of Chilliz mi udang paste.  I tried it
  452. <a href="http://www.lemis.com/grog/diary-nov2023.php?subtitle=New%20mi%20udang&amp;article=D-20231103-005739#D-20231103-005739">last year</a> and found it boring.  But it's there, so I made it up.  Yes, boring.  Not
  453. bad, but not to be repeated
  454.      </p>
  455.      
  456. End deselected topic ko (More Chilliz mi udang) -->
  457.  
  458.            
  459. <item>
  460. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2024.php#D-20240628-015739</guid>
  461. <link>http://www.lemis.com/grog/diary-jun2024.php?topics=c#D-20240628-015739</link>
  462. <category>technology</category>
  463. <category>opinion</category>
  464. <title>More VirtualBox fun</title>
  465.  <description>
  466.    <![CDATA[
  467.    <div align="justify">
  468.      <p>
  469. When I went to bed last night, <i>disaster.lemis.com</i> was still running fine.  Fixed?
  470.      </p>
  471.  
  472.      <p>
  473. No.  When I got up this morning, I discovered that it had stopped responding at 23:32:20,
  474. with the same symptoms as I have been having before.
  475.      </p>
  476.  
  477.      <p>
  478. What next?  Look at the log files.  Nothing, neither in <i>/var/log/messages</i> nor in the
  479. <a href="https://en.wikipedia.org/wiki/VirtualBox">VirtualBox</a> logs.  Where do I
  480. go from here?  Changing hypervisors doesn't seem to be an option: <a href="https://en.wikipedia.org/wiki/Bhyve">Bhyve</a> seems to have issues with Microsoft,
  481. <a href="https://en.wikipedia.org/wiki/VMware">VMware</a> doesn't run on <a href="https://www.freebsd.org/">FreeBSD</a>, and what I've seen of <a href="https://en.wikipedia.org/wiki/Xen">Xen</a> suggests that it needs to run on the bare
  482. hardware.
  483.      </p>
  484.  
  485.      <p>
  486. Change machines?  That currently looks like the best option.  Use one of my <a href="https://en.wikipedia.org/wiki/ThinkCentre">ThinkCentres</a>.  But that will require
  487. preparation.
  488.      </p>
  489.      </div>
  490.    ]]>
  491.  </description>
  492.  <dc:creator>Greg Lehey</dc:creator>
  493.  <dc:date>2024-06-28T01:57:39+00:00</dc:date>
  494. </item>
  495.  
  496.            
  497. <item>
  498. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2024.php#D-20240628-021657</guid>
  499. <link>http://www.lemis.com/grog/diary-jun2024.php?topics=c#D-20240628-021657</link>
  500. <category>technology</category>
  501. <category>opinion</category>
  502. <title>fvwm3: success?</title>
  503.  <description>
  504.    <![CDATA[
  505.    <div align="justify">
  506.      <p>
  507. So I moved on to my other issue, <a href="https://www.fvwm.org/"><i>fvwm3</i></a> configuration.  The obvious thing was to change all of the specifications that <i>fvwm3</i>
  508. complained about.  That wasn't as simple as it looked.  For example, it complained about
  509. this line:
  510.      </p>
  511.  
  512.      <blockquote class="fullwidth">
  513. <div style="text-align:left">
  514.  <tt>
  515. HilightColor black palegreen
  516.  </tt>
  517. </div>
  518. </blockquote>
  519.  
  520.      <p>
  521. What does the man page say?  What man page?  I have <i>fvwm3(1)</i>, but it doesn't mention
  522. anything like that.  On the web I found <a href="https://manpages.ubuntu.com/manpages/kinetic/man1/fvwm3.1.html">this page</a>, but
  523. though the content is different and more complete, it also didn't help.  But somewhere that
  524. I forgot to write down told me:
  525.      </p>
  526.  
  527.      <blockquote class="fullwidth">
  528. <div style="text-align:left">
  529.  <tt>
  530. HilightColor textcolor backgroundcolor
  531. <br />&nbsp;&nbsp; &nbsp; &nbsp;This command is obsoleted by the Style options HilightFore and HilightBack. Please use
  532. <br />
  533. <br />&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Style * HilightFore textcolor, HilightBack backgroundcolor
  534. <br />
  535. <br />&nbsp;&nbsp; &nbsp; &nbsp;instead.
  536. <br />
  537.  </tt>
  538. </div>
  539. </blockquote>
  540.  
  541.      <p>
  542. Only much later did I discover that there are multiple man pages, though <i>fvwm3(1)</i>
  543. doesn't have a <b>SEE&nbsp;ALSO</b> section:
  544.      </p>
  545.  
  546.      <blockquote class="fullwidth">
  547. <div style="text-align:left">
  548.  <tt>
  549. /usr/local/share/man/man1/fvwm3.1.gz
  550. <br />/usr/local/share/man/man1/fvwm3all.1.gz
  551. <br />/usr/local/share/man/man1/fvwm3commands.1.gz
  552. <br />/usr/local/share/man/man1/fvwm3menus.1.gz
  553. <br />/usr/local/share/man/man1/fvwm3styles.1.gz
  554. <br />
  555.  </tt>
  556. </div>
  557. </blockquote>
  558.  
  559.      <p>
  560. I don't know how much it would have helped.  <i>fvwm3</i> still didn't want to know:
  561.      </p>
  562.  
  563.      <blockquote class="fullwidth">
  564. <div style="text-align:left">
  565.  <tt>
  566. [1719458711.919614] parse_and_set_window_style: Bad style option: HilightFore black
  567. <br />[1719458711.919618] parse_and_set_window_style: Bad style option: &nbsp;HilightBack palegreen
  568. <br />
  569.  </tt>
  570. </div>
  571. </blockquote>
  572.  
  573.      <p>
  574. But it seems that I don't really need that.  After setting all my Colorsets, it still didn't
  575. want to do what I want.  Clearly I'm missing something important, but it seems that this
  576. part is most important:
  577.      </p>
  578.  
  579.      <blockquote class="fullwidth">
  580. <div style="text-align:left">
  581.  <tt>
  582. # 3: Colorsets
  583. <br />#
  584. <br /># &nbsp; 0 &#45; Default
  585. <br /># &nbsp; 1 &#45; Inactive Windows
  586. <br /># &nbsp; 2 &#45; Active Window
  587. <br /># &nbsp; 3 &#45; Inactive Windows Borders
  588. <br /># &nbsp; 4 &#45; Active Windows Borders
  589. <br /># &nbsp; 5 &#45; Menu &#45; Inactive Item
  590. <br /># &nbsp; 6 &#45; Menu &#45; Active Item
  591. <br /># &nbsp; 7 &#45; Menu &#45; Grayed Item
  592. <br /># &nbsp; 8 &#45; Menu &#45; Title
  593. <br />
  594.  </tt>
  595. </div>
  596. </blockquote>
  597.  
  598.      <p>
  599. Played around with that, and gradually I got to the point where some of the colours were
  600. correct.  I could even live with that—the colours I use were chosen more at random than out
  601. of any logic.  But I wish I understood this stuff.
  602.      </p>
  603.  
  604.      <p>
  605. Next step: the <i>xterms</i> files.  A lot of what's there would fit better into
  606. an <i>.Xdefaults</i> file.  How much work should I do?
  607.      </p>
  608.      </div>
  609.    ]]>
  610.  </description>
  611.  <dc:creator>Greg Lehey</dc:creator>
  612.  <dc:date>2024-06-28T02:16:57+00:00</dc:date>
  613. </item>
  614.  
  615.                  
  616. <item>
  617. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2024.php#D-20240629-005229</guid>
  618. <link>http://www.lemis.com/grog/diary-jun2024.php?topics=c#D-20240629-005229</link>
  619. <category>technology</category>
  620. <category>opinion</category>
  621. <title>More VirtualBox fun</title>
  622.  <description>
  623.    <![CDATA[
  624.    <div align="justify">
  625.      <p>
  626. As planned, set up one of my <a href="https://en.wikipedia.org/wiki/ThinkCentre">ThinkCentres</a> for <a href="https://en.wikipedia.org/wiki/VirtualBox">VirtualBox</a> testing.  I was going to call it <i>monorchid</i> in memory of my old test
  627. box for <a href="https://papers.freebsd.org/2001/grog-smpng/">SMPng</a>, but then it
  628. occurred to me that even the oldest machines now have multiple processors.  This one has
  629. four, so I called it <i>quartet.lemis.com</i>.
  630.      </p>
  631.  
  632.      <p>
  633. Things didn't go easily.  I ran into the old issue with that I had <a href="http://www.lemis.com/grog/diary-mar2024.php?subtitle=Putting%20ryoms%20to%20the%20test&amp;article=D-20240317-013629#D-20240317-013629">in March</a>.  But even after setting that, things weren't smooth.  Did I have the kernel
  634. modules?
  635.      </p>
  636.  
  637.      <blockquote class="fullwidth">
  638. <div style="text-align:left">
  639.  <tt>
  640.  
  641. <br /><code><font color="blue">=== root@quartet (/dev/pts/0)</font> <font color="red">/src/VirtualBox</font> <font color="blue">30</font> &#45;&gt; <b><tt>kldstat|grep vbox</tt></b></code>
  642. <br /><code><font color="blue">=== root@quartet (/dev/pts/0)</font> <font color="red">/src/VirtualBox</font> <font color="blue">40</font> &#45;&gt; <b><tt>kldload vboxnetadp</tt></b></code>
  643. <br />kldload: can't load vboxnetadp: module already loaded or in kernel
  644. <br /><code><font color="blue">=== root@quartet (/dev/pts/0)</font> <font color="red">/src/VirtualBox</font> <font color="blue">41</font> &#45;&gt; <b><tt>kldload vboxdrv</tt></b></code>
  645. <br />kldload: can't load vboxdrv: module already loaded or in kernel
  646. <br />
  647.  </tt>
  648. </div>
  649. </blockquote>
  650.  
  651.      <p>
  652. Huh?  This is a <tt>GENERIC</tt> kernel, which doens't have VirtualBox modules.  Another
  653. <a href="https://en.wikipedia.org/wiki/Schrödinger's_cat">Schrödinger's cat</a>?  Do
  654. we have some mismatch somewhere?  To be on the safe side, started bringing the system up to
  655. date.  That's slow.  Another day gone by.
  656.      </p>
  657.      </div>
  658.    ]]>
  659.  </description>
  660.  <dc:creator>Greg Lehey</dc:creator>
  661.  <dc:date>2024-06-29T00:52:29+00:00</dc:date>
  662. </item>
  663.  
  664.            
  665. <item>
  666. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2024.php#D-20240629-005402</guid>
  667. <link>http://www.lemis.com/grog/diary-jun2024.php?topics=c#D-20240629-005402</link>
  668. <category>history</category>
  669. <category>technology</category>
  670. <title>Why quartet?</title>
  671.  <description>
  672.    <![CDATA[
  673.    <div align="justify">
  674.      <p>
  675. Why did I call the new machine <i>quartet.lemis.com</i>?  That goes back decades.  At
  676. <a href="https://en.wikipedia.org/wiki/Tandem_Computers">Tandem</a> our first Unix
  677. machine was an LXN, a rebadged <a href="https://en.wikipedia.org/wiki/Altos_Computer_Systems">Altos</a> machine.  Our first
  678. real Tandem Unix box was the <a href="https://techmonitor.ai/technology/tandem_promises_unix_system_v4_on_new_integrity_s2_machine_as_soon_as_it_is_stable">Integrity S2</a>.  So when it came to naming the machines, the LXN was
  679. called <i>solo.euts.tandem.com</i>, and the S2 was called <i>trio.euts.tandem.com</i>.
  680.      </p>
  681.  
  682.      <p>
  683. After I left Tandem, they had a new machine, which they
  684. called <i>quattro.euts.tandem.com</i>—that would never have happened if I had stayed.  In
  685. English, we have solo, duo, trio, quartet and more.  Since my “new” machine has 4
  686. CPUs, <i>quartet</i> is the obvious choice.
  687.      </p>
  688.      </div>
  689.    ]]>
  690.  </description>
  691.  <dc:creator>Greg Lehey</dc:creator>
  692.  <dc:date>2024-06-29T00:54:02+00:00</dc:date>
  693. </item>
  694.  
  695.            
  696. <item>
  697. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2024.php#D-20240629-015651</guid>
  698. <link>http://www.lemis.com/grog/diary-jun2024.php?topics=c#D-20240629-015651</link>
  699. <category>technology</category>
  700. <category>opinion</category>
  701. <title>SSD strangenesses</title>
  702.  <description>
  703.    <![CDATA[
  704.    <div align="justify">
  705.      <p>
  706. The first step in installing <i>quartet</i> was copying a system image.  That's simple: I
  707. have a number of identical 128 GB <a href="https://en.wikipedia.org/wiki/SSD">SSDs</a>, one of which has the system for <i>teevee</i>.  So all I need is <i>dd</i>.
  708.      </p>
  709.  
  710.      <blockquote class="fullwidth">
  711. <div style="text-align:left">
  712.  <tt>
  713. <code><font color="blue">=== root@teevee (/dev/pts/0)</font> <font color="red">/home/grog</font> <font color="blue">3</font> &#45;&gt; <b><tt>time dd if=/dev/ada0 of=/dev/ada1 bs=1m</tt></b></code>
  714. <br />122104+1 records in
  715. <br />122104+1 records out
  716. <br />128035676160 bytes transferred in 1944.455866 secs (65846532 bytes/sec)
  717. <br />
  718.  </tt>
  719. </div>
  720. </blockquote>
  721.  
  722.      <p>
  723. 65 MB/s?  That's not exactly blindingly fast for an SSD.  I had been watching “progress”
  724. from another <i>xterm</i>, which showed me:
  725.      </p>
  726.  
  727.      <blockquote class="fullwidth">
  728. <div style="text-align:left">
  729.  <tt>
  730. <code><font color="blue">=== grog@teevee (/dev/pts/1)</font> <font color="red">~</font> <font color="blue">3</font> &#45;&gt; <b><tt>iostat 1</tt></b></code>
  731. <br />&nbsp;&nbsp; &nbsp; &nbsp; tty &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ada0 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ada1 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;pass0 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; cpu
  732. <br />&nbsp;tin &nbsp;tout KB/t &nbsp; tps &nbsp;MB/s KB/t &nbsp; tps &nbsp;MB/s KB/t &nbsp; tps &nbsp;MB/s &nbsp;us ni sy in id
  733. <br />...
  734. <br />&nbsp;&nbsp; 0 &nbsp; &nbsp;84 1024 &nbsp; &nbsp;19 18.85 1024 &nbsp; &nbsp;19 18.85 &nbsp;0.0 &nbsp; &nbsp; 0 &nbsp;0.00 &nbsp; 0 &nbsp;0 &nbsp;0 &nbsp;0 100
  735. <br />&nbsp;&nbsp; 0 &nbsp; &nbsp;80 1024 &nbsp; &nbsp;18 17.96 1024 &nbsp; &nbsp;19 18.96 &nbsp;0.0 &nbsp; &nbsp; 0 &nbsp;0.00 &nbsp; 0 &nbsp;0 &nbsp;0 &nbsp;0 100
  736. <br />&nbsp;&nbsp; 0 &nbsp; &nbsp;80 1024 &nbsp; 195 194.80 1024 &nbsp; 195 194.80 &nbsp;0.0 &nbsp; &nbsp; 0 &nbsp;0.00 &nbsp; 0 &nbsp;0 &nbsp;0 &nbsp;0 100
  737. <br />&nbsp;&nbsp; 0 &nbsp; &nbsp;80 1024 &nbsp; &nbsp;50 50.04 1024 &nbsp; &nbsp;49 49.06 &nbsp;0.0 &nbsp; &nbsp; 0 &nbsp;0.00 &nbsp; 0 &nbsp;0 &nbsp;0 &nbsp;0 100
  738. <br />&nbsp;&nbsp; 0 &nbsp; &nbsp;81 1024 &nbsp; &nbsp;18 18.15 1024 &nbsp; &nbsp;18 18.15 &nbsp;0.0 &nbsp; &nbsp; 0 &nbsp;0.00 &nbsp; 0 &nbsp;0 &nbsp;0 &nbsp;0 100
  739. <br />&nbsp;&nbsp; 0 &nbsp; &nbsp;77 1024 &nbsp; &nbsp;19 19.27 1024 &nbsp; &nbsp;19 19.27 &nbsp;0.0 &nbsp; &nbsp; 0 &nbsp;0.00 &nbsp; 0 &nbsp;0 &nbsp;0 &nbsp;0 100
  740. <br />&nbsp;&nbsp; 0 &nbsp; &nbsp;84 1024 &nbsp; &nbsp;19 18.80 1024 &nbsp; &nbsp;19 18.80 &nbsp;0.0 &nbsp; &nbsp; 0 &nbsp;0.00 &nbsp; 0 &nbsp;0 &nbsp;0 &nbsp;0 100
  741. <br />&nbsp;&nbsp; 0 &nbsp; &nbsp;77 1024 &nbsp; &nbsp;19 19.17 1024 &nbsp; &nbsp;19 19.17 &nbsp;0.0 &nbsp; &nbsp; 0 &nbsp;0.00 &nbsp; 0 &nbsp;0 &nbsp;0 &nbsp;0 100
  742. <br />&nbsp;&nbsp; 0 &nbsp; &nbsp;80 1024 &nbsp; &nbsp;19 18.99 1024 &nbsp; &nbsp;19 18.99 &nbsp;0.0 &nbsp; &nbsp; 0 &nbsp;0.00 &nbsp; 0 &nbsp;0 &nbsp;0 &nbsp;0 100
  743. <br />&nbsp;&nbsp; 0 &nbsp; &nbsp;81 1024 &nbsp; &nbsp;50 49.53 1024 &nbsp; &nbsp;51 50.54 &nbsp;0.0 &nbsp; &nbsp; 0 &nbsp;0.00 &nbsp; 0 &nbsp;0 &nbsp;0 &nbsp;0 100
  744. <br />&nbsp;&nbsp; 0 &nbsp; &nbsp;79 1024 &nbsp; 192 191.85 1024 &nbsp; 191 190.86 &nbsp;0.0 &nbsp; &nbsp; 0 &nbsp;0.00 &nbsp; 0 &nbsp;0 &nbsp;0 &nbsp;0 100
  745. <br />
  746.  </tt>
  747. </div>
  748. </blockquote>
  749.  
  750.      <p>
  751. What happened there?  It reminds me of <a href="https://en.wikipedia.org/wiki/Shingled_Magnetic_Recording">Shingled Magnetic
  752. Recording</a> disks, but these are both SSDs.  It seemed to be related either to copying
  753. or to writing: I could read at round 600 MB/s.
  754.      </p>
  755.      </div>
  756.    ]]>
  757.  </description>
  758.  <dc:creator>Greg Lehey</dc:creator>
  759.  <dc:date>2024-06-29T01:56:51+00:00</dc:date>
  760. </item>
  761.  
  762.            
  763. <!-- topic gho not selected
  764.      <p>
  765. Finally got my act together to remove the cobwebs that I found in the power box for the bore
  766. pump <a href="http://www.lemis.com/grog/diary-jun2024.php?topics=ghJ&amp;subtitle=Pump%20problems&amp;article=D-20240621-012748#D-20240621-012748">last week</a>.  Adrian from <a href="https://www.ultimategroup.com.au/">UPI</a> had suggested using compressed air to blow away the cobwebs.
  767.      </p>
  768.  
  769.      <p>
  770. That was easier said than done.  After an attempt, it looked like this:
  771.      </p>
  772.  
  773.      
  774.      <p>
  775. Is that any better?  Tried with a brush from the kitchen and then compressed air, and things
  776. looked better:
  777.      </p>
  778.  
  779.      
  780.      <p>
  781. But it still wouldn't start.  With a multimeter I confirmed that there was power on the
  782. first of these boxes (lower on the first image), but nothing on the second.
  783.      </p>
  784.  
  785.      
  786.      <p>
  787. But the cable in between looks like this:
  788.      </p>
  789.  
  790.      
  791.      <p>
  792. That's probably the real cause of the problem.  My days of electrical wiring are over, so
  793. Adrian can come and fix it.
  794.      </p>
  795.      
  796. End deselected topic gho (Fixing the bore pump) -->
  797.  
  798.                  
  799. <item>
  800. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2024.php#D-20240630-002403</guid>
  801. <link>http://www.lemis.com/grog/diary-jun2024.php?topics=c#D-20240630-002403</link>
  802. <category>technology</category>
  803. <category>opinion</category>
  804. <title>Still more VirtualBox fun</title>
  805.  <description>
  806.    <![CDATA[
  807.    <div align="justify">
  808.      <p>
  809. Finally my world build was done.  Rebooted <i>quartet</i> and ran <i>make installworld</i>.
  810. It failed!
  811.      </p>
  812.  
  813.      <blockquote class="fullwidth">
  814. <div style="text-align:left">
  815.  <tt>
  816. install &nbsp;&#45;o root &#45;g wheel &#45;m 444 ftime.3.gz &nbsp;/usr/share/man/man3/
  817. <br />install: ftime.3.gz: No such file or directory
  818. <br />
  819.  </tt>
  820. </div>
  821. </blockquote>
  822.  
  823.      <p>
  824. How did that happen?  My best bet is that the culprit was the nightly <i>cron</i> job that
  825. updates the source trees.  Installed as best I could, and then on.
  826.      </p>
  827.  
  828.      <p>
  829. OK, update the <a href="https://en.wikipedia.org/wiki/VirtualBox">VirtualBox</a> packages to be on the safe side.  But no, I was up to date.
  830.      </p>
  831.  
  832.      <blockquote class="fullwidth">
  833. <div style="text-align:left">
  834.  <tt>
  835. <code><font color="blue">=== root@quartet (/dev/pts/0)</font> <font color="red">/src/VirtualBox</font> <font color="blue">40</font> &#45;&gt; <b><tt>kldload vboxnetadp</tt></b></code>
  836. <br />kldload: can't load vboxnetadp: module already loaded or in kernel
  837.  </tt>
  838. </div>
  839. </blockquote>
  840.  
  841.      <p>
  842. We've seen that before.  OK, what does <i>ktrace</i> tell me?
  843.      </p>
  844.  
  845.      <blockquote class="fullwidth">
  846. <div style="text-align:left">
  847.  <tt>
  848. &nbsp;72203 kldload &nbsp;CALL &nbsp;kldload(0x36febbf8778)
  849. <br />&nbsp;72203 kldload &nbsp;NAMI &nbsp;"/boot/kernel/linker.hints"
  850. <br />&nbsp;72203 kldload &nbsp;NAMI &nbsp;"/boot/kernel/vboxnetadp"
  851. <br />&nbsp;72203 kldload &nbsp;NAMI &nbsp;"/boot/kernel/vboxnetadp.ko"
  852. <br />&nbsp;72203 kldload &nbsp;NAMI &nbsp;"/boot/modules/linker.hints"
  853. <br />&nbsp;72203 kldload &nbsp;NAMI &nbsp;"/boot/modules/vboxnetadp.ko"
  854. <br />&nbsp;72203 kldload &nbsp;NAMI &nbsp;"/boot/modules/vboxnetadp.ko"
  855. <br />&nbsp;72203 kldload &nbsp;NAMI &nbsp;"/boot/kernel/linker.hints"
  856. <br />&nbsp;72203 kldload &nbsp;NAMI &nbsp;"/boot/kernel/vboxdrv"
  857. <br />&nbsp;72203 kldload &nbsp;NAMI &nbsp;"/boot/kernel/vboxdrv.ko"
  858. <br />&nbsp;72203 kldload &nbsp;NAMI &nbsp;"/boot/modules/linker.hints"
  859. <br />&nbsp;72203 kldload &nbsp;NAMI &nbsp;"/boot/modules/vboxdrv.ko"
  860. <br />&nbsp;72203 kldload &nbsp;NAMI &nbsp;"/boot/modules/vboxdrv.ko"
  861. <br />&nbsp;72203 kldload &nbsp;NAMI &nbsp;"/boot/kernel/linker.hints"
  862. <br />&nbsp;72203 kldload &nbsp;NAMI &nbsp;"/boot/kernel/kernel"
  863. <br />&nbsp;72203 kldload &nbsp;RET &nbsp; kldload &#45;1 errno 17 File exists
  864. <br />&nbsp;72203 kldload &nbsp;CALL &nbsp;write(0x2,0x36febbf7560,0x9)
  865. <br />&nbsp;72203 kldload &nbsp;GIO &nbsp; fd 2 wrote 9 bytes
  866. <br />&nbsp;&nbsp; &nbsp; &nbsp; "kldload: "
  867. <br />&nbsp;72203 kldload &nbsp;RET &nbsp; write 9
  868. <br />&nbsp;72203 kldload &nbsp;CALL &nbsp;write(0x2,0x36febbf7650,0x39)
  869. <br />&nbsp;72203 kldload &nbsp;GIO &nbsp; fd 2 wrote 57 bytes
  870. <br />&nbsp;&nbsp; &nbsp; &nbsp; "can't load vboxnetadp: module already loaded or in kernel"
  871. <br />
  872.  </tt>
  873. </div>
  874. </blockquote>
  875.  
  876.      <p>
  877. What's it looking at there?  Clearly it's finding dependencies.  To be sure, I'd have to
  878. have a look at the source code.  But while I was scratching my head about that, I saw this
  879. on the console:
  880.      </p>
  881.  
  882.      <blockquote class="fullwidth">
  883. <div style="text-align:left">
  884.  <tt>
  885. Jun 29 10:01:52 quartet kernel: KLD vboxdrv.ko: depends on kernel &#45; not available or version mismatch
  886. <br />Jun 29 10:01:52 quartet kernel: KLD vboxnetadp.ko: depends on vboxdrv &#45; not available or version mismatch
  887. <br />
  888.  </tt>
  889. </div>
  890. </blockquote>
  891.  
  892.      <p>
  893. That's a <i>completely</i> different message.  I really need to fix that.
  894.      </p>
  895.  
  896.      <p>
  897. OK, it looks like the packages are too stupid to understand kernel dependencies.  Rebuild
  898. the ports <i>virtualbox-ose</i> and <i>virtualbox-ose-kmod</i>.  <i>virtualbox-ose</i> was
  899. an absolute pain.  First it decided to build <a href="https://en.wikipedia.org/wiki/GNU_Compiler_Collection"><i>gcc</i></a> 13, and then it
  900. tripped over irrelevant <a href="https://en.wikipedia.org/wiki/Python_(programming_language)">python</a> dependencies,
  901. which I worked around by removing the old version and trying again.  But then this one came
  902. up:
  903.      </p>
  904.  
  905.      <blockquote class="fullwidth">
  906. <div style="text-align:left">
  907.  <tt>
  908. ===> &nbsp; py311&#45;setuptools&#45;rust&#45;1.9.0 depends on executable: cargo &#45; not found
  909. <br />*** Error code 1
  910. <br />
  911.  </tt>
  912. </div>
  913. </blockquote>
  914.  
  915.      <p>
  916. What's that?  But thinking about it, do I really
  917. need <i>virtualbox-ose</i>?  <i>virtualbox-ose-kmod</i> is the kernel module.  Built that,
  918. which was relatively fast and painless, and <i>finally</i>, after something like 24 hours, I
  919. was able to load the modules.
  920.      </p>
  921.  
  922.      <p>
  923. Next, start <i>disaster</i>.  Can't do that: “VT-x is disabled in the BIOS for all CPU modes
  924. (VERR_VMX_MSR_ALL_VMX_DISABLED)”.
  925.      </p>
  926.  
  927.      <p>
  928. OK, check the <a href="https://en.wikipedia.org/wiki/BIOS">BIOS</a>.  How do I
  929. enter?  I thought it was either <b>F2</b> or <b>DEL</b> for all BIOSes, but that didn't
  930. work.  Finally a web search told me: for <a href="https://en.wikipedia.org/wiki/ThinkCentre">ThinkCentres</a>, <b>F1</b> is your friend.
  931. And there, under Advanced/CPU setup, I found that I had to enable Intel (R) Virtualization
  932. Technology, which then enabled me to enable VT-d, hopefully the same thing as VT-x, and TxT.
  933.      </p>
  934.  
  935.      <p>
  936. And that worked.  <i>Finally</i> I was able to start <i>disaster</i>.  Got
  937. an <i>rdesktop</i> session running.  And then disaster struck: I got the same network hang
  938. that I had had under <i>hydra</i>.  Only this time <i>quartet</i> had grabbed the mouse and
  939. maybe the keyboard, so I couldn't respond.  There's a solution to that, the <b>Host</b> key,
  940. normally bound to <b>Control_R</b>.  But my key map doesn't have a <b>Control_R</b>!
  941.      </p>
  942.  
  943.      <p>
  944. Shot down the VirtualBox instance, which unstuck things, and of course updated my key map to
  945. add a <b>Control-R</b> key.  I chose the crescent moon symbol at top right of the <a href="https://deskthority.net/wiki/Sun_Type_7">Sun Type 7</a> keyboard, which, as the old
  946. keymap told me, is normally bound to <b>XF86PowerOff</b>—talk about <a href="http://www.lemis.com/grog/Rant/bad-language.php#intuitive">intuitive</a>!
  947.      </p>
  948.  
  949.      <p>
  950. But somehow I'm stuck, again.  The good news seems to be that it's not related
  951. to <i>hydra</i>.  But what can I do?  Try <a href="https://en.wikipedia.org/wiki/Bhyve">bhyve</a> again?  All the instructions relate to installing <i>new</i> copies of
  952. Microsoft on <i>bhyve</i>.  Off looking again, and for the fun of it, asked <a href="https://gemini.google.com/">Gemini</a>, which indeed came up with <a href="https://gemini.google.com/app/926c37cf97ff2289">instructions</a> that don't look
  953. overly encouraging.  In particular, they require additional drivers on the guest side,
  954. something that seems to contradict the idea of a virtual machine.  But maybe I'll take a
  955. look.  In the meantime, I have real machines that can do the job.
  956.      </p>
  957.  
  958.      <p>
  959. So: for the moment, back to my other issue, <a href="https://www.fvwm.org/"><i>fvwm3</i></a>.  That shows some promise of becoming useful, even if I still don't
  960. understand it.
  961.      </p>
  962.      </div>
  963.    ]]>
  964.  </description>
  965.  <dc:creator>Greg Lehey</dc:creator>
  966.  <dc:date>2024-06-30T00:24:03+00:00</dc:date>
  967. </item>
  968.  
  969.                        
  970. <!-- topic ko not selected
  971.      <p>
  972. Baked <a href="http://www.lemis.com/grog/recipes/bread.php">bread</a> again today.  As everything was ready
  973. for proofing, I found a little more dough in the pot.  Should I mix it in again?  That's a
  974. lot of work.  What happens if I just push it on top of the dough?
  975.      </p>
  976.  
  977.            
  978.      <p>
  979. Yes, the splodges are ugly, but will they stay that way?  No, it seems.  Here before putting
  980. into the oven and afterwards:
  981.      </p>
  982.  
  983.            
  984.      <p>
  985. So I don't need to be overly careful with the surface.
  986.      </p>
  987.      
  988. End deselected topic ko (Moulding bread dough) -->
  989.  
  990.            
  991. <item>
  992. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2024.php#D-20240701-021318</guid>
  993. <link>http://www.lemis.com/grog/diary-jun2024.php?topics=c#D-20240701-021318</link>
  994. <category>health</category>
  995. <category>technology</category>
  996. <category>opinion</category>
  997. <title>Donate somebody else's organs!</title>
  998.  <description>
  999.    <![CDATA[
  1000.    <div align="justify">
  1001.      <p>
  1002. I've been planning to apply for an organ donor pass for years now, and today I found I can
  1003. do it <a href="https://www.donatelife.gov.au/">on the web</a>.  Only one minute!
  1004. Well, 3.  First I need to find my <a href="https://en.wikipedia.org/wiki/Medicare_(Australia)">Medicare</a> card and enter the
  1005. details, and then enter my name in a form that the form likes (to match what's on the card).
  1006.      </p>
  1007.  
  1008.      <p>
  1009. And that's it!  I'm a certified organ donor!  All I needed was my name, address and Medicare
  1010. card number.  I could do that for lots of people without them knowing.  In an age where
  1011. people are paranoid about security, it's amazing that I can get a spare kidney or two
  1012. without the donor knowing (even before his death).  I didn't even get a confirmation email
  1013. message.
  1014.      </p>
  1015.      </div>
  1016.    ]]>
  1017.  </description>
  1018.  <dc:creator>Greg Lehey</dc:creator>
  1019.  <dc:date>2024-07-01T02:13:18+00:00</dc:date>
  1020. </item>
  1021.  
  1022.            
  1023. <item>
  1024. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2024.php#D-20240701-021653</guid>
  1025. <link>http://www.lemis.com/grog/diary-jun2024.php?topics=c#D-20240701-021653</link>
  1026. <category>technology</category>
  1027. <category>opinion</category>
  1028. <title>Understanding Xdefaults</title>
  1029.  <description>
  1030.    <![CDATA[
  1031.    <div align="justify">
  1032.      <p>
  1033. Now I have an almost functional <a href="https://www.fvwm.org/"><i>fvwm3</i></a> configuration.  How do I polish it?  An obvious thing would be to move much of the
  1034. specifications to the <i>.Xdefaults</i> file.  I already have some stuff in there.  For
  1035. example, for <i>xterm</i>:
  1036.      </p>
  1037.  
  1038.      <blockquote class="fullwidth">
  1039. <div style="text-align:left">
  1040.  <tt>
  1041. xterm*Geometry: 100x50
  1042. <br />xterm*faceName: DejaVu Sans Mono
  1043. <br />xterm*faceSize: 9
  1044. <br />
  1045.  </tt>
  1046. </div>
  1047. </blockquote>
  1048.  
  1049.      <p>
  1050. So I don't need to put those details in the <i>fvwm3</i> config.  But what about the others?
  1051. Currently I have:
  1052.      </p>
  1053.  
  1054.      <blockquote class="fullwidth">
  1055. <div style="text-align:left">
  1056.  <tt>
  1057. + "hydra" Exec LC_ALL=en_AU.UTF&#45;8 /usr/local/bin/uxterm &#45;name "xterm" &#45;s &#45;sl 2048 &#45;sb &#45;ls &#45;j &#45;rw &#45;display :0.3 &#45;geometry 90x50+53+0 &#45;e /usr/local/bin/bash &amp;
  1058. <br />+ "hydra" Exec LC_ALL=en_AU.UTF&#45;8 /usr/local/bin/uxterm &#45;name "xterm&#45;r" &#45;s &#45;sl 2048 &#45;sb &#45;ls &#45;j &#45;rw &#45;display :0.3 &#45;geometry 90x50&#45;53+0 &#45;e /usr/local/bin/bash &amp;
  1059.  </tt>
  1060. </div>
  1061. </blockquote>
  1062.  
  1063.      <p>
  1064. That defines the <i>xterm</i> parameters for left and right <i>xterms</i>.  The big
  1065. difference is the geometry (one 53 pixels from the left margin, one 53 pixels from the right
  1066. margin).  For that, the <tt>-name</tt> parameter is different.  But how do I
  1067. tell <i>.Xdefaults</i> how to set the geometry?  Off looking in the application defaults (in
  1068. this case, <i>/usr/local/lib/X11/app-defaults/XTerm</i>), and to my surprise only found one
  1069. of the parameters that I have in <i>.Xdefaults</i>, <tt>faceSize</tt>.  And also nothing
  1070. that started with <tt>xterm*</tt>.
  1071.      </p>
  1072.  
  1073.      <p>
  1074. So where's the list?  And do the names correspond to the names on the <i>xterm</i>
  1075. invocation?  Where are they defined?  A web search just told me that <i>.Xdefaults</i> is an
  1076. old, worn-out magic word, and that <i>.Xresources</i> is better, but also no longer needed.
  1077.      </p>
  1078.  
  1079.      <p>
  1080. It's been over a third of a century since I started using <a href="https://www.x.org/">X</a>.  It seems that I have forgotten more than I have learnt.
  1081.      </p>
  1082.      </div>
  1083.    ]]>
  1084.  </description>
  1085.  <dc:creator>Greg Lehey</dc:creator>
  1086.  <dc:date>2024-07-01T02:16:53+00:00</dc:date>
  1087. </item>
  1088.  
  1089.  
  1090.                  
  1091. <!-- topic h not selected
  1092.      <p>
  1093. We're going through an unusually cool period of weather at the moment:
  1094.      </p>
  1095.  
  1096.      <blockquote class="fullwidth">
  1097. <div style="text-align:left">
  1098.  <tt>
  1099. mysql> &nbsp;<b>select year(date), min(outside_temp), avg(outside_temp), max(outside_temp)
  1100. <br />&nbsp;&nbsp; &nbsp; &nbsp; &nbsp;from observations
  1101. <br />&nbsp;&nbsp; &nbsp; &nbsp; &nbsp;where month(date) = 6
  1102. <br />&nbsp;&nbsp; &nbsp; &nbsp; &nbsp;group by year(date);</b>
  1103. <br />+&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;+&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;+&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;+&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;+
  1104. <br />| year(date) | min(outside_temp) | avg(outside_temp) &nbsp;| max(outside_temp) |
  1105. <br />+&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;+&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;+&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;+&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;+
  1106. <br />| &nbsp; &nbsp; &nbsp; 2017 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0.1 | &nbsp;8.583251664357402 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;17.2 |
  1107. <br />| &nbsp; &nbsp; &nbsp; 2018 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&#45;0.2 | &nbsp;8.587153978918375 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;18.9 |
  1108. <br />| &nbsp; &nbsp; &nbsp; 2019 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&#45;0.9 | &nbsp;9.446074306448931 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;17.6 |
  1109. <br />| &nbsp; &nbsp; &nbsp; 2020 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&#45;0.7 | &nbsp;8.782459793250906 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;16.6 |
  1110. <br />| &nbsp; &nbsp; &nbsp; 2021 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0.8 | &nbsp; 9.77173985397815 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;18.2 |
  1111. <br />| &nbsp; &nbsp; &nbsp; 2022 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0.6 | &nbsp; 8.86966862322499 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;19.6 |
  1112. <br />| &nbsp; &nbsp; &nbsp; 2023 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&#45;0.4 | 10.222608372489137 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;20.5 |
  1113. <br />| &nbsp; &nbsp; &nbsp; 2024 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&#45;2.4 | &nbsp;8.394851808112373 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;16.5 |
  1114. <br />+&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;+&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;+&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;+&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;+
  1115. <br />
  1116.  </tt>
  1117. </div>
  1118. </blockquote>
  1119.  
  1120.      <p>
  1121. And of course we had to discover that our new <a href="https://www.mitsubishielectric.com.au/product/msz-ap25-80vgd-split-system-air-conditioner/">Mitsubishi Electric MSZ-AP60VG(D)</a> air conditioner isn't really up to the task.  It
  1122. takes hours in the morning to bring the lounge room up to temperature:
  1123.      </p>
  1124.  
  1125.      <a href="Day/20240630/temperatures-2024-06-30-raw-big.png">
  1126.        <img alt="Click to see larger image" title="Click to see larger image"
  1127.             src="Day/20240630/temperatures-2024-06-30-raw-small.png"
  1128.     height="250" width="375"/>
  1129.      </a>
  1130.  
  1131.      <p>
  1132. I turned it on shortly after 5:00, and it took until 10:00 to come up to temperature (top
  1133. line).  I'm going to have to leave it running overnight.
  1134.      </p>
  1135.      
  1136. End deselected topic h (Cold weather) -->
  1137.  
  1138.            
  1139. <item>
  1140. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jul2024.php#D-20240702-015105</guid>
  1141. <link>http://www.lemis.com/grog/diary-jul2024.php?topics=c#D-20240702-015105</link>
  1142. <category>technology</category>
  1143. <category>general</category>
  1144. <category>opinion</category>
  1145. <title>Lies, damn lies and statistics</title>
  1146.  <description>
  1147.    <![CDATA[
  1148.    <div align="justify">
  1149.      <p>
  1150. Last month was cold?  How about this month?
  1151.      </p>
  1152.  
  1153.      <blockquote class="fullwidth">
  1154. <div style="text-align:left">
  1155.  <tt>
  1156. mysql> &nbsp;<b>select year(date), min(outside_temp), avg(outside_temp), max(outside_temp)
  1157. <br />&nbsp;&nbsp; &nbsp; &nbsp; &nbsp;from observations
  1158. <br />&nbsp;&nbsp; &nbsp; &nbsp; &nbsp;where month(date) = 7
  1159. <br />&nbsp;&nbsp; &nbsp; &nbsp; &nbsp;group by year(date);</b>
  1160. <br />
  1161. <br />+&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;+&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;+&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;+&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;+
  1162. <br />| year(date) | min(outside_temp) | avg(outside_temp) &nbsp;| max(outside_temp) |
  1163. <br />+&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;+&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;+&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;+&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;+
  1164. <br />| &nbsp; &nbsp; &nbsp; 2017 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&#45;1.8 | &nbsp;8.386610996751084 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;17.2 |
  1165. <br />| &nbsp; &nbsp; &nbsp; 2018 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&#45;0.5 | &nbsp; 8.84761882739429 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;19.7 |
  1166. <br />| &nbsp; &nbsp; &nbsp; 2019 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 1 | &nbsp;9.319298495442224 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;18.5 |
  1167. <br />| &nbsp; &nbsp; &nbsp; 2020 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&#45;0.8 | &nbsp;8.394708139534231 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;16.7 |
  1168. <br />| &nbsp; &nbsp; &nbsp; 2021 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&#45;0.6 | &nbsp;8.415084340357575 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;17.2 |
  1169. <br />| &nbsp; &nbsp; &nbsp; 2022 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&#45;2.6 | &nbsp;8.445030549610115 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;20.4 |
  1170. <br />| &nbsp; &nbsp; &nbsp; 2023 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&#45;0.5 | &nbsp;9.574544398292241 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;17.9 |
  1171. <br />| &nbsp; &nbsp; &nbsp; 2024 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0.9 | 2.9052224463604865 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 6.8 |
  1172. <br />+&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;+&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;+&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;+&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;+
  1173. <br />
  1174.  </tt>
  1175. </div>
  1176. </blockquote>
  1177.  
  1178.      <p>
  1179. The maximum temperature is much lower than the average of any previous year!  Of course,
  1180. that's what you get with 10 hours of overnight data.
  1181.      </p>
  1182.      </div>
  1183.    ]]>
  1184.  </description>
  1185.  <dc:creator>Greg Lehey</dc:creator>
  1186.  <dc:date>2024-07-02T01:51:05+00:00</dc:date>
  1187. </item>
  1188.  
  1189.            
  1190. <item>
  1191. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jul2024.php#D-20240702-015414</guid>
  1192. <link>http://www.lemis.com/grog/diary-jul2024.php?topics=c#D-20240702-015414</link>
  1193. <category>language</category>
  1194. <category>technology</category>
  1195. <category>food</category>
  1196. <category>and</category>
  1197. <category>drink</category>
  1198. <category>opinion</category>
  1199. <title>Constructive translations</title>
  1200.  <description>
  1201.    <![CDATA[
  1202.    <div align="justify">
  1203.      <p>
  1204. <a href="https://en.wikipedia.org/wiki/Google_Translate">Google Translate</a> is
  1205. quite useful for reading labels on East Asian food, but it has its limits.  Here's a
  1206. particularly amusing one:
  1207.      </p>
  1208.  
  1209.        <a id="Photo-3" name="Photo-3"
  1210.          href="diary-jul2024.php?dirdate=20240701&amp;imagesizes=1112&amp;topics=c#Photo-3">
  1211.          <img alt="This should be Google-translate-fail-1.jpeg.  Is it missing?" border="0" id="Photo_3"
  1212.               title="Photo Google-translate-fail-1.jpeg.  Click to redisplay larger version of image."
  1213.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20240701/small/Google-translate-fail-1.jpeg"
  1214.               width="174" height="387"
  1215.           /></a>
  1216.        <a id="Photo-4" name="Photo-4"
  1217.          href="diary-jul2024.php?dirdate=20240701&amp;imagesizes=11112&amp;topics=c#Photo-4">
  1218.          <img alt="This should be Google-translate-fail-2.jpeg.  Is it missing?" border="0" id="Photo_4"
  1219.               title="Photo Google-translate-fail-2.jpeg.  Click to redisplay larger version of image."
  1220.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20240701/small/Google-translate-fail-2.jpeg"
  1221.               width="174" height="387"
  1222.           /></a>
  1223.  
  1224.      <p>
  1225.      </p>
  1226.  
  1227.        <a id="Photo-5" name="Photo-5"
  1228.          href="diary-jul2024.php?dirdate=20240701&amp;imagesizes=111112&amp;topics=c#Photo-5">
  1229.          <img alt="This should be Google-translate-fail-1-detail.jpeg.  Is it missing?" border="0" id="Photo_5"
  1230.               title="Photo Google-translate-fail-1-detail.jpeg.  Click to redisplay larger version of image."
  1231.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20240701/small/Google-translate-fail-1-detail.jpeg"
  1232.               width="305" height="221"
  1233.           /></a>
  1234.   <a id="Photo-6" name="Photo-6"
  1235.          href="diary-jul2024.php?dirdate=20240701&amp;imagesizes=1111112&amp;topics=c#Photo-6">
  1236.          <img alt="This should be Google-translate-fail-2-detail.jpeg.  Is it missing?" border="0" id="Photo_6"
  1237.               title="Photo Google-translate-fail-2-detail.jpeg.  Click to redisplay larger version of image."
  1238.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20240701/small/Google-translate-fail-2-detail.jpeg"
  1239.               width="292" height="231"
  1240.           /></a>
  1241.  
  1242.      <p>
  1243. Somehow Google Translate is just too eager to please.
  1244.      </p>
  1245.      </div>
  1246.    ]]>
  1247.  </description>
  1248.  <dc:creator>Greg Lehey</dc:creator>
  1249.  <dc:date>2024-07-02T01:54:14+00:00</dc:date>
  1250. </item>
  1251.  
  1252.            
  1253. <!-- topic ga not selected
  1254.      <p>
  1255. Jesse Walsh along to do some more garden work today, notably the “island” in the driveway:
  1256.      </p>
  1257.  
  1258.      
  1259.      <p>
  1260. The <a href="https://en.wikipedia.org/wiki/Leucospermum">Leucospermum</a> had been
  1261. so covered in <a href="https://en.wikipedia.org/wiki/Carpobrotus">Carpobrotus</a> that there's a big bald patch:
  1262.      </p>
  1263.  
  1264.      
  1265.      <p>
  1266. At the other end also planted some small <a href="https://en.wikipedia.org/wiki/Carpobrotus">Carpobrotus</a> and some nameless plants
  1267. that <a href="http://www.lemis.com/yvonne/">Yvonne</a> got from Kelly-ann Nyari:
  1268.      </p>
  1269.  
  1270.      
  1271.      
  1272.      
  1273.      <p>
  1274. And while tidying up, he found a particularly bloated frog:
  1275.      </p>
  1276.  
  1277.      
  1278.      <p>
  1279. Also planted a long-suffering <a href="https://en.wikipedia.org/wiki/Buddleja_×_weyeriana">Buddleja_×_weyeriana</a> in front
  1280. of the “shade area”:
  1281.      </p>
  1282.  
  1283.      
  1284.      <p>
  1285.      </p>
  1286.      
  1287. End deselected topic ga (More garden work) -->
  1288.  
  1289.            
  1290. <item>
  1291. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jul2024.php#D-20240702-023308</guid>
  1292. <link>http://www.lemis.com/grog/diary-jul2024.php?topics=c#D-20240702-023308</link>
  1293. <category>technology</category>
  1294. <category>opinion</category>
  1295. <title>X configuration: RTFM!</title>
  1296.  <description>
  1297.    <![CDATA[
  1298.    <div align="justify">
  1299.      <p>
  1300. More searching for answers to the <i>.Xdefaults</i> issue today.  What does
  1301. the <i>xterm(1)</i> man page say?  <i>Much</i> more than it did 30 years ago.  Now there are
  1302. 7,758 lines, about 130 pages.  When I learnt <a href="https://www.x.org/">X</a> it
  1303. was 253 lines, less than 5 pages.  And much of this new version describes exactly what I'm
  1304. looking for: a line like <tt>xterm-r*faceName: DejaVu Sans Mono</tt> refers to a
  1305. name <tt>xterm-r</tt>, which is described in <i>X(1)</i>:
  1306.      </p>
  1307.  
  1308.      <blockquote class="fullwidth">
  1309.        <div class="listitemwidth">
  1310.          <b>-name</b>
  1311.  
  1312.  <blockquote class="fullwidth">
  1313.            <div class="list2width">
  1314.              This option specifies the name under which resources for the application should be
  1315.              found.  This option is useful in shell aliases to distinguish between invocations of
  1316.              an application, without resorting to creating links to alter the executable file name.
  1317.            </div>
  1318.  </blockquote>
  1319.        </div>
  1320.      </blockquote>
  1321.  
  1322.      <p>
  1323. And it's used like this:
  1324.      </p>
  1325.  
  1326.      <blockquote class="fullwidth">
  1327. <div style="text-align:left">
  1328.  <tt>
  1329. /usr/local/bin/uxterm <b>&#45;name "xterm&#45;r"</b> &#45;s &#45;sl 2048 &#45;sb &#45;ls &#45;j &#45;rw &#45;display :0.3 &#45;geometry 90x50&#45;53+0 &#45;e /usr/local/bin/bash
  1330.  </tt>
  1331. </div>
  1332. </blockquote>
  1333.  
  1334.      <blockquote class="fullwidth">
  1335. <div style="text-align:left">
  1336.  <tt>
  1337.  
  1338.  </tt>
  1339. </div>
  1340. </blockquote>
  1341.  
  1342.      <p>
  1343. And <tt>faceName</tt> is a resource described in the man page.
  1344.      </p>
  1345.  
  1346.      <p>
  1347. So now I have the background to actually <i>do</i> something.  Looking through the
  1348. configuration file, I find that most of these names simply refer to colours.  They're
  1349. relatively arbitrary, but they also describe the location of the icons.  Here a “before” and
  1350. “after” converting to Color
  1351.      </p>
  1352.  
  1353.      <blockquote class="fullwidth">
  1354. <div style="text-align:left">
  1355.  <tt>
  1356. Style "xterm&#45;r" &nbsp; &nbsp; Icon xterm.xpm,Color yellow/black,IconBox &nbsp;&#45;40 300 &#45;1 &#45;140
  1357. <br />Style "xterm&#45;r" &nbsp; &nbsp; Icon xterm.xpm,Colorset 21,IconBox &nbsp;&#45;40 300 &#45;1 &#45;140
  1358.  </tt>
  1359. </div>
  1360. </blockquote>
  1361.  
  1362.      <p>
  1363. So now I need to create entries for each of these names.  Currently I have <tt>xterm-lx</tt>
  1364. <tt>xterm-rx</tt>, <tt>xterm-r</tt>, <tt>xterm-rsxa</tt> and <tt>xterm-rsxd</tt>.  Do I need
  1365. all of them?  Probably not.
  1366.      </p>
  1367.  
  1368.      <p>
  1369. And then there are the options passed to the <i>xterm</i>:
  1370.      </p>
  1371.  
  1372.      <blockquote class="fullwidth">
  1373. <div style="text-align:left">
  1374.  <tt>
  1375. /usr/local/bin/uxterm &#45;name "xterm&#45;r" &#45;s &#45;sl 2048 &#45;sb &#45;ls &#45;j &#45;rw &#45;display :0.3 &#45;geometry 90x50&#45;53+0 &#45;e /usr/local/bin/bash
  1376.  </tt>
  1377. </div>
  1378. </blockquote>
  1379.  
  1380.      <ul>
  1381.        <li class="fullwidth">
  1382.          <div class="listitemwidth">
  1383.            <b>-s</b>: async scroll.  Replace with <b>multiScroll</b> resource.
  1384.          </div>
  1385.        </li>
  1386.  
  1387.        <li class="fullwidth">
  1388.          <div class="listitemwidth">
  1389.            <b>-sl 2048</b>: Save lines at top.  Replace with <b>saveLines</b> resource.
  1390.          </div>
  1391.        </li>
  1392.  
  1393.        <li class="fullwidth">
  1394.          <div class="listitemwidth">
  1395.    <b>-sb</b>: Add scroll bar.  Replace with <b>scrollBar</b> resource.
  1396.          </div>
  1397.        </li>
  1398.  
  1399.        <li class="fullwidth">
  1400.          <div class="listitemwidth">
  1401.            <b>-ls</b>: This is a login shell.  The parameter is ignored when <tt>-e</tt> is
  1402.            specified, so no replacement.
  1403.          </div>
  1404.        </li>
  1405.  
  1406.        <li class="fullwidth">
  1407.          <div class="listitemwidth">
  1408.            <b>-j</b>: Jump scroll.  Replace with <b>jumpScroll</b> resource, except that it's the
  1409.            default.
  1410.          </div>
  1411.        </li>
  1412.  
  1413.        <li class="fullwidth">
  1414.          <div class="listitemwidth">
  1415.            <b>-rw</b> Reverse wraparound.  Replace with <b>reverseWrap</b> resource.
  1416.          </div>
  1417.        </li>
  1418.  
  1419.        <li class="fullwidth">
  1420.          <div class="listitemwidth">
  1421.            <b>-geometry</b>: Specify the geometry.  Replace with <b>Geometry</b> resource.
  1422.          </div>
  1423.        </li>
  1424.      </ul>
  1425.  
  1426.      <p>
  1427. So after all that, my invocation reduces to:
  1428.      </p>
  1429.  
  1430.      <blockquote class="fullwidth">
  1431. <div style="text-align:left">
  1432.  <tt>
  1433. /usr/local/bin/uxterm &#45;name "xterm&#45;r" &#45;display :0.3 &#45;e /usr/local/bin/bash
  1434.  </tt>
  1435. </div>
  1436. </blockquote>
  1437.  
  1438.      <p>
  1439. Do I need to specify the display?  Probably not.  But there's no resource to specify the
  1440. shell; the best choice there is the <tt>SHELL</tt> environment variable.  If that works, I
  1441. can reduce things to
  1442.      </p>
  1443.  
  1444.      <blockquote class="fullwidth">
  1445. <div style="text-align:left">
  1446.  <tt>
  1447. /usr/local/bin/uxterm &#45;name "xterm&#45;r"
  1448.  </tt>
  1449. </div>
  1450. </blockquote>
  1451.  
  1452.      <p>
  1453. So do I need to generate individual files?  Yes, unfortunately.  I still have different
  1454. invocations for local and remote machines, which could potentially reduce to something like
  1455. this on <i>hydra</i>:
  1456.      </p>
  1457.  
  1458.      <blockquote class="fullwidth">
  1459. <div style="text-align:left">
  1460.  <tt>
  1461. + "eureka" Exec ssh &#45;A eureka /usr/local/bin/uxterm &#45;name "xterm&#45;r" &amp;
  1462. <br />+ "hydra" &nbsp; &nbsp; &nbsp; &nbsp;Exec /usr/local/bin/uxterm &#45;name "xterm&#45;r" &amp;
  1463. <br />
  1464.  </tt>
  1465. </div>
  1466. </blockquote>
  1467.  
  1468.      <p>
  1469. And on <i>eureka</i> it would be the other way round.  Still, things look a lot simpler like
  1470. that.  The next step is to decide what names to use, and how to allocate them.
  1471.      </p>
  1472.      </div>
  1473.    ]]>
  1474.  </description>
  1475.  <dc:creator>Greg Lehey</dc:creator>
  1476.  <dc:date>2024-07-02T02:33:08+00:00</dc:date>
  1477. </item>
  1478.  
  1479.            
  1480. <item>
  1481. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jul2024.php#D-20240702-032649</guid>
  1482. <link>http://www.lemis.com/grog/diary-jul2024.php?topics=c#D-20240702-032649</link>
  1483. <category>history</category>
  1484. <category>technology</category>
  1485. <title>20 years of wrong directions</title>
  1486.  <description>
  1487.    <![CDATA[
  1488.    <div align="justify">
  1489.      <p>
  1490. <a href="http://www.lemis.com/grog/diary-jul2004.php#1">Twenty years ago today</a> I started this
  1491. idea of saving all my <a href="https://en.wikipedia.org/wiki/Revision_Control_System">RCS</a> files in a separate hierarchy.  <b>Bad</b> idea, and it's still biting me.
  1492.      </p>
  1493.      </div>
  1494.    ]]>
  1495.  </description>
  1496.  <dc:creator>Greg Lehey</dc:creator>
  1497.  <dc:date>2024-07-02T03:26:49+00:00</dc:date>
  1498. </item>
  1499.  
  1500.            
  1501. <item>
  1502. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jul2024.php#D-20240702-032758</guid>
  1503. <link>http://www.lemis.com/grog/diary-jul2024.php?topics=c#D-20240702-032758</link>
  1504. <category>technology</category>
  1505. <category>opinion</category>
  1506. <title>bhyve: out</title>
  1507.  <description>
  1508.    <![CDATA[
  1509.    <div align="justify">
  1510.      <p>
  1511. I've already had my concerns about using <a href="https://en.wikipedia.org/wiki/Bhyve"><i>bhyve</i></a> instead of <a href="https://en.wikipedia.org/wiki/VirtualBox">VirtualBox</a>, but another thing that concerned me was how to save a running instance.
  1512. Once again <a href="https://en.wikipedia.org/wiki/Google_Gemini">Google Gemini</a> to <a href="https://gemini.google.com/app/fe86600d6842bec4">my aid</a>.  You don't:
  1513.      </p>
  1514.  
  1515.      <blockquote class="fullwidth">
  1516.        <div class="listitemwidth">
  1517.          Unfortunately, as of July 1, 2024, bhyve itself doesn't offer a built-in feature to save
  1518.          the state of a running virtual machine. This functionality is under development, but
  1519.          there's no official release yet.
  1520.        </div>
  1521.      </blockquote>
  1522.      </div>
  1523.    ]]>
  1524.  </description>
  1525.  <dc:creator>Greg Lehey</dc:creator>
  1526.  <dc:date>2024-07-02T03:27:58+00:00</dc:date>
  1527. </item>
  1528.  
  1529.                  
  1530. <!-- topic HPo not selected
  1531.      <p>
  1532. The <a href="https://en.wikipedia.org/wiki/Supreme_Court_of_the_USA">Supreme Court of
  1533. the USA</a> has made an <a href="https://www.washingtonpost.com/politics/2024/07/01/trump-presidential-immunity-supreme-court/">amazing decision</a>: the President is above the law.
  1534.      </p>
  1535.  
  1536.      <p>
  1537. I needed to catch my breath.  This special treatment of the ruler was one of the differences
  1538. between the USA and Great Britain.  It seems that the concept of equality under the law is
  1539. not stated as clearly in US law as it is elsewhere, but the <a href="https://en.wikipedia.org/wiki/Fourteenth_Amendment_to_the_United_States_Constitution">Fourteenth Amendment to the United States Constitution</a> implies it, and it also
  1540. states:
  1541.      </p>
  1542.  
  1543.      <blockquote class="fullwidth">
  1544.        <div class="listitemwidth">
  1545.          <b>Section 3</b>. No person shall be a Senator or Representative in Congress, or elector
  1546.          of President and Vice President, or hold any office, civil or military, under the United
  1547.          States, or under any State, who, having previously taken an oath, as a member of Congress,
  1548.          or as an officer of the United States, or as a member of any State legislature, or as an
  1549.          executive or judicial officer of any State, to support the Constitution of the United
  1550.          States, shall have engaged in insurrection or rebellion against the same, or given aid or
  1551.          comfort to the enemies thereof.
  1552.        </div>
  1553.      </blockquote>
  1554.  
  1555.      <p>
  1556. And, it seems, this decision reverses exactly the issue of the <a href="https://en.wikipedia.org/wiki/Fourteenth_Amendment_to_the_United_States_Constitution#January_6_United_States_Capitol_attack">attack on the US Capitol</a> on 6 January 2021.  How can that happen?  My understanding
  1557. is that the only way to reverse this decision is for the Supreme Court to change its mind.
  1558.      </p>
  1559.  
  1560.      <p>
  1561. The consequences are staggering.  <a href="https://www.theshovel.com.au/">The
  1562. Shovel</a> put it into perspective.  <a href="https://theshovel.com.au/2024/07/02/biden-responds-to-supreme-court-ruling-by-assassinating-donald-trump/">Biden Responds to Supreme Court Ruling by Immediately Assassinating Donald Trump</a>.
  1563. Part of the article is worth reading:
  1564.      </p>
  1565.  
  1566.      <blockquote class="fullwidth">
  1567.        <div class="listitemwidth">
  1568.          The Biden team used an unconventional method to carry out the assassination – an actor
  1569.          posing as Vladimir Putin was hired to tell Trump that he doesn’t like him. Trump
  1570.          immediately died of sadness.
  1571.        </div>
  1572.      </blockquote>
  1573.  
  1574.      <p>
  1575. But somehow that's the death knell of US democracy.  The 2020s have not been a good decade
  1576. so far.  I see even worse times ahead.
  1577.      </p>
  1578.      
  1579. End deselected topic HPo (The end of US democracy?) -->
  1580.  
  1581.            
  1582. <!-- topic g not selected
  1583.      <p>
  1584. Our front gate does not shut very accurately, and lately it has been overshooting the
  1585. “closed” position.  A minor adjustment, maybe?
  1586.      </p>
  1587.  
  1588.      <div align="left">
  1589.      </div>
  1590.  
  1591.      <p>
  1592. It doesn't look like much, but I think it should be enough.  I didn't want to overdo it and
  1593. risk breaking off the hook.
  1594.      </p>
  1595.      
  1596. End deselected topic g (Fixing the gate) -->
  1597.  
  1598.            
  1599. <item>
  1600. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jul2024.php#D-20240703-011908</guid>
  1601. <link>http://www.lemis.com/grog/diary-jul2024.php?topics=c#D-20240703-011908</link>
  1602. <category>general</category>
  1603. <category>technology</category>
  1604. <category>opinion</category>
  1605. <title>ANZ: You typed the wrong password</title>
  1606.  <description>
  1607.    <![CDATA[
  1608.    <div align="justify">
  1609.      <p>
  1610. Time for my monthly check on my bank accounts today.  But no, my <a href="https://en.wikipedia.org/wiki/ANZ_Bank">ANZ</a> web page told me that my password was
  1611. wrong.
  1612.      </p>
  1613.  
  1614.      <p>
  1615. What?  It's stored in the web browser.  I also have it written down, so I tried that.  No,
  1616. wrong.  Please reset.
  1617.      </p>
  1618.  
  1619.      <p>
  1620. How did that happen?  It's definitely not my doing.  Called up and finally, after nearly a
  1621. minute of announcements, I was asked the reason for my call.  “I think my password has been
  1622. breached”.
  1623.      </p>
  1624.  
  1625.      <p>
  1626. <b><i>WRONG</i></b>.  Another two minutes explaining to me how to use the <a href="https://play.google.com/store/apps/details?id=com.anz.android.gomoney">ANZ App</a> to
  1627. reset my password.  And then I was disconnected.  Nearly 3 minutes for nothing.
  1628.      </p>
  1629.  
  1630.      <p>
  1631. Tried again, this time telling the non-recognition that I had a security breach.  OK, 5 to
  1632. 10 minute wait, which proved to be closer to 15.  Connected to Gracia, who told me that no
  1633. special characters were allowed in the password, and then helped me reset it after a third
  1634. time also failed and locked me out of my account.
  1635.      </p>
  1636.  
  1637.      <p>
  1638. When was my password last changed?  2 May, she said.  OK, I've logged in since then, so if
  1639. their site didn't let me log in, there must be something seriously wrong.  Please inform
  1640. your security team.  ”I am the security team”.  No escalation needed: I typed my password
  1641. with an special character or some other error.
  1642.      </p>
  1643.  
  1644.      <p>
  1645. Please take a complaint.  After three attempts and a threat to involve the regulatory
  1646. bodies, she agreed to do so.  Give me the complaint number, please.  Can't do that yet, will
  1647. send a “text message”, presumably an <a href="https://en.wikipedia.org/wiki/SMS">SMS</a>.  No, I'd like to have an email, please.  Sorry, we can't send email.  Wait on
  1648. the line.
  1649.      </p>
  1650.  
  1651.      <p>
  1652. Finally she came back with the number.  And where do we go from here?  She seemed to think
  1653. that that was the last I would hear of it, and maybe she's right.  And after all, she said,
  1654. I just typed my password in wrong.
  1655.      </p>
  1656.  
  1657.      <p>
  1658. I exploded, being rather rude and calling her an idiot.  I regret that, but I've seldom had
  1659. such a frustrating and stupid interaction.
  1660.      </p>
  1661.  
  1662.      <p>
  1663. And after it was all over and done, I got an email with the complaint number.
  1664.      </p>
  1665.  
  1666.      <p>
  1667. Somehow this is <i>so</i> like the interaction with <a href="https://aussiebroadband.com.au/">Aussie Broadband</a> <a href="http://www.lemis.com/grog/diary-apr2024.php#D-20240407-003200">a few months ago</a>.  We're being
  1668. held to ransom by the “help desk” people.
  1669.      </p>
  1670.      </div>
  1671.    ]]>
  1672.  </description>
  1673.  <dc:creator>Greg Lehey</dc:creator>
  1674.  <dc:date>2024-07-03T01:19:08+00:00</dc:date>
  1675. </item>
  1676.  
  1677.                  
  1678. <!-- topic Jgh not selected
  1679.      <p>
  1680. Steven from <a href="https://www.ultimategroup.com.au/">UPI</a> along today with an
  1681. apprentice (Riley?) to look at the wiring of the bore pump.  Irritatingly, it worked for
  1682. him, sort of.  At least the pump ran.  But it seems that these junction boxes are really
  1683. pressure switches, one for the pump, one for the pressure cell.  And both of them were badly
  1684. corroded by the bore water:
  1685.      </p>
  1686.  
  1687.      
  1688.      <p>
  1689. So he had to replace both of them, along with the pressure gauge:
  1690.      </p>
  1691.  
  1692.      
  1693.      <p>
  1694. Why are they not made of a material that doesn't corrode?  They're very expensive—the parts
  1695. alone came to a total of $450.
  1696.      </p>
  1697.      
  1698. End deselected topic Jgh (Repairing the bore pump) -->
  1699.  
  1700.            
  1701. <!-- topic ko not selected
  1702.      <p>
  1703. It's been <a href="http://www.lemis.com/grog/diary-jun2024.php?subtitle=Preserved%20lemons&amp;article=D-20240626-011901#D-20240626-011901">a little over a week</a> since I started on my preserved lemons:
  1704.      </p>
  1705.  
  1706.            
  1707.      <p>
  1708. Now they look like this:
  1709.      </p>
  1710.  
  1711.      
  1712.      <p>
  1713. One of the big differences between the recipes was whether to add lemon juice or not.  The
  1714. rationale is that the lemons will go mouldy if they're not covered.  No recipe specifically
  1715. wants them uncovered, so my guess is that the ones that don't add juice expect there to be
  1716. enough juice in the lemons themselves.  Clearly that's not the case here, so today I added
  1717. what proved to be 100 ml of lemon juice:
  1718.      </p>
  1719.  
  1720.      
  1721.      <p>
  1722. So far there's not much evidence of softening.
  1723.      </p>
  1724.      
  1725. End deselected topic ko (Preserved lemons, status) -->
  1726.  
  1727.                  
  1728. <!-- topic hkG not selected
  1729.      <p>
  1730. Somehow a number of things have cropped up that required me to go shopping: <a href="http://www.lemis.com/grog/Albums/Animals/Mona.php">Mona</a> has learnt how to open doors, so we need knobs
  1731. instead of levers.  As often, I needed a visit to the <a href="https://www.facebook.com/fruitshackwendouree/">Fruit Shack</a>, and my glasses still
  1732. needed adjustment.  In addition, <a href="https://en.wikipedia.org/wiki/ALDI">ALDI</a> had an air compressor on offer, and it was too heavy for <a href="http://www.lemis.com/yvonne/">Yvonne</a> to pick up yesterday, so did that too.
  1733.      </p>
  1734.  
  1735.      <p>
  1736. And somehow the day was done.  The good news is that everything went smoothly, not a
  1737. foregone conclusion.
  1738.      </p>
  1739.      
  1740. End deselected topic hkG (Shopping again) -->
  1741.  
  1742.            
  1743. <item>
  1744. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jul2024.php#D-20240705-023636</guid>
  1745. <link>http://www.lemis.com/grog/diary-jul2024.php?topics=c#D-20240705-023636</link>
  1746. <category>technology</category>
  1747. <category>opinion</category>
  1748. <title>ANZ password: Groggy's fault</title>
  1749.  <description>
  1750.    <![CDATA[
  1751.    <div align="justify">
  1752.      <p>
  1753. Checking my local web pages, discovered this:
  1754.      </p>
  1755.  
  1756.      <blockquote class="fullwidth">
  1757. <div style="text-align:left">
  1758.  <tt>
  1759. &nbsp;&nbsp;&#45;r&#45;&#45;r&#45;&#45;r&#45;&#45; &nbsp; &nbsp;1 grog &nbsp;lemis &nbsp; &nbsp;6462 &nbsp;2 May 14:32 bank.php
  1760.  </tt>
  1761. </div>
  1762. </blockquote>
  1763.  
  1764.      <p>
  1765. That's the page I use to access financial web sites.  And it had a new password, one that I
  1766. hadn't transferred to my password list.  So the issues that I had <a href="http://www.lemis.com/grog/diary-jul2024.php#D-20240703-011908">on Tuesday</a> <i>were</i> my fault
  1767. after all.
  1768.      </p>
  1769.  
  1770.      <p>
  1771. Did Gracia do the right thing then?  No. she couldn't have known that, and her utter
  1772. conviction that I had typed a special character in the password shows a lack of will to
  1773. investigate the real issues.  But I <i>do</i> feel silly.
  1774.      </p>
  1775.      </div>
  1776.    ]]>
  1777.  </description>
  1778.  <dc:creator>Greg Lehey</dc:creator>
  1779.  <dc:date>2024-07-05T02:36:36+00:00</dc:date>
  1780. </item>
  1781.  
  1782.            
  1783. <item>
  1784. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jul2024.php#D-20240705-024130</guid>
  1785. <link>http://www.lemis.com/grog/diary-jul2024.php?topics=c#D-20240705-024130</link>
  1786. <category>technology</category>
  1787. <category>general</category>
  1788. <category>opinion</category>
  1789. <title>Problems with NBN scheduled outages</title>
  1790.  <description>
  1791.    <![CDATA[
  1792.    <div align="justify">
  1793.      <p>
  1794. It seems that I'm <a href="https://jokesfunnystories.quora.com/Do-you-know-any-original-and-new-jokes-8">not the
  1795. only person</a> to get annoyed by <a href="https://www.nbnco.com.au/">National
  1796. Broadband Network</a> scheduled outages.
  1797.      </p>
  1798.      </div>
  1799.    ]]>
  1800.  </description>
  1801.  <dc:creator>Greg Lehey</dc:creator>
  1802.  <dc:date>2024-07-05T02:41:30+00:00</dc:date>
  1803. </item>
  1804.  
  1805.                  
  1806. <!-- topic ko not selected
  1807.      <p>
  1808. The (Korean) title 두부부침양념장 transliterates as <a href="https://www.maangchi.com/recipe/dububuchim-yangnyeomjang"> dububuchim-yangnyeomjang</a>, a tongue-twister that even reflects in the Korean spelling.  It translates as “Pan fried
  1809. tofu with spicy sauce”, but it seems easier to distinguish it by calling it <a href="http://www.lemis.com/grog/recipes/Korean-fried-dofu.php">Korean fried dofu</a>.
  1810.      </p>
  1811.  
  1812.      <p>
  1813. The photo looked good:
  1814.      </p>
  1815.  
  1816.      <a href="https://www.maangchi.com/wp-content/uploads/2009/09/panfriedtofu-sprinkle-sesameseeds-620x400.jpg">
  1817.      <img alt=""
  1818.          title=".  Click to see in original size."
  1819.          src="https://www.maangchi.com/wp-content/uploads/2009/09/panfriedtofu-sprinkle-sesameseeds-620x400.jpg"
  1820.          width="300"
  1821.          /></a>
  1822.      <p>
  1823. So yesterday I bought some <a href="https://en.wikipedia.org/wiki/Dofu">dofu</a>,
  1824. not quite the same as used in the recipe:
  1825.      </p>
  1826.  
  1827.      
  1828.      <p>
  1829. In particular, the pieces are smaller.
  1830.      </p>
  1831.  
  1832.      <p>
  1833. After a bit of recipe translation, came up with this:
  1834.      </p>
  1835.  
  1836.      
  1837.      <p>
  1838. The rice is mentioned in the original recipe, but not illustrated.
  1839.      </p>
  1840.  
  1841.      <h2>Ingredients</h2>
  1842.  
  1843.      <p>
  1844. Per serving
  1845.      </p>
  1846.  
  1847.          <table summary="Ingredients">
  1848.        <tr>
  1849.          <td align="right"><b>quantity</b></td>
  1850.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1851.          <td><b>ingredient</b> </td>
  1852.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1853.          <td><b>step</b> </td>
  1854.        </tr>
  1855.  
  1856.       <tr>
  1857.          <td valign="top" align="right">150 g</td>
  1858.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1859.          <td valign="top" align="left">firm dofu</td>
  1860.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1861.          <td valign="top" align="right">1</td>
  1862.       </tr>
  1863.       <tr>
  1864.         <td>
  1865.         </td>
  1866.       </tr>
  1867.  
  1868.       <tr>
  1869.          <td valign="top" align="right">12 g</td>
  1870.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1871.          <td valign="top" align="left">soya sauce</td>
  1872.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1873.          <td valign="top" align="right">2</td>
  1874.       </tr>
  1875.  
  1876.       <tr>
  1877.          <td valign="top" align="right">5 g</td>
  1878.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1879.          <td valign="top" align="left">gochugaru (Korean chili flakes, 고춧가루)</td>
  1880.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1881.          <td valign="top" align="right">2</td>
  1882.       </tr>
  1883.  
  1884.       <tr>
  1885.          <td valign="top" align="right">15 g</td>
  1886.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1887.          <td valign="top" align="left">garlic</td>
  1888.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1889.          <td valign="top" align="right">2</td>
  1890.       </tr>
  1891.  
  1892.       <tr>
  1893.          <td valign="top" align="right">30 g</td>
  1894.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1895.          <td valign="top" align="left">onion, chopped finely</td>
  1896.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1897.          <td valign="top" align="right">2</td>
  1898.       </tr>
  1899.  
  1900.       <tr>
  1901.          <td valign="top" align="right">12 ml</td>
  1902.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1903.          <td valign="top" align="left">sesame oil</td>
  1904.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1905.          <td valign="top" align="right">2</td>
  1906.       </tr>
  1907.  
  1908.       <tr>
  1909.          <td valign="top" align="right"></td>
  1910.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1911.          <td valign="top" align="left">sesame seeds</td>
  1912.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1913.          <td valign="top" align="right">2</td>
  1914.       </tr>
  1915.       <tr>
  1916.         <td>
  1917.         </td>
  1918.       </tr>
  1919.  
  1920.       <tr>
  1921.          <td valign="top" align="right">15 g (1)</td>
  1922.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1923.          <td valign="top" align="left">spring onion</td>
  1924.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1925.          <td valign="top" align="right">3</td>
  1926.       </tr>
  1927.       <tr>
  1928.         <td>
  1929.         </td>
  1930.       </tr>
  1931.      </table>
  1932.  
  1933.      <h2>
  1934. Preparation
  1935.      </h2>
  1936.  
  1937.      <ol>
  1938.        <li class="fullwidth">
  1939.          <p class="listitemwidth">
  1940.            Cut the dofu into slices about 6-7 mm thick:
  1941.          </p>
  1942.  
  1943.  
  1944.  <p class="listitemwidth">
  1945.    Fry until crispy:
  1946.  </p>
  1947.  
  1948.          </li>
  1949.  
  1950.        <li class="fullwidth">
  1951.          <p class="listitemwidth">
  1952.            Mix the ingredients together:
  1953.          </p>
  1954.  
  1955.          </li>
  1956.  
  1957.        <li class="fullwidth">
  1958.          <p class="listitemwidth">
  1959.            Cut spring onion and add to the sauce:
  1960.          </p>
  1961.  
  1962.          </li>
  1963.  
  1964.        <li class="fullwidth">
  1965.          <p class="listitemwidth">
  1966.            Serve with rice:
  1967.          </p>
  1968.  
  1969.          </li>
  1970.      </ol>
  1971.      
  1972. End deselected topic ko (두부부침양념장) -->
  1973.  
  1974.            
  1975. <!-- topic Po not selected
  1976.      <p>
  1977. A number of national elections are creating interest at the moment: the <a href="https://en.wikipedia.org/wiki/USA">USA</a>, <a href="https://en.wikipedia.org/wiki/Iran">Iran</a>, <a href="https://en.wikipedia.org/wiki/France">France</a> and now the <a href="https://en.wikipedia.org/wiki/United_Kingdom">United Kingdom</a>.  The USA elections
  1978. have been number one topic for months, and there are another 4 months to go (until
  1979. <a href="https://en.wikipedia.org/wiki/Melbourne_Cup">Melbourne Cup</a> day).
  1980. France started its election campaign at the beginning of last month and had elections on
  1981. Sunday, only the results were a tie, so they need a second round come Sunday.  In Iran it
  1982. was similar: they called elections at the beginning of last month, they were held last
  1983. Friday, and they, too, need a run-off that will take place today.
  1984.      </p>
  1985.  
  1986.      <p>
  1987. Meanwhile, in the UK, they <i>also</i> called elections at the beginning of last month.
  1988. They took place yesterday.  No run-off: polling ended at 22:00 BST (7:00 this morning here),
  1989. and by the evening the <a href="https://en.wikipedia.org/wiki/King_Charles_III">King</a> had invited <a href="https://en.wikipedia.org/wiki/Sir_Keir_Starmer">Sir
  1990. Keir Starmer</a> to form a government.  No messing around like in the USA, where the
  1991. incumbent has 2½ months to subvert the election before the president-elect actually takes
  1992. office.
  1993.      </p>
  1994.      
  1995. End deselected topic Po (Britain votes and gets on with it) -->
  1996.  
  1997.            
  1998. <!-- topic Jaho not selected
  1999.      <p>
  2000. I really don't like the idea of round doorknobs: they're significantly more difficult to
  2001. handle than the lever type.  But <a href="http://www.lemis.com/grog/Albums/Animals/Mona.php">Mona</a> agrees, so I have to do something.
  2002.      </p>
  2003.  
  2004.      <p>
  2005. Then <a href="http://www.lemis.com/yvonne/">Yvonne</a> came up with the obvious answer: reposition the
  2006. levers so that they're pointing down.  Now why didn't I come up with that idea?  But it
  2007. turned out that the maker of the levers had found an asnwer: you can't.  So I had to mount
  2008. the knobs after all:
  2009.      </p>
  2010.  
  2011.            
  2012.      <p>
  2013. Mona was not amused.  In the evening we heard her trying to get into my office and failing.
  2014. She didn't exactly growl, but her tail was twice the normal thickness.  Somehow I feel that
  2015. I have let her down: here she had the great success of finding a new way through doors, and
  2016. already it stops working.
  2017.      </p>
  2018.      
  2019. End deselected topic Jaho (New doorknobs) -->
  2020.  
  2021.                  
  2022. <!-- topic ko not selected
  2023.      <p>
  2024. I have a surprising amount of <a href="https://en.wikipedia.org/wiki/Dofu">dofu</a> and almost no recipes for it.  How about using some in my <a href="http://www.lemis.com/grog/recipes/pad-thai-breakfast.php">Pad Thai</a> recipe?  Fried the slices a little
  2025. hotter (7 on the induction cooker), which resulted in much faster browning, but despite all
  2026. attempts they still stuck a little.
  2027.      </p>
  2028.  
  2029.      
  2030.      <p>
  2031. And while I was at it, I used a different <a href="https://en.wikipedia.org/wiki/ALDI">ALDI</a> paste (first image) instead of their “Pad Thai” paste:
  2032.      </p>
  2033.  
  2034.            
  2035.      <p>
  2036. The result?
  2037.      </p>
  2038.  
  2039.      
  2040.      <p>
  2041. Boring!  And the “stirfry” sauce tasted of almost nothing.
  2042.      </p>
  2043.      
  2044. End deselected topic ko (Breakfast experiment fail) -->
  2045.  
  2046.            
  2047. <item>
  2048. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jul2024.php#D-20240707-014443</guid>
  2049. <link>http://www.lemis.com/grog/diary-jul2024.php?topics=c#D-20240707-014443</link>
  2050. <category>technology</category>
  2051. <category>history</category>
  2052. <category>opinion</category>
  2053. <title>A mouse!</title>
  2054.  <description>
  2055.    <![CDATA[
  2056.    <div align="justify">
  2057.      <p>
  2058. I'm still planning to put in the new <i>teevee.lemis.com</i> in the lounge room Real Soon
  2059. Now.  The intention is to run it in parallel with <i>tiwi</i> until I'm happy.  Until then,
  2060. all the videos will be on <i>tiwi</i>.  Things that are missing are: keyboard, mouse,
  2061. display card (maybe).
  2062.      </p>
  2063.  
  2064.      <p>
  2065. Surely I have lots of keyboards and mice?  Yes, I do, but for some reason they “don't work”,
  2066. at least partially because all the dongles are unmarked, and <a href="http://www.lemis.com/grog/diary-jan2024.php?subtitle=Configuring%20mouse%20in%20the%20new%20scheme%20of%20things&amp;article=D-20240105-003925#D-20240105-003925">none of my experiments in pairing them</a> have worked.  So when I was in town <a href="http://www.lemis.com/grog/diary-jul2024.php?subtitle=Shopping%20again&amp;article=D-20240705-023305#D-20240705-023305">on Thursday</a>, I picked up an el-cheapo wireless keyboard and mouse from <a href="https://en.wikipedia.org/wiki/Officeworks">Officeworks</a>, total price $33.
  2067.      </p>
  2068.  
  2069.      <p>
  2070. They had others on offer, including things aimed at Apple for round 10 times the price, so I
  2071. wasn't expecting very much.  But what I found was much better than I dared to hope.
  2072.      </p>
  2073.  
  2074.      <p>
  2075. Backspace 35 years to my first graphics environments.  Mice had three buttons and nothing
  2076. else, and of course they were wired.  Since then a number of things have happened: wireless
  2077. mice appeared (<i><b>very</b></i> good; I had to use cable mice again recently, and they're
  2078. a real pain), scroll wheels appeared (also useful), and the second button went away
  2079. (<b><i>bad</i></b>).  To make up for it, some high-end mice ended up with additional buttons
  2080. for the (right) thumb, and I was able to remap them to button 2.  But the cheap mice didn't.
  2081.      </p>
  2082.  
  2083.      <p>
  2084. But this one does!  In fact, the button layout is the same as my <a href="https://en.wikipedia.org/wiki/Logitech">Logitech</a> M705: two main buttons, scroll
  2085. wheel in between, which can also be pressed for a button press, and two buttons for the
  2086. thumb.  <i>xev</i> tells me:
  2087.      </p>
  2088.  
  2089.      <table summary="Automatically generated table">
  2090.       <tr>
  2091.          <td valign="top" align="left">left</td>
  2092.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2093.          <td valign="top" align="left">right</td>
  2094.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2095.          <td valign="top" align="left">scroll</td>
  2096.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2097.          <td valign="top" align="left">scroll</td>
  2098.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2099.          <td valign="top" align="left">scroll</td>
  2100.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2101.          <td valign="top" align="left">thumb</td>
  2102.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2103.          <td valign="top" align="left">thumb</td>
  2104.       </tr>
  2105.  
  2106.       <tr>
  2107.          <td valign="top" align="left"></td>
  2108.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2109.          <td valign="top" align="left"></td>
  2110.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2111.          <td valign="top" align="left">forward</td>
  2112.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2113.          <td valign="top" align="left">back</td>
  2114.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2115.          <td valign="top" align="left">press</td>
  2116.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2117.          <td valign="top" align="left">forward</td>
  2118.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2119.          <td valign="top" align="left">back</td>
  2120.       </tr>
  2121.  
  2122.       <tr>
  2123.          <td valign="top" align="left">1</td>
  2124.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2125.          <td valign="top" align="left">3</td>
  2126.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2127.          <td valign="top" align="left">4</td>
  2128.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2129.          <td valign="top" align="left">5</td>
  2130.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2131.          <td valign="top" align="left">2</td>
  2132.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2133.          <td valign="top" align="left">9</td>
  2134.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2135.          <td valign="top" align="left">8</td>
  2136.       </tr>
  2137.  
  2138.       <tr>
  2139.          <td valign="top" align="left"></td>
  2140.       </tr>
  2141.    </table>
  2142.  
  2143.      <p>
  2144. That's the same for the Logitech mouse, except that the thumb buttons have been remapped.
  2145.      </p>
  2146.  
  2147.      <p>
  2148. The probe messages are:
  2149.      </p>
  2150.  
  2151.      <blockquote class="fullwidth">
  2152. <div style="text-align:left">
  2153.  <tt>
  2154. ugen0.3: &lt;Telink 2.4G Mouse&gt; at usbus0
  2155. <br />ums1 on uhub4
  2156. <br />ums1: &lt;Telink 2.4G Mouse, class 0/0, rev 1.10/1.00, addr 34&gt; on usbus0
  2157. <br />ums1: 5 buttons and [XYZ] coordinates ID=1
  2158. <br />
  2159.  </tt>
  2160. </div>
  2161. </blockquote>
  2162.  
  2163.      <p>
  2164. That's much more than I had hoped for.  And to make things even better, the mouse has a
  2165. storage place for the dongle, so if I do take it out of service, at least I won't have to
  2166. look for the dongle.
  2167.      </p>
  2168.      </div>
  2169.    ]]>
  2170.  </description>
  2171.  <dc:creator>Greg Lehey</dc:creator>
  2172.  <dc:date>2024-07-07T01:44:43+00:00</dc:date>
  2173. </item>
  2174.  
  2175.                  
  2176. <!-- topic p not selected
  2177.      <p>
  2178. I've been using my <a href="http://en.wikipedia.org/wiki/Olympus_E-30">Olympus E-30</a> for
  2179. photos of a still-planned <a href="https://en.wikipedia.org/wiki/Analemma">Analemma</a> series for <a href="http://www.lemis.com/grog/diary-aug2019.php?subtitle=Analemma%20experiments&amp;article=D-20190811-031250#D-20190811-031250">almost 5 years</a>.  I use a 10 stop (99.9%) neutral density filter and take two images,
  2180. one at 1/4000 s and f/5.6 for the sun, and the other at 2 s and f/5.6 for the surroundings:
  2181.      </p>
  2182.  
  2183.            
  2184.      <p>
  2185. The intention is to align the surrounding images, and then use the same alignment to join
  2186. the sun images.  I must now really have images for every day of the year, and at some point
  2187. I should really get round to doing it.
  2188.      </p>
  2189.  
  2190.      <p>
  2191. But today it occurred to me that I have almost never taken photos with the camera and
  2192. auto-exposure.  Tried that today.  Big fail:
  2193.      </p>
  2194.  
  2195.      
  2196.      <p>
  2197. It must have been 6 <a href="https://en.wikipedia.org/wiki/Exposure_value">EV</a> underexposed.  Even attempts to correct it didn't help much.
  2198.      </p>
  2199.  
  2200.      
  2201.      <p>
  2202. What went wrong there?  Yes, I still had the ND filter on, but auto-exposure should have
  2203. compensated for that.
  2204.      </p>
  2205.      
  2206. End deselected topic p (Olympus E-30 auto-exposure) -->
  2207.  
  2208.            
  2209. <item>
  2210. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jul2024.php#D-20240708-014220</guid>
  2211. <link>http://www.lemis.com/grog/diary-jul2024.php?topics=c#D-20240708-014220</link>
  2212. <category>technology</category>
  2213. <category>opinion</category>
  2214. <title>Understanding mice</title>
  2215.  <description>
  2216.    <![CDATA[
  2217.    <div align="justify">
  2218.      <p>
  2219. More playing around with my new mouse today, on <i>tiwi</i>.  Yes, it works, but how do I
  2220. remap the side buttons?  <i>moused</i> is started with
  2221.      </p>
  2222.  
  2223.      <blockquote class="fullwidth">
  2224. <div style="text-align:left">
  2225.  <tt>
  2226. root &nbsp; &nbsp; &nbsp; 36620 &nbsp; 0,0 &nbsp;0,0 &nbsp; &nbsp;13112 &nbsp; &nbsp;1720 &nbsp;&#45; &nbsp;Is &nbsp; 22:13 &nbsp; &nbsp; &nbsp; &nbsp; 0:00,00 /usr/sbin/moused &#45;3 &#45;p /dev/ums1 &#45;t auto &#45;I /var/run/moused.ums1.pid
  2227. <br />
  2228.  </tt>
  2229. </div>
  2230. </blockquote>
  2231.  
  2232.      <p>
  2233. That doesn't even match the entries in <i>/etc/rc.conf.d</i>:
  2234.      </p>
  2235.  
  2236.      <blockquote class="fullwidth">
  2237. <div style="text-align:left">
  2238.  <tt>
  2239. moused:moused_enable="YES"
  2240. <br />moused:moused_flags="&#45;m 2=4" &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;# Remap rear side button to 2.
  2241. <br />
  2242.  </tt>
  2243. </div>
  2244. </blockquote>
  2245.  
  2246.      <p>
  2247. And if it did, it wouldn't help: the side buttons are 8 and 9, not 4.  Is there something in
  2248. the <a href="https://www.x.org/">X</a> configuration file?  No:
  2249.      </p>
  2250.  
  2251.      <blockquote class="fullwidth">
  2252. <div style="text-align:left">
  2253.  <tt>
  2254. Section "InputDevice"
  2255. <br />&nbsp;&nbsp; &nbsp;# generated from default
  2256. <br />&nbsp;&nbsp; &nbsp;Identifier &nbsp; &nbsp; "Mouse0"
  2257. <br />&nbsp;&nbsp; &nbsp;Driver &nbsp; &nbsp; &nbsp; &nbsp; "mouse"
  2258. <br />&nbsp;&nbsp; &nbsp;Option &nbsp; &nbsp; &nbsp; &nbsp; "Protocol" "auto"
  2259. <br />&nbsp;&nbsp; &nbsp;Option &nbsp; &nbsp; &nbsp; &nbsp; "Device" "/dev/sysmouse"
  2260. <br />&nbsp;&nbsp; &nbsp;Option &nbsp; &nbsp; &nbsp; &nbsp; "Emulate3Buttons" "yes"
  2261. <br />&nbsp;&nbsp; &nbsp;Option &nbsp; &nbsp; &nbsp; &nbsp; "ZAxisMapping" "4 5"
  2262. <br />EndSection
  2263. <br />
  2264.  </tt>
  2265. </div>
  2266. </blockquote>
  2267.  
  2268.      <p>
  2269. OK, shoot down the <i>moused</i> instance and start it again with the correct
  2270. option <tt>&#45;m&nbsp;2=8</tt>.  But when I shot it down, the mouse carried on
  2271. working!  <i>/dev/sysmouse</i> must bypass the driver daemon.
  2272.      </p>
  2273.  
  2274.      <p>
  2275. I've
  2276. been playing with X configuration for <a href="http://www.lemis.com/grog/diary-mar1992.php?subtitle=Beta%20test%20report,%20BSDI/386,%2020%20March%201992&amp;article=D20-10#D20-10">over 30 years</a>, but they keep changing the goalposts.
  2277.      </p>
  2278.      </div>
  2279.    ]]>
  2280.  </description>
  2281.  <dc:creator>Greg Lehey</dc:creator>
  2282.  <dc:date>2024-07-08T01:42:20+00:00</dc:date>
  2283. </item>
  2284.  
  2285.            
  2286. <!-- topic ko not selected
  2287.      <p>
  2288. <a href="http://www.lemis.com/yvonne/">Yvonne</a> made dinner tonight, a fish gratin:
  2289.      </p>
  2290.  
  2291.      <div align="left">
  2292.      </div>
  2293.  
  2294.      <p>
  2295.      </p>
  2296.      
  2297. End deselected topic ko (Fish gratin) -->
  2298.  
  2299.                  
  2300. <!-- topic Po not selected
  2301.      <p>
  2302. There were three important elections in the last few days: the <a href="https://en.wikipedia.org/wiki/United_Kingdom">United Kingdom</a> <a href="https://en.wikipedia.org/wiki/2024_United_Kingdom_general_election">general election</a>, the <a href="https://en.wikipedia.org/wiki/2024_French_legislative_election">French legislative election</a> and the <a href="https://en.wikipedia.org/wiki/2024_Iranian_presidential_election">Iranian presidential
  2303. election</a>.  All of them were interesting: arguably the results in the UK and Iran show
  2304. positive tendencies, and in France they were able to limit the power of the <a href="https://en.wikipedia.org/wiki/Rassemblement_National">Rassemblement National</a>.
  2305.      </p>
  2306.  
  2307.      <p>
  2308. But the details are interesting: in France and Iran the elections were second rounds.  In
  2309. Iran only 27.2% of registered voters voted for the winner <a href="https://en.wikipedia.org/wiki/Masoud_Pezeshkian">Masoud Pezeshkian</a>.  The other
  2310. candidate, <a href="https://en.wikipedia.org/wiki/Saeed_Jalili">Saeed Jalili</a>,
  2311. received 22.5%.  And over 50% of registered voters didn't vote at all.  What would have
  2312. happened if they <i>had</i> voted?
  2313.      </p>
  2314.  
  2315.      <p>
  2316. But what if there are more than two candidates?  Take the situation of the first French
  2317. election round, where most constituencies had multiple candidates.  And that was to the
  2318. advantage of the RN.  So in the second round the other two main parties, the <a href="https://en.wikipedia.org/wiki/Nouveau_Front_populaire">Nouveau Front populaire</a> and
  2319. the <a href="https://en.wikipedia.org/wiki/Ensemble_pour_la_République">Ensemble pour
  2320. la République</a> (the party of <a href="https://en.wikipedia.org/wiki/Emmanuel_Macron">Emmanuel Macron</a>), decided to only
  2321. field one candidate for many of the constituencies.  The result: RN got 37.06% of the votes,
  2322. NFP got 25.8%, and Ensemble got only 24.53%.  So the RN won, right?  Wrong.  They ended up
  2323. with only 142 seats, while the NFP got 180 and Ensemble got 159.  That only makes sense (and
  2324. then only just) because of the way the votes were distributed.
  2325.      </p>
  2326.  
  2327.      <p>
  2328. And then there's the UK, where the <a href="https://en.wikipedia.org/wiki/Labour_Party_(UK)">Labour Party</a> defeated the
  2329. <a href="https://en.wikipedia.org/wiki/Conservative_Party_(UK)">Conservative Party</a> by a “landslide”.  Labour got 211 more seats, the Conservatives lost 251 seats for their
  2330. worst-ever result.  But looking at the vote count, Labour got 33.69% of all votes cast, only
  2331. 1.6% more than in 2019.  And that, along with a more significant loss by the Conservatives
  2332. (19.9%) made the difference between 200 and 411 seats out of 650.
  2333.      </p>
  2334.  
  2335.      <p>
  2336. What's wrong with this picture?  In Iran, low voter turnout means that the results are only
  2337. marginally representative of what people want.  In France, and arguably in the UK, the
  2338. number of candidates determine who wins.  And in Australia?  I'm coming to the conclusion
  2339. that the Australian system is better: it requires compulsory voting, which must result in a
  2340. more accurate representation of what the voters want, and if your candidate doesn't win, you
  2341. specify who should get the vote instead.  I wonder how that would have affected the results
  2342. in the three countries.
  2343.      </p>
  2344.  
  2345.      <p>
  2346. But once again I'm reminded of <a href="https://en.wikipedia.org/wiki/Jawaharlal_Nehru">Jawaharlal Nehru's</a> comment “Democracy is good. I say this because other systems are
  2347. worse”.
  2348.      </p>
  2349.      
  2350. End deselected topic Po (The people have spoken—some of them) -->
  2351.  
  2352.            
  2353. <item>
  2354. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jul2024.php#D-20240709-005843</guid>
  2355. <link>http://www.lemis.com/grog/diary-jul2024.php?topics=c#D-20240709-005843</link>
  2356. <category>technology</category>
  2357. <category>opinion</category>
  2358. <title>Understanding mice</title>
  2359.  <description>
  2360.    <![CDATA[
  2361.    <div align="justify">
  2362.      <p>
  2363. <a href="http://www.lemis.com/grog/diary-jul2024.php?topics=c&amp;subtitle=Understanding%20mice&amp;article=D-20240708-014220#D-20240708-014220">Yesterday's</a> confusion with mice puzzled me.  Wasn't there a way to set a button map?
  2364.      </p>
  2365.  
  2366.      <p>
  2367. Yes, and I found it <a href="http://www.lemis.com/grog/diary-jan2024.php?subtitle=Configuring%20mouse%20in%20the%20new%20scheme%20of%20things&amp;article=D-20240105-003925#D-20240105-003925">not so long ago</a>: there's a button map that <i>xinput</i> is too polite to display
  2368. with <tt>xinput list-props</tt>.  Instead I need <tt>xinput get-button-map</tt>
  2369.      </p>
  2370.  
  2371.      <p>
  2372. With that information, I've added this to <a href="http://www.lemis.com/grog/HOWTO/X-configuration.php">my
  2373. HOWTO page</a>:
  2374.      </p>
  2375.  
  2376.      <p>
  2377. Current (2024) versions of <a href="https://www.x.org/">X</a> don't seem to
  2378. use <i>moused</i> any more.  Use <i>/dev/sysmouse</i>:
  2379.      </p>
  2380.  
  2381.      <blockquote class="fullwidth">
  2382. <div style="text-align:left">
  2383.  <tt>
  2384. Section "InputDevice"
  2385. <br />&nbsp;&nbsp; &nbsp;# generated from default
  2386. <br />&nbsp;&nbsp; &nbsp;Identifier &nbsp; &nbsp; "Mouse0"
  2387. <br />&nbsp;&nbsp; &nbsp;Driver &nbsp; &nbsp; &nbsp; &nbsp; "mouse"
  2388. <br />&nbsp;&nbsp; &nbsp;Option &nbsp; &nbsp; &nbsp; &nbsp; "Protocol" "auto"
  2389. <br />&nbsp;&nbsp; &nbsp;Option &nbsp; &nbsp; &nbsp; &nbsp; "Device" "/dev/sysmouse"
  2390. <br />&nbsp;&nbsp; &nbsp;Option &nbsp; &nbsp; &nbsp; &nbsp; "ZAxisMapping" "4 5"
  2391. <br />EndSection
  2392. <br />
  2393.  </tt>
  2394. </div>
  2395. </blockquote>
  2396.  
  2397.      <p>
  2398. It's not clear if <tt>ZAxisMapping</tt> is of any use.
  2399.      </p>
  2400.  
  2401.      <p>
  2402. I used to include this:
  2403.      </p>
  2404.  
  2405.      <blockquote class="fullwidth">
  2406. <div style="text-align:left">
  2407.  <tt>
  2408. &nbsp;&nbsp; &nbsp;Option &nbsp; &nbsp; &nbsp; &nbsp; "Emulate3Buttons" "yes"
  2409. <br />
  2410.  </tt>
  2411. </div>
  2412. </blockquote>
  2413.  
  2414.      <p>
  2415. But there's a better way to do this.  First find the mouse or mice:
  2416.      </p>
  2417.  
  2418.      <blockquote class="fullwidth">
  2419. <div style="text-align:left">
  2420.  <tt>
  2421. <code><font color="blue">=== grog@hydra (/dev/pts/23)</font> <font color="red">~</font> <font color="blue">369</font> &#45;&gt; <b><tt>xinput</tt></b></code>
  2422. <br />⎡ Virtual core pointer &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;id=2 &nbsp; &nbsp;[master pointer &nbsp;(3)]
  2423. <br />⎜ &nbsp; ↳ Virtual core XTEST pointer &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;id=4 &nbsp; &nbsp;[slave &nbsp;pointer &nbsp;(2)]
  2424. <br />⎜ &nbsp; ↳ System mouse &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;id=6 &nbsp; &nbsp;[slave &nbsp;pointer &nbsp;(2)]
  2425. <br />⎜ &nbsp; ↳ <b>Logitech USB Receiver</b> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; id=11 &nbsp; [slave &nbsp;pointer &nbsp;(2)]
  2426. <br />⎜ &nbsp; ↳ <b>Telink 2.4G Mouse</b> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; id=12 &nbsp; [slave &nbsp;pointer &nbsp;(2)]
  2427. <br />⎣ Virtual core keyboard &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; id=3 &nbsp; &nbsp;[master keyboard (2)]
  2428. <br />&nbsp;&nbsp; &nbsp;↳ Virtual core XTEST keyboard &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; id=5 &nbsp; &nbsp;[slave &nbsp;keyboard (3)]
  2429. <br />&nbsp;&nbsp; &nbsp;↳ System keyboard multiplexer &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; id=7 &nbsp; &nbsp;[slave &nbsp;keyboard (3)]
  2430. <br />&nbsp;&nbsp; &nbsp;↳ Power Button &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;id=8 &nbsp; &nbsp;[slave &nbsp;keyboard (3)]
  2431. <br />&nbsp;&nbsp; &nbsp;↳ Logitech USB Receiver &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; id=9 &nbsp; &nbsp;[slave &nbsp;keyboard (3)]
  2432. <br />&nbsp;&nbsp; &nbsp;↳ vendor 0x0430 Sun USB Keyboard &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;id=10 &nbsp; [slave &nbsp;keyboard (3)]
  2433. <br />
  2434.  </tt>
  2435. </div>
  2436. </blockquote>
  2437.  
  2438.      <p>
  2439. Yes, those are two mice.  Next,
  2440.      </p>
  2441.  
  2442.      <blockquote class="fullwidth">
  2443. <div style="text-align:left">
  2444.  <tt>
  2445. <code><font color="blue">=== grog@hydra (/dev/pts/26)</font> <font color="red">~</font> <font color="blue">9</font> &#45;&gt; <b><tt>xinput list&#45;props 11</tt></b></code>
  2446. <br />Device 'Logitech USB Receiver':
  2447. <br />&nbsp;&nbsp; &nbsp; &nbsp; &nbsp;Device Enabled (155): &nbsp; 1
  2448. <br />...
  2449. <br />&nbsp;&nbsp; &nbsp; &nbsp; &nbsp;libinput Middle Emulation Enabled (287): &nbsp; &nbsp; &nbsp; &nbsp;0
  2450. <br />&nbsp;&nbsp; &nbsp; &nbsp; &nbsp;libinput Middle Emulation Enabled Default (288): &nbsp; &nbsp; &nbsp; &nbsp;0
  2451.  </tt>
  2452. </div>
  2453. </blockquote>
  2454.  
  2455.      <p>
  2456. The important thing here is the number 287 in that output.  Next, note the name in the
  2457. initial output and enter:
  2458.      </p>
  2459.  
  2460.      <blockquote class="fullwidth">
  2461. <div style="text-align:left">
  2462.  <tt>
  2463. # Logitech mouse: find the ID
  2464. <br />MOUSEID=$(xinput | grep &#45;m 1 "<b>Logitech USB</b>" | sed 's/^.*id=\([0&#45;9]*\)[ \t].*$/\1/')
  2465. <br />xinput set&#45;prop $MOUSEID 287 1 &nbsp;# Logitech
  2466.  </tt>
  2467. </div>
  2468. </blockquote>
  2469.  
  2470.      <p>
  2471. If the mouse has other buttons that can be remapped, do something like:
  2472.      </p>
  2473.  
  2474.      <blockquote class="fullwidth">
  2475. <div style="text-align:left">
  2476.  <tt>
  2477. # Logitech mouse: find the ID
  2478. <br />MOUSEID=$(xinput | grep &#45;m 1 "<b>Logitech USB</b>" | sed 's/^.*id=\([0&#45;9]*\)[ \t].*$/\1/')
  2479. <br /># And set middle button to 8 and 9
  2480. <br />xinput set&#45;button&#45;map $MOUSEID 1 2 3 4 5 6 7 <b>2 2</b> 10 11 12 13 14 15 16
  2481.  </tt>
  2482. </div>
  2483. </blockquote>
  2484.  
  2485.      <p>
  2486. That's the same assignment to <tt>MOUSEID</tt>.  This sets buttons 8 and 9 to return button
  2487. 2.
  2488.      </p>
  2489.      </div>
  2490.    ]]>
  2491.  </description>
  2492.  <dc:creator>Greg Lehey</dc:creator>
  2493.  <dc:date>2024-07-09T00:58:43+00:00</dc:date>
  2494. </item>
  2495.  
  2496.                  
  2497. <item>
  2498. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jul2024.php#D-20240710-020702</guid>
  2499. <link>http://www.lemis.com/grog/diary-jul2024.php?topics=c#D-20240710-020702</link>
  2500. <category>general</category>
  2501. <category>technology</category>
  2502. <category>multimedia</category>
  2503. <category>opinion</category>
  2504. <title>Quiet day</title>
  2505.  <description>
  2506.    <![CDATA[
  2507.    <div align="justify">
  2508.      <p>
  2509. Today was one of those days where I didn't do anything worth mentioning, quite a difference
  2510. from the last few weeks.  When am I going to continue with upgrading <i>tiwi</i>
  2511. (or <i>teevee</i>)?  Somehow the issue with <a href="https://en.wikipedia.org/wiki/VirtualBox">VirtualBox</a> has thrown a spanner in the
  2512. works.  An obvious attempt to localize the problem would be to try the same scenario running
  2513. <a href="https://en.wikipedia.org/wiki/Linux">Linux</a>.  And for that I need a
  2514. machine for the installation—the same one that I need for <i>teevee</i>.
  2515.      </p>
  2516.  
  2517.      <p>
  2518. What do I do?  So far, nothing.  If I can speed up the migration from <i>tiwi</i>
  2519. to <i>teevee</i>, I will have a machine for the VirtualBox testing.
  2520.      </p>
  2521.      </div>
  2522.    ]]>
  2523.  </description>
  2524.  <dc:creator>Greg Lehey</dc:creator>
  2525.  <dc:date>2024-07-10T02:07:02+00:00</dc:date>
  2526. </item>
  2527.  
  2528.                  
  2529. <item>
  2530. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jul2024.php#D-20240711-024029</guid>
  2531. <link>http://www.lemis.com/grog/diary-jul2024.php?topics=c#D-20240711-024029</link>
  2532. <category>technology</category>
  2533. <category>opinion</category>
  2534. <title>Scam from Google Play</title>
  2535.  <description>
  2536.    <![CDATA[
  2537.    <div align="justify">
  2538.      <p>
  2539. While looking for that most elusive of things, a good <a href="https://en.wikipedia.org/wiki/Android_(operating_system)">Android</a> app, got this
  2540. unsolicited popup:
  2541.      </p>
  2542.  
  2543.        <a id="Photo-7" name="Photo-7"
  2544.          href="diary-jul2024.php?dirdate=20240710&amp;imagesizes=11111112&amp;topics=c#Photo-7">
  2545.          <img alt="This should be Scam-from-Google-Play-detail.jpeg.  Is it missing?" border="0" id="Photo_7"
  2546.               title="Photo Scam-from-Google-Play-detail.jpeg.  Click to redisplay larger version of image."
  2547.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20240710/small/Scam-from-Google-Play-detail.jpeg"
  2548.               width="263" height="256"
  2549.           /></a>
  2550.  
  2551.      <p>
  2552. <tt>221.236.211.162</tt>?  That's not an IP that I use.  A bit of checking showed:
  2553.      </p>
  2554.  
  2555.      <blockquote class="fullwidth">
  2556. <div style="text-align:left">
  2557.  <tt>
  2558. <code><font color="blue">=== grog@eureka (/dev/pts/6)</font> <font color="red">~</font> <font color="blue">204</font> &#45;&gt; <b><tt>host 221.236.211.162</tt></b></code>
  2559. <br />162.211.236.221.in&#45;addr.arpa domain name pointer 162.211.236.221.broad.cd.sc.dynamic.163data.com.cn.
  2560. <br />
  2561.  </tt>
  2562. </div>
  2563. </blockquote>
  2564.  
  2565.      <p>
  2566. A <i>traceroute</i> failed after 13 hops, so it's clearly not nearby.
  2567.      </p>
  2568.  
  2569.      <p>
  2570. What does that mean?  Possibly the advertisement can't determine the IP addresses in use on
  2571. my phone, but why use a fake address?  Is this some kind of scam?  And in passing, it
  2572. suggests that the IP addresses can be hidden by encrypting the content.  Whoever wrote that
  2573. doesn't understand the <a href="https://en.wikipedia.org/wiki/Internet_Protocol">Internet Protocol</a>, or thinks that the user is stupid enough not to know it:
  2574. encryption doesn't change the IP addresses.
  2575.      </p>
  2576.      </div>
  2577.    ]]>
  2578.  </description>
  2579.  <dc:creator>Greg Lehey</dc:creator>
  2580.  <dc:date>2024-07-11T02:40:29+00:00</dc:date>
  2581. </item>
  2582.  
  2583.            
  2584. <item>
  2585. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jul2024.php#D-20240711-024429</guid>
  2586. <link>http://www.lemis.com/grog/diary-jul2024.php?topics=c#D-20240711-024429</link>
  2587. <category>multimedia</category>
  2588. <category>technology</category>
  2589. <category>opinion</category>
  2590. <title>More work on teevee</title>
  2591.  <description>
  2592.    <![CDATA[
  2593.    <div align="justify">
  2594.      <p>
  2595. Finally got round to doing some more “work” on <i>teevee</i>.  Somehow this cable mess
  2596. really gets me down.  Spent a lot of time trying to get the correct cables in the right
  2597. place, in principle only monitor and audio.  And apart from minor frobs to get the mouse
  2598. right and to mount the correct file systems, all worked pretty much out of the box.  But the
  2599. next step is more cabling in the lounge room, which is another horror.
  2600.      </p>
  2601.      </div>
  2602.    ]]>
  2603.  </description>
  2604.  <dc:creator>Greg Lehey</dc:creator>
  2605.  <dc:date>2024-07-11T02:44:29+00:00</dc:date>
  2606. </item>
  2607.  
  2608.            
  2609. <!-- topic Hho not selected
  2610.            <p>
  2611. Unexpected mail from Benoît Nogues today:
  2612.      </p>
  2613.  
  2614.      <blockquote class="fullwidth">
  2615. <div style="text-align:left">
  2616.  <tt>
  2617. Following the death of Mr Louis Binos de Pombarat , the notary in charge of the estate wants to contact Yvonne , please contact the notary office :
  2618. <br />
  2619.  </tt>
  2620. </div>
  2621. </blockquote>
  2622.  
  2623.            <p>
  2624. What's that?  It was too late for us today, but it's intriguing.  It's unlikely that Louis
  2625. left anything to Yvonne: they clarified their relationship with the divorce in 1980.  What
  2626. else might be the reason?
  2627.      </p>
  2628.      
  2629. End deselected topic Hho (Executing wills) -->
  2630.  
  2631.                  
  2632. <!-- topic aho not selected
  2633.      <p>
  2634. In the last millennium an interesting combination of advertising and information arose:
  2635. fridge magnets, small magnetic cards that stuck to the side of a refrigerator and contained
  2636. address information for companies.  Our most exposed fridge contained a whole lot of them.
  2637.      </p>
  2638.  
  2639.      <p>
  2640. But clearly the cats think that that's a bad idea:
  2641.      </p>
  2642.  
  2643.      
  2644.      <p>
  2645. And do we really use them?  I think not.
  2646.      </p>
  2647.      
  2648. End deselected topic aho (What use fridge magnets?) -->
  2649.  
  2650.            
  2651. <!-- topic kGo not selected
  2652.      <p>
  2653. From time to time, like <a href="http://www.lemis.com/grog/diary-jun2024.php#D-20240626-011901">here</a>, I comment on the impression that almost every US American recipe includes
  2654. sugar, and I've taken to ignoring it.  But today I came across <a href="https://brilliantmaps.com/daily-sugar-intake/">this map</a> of daily sugar intake by
  2655. state in the USA:
  2656.      </p>
  2657.  
  2658.      <a href="https://brilliantmaps.com/wp-content/uploads/daily-sugar-intake-1536x1075.png">
  2659.      <img alt=""
  2660.          title=".  Click to see in original size."
  2661.          src="https://brilliantmaps.com/wp-content/uploads/daily-sugar-intake-1536x1075.png"
  2662.          width="500"
  2663.          /></a>      <img alt="Image"
  2664.          title="Image"
  2665.          src="http://www.lemis.com/grog/Day/20240711/daily-sugar-intake-1536x1075-detail.png"
  2666.        />
  2667.  
  2668.      <p>
  2669. The measurements are in <a href="http://www.lemis.com/grog/recipes/measures.php#spoon">teaspoons</a> per day.
  2670. Interestingly, though, it seems that the weight of a teaspoon of sugar has been standardized
  2671. in the USA: 4.2 g (or 4 g between friends).  That's particularly interesting because of the
  2672. unit: 4.2 g, not 0.148 ounces.
  2673.      </p>
  2674.  
  2675.      <p>
  2676. So that means that the average US American eats between 56 and 85 g of added sugar every
  2677. day!  That's quite amazing.  What does “added” mean?  Beyond what is naturally present in
  2678. foodstuffs, it seems.  Clearly there are borderline situations.  Does it include the sugar
  2679. in orange juice?  In honey?  I would guess no and yes, respectively.
  2680.      </p>
  2681.  
  2682.      <p>
  2683. The other thing is in the fine print: the <a href="https://en.wikipedia.org/wiki/American_Heart_Association">American Heart Association</a> recommends between 6 to 9 tsp/day (25 to 38 g).  While it's considerably less than actual
  2684. consumption, it still seems to be amazingly high.  I've compared my consumption: 0, assuming
  2685. the single glass of orange juice for breakfast doesn't count.  That's not a reaction to my
  2686. <a href="https://en.wikipedia.org/wiki/Diabetes_mellitus">diabetes</a>: I just don't
  2687. want any more.
  2688.      </p>
  2689.      
  2690. End deselected topic kGo (How much sugar?) -->
  2691.  
  2692.                  
  2693. <!-- topic h not selected
  2694.      <p>
  2695. Estíbaliz Harrison (a name I hadn't heard before) along today to do some cleaning.  She's
  2696. the first cleaner we have had who does it on a professional basis, and she did a good job.
  2697. The most interesting thing is her name, which I had never heard before.  But she calls
  2698. herself Steph, a lot easier to pronounce and remember.
  2699.      </p>
  2700.      
  2701. End deselected topic h (¡Hola Estíbaliz!) -->
  2702.  
  2703.            
  2704. <item>
  2705. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jul2024.php#D-20240713-034810</guid>
  2706. <link>http://www.lemis.com/grog/diary-jul2024.php?topics=c#D-20240713-034810</link>
  2707. <category>technology</category>
  2708. <category>opinion</category>
  2709. <title>VirtualBox on Ubuntu</title>
  2710.  <description>
  2711.    <![CDATA[
  2712.    <div align="justify">
  2713.      <p>
  2714. My continuing pain with <a href="https://en.wikipedia.org/wiki/VirtualBox">VirtualBox</a> had established that the problem was not (only?) related to the hardware
  2715. on which it ran: it also happened on <i>quartet</i>, a test <a href="https://en.wikipedia.org/wiki/ThinkCentre">ThinkCentre</a>.  So if it's a single point
  2716. of failure, it's probably either <a href="https://www.freebsd.org/">FreeBSD</a> or
  2717. the specific VirtualBox port.
  2718.      </p>
  2719.  
  2720.      <p>
  2721. OK, before I move <i>quartet</i> (as <i>teevee</i>) to the lounge room, how about installing
  2722. <a href="https://en.wikipedia.org/wiki/Ubuntu">Ubuntu</a> on it and trying like
  2723. that?
  2724.      </p>
  2725.  
  2726.      <p>
  2727. I've been through the installation <a href="http://www.lemis.com/grog/diary-jun2024.php?subtitle=Ubuntu%20again&amp;article=D-20240623-021811#D-20240623-021811">a couple of weeks ago</a>, and I still have the install media.  How hard can it be?
  2728. Excruciating!  It started with a broken copy to the USB card, but after I had done the
  2729. install, I still needed to integrate it into the home LAN.  For <a href="https://en.wikipedia.org/wiki/Network_File_System">NFS</a> I need a user <tt>grog</tt>
  2730. and a UID that matches the other systems.  How do you do that?  The “Settings” menus don't
  2731. seem to cater for it.  And when I entered my password, it decided that it didn't like it.
  2732. Not “please choose another password”, just blanked-out buttons and input fields (“I implied
  2733. that I didn't like the password.  Don't try to enter it again!”).
  2734.      </p>
  2735.  
  2736.      <p>
  2737. OK, at least I can change my IP address.  Yes, it allows me.  But I can't specify a domain
  2738. name.  OK, fix it in <i>/etc/resolv.conf</i>.  But no, you can't do that!
  2739.      </p>
  2740.  
  2741.      <blockquote class="fullwidth">
  2742. <div style="text-align:left">
  2743.  <tt>
  2744. # This is /run/systemd/resolve/stub&#45;resolv.conf managed by man:systemd&#45;resolved(8).
  2745. <br /># Do not edit.
  2746. <br />#
  2747. <br /># ...
  2748. <br />nameserver 127.0.0.53
  2749. <br />options edns0 trust&#45;ad
  2750. <br />search .
  2751. <br />
  2752.  </tt>
  2753. </div>
  2754. </blockquote>
  2755.  
  2756.      <blockquote class="fullwidth">
  2757. <div style="text-align:left">
  2758.  <tt>
  2759. root@echuca:/etc# <b>ls &#45;l resolv.conf</b>
  2760. <br />lrwxrwxrwx 1 root root 39 Apr 24 20:47 <span style="color: cyan"></span>resolv.conf &#45;> ../run/systemd/resolve/stub&#45;resolv.conf
  2761. <br />
  2762.  </tt>
  2763. </div>
  2764. </blockquote>
  2765.  
  2766.      <p>
  2767. But that's all wrong!  And the “Settings” don't give me the option of changing it, though
  2768. they know that the name server address is <tt>192.109.197.137</tt>.  There's this horrible
  2769. <a href="https://en.wikipedia.org/wiki/Systemd"><i>systemd</i></a> thing.  What can
  2770. I do?  Rename it and create a new <i>resolv.conf</i> like God intended.  Who knows how long
  2771. it will stay there.
  2772.      </p>
  2773.  
  2774.      <p>
  2775. Ultimately installed a number of <del></del> apts, many of which I would have expected to be
  2776. present in the base
  2777. system: <i>rwho</i>, <i>openssh-server</i>, <i>xterm</i>, <i>ifconfig</i>, <i>emacs</i>.  In
  2778. passing, one of the dependencies was <a href="https://en.wikipedia.org/wiki/Postfix_(software)">Postfix</a>, which was also
  2779. configured for me.  I should take a look at what it has done.
  2780.      </p>
  2781.  
  2782.      <p>
  2783. And with that I was able to fix up <i>/etc/passwd</i> and friends.
  2784.      </p>
  2785.  
  2786.      <p>
  2787. Next, mount <a href="https://en.wikipedia.org/wiki/Network_File_System">NFS</a> file
  2788. systems.  No, no, you can't do that!  First you need a <i>mount.&lt;something&gt;</i> (the
  2789. same message applies to other file systems).  OK, Ubuntu, where do I get it?  389 lines of
  2790. output that all looked like this:
  2791.      </p>
  2792.  
  2793.        <a id="Photo-8" name="Photo-8"
  2794.          href="diary-jul2024.php?dirdate=20240712&amp;imagesizes=111111112&amp;topics=c#Photo-8">
  2795.          <img alt="This should be Ubuntu-filth-1.png.  Is it missing?" border="0" id="Photo_8"
  2796.               title="Photo Ubuntu-filth-1.png.  Click to redisplay larger version of image."
  2797.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20240712/small/Ubuntu-filth-1.png"
  2798.               width="590" height="115"
  2799.           /></a>
  2800.  
  2801.      <p>
  2802. This <b><i>HORRIBLE</i></b> half-coloured text!  In this case I found that putting the
  2803. output through <i>less</i> sanitized it, showing that the vast majority of the entries have
  2804. nothing obvious to do with NFS.  But <b><i>WHY</i></b> is it so difficult to get Linux to
  2805. shut up?  Off on a tangent to find ways, but there seem to be none.  <a href="https://gemini.google.com/app/055914f5479c1ef5">This answer</a> suggests two ways,
  2806. both of which look like they should work, but don't:
  2807.      </p>
  2808.  
  2809.      <ol>
  2810.        <li class="fullwidth">
  2811.          <div class="listitemwidth">
  2812.            Set <tt>TERM=xterm-mono</tt>.
  2813.          </div>
  2814.        </li>
  2815.  
  2816.        <li class="fullwidth">
  2817.          <div class="listitemwidth">
  2818.            Create a file <i>/etc/terminal-colors.d/disable</i>.
  2819.          </div>
  2820.        </li>
  2821.      </ol>
  2822.  
  2823.      <p>
  2824. Even the second solution has a caveat: “The presence of this file disables color output for
  2825. compatible utilities”.  Clearly everything I use is incompatible.
  2826.      </p>
  2827.  
  2828.      <p>
  2829. People, this is <b><i>STUPID</i></b>.  If you really, <i>really</i> want to splash colour
  2830. over a screen, you should at least set the background as well.
  2831.      </p>
  2832.  
  2833.      <p>
  2834. Back to the case in hand: I found the package for <i>mount.nfs</i>, but forgot to write it
  2835. down, possibly <i>nfs-common</i>.  It wasn't immediately obvious.  Next time will be the
  2836. same pain all over again.  But after that, with a marginal environment set up, I was able to
  2837. install <a href="https://en.wikipedia.org/wiki/VirtualBox">VirtualBox</a>.  It
  2838. looks—again—completely different.  It's version 7.0.16, while on FreeBSD it's 6.1.18.
  2839. That's not as out-of-date as it might seem: both seem to be maintained in parallel, and both
  2840. date from this year, though VirtualBox 7.0.0 was released on 10 October 2022.  But it would
  2841. be interesting to see whether my network problems would occur under 7.0.  Can I face the
  2842. prospect of updating the port?
  2843.      </p>
  2844.  
  2845.      <p>
  2846. Lots of messing round, copying hundreds of gigabytes of files, but kept running into
  2847. problems starting the VM.  I really need to read up on this and find the correct way to
  2848. start it.
  2849.      </p>
  2850.      </div>
  2851.    ]]>
  2852.  </description>
  2853.  <dc:creator>Greg Lehey</dc:creator>
  2854.  <dc:date>2024-07-13T03:48:10+00:00</dc:date>
  2855. </item>
  2856.  
  2857.                  
  2858. <!-- topic g not selected
  2859.      <p>
  2860.        Jesse Walsh along today to do some more work in the garden.        </p>
  2861.      
  2862. End deselected topic g (More garden work) -->
  2863.  
  2864.            
  2865. <item>
  2866. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jul2024.php#D-20240714-003431</guid>
  2867. <link>http://www.lemis.com/grog/diary-jul2024.php?topics=c#D-20240714-003431</link>
  2868. <category>technology</category>
  2869. <category>opinion</category>
  2870. <title>More VirtualBox fun</title>
  2871.  <description>
  2872.    <![CDATA[
  2873.    <div align="justify">
  2874.      <p>
  2875. Spent a large part of the day setting up <a href="https://en.wikipedia.org/wiki/VirtualBox">VirtualBox</a> on <a href="https://en.wikipedia.org/wiki/Ubuntu">Ubuntu</a>.  I have resolved at least one thing:
  2876. to move a VM from one instance of VirtualBox to another, I need to press the “Add” button,
  2877. not the “New” button.  And that uses the configuration file (like <i>despise.vbox</i>), and
  2878. it works up to a point.  Clearly a saved image isn't going to work well, especially as in
  2879. this case I had to reduce the memory from 24 to 16 GB and the number of CPUs from 8 to 4.
  2880.      </p>
  2881.  
  2882.      <p>
  2883. But it's so <i>slow</i>!  Well, at least the disks were.  There was a difference: this setup
  2884. uses normal magnetic disks, while my other instances have used <a href="https://en.wikipedia.org/wiki/SSD">SSDs</a>.  But I used magnetic disks
  2885. on <i>eureka</i>, and they were nothing like as slow as on <i>echuca</i>, the Ubuntu
  2886. “machine”.  After a cold boot it took two hours for disk activity to die down.
  2887.      </p>
  2888.  
  2889.      <p>
  2890. Why is it so slow?  Is this Ubuntu, or is it VirtualBox 7?  While I was pondering that, took
  2891. my weekly <a href="http://www.lemis.com/grog/stones-road/exterior.php">house photos</a>, which I had
  2892. wanted to process on this instance of <i>despise</i>.  That was clearly not the optimum way,
  2893. so I did them on <i>distress</i>, a real machine, instead.
  2894.      </p>
  2895.  
  2896.      <p>
  2897. Later, though, things had calmed down, so I tried again.  Surprisingly, there was little
  2898. difference.  <i>distress</i> and <i>echuca</i> (the Ubuntu host) are both <a href="https://en.wikipedia.org/wiki/ThinkCentre">ThinkCentre</a> M93ps, so the results
  2899. should be comparable.  Based on events, I had expected the VirtualBox instance to be an
  2900. order of magnitude slower, but in fact there wasn't much difference: the hardware version
  2901. converted 129 images in 17:37 minutes, while the VM took 18:55, about 93% of the throughput
  2902. of the naked machine.  That's quite acceptable.  The real question is just why there's so
  2903. much disk activity.
  2904.      </p>
  2905.      </div>
  2906.    ]]>
  2907.  </description>
  2908.  <dc:creator>Greg Lehey</dc:creator>
  2909.  <dc:date>2024-07-14T00:34:31+00:00</dc:date>
  2910. </item>
  2911.  
  2912.            
  2913. <item>
  2914. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jul2024.php#D-20240714-023023</guid>
  2915. <link>http://www.lemis.com/grog/diary-jul2024.php?topics=c#D-20240714-023023</link>
  2916. <category>technology</category>
  2917. <category>general</category>
  2918. <category>food</category>
  2919. <category>and</category>
  2920. <category>drink</category>
  2921. <category>opinion</category>
  2922. <title>The pain of cables</title>
  2923.  <description>
  2924.    <![CDATA[
  2925.    <div align="justify">
  2926.      <p>
  2927. <a href="http://www.lemis.com/grog/recipes/ossobuco.php"><i>Osso buco</i></a> for dinner tonight.  For that,
  2928. we need <a href="http://www.lemis.com/grog/recipes/risotto-alla-milanese.php"><i>risotto alla milanese</i></a>.  And how about that, according to our freezer database, we have some in basket 9.
  2929.      </p>
  2930.  
  2931.      <p>
  2932. Do I believe that?  Not overly.  But it's a good chance to bring the database up to date
  2933. with reality.  Print out the contents of 9 and compare.
  2934.      </p>
  2935.  
  2936.      <p>
  2937. Oh.
  2938.      </p>
  2939.  
  2940.      <blockquote class="fullwidth">
  2941. <div style="text-align:left">
  2942.  <tt>
  2943. <code><font color="blue">=== grog@eureka (/dev/pts/7)</font> <font color="red">~</font> <font color="blue">109</font> &#45;&gt; <b><tt>echo 'select * from freezer where basket="9" order by description ;' | mysql household | a2ps</tt></b></code>
  2944. <br />ERROR 1064 (42000) at line 1: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '0~select * from freezer where basket="9" order by description' at line 1
  2945. <br />
  2946.  </tt>
  2947. </div>
  2948. </blockquote>
  2949.  
  2950.      <p>
  2951. Huh?  That's exactly the query I submitted directly.  Why doesn't it like it?  It took me a
  2952. while to realize that the mouse was adding invisible information.  Pasted directly
  2953. into <i>mysql</i>, it looked like:
  2954.      </p>
  2955.  
  2956.      <blockquote class="fullwidth">
  2957. <div style="text-align:left">
  2958.  <tt>
  2959. <code><font color="blue">=== grog@eureka (/dev/pts/7)</font> <font color="red">~</font> <font color="blue">110</font> &#45;&gt; <b><tt>mysql household</tt></b></code>
  2960. <br />mysql> <b>0~select * from freezer where basket="9" order by description ;1~</b>
  2961. <br />
  2962.  </tt>
  2963. </div>
  2964. </blockquote>
  2965.  
  2966.      <p>
  2967. Why?  A sick mouse?  Yet Another thing to investigate.  Prepared the query in <a href="https://www.gnu.org/software/emacs/"><i>Emacs</i></a> and it worked.  Well, no error
  2968. messages.  But no output on the printer either.
  2969.      </p>
  2970.  
  2971.      <p>
  2972. What does <i>lpr</i> say?  “Can't communicate with lp”.  Took a look: no network cable!  I
  2973. must have “borrowed” it for something else.  Off looking for a relatively long cable, and
  2974. finally found a particularly nasty-looking one that must once have done duty in <a href="http://www.lemis.com/wantadilla/">Wantadilla</a>, where it had been stuck to the floor with masking tape.
  2975. One end had the fixing tab broken off, but that shouldn't be a problem.  But the office
  2976. switch (16 ports) didn't have a spare port!  Surely I don't have that many devices
  2977. connected.
  2978.      </p>
  2979.  
  2980.      <p>
  2981. No, at least one cable had nothing on the other end.  OK, connected it up.  On the second
  2982. attempt I was able to talk to it.  But still no output!
  2983.      </p>
  2984.  
  2985.      <p>
  2986. Is that something with <i>a2ps</i>?  I had some distant memory of having it set up to
  2987. automatically send to <i>lpr</i>.  But I can do that directly: pipe to <i>lpr</i> instead
  2988. of <i>a2ps</i>.  And that worked, sort of, merrily going off the right margin: no <b>^M</b>
  2989. characters.
  2990.      </p>
  2991.  
  2992.      <p>
  2993. Finally chased down where I use <i>a2ps</i>.  It wants to be invoked a <i>a2ps -M A4</i>.
  2994. And then—finally—I got my single page of output.
  2995.      </p>
  2996.  
  2997.      <p>
  2998. And the risotto?  No, none there, but a couple of other things that I had forgotten to
  2999. enter.  Databases are fine for this sort of thing, <i>if</i> you keep them up to date.  But
  3000. that's such a pain.
  3001.      </p>
  3002.      </div>
  3003.    ]]>
  3004.  </description>
  3005.  <dc:creator>Greg Lehey</dc:creator>
  3006.  <dc:date>2024-07-14T02:30:23+00:00</dc:date>
  3007. </item>
  3008.  
  3009.            
  3010. <!-- topic ko not selected
  3011.      <p>
  3012. So I had to make a new <a href="http://www.lemis.com/grog/recipes/risotto-alla-milanese.php">risotto alla
  3013. milanese</a>.  I never cease to marvel at the amount of broth it needs: 4 times the weight
  3014. of the rice, where I normally use about 1.8 times as much water to cook normal rice.
  3015.      </p>
  3016.  
  3017.      <p>
  3018. And it wants <i>beef broth</i>, not water.  Do we have that?  Looked in the pantry and found
  3019. a particularly dusty container with something claiming to be beef broth, suitable for
  3020. vegetarians.  That sounds wrong, probably the reason that the container is almost full,
  3021. although it past its “best by” date in April 2002.  Found another one that was only 9 years
  3022. out of date, mixed it up and... it was <i>far</i> too dark.  So in the end I used chicken
  3023. broth powder.
  3024.      </p>
  3025.  
  3026.      <p>
  3027. First insight: yes, I knew that the risotto takes a long time.  I had given it 30 minutes,
  3028. but it was not really enough.  45 minutes would be better.  Second insight: it really needs
  3029. to be done slowly.  After 30 minutes and ridiculous quantities of liquid, it <i>still</i>
  3030. wasn't cooked through.  I really hadn't expected that.
  3031.      </p>
  3032.      
  3033. End deselected topic ko (Thoughts on risotto alla milanese) -->
  3034.  
  3035.                  
  3036. <!-- topic ko not selected
  3037.      <p>
  3038. Started a new pack of <a href="http://www.lemis.com/grog/recipes/noodle-cooking-times.php#Chef-Lo">“Chef Lo”
  3039. noodles</a> today to go with <a href="http://www.lemis.com/grog/recipes/mi-udang-tean.php"><i>mi udang</i></a>.  I had assumed without checking that they would need 2 minutes, like nearly all noodles
  3040. of this nature.  But no, after 2 minutes the basket had barely opened.  In the end I gave
  3041. them 3, though they were still relatively firm.  After being in the soup for a while they
  3042. softened, so maybe 3 to 4 minutes is correct.
  3043.      </p>
  3044.  
  3045.      <p>
  3046. But then I checked the <a href="http://www.lemis.com/grog/recipes/noodle-cooking-times.php#Chef-Lo">cooking
  3047. times</a> page.  2 minutes!  No, not this time round.  On the other hand, they didn't
  3048. stick together like they used to.  Have they changed the composition?
  3049.      </p>
  3050.      
  3051. End deselected topic ko (More noodle cooking times) -->
  3052.  
  3053.            
  3054. <item>
  3055. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jul2024.php#D-20240715-000256</guid>
  3056. <link>http://www.lemis.com/grog/diary-jul2024.php?topics=c#D-20240715-000256</link>
  3057. <category>technology</category>
  3058. <category>opinion</category>
  3059. <title>More VirtualBox pain</title>
  3060.  <description>
  3061.    <![CDATA[
  3062.    <div align="justify">
  3063.      <p>
  3064. More messing around with <a href="https://en.wikipedia.org/wiki/VirtualBox">VirtualBox</a> today.  Why can't I save the state of a virtual machine?  More
  3065. experimentation showed that I couldn't do <i>anything</i> to stop it.  No suspend.  No ACPI
  3066. shutdown request (was just ignored).  No power off.  All I could do was to shut down the VM
  3067. from within (with the <i>SHUTDOWN</i> command).
  3068.      </p>
  3069.  
  3070.      <p>
  3071. Clearly something's wrong there.  Searching the web, found a reference to the user belonging
  3072. to the <tt>vboxusers</tt> group.  I knew that, of course, but I had expected a clean install
  3073. to set it, and it didn't.  But it didn't help.  Tried starting as <tt>root</tt>, and that
  3074. didn't help either.
  3075.      </p>
  3076.  
  3077.      <p>
  3078. Clearly the package for <a href="https://en.wikipedia.org/wiki/Ubuntu">Ubuntu</a> isn't all that it's cut out to be.  OK, I never really intended to use it.  Try a different
  3079. tack: port version 7(.0.18) to <a href="https://www.freebsd.org/">FreeBSD</a>.  Off
  3080. to do that, tripping over a strangeness in the <i>Makefile</i>:
  3081.      </p>
  3082.  
  3083.      <blockquote class="fullwidth">
  3084. <div style="text-align:left">
  3085.  <tt>
  3086. MASTER_SITES= https://download.virtualbox.org/virtualbox/${PORTVERSION}/:src \
  3087. <br /> LOCAL/bofh/emulators/virtualbox&#45;ose:docs
  3088. <br />
  3089.  </tt>
  3090. </div>
  3091. </blockquote>
  3092.  
  3093.      <p>
  3094. What's this <tt>LOCAL</tt>?  I couldn't find the docs on the <a href="https://download.virtualbox.org/virtualbox/">web site</a>, and what I see suggests
  3095. that they have been created locally.  OK, I can fake that: just link the docs for version
  3096. 6.1.50.
  3097.      </p>
  3098.  
  3099.      <p>
  3100. But things still weren't done.  The patch files failed.  That's not surprising, but I was
  3101. unprepared for the number of patches: 95 of them!  Why are they all needed?  But that kills
  3102. it for now.  I should check with others what efforts have been made before going to what
  3103. could be much more trouble.
  3104.      </p>
  3105.      </div>
  3106.    ]]>
  3107.  </description>
  3108.  <dc:creator>Greg Lehey</dc:creator>
  3109.  <dc:date>2024-07-15T00:02:56+00:00</dc:date>
  3110. </item>
  3111.  
  3112.            
  3113. <item>
  3114. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jul2024.php#D-20240715-001537</guid>
  3115. <link>http://www.lemis.com/grog/diary-jul2024.php?topics=c#D-20240715-001537</link>
  3116. <category>technology</category>
  3117. <category>health</category>
  3118. <category>opinion</category>
  3119. <title>A new monitor</title>
  3120.  <description>
  3121.    <![CDATA[
  3122.    <div align="justify">
  3123.      <p>
  3124. It's been <a href="http://www.lemis.com/grog/diary-oct2023.php?subtitle=Looking%20at%20hydra&amp;article=D-20231018-231622#D-20231018-231622">nearly 9 months</a> since I got <i>hydra.lemis.com</i>, my new machine.  And I still
  3125. haven't completed the migration.
  3126.      </p>
  3127.  
  3128.      <p>
  3129. One of the issues was the <a href="https://www.x.org/">X</a> configuration, of
  3130. course, and I had run into trouble with my old Matrix monitor, which is probably on its last
  3131. legs.  I had kept it because of the lower resolution, only 2560×1440, while the new LG
  3132. <a href="https://www.lg.com/us/monitors/lg-27up850-w-uhd-monitor">27UP850</a> monitor is 3840×2160.  But since my <a href="http://www.lemis.com/grog/diary-mar2024.php?topics=Gc&amp;subtitle=Eye%20rebuild&amp;article=D-20240322-003739#D-20240322-003739">cataract operation</a>, it seems that 3840×2160 is perfectly readable.
  3133.      </p>
  3134.  
  3135.      <p>
  3136. So: another 27UP850.  I know my way round the thing, it works well, and now it's over 25%
  3137. cheaper, since it's last year's model.
  3138.      </p>
  3139.  
  3140.      <p>
  3141. Will I ever complete this changeover?
  3142.      </p>
  3143.      </div>
  3144.    ]]>
  3145.  </description>
  3146.  <dc:creator>Greg Lehey</dc:creator>
  3147.  <dc:date>2024-07-15T00:15:37+00:00</dc:date>
  3148. </item>
  3149.  
  3150.                  
  3151. <item>
  3152. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jul2024.php#D-20240715-234840</guid>
  3153. <link>http://www.lemis.com/grog/diary-jul2024.php?topics=c#D-20240715-234840</link>
  3154. <category>technology</category>
  3155. <category>general</category>
  3156. <category>opinion</category>
  3157. <title>VirtualBox: enough!</title>
  3158.  <description>
  3159.    <![CDATA[
  3160.    <div align="justify">
  3161.      <p>
  3162. So where do I go from here with <a href="https://en.wikipedia.org/wiki/VirtualBox">VirtualBox</a>?  Discuss the matter on the <a href="https://www.freebsd.org/">FreeBSD</a> mailing list.  But I'm not a member, and something seems to have gone wrong
  3163. with the signup.
  3164.      </p>
  3165.  
  3166.      <p>
  3167. Enough!  This is really very frustrating.  I'll leave it for a while; after all, I <i>do</i>
  3168. have Microsoft boxen that will do the job.  Instead I'll turn my attention back to the
  3169. new <i>teevee</i>.  And for that I need a better display card than the <a href="https://en.wikipedia.org/wiki/GeForce_700_series">GeForce 710</a> that I have been
  3170. using.  Apart from potential performance issues, the fan is noisy, and blowing it out with
  3171. compressed air doesn't help.  So I've ordered a <a href="https://en.wikipedia.org/wiki/GeForce_10_series">GeForce 1030</a> to replace it.
  3172.      </p>
  3173.      </div>
  3174.    ]]>
  3175.  </description>
  3176.  <dc:creator>Greg Lehey</dc:creator>
  3177.  <dc:date>2024-07-15T23:48:40+00:00</dc:date>
  3178. </item>
  3179.  
  3180.            
  3181. <item>
  3182. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jul2024.php#D-20240715-235624</guid>
  3183. <link>http://www.lemis.com/grog/diary-jul2024.php?topics=c#D-20240715-235624</link>
  3184. <category>technology</category>
  3185. <category>opinion</category>
  3186. <title>Aussie does it again!</title>
  3187.  <description>
  3188.    <![CDATA[
  3189.    <div align="justify">
  3190.      <p>
  3191. Mail from <a href="https://aussiebroadband.com.au/">Aussie Broadband</a> today with
  3192. their inimitable asterisks:
  3193.      </p>
  3194.  
  3195.      <blockquote class="fullwidth">
  3196. <div style="text-align:left">
  3197.  <tt>
  3198. Subject: It's time to review your emergency contact details
  3199. <br />
  3200. <br />We’re just checking in to make sure all of your **emergency** details are correct.
  3201. <br />...
  3202. <br />Address: **29 STONES RD DEREEL VIC 3352**
  3203. <br />Contact number: **0353184210**
  3204. <br />
  3205.  </tt>
  3206. </div>
  3207. </blockquote>
  3208.  
  3209.      <p>
  3210. Well, no.  They include the numbers of the four <a href="https://en.wikipedia.org/wiki/VoIP">VoIP</a> lines that they have half provisioned,
  3211. but not the mobile phone that they also have on file.  And two of those VoIP lines are not
  3212. connected.  Time to change things.
  3213.      </p>
  3214.  
  3215.      <p>
  3216. Log in.  “Invalid user or password”.  On three different browsers with saved passwords.
  3217. Clearly they've changed things at their end.  Finally got it changed, after
  3218. this <i>horrible</i> <a href="https://en.wikipedia.org/wiki/2FA">2FA</a>, requiring
  3219. the “security” of a mobile phone.  No obvious way to supply the contact information.
  3220.      </p>
  3221.  
  3222.      <p>
  3223. OK, try the <a href="https://play.google.com/store/search?q=myaussie%2bapp&amp;c=apps">MyAussie</a> app on my phone.  Wrong password!  OK, change that too.  <i>Another</i> 2FA,
  3224. this time sent to the same phone!  What kind of security is that?
  3225.      </p>
  3226.  
  3227.      <p>
  3228. And then I found that the fingerprint access that I had admired <a href="http://www.lemis.com/grog/diary-may2024.php?subtitle=NBN%20outage!&amp;article=D-20240501-230326#D-20240501-230326">a couple of months ago</a> was no longer available.  OK, I have the documentation online.
  3229. How do I set it up?
  3230.      </p>
  3231.  
  3232.      <p>
  3233. Back to the web site.  <a href="https://www.aussiebroadband.com.au/help-centre/">“Self-help articles on Internet, mobile, our app and more”</a>.  OK.  No mention of the
  3234. app <i>at all</i>, just an offer of a “chat now”.  Tried that, but they lied:
  3235.      </p>
  3236.  
  3237.      <p><font color="red">Can't open /home/grog/www.lemis.com/grog/Photos/20240715/photolist.php: fopen(/home/grog/www.lemis.com/grog/Photos/20240715/photolist.php): failed to open stream: No such file or directory</font></p>  <a id="Photo-9" name="Photo-9"
  3238.          href="diary-jul2024.php?dirdate=20240715&amp;imagesizes=1111111112&amp;topics=c#Photo-9">
  3239.          <img alt="This should be Aussie-chat.png.  Is it missing?" border="0" id="Photo_9"
  3240.               title="Photo Aussie-chat.png.  Click to redisplay larger version of image."
  3241.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20240715/small/Aussie-chat.png"
  3242.               width="590" height="115"
  3243.           /></a>
  3244.  
  3245.      <p>
  3246. Four minutes wait!  I've never seen that.  When I finally got a response, it seemed like he
  3247. was multitasking.  “Where's the docco?”  First he wanted my name, address and date of birth.
  3248. Just for supplying a pointer to the docco.  No, “Can you try reinstalling the app?”  No,
  3249. that's not an answer to my question.  In the end I asked him to find out and send me email.
  3250. I didn't get any, of course.  But while we were talking, I got a prompt on my phone: enter
  3251. fingerprint.  And that worked.  I wonder if they even have documentation for the app.
  3252.      </p>
  3253.  
  3254.      <p>
  3255. How Aussie have deteriorated!
  3256.      </p>
  3257.      </div>
  3258.    ]]>
  3259.  </description>
  3260.  <dc:creator>Greg Lehey</dc:creator>
  3261.  <dc:date>2024-07-15T23:56:24+00:00</dc:date>
  3262. </item>
  3263.  
  3264.            
  3265. <!-- topic pPo not selected
  3266.      <p>
  3267. It seems that news has stood still since <a href="https://en.wikipedia.org/wiki/Donald_Trump">Donald Trump</a> was hit in the ear by a
  3268. bullet at a rally yesterday.  As one person said, “Never since <a href="https://en.wikipedia.org/wiki/Stormy_Daniels">Stormy Daniels</a> has anybody been so
  3269. disappointed by two inches”.
  3270.      </p>
  3271.  
  3272.      <p>
  3273. But then this photo surfaced:
  3274.      </p>
  3275.  
  3276.      <a href="https://static01.nyt.com/images/2024/08/13/us/politics/13election-live-photo-assess/13election-live-photo-assess-jumbo-v2.jpg">
  3277.      <img alt=""
  3278.          title=".  Click to see in original size."
  3279.          src="https://static01.nyt.com/images/2024/08/13/us/politics/13election-live-photo-assess/13election-live-photo-assess-jumbo-v2.jpg"
  3280.          width="512"
  3281.          /></a>
  3282.      <p>
  3283. That's from <a href="https://www.nytimes.com/2024/07/14/us/politics/photo-path-trump-assassination.html">this
  3284. article</a> in the <a href="https://en.wikipedia.org/wiki/New_York_Times">New York
  3285. Times</a>.  Could it really be a bullet?  Yes, I think so.  I'm sure <a href="https://en.wikipedia.org/wiki/Doug_Mills_(photographer)">Doug Mills</a>, the
  3286. photographer, is over the moon.
  3287.      </p>
  3288.  
  3289.      <p>
  3290. Is it fake?  The article doesn't think so.  Neither do I.  I could have taken it too.  I
  3291. would just have needed to be there, point my camera in the right direction and take
  3292. continuous photos at 60 fps.  And that's effectively what the article says.  But some of the
  3293. details are interesting:
  3294.      </p>
  3295.  
  3296.      <blockquote class="fullwidth">
  3297.        <div class="listitemwidth">
  3298.          Mr. Mills was using a Sony digital camera capable of capturing images at up to 30 frames
  3299.          per second. He took these photos with a shutter speed of 1/8,000th of a second — extremely
  3300.          fast by industry standards.
  3301.        </div>
  3302.      </blockquote>
  3303.  
  3304.      <p>
  3305. 1/8000 s is no longer “extremely fast”.  My <a href="https://en.wikipedia.org/wiki/Olympus_E-30">Olympus E-30</a>, now 15 years old, has
  3306. that speed.  So do our three OM-D cameras.  But in fact it's not even overly fast for modern
  3307. cameras.  If he was taking 30 fps, he was probably using an electronic shutter.  On my
  3308. <a href="https://en.wikipedia.org/wiki/Olympus_OM-D_E-M1_Mark_II">Olympus OM-D E-M1
  3309. Mark II</a> and <a href="http://www.lemis.com/yvonne/">Yvonne's</a> <a href="https://en.wikipedia.org/wiki/Olympus_OM-D_E-M5_Mark_III">E-M5 Mark III</a> that's
  3310. 1/32000 s.  And of course the 30 fps isn't overly fast either: my E-M1 Mark II, now 7 years
  3311. old, can do double that, and the latest <a href="https://en.wikipedia.org/wiki/OM_System">OM System</a> cameras can do 120 fps.  Much
  3312. more important is how long they can keep it up.
  3313.      </p>
  3314.  
  3315.      <p>
  3316. And then there's the question of accuracy.  They go on to say:
  3317.      </p>
  3318.  
  3319.      <blockquote class="fullwidth">
  3320.        <div class="listitemwidth">
  3321.          “If the gunman was firing an AR-15-style rifle, the .223-caliber or 5.56-millimeter
  3322.          bullets they use travel at roughly 3,200 feet per second when they leave the weapon’s
  3323.          muzzle,’’ Mr. Harrigan said. “And with a 1/8,000th of a second shutter speed, this would
  3324.          allow the bullet to travel approximately four-tenths of a foot while the shutter is open.”
  3325.        </div>
  3326.      </blockquote>
  3327.  
  3328.      <p>
  3329. OK, is that <i>really</i> 0.223&quot;?  I recall from my schooldays playing around with
  3330. “.22” rifles.  But <a href="https://en.wikipedia.org/wiki/AR-15%E2%80%93style_rifle#Calibers">yes</a>, that seems
  3331. to be the calibre.  Only: 0.223&quot; is 5.66[42] mm.  Where do they get 5.56 mm?  Wikipedia
  3332. agrees with 5.56 mm.  Is it a different way of measuring them?
  3333.      </p>
  3334.  
  3335.      <p>
  3336. And then the longitudinal measurements.  It's interesting that they divide feet by 10:
  3337. “four-tenths” of a foot is 4.8&quot;.  Assuming that the speed is correct, that converts to
  3338. 975 m/s.  In 1/8000 s that would be 12.2 cm, pretty much 5&quot;, a little more the width of
  3339. a hand.  What the photo shows is <i>much</i> longer than that.  Maybe the shutter speed was
  3340. wrong: looking at that photo, I'd assume 1/2000 s.
  3341.      </p>
  3342.  
  3343.      <p>
  3344. And then there's the question whether it's even genuine.  If it was taken with a 30 fps
  3345. mode, there would have been more images showing the path of the bullet.  But they say
  3346. “capable” of taking up to 30 fps.  What's the reality?  Later they show three images taken,
  3347. at a guess, about 0.5 s apart.  And normal logic suggests that Mills wouldn't have taken
  3348. that many photos of what was essentially a static subject.
  3349.      </p>
  3350.  
  3351.      <p>
  3352. Surely I'm not the only person to be puzzled by these details.  Yes, it's close to my own
  3353. interests, but this is a photo that is going to go down in the annals.  Millions of people
  3354. have looked at it.  Has nobody thought about these details?
  3355.      </p>
  3356.      
  3357. End deselected topic pPo (Catching the Trump bullet) -->
  3358.  
  3359.                  
  3360. <item>
  3361. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jul2024.php#D-20240717-023746</guid>
  3362. <link>http://www.lemis.com/grog/diary-jul2024.php?topics=c#D-20240717-023746</link>
  3363. <category>technology</category>
  3364. <category>opinion</category>
  3365. <title>Back to X configuration</title>
  3366.  <description>
  3367.    <![CDATA[
  3368.    <div align="justify">
  3369.      <p>
  3370. Lately I've been doing very little, and the wait for getting <a href="https://en.wikipedia.org/wiki/VirtualBox">VirtualBox</a> running correctly—if at
  3371. all—means that I have time to look at other painful things.
  3372.      </p>
  3373.  
  3374.      <p>
  3375. So, today <a href="https://www.fvwm.org/"><i>fvwm3</i></a>.  The more I look at it,
  3376. the more it's a can of worms.  There are two major problems:
  3377.      </p>
  3378.  
  3379.      <ul>
  3380.        <li class="fullwidth">
  3381.          <div class="listitemwidth">
  3382.            The documentation is oriented towards the developer, not the end user.  It seems that
  3383.    the syntax for <tt>MenuStyle</tt> has changed.  I used to have:
  3384.          </div>
  3385.  
  3386.  <blockquote class="fullwidth">
  3387. <div style="text-align:left">
  3388.  <tt>
  3389. MenuStyle black gold brown &#45;*&#45;*&#45;medium&#45;r&#45;*&#45;sans&#45;12&#45;*&#45;*&#45;*&#45;p&#45;*&#45;*&#45;* mwm
  3390.  </tt>
  3391. </div>
  3392. </blockquote>
  3393.  
  3394.  <p class="listitemwidth">
  3395.    But now it complains about the keyword <tt>gold</tt>.  The documentation starts with
  3396.  </p>
  3397.  
  3398.  <blockquote class="fullwidth">
  3399.            <div class="listitemwidth">
  3400.              <b>MenuStyle <i>stylename [options]</i></b>
  3401.            </div>
  3402.  
  3403.    <p class="list2width">
  3404.      Sets a new menu style or changes a previously defined style. The stylename is the
  3405.      style name...
  3406.    </p>
  3407.  
  3408.    <p class="list2width">
  3409.      <i>options</i> is a comma separated list containing some of the keywords Fvwm / Mwm /
  3410.      Win, BorderWidth, HilightBack / !HilightBack, HilightTitleBack, ActiveFore /
  3411.      !ActiveFore, MenuColorset, ActiveColorset, GreyedColorset, TitleColorset,
  3412.      Hilight3DThick / Hilight3DThin / Hilight3DOff, Hilight3DThickness, Animation /
  3413.      !Animation, Font, TitleFont, PopupDelay, PopupOffset, TitleWarp ...
  3414.    </p>
  3415.  </blockquote>
  3416.  
  3417.  <p class="listitemwidth">
  3418.    It goes on for pages, with a few examples that don't really point at what I'm doing.
  3419.    About the best thing that I can glean is that the <tt>black</tt> in the original entry
  3420.    has become the name of an unused <tt>MenuStyle</tt>.
  3421.  </p>
  3422.        </li>
  3423.  
  3424.        <li class="fullwidth">
  3425.          <div class="listitemwidth">
  3426.            My previous configuration file Just Growed over decades, and I didn't keep any records
  3427.            of what I did, neither in my diary (which I wasn't keeping at the time) nor in
  3428.            <a href="https://en.wikipedia.org/wiki/Revision_Control_System">RCS</a>.  What
  3429.            few comments I put in didn't really help.
  3430.          </div>
  3431.        </li>
  3432.      </ul>
  3433.  
  3434.      <p>
  3435. But one thing is becoming clearer: I can move a lot of this stuff into the <i>.Xdefaults</i>
  3436. file, and I spent a fair amount of time playing with that, not without some success.
  3437.      </p>
  3438.      </div>
  3439.    ]]>
  3440.  </description>
  3441.  <dc:creator>Greg Lehey</dc:creator>
  3442.  <dc:date>2024-07-17T02:37:46+00:00</dc:date>
  3443. </item>
  3444.  
  3445.                  
  3446. <!-- topic k not selected
  3447.      <p>
  3448. <a href="http://www.lemis.com/grog/diary-dec2023.php?subtitle=Whetstones&amp;article=D-20231221-015357#D-20231221-015357">A few months back</a> I went to some trouble to sharpen my kitchen knives.  Yes, they got
  3449. sharper, but it was much more work than I had expected.
  3450.      </p>
  3451.  
  3452.      <p>
  3453. Today I read <a href="https://www.quora.com/How-expensive-does-a-knife-have-to-be-before-you-will-consider-getting-it-professionally-sharpened/answer/Jesse-Cooks-and-Reads">this article</a> in <a href="https://en.wikipedia.org/wiki/Quora">Quora</a>,
  3454. which still isn't dead.  The article explains that cheap knives are much harder to sharpen
  3455. than more expensive ones, but the expensive ones need sharpening more frequently.
  3456. Specifically, he mentions molybdenum alloy or carbon steel for the expensive knives and 440
  3457. stainless steel for the cheap ones.  Should I try something a bit more up-market?
  3458.      </p>
  3459.      
  3460. End deselected topic k (How to sharpen knives) -->
  3461.  
  3462.            
  3463. <item>
  3464. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jul2024.php#D-20240718-003303</guid>
  3465. <link>http://www.lemis.com/grog/diary-jul2024.php?topics=c#D-20240718-003303</link>
  3466. <category>technology</category>
  3467. <category>opinion</category>
  3468. <title>fvwm3: enough?</title>
  3469.  <description>
  3470.    <![CDATA[
  3471.    <div align="justify">
  3472.      <p>
  3473. More playing around with <a href="https://www.fvwm.org/"><i>fvwm3</i></a> today, and
  3474. at least partially cracked the <tt>MenuStyle</tt> entry.  Instead of this,
  3475.      </p>
  3476.  
  3477.  <blockquote class="fullwidth">
  3478. <div style="text-align:left">
  3479.  <tt>
  3480. MenuStyle black gold brown &#45;*&#45;*&#45;medium&#45;r&#45;*&#45;sans&#45;12&#45;*&#45;*&#45;*&#45;p&#45;*&#45;*&#45;* mwm
  3481.  </tt>
  3482. </div>
  3483. </blockquote>
  3484.  
  3485.      <p>
  3486. I tried this:
  3487.      </p>
  3488.  
  3489.      <blockquote class="fullwidth">
  3490. <div style="text-align:left">
  3491.  <tt>
  3492. MenuStyle * mwm
  3493.  </tt>
  3494. </div>
  3495. </blockquote>
  3496.  
  3497.      <p>
  3498. It didn't complain, but the colours were wrong.  OK, we know that: <tt>Colorset</tt>.  But
  3499. no, it didn't want to know.  It wants <tt><b>Menu</b>Colorset</tt>:
  3500.      </p>
  3501.  
  3502.      <blockquote class="fullwidth">
  3503. <div style="text-align:left">
  3504.  <tt>
  3505. MenuStyle * MenuColorset 5, mwm
  3506.  </tt>
  3507. </div>
  3508. </blockquote>
  3509.  
  3510.      <p>
  3511. But with that, I finally have my configuration the way I want it.  And moving the
  3512. specifications from the window manager to <i>.Xdefaults</i> has changed a number of things.
  3513. Here an example of “before” and “after”:
  3514.      </p>
  3515.  
  3516.      <blockquote class="fullwidth">
  3517. <div style="text-align:left">
  3518.  <tt>
  3519. + &nbsp; &nbsp; &nbsp; "eureka" &nbsp; &nbsp; &nbsp; &nbsp;Exec ssh &#45;A eureka LC_ALL=en_AU.UTF&#45;8 /usr/local/bin/uxterm &#45;name "xterm" &#45;bg BlanchedAlmond &#45;s &#45;sl 2048 &#45;sb &#45;ls &#45;j &#45;rw &#45;display hydra:0.3 &#45;geometry 90x50+53+0 &#45;e /usr/local/bin/bash &amp;
  3520. <br />+ &nbsp; &nbsp; &nbsp; "eureka" &nbsp; &nbsp; &nbsp; &nbsp;Exec ssh &#45;A eureka LC_ALL=en_AU.UTF&#45;8 /usr/local/bin/uxterm &#45;name "xterm&#45;r" &#45;s &#45;sl 2048 &#45;sb &#45;ls &#45;j &#45;rw &#45;display hydra:0.3 &#45;e /usr/local/bin/bash &amp;
  3521. <br />
  3522.  </tt>
  3523. </div>
  3524. </blockquote>
  3525.  
  3526.      <p>
  3527. The down side is in the <i>.Xdefaults</i> file, of course.  I have 13 “names” for
  3528. my <i>xterms</i>, all differing only in geometry and font size.  But for that I need 26
  3529. entries for each screen.  There should be a way to inherit things from a parent.  Maybe
  3530. there is, but I haven't found it.
  3531.      </p>
  3532.      </div>
  3533.    ]]>
  3534.  </description>
  3535.  <dc:creator>Greg Lehey</dc:creator>
  3536.  <dc:date>2024-07-18T00:33:03+00:00</dc:date>
  3537. </item>
  3538.  
  3539.            
  3540. <!-- topic ho not selected
  3541.      <p>
  3542. A while back we got a registration renewal notice for <a href="http://www.lemis.com/yvonne/">Yvonne's</a> car from <a href="https://en.wikipedia.org/wiki/VicRoads">VicRoads</a>.  And
  3543. almost immediately another letter telling us that the sum was wrong.  OK, pay the new sum.
  3544. No, can't do that, the sum is encoded in this silly <a href="https://en.wikipedia.org/wiki/BPAY">BPAY</a> system.  Pay the sum indicated and we'll
  3545. contact you about the rest.
  3546.      </p>
  3547.  
  3548.      <p>
  3549. That happened today, with a letter that suggested that it was all our fault that we hadn't
  3550. payed the final $12.65.  Never mind, you can call 13 11 71 and pay by credit card (<b>card
  3551. payment fee applies</b>) or go personally to VicRoads in <a href="https://en.wikipedia.org/wiki/Ballarat">Ballarat</a> (and wait in line).
  3552.      </p>
  3553.  
  3554.      <p>
  3555. Both are seriously inconvenient and costly.  But there's no mention of a way to transfer the
  3556. money.  That's really offensive.
  3557.      </p>
  3558.      
  3559. End deselected topic ho (VicRoads insult to injury) -->
  3560.  
  3561.      
  3562.      
  3563. <!-- topic Jho not selected
  3564.      <p>
  3565. A couple of days ago I had another greeting from Jim Lannen, my least favourite sparky, whom
  3566. by chance I first met <a href="http://www.lemis.com/grog/diary-jul2014.php?subtitle=A%20new%20electrician?&amp;article=D-20140719-011101#D-20140719-011101">ten years ago today</a>.  It has been raining a lot lately, and the power connection to
  3567. the septic tank pump got wet, causing the <a href="https://en.wikipedia.org/wiki/Residual-current_device">RCD</a> to trip.  It was late
  3568. at night, so I just disconnected it.
  3569.      </p>
  3570.  
  3571.      <p>
  3572. But clearly the tank needs to be emptied, and this evening the warning light went on.  The
  3573. problem is that the power point is in the middle of nowhere, so even though it's an outdoor
  3574. power point, it's not adequately protected:
  3575.      </p>
  3576.  
  3577.            
  3578.      <p>
  3579. This has happened in the past, and drying the connections has worked round the problem.  But
  3580. try as I might, I couldn't get the damn thing to work today.  Another thing to be looked at
  3581. tomorrow, this time more urgently.  Is it even the same problem, or has the pump given up?
  3582. It ran for about 20 seconds before tripping the RCD.  Whom do I call?  A sparky?  <a href="https://www.ultimategroup.com.au/">UPI</a>?  Mari Hendriks, the plumber?  This has the
  3583. potential to—once again—become expensive.
  3584.      </p>
  3585.      
  3586. End deselected topic Jho (Septic tank pump fail) -->
  3587.  
  3588.                  
  3589. <!-- topic Jh not selected
  3590.      <p>
  3591. Outside first thing this morning and connected the septic tank pump to a different circuit
  3592. with an extension lead.  Success!  So at least the pump itself is still working.
  3593.      </p>
  3594.  
  3595.      <p>
  3596. What causes are left?  The most obvious would be the presence of moisture in the power
  3597. point.  But there's also the possibility that there are a number of connections with slight
  3598. current leaks, like to the bore pump, which is on the same circuit.  Finding that could take
  3599. time.  But at least we now have time.
  3600.      </p>
  3601.      
  3602. End deselected topic Jh (Septic tank pump success) -->
  3603.  
  3604.      
  3605.      
  3606. <item>
  3607. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jul2024.php#D-20240718-232530</guid>
  3608. <link>http://www.lemis.com/grog/diary-jul2024.php?topics=c#D-20240718-232530</link>
  3609. <category>technology</category>
  3610. <title>More fvwm3 conversions</title>
  3611.  <description>
  3612.    <![CDATA[
  3613.    <div align="justify">
  3614.      <p>
  3615. Continued with my <a href="https://www.x.org/">X</a> reconfiguration today, and
  3616. discovered that I had forgot the details that I had investigated <a href="http://www.lemis.com/grog/diary-jul2024.php?subtitle=X%20configuration:%20RTFM!&amp;article=D-20240702-023308#D-20240702-023308">at the beginning of the month</a>.  Put them in, and they worked.  But now I have even
  3617. more multiple entries.  Spent some time looking for ways to inherit resources, but there
  3618. doesn't seem to be one.  Now I have 163 mainly duplicate resources in my <i>.Xdefaults</i>
  3619. file, and it looks like it might increase.
  3620.      </p>
  3621.      </div>
  3622.    ]]>
  3623.  </description>
  3624.  <dc:creator>Greg Lehey</dc:creator>
  3625.  <dc:date>2024-07-18T23:25:30+00:00</dc:date>
  3626. </item>
  3627.  
  3628.      
  3629.      
  3630. <!-- topic ao not selected
  3631.      <p>
  3632. While walking the dogs today, came across this sight:
  3633.      </p>
  3634.  
  3635.      
  3636.      <p>
  3637. What's that?  Looks like blood.  And sure enough,
  3638.      </p>
  3639.  
  3640.            
  3641.      <p>
  3642. What happened there?  Yes, kangaroos get hit by cars and die.  But this one didn't seem to
  3643. have anything like that.  Instead, its stomach was torn open, and internal organs (lungs?)
  3644. had been removed:
  3645.      </p>
  3646.  
  3647.            
  3648.      <p>
  3649. How did that happen?
  3650.      </p>
  3651.      
  3652. End deselected topic ao (Bad day for kangaroos) -->
  3653.  
  3654.                  
  3655. <!-- topic a not selected
  3656.      <p>
  3657. <a href="http://www.lemis.com/yvonne/">Yvonne</a> found this picture today:
  3658.      </p>
  3659.  
  3660.      
  3661.      <p>
  3662. <a href="http://www.lemis.com/grog/Albums/Animals/Mona.php">Mona</a> is still not really happy with the
  3663. dogs, but she's coming to terms with them, even when they come closer:
  3664.      </p>
  3665.  
  3666.      
  3667.      <p>
  3668. Not before time.  The red eyes are a reflection of the blanket she's sitting on, not her
  3669. mood.
  3670.      </p>
  3671.  
  3672.      
  3673.      <p>
  3674.      </p>
  3675.      
  3676. End deselected topic a (Mona acclimatization) -->
  3677.  
  3678.            
  3679. <item>
  3680. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jul2024.php#D-20240720-024534</guid>
  3681. <link>http://www.lemis.com/grog/diary-jul2024.php?topics=c#D-20240720-024534</link>
  3682. <category>technology</category>
  3683. <category>opinion</category>
  3684. <title>Emacs resources</title>
  3685.  <description>
  3686.    <![CDATA[
  3687.    <div align="justify">
  3688.      <p>
  3689. So gradually my <i>xterm</i> configuration is close to where I want it, though the effect on
  3690. the <i>.Xdefaults</i> file is clear:
  3691.      </p>
  3692.  
  3693.      <blockquote class="fullwidth">
  3694. <div style="text-align:left">
  3695.  <tt>
  3696. <code><font color="blue">=== grog@hydra (/dev/pts/23)</font> <font color="red">~</font> <font color="blue">762</font> &#45;&gt; <b><tt>l /eureka/home/grog/.Xdefaults .Xdefaults&#45;hydra</tt></b></code>
  3697. <br />&#45;rw&#45;r&#45;&#45;r&#45;&#45; &nbsp;1 grog &nbsp;lemis &nbsp;2,477 30 Jun 14:38 /eureka/home/grog/.Xdefaults
  3698. <br />&#45;r&#45;&#45;r&#45;&#45;r&#45;&#45; &nbsp;1 grog &nbsp;lemis &nbsp;7,644 19 Jul 13:30 .Xdefaults&#45;hydra
  3699. <br />
  3700.  </tt>
  3701. </div>
  3702. </blockquote>
  3703.  
  3704.      <p>
  3705. Next, <a href="https://www.gnu.org/software/emacs/"><i>Emacs</i></a>.  And somehow
  3706. things started all over again.  Somehow the <a href="https://www.gnu.org/software/emacs/manual/html_node/emacs/Resources.html">specified
  3707. resources</a> don't seem to have any effect.  They do, however, have a couple of
  3708. strangenesses.  For example, I have:
  3709.      </p>
  3710.  
  3711.      <blockquote class="fullwidth">
  3712. <div style="text-align:left">
  3713.  <tt>
  3714. emacs*Geometry: 110x75
  3715.  </tt>
  3716. </div>
  3717. </blockquote>
  3718.  
  3719.      <p>
  3720. That's the <i>xrdb</i> syntax that I know.  But an example in the Emacs manual uses a dot
  3721. instead of an asterisk:
  3722.      </p>
  3723.  
  3724.      <blockquote class="fullwidth">
  3725. <div style="text-align:left">
  3726.  <tt>
  3727. emacs.Foreground: dark green
  3728.  </tt>
  3729. </div>
  3730. </blockquote>
  3731.  
  3732.      <p>
  3733. Does that work?  Does it make a difference?  It seems that <tt>emacs</tt> and <tt>Emacs</tt>
  3734. do make a difference:
  3735.      </p>
  3736.  
  3737.      <blockquote class="fullwidth">
  3738.        <div class="listitemwidth">
  3739.          The program name is the name of the executable file to which the resource applies. For
  3740.          Emacs, this is normally ‘emacs’. To specify a definition that applies to all instances of
  3741.          Emacs, regardless of the name of the Emacs executable, use ‘Emacs’.
  3742.        </div>
  3743.      </blockquote>
  3744.  
  3745.      <p>
  3746. I need to understand that.  Could it be a hint at some kind of hierarchy?  Courtesy
  3747. of <i>emacs</i> or of X?
  3748.      </p>
  3749.  
  3750.      <p>
  3751. One thing did become increasingly irritating, though: this popup telling me that “pure-GTK”
  3752. doesn't work with <a href="https://www.x.org/">X</a>.  Somehow, over 6 months later,
  3753. it still grates that a port should be configured to work with <a href="https://en.wikipedia.org/wiki/Wayland">Wayland</a> but not with X.  OK, time to fix
  3754. it.
  3755.      </p>
  3756.  
  3757.      <blockquote class="fullwidth">
  3758. <div style="text-align:left">
  3759.  <tt>
  3760. <span style="background&#45;color: BlanchedAlmond">
  3761. <br /><code><font color="blue">=== root@hydra (/dev/pts/32)</font> <font color="red">/usr/ports/graphics/hugin</font> <font color="blue">81</font> &#45;&gt; <b><tt>git diff /usr/ports/editors/emacs&#45;devel/Makefile diff</tt></b></code>
  3762. <br />diff &#45;&#45;git a/editors/emacs&#45;devel/Makefile b/editors/emacs&#45;devel/Makefile
  3763. <br />&#45;&#45;&#45; a/editors/emacs&#45;devel/Makefile
  3764. <br />+++ b/editors/emacs&#45;devel/Makefile
  3765. <br /><span style="color:blue">@@ &#45;87,7 +87,7 @@</span> OPTIONS_DEFINE= &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ACL DBUS GNUTLS GSETTINGS HARFBUZZ JSON LCMS2 \
  3766. <br />&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;XFT XIM XML XWIDGETS
  3767. <br />&nbsp;OPTIONS_DEFAULT= &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ACL CAIRO DBUS GIF GNUTLS GSETTINGS GTK3 \
  3768. <br />&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;HARFBUZZ JPEG JSON KQUEUE LCMS2 MAILUTILS \
  3769. <br /><span style="color: red">&#45; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; MODULES NATIVECOMP OSS PGTK PNG SCROLLBARS \</span>
  3770. <br /><span style="color: white">+ &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; MODULES NATIVECOMP OSS PNG SCROLLBARS \</span>
  3771. <br />&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;SOURCES SQLITE3 SVG THREADS TIFF TREESITTER \
  3772. <br />&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;WEBP XML
  3773. <br />&nbsp;OPTIONS_GROUP= &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; GRAPHICS
  3774. <br /><span style="color:blue">@@ &#45;118,7 +118,7 @@</span> MAILUTILS_DESC= &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Mail framework via GNU Mailutils
  3775. <br />&nbsp;MODULES_DESC= &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Dynamic modules support
  3776. <br />&nbsp;NATIVECOMP_DESC= &nbsp; &nbsp; &nbsp; Emacs Lisp native compiler support
  3777. <br />&nbsp;OTF_DESC= &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Opentype fonts
  3778. <br /><span style="color: red">&#45;PGTK_DESC= &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Pure GTK GUI [implies CAIRO, GTK3]</span>
  3779. <br /><span style="color: white">+PGTK_DESC= &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Pure GTK GUI [implies CAIRO, GTK3, wayland only]</span>
  3780. <br />&nbsp;SCROLLBARS_DESC= &nbsp; &nbsp; &nbsp; Toolkit scroll&#45;bars
  3781. <br />&nbsp;SOURCES_DESC= &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Install sources
  3782. <br />&nbsp;SVG_DESC= &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Scalable vector graphics support [implies PNG]
  3783. <br /></span>
  3784.  </tt>
  3785. </div>
  3786. </blockquote>
  3787.  
  3788.      <p>
  3789. How I love Linux half-coloured output!  How I wish I could turn it off globally!  At least
  3790. my choice of a not-quite-white background at least gives a clue that there's something
  3791. there, and I can “highlight” the white on pale output on a web browser.  Even that doesn't
  3792. work in an <i>xterm</i>.  And where does this <tt>diff&nbsp;--git</tt> come from?  It's not
  3793. in <a href="https://www.freebsd.org/">FreeBSD</a> <i>diff</i>.
  3794.      </p>
  3795.  
  3796.      <p>
  3797. But somehow that didn't work.  When I ran config, I still had <tt>PGTK</tt> set.  Saved
  3798. configuration?  Couldn't find it.  I had to run <i>ktrace</i> to find where it was
  3799. hidden: <i>/var/db/ports/editors_emacs-devel/options</i>.  Now why did they do that?
  3800.      </p>
  3801.  
  3802.      <p>
  3803. Things still weren't done, of course.  It wanted to build <a href="https://en.wikipedia.org/wiki/GCC">gcc 13</a>, and for some reason it failed.  OK,
  3804. install the package.  And then some random dependency took exception to my <i>autoconf</i>.
  3805. Another package, and then the thing went off on its merry way.
  3806.      </p>
  3807.  
  3808.      <p>
  3809. People, we've had the Ports Collection for over 30 years.  When is it going to grow up?
  3810.      </p>
  3811.      </div>
  3812.    ]]>
  3813.  </description>
  3814.  <dc:creator>Greg Lehey</dc:creator>
  3815.  <dc:date>2024-07-20T02:45:34+00:00</dc:date>
  3816. </item>
  3817.  
  3818.            
  3819. <item>
  3820. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jul2024.php#D-20240720-033449</guid>
  3821. <link>http://www.lemis.com/grog/diary-jul2024.php?topics=c#D-20240720-033449</link>
  3822. <category>technology</category>
  3823. <title>xterm clipboard access</title>
  3824.  <description>
  3825.    <![CDATA[
  3826.    <div align="justify">
  3827.      <p>
  3828. A while back I found suggestions that <a href="https://www.x.org/">X</a>, and in
  3829. particular <a href="https://en.wikipedia.org/wiki/Xterm"><i>xterm</i></a>, can
  3830. access the clipboard directly.  I made a note of it in my diary, but not clearly enough: it
  3831. took me 20 minutes to chase down <a href="https://unix.stackexchange.com/questions/225062/how-can-i-copy-text-from-xterm-awesome-debian-virtualbox">this reference</a>, to which I referred <a href="http://www.lemis.com/grog/diary-may2024.php?subtitle=X%20configuration%20continued&amp;article=D-20240531-023146#D-20240531-023146">less than 2 months ago</a>.  It wasn't without issues, which I should chase up.
  3832.      </p>
  3833.      </div>
  3834.    ]]>
  3835.  </description>
  3836.  <dc:creator>Greg Lehey</dc:creator>
  3837.  <dc:date>2024-07-20T03:34:49+00:00</dc:date>
  3838. </item>
  3839.  
  3840.                  
  3841. <item>
  3842. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jul2024.php#D-20240721-002744</guid>
  3843. <link>http://www.lemis.com/grog/diary-jul2024.php?topics=c#D-20240721-002744</link>
  3844. <category>technology</category>
  3845. <title>New Emacs</title>
  3846.  <description>
  3847.    <![CDATA[
  3848.    <div align="justify">
  3849.      <p>
  3850. My <a href="https://www.gnu.org/software/emacs/"><i>Emacs</i></a> build finished
  3851. yesterday without complications, and this morning I installed it, also almost without
  3852. complications.  Only this message:
  3853.      </p>
  3854.  
  3855.      <blockquote class="fullwidth">
  3856.        <div class="listitemwidth">
  3857.          Emacs is now built with native compilation enabled by default, which requires GCC version
  3858.  11 or later.  However, it is known that some elisp applications don't work correctly when
  3859.  compiled.  You can work around any such issues by disabling native compilation using the
  3860.  following steps...
  3861.        </div>
  3862.      </blockquote>
  3863.  
  3864.      <p>
  3865. That's in <i>/usr/ports/editors/emacs-devel/pkg-message</i>.  Is it something to worry
  3866. about?  Only, I suppose, if I get an “application” that doesn't work when being compiled.
  3867. Apart from that, it started, worked correctly, and <i>respected my <a href="https://www.x.org/">X</a> resources</i>.  Can it be that the “Pure <a href="https://en.wikipedia.org/wiki/GTK">GTK</a> disables X resources?  Since it's intended
  3868. for <a href="https://en.wikipedia.org/wiki/Wayland">Wayland</a>, that could be the
  3869. case.
  3870.      </p>
  3871.      </div>
  3872.    ]]>
  3873.  </description>
  3874.  <dc:creator>Greg Lehey</dc:creator>
  3875.  <dc:date>2024-07-21T00:27:44+00:00</dc:date>
  3876. </item>
  3877.  
  3878.            
  3879. <item>
  3880. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jul2024.php#D-20240721-003257</guid>
  3881. <link>http://www.lemis.com/grog/diary-jul2024.php?topics=c#D-20240721-003257</link>
  3882. <category>technology</category>
  3883. <category>photography</category>
  3884. <category>opinion</category>
  3885. <title>More ports pain</title>
  3886.  <description>
  3887.    <![CDATA[
  3888.    <div align="justify">
  3889.      <p>
  3890. <a href="http://www.lemis.com/grog/stones-road/exterior.php">House photo</a> day today, made more
  3891. difficult by wind and threatening rain.  But I got the photos done.  The fun started with
  3892. the processing:
  3893.      </p>
  3894.  
  3895.      <blockquote class="fullwidth">
  3896. <div style="text-align:left">
  3897.  <tt>
  3898. /usr/local/share/hugin/data/plugins/top_five.py
  3899. <br />&nbsp;&nbsp; CAT:Control Points
  3900. <br />&nbsp;&nbsp; NAM:keep 5 CPs per image pair
  3901. <br />&nbsp;&nbsp; fails @api&#45;max
  3902. <br />
  3903.  </tt>
  3904. </div>
  3905. </blockquote>
  3906.  
  3907.      <p>
  3908. What does that mean?  <a href="http://hugin.sourceforge.net"><i>Hugin</i></a> complains about things all the time, but this one was fatal.  My best bet is that it was a
  3909. knotted <a href="https://en.wikipedia.org/wiki/Python_(programming_language)">python</a>.  OK, reinstall <i>Hugin</i>.
  3910.      </p>
  3911.  
  3912.      <blockquote class="fullwidth">
  3913. <div style="text-align:left">
  3914.  <tt>
  3915. ===&gt; &nbsp; Registering installation for hugin&#45;2023.0.0_4
  3916. <br />pkg&#45;static: Unable to access file /home/src/FreeBSD/git/ports/graphics/hugin/work/stage/usr/local/lib/python3.11/site&#45;packages/_hsi.so:No such file or directory
  3917. <br />pkg&#45;static: Unable to access file /home/src/FreeBSD/git/ports/graphics/hugin/work/stage/usr/local/lib/python3.11/site&#45;packages/hpi.py:No such file or directory
  3918. <br />pkg&#45;static: Unable to access file /home/src/FreeBSD/git/ports/graphics/hugin/work/stage/usr/local/lib/python3.11/site&#45;packages/hsi.py:No such file or directory
  3919. <br />
  3920.  </tt>
  3921. </div>
  3922. </blockquote>
  3923.  
  3924.      <p>
  3925. More ports agony!  But I should be able to install the package:
  3926.      </p>
  3927.  
  3928.      <blockquote class="fullwidth">
  3929. <div style="text-align:left">
  3930.  <tt>
  3931. <code><font color="blue">=== root@hydra (/dev/pts/32)</font> <font color="red">/usr/ports/graphics/hugin</font> <font color="blue">74</font> &#45;&gt; <b><tt>pkg install hugin</tt></b></code>
  3932. <br />The following 32 package(s) will be affected (of 0 checked):
  3933. <br />
  3934. <br />Installed packages to be REMOVED:
  3935. <br />&nbsp;&nbsp; &nbsp; &nbsp; &nbsp;ImageMagick7: 7.1.0.62_8
  3936. <br />&nbsp;&nbsp; &nbsp; &nbsp; &nbsp;imlib2: 1.12.2_3,2
  3937. <br />&nbsp;&nbsp; &nbsp; &nbsp; &nbsp;ja&#45;tex&#45;ptex: 3.6_4
  3938. <br />&nbsp;&nbsp; &nbsp; &nbsp; &nbsp;poppler: 23.05.0_2
  3939. <br />&nbsp;&nbsp; &nbsp; &nbsp; &nbsp;tex&#45;dvipdfmx: 20230313
  3940. <br />&nbsp;&nbsp; &nbsp; &nbsp; &nbsp;... many more tex
  3941. <br />&nbsp;&nbsp; &nbsp; &nbsp; &nbsp;xteddy: 2.2_3
  3942. <br />
  3943.  </tt>
  3944. </div>
  3945. </blockquote>
  3946.  
  3947.      <p>
  3948. What's that?  Once again it wants to completely update my system.  What a pain!  And why the
  3949. choice of what to remove?  <i>/usr/ports/games/xteddy</i> is a game that I found from Thomas
  3950. Adam of <a href="https://www.fvwm.org/"><i>fvwm</i></a> fame.  It's not my thing,
  3951. and I was just too lazy to remove it, but how can it possibly conflict with <i>Hugin</i>?
  3952.      </p>
  3953.  
  3954.      <p>
  3955. So what do I do?  Could it be that the package list is not up to date?  Still more work to
  3956. do for something that shouldn't have changed.  But since I still have the issues with
  3957. <a href="https://en.wikipedia.org/wiki/Enblend"><i>enblend</i></a>, it was simpler
  3958. to do everything on <i>eureka</i>.  Somehow this migration will never end.
  3959.      </p>
  3960.      </div>
  3961.    ]]>
  3962.  </description>
  3963.  <dc:creator>Greg Lehey</dc:creator>
  3964.  <dc:date>2024-07-21T00:32:57+00:00</dc:date>
  3965. </item>
  3966.  
  3967.            
  3968. <item>
  3969. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jul2024.php#D-20240721-004407</guid>
  3970. <link>http://www.lemis.com/grog/diary-jul2024.php?topics=c#D-20240721-004407</link>
  3971. <category>technology</category>
  3972. <category>opinion</category>
  3973. <title>Here's a basket for all your eggs</title>
  3974.  <description>
  3975.    <![CDATA[
  3976.    <div align="justify">
  3977.      <p>
  3978. I continue to get popups like this on random web sites:
  3979.      </p>
  3980.  
  3981.        <a id="Photo-10" name="Photo-10"
  3982.          href="diary-jul2024.php?dirdate=20240720&amp;imagesizes=11111111112&amp;topics=c#Photo-10">
  3983.          <img alt="This should be Eggs-baskets.png.png.  Is it missing?" border="0" id="Photo_10"
  3984.               title="Photo Eggs-baskets.png.png.  Click to redisplay larger version of image."
  3985.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20240720/small/Eggs-baskets.png.png"
  3986.               width="304" height="222"
  3987.           /></a>
  3988.  
  3989.      <p>
  3990. What a good idea!  It makes it so much easier to compromise multiple sites if somebody gets
  3991. your Google password.
  3992.      </p>
  3993.  
  3994.      <p>
  3995. The real issue is, of course, that creating and maintaining passwords is too complicated,
  3996. especially if you're using a mobile phone.  I keep a non-standard list of passwords <i>and
  3997. associated email addresses</i>, of which I have several hundred.  Crack one of those and you
  3998. have access to one site only.  Spam me on it and I can remove it.  Begone foul spammer!
  3999.      </p>
  4000.      </div>
  4001.    ]]>
  4002.  </description>
  4003.  <dc:creator>Greg Lehey</dc:creator>
  4004.  <dc:date>2024-07-21T00:44:07+00:00</dc:date>
  4005. </item>
  4006.  
  4007.            
  4008. <item>
  4009. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jul2024.php#D-20240721-004813</guid>
  4010. <link>http://www.lemis.com/grog/diary-jul2024.php?topics=c#D-20240721-004813</link>
  4011. <category>technology</category>
  4012. <category>general</category>
  4013. <category>opinion</category>
  4014. <title>World network crash</title>
  4015.  <description>
  4016.    <![CDATA[
  4017.    <div align="justify">
  4018.      <p>
  4019. Email from the <a href="https://en.wikipedia.org/wiki/The_Courier_(Ballarat)">Ballarat
  4020. Courier</a> today:
  4021.      </p>
  4022.  
  4023.      <blockquote class="fullwidth">
  4024. <div style="text-align:left">
  4025.  <tt>
  4026. Date: Fri, 19 Jul 2024 00:47:00 &#45;0600
  4027. <br />Subject: Breaking: Major IT outage impacting banks, media, airlines and supermarkets
  4028.  </tt>
  4029. </div>
  4030. </blockquote>
  4031.  
  4032.      <p>
  4033. Why should the Ballarat Courier report that?  Nobody else did.
  4034.      </p>
  4035.  
  4036.      <p>
  4037. Well, for about 1¼ hours.  Then the <a href="https://en.wikipedia.org/wiki/New_York_Times">New York Times</a> came up with this:
  4038.      </p>
  4039.  
  4040.      <blockquote class="fullwidth">
  4041. <div style="text-align:left">
  4042.  <tt>
  4043. date: Fri, 19 Jul 2024 04:01:28 &#45;0400
  4044. <br />Subject: Breaking news: Global tech outage grounds flights and hits businesses
  4045.  </tt>
  4046. </div>
  4047. </blockquote>
  4048.  
  4049.      <p>
  4050. Reading headers is frequently interesting.  The Ballarat Courier seems to think that it's in
  4051. the US Mountain time zone—maybe its server is.  And the Times uses lower case for
  4052. its <tt>Date</tt> header.
  4053.      </p>
  4054.  
  4055.      <p>
  4056. How did the Ballarat Courier get there first?  Part was because at the time it seemed to be
  4057. limited to Australia—not the first time that our geographical position has caused us to find
  4058. a global problem first.  But somehow the Courier often seems to be the first to report
  4059. something global.
  4060.      </p>
  4061.  
  4062.      <p>
  4063. So, what was it?  <i>Lots</i> of news about it, of course, but it took forever to find out
  4064. what had happened.  A botched update from <a href="https://en.wikipedia.org/wiki/CrowdStrike">CrowdStrike</a> caused a <a href="https://en.wikipedia.org/wiki/BSOD">BSOD</a> on Microsoft machines.  And after
  4065. rebooting it got loaded before anything could be done, so the machines went into a reboot
  4066. loop.  The <a href="https://www.tomshardware.com/software/windows/how-to-fix-crowdstrike-bsods-in-three-minutes-fix-requires-manual-changes-but-they-are-simple">solution</a> required physical access to the machines in question.
  4067.      </p>
  4068.  
  4069.      <p>
  4070. Could this happen to <a href="https://www.freebsd.org/">FreeBSD</a>?  A good
  4071. operating system can't be shot down by an application program.  But yes!  It seems that the
  4072. module in question corresponds to a kernel module, so protection from application programs
  4073. isn't enough.  Only the FreeBSD solution is simpler: boot single user, remove the module,
  4074. continue with boot.  Does it still require physical access?
  4075.      </p>
  4076.  
  4077.      <p>
  4078. The real issue seems to be inadequate testing and too-fast rollout.  Kernel modules can
  4079. cause crashes.  Don't spread the same module around the world all at once.
  4080.      </p>
  4081.      </div>
  4082.    ]]>
  4083.  </description>
  4084.  <dc:creator>Greg Lehey</dc:creator>
  4085.  <dc:date>2024-07-21T00:48:13+00:00</dc:date>
  4086. </item>
  4087.  
  4088.            
  4089. <!-- topic ao not selected
  4090.      <p>
  4091. We've had <a href="http://www.lemis.com/grog/Albums/Animals/Mona.php">Mona</a> for three months now.
  4092. Things haven't developed quite as we expected.  In particular, she still doesn't sleep with
  4093. <a href="http://www.lemis.com/grog/Albums/Animals/Bruno.php">Bruno</a>, though there was a time when I
  4094. thought that they would get there.  My guess is that they never will.
  4095.      </p>
  4096.  
  4097.      <p>
  4098. On the other hand, she's getting closer and closer to <a href="http://www.lemis.com/yvonne/">Yvonne</a> and myself.  Her only issue is with the dogs, and though that's getting better—see
  4099. <a href="http://www.lemis.com/grog/diary-jul2024.php?subtitle=Mona%20acclimatization&amp;article=D-20240720-024114#D-20240720-024114">yesterday</a>—there's still a way to go.
  4100.      </p>
  4101.      
  4102. End deselected topic ao (Mona at three months) -->
  4103.  
  4104.            
  4105. <!-- topic ko not selected
  4106.      <p>
  4107. I've received a bottle of „Schwarzwälder Kirschwasser“ (“Black Forest cherry water”) from
  4108. Andrea <b>&amp;</b> Daniel Schöpf in <a href="https://de.wikipedia.org/wiki/Steinach_(Ortenaukreis)">Steinach</a>, apparently a very
  4109. small producer.  What does it taste like?  This evening we had <a href="http://www.lemis.com/grog/recipes/fondue.php">fondue</a> for dinner, time for a comparison with the other two
  4110. that I have:
  4111.      </p>
  4112.  
  4113.            
  4114.      <p>
  4115. And how was it?  I don't know.  I seem to have lost my sense of taste.  They all tasted
  4116. pretty much the same.  At least it's not like this <i>horrible</i> <a href="https://www.danmurphys.com.au/product/DM_29820/baitz-kirsch-500ml">Baitz</a> Kirsch.
  4117.      </p>
  4118.      
  4119. End deselected topic ko (New Kirsch) -->
  4120.  
  4121.                  
  4122. <!-- topic a not selected
  4123.      <p>
  4124. Seen this afternoon.
  4125.      </p>
  4126.  
  4127.      
  4128.      <p>
  4129. The dogs were outside, of course.
  4130.      </p>
  4131.      
  4132. End deselected topic a (Mona in bedroom) -->
  4133.  
  4134.            
  4135. <item>
  4136. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jul2024.php#D-20240722-015501</guid>
  4137. <link>http://www.lemis.com/grog/diary-jul2024.php?topics=c#D-20240722-015501</link>
  4138. <category>technology</category>
  4139. <title>More X configuration fun</title>
  4140.  <description>
  4141.    <![CDATA[
  4142.    <div align="justify">
  4143.      <p>
  4144. What's next with my <a href="https://www.x.org/">X</a> configuration?  Where should
  4145. I start?  A good one would be to interface with the <a href="https://en.wikipedia.org/wiki/Clipboard_(computing)">clipboard</a>.  I've <a href="http://www.lemis.com/grog/diary-may2024.php?subtitle=X%20configuration%20continued&amp;article=D-20240531-023146#D-20240531-023146">tried this before</a>, but it didn't work as I expected.  Time to look again.
  4146.      </p>
  4147.  
  4148.      <p>
  4149. Another answer in the <a href="https://unix.stackexchange.com/questions/225062/how-can-i-copy-text-from-xterm-awesome-debian-virtualbox?newreg=be86b9f1139248988c2f5f5980a0ebfb">page that described the <i>xterm</i> feature</a> recommends adding this
  4150. to <i>.Xdefaults</i>:
  4151.      </p>
  4152.  
  4153.      <blockquote class="fullwidth">
  4154. <div style="text-align:left">
  4155.  <tt>
  4156. xterm*VT100.Translations: #override \
  4157. <br />&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Ctrl Shift &lt;Key&gt;V: &nbsp; &nbsp;insert&#45;selection(CLIPBOARD) \n\
  4158. <br />&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Ctrl Shift &lt;Key&gt;C: &nbsp; &nbsp;copy&#45;selection(CLIPBOARD)
  4159. <br />
  4160.  </tt>
  4161. </div>
  4162. </blockquote>
  4163.  
  4164.      <p>
  4165. But that's strange.  I don't see anything like that elsewhere, and I'd prefer to do it with
  4166. the mouse.  Other pages suggest that you can set mouse bindings there too, but they don't
  4167. make it very clear what to do.  How about dumping the current <i>xterm</i> bindings?  A
  4168. quick search pointed me at <i>editres</i>.  Tried that, didn't get a response.  A web search
  4169. showed that <a href="https://github.com/XQuartz/XQuartz/discussions/183">I'm not
  4170. alone</a>, though there weren't many hits, and one of them was <a href="http://www.lemis.com/grog/diary-dec2023.php#D-20231202-011442">this one</a>, which I
  4171. wrote 7 months ago.
  4172.      </p>
  4173.  
  4174.      <p>
  4175. There I found a way to dump the current resource database entries with <i>xrdb -query</i>,
  4176. but that only shows, well, the resource database, not the compiled-in defaults that I was
  4177. looking for.  Once again a dead end.  About all I found was:
  4178.      </p>
  4179.  
  4180.      <blockquote class="fullwidth">
  4181. <div style="text-align:left">
  4182.  <tt>
  4183. *VT100*utf8: &nbsp; &nbsp;1
  4184. <br />*VT100.translations: &nbsp; &nbsp;#override &lt;Key&gt;Next: scroll&#45;forw(1,page) \n\
  4185. <br />&nbsp;&lt;Key&gt;Prior: scroll&#45;back(1,page)
  4186. <br />
  4187.  </tt>
  4188. </div>
  4189. </blockquote>
  4190.  
  4191.      <p>
  4192. I also found <a href="https://unix.stackexchange.com/questions/312360/start-xterm-instance-with-different-configurations">this page</a>, which I haven't digested yet.  It points to documentation of the resource
  4193. entries in <i>X(7)</i>, and mentions that the name at the beginning of a resource
  4194. specification can be either an <i>instance</i> or a <i>class</i>, though it's not (yet)
  4195. clear how they differ.  In the example, instances start with a lower case letter and classes
  4196. with an upper case letter, but it's not clear that that's significant.
  4197.      </p>
  4198.  
  4199.      <p>
  4200. While searching for answers, came across <a href="https://invisible-island.net/xterm/ctlseqs/ctlseqs.html#h4-Functions-using-CSI-_-ordered-by-the-final-character-lparen-s-rparen:CSI-?-Pm-h:Ps-=-1-0-3-6.1F81">this page</a>, which purports to be a complete list of <i>xterm</i> control sequences.
  4201. Can it help with this <b><i>horrible</i></b> page resizing during ports builds that I
  4202. complained about in <i>&lt;mumble&gt;</i>?  Well, I thought I did.  When building
  4203. ports, <i>something</i> changes the number of lines on the page:
  4204.      </p>
  4205.  
  4206.      <blockquote class="fullwidth">
  4207. <div style="text-align:left">
  4208.  <tt>
  4209. ===== Fri 19 Jul 2024 15:05:41 AEST on hydra.lemis.com: Make config
  4210. <br />[1;24r^M
  4211. <br />===&gt; Options unchanged
  4212. <br />
  4213.  </tt>
  4214. </div>
  4215. </blockquote>
  4216.  
  4217.      <p>
  4218. The result is that text at the bottom of the page stays there, and it seems that the build
  4219. has hung, when in fact the real output is only ⅓ of the way from the top.  Why do they do
  4220. that?  And how do I find it?  The page proved to be singularly useless, since I can't find
  4221. that control sequence there.  But it brought back to me that there's One More Thing to look
  4222. for.
  4223.      </p>
  4224.      </div>
  4225.    ]]>
  4226.  </description>
  4227.  <dc:creator>Greg Lehey</dc:creator>
  4228.  <dc:date>2024-07-22T01:55:01+00:00</dc:date>
  4229. </item>
  4230.  
  4231.                  
  4232. <item>
  4233. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jul2024.php#D-20240723-004029</guid>
  4234. <link>http://www.lemis.com/grog/diary-jul2024.php?topics=c#D-20240723-004029</link>
  4235. <category>technology</category>
  4236. <category>language</category>
  4237. <category>general</category>
  4238. <category>opinion</category>
  4239. <title>Understanding the CrowdStrike failure</title>
  4240.  <description>
  4241.    <![CDATA[
  4242.    <div align="justify">
  4243.      <p>
  4244. <a href="http://www.lemis.com/grog/diary-jul2024.php?subtitle=World%20network%20crash&amp;article=D-20240721-004813#D-20240721-004813">A couple of days ago</a> I engaged in guesswork about how the <a href="https://en.wikipedia.org/wiki/CrowdStrike">CrowdStrike</a> bug caused the global
  4245. system crash.  Today Ginger Wolnik posted a reference to this video on the Tandem Alumnni
  4246. mailing list:
  4247.      </p>
  4248.  
  4249.      <iframe width="400"
  4250.            height="300"
  4251.            src="http://www.youtube.com/embed/wAzEJxOo1ts"
  4252. allowfullscreen
  4253.            frameborder="0" >
  4254.     </iframe>
  4255.  
  4256.      <p>
  4257. It pretty much supports my guesswork: a kernel module had an unrecoverable error.  But the
  4258. details are interesting.  Microsoft has a bad reputation for security, but in this case it
  4259. seems that it's not to blame.  As I guessed, the CrowdStrike software includes kernel
  4260. modules.  But Microsoft tests all third-party kernel modules before giving them its seal of
  4261. approval.
  4262.      </p>
  4263.  
  4264.      <p>
  4265. So: did they slip up?  Well, sort of.  They left a loophole: modules can load data files
  4266. that aren't certified.  And these data files can contain pseudocode, and that's where the
  4267. problem occurred.
  4268.      </p>
  4269.  
  4270.      <p>
  4271. Why did CrowdStrike resort to this method?  They need to react quickly to threats, and to be
  4272. responsive they can't put every change through the certification process.  So Microsoft is
  4273. blameless.
  4274.      </p>
  4275.  
  4276.      <p>
  4277. Well, almost.  They have allowed this loophole to occur.  But potentially the same problem
  4278. could happen on just about any other platform.  And clearly CrowdStrike is to blame by
  4279. rolling out the change to everybody all at once.
  4280.      </p>
  4281.  
  4282.      <p>
  4283. The video is interesting for another reason: it has automatically generated subtitles, and
  4284. they come up with a number of amusing misinterpretations.  The problem occurs in curdle mode
  4285. because of inadequate air checking.  And anti-stress (NT stress) didn't find them
  4286.      </p>
  4287.  
  4288.      <p>
  4289. Don't like curdle?  How about colel?
  4290.      </p>
  4291.  
  4292.      <p>
  4293. And then, at 9:37 into the clip, I find entries for blackboxbsd, blackboxntfs and
  4294. blackboxpnp.  OK, NTFS I know.  Black Box I know to: it was our ill-fated police interview
  4295. project <a href="http://www.lemis.com/grog/diary-aug2006.php?topics=c#11">18 years ago</a>.  <a href="https://en.wikipedia.org/wiki/NTFS">NTFS</a> I also know.  And of course I know
  4296. <a href="https://en.wikipedia.org/wiki/BSD">BSD</a>.  But <a href="https://learn.microsoft.com/en-us/windows-hardware/drivers/debuggercmds/-blackboxbsd">blackboxbsd</a> has a completely different meaning: “Boot Status Data”.
  4297.      </p>
  4298.      </div>
  4299.    ]]>
  4300.  </description>
  4301.  <dc:creator>Greg Lehey</dc:creator>
  4302.  <dc:date>2024-07-23T00:40:29+00:00</dc:date>
  4303. </item>
  4304.  
  4305.            
  4306. <!-- topic a not selected
  4307.      <p>
  4308. <a href="http://www.lemis.com/grog/Albums/Animals/Mona.php">Mona</a> came into my office today and
  4309. promptly vomited:
  4310.      </p>
  4311.  
  4312.      
  4313.      <p>
  4314. A <a href="https://en.wikipedia.org/wiki/Hairball">hairball</a>.  I've heard of
  4315. them, but in all my time with cats this is the first that I have seen.  At 2.5 cm it looked
  4316. quite big, but it seems that they can get much bigger.
  4317.      </p>
  4318.      
  4319. End deselected topic a (A hairball) -->
  4320.  
  4321.            
  4322. <!-- topic go not selected
  4323.      <p>
  4324. It's a month after the <a href="https://en.wikipedia.org/wiki/Solstice">solstice</a>, time for the monthly <a href="http://www.lemis.com/grog/Albums/garden/Flowers-20240722.php">garden
  4325. photos</a>.
  4326.      </p>
  4327.  
  4328.      <p>
  4329. It's the middle of winter, and a month ago we had a relatively heavy frost.  That was
  4330. particularly evident on my <a href="https://en.wikipedia.org/wiki/Hibiscus_rosa-sinensis">Hibiscus rosa-sinensis</a> “Uncle Max”, which had fortunately been protected by some dead <a href="https://en.wikipedia.org/wiki/Canna_(plant)">cannas</a>.
  4331.      </p>
  4332.  
  4333.      
  4334.      <p>
  4335. But then somebody removed them, and now it looks like this:
  4336.      </p>
  4337.  
  4338.      
  4339.      <p>
  4340. Will it survive?  It has done so before.
  4341.      </p>
  4342.  
  4343.      <p>
  4344. The frost also means that there are even fewer flowers than normal for this time of year.
  4345. In particular, there are almost no roses:
  4346.      </p>
  4347.  
  4348.            
  4349.      <p>
  4350. The spring flowers are on their way:
  4351.      </p>
  4352.  
  4353.      <div align="left">
  4354.      </div>
  4355.  
  4356.      <p>
  4357. The <a href="https://en.wikipedia.org/wiki/Strelitzia_nicolai">Strelitzia nicolai</a> is already showing a bud:
  4358.      </p>
  4359.  
  4360.      
  4361.      <p>
  4362. But the <a href="https://en.wikipedia.org/wiki/Strelitzia_reginae">Strelitziae
  4363. reginae</a> that were replanted are not looking any happier:
  4364.      </p>
  4365.  
  4366.            
  4367.      <p>
  4368. The <a href="https://en.wikipedia.org/wiki/Tree_fern">tree fern</a> is also looking
  4369. unhappier than for a while, perhaps because it's being throttled by some creeper:
  4370.      </p>
  4371.  
  4372.            
  4373.      <p>
  4374. And despite all my exhortations, the weeds are winning against the gardener:
  4375.      </p>
  4376.  
  4377.      <div align="left">
  4378.      </div>
  4379.  
  4380.      <p>
  4381. Not for the first time, I wonder why I bother.
  4382.      </p>
  4383.      
  4384. End deselected topic go (Garden flowers in mid-winter) -->
  4385.  
  4386.            
  4387. <!-- topic p not selected
  4388.      <p>
  4389. I've been keeping <a href="http://www.lemis.com/grog/photography/battery-charge.php">records</a> of my
  4390. camera battery life for the best part of 15 years.  Every time a battery needs recharging, I
  4391. note the file number of the last image it took, and compare it with the one before.
  4392.      </p>
  4393.  
  4394.      <p>
  4395. But that relies on the file numbers incrementing uniformly.  What happens if the file number
  4396. changes for some reason?  That happened recently with my “new” <a href="https://en.wikipedia.org/wiki/Olympus_OM-D_E-M1">Olympus OM-D E-M1 Mark I</a>, which
  4397. was set to reset the file number to 1 every time all files were erased.  There's another
  4398. option, which I should have set, to just keep counting.  That way I can also tell how many
  4399. photos the camera has taken.
  4400.      </p>
  4401.  
  4402.      <p>
  4403. So how do I recover?  First, find what the number should be, the last 4 digits of the
  4404. shutter count.  And I can find that in the <a href="http://www.lemis.com/grog/photography/Olympus-secret-menus.php">secret menus</a>: 9916 total.  Then, using
  4405. <a href="https://en.wikipedia.org/wiki/Mtools"><i>mtools</i></a>:
  4406.      </p>
  4407.  
  4408.      <blockquote class="fullwidth">
  4409. <div style="text-align:left">
  4410.  <tt>
  4411. <code><font color="blue">=== root@hydra (/dev/pts/32)</font> <font color="red">~</font> <font color="blue">101</font> &#45;&gt; <b><tt>mcd c:dcim/100olymp</tt></b></code>
  4412. <br /><code><font color="blue">=== root@hydra (/dev/pts/32)</font> <font color="red">~</font> <font color="blue">101</font> &#45;&gt; <b><tt>mcopy c:97220057.ORF c:97229916.ORF</tt></b></code>
  4413. <br />
  4414.  </tt>
  4415. </div>
  4416. </blockquote>
  4417.  
  4418.      <p>
  4419. The <b>9</b> at the beginning of the file name is a setting I applied: this is our 9th
  4420. Olympus camera that supports renaming files, so it helps me keep the images apart.
  4421.      </p>
  4422.  
  4423.      <p>
  4424. In passing, the <a href="https://en.wikipedia.org/wiki/Olympus_OM-D_E-M1_Mark_II">Olympus OM-D E-M1 Mark II</a> now has taken 63310 photos with the shutter.
  4425.      </p>
  4426.      
  4427. End deselected topic p (Resetting photo numbers) -->
  4428.  
  4429.                  
  4430. <item>
  4431. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jul2024.php#D-20240724-015747</guid>
  4432. <link>http://www.lemis.com/grog/diary-jul2024.php?topics=c#D-20240724-015747</link>
  4433. <category>technology</category>
  4434. <category>language</category>
  4435. <category>opinion</category>
  4436. <title>Network failure out of sympathy?</title>
  4437.  <description>
  4438.    <![CDATA[
  4439.    <div align="justify">
  4440.      <p>
  4441. What does “riven” mean?  It's clearly the past participle of a strong verb, but which?  Does
  4442. it conjugate like “strive”?  Off to check the found of all wisdom, the <a href="https://www.oed.com/">OED</a>.
  4443.      </p>
  4444.  
  4445.      <p>
  4446. Are you human?  Oh, <i>no</i>.  They've added a <a href="https://en.wikipedia.org/wiki/CAPTCHA">CAPTCHA</a> to insult their users.  But after
  4447. correctly answering the CAPTCHA, I got another one.  And another one.  The thing was stuck
  4448. in a loop.  Called up the <a href="https://en.wikipedia.org/wiki/State_Library_of_Victoria">State Library of Victoria</a>, where Tom confirmed that OED had changed something, and that they (SLV) had been having
  4449. trouble, as had all other libraries, and that it wouldn't be solved today.
  4450.      </p>
  4451.  
  4452.      <p>
  4453. In the meantime I had tried logging in to the <a href="https://en.wikipedia.org/wiki/National_Library_of_Australia">National Library of
  4454. Australia</a>.  Timeout.  I could access the site, but not log in.  No hope of even
  4455. getting as far as the OED.
  4456.      </p>
  4457.  
  4458.      <p>
  4459. Back to the SLV and tried to access the <a href="https://www-macquariedictionary-com-au.ezproxy.slv.vic.gov.au/amember/signup/">Macquarie
  4460. Dictionary</a>.  No, login timeout, reported as “error code: 502”, clearly an end-user
  4461. report.  All this goes far beyond whatever OED has done.
  4462.      </p>
  4463.  
  4464.      <p>
  4465. And then the <a href="https://en.wikipedia.org/wiki/Bureau_of_Meteorology">Bureau of
  4466. Meteorology</a> got in on the act:
  4467.      </p>
  4468.  
  4469.        <a id="Photo-11" name="Photo-11"
  4470.          href="diary-jul2024.php?dirdate=20240723&amp;imagesizes=111111111112&amp;topics=c#Photo-11">
  4471.          <img alt="This should be BOM-fail-detail.jpeg.  Is it missing?" border="0" id="Photo_11"
  4472.               title="Photo BOM-fail-detail.jpeg.  Click to redisplay larger version of image."
  4473.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20240723/small/BOM-fail-detail.jpeg"
  4474.               width="203" height="334"
  4475.           /></a>
  4476.  
  4477.      <p>
  4478. No “Internet”?  Has my link gone down?  No, clearly something at the BOM.  It seems to have
  4479. lasted all day, but it was gone by the evening.
  4480.      </p>
  4481.  
  4482.      <p>
  4483. Clearly none of this can have anything to do with the <a href="https://en.wikipedia.org/wiki/2024_CrowdStrike_incident">CrowdStrike incident</a>.
  4484. Sympathy, maybe?
  4485.      </p>
  4486.      </div>
  4487.    ]]>
  4488.  </description>
  4489.  <dc:creator>Greg Lehey</dc:creator>
  4490.  <dc:date>2024-07-24T01:57:47+00:00</dc:date>
  4491. </item>
  4492.  
  4493.                  
  4494. <item>
  4495. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jul2024.php#D-20240725-021946</guid>
  4496. <link>http://www.lemis.com/grog/diary-jul2024.php?topics=c#D-20240725-021946</link>
  4497. <category>technology</category>
  4498. <category>opinion</category>
  4499. <title>New display card</title>
  4500.  <description>
  4501.    <![CDATA[
  4502.    <div align="justify">
  4503.      <p>
  4504. The display card that I ordered <a href="http://www.lemis.com/grog/diary-jul2024.php?topics=c&amp;subtitle=VirtualBox:%20enough!&amp;article=D-20240715-234840#D-20240715-234840">last week</a> is there.  For once it's not the fault of <a href="https://en.wikipedia.org/wiki/Australia_Post">Australia Post</a>: it arrived in
  4505. <a href="https://en.wikipedia.org/wiki/Napoleons,_Victoria">Napoleons</a> (sorry,
  4506. NAPOLEON) a week ago, just after <a href="http://www.lemis.com/yvonne/">Yvonne</a> did her shopping, and
  4507. since it wasn't urgent, I waited until today.
  4508.      </p>
  4509.  
  4510.      <p>
  4511. It's <i>enormous</i>!  The package measured 31×43x6.5 cm, or 8.66 l!
  4512.      </p>
  4513.  
  4514.        <a id="Photo-12" name="Photo-12"
  4515.          href="diary-jul2024.php?dirdate=20240724&amp;imagesizes=1111111111112&amp;topics=c#Photo-12">
  4516.          <img alt="This should be Display-card-1.jpeg.  Is it missing?" border="0" id="Photo_12"
  4517.               title="Photo Display-card-1.jpeg.  Click to redisplay larger version of image."
  4518.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20240724/small/Display-card-1.jpeg"
  4519.               width="302" height="223"
  4520.           /></a>
  4521.  
  4522.      <p>
  4523. But most of it was air: the real package measured 29.5×21×5.3 cm, only 3.28 l:
  4524.      </p>
  4525.  
  4526.        <a id="Photo-13" name="Photo-13"
  4527.          href="diary-jul2024.php?dirdate=20240724&amp;imagesizes=11111111111112&amp;topics=c#Photo-13">
  4528.          <img alt="This should be Display-card-2.jpeg.  Is it missing?" border="0" id="Photo_13"
  4529.               title="Photo Display-card-2.jpeg.  Click to redisplay larger version of image."
  4530.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20240724/small/Display-card-2.jpeg"
  4531.               width="302" height="223"
  4532.           /></a>
  4533.  
  4534.      <p>
  4535. That's still ridiculous.  The card itself measures 16×7×1.7 cm, or 0.19 l, only 2.2% of the
  4536. volume of the package:
  4537.      </p>
  4538.  
  4539.        <a id="Photo-14" name="Photo-14"
  4540.          href="diary-jul2024.php?dirdate=20240724&amp;imagesizes=111111111111112&amp;topics=c#Photo-14">
  4541.          <img alt="This should be Display-card-4.jpeg.  Is it missing?" border="0" id="Photo_14"
  4542.               title="Photo Display-card-4.jpeg.  Click to redisplay larger version of image."
  4543.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20240724/small/Display-card-4.jpeg"
  4544.               width="302" height="223"
  4545.           /></a>
  4546.        <a id="Photo-15" name="Photo-15"
  4547.          href="diary-jul2024.php?dirdate=20240724&amp;imagesizes=1111111111111112&amp;topics=c#Photo-15">
  4548.          <img alt="This should be Display-card-6.jpeg.  Is it missing?" border="0" id="Photo_15"
  4549.               title="Photo Display-card-6.jpeg.  Click to redisplay larger version of image."
  4550.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20240724/small/Display-card-6.jpeg"
  4551.               width="300" height="225"
  4552.           /></a>
  4553.  
  4554.      <p>
  4555. Why do people do this?  <a href="https://en.wikipedia.org/wiki/Gigabyte_Technology">Gigabyte</a> really doesn't need to make such an enormous, wasteful package.
  4556.      </p>
  4557.      </div>
  4558.    ]]>
  4559.  </description>
  4560.  <dc:creator>Greg Lehey</dc:creator>
  4561.  <dc:date>2024-07-25T02:19:46+00:00</dc:date>
  4562. </item>
  4563.  
  4564.            
  4565. <item>
  4566. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jul2024.php#D-20240725-023717</guid>
  4567. <link>http://www.lemis.com/grog/diary-jul2024.php?topics=c#D-20240725-023717</link>
  4568. <category>technology</category>
  4569. <category>opinion</category>
  4570. <title>A new monitor</title>
  4571.  <description>
  4572.    <![CDATA[
  4573.    <div align="justify">
  4574.      <p>
  4575. Finally the monitor that I ordered <a href="http://www.lemis.com/grog/diary-jul2024.php?topics=c&amp;subtitle=A%20new%20monitor&amp;article=D-20240715-001537#D-20240715-001537">last week</a>—a day before the display card—has arrived.  I paid for it on Sunday, 14
  4576. July, but it wasn't sent until the afternoon of Monday, 22 July.  And to make up for that,
  4577. it arrived today, less than 2 days after being sent, and it was delivered to my door.  Not
  4578. bad for free postage.
  4579.      </p>
  4580.  
  4581.      <p>
  4582. Now the real work starts: tidying up the monitor arrangement that once
  4583. displayed <i>eureka</i>, which has been there for over 9 years:
  4584.      </p>
  4585.  
  4586.        <a id="Photo-16" name="Photo-16"
  4587.          href="diary-jul2024.php?dirdate=20240724&amp;imagesizes=11111111111111112&amp;topics=c#Photo-16">
  4588.          <img alt="This should be Office-2.jpeg.  Is it missing?" border="0" id="Photo_16"
  4589.               title="Photo Office-2.jpeg.  Click to redisplay larger version of image."
  4590.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20240724/small/Office-2.jpeg"
  4591.               width="302" height="223"
  4592.           /></a>
  4593.        <a id="Photo-17" name="Photo-17"
  4594.          href="diary-jul2024.php?dirdate=20240724&amp;imagesizes=111111111111111112&amp;topics=c#Photo-17">
  4595.          <img alt="This should be Behind-monitors.jpeg.  Is it missing?" border="0" id="Photo_17"
  4596.               title="Photo Behind-monitors.jpeg.  Click to redisplay larger version of image."
  4597.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20240724/small/Behind-monitors.jpeg"
  4598.               width="223" height="301"
  4599.           /></a>
  4600.  
  4601.      <p>
  4602.      </p>
  4603.      </div>
  4604.    ]]>
  4605.  </description>
  4606.  <dc:creator>Greg Lehey</dc:creator>
  4607.  <dc:date>2024-07-25T02:37:17+00:00</dc:date>
  4608. </item>
  4609.  
  4610.            
  4611. <item>
  4612. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jul2024.php#D-20240725-043350</guid>
  4613. <link>http://www.lemis.com/grog/diary-jul2024.php?topics=c#D-20240725-043350</link>
  4614. <category>technology</category>
  4615. <title>Can't save Emacs buffer</title>
  4616.  <description>
  4617.    <![CDATA[
  4618.    <div align="justify">
  4619.      <p>
  4620. Writing an email today, I tried to save the buffer.  No go:
  4621.      </p>
  4622.  
  4623.      <blockquote class="fullwidth">
  4624. <div style="text-align:left">
  4625.  <tt>
  4626. select&#45;safe&#45;coding&#45;system: Loading charset map: No such file or directory, MULE&#45;uviscii
  4627.  </tt>
  4628. </div>
  4629. </blockquote>
  4630.  
  4631.      <p>
  4632. Huh?  What's that?  It seems to be related to the fact that the message contained
  4633. non-<a href="https://en.wikipedia.org/wiki/ASCII">ASCII</a> characters.  A bit of a
  4634. web search brought <a href="https://emacs.stackexchange.com/questions/71259/loading-charset-map-no-such-file-or-directory-jisx0208">this page</a> to light, which helped me work through to discover the
  4635. directory <i>/usr/local/share/emacs/30.0.50/etc/charsets/</i>.  Previously it
  4636. contained <i>MULE-uviscii.map</i>, but now it doesn't.  Clearly it relates to my recent
  4637. rebuild of <a href="https://www.gnu.org/software/emacs/"><i>Emacs</i></a>, but how?
  4638. I found an older version, and it doesn't look like something that changes frequently, so
  4639. putting it in place worked around the problem.  But what other issues are lurking in the
  4640. shadows?
  4641.      </p>
  4642.  
  4643.      <p>
  4644. Ports Collection: well over a quarter of a century of pain.
  4645.      </p>
  4646.      </div>
  4647.    ]]>
  4648.  </description>
  4649.  <dc:creator>Greg Lehey</dc:creator>
  4650.  <dc:date>2024-07-25T04:33:50+00:00</dc:date>
  4651. </item>
  4652.  
  4653.                        
  4654. <item>
  4655. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jul2024.php#D-20240725-233904</guid>
  4656. <link>http://www.lemis.com/grog/diary-jul2024.php?topics=c#D-20240725-233904</link>
  4657. <category>technology</category>
  4658. <title>Office restructure, next step</title>
  4659.  <description>
  4660.    <![CDATA[
  4661.    <div align="justify">
  4662.      <p>
  4663. Spent much of the day moving monitors around.  It shouldn't have been difficult, but there
  4664. were constraints:
  4665.      </p>
  4666.  
  4667.      <ul>
  4668.        <li class="fullwidth">
  4669.          <div class="listitemwidth">
  4670.            Remove junk accumulated round the old monitors.
  4671.          </div>
  4672.        </li>
  4673.  
  4674.        <li class="fullwidth">
  4675.          <div class="listitemwidth">
  4676.            No computer to be powered down.
  4677.          </div>
  4678.        </li>
  4679.  
  4680.        <li class="fullwidth">
  4681.          <div class="listitemwidth">
  4682.            Remove mess from behind the monitors.
  4683.          </div>
  4684.        </li>
  4685.  
  4686.        <li class="fullwidth">
  4687.          <div class="listitemwidth">
  4688.            Find cables of appropriate length and type to connect to the monitors.
  4689.          </div>
  4690.        </li>
  4691.      </ul>
  4692.  
  4693.      <p>
  4694. In the process, I found a lot of old documentation, including appointment cards dating back
  4695. as far as June 2017.  And I managed not to disconnect any cables.  Sadly, the power
  4696. connector to <i>eureka</i> was loose, so I did have to reboot it—exactly at a time where it
  4697. had no monitor connected.  But I got things done faster than expected, by midday.  Here
  4698. before and after:
  4699.      </p>
  4700.  
  4701.        <a id="Photo-18" name="Photo-18"
  4702.          href="diary-jul2024.php?dirdate=20240724&amp;imagesizes=1111111111111111112&amp;topics=c#Photo-18">
  4703.          <img alt="This should be Office-2-detail.jpeg.  Is it missing?" border="0" id="Photo_18"
  4704.               title="Photo Office-2-detail.jpeg.  Click to redisplay larger version of image."
  4705.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20240724/small/Office-2-detail.jpeg"
  4706.               width="400" height="169"
  4707.           /></a>
  4708.        <a id="Photo-19" name="Photo-19"
  4709.          href="diary-jul2024.php?dirdate=20240725&amp;imagesizes=11111111111111111112&amp;topics=c#Photo-19">
  4710.          <img alt="This should be Office-4-detail.jpeg.  Is it missing?" border="0" id="Photo_19"
  4711.               title="Photo Office-4-detail.jpeg.  Click to redisplay larger version of image."
  4712.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20240725/small/Office-4-detail.jpeg"
  4713.               width="396" height="170"
  4714.           /></a>
  4715.  
  4716.      <p>
  4717. Now to get used to being in my normal position again, after 9 months of being displaced.
  4718.      </p>
  4719.      </div>
  4720.    ]]>
  4721.  </description>
  4722.  <dc:creator>Greg Lehey</dc:creator>
  4723.  <dc:date>2024-07-25T23:39:04+00:00</dc:date>
  4724. </item>
  4725.  
  4726.      
  4727.      
  4728. <item>
  4729. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jul2024.php#D-20240726-014530</guid>
  4730. <link>http://www.lemis.com/grog/diary-jul2024.php?topics=c#D-20240726-014530</link>
  4731. <category>technology</category>
  4732. <category>history</category>
  4733. <category>opinion</category>
  4734. <title>The end of the SPARCstations</title>
  4735.  <description>
  4736.    <![CDATA[
  4737.    <div align="justify">
  4738.      <p>
  4739.  
  4740. What's constant about these photos?
  4741.      </p>
  4742.  
  4743.      <div align="left">
  4744.  <a id="Photo-20" name="Photo-20"
  4745.          href="diary-jul2024.php?dirdate=19961101&amp;imagesizes=111111111111111111112&amp;topics=c#Photo-20">
  4746.          <img alt="This should be Closeup.jpeg.  Is it missing?" border="0" id="Photo_20"
  4747.               title="Photo Closeup.jpeg.  Click to redisplay larger version of image."
  4748.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/19961101/small/Closeup.jpeg"
  4749.               width="315" height="214"
  4750.           /></a>
  4751.  <a id="Photo-21" name="Photo-21"
  4752.          href="diary-jul2024.php?dirdate=19980701&amp;imagesizes=1111111111111111111112&amp;topics=c#Photo-21">
  4753.          <img alt="This should be Greg-in-office.jpeg.  Is it missing?" border="0" id="Photo_21"
  4754.               title="Photo Greg-in-office.jpeg.  Click to redisplay larger version of image."
  4755.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/19980701/small/Greg-in-office.jpeg"
  4756.               width="300" height="225"
  4757.           /></a>
  4758.  <a id="Photo-22" name="Photo-22"
  4759.          href="diary-jul2024.php?dirdate=19991012&amp;imagesizes=11111111111111111111112&amp;topics=c#Photo-22">
  4760.          <img alt="This should be Greg-in-office.jpeg.  Is it missing?" border="0" id="Photo_22"
  4761.               title="Photo Greg-in-office.jpeg.  Click to redisplay larger version of image."
  4762.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/19991012/small/Greg-in-office.jpeg"
  4763.               width="322" height="209"
  4764.           /></a>
  4765.  <a id="Photo-23" name="Photo-23"
  4766.          href="diary-jul2024.php?dirdate=20060707&amp;imagesizes=111111111111111111111112&amp;topics=c#Photo-23">
  4767.          <img alt="This should be desktop-middle.jpeg.  Is it missing?" border="0" id="Photo_23"
  4768.               title="Photo desktop-middle.jpeg.  Click to redisplay larger version of image."
  4769.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20060707/small/desktop-middle.jpeg"
  4770.               width="300" height="225"
  4771.           /></a>
  4772.  <a id="Photo-24" name="Photo-24"
  4773.          href="diary-jul2024.php?dirdate=20180425&amp;imagesizes=1111111111111111111111112&amp;topics=c#Photo-24">
  4774.          <img alt="This should be Greg-in-office-9.jpeg.  Is it missing?" border="0" id="Photo_24"
  4775.               title="Photo Greg-in-office-9.jpeg.  Click to redisplay larger version of image."
  4776.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20180425/small/Greg-in-office-9.jpeg"
  4777.               width="388" height="174"
  4778.           /></a>
  4779.      </div>
  4780.  
  4781.      <p>
  4782. Clearly not the image quality.  Clearly not the aging person between keyboard and chair.
  4783. Also not the location, nor the displays.  Not even the keyboards, which I had to change
  4784. before the last photo.  But there is one constant: the monitors are mounted on <a href="https://en.wikipedia.org/wiki/SPARCstation">SPARCstation</a> pizzaboxes.  I had long
  4785. since stopped using them as computers, but they did very well at propping up the monitors,
  4786. and they have been doing it for round 30 years.
  4787.      </p>
  4788.  
  4789.      <p>
  4790. No more:
  4791.      </p>
  4792.  
  4793.        <a id="Photo-25" name="Photo-25"
  4794.          href="diary-jul2024.php?dirdate=20240725&amp;imagesizes=11111111111111111111111112&amp;topics=c#Photo-25">
  4795.          <img alt="This should be Office-4-detail.jpeg.  Is it missing?" border="0" id="Photo_25"
  4796.               title="Photo Office-4-detail.jpeg.  Click to redisplay larger version of image."
  4797.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20240725/small/Office-4-detail.jpeg"
  4798.               width="396" height="170"
  4799.           /></a>
  4800.  
  4801.      <p>
  4802. The new monitors have their own stands, no SPARCstation needed.  And while changing over, it
  4803. became clear how much space they had taken up.  I now have more space for appointment cards
  4804. and things under the monitors.  And things look tider from behind too.  Here before and
  4805. after:
  4806.      </p>
  4807.  
  4808.        <a id="Photo-26" name="Photo-26"
  4809.          href="diary-jul2024.php?dirdate=20240724&amp;imagesizes=111111111111111111111111112&amp;topics=c#Photo-26">
  4810.          <img alt="This should be Behind-monitors.jpeg.  Is it missing?" border="0" id="Photo_26"
  4811.               title="Photo Behind-monitors.jpeg.  Click to redisplay larger version of image."
  4812.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20240724/small/Behind-monitors.jpeg"
  4813.               width="223" height="301"
  4814.           /></a>
  4815.        <a id="Photo-27" name="Photo-27"
  4816.          href="diary-jul2024.php?dirdate=20240725&amp;imagesizes=1111111111111111111111111112&amp;topics=c#Photo-27">
  4817.          <img alt="This should be Behind-monitors.jpeg.  Is it missing?" border="0" id="Photo_27"
  4818.               title="Photo Behind-monitors.jpeg.  Click to redisplay larger version of image."
  4819.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20240725/small/Behind-monitors.jpeg"
  4820.               width="223" height="302"
  4821.           /></a>
  4822.  
  4823.      <p>
  4824. Yes,still a lot of cables, but far fewer things for the cats to throw onto the floor.
  4825.      </p>
  4826.      </div>
  4827.    ]]>
  4828.  </description>
  4829.  <dc:creator>Greg Lehey</dc:creator>
  4830.  <dc:date>2024-07-26T01:45:30+00:00</dc:date>
  4831. </item>
  4832.  
  4833.            
  4834. <!-- topic h not selected
  4835.      <p>
  4836. Into <a href="https://en.wikipedia.org/wiki/Sebastopol,_Victoria">Sebastopol</a> today for a haircut.  Originally I had planned a whole lot of things, but somehow they
  4837. either sorted themselves out, or became unimportant.  So a long drive just for that.
  4838.      </p>
  4839.      
  4840. End deselected topic h (A haircut) -->
  4841.  
  4842.            
  4843. <item>
  4844. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jul2024.php#D-20240726-020544</guid>
  4845. <link>http://www.lemis.com/grog/diary-jul2024.php?topics=c#D-20240726-020544</link>
  4846. <category>technology</category>
  4847. <category>opinion</category>
  4848. <title>X configuration, part 4723</title>
  4849.  <description>
  4850.    <![CDATA[
  4851.    <div align="justify">
  4852.      <p>
  4853. The good news about connecting up my new monitor was that it worked out of the box.  Of
  4854. course, it was connected to a running output (<i>hydra:0.2</i>) configured for 1920x1080,
  4855. but it picked that up and ran with it.
  4856.      </p>
  4857.  
  4858.      <p>
  4859. That was the good news.  I wasn't expecting the reconfiguration to be easy, and my
  4860. expectations were met.  Although I had an output on the rightmost monitor (to
  4861. become <i>hydra:0.3</i>, but currently <i>hydra:0.0</i>), the server and <a href="https://en.wikipedia.org/wiki/Nvidia">Nvidia</a> software didn't want to know about
  4862. it, thus the blue screen on that monitor:
  4863.      </p>
  4864.  
  4865.        <a id="Photo-28" name="Photo-28"
  4866.          href="diary-jul2024.php?dirdate=20240725&amp;imagesizes=11111111111111111111111111112&amp;topics=c#Photo-28">
  4867.          <img alt="This should be Office-4-detail.jpeg.  Is it missing?" border="0" id="Photo_28"
  4868.               title="Photo Office-4-detail.jpeg.  Click to redisplay larger version of image."
  4869.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20240725/small/Office-4-detail.jpeg"
  4870.               width="396" height="170"
  4871.           /></a>
  4872.  
  4873.      <p>
  4874. OK, run <i>nvidia-settings</i>.  I've been there before, and it wasn't quite as painful.
  4875. But once again I couldn't get it to position the screens correctly, and it also wouldn't
  4876. save the configuration file where I wanted it to.  Finally I saved it, but it was broken.
  4877. Despite “finding” the new monitor (“LG Electronics LG ULTRAFINE”), it included the old name
  4878. in the configuration file.  It knew about the refresh rates, though.  Here an excerpt from
  4879. the <tt>Monitor</tt> sections:
  4880.      </p>
  4881.  
  4882.      <blockquote class="fullwidth">
  4883. <div style="text-align:left">
  4884.  <tt>
  4885. Section "Monitor"
  4886. <br />&nbsp;&nbsp; &nbsp;Identifier &nbsp; &nbsp; "Monitor0"
  4887. <br />&nbsp;&nbsp; &nbsp;ModelName &nbsp; &nbsp; &nbsp;"Ancor Communications Inc VS248"
  4888. <br />&nbsp;&nbsp; &nbsp;HorizSync &nbsp; &nbsp; &nbsp; 30.0 &#45; 83.0
  4889. <br />&nbsp;&nbsp; &nbsp;VertRefresh &nbsp; &nbsp; 50.0 &#45; 76.0
  4890. <br />EndSection
  4891. <br />
  4892. <br />Section "Monitor"
  4893. <br />&nbsp;&nbsp; &nbsp;Identifier &nbsp; &nbsp; "Monitor1"
  4894. <br />&nbsp;&nbsp; &nbsp;ModelName &nbsp; &nbsp; &nbsp;"LG Electronics LG ULTRAFINE"
  4895. <br />&nbsp;&nbsp; &nbsp;HorizSync &nbsp; &nbsp; &nbsp; 30.0 &#45; 135.0
  4896. <br />&nbsp;&nbsp; &nbsp;VertRefresh &nbsp; &nbsp; 40.0 &#45; 60.0
  4897. <br />EndSection
  4898. <br />
  4899. <br />Section "Monitor"
  4900. <br />&nbsp;&nbsp; &nbsp;Identifier &nbsp; &nbsp; "Monitor2"
  4901. <br />&nbsp;&nbsp; &nbsp;ModelName &nbsp; &nbsp; &nbsp;"Ancor Communications Inc VS248"
  4902. <br />&nbsp;&nbsp; &nbsp;HorizSync &nbsp; &nbsp; &nbsp; 30.0 &#45; 135.0
  4903. <br />&nbsp;&nbsp; &nbsp;VertRefresh &nbsp; &nbsp; 40.0 &#45; 60.0
  4904. <br />
  4905.  </tt>
  4906. </div>
  4907. </blockquote>
  4908.  
  4909.      <p>
  4910. In addition, it wouldn't let me position the monitors correctly.  More playing around, and
  4911. after a while found the answer (maybe) in <a href="http://www.lemis.com/grog/diary-dec2023.php?topics=c&amp;subtitle=More%20fun%20with%20X&amp;article=D-20231214-020412#D-20231214-020412">my December diary</a>:
  4912.      </p>
  4913.  
  4914.        <a id="Photo-29" name="Photo-29"
  4915.          href="diary-jul2024.php?dirdate=20231213&amp;imagesizes=111111111111111111111111111112&amp;topics=c#Photo-29">
  4916.          <img alt="This should be nvidia-settings-2.png.  Is it missing?" border="0" id="Photo_29"
  4917.               title="Photo nvidia-settings-2.png.  Click to redisplay larger version of image."
  4918.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20231213/small/nvidia-settings-2.png"
  4919.               width="332" height="203"
  4920.           /></a>
  4921.  
  4922.      <p>
  4923. Does that work?  No, but for a different reason:
  4924.      </p>
  4925.  
  4926.      <blockquote class="fullwidth">
  4927. <div style="text-align:left">
  4928.  <tt>
  4929. <code><font color="blue">=== root@hydra (/dev/pts/32)</font> <font color="red">/usr/ports/editors/emacs&#45;devel</font> <font color="blue">120</font> &#45;&gt; <b><tt>nvidia&#45;settings</tt></b></code>
  4930. <br /><code><font color="blue">=== root@hydra (/dev/pts/32)</font> <font color="red">/usr/ports/editors/emacs&#45;devel</font> <font color="blue">121</font> &#45;&gt; <b><tt>nvidia&#45;settings</tt></b></code>
  4931. <br />nvidia&#45;settings: Fatal IO error 22 (Invalid argument) on X server hydra.lemis.com:0.0.
  4932. <br />
  4933.  </tt>
  4934. </div>
  4935. </blockquote>
  4936.  
  4937.      <p>
  4938. The first invocation worked, but when I did it the second time, some time later, it had
  4939. apparently changed something in the server, and I could no longer start the program.  It
  4940. also apparently reset the mouse bindings and the keyboard map.  It wasn't the server itself,
  4941. which has been running for well over a month:
  4942.      </p>
  4943.  
  4944.      <blockquote class="fullwidth">
  4945. <div style="text-align:left">
  4946.  <tt>
  4947. USER &nbsp;PID %CPU %MEM &nbsp; &nbsp; &nbsp;VSZ &nbsp; &nbsp;RSS TT &nbsp;STAT STARTED &nbsp; &nbsp; &nbsp; TIME COMMAND
  4948. <br />root 2307 &nbsp;0.0 &nbsp;0.1 25948804 226184 v0 &nbsp;S &nbsp; &nbsp;15Jun24 4710:04.67 /usr/local/libexec/Xorg :0 &#45;config xorg&#45;0.conf &#45;logverbose 6 &#45;listen tcp &#45;auth /home/grog
  4949. <br />
  4950.  </tt>
  4951. </div>
  4952. </blockquote>
  4953.  
  4954.      <p>
  4955. So: frob the configuration file manually and check as server 4.
  4956.      </p>
  4957.      </div>
  4958.    ]]>
  4959.  </description>
  4960.  <dc:creator>Greg Lehey</dc:creator>
  4961.  <dc:date>2024-07-26T02:05:44+00:00</dc:date>
  4962. </item>
  4963.  
  4964.            
  4965. <item>
  4966. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jul2024.php#D-20240726-023449</guid>
  4967. <link>http://www.lemis.com/grog/diary-jul2024.php?topics=c#D-20240726-023449</link>
  4968. <category>technology</category>
  4969. <category>general</category>
  4970. <category>opinion</category>
  4971. <title>An offer you can't refuse</title>
  4972.  <description>
  4973.    <![CDATA[
  4974.    <div align="justify">
  4975.      <p>
  4976. Seen on the <a href="https://en.wikipedia.org/wiki/The_Courier_(Ballarat)">Ballarat
  4977. Courier</a> today:
  4978.      </p>
  4979.  
  4980.      <blockquote class="fullwidth">
  4981. <div style="text-align:left">
  4982.  <tt>
  4983. Login or signup to continue reading $0/
  4984. <br />$<a href="https://en.wikipedia.org/wiki/NaN">NaN</a>/year
  4985. <br />All articles from our website &amp; app
  4986. <br />
  4987.  </tt>
  4988. </div>
  4989. </blockquote>
  4990.  
  4991.      <p>
  4992. Who can refuse that?
  4993.      </p>
  4994.      </div>
  4995.    ]]>
  4996.  </description>
  4997.  <dc:creator>Greg Lehey</dc:creator>
  4998.  <dc:date>2024-07-26T02:34:49+00:00</dc:date>
  4999. </item>
  5000.  
  5001.      </channel>
  5002. </rss>
  5003.  

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid RSS" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=http%3A//www.lemis.com/grog/diary.xml.php%3Ftopics%3Dc

Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda