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>2025-06-30T15:52:51+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 kHo not selected
  20.      <p>
  21. I seem to be spending half my time in the kitchen lately, though <a href="http://www.lemis.com/yvonne/">Yvonne</a> did nearly all the cooking this weekend.  But I had lots of things to cook and
  22. freeze, including <a href="http://www.lemis.com/grog/recipes/frijoles.php"><i>frijoles de la olla</i></a> and
  23. <a href="http://www.lemis.com/grog/recipes/salsa-pomodori.php"><i>salsa di pomodori</i></a>, and also some
  24. chicken thighs to cook for breakfast.
  25.      </p>
  26.  
  27.      <p>
  28. I cooked the chicken thighs in an old pot, which chose today to lose the grip for the lid:
  29.      </p>
  30.  
  31.      <div align="left">
  32.      </div>
  33.  
  34.      <p>
  35. Not to worry.  It has served me well, and we can pick up something similar for almost
  36. nothing at the <a href="https://en.wikipedia.org/wiki/Op_shop">op shop</a>.  But
  37. then I wondered.  How long have I had it.  Yvonne agreed that I probably already had it when
  38. we met <a href="http://www.lemis.com/grog/diary-jul1982.php?topics=c#25">43 years ago</a>.  Did I buy it round the same time as
  39. this chopping board?
  40.      </p>
  41.  
  42.      
  43.      <p>
  44. I have guessed that I bought that when I got my first flat in Germany, <a href="http://www.lemis.com/grog/diary-may1973.php?topics=c#15">52 years ago</a>.  Did I get the pot at the same time?  The only photo I
  45. have that could give a clue is this, which I must have taken in early 1978:
  46.      </p>
  47.  
  48.            
  49.      <p>
  50. In passing, admire the vignetting and the distortion at the edges.  This must have been
  51. taken with my 18 mm Sigma ultra-wide-angle lens.  But it's no wider than my <a href="https://www.dpreview.com/reviews/olympus-9-18-4-5p6-o20">Zuiko Digital 9-18 mm</a> lens, which is much sharper at the edges.
  52.      </p>
  53.  
  54.      <p>
  55. Yes, the chopping board is there, but the pot isn't, only another one that I still have,
  56. currently also in use:
  57.      </p>
  58.  
  59.            
  60.      <p>
  61. Still, I suspect that I have had the other one longer.
  62.      </p>
  63.  
  64.      <p>
  65. And then, of course, the question: how do I lift the lid of the pot when it's hot?  An even
  66. older item of “kitchenware” to the rescue:
  67.      </p>
  68.  
  69.      
  70.      <p>
  71. My guess is that I got them in 1962.
  72.      </p>
  73.      
  74. End deselected topic kHo (Another day in the kitchen) -->
  75.  
  76.            
  77. <!-- topic klo not selected
  78.      <p>
  79. I've tried a different kind of fish ball—I thought.
  80.      </p>
  81.  
  82.      
  83.      <p>
  84. When I bit into them, there was a black content, possibly roe.  <a href="https://en.wikipedia.org/wiki/Google_Translate">Google Translate</a> to the rescue?
  85. Yes: they're crocodile balls.
  86.      </p>
  87.  
  88.      <p>
  89. Really?  No, just guessing.  It tried again and came up with “eel balls”, which matches the
  90. content list on the back of the packaging:
  91.      </p>
  92.  
  93.      
  94.      <p>
  95. Google Translate would be much more useful if it didn't try to guess.
  96.      </p>
  97.      
  98. End deselected topic klo (What are those balls?) -->
  99.  
  100.            
  101. <!-- topic kGo not selected
  102.      <p>
  103. More potato slices for dinner today—the only contribution I had made.  After my fun with the
  104. new <a href="https://en.wikipedia.org/wiki/Mandoline">mandolin</a> <a href="http://www.lemis.com/grog/diary-mar2025.php?subtitle=How%20not%20to%20slice%20potatoes&amp;article=D-20250331-000434#D-20250331-000434">in March</a>, held a particularly reticent potato with a pot holder.
  105.      </p>
  106.  
  107.      <p>
  108. Also not a good idea:
  109.      </p>
  110.  
  111.      
  112.      <p>
  113. <a href="http://www.lemis.com/yvonne/">Yvonne</a> was particularly upset, since it's one of her
  114. favourites (hint: has a horse on it).
  115.      </p>
  116.      
  117. End deselected topic kGo (Another mandolin injury) -->
  118.  
  119.                  
  120. <item>
  121. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-may2025.php#D-20250527-025133</guid>
  122. <link>http://www.lemis.com/grog/diary-may2025.php?topics=c#D-20250527-025133</link>
  123. <category>technology</category>
  124. <category>opinion</category>
  125. <title>Still more web server overload</title>
  126.  <description>
  127.    <![CDATA[
  128.    <div align="justify">
  129.      <p>
  130. Somehow the web server problems haven't gone away, at least not for long.  I've been
  131. planning to find ways to identify the culprits and limit their access.
  132.      </p>
  133.  
  134.      <p>
  135. Various suggestions on IRC.  Jamie Fraser came up with the issue of <a href="https://en.wikipedia.org/wiki/.htaccess">.htaccess</a>.  Not an issue: I don't use it.
  136.      </p>
  137.  
  138.      <p>
  139. Oh:
  140.      </p>
  141.  
  142.      <blockquote class="fullwidth">
  143. <div style="text-align:left">
  144.  <tt>
  145. <code><font color="blue">=== root@lax (/dev/pts/0)</font> <font color="red">/var/log/www</font> <font color="blue">50</font> &#45;&gt; <b><tt>find ~grog/www.lemis.com &#45;name ".htaccess"</tt></b></code>
  146. <br />/home/grog/www.lemis.com/grog/Day/20211118/.htaccess
  147. <br />/home/grog/www.lemis.com/grog/Documentation/PUS/.htaccess
  148. <br />/home/grog/www.lemis.com/grog/Photos/19730801/.htaccess
  149. <br />/home/grog/www.lemis.com/grog/Photos/20080325/.htaccess
  150. <br />/home/grog/www.lemis.com/grog/webserver/.htaccess
  151. <br />/home/grog/www.lemis.com/grog/AUUG&#45;copy/exec/.htaccess
  152. <br />/home/grog/www.lemis.com/myth/data/.htaccess
  153. <br />/home/grog/www.lemis.com/myth/.htaccess
  154. <br />
  155.  </tt>
  156. </div>
  157. </blockquote>
  158.  
  159.      <p>
  160. What's all that stuff?  Some of them were 18 years old.  Clearly not needed, so I removed
  161. them all.  But that's not enough, it seems: the web server still needs to check for its
  162. presence, all the way up to the top of the tree.  So change this:
  163.      </p>
  164.  
  165.      <blockquote class="fullwidth">
  166. <div style="text-align:left">
  167.  <tt>
  168. &#45;&#45;&#45; /usr/local/etc/apache24/Includes/www.lemis.com.conf 2025/05/24 02:00:35 &nbsp; &nbsp; 1.10
  169. <br />+++ /usr/local/etc/apache24/Includes/www.lemis.com.conf 2025/05/26 03:52:16
  170. <br />@@ &#45;40,7 +40,6 @@
  171. <br />&nbsp;&lt;Directory /home/grog/www.lemis.com&gt;
  172. <br />&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; Options All MultiViews
  173. <br />&#45; &nbsp; &nbsp; &nbsp; &nbsp;AllowOverride All
  174. <br />+ &nbsp; &nbsp; &nbsp; &nbsp;AllowOverride None
  175. <br />
  176.  </tt>
  177. </div>
  178. </blockquote>
  179.  
  180.      <p>
  181. And how about that, the server load went down, from 15 to 7.  But it didn't stay that way:
  182. soon after it went up to 195.  While the idea is good, any performance improvement is a drop
  183. in the ocean compared to the overloading I'm seeing.
  184.      </p>
  185.  
  186.      <p>
  187. Then Daniel O'Connor came up with a whole lot of rewrites:
  188.      </p>
  189.  
  190.      <blockquote class="fullwidth">
  191. <div style="text-align:left">
  192.  <tt>
  193. &#45;&#45;&#45; /usr/local/etc/apache24/Includes/www.lemis.com.conf 2025/05/26 03:53:00 &nbsp; &nbsp; 1.12
  194. <br />+++ /usr/local/etc/apache24/Includes/www.lemis.com.conf 2025/05/26 05:08:33
  195. <br />@@ &#45;24,12 +24,1424 @@
  196. <br />+ &nbsp; &nbsp;Satisfy Any
  197. <br />+ &nbsp; &nbsp;Allow from all
  198. <br />&nbsp;&nbsp; &nbsp; Options &#45;Indexes
  199. <br /># Ichido AI Bot Blocker.
  200. <br />+ &nbsp; &nbsp;RewriteEngine on
  201. <br />+ &nbsp; &nbsp;RewriteCond %{HTTP_USER_AGENT} ^.*007ac9\ Crawler.*$
  202. <br />+ &nbsp; &nbsp;RewriteRule . &#45; [R=403,L]
  203. <br />+ &nbsp; &nbsp;RewriteCond %{HTTP_USER_AGENT} ^.*008.*$
  204. <br />...
  205.  </tt>
  206. </div>
  207. </blockquote>
  208.  
  209.      <p>
  210. All in all, it increased the file size from 55 to 1451 lines.  Somehow that seems too
  211. repetitive.  More to the point, though, it doesn't seem to do much.  From my dozens of hits
  212. per second it only rejected about 10 a minute.  So I'm still left with this periodic
  213. overload.
  214.      </p>
  215.      </div>
  216.    ]]>
  217.  </description>
  218.  <dc:creator>Greg Lehey</dc:creator>
  219.  <dc:date>2025-05-27T02:51:33+00:00</dc:date>
  220. </item>
  221.  
  222.            
  223. <!-- topic ho not selected
  224.      <p>
  225. While walking the dogs, a car came up and asked about the location.  It seems that he (Brad)
  226. was considering moving from <a href="https://en.wikipedia.org/wiki/Inverleigh,_Victoria">Inverleigh</a> to <a href="https://en.wikipedia.org/wiki/Dereel">Dereel</a>.
  227.      </p>
  228.  
  229.      <p>
  230. Why?  I had always thought Inverleigh to be a nice place to live.  Yes, but it's expensive.
  231. He could sell his house in Inverleigh, move here and be debt free.  The place he is looking
  232. at is in Rozenstein Road, 500 m due west of our property.  It's covered in trees, and
  233. they're asking $175,000 to $190,000 for it.  We paid $85,000 for ours <a href="http://www.lemis.com/grog/diary-nov2013.php?subtitle=More%20land%20stuff&amp;article=D-20131129-233549#D-20131129-233549">11½ years ago</a>, and it was clear for the most part.  How the prices have gone up!
  234.      </p>
  235.      
  236. End deselected topic ho (Moving to Dereel) -->
  237.  
  238.            
  239. <!-- topic go not selected
  240.      <p>
  241. <a href="http://www.lemis.com/yvonne/">Yvonne</a> has had the idea of planting trees in the “north
  242. paddock”, the part of our property to the north-west of the garden.  Not a bad idea, but she
  243. wanted to transplant established native trees, preferably an <a href="https://en.wikipedia.org/wiki/Allocasuarina">Allocasuarina</a>.
  244.      </p>
  245.  
  246.      <p>
  247. That doesn't sound optimal.  They don't grow very fast, they want a bit of shade, and they
  248. probably wouldn't survive transplantation.  How about an <a href="https://en.wikipedia.org/wiki/Acacia_melanoxylon">Acacia melanoxylon</a> (“blackwood”), which grow like fury.  Here a volunteer that grew too close to the house and
  249. which we had to remove.  The photos were taken on <a href="http://www.lemis.com/grog/diary-jul2018.php?topics=c#14">14 July 2018</a> and
  250. <a href="http://www.lemis.com/grog/diary-apr2024.php?topics=c#13">13 April 2024</a>, less than 6 years apart:
  251.      </p>
  252.  
  253.            
  254.      <p>
  255. We were walking the dogs at the time, so we considered the saplings growing along the side
  256. of the road.  Acacia melanoxylon, <a href="https://en.wikipedia.org/wiki/Acacia_myrtifolia">Acacia myrtifolia</a>—and this one,
  257. that I can't identify:
  258.      </p>
  259.  
  260.      
  261.      <p>
  262. It's clearly an Acacia, but what kind?  I recall some particularly fragrant one that I had
  263. seen a while back.  How big do they get?
  264.      </p>
  265.      
  266. End deselected topic go (What's that acacia?) -->
  267.  
  268.                  
  269. <item>
  270. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-may2025.php#D-20250528-022358</guid>
  271. <link>http://www.lemis.com/grog/diary-may2025.php?topics=c#D-20250528-022358</link>
  272. <category>technology</category>
  273. <category>opinion</category>
  274. <title>More web server investigations</title>
  275.  <description>
  276.    <![CDATA[
  277.    <div align="justify">
  278.      <p>
  279. The <a href="https://en.wikipedia.org/wiki/Apache_(web_server)">Apache (web server)</a> rules that Daniel O'Connor gave me included the comment “# Ichido AI Bot Blocker”.  That
  280. sounded like something to look up, and I ended up at <a href="https://datadome.co/">https://datadome.co/</a> (note that missing <b>g</b>).  I had to sign up, so I tried that.  Got the usual
  281. “please verify your email address” message.  Click.  “Can't resolve <a href="https://cf-app.datadome.co">cf-app.datadome.co</a>.
  282.      </p>
  283.  
  284.      <p>
  285. I've never seen that before on a serious web site.  Maybe I haven't now.  It stayed like
  286. that for several hours, and then I got:
  287.      </p>
  288.  
  289.      <blockquote class="fullwidth">
  290. <div style="text-align:left">
  291.  <tt>
  292. You have been blocked.
  293. <br />Why this blocking? Something about the behaviour of the browser has caught our attention.
  294. <br />
  295. <br />There are various possible explanations for this:
  296. <br />
  297. <br />&nbsp;&nbsp; &nbsp;&#45; you are browsing and clicking at a speed much faster than expected of a human being
  298. <br />&nbsp;&nbsp; &nbsp;&#45; something is preventing Javascript from working on your computer
  299. <br />&nbsp;&nbsp; &nbsp;&#45; there is a robot on the same network (IP 121.200.11.253) as you
  300. <br />
  301.  </tt>
  302. </div>
  303. </blockquote>
  304.  
  305.      <p>
  306. OK, DataDome, you've shown your ability.  Goodbye.
  307.      </p>
  308.      </div>
  309.    ]]>
  310.  </description>
  311.  <dc:creator>Greg Lehey</dc:creator>
  312.  <dc:date>2025-05-28T02:23:58+00:00</dc:date>
  313. </item>
  314.  
  315.            
  316. <!-- topic th not selected
  317.      <p>
  318. We're gradually moving our finances to <a href="https://en.wikipedia.org/wiki/Bank_Australia">Bank Australia</a>, a bank with the
  319. interesting property that it's really just the function (Bank) and country (Australia).  I
  320. don't know many like that.
  321.      </p>
  322.  
  323.      <p>
  324. But then this evening we watched <a href="https://www.imdb.com/title/tt0621625">an
  325. episode</a> of <a href="https://en.wikipedia.org/wiki/Inspector_Rex">Köter Rex</a>.  A bank robbery?  Here?
  326.      </p>
  327.  
  328.      
  329.      <p>
  330. That was first broadcast on 19 April 2000.  Did it maybe give Bank Australia the idea of the
  331. name?
  332.      </p>
  333.      
  334. End deselected topic th (Bank Austria?) -->
  335.  
  336.                  
  337. <item>
  338. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-may2025.php#D-20250529-021130</guid>
  339. <link>http://www.lemis.com/grog/diary-may2025.php?topics=c#D-20250529-021130</link>
  340. <category>technology</category>
  341. <category>general</category>
  342. <category>opinion</category>
  343. <title>New weather station</title>
  344.  <description>
  345.    <![CDATA[
  346.    <div align="justify">
  347.      <p>
  348. The <a href="https://www.bigw.com.au/product/tesa-ws1081-solar-powered-touch-panel-weather-center-with-pc-interface/p/9900026687">Tesa WS1081 Solar Powered Touch Panel Weather Center with PC interface</a> that I ordered
  349. <a href="http://www.lemis.com/grog/diary-may2025.php?topics=c&amp;subtitle=A%20new%20weather%20station?&amp;article=D-20250519-020936#D-20250519-020936">last week</a> as a replacement for my flaky <a href="http://www.lemis.com/grog/programs/WH1080.php">Fine Offset WH-1081</a> has arrived, not a moment too soon: last night I had lost
  350. communication between the inside and outside units for 14 hours.
  351.      </p>
  352.  
  353.      <p>
  354. It was back now, but before assembling the whole thing, it would be interesting to see if
  355. the inside unit is compatible, both with the computer and with the outside unit.  The first
  356. inspection looked less than good.  Here the rear of both inside units, the old one on the
  357. left:
  358.      </p>
  359.  
  360.        <a id="Photo-0" name="Photo-0"
  361.          href="diary-may2025.php?dirdate=20250529&amp;imagesizes=2&amp;topics=c&amp;edit=0#Photo-0">
  362.          <img alt="This should be WS1081-Weather-station-rear-2-detail.jpeg.  Is it missing?" border="0" id="Photo_0"
  363.               title="Photo WS1081-Weather-station-rear-2-detail.jpeg.  Click to redisplay larger version of image."
  364.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250529/small/WS1081-Weather-station-rear-2-detail.jpeg"
  365.               width="408" height="166"
  366.           /></a>
  367.        <a id="Photo-1" name="Photo-1"
  368.          href="diary-may2025.php?dirdate=20250529&amp;imagesizes=12&amp;topics=c&amp;edit=0#Photo-1">
  369.          <img alt="This should be WS1081-Weather-station-rear-1-detail.jpeg.  Is it missing?" border="0" id="Photo_1"
  370.               title="Photo WS1081-Weather-station-rear-1-detail.jpeg.  Click to redisplay larger version of image."
  371.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250529/small/WS1081-Weather-station-rear-1-detail.jpeg"
  372.               width="402" height="168"
  373.           /></a>
  374.  
  375.      <p>
  376. Different frequencies!  Still, it's worth seeing if the new unit can communicate with my
  377. software.  Yes.  And how about that, it can communicate with the outside unit as well,
  378. despite the 900 kHz difference in frequency.  Clearly it's just too polite to go into
  379. excessive detail about the frequency.
  380.      </p>
  381.  
  382.      <p>
  383. And of course there's another detail that I hadn't noticed: the model number is the same,
  384. WS1081.  I had assumed that my old one was a WH-1081, and I hadn't noticed that the number
  385. is the same.  OK, let's leave it like that for the while to see whether the fault with the
  386. old unit is with the inside unit (in which case the outside unit would still communicate
  387. with the new inside unit) or with the outside unit (in which case both inside units would
  388. fail).
  389.      </p>
  390.      </div>
  391.    ]]>
  392.  </description>
  393.  <dc:creator>Greg Lehey</dc:creator>
  394.  <dc:date>2025-05-29T02:11:30+00:00</dc:date>
  395. </item>
  396.  
  397.                  
  398. <item>
  399. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-may2025.php#D-20250530-013002</guid>
  400. <link>http://www.lemis.com/grog/diary-may2025.php?topics=c#D-20250530-013002</link>
  401. <category>technology</category>
  402. <category>general</category>
  403. <category>opinion</category>
  404. <title>Renewed weather station pain</title>
  405.  <description>
  406.    <![CDATA[
  407.    <div align="justify">
  408.      <p>
  409. Overnight the weather station(s) had a communication dropout again.  Both were affected, so
  410. it must have been the outside station.
  411.      </p>
  412.  
  413.      <p>
  414. That's not important: it's slated for removal anyway.  Now to install the new one.
  415.      </p>
  416.  
  417.      <p>
  418. It wasn't easy.  In fact, I gave up:
  419.      </p>
  420.  
  421.      <ul>
  422.        <li class="fullwidth">
  423.          <p class="listitemwidth">
  424.            The new station came without a mounting pole.  OK, use the existing one.  Sorry, no can
  425.            do: the mounting brackets are too big, and they can't be adjusted to the existing pole.
  426.            So to mount it at all I first need to buy a new pole.
  427.          </p>
  428.        </li>
  429.  
  430.        <li class="fullwidth">
  431.          <p class="listitemwidth">
  432.            The other end of the mount makes no sense to me.  The mounting bracket has no holes to
  433.            mount on the station, and the moulding on the underside doesn't match anything:
  434.          </p>
  435.  
  436.    <a id="Photo-2" name="Photo-2"
  437.          href="diary-may2025.php?dirdate=20250530&amp;imagesizes=112&amp;topics=c&amp;edit=0#Photo-2">
  438.          <img alt="This should be WS1081-weather-station-1.jpeg.  Is it missing?" border="0" id="Photo_2"
  439.               title="Photo WS1081-weather-station-1.jpeg.  Click to redisplay larger version of image."
  440.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250530/small/WS1081-weather-station-1.jpeg"
  441.               width="304" height="221"
  442.           /></a>
  443.  
  444.  <p class="listitemwidth">
  445.    My best guess is that the moulding is irrelevant, and that the bracket is a clamp fit to
  446.    the underside, roughly as shown here:
  447.  </p>
  448.  
  449.    <a id="Photo-3" name="Photo-3"
  450.          href="diary-may2025.php?dirdate=20250530&amp;imagesizes=1112&amp;topics=c&amp;edit=0#Photo-3">
  451.          <img alt="This should be WS1081-weather-station-4.jpeg.  Is it missing?" border="0" id="Photo_3"
  452.               title="Photo WS1081-weather-station-4.jpeg.  Click to redisplay larger version of image."
  453.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250530/small/WS1081-weather-station-4.jpeg"
  454.               width="363" height="186"
  455.           /></a>
  456.  
  457.  <p class="listitemwidth">
  458.    So if the bracket isn't tightened with enough, a strong wind can blow the whole thing
  459.    away.  If it's tightened too much, it will damage the underside of the unit beyond
  460.    repair.
  461.  </p>
  462.        </li>
  463.  
  464.        <li class="fullwidth">
  465.          <p class="listitemwidth">
  466.            According to the instructions, and contrary to a video I have seen, the unit does not
  467.            recharge batteries.  It doesn't even accept rechargeable batteries.  That's a strong
  468.            regression from the last unit, which does have rechargeable batteries and recharges
  469.            them.  It's not clear if the instructions are correct; the unit <i>does</i> have a solar
  470.            panel, presumably at least also to measure <a href="https://en.wikipedia.org/wiki/Insolation">insolation</a>, so it would be able to
  471.            recharge the batteries.
  472.          </p>
  473.  
  474.  <p class="listitemwidth">
  475.    To make up for this deficiency, they have made it very difficult to change the
  476.    batteries.  They're mounted under a screw-in cover on the underside of the unit:
  477.  </p>
  478.  
  479.    <a id="Photo-4" name="Photo-4"
  480.          href="diary-may2025.php?dirdate=20250530&amp;imagesizes=11112&amp;topics=c&amp;edit=0#Photo-4">
  481.          <img alt="This should be Weather-station-1.jpeg.  Is it missing?" border="0" id="Photo_4"
  482.               title="Photo Weather-station-1.jpeg.  Click to redisplay larger version of image."
  483.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250530/small/Weather-station-1.jpeg"
  484.               width="311" height="217"
  485.           /></a>
  486.    <a id="Photo-5" name="Photo-5"
  487.          href="diary-may2025.php?dirdate=20250530&amp;imagesizes=111112&amp;topics=c&amp;edit=0#Photo-5">
  488.          <img alt="This should be WS1081-weather-station-3-detail.jpeg.  Is it missing?" border="0" id="Photo_5"
  489.               title="Photo WS1081-weather-station-3-detail.jpeg.  Click to redisplay larger version of image."
  490.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250530/small/WS1081-weather-station-3-detail.jpeg"
  491.               width="240" height="280"
  492.           /></a>
  493.  
  494.  <p class="listitemwidth">
  495.    To be clear: this shows the unit upside-down, which will not be the case when the unit
  496.    has been mounted and just needs the batteries changed.  You need to climb up on a ladder
  497.    with a screwdriver and hope that they don't fall out.
  498.  </p>
  499.  
  500.  <p class="listitemwidth">
  501.    By coincidence, this also shows the mounting brackets and confirms my guess about the
  502.    way the unit is attached.
  503.  </p>
  504.        </li>
  505.  
  506.        <li class="fullwidth">
  507.          <p class="listitemwidth">
  508.            The instructions also clarify the lie about the range of the unit.  The <a href="https://www.lacrossetechnology.au/products/ws1081-ver3-tesa-solar-powered-touch-panel-weather-center-with-pc-interface">specifications</a> state “Transmission range up to 100m”.  But that's the best case,
  509.            of course.  The instructions are too polite to use international measurements, but state
  510.            that the absolute best case is 300 ft (90 m).  “Typically you will get 100 feet <i>[30
  511.            m]</i> maximum”.  They also state that the device is particularly sensitive to
  512.            <a href="https://en.wikipedia.org/wiki/Electromagnetic_interference">EMI</a> and
  513.            <a href="https://en.wikipedia.org/w/index.php?title=Radio-frequency_interference">RFI</a>, which they consider to be two different things.
  514.          </p>
  515.        </li>
  516.      </ul>
  517.  
  518.      <p>
  519. That's a large number of issues and regressions, but ultimately it was this last point that
  520. is the issue.  I put the batteries in the unit (the old one was conveniently
  521. non-communicative), and the inside units recognized the signal immediately.  They were
  522. showing too high a temperature, since the outside unit was still inside.  So I put it
  523. outside on the verandah table:
  524.      </p>
  525.  
  526.        <a id="Photo-6" name="Photo-6"
  527.          href="diary-may2025.php?dirdate=20250530&amp;imagesizes=1111112&amp;topics=c&amp;edit=0#Photo-6">
  528.          <img alt="This should be WS1081-weather-station-5.jpeg.  Is it missing?" border="0" id="Photo_6"
  529.               title="Photo WS1081-weather-station-5.jpeg.  Click to redisplay larger version of image."
  530.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250530/small/WS1081-weather-station-5.jpeg"
  531.               width="319" height="211"
  532.           /></a>
  533. a
  534.      <p>
  535. That's about 10 m away, line of sight through the window.  And it took something like 20
  536. minutes for the unit to register the change in temperature.
  537.      </p>
  538.  
  539.      <p>
  540. My guess is that the firmware in the inside station is tuned to this unreliability and will
  541. only give up on a temperature display if a considerable period (30 minutes?) elapses with no
  542. update.  But that's not good enough.  Back it goes.
  543.      </p>
  544.  
  545.      <p>
  546.  
  547. So what do I do?  How about a <a href="https://en.wikipedia.org/wiki/Wi-Fi">Wi-Fi</a> unit?  Out to measure the Wi-Fi strength outside.  Not good, but present, and my phone
  548. managed to connect to the Internet.  So it looks like that's what I should get.
  549.      </p>
  550.  
  551.      <p>
  552. But which one?  That's a whole new can of worms.  The only reason I bought the WS1081 was in
  553. the (fulfilled) hope that it would work with my existing software along with the
  554. (unfulfilled) hope that they would have become more reliable in the last 15 years.  A Wi-Fi
  555. unit will at the very least require adaptation of the link level.  How hard can it be?
  556.      </p>
  557.  
  558.      <p>
  559. Another question for <a href="https://en.wikipedia.org/wiki/Google_Gemini">Google
  560. Gemini</a>, bringing <a href="http://www.lemis.com/grog/weather/notes.php">a lot of information</a> that I still need to digest.  One of the most interesting things was:
  561.      </p>
  562.  
  563.      <ul>
  564.        <li class="fullwidth">
  565.          <div class="listitemwidth">
  566.            Local API Access (for advanced users): While not for everyone, some stations (like
  567.            WeatherFlow Tempest or Davis WeatherLink Live) offer local APIs that allow direct access
  568.            to real-time data on your local network, offering maximum flexibility for tech-savvy
  569.            users.
  570.          </div>
  571.        </li>
  572.      </ul>
  573.  
  574.      <p>
  575. That sounds interesting.  Looking further, I found <a href="https://weatherlink.github.io/weatherlink-live-local-api/">this page</a> showing that
  576. I can access at least the Davis units with normal <a href="https://en.wikipedia.org/wiki/HTTP">HTTP</a>.  But what do the things cost?  I can see
  577. myself paying double what I have done.  And there's a lot of investigation as well.
  578.      </p>
  579.      </div>
  580.    ]]>
  581.  </description>
  582.  <dc:creator>Greg Lehey</dc:creator>
  583.  <dc:date>2025-05-30T01:30:02+00:00</dc:date>
  584. </item>
  585.  
  586.                  
  587. <item>
  588. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-may2025.php#D-20250531-040201</guid>
  589. <link>http://www.lemis.com/grog/diary-may2025.php?topics=c#D-20250531-040201</link>
  590. <category>technology</category>
  591. <category>general</category>
  592. <category>opinion</category>
  593. <title>Still more weather station pain</title>
  594.  <description>
  595.    <![CDATA[
  596.    <div align="justify">
  597.      <p>
  598. I had pretty much given up on the new weather station, but it's good to sleep over these
  599. things.  With the new station just outside the lounge room door, there were no more
  600. noticeable outages, though theoretically I should have checked how many retries I needed to
  601. get a reading.  What I did see, with both indoor units, was lots of:
  602.      </p>
  603.  
  604.      <blockquote class="fullwidth">
  605. <div style="text-align:left">
  606.  <tt>
  607. May 30 04:53:11 tiwi wh1080[55533]: Can't read device: Input/output error or Unknown error (5)
  608. <br />
  609.  </tt>
  610. </div>
  611. </blockquote>
  612.  
  613.      <p>
  614. I'm not sure that that's the fault of the devices; I've had them for years, and it could be
  615. a program bug, either in my program or in the <a href="https://en.wikipedia.org/wiki/USB">USB</a> stack.
  616.      </p>
  617.  
  618.      <p>
  619. What I did do was to take each of the indoor device in turn into my office.  Neither could
  620. communicate with the outdoor unit only 15 m away.  So I need a new weather station.  Dammit,
  621. I can afford something more expensive, just as long as it does what I want.
  622.      </p>
  623.  
  624.      <p>
  625. Off looking, and came up with an amazing number of contradictions and lack of information.
  626. A Google search for <a href="https://www.google.com/search?q=best%2bdomestic%2bweather%2bstation%2baustralia">best domestic
  627. weather station australia</a> came up with <a href="https://www.thespruce.com/best-home-weather-stations-5497436">After Testing 18 Home
  628. Weather Stations, Here Are The Best We Recommend</a>.  The “Best Overall” was the
  629. “WeatherFlow Tempest Weather System at Amazon | $349”.  Yes, that's how they describe it.
  630. And that's one of the two makes that <a href="https://en.wikipedia.org/wiki/Google_Gemini">Google Gemini</a> had flagged for good
  631. software interface.  OK, Amazon, <a href="https://www.amazon.com.au/Tempest-Weather-Accurate-Forecasts-Wireless/dp/B0868WY7NY">more details please</a>.  $814.73!  That's a funny way to write $349.  Ah, you want to
  632. pay in <i>Australian</i> dollars, and clearly the exchange rate is $0.428 (in fact, it's
  633. currently $0.643).  But not to worry:
  634.      </p>
  635.  
  636.      <blockquote class="fullwidth">
  637.        <div class="listitemwidth">
  638.  <span style="color:red">
  639.    Sorry, your selected delivery location is beyond seller's shipping coverage for this
  640.    item. Please choose a different delivery location or purchase from another seller
  641.  </span>
  642.        </div>
  643.      </blockquote>
  644.  
  645.      <p>
  646. In fact, it seems that WeatherFlow isn't represented at all in Australia.  Given the pain
  647. I've had, I think that's a reason to avoid them.
  648.      </p>
  649.  
  650.      <p>
  651. Then there's <a href="https://www.techgearlab.com/topics/electronics/best-weather-station">The 6 Best Weather
  652. Stations of 2025</a> from <a href="https://www.techgearlab.com/">Techgear</a>.  It
  653. looked good: the editor's choice was two from <a href="https://www.ambientweather.com/">Ambient weather</a>, the other maker recommended by Gemini:
  654.      </p>
  655.  
  656.        <a id="Photo-7" name="Photo-7"
  657.          href="diary-may2025.php?dirdate=20250530&amp;imagesizes=11111112&amp;topics=c&amp;edit=0#Photo-7">
  658.          <img alt="This should be Weather-stations-2.jpeg.  Is it missing?" border="0" id="Photo_7"
  659.               title="Photo Weather-stations-2.jpeg.  Click to redisplay larger version of image."
  660.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250530/small/Weather-stations-2.jpeg"
  661.               width="216" height="311"
  662.           /></a>
  663.  
  664.      <p>
  665. Those prices look much better than what I had feared.  Ha ha, only joking: they're US
  666. prices, and with the ridiculous shipping costs, <a href="https://en.wikipedia.org/wiki/Amazon_(company)">Amazon</a> wants $355.  Still, that
  667. looks better.  Where's the catch?
  668.      </p>
  669.  
  670.      <blockquote class="fullwidth">
  671.        <div class="listitemwidth">
  672.          No way to export data
  673.        </div>
  674.      </blockquote>
  675.  
  676.      <p>
  677. That looks like a knock-out criterion.  But can it be right?  If it has <a href="https://en.wikipedia.org/wiki/Wi-Fi">Wi-Fi</a> connectivity, it should be possible to
  678. get the data out.  Quite possibly they mean something else altogether.
  679.      </p>
  680.  
  681.      <p>
  682. What looks more dangerous is the “transmission range”: 101 m (330 ft).  That's what my
  683. current unit claims, and it's not enough for the 15 m in the Real World.  Possibly this unit
  684. is closer to the specs, but who knows?
  685.      </p>
  686.  
  687.      <p>
  688. But it's “Wi-Fi”.  Doesn't that make a difference?  No, it seems.  The “Wi-Fi” refers to
  689. some other interface, possibly replacing the <a href="https://en.wikipedia.org/wiki/USB">USB</a> interface on my current units.  As far as I
  690. can tell, all units communicate with plain <a href="https://en.wikipedia.org/wiki/Radio_Frequency">RF</a>.
  691.      </p>
  692.  
  693.      <p>
  694. So round about here I need to step back and decide what I really want:
  695.      </p>
  696.  
  697.      <ul>
  698.        <li class="fullwidth">
  699.          <div class="listitemwidth">
  700.            Computer interface with open formats.
  701.          </div>
  702.        </li>
  703.  
  704.        <li class="fullwidth">
  705.          <div class="listitemwidth">
  706.            Easy mounting.  Does it have a mounting pole?  Yes, I can buy one from <a href="https://www.instrumentchoice.com.au/">Instrument Choice</a>, who seem to be the
  707.            leading supplier in Australia.  I recall seeing one for round $180, significantly more
  708.            than I paid for the old unit that included to pole.
  709.          </div>
  710.        </li>
  711.  
  712.        <li class="fullwidth">
  713.          <div class="listitemwidth">
  714.            Rechargeable battery.
  715.          </div>
  716.        </li>
  717.  
  718.        <li class="fullwidth">
  719.          <div class="listitemwidth">
  720.            Adequate range for my situation.  After some comparison, it seems that 100 m is a fairly
  721.            typical range.  Do other units do better, or do I have a particularly noisy environment?
  722.          </div>
  723.        </li>
  724.      </ul>
  725.  
  726.      <p>
  727. And somehow the pricing from some suppliers suggest that they're trying to pull a fast one.
  728. <a href="https://ambientweather.com/ws-2000-smart-weather-station">Ambient Weather</a> offers mounts from $115.36 to $197.78, ultimately just poles.  And a different power
  729. adapter (in other words, different plug) costs an <i>additional</i> $32.95.
  730.      </p>
  731.  
  732.      <p>
  733. As long as these criteria are met, I can probably work around any other strangenesses.  But
  734. it's so difficult to find useful data.  <a href="https://ambientweather.com/ws-2000-smart-weather-station">Ambient Weather</a> has a
  735. comparison table that compares these two units and also a cheaper and more expensive unit.
  736. But so much of the comparison is nonsense.  The WS-2000 can detect sunrise, sunset, moonrise
  737. and moonset, while the cheaper WS-2009 can't.  You don't need a weather station for that:
  738. the data is available in many places.  And it confirms that the WS-2000 is “Internet
  739. connected”, so it's not clear what the <a href="https://www.techgearlab.com/topics/electronics/best-weather-station">Techgearlab</a> review is talking about.
  740.      </p>
  741.  
  742.      <p>
  743. But then there's another unit that I saw and then lost again, which offers all sorts of
  744. additional sensors.  Do I need them?  Can I afford them?
  745.      </p>
  746.      </div>
  747.    ]]>
  748.  </description>
  749.  <dc:creator>Greg Lehey</dc:creator>
  750.  <dc:date>2025-05-31T04:02:01+00:00</dc:date>
  751. </item>
  752.  
  753.                        
  754. <item>
  755. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-may2025.php#D-20250531-231938</guid>
  756. <link>http://www.lemis.com/grog/diary-may2025.php?topics=c#D-20250531-231938</link>
  757. <category>language</category>
  758. <category>technology</category>
  759. <category>opinion</category>
  760. <title>The return of the Umlaut</title>
  761.  <description>
  762.    <![CDATA[
  763.    <div align="justify">
  764.      <p>
  765. <a href="http://www.lemis.com/grog/diary-apr2025.php?subtitle=I%20don%27t%20want%20a%20review&amp;article=D-20250426-015842#D-20250426-015842">Last month</a> I got worked up about the fact that my cousin Sandy doesn't want to spell
  766. things correctly in her documentation.  She deliberately removed all <a href="https://en.wikipedia.org/wiki/Umlaut_(diacritic)">umlaut</a> indications from German
  767. texts, giving rise to names like <a href="https://en.wikipedia.org/wiki/Konigsberg">Konigsberg</a> and Sohl (relatives called Söhl).  I find it painful.
  768.      </p>
  769.  
  770.      <p>
  771. But today I saw not one, but two cases where the umlaut marking was unexpectedly present.
  772. First, spam:
  773.      </p>
  774.  
  775.      <blockquote class="fullwidth">
  776. <div style="text-align:left">
  777.  <tt>
  778. &nbsp;&nbsp;27 N + 31&#45;05&#45;2025 To groggly@FreeBSD Arnault Bernard &nbsp; &nbsp; &nbsp;( &nbsp; 0) N + Mr. Bernärd häs dönäted 3.5,000,000USD tö yöu för the purpöse öf chärity project. Kindly respond to bernardarnault318@gmail.com för möre införmätion.
  779.  </tt>
  780. </div>
  781. </blockquote>
  782.  
  783.      <p>
  784. Interestingly, there's no <b>ü</b> in there.  Presumably the intention was to evade spam
  785. checkers.  But then in the evening, while watching TV, we saw:
  786.      </p>
  787.  
  788.        <a id="Photo-8" name="Photo-8"
  789.          href="diary-may2025.php?dirdate=20250531&amp;imagesizes=111111112&amp;topics=c&amp;edit=0#Photo-8">
  790.          <img alt="This should be Noething.jpeg.  Is it missing?" border="0" id="Photo_8"
  791.               title="Photo Noething.jpeg.  Click to redisplay larger version of image."
  792.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250531/small/Noething.jpeg"
  793.               width="346" height="195"
  794.           /></a>
  795.        <a id="Photo-9" name="Photo-9"
  796.          href="diary-may2025.php?dirdate=20250531&amp;imagesizes=1111111112&amp;topics=c&amp;edit=0#Photo-9">
  797.          <img alt="This should be Noething-detail.jpeg.  Is it missing?" border="0" id="Photo_9"
  798.               title="Photo Noething-detail.jpeg.  Click to redisplay larger version of image."
  799.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250531/small/Noething-detail.jpeg"
  800.               width="436" height="155"
  801.           /></a>
  802.  
  803.      <p>
  804. That's in <a href="https://www.fernsehserien.de/die-rettungsflieger/folgen/7x04-schmerzhafte-erfahrung-136400">„Schmerzhafte Erfahrung“</a>, an episode of <a href="https://www.fernsehserien.de/die-rettungsflieger/">„Die Rettungsflieger“</a>, clearly
  805. in German.  Why is the woman called Mrs Nöthing?  It's a plausible German name, but I can't
  806. help thinking that the script writer was thinking of nothing useful.
  807.      </p>
  808.      </div>
  809.    ]]>
  810.  </description>
  811.  <dc:creator>Greg Lehey</dc:creator>
  812.  <dc:date>2025-05-31T23:19:38+00:00</dc:date>
  813. </item>
  814.  
  815.            
  816. <!-- topic HGo not selected
  817.      <p>
  818. Today was our daughter <a href="http://www.lemis.com/yana/">Yana's</a> 40th birthday, and we exchanged
  819. email.  She asked about our family history, specifically the Irish side of the family, so
  820. once again one of <a href="http://www.lemis.com/grog/Albums/People/The-Leheys-from-Goldengarden.pdf">Sandy's documents</a> came in handy, this time without obvious misspellings.
  821.      </p>
  822.  
  823.      <p>
  824. It seems that I have never read the entire document.  I know that I am the last in a long
  825. line of G. F. Leheys (though the others were all called George Francis), but I came across
  826. an interesting detail: my great-grandfather George Lehey (son of my great-great-grandfather
  827. George Lehey and father of my grandfather George Lehey) died in 1921 of <a href="https://en.wikipedia.org/wiki/Pernicious_anaemia">pernicious anaemia</a>.  That rings
  828. a bell.  I suffer (if that's the word) from elevated <a href="https://en.wikipedia.org/wiki/Mean_Corpuscular_Volume">Mean Corpuscular Volume</a> (MCV) levels, and that's <a href="http://www.lemis.com/grog/diary-jan2020.php?subtitle=Doctor%20again&amp;article=D-20200201-012256#D-20200201-012256">somehow related to pernicious anaemia</a>.  There's also a question of <a href="https://pubmed.ncbi.nlm.nih.gov/9118603/">benign familial macrocytosis</a>, a
  829. hereditary complaint which I don't seem to have mentioned in this diary.  I had asked my two
  830. closest living relatives, my sister Bev and Yana, to compare their blood test results.  My
  831. sister lives in England, and thus, despite her age (74) does not have regular checkups.
  832. Yana had recently sent me her blood test results, which didn't show anything of interest.
  833. But I have an appointment with Dr Paul Smith on Monday, so I'll discuss it all with him
  834. then.
  835.      </p>
  836.      
  837. End deselected topic HGo (Hereditary illnesses?) -->
  838.  
  839.            
  840. <item>
  841. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-may2025.php#D-20250601-020022</guid>
  842. <link>http://www.lemis.com/grog/diary-may2025.php?topics=c#D-20250601-020022</link>
  843. <category>technology</category>
  844. <category>opinion</category>
  845. <title>fra: connectivity problems?</title>
  846.  <description>
  847.    <![CDATA[
  848.    <div align="justify">
  849.      <p>
  850. My external web servers have had no overload for a while, but I have an instance
  851. of <i>top</i> running on the external servers to keep up.  Over the course of the
  852. day, <i>fra.lemis.com</i> showed other problems:
  853.      </p>
  854.  
  855.      <blockquote class="fullwidth">
  856. <div style="text-align:left">
  857.  <tt>
  858. client_loop: send disconnect: Broken pipe
  859. <br />Disconnected at Fri 30 May 2025 08:47:22 AEST
  860. <br />ssh: connect to host fra.lemis.com port 22: Operation timed out
  861. <br />Disconnected at Fri 30 May 2025 08:48:42 AEST
  862. <br />Fssh_kex_exchange_identification: read: Connection reset by peer
  863. <br />Connection reset by 192.248.184.
  864. <br />Disconnected at Fri 30 May 2025 08:53:44 AEST
  865. <br />client_loop: send disconnect: Broken pipe
  866. <br />Disconnected at Sat 31 May 2025 03:57:33 AEST
  867. <br />Connection closed by 192.248.184.42 port 22
  868. <br />rsync: connection unexpectedly closed (0 bytes received so far) [sender]
  869. <br />rsync error: error in rsync protocol data stream (code 12) at io.c(231) [sender=3.3.0]
  870. <br />Fri 30 May 2025 12:38:16 AEST
  871. <br />Connection closed by 192.248.184.42 port 22
  872. <br />rsync: connection unexpectedly closed (0 bytes received so far) [sender]
  873. <br />rsync error: error in rsync protocol data stream (code 12) at io.c(231) [sender=3.3.0]
  874. <br />
  875.  </tt>
  876. </div>
  877. </blockquote>
  878.  
  879.      <p>
  880. That's at least 5 disconnections, at least 2 of them while trying to reestablish connection.
  881. All the signs of network issues in <a href="https://en.wikipedia.org/wiki/Frankfurt">Frankfurt</a>, especially since other servers were not affected.  Why didn't <a href="https://www.vultr.com/">Vultr</a> report anything?
  882.      </p>
  883.      </div>
  884.    ]]>
  885.  </description>
  886.  <dc:creator>Greg Lehey</dc:creator>
  887.  <dc:date>2025-06-01T02:00:22+00:00</dc:date>
  888. </item>
  889.  
  890.  
  891.                  
  892. <item>
  893. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250602-004654</guid>
  894. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250602-004654</link>
  895. <category>technology</category>
  896. <category>music</category>
  897. <title>Web server load</title>
  898.  <description>
  899.    <![CDATA[
  900.    <div align="justify">
  901.      <p>
  902. The load on my web servers has been quite tolerable over the last week or so, with load
  903. averages mainly below 1.  That doesn't correspond directly to the number of hits.
  904. Today <i>lax</i> had:
  905.      </p>
  906.  
  907.      <blockquote class="fullwidth">
  908. <div style="text-align:left">
  909.  <tt>
  910. On 30 May 2025 you had a total of 702441 hits.
  911. <br />...
  912. <br />193130 /grog/photos/Photos.php?dirdate=19980703
  913.  </tt>
  914. </div>
  915. </blockquote>
  916.  
  917.      <p>
  918. That's much less than the 14 million or so that I had a while back, but it's still 5%, while
  919. the server load has dropped by over 99%.  And why is this URL top of the list?  It's of
  920. <a href="http://www.lemis.com/grog/photos/Photos.php?dirdate=19980703">my musical instruments</a>, 27
  921. years ago.  I should investigate these things more
  922.      </p>
  923.      </div>
  924.    ]]>
  925.  </description>
  926.  <dc:creator>Greg Lehey</dc:creator>
  927.  <dc:date>2025-06-02T00:46:54+00:00</dc:date>
  928. </item>
  929.  
  930.            
  931. <item>
  932. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250602-004854</guid>
  933. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250602-004854</link>
  934. <category>technology</category>
  935. <category>opinion</category>
  936. <title>Destroying Frankfurt</title>
  937.  <description>
  938.    <![CDATA[
  939.    <div align="justify">
  940.      <p>
  941. My server <i>ffm.lemis.com</i> has been up for nearly 20 months:
  942.      </p>
  943.  
  944.      <blockquote class="fullwidth">
  945. <div style="text-align:left">
  946.  <tt>
  947. <code><font color="blue">=== grog@ffm (/dev/pts/0)</font> <font color="red">~</font> <font color="blue">14</font> &#45;&gt; <b><tt>date; uptime</tt></b></code>
  948. <br />Sun Jun &nbsp;1 03:17:01 UTC 2025
  949. <br />&nbsp;3:17AM &nbsp;up 605 days, 16:20, 1 user, load averages: 0.25, 0.29, 0.33
  950. <br />
  951.  </tt>
  952. </div>
  953. </blockquote>
  954.  
  955.      <p>
  956. That's not its longest uptime.  <a href="http://www.lemis.com/grog/diary-oct2023.php?subtitle=System%20down!&amp;article=D-20231006-002525#D-20231006-002525">1½ years ago</a> it reached an uptime of 2067 days (5 years, 8 months) before it went
  957. down due to some failure with <a href="https://en.wikipedia.org/wiki/DigitalOcean">DigitalOcean</a>.
  958.      </p>
  959.  
  960.      <p>
  961. But now I have two servers in <a href="https://en.wikipedia.org/wiki/Frankfurt_am_Main">Frankfurt am Main</a>, and all <i>ffm</i> is doing is running <a href="https://en.wikipedia.org/wiki/Squid_(software)"><i>squid</i></a>.  <i>fra.lemis.com</i> can do that too.  So shut down:
  962.      </p>
  963.  
  964.      <blockquote class="fullwidth">
  965. <div style="text-align:left">
  966.  <tt>
  967. <code><font color="blue">=== root@ffm (/dev/pts/0)</font> <font color="red">/home/grog</font> <font color="blue">2</font> &#45;&gt; <b><tt></tt></b></code>
  968. <br />*** FINAL System shutdown message from grog@ffm.lemis.com ***
  969. <br />
  970. <br />System going down IMMEDIATELY
  971. <br />
  972. <br />System shutdown time has arrived
  973. <br />Connection to ffm.lemis.com closed by remote host.
  974. <br />Connection to ffm.lemis.com closed.
  975. <br />Disconnected at Sun 1 Jun 2025 13:18:29 AEST
  976. <br />
  977.  </tt>
  978. </div>
  979. </blockquote>
  980.  
  981.      <p>
  982. Did <a href="https://www.vultr.com/">Vultr</a> register that?  No.  For that, I need
  983. to <i>destroy</i> it, removing all trace of it, and in particular the IP address.
  984.      </p>
  985.  
  986.      <blockquote class="fullwidth">
  987. <div style="text-align:left">
  988.  <tt>
  989. <code><font color="blue">=== grog@eureka (/dev/pts/9)</font> <font color="red">~</font> <font color="blue">128</font> &#45;&gt; <b><tt>host ffm</tt></b></code>
  990. <br />ffm.lemis.com has address 45.63.116.55
  991. <br /><code><font color="blue">=== grog@eureka (/dev/pts/9)</font> <font color="red">~</font> <font color="blue">129</font> &#45;&gt; <b><tt>host 45.63.116.55</tt></b></code>
  992. <br />55.116.63.45.in&#45;addr.arpa domain name pointer 45.63.116.55.vultrusercontent.com.
  993. <br />
  994.  </tt>
  995. </div>
  996. </blockquote>
  997.  
  998.      <p>
  999. I still have a snapshot of <i>ffm</i>, taken at
  1000. 2025-05-23 02:14:56 (presumably <a href="https://en.wikipedia.org/wiki/UTC">UTC</a>).  It's 9.1 GB in size, but for billing purposes they tell me it's 25GB, the uncompressed
  1001. size.  I wonder if I can download it somewhere and restore it later.
  1002.      </p>
  1003.      </div>
  1004.    ]]>
  1005.  </description>
  1006.  <dc:creator>Greg Lehey</dc:creator>
  1007.  <dc:date>2025-06-02T00:48:54+00:00</dc:date>
  1008. </item>
  1009.  
  1010.            
  1011. <item>
  1012. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250602-010853</guid>
  1013. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250602-010853</link>
  1014. <category>technology</category>
  1015. <category>general</category>
  1016. <category>opinion</category>
  1017. <title>Weather stations reconsidered</title>
  1018.  <description>
  1019.    <![CDATA[
  1020.    <div align="justify">
  1021.      <p>
  1022. So what new weather station do I buy?  All are more expensive than the one I have (I think),
  1023. and all will require me to adapt my software.
  1024.      </p>
  1025.  
  1026.      <p>
  1027. And then I saw the title of the instruction manual for my current WS1081:
  1028.      </p>
  1029.  
  1030.      <blockquote class="fullwidth">
  1031.        <div class="listitemwidth">
  1032.          TOUCH SCREEN WEATHER STATION WITH SOLAR POWERED
  1033.        </div>
  1034.      </blockquote>
  1035.  
  1036.      <p>
  1037. Yes, that's what they wrote.  But inside it states (top of page 7):
  1038.      </p>
  1039.  
  1040.      <blockquote class="fullwidth">
  1041.        <div class="listitemwidth">
  1042.          Rechargeable batteries have lower voltages and should never be used.
  1043.        </div>
  1044.      </blockquote>
  1045.  
  1046.      <p>
  1047. But then, who writes accurate instruction manuals nowadays?  In fact, this one looks
  1048. relatively good in comparison to the nonsense I've seen elsewhere.
  1049.      </p>
  1050.  
  1051.      <p>
  1052. So: back to my list of issues:
  1053.      </p>
  1054.  
  1055.      <ol>
  1056.        <li class="fullwidth">
  1057.          <div class="listitemwidth">
  1058.            <i>Doesn't handle rechargeable batteries:</i> Ha ha, only joking, we advertise the thing
  1059.            with rechargeable batteries.
  1060.          </div>
  1061.        </li>
  1062.  
  1063.        <li class="fullwidth">
  1064.          <div class="listitemwidth">
  1065.            <i>Range:</i> I have only tried it on the verandah table.  Put it up in the air where it
  1066.            belongs and it may do better.
  1067.          </div>
  1068.        </li>
  1069.  
  1070.        <li class="fullwidth">
  1071.          <div class="listitemwidth">
  1072.            <i>No pole:</i> This seems to be modern.  I'd need to get a pole for a replacement too.
  1073.          </div>
  1074.        </li>
  1075.  
  1076.        <li class="fullwidth">
  1077.          <div class="listitemwidth">
  1078.            <i>Mounting seems flimsy:</i> I could find a way to stop it blowing away if it comes
  1079.            dislodged.
  1080.          </div>
  1081.        </li>
  1082.  
  1083.        <li class="fullwidth">
  1084.          <div class="listitemwidth">
  1085.            <i>Unreliable software:</i> This could be my fault.
  1086.          </div>
  1087.        </li>
  1088.      </ol>
  1089.  
  1090.      <p>
  1091. So what do I do?  Put in some rechargeable batteries and put the thing in the position where
  1092. it belongs and see what happens.
  1093.      </p>
  1094.      </div>
  1095.    ]]>
  1096.  </description>
  1097.  <dc:creator>Greg Lehey</dc:creator>
  1098.  <dc:date>2025-06-02T01:08:53+00:00</dc:date>
  1099. </item>
  1100.  
  1101.            
  1102. <!-- topic g not selected
  1103.      <p>
  1104. I've been making cuttings of my <a href="https://en.wikipedia.org/wiki/Hibiscus_rosa-sinensis">Hibiscus rosa-sinensis</a> “Uncle Max” for years, and it works well.  I've never heard of growing them from seeds.  But
  1105. these are clearly seed pods:
  1106.      </p>
  1107.  
  1108.            
  1109.      <p>
  1110. I suppose I should plant them and see what happens.
  1111.      </p>
  1112.      
  1113. End deselected topic g (Hibiscus seeds) -->
  1114.  
  1115.            
  1116. <item>
  1117. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250602-013141</guid>
  1118. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250602-013141</link>
  1119. <category>technology</category>
  1120. <category>opinion</category>
  1121. <title>Reddit confusion</title>
  1122.  <description>
  1123.    <![CDATA[
  1124.    <div align="justify">
  1125.      <p>
  1126. I signed up for <a href="https://en.wikipedia.org/wiki/Reddit">Reddit</a> years ago,
  1127. and I almost never used it.  But there are some interesting links on weather stations
  1128. (<tt><a href="https://www.reddit.com/r/myweatherstation">r/myweatherstation</a></tt>), so I tried to sign in.  “User name or password invalid”, their way of saying “we
  1129. have forgotten about you”.  OK, sign up again with a different name.  Sorry, Groogle
  1130. taken. Groogled taken. Groogledddd taken.  Sorry, Reddittttt, you're lying.
  1131.      </p>
  1132.  
  1133.      <p>
  1134. Finally found a way around its broken user name recognition and signed up.  Wait for
  1135. confirmation message.  Message doesn't show.
  1136.      </p>
  1137.  
  1138.      <p>
  1139. Try again.  Same thing.  Try again.  Same thing. “We're having problems”.  But then I found
  1140. a way to register without an email address (why?).  And that worked.  Some time later, round
  1141. 5 minutes, the confirmation messages came in, but they knew my new user name and had
  1142. associated it with the email address I gave them.  What's their problem?
  1143.      </p>
  1144.      </div>
  1145.    ]]>
  1146.  </description>
  1147.  <dc:creator>Greg Lehey</dc:creator>
  1148.  <dc:date>2025-06-02T01:31:41+00:00</dc:date>
  1149. </item>
  1150.  
  1151.                  
  1152. <item>
  1153. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250603-020627</guid>
  1154. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250603-020627</link>
  1155. <category>technology</category>
  1156. <category>general</category>
  1157. <title>More weather station investigations</title>
  1158.  <description>
  1159.    <![CDATA[
  1160.    <div align="justify">
  1161.      <p>
  1162. Can my new WS1081 weather station run on and charge <a href="https://en.wikipedia.org/wiki/Nickel-cadmium_battery">Nickel-Cadmium batteries</a>?
  1163. The first is easy to check: put in some charged batteries and see what happens.  It works!
  1164. So at least part of the instructions are wrong.
  1165.      </p>
  1166.  
  1167.      <p>
  1168. And charging them?  That will take a while to confirm.  What does <a href="https://gemini.google.com/">Google Gemini</a> say?
  1169.      </p>
  1170.  
  1171.      <blockquote class="fullwidth">
  1172.        <div class="listitemwidth">
  1173.          The WS1081 weather station itself does not recharge batteries directly.
  1174.        </div>
  1175.  
  1176. <div class="listitemwidth">
  1177.  Outdoor Sensor (Multi-sensor): Often uses 2 x AA rechargeable batteries, and in some
  1178.  versions, it's solar-powered, which can help prolong the life of the rechargeable
  1179.  batteries.
  1180. </div>
  1181.      </blockquote>
  1182.  
  1183.      <p>
  1184. Oh.  Can I believe it?  So far it looks at least as plausible as anything in the
  1185. documentation.  So—I think—back it goes.
  1186.      </p>
  1187.      </div>
  1188.    ]]>
  1189.  </description>
  1190.  <dc:creator>Greg Lehey</dc:creator>
  1191.  <dc:date>2025-06-03T02:06:27+00:00</dc:date>
  1192. </item>
  1193.  
  1194.            
  1195. <!-- topic GHo not selected
  1196.      <p>
  1197. Into town for a six-monthly doctor's appointment and also a couple of vaccinations,
  1198. <a href="https://en.wikipedia.org/wiki/Influenza">influenza</a> and <a href="https://en.wikipedia.org/wiki/COVID-19">COVID-19</a>.  The nurse who had been intended
  1199. to perform the vaccinations had been held up, so Paul did it himself, showing in the process
  1200. that his supplies for this sort of thing are a little unusual:
  1201.      </p>
  1202.  
  1203.            
  1204.      <p>
  1205. The blood test results were nothing unusual, but today I had <a href="http://www.lemis.com/yana/">Yana's</a> results there as well.  Her <a href="https://en.wikipedia.org/wiki/Mean_Corpuscular_Volume">Mean Corpuscular Volume</a> (MCV) was normal, but there were some issues with low <a href="https://en.wikipedia.org/wiki/Vitamin_B12">Vitamin B₁₂</a>, something that I have had
  1206. to do with <a href="http://www.lemis.com/grog/diary-dec2014.php?subtitle=To%20the%20doctor%20again&amp;article=D-20141218-234258#D-20141218-234258">in the past</a>.  I tried to tell Paul when it was, but it seems he already had the
  1207. information: he had found the issue interesting enough to include all my old medical notes
  1208. from the time before <a href="http://www.lemis.com/grog/diary-sep2016.php?subtitle=Doctor%20again&amp;article=D-20160923-042010#D-20160923-042010">I switched to him as my GP</a>.  And it seems that in all that time my MCV has been round
  1209. the 103 fl mark, the value I had today.
  1210.      </p>
  1211.  
  1212.      <p>
  1213. But then there's the issue of my great-grandfather, George Francis Lehey (1859-1921), who
  1214. died of <a href="https://en.wikipedia.org/wiki/Pernicious_anaemia">pernicious
  1215. anaemia</a>.  That, too, is related to <a href="https://en.wikipedia.org/wiki/Vitamin_B12">Vitamin B₁₂</a>.  But my B₁₂ levels have
  1216. been fine for the last 10 years, and there have been no issues with <a href="https://en.wikipedia.org/wiki/Intrinsic_factor">intrinsic factor</a> and
  1217. Anti-<a href="https://en.wikipedia.org/wiki/Parietal_cell">parietal cell</a> Antibodies.  As he put it, the MCV is consistently elevated, but there's nothing pointing to
  1218. why.  Still, Yana's B₁₂ issues and George's (1959-1921) cause of death suggest that we
  1219. should look more carefully.  My pathology request for November includes active B₁₂/folate,
  1220. intrinsic factor antibodies and anti-parietal cell autoantibodies.
  1221.      </p>
  1222.  
  1223.      <p>
  1224. And then there were other issues.  How much <a href="https://en.wikipedia.org/wiki/Vitamin_B6">Vitamin B₆</a> is too much?  My magnesium
  1225. tablets contain 60 mg per tablet, and it seems that <a href="http://www.lemis.com/grog/diary-jan2025.php?subtitle=Vitamin%20B%E2%82%86%20overdose?&amp;article=D-20250130-225447#D-20250130-225447">that's far too much</a>.  Paul came up with some test that showed people taking multiple
  1226. grams of B₆ daily over several years with no ill effects, but then the directive that all
  1227. medications with more than 10 mg B₆ per dose should carry a warning label.  So he recommends
  1228. finding an alternative with less B₆.
  1229.      </p>
  1230.  
  1231.      <p>
  1232. And then he finally had the results of the <a href="https://en.wikipedia.org/wiki/DEXA">DEXA</a> scan.  Values between -2.3 for the femoral neck and -1.1 for the lumbar spine,
  1233. both in the <a href="https://en.wikipedia.org/wiki/Osteopenia">osteopenia</a> range.
  1234. That's not significantly different from <a href="http://www.lemis.com/grog/diary-nov2022.php?subtitle=Osteopenia!&amp;article=D-20221126-011600#D-20221126-011600">2½ years ago</a>.
  1235.      </p>
  1236.      
  1237. End deselected topic GHo (Medical checkup) -->
  1238.  
  1239.            
  1240. <item>
  1241. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250603-042909</guid>
  1242. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250603-042909</link>
  1243. <category>technology</category>
  1244. <category>history</category>
  1245. <title>Web site activity over the years</title>
  1246.  <description>
  1247.    <![CDATA[
  1248.    <div align="justify">
  1249.      <p>
  1250. My web server loads seem to be subsiding again, though there's evidence of load averages
  1251. above 10:
  1252.      </p>
  1253.  
  1254.      <blockquote class="fullwidth">
  1255. <div style="text-align:left">
  1256.  <tt>
  1257. last pid: 63326; &nbsp;load averages: &nbsp;0.51, &nbsp;0.39, &nbsp;0.348
  1258.  </tt>
  1259. </div>
  1260. </blockquote>
  1261.  
  1262.      <p>
  1263. That third place after the decimal at the end of the line is the result of one of the three
  1264. being above 10, shifting the text one line to the right.  When it goes down again, the last
  1265. digit doesn't get erased.
  1266.      </p>
  1267.  
  1268.      <p>
  1269. But by chance I found <a href="http://www.lemis.com/grog/diary-jan2004.php?topics=c#31">this</a>:
  1270.      </p>
  1271.  
  1272.      <blockquote class="fullwidth">
  1273. <div style="text-align:left">
  1274.  <tt>
  1275. On 30 January 2004 you had a total of 2875 HTML hits.
  1276. <br />Top 30 hits:
  1277. <br />&nbsp;&nbsp; &nbsp;228 /grog/cats.php
  1278. <br />&nbsp;&nbsp; &nbsp;136 /grog/diary.php
  1279. <br />&nbsp;&nbsp; &nbsp; 68 /grog/
  1280. <br />
  1281.  </tt>
  1282. </div>
  1283. </blockquote>
  1284.  
  1285.      <p>
  1286. How times have changed!
  1287.      </p>
  1288.      </div>
  1289.    ]]>
  1290.  </description>
  1291.  <dc:creator>Greg Lehey</dc:creator>
  1292.  <dc:date>2025-06-03T04:29:09+00:00</dc:date>
  1293. </item>
  1294.  
  1295.                  
  1296. <!-- topic ko not selected
  1297.      <p>
  1298. Another attempt at <a href="http://www.lemis.com/grog/recipes/pad-see-ew.php">pad see ew</a> today.  As
  1299. planned <a href="http://www.lemis.com/grog/diary-may2025.php?subtitle=Pad%20see%20ew%20with%20wide%20rice%20noodles&amp;article=D-20250523-022330#D-20250523-022330">last time</a>, I made more sauce.  I also fried the noodles by themselves in hope of
  1300. finding the elusive <a href="https://mammafong.com/blogs/mammas-cooking-diary/wok-hei-capturing-the-essence-of-fire-in-your-cooking">“Wok hei”</a> that is part of the charm of the dish.  The result was darker (here 2 weeks
  1301. ago and today)
  1302.      </p>
  1303.  
  1304.            
  1305.      <p>
  1306. It didn't taste bad, but I'm left wondering if I understand what “wok hei” (“the breath of
  1307. the wok”) really tastes like.  People talk of a “smoky” flavour, but that too is subject to
  1308. interpretation.
  1309.      </p>
  1310.      
  1311. End deselected topic ko (Wok hei?  What hey?) -->
  1312.  
  1313.            
  1314. <item>
  1315. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250604-014321</guid>
  1316. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250604-014321</link>
  1317. <category>technology</category>
  1318. <category>general</category>
  1319. <category>opinion</category>
  1320. <title>More storage!</title>
  1321.  <description>
  1322.    <![CDATA[
  1323.    <div align="justify">
  1324.      <p>
  1325. My computer storage requirements continue to increase, mainly because of multimedia.  I now
  1326. have 18 TB of videos:
  1327.      </p>
  1328.  
  1329.      <blockquote class="fullwidth">
  1330. <div style="text-align:left">
  1331.  <tt>
  1332. Filesystem &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;1048576&#45;blocks &nbsp; &nbsp; &nbsp; Used &nbsp; &nbsp; Avail Capacity &nbsp;Mounted on
  1333. <br />/dev/ada0p4 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;7,567,870 &nbsp;7,380,176 &nbsp; 112,015 &nbsp; &nbsp;99% &nbsp; &nbsp;/spool
  1334. <br />/dev/da0p1 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 5,722,572 &nbsp;4,592,114 1,073,232 &nbsp; &nbsp;81% &nbsp; &nbsp;/VB2
  1335. <br />hydra:/Video &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3,815,019 &nbsp;3,340,961 &nbsp; 435,907 &nbsp; &nbsp;88% &nbsp; &nbsp;/Video
  1336. <br />total &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 17,105,462 15,313,427 1,620,980 &nbsp; &nbsp;90%
  1337.  </tt>
  1338. </div>
  1339. </blockquote>
  1340.  
  1341.      <p>
  1342. And though my photo storage is just below the 8 TB limit of my backup disks, it won't stay
  1343. that way for long.  Time for some larger backup disks, and by chance found a couple of 16 TB
  1344. external backup disks on <a href="https://www.ebay.com.au/">eBay</a> for $560 each.
  1345. That seemed reasonable.  I can use the old backup disks for something else.
  1346.      </p>
  1347.  
  1348.      <p>
  1349. But wait, there's more!  Use (this code) and get 10% off.  Yes, I can do that.
  1350.      </p>
  1351.  
  1352.      <p>
  1353. Or can I?  To get the discount, I need to use this horrible <a href="https://en.wikipedia.org/wiki/Afterpay">Afterpay</a>.  I really hate everything that
  1354. Afterpay stands for, but $100 are $100 (well, in this case $112).  So sign in.  Oh:
  1355.      </p>
  1356.  
  1357.        <a id="Photo-10" name="Photo-10"
  1358.          href="diary-jun2025.php?dirdate=20250603&amp;imagesizes=11111111112&amp;topics=c&amp;edit=0#Photo-10">
  1359.          <img alt="This should be afterpay-2.jpeg.  Is it missing?" border="0" id="Photo_10"
  1360.               title="Photo afterpay-2.jpeg.  Click to redisplay larger version of image."
  1361.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250603/small/afterpay-2.jpeg"
  1362.               width="332" height="204"
  1363.           /></a>
  1364.  
  1365.      <p>
  1366. That's not my real email address, of course, but I entered it to see if it made any
  1367. difference.  It didn't: the message was the same as with my valid address.  OK, try with the
  1368. phone number:
  1369.      </p>
  1370.  
  1371.        <a id="Photo-11" name="Photo-11"
  1372.          href="diary-jun2025.php?dirdate=20250603&amp;imagesizes=111111111112&amp;topics=c&amp;edit=0#Photo-11">
  1373.          <img alt="This should be afterpay-1.jpeg.  Is it missing?" border="0" id="Photo_11"
  1374.               title="Photo afterpay-1.jpeg.  Click to redisplay larger version of image."
  1375.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250603/small/afterpay-1.jpeg"
  1376.               width="326" height="207"
  1377.           /></a>
  1378.  
  1379.      <p>
  1380. That has one difference from what it wanted: +61&nbsp;0490&nbsp;494&nbsp;001.  Again, no
  1381. difference, either with its invalid number or my corrected one.
  1382.      </p>
  1383.  
  1384.      <p>
  1385. Damn it, afterpay, I'll sign up again.  Or at least I tried.  I couldn't find a way to sign
  1386. up!  All it wanted was to breach security on my mobile phone with its app.  OK, if that's
  1387. the way it wants it.  I can always remove the app when I'm done.  And that worked, but I
  1388. couldn't find a way to associate it with my eBay account.
  1389.      </p>
  1390.  
  1391.      <p>
  1392. OK, try another tack.  Try the whole thing with <a href="https://en.wikipedia.org/wiki/Chromium_%28web_browser%29">Chromium</a> instead of
  1393. <a href="https://en.wikipedia.org/wiki/Firefox"><i>firefox</i></a>.  Yes!  So this
  1394. was just afterpay's way of saying “I don't want to talk to your <i>firefox</i>”.
  1395.      </p>
  1396.  
  1397.      <p>
  1398. afterpay, <i>how</i> I hate you!
  1399.      </p>
  1400.      </div>
  1401.    ]]>
  1402.  </description>
  1403.  <dc:creator>Greg Lehey</dc:creator>
  1404.  <dc:date>2025-06-04T01:43:21+00:00</dc:date>
  1405. </item>
  1406.  
  1407.            
  1408. <!-- topic g not selected
  1409.      <p>
  1410. Winter started a couple of days ago, a time where autumn meets spring.  On the one hand the
  1411. first bulbs are starting to flower:
  1412.      </p>
  1413.  
  1414.      <div align="left">
  1415.      </div>
  1416.  
  1417.      <p>
  1418. And on the other hand, we still have roses and <a href="https://en.wikipedia.org/wiki/Hibiscus_rosa-sinensis">hibiscus</a>:
  1419.      </p>
  1420.  
  1421.            
  1422.      <p>
  1423. The hibiscus in particular is interesting because it is flowering about as well as it has
  1424. done all summer.
  1425.      </p>
  1426.      
  1427. End deselected topic g (Garden flowers in winter) -->
  1428.  
  1429.                  
  1430. <!-- topic Jho not selected
  1431.      <p>
  1432. Up round 6:00 this morning and turned the heat on, as every morning.  But when I got up two
  1433. hours later, the temperature in the lounge room had still not come up to the set 21°.
  1434. Instead I heard several de-icing cycles from the air conditioner: the outside temperature
  1435. was pretty much 0°, and even with the second air conditioner, we were still round 19.4°.  It
  1436. took until 11:12 before the lounge room temperature hit the set 21°.  Time to keep the main
  1437. unit running overnight.
  1438.      </p>
  1439.      
  1440. End deselected topic Jho (Winter arrives) -->
  1441.  
  1442.            
  1443. <!-- topic ko not selected
  1444.      <p>
  1445. One of the issues I have with my <a href="http://www.lemis.com/grog/recipes/Laugengebaeck.php">Laugengebäck</a> is that it needs food-grade <a href="https://en.wikipedia.org/wiki/Sodium_hydroxide">sodium hydroxide</a>.  Where do you get that?  My searches online gave me one result,
  1446. costing over $100 per kilogram.
  1447.      </p>
  1448.  
  1449.      <p>
  1450. Once again, <a href="https://gemini.google.com/">Google Gemini</a> to the rescue,
  1451. pointing me inter alia at <a href="https://www.risenflour.com.au/store/Lye-NaOH-Caustic-Soda-Pearls-p521680481">Risenflour.com</a>, who offer food grade pearls for $23.95 per kilogram.  That's only
  1452. roughly double to cost of commercial sodium hydroxide.
  1453.      </p>
  1454.  
  1455.      <p>
  1456. But we're not done.  After some searching, the web site divulged that they're in <a href="https://en.wikipedia.org/wiki/Perth,_WA">Perth</a>, and the postage is expensive
  1457. because of the danger of the material.  Gemini also gave me other links, including
  1458. <a href="https://www.melbournefooddepot.com/buy/sodium-hydroxide-granules-food-grade-lye-800g/PS0099">the people</a> who want $100.25 for 800 g.  I'll have to go through the whole list to
  1459. find who makes it easy to buy the stuff.  Time to start a <a href="http://www.lemis.com/grog/recipes/NaOH-suppliers.php">list</a>.
  1460.      </p>
  1461.      
  1462. End deselected topic ko (Finding sodium hydroxide) -->
  1463.  
  1464.            
  1465. <item>
  1466. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250605-024132</guid>
  1467. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250605-024132</link>
  1468. <category>general</category>
  1469. <category>technology</category>
  1470. <category>opinion</category>
  1471. <title>The devil you know</title>
  1472.  <description>
  1473.    <![CDATA[
  1474.    <div align="justify">
  1475.      <p>
  1476. So what new weather station do I buy?  <i>Do</i> I buy a new weather station?  Yes, the
  1477. current WS1091 is really unreliable, but it's not clear that others are any better.
  1478. It <i>is</i> clear that I would have to do considerable work to interface a new one to my
  1479. system.  So: I can live with changing the batteries occasionally.  Will the thing talk to
  1480. the base station when it's mounted in the correct place?  Put it up there provisionally:
  1481.      </p>
  1482.  
  1483.        <a id="Photo-12" name="Photo-12"
  1484.          href="diary-jun2025.php?dirdate=20250605&amp;imagesizes=1111111111112&amp;topics=c&amp;edit=0#Photo-12">
  1485.          <img alt="This should be Weather-stations.jpeg.  Is it missing?" border="0" id="Photo_12"
  1486.               title="Photo Weather-stations.jpeg.  Click to redisplay larger version of image."
  1487.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250605/small/Weather-stations.jpeg"
  1488.               width="300" height="225"
  1489.           /></a>
  1490.  
  1491.      <p>
  1492. Yes, there are no wind measurements (the vanes haven't been fitted, and they wouldn't turn
  1493. anyway), but that's no worse than what I've had for the last year or two.  So I'll keep my
  1494. eye on it.
  1495.      </p>
  1496.      </div>
  1497.    ]]>
  1498.  </description>
  1499.  <dc:creator>Greg Lehey</dc:creator>
  1500.  <dc:date>2025-06-05T02:41:32+00:00</dc:date>
  1501. </item>
  1502.  
  1503.                  
  1504. <item>
  1505. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250606-020408</guid>
  1506. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250606-020408</link>
  1507. <category>technology</category>
  1508. <title>Can't contact fra</title>
  1509.  <description>
  1510.    <![CDATA[
  1511.    <div align="justify">
  1512.      <p>
  1513. While trying to sync to my web servers today, received a connection error message
  1514. from <i>fra.lemis.com</i>.  Trying again with <i>ssh</i> gave me:
  1515.      </p>
  1516.  
  1517.      <blockquote class="fullwidth">
  1518. <div style="text-align:left">
  1519.  <tt>
  1520. <code><font color="blue">=== grog@hydra (/dev/pts/18)</font> <font color="red">~/Photos/20250603</font> <font color="blue">289</font> &#45;&gt; <b><tt>ssh fra</tt></b></code>
  1521. <br />ssh: connect to host fra.lemis.com port 22: Connection refused
  1522. <br />Disconnected at Thu 5 Jun 2025 12:08:26 AEST
  1523. <br />
  1524.  </tt>
  1525. </div>
  1526. </blockquote>
  1527.  
  1528.      <p>
  1529. What's that?  It proved that <i>sshd</i> wasn't running, at least not the one I wanted to
  1530. connect to.  Fortunately I had a couple of connections open, so I was able to restart it
  1531. with little trouble.  But what if I hadn't?  I'd have had to brave this <a href="https://www.vultr.com/">Vultr</a> “console” access that has given me so much pain in
  1532. the past.
  1533.      </p>
  1534.  
  1535.      <p>
  1536. Anything in the logs?  The closest clue might be this:
  1537.      </p>
  1538.  
  1539.      <blockquote class="fullwidth">
  1540. <div style="text-align:left">
  1541.  <tt>
  1542. Jun &nbsp;4 00:15:52 fra kernel: pid 73110 (sort), jid 0, uid 1004, was killed: failed to reclaim memory
  1543. <br />Jun &nbsp;4 00:17:42 fra kernel: pid 73316 (sshd), jid 0, uid 0: exited on signal 11 (no core dump &#45; bad address)
  1544. <br />
  1545.  </tt>
  1546. </div>
  1547. </blockquote>
  1548.  
  1549.      <p>
  1550. The times here are <a href="https://en.wikipedia.org/wiki/UTC">UTC</a>, 10 hours
  1551. behind my <a href="https://en.wikipedia.org/wiki/Time_in_Australia">local time</a> (AEST, UTC+10).  The <tt>SIGSEGV</tt>s happen far too often, and they seem not to be overly
  1552. serious, though it does suggest a bug in <i>sshd</i>.  But the <i>sort</i> error suggests
  1553. that maybe I should put in some swap after all.  Still, that doesn't seem to be the issue.
  1554.      </p>
  1555.  
  1556.      <blockquote class="fullwidth">
  1557. <div style="text-align:left">
  1558.  <tt>
  1559. Jun &nbsp;4 02:03:33 fra sshd[74499]: error: PAM: Authentication error for smmsp from 80.250.155.76
  1560. <br />Jun &nbsp;4 02:03:36 fra sshd[74502]: error: PAM: Authentication error for illegal user Admin from ip&#45;d9bc.d&#45;net.kiev.ua
  1561. <br />Jun &nbsp;4 02:09:22 fra sshd[74554]: error: PAM: Authentication error for illegal user postgres from p1368118&#45;ipxg05201yosida.nagano.ocn.ne.jp
  1562. <br />Jun &nbsp;4 02:10:33 fra sshd[74571]: error: PAM: Authentication error for illegal user Default from 124.105.216.239
  1563. <br />
  1564.  </tt>
  1565. </div>
  1566. </blockquote>
  1567.  
  1568.      <p>
  1569. My connection error above happened at 02:08:26, while <i>sshd</i> was merrily rejecting
  1570. illegal connection requests.  So why did it not even respond to mine?  Head-scratching
  1571. needed.
  1572.      </p>
  1573.      </div>
  1574.    ]]>
  1575.  </description>
  1576.  <dc:creator>Greg Lehey</dc:creator>
  1577.  <dc:date>2025-06-06T02:04:08+00:00</dc:date>
  1578. </item>
  1579.  
  1580.            
  1581. <!-- topic ko not selected
  1582.      <p>
  1583. Sent a message to <a href="https://www.risenflour.com.au/">Risenflour</a> about
  1584. shipping costs for <a href="https://www.risenflour.com.au/store/Lye-NaOH-Caustic-Soda-Pearls-p521680481">sodium
  1585. hydroxide</a>.  The response came quickly and painfully:
  1586.      </p>
  1587.  
  1588.      <blockquote class="fullwidth">
  1589. <div style="text-align:left">
  1590.  <tt>
  1591. The estimated postage to your suburb of Parkville is $42.00, in addition to
  1592. <br />the cost of the products you wish to order. To the other address you gave
  1593. <br />me Dereel the postage is $95.00 😱
  1594.  </tt>
  1595. </div>
  1596. </blockquote>
  1597.  
  1598.      <p>
  1599. Ouch!  That might explain the high prices some other sources charge.  But it occurs to me:
  1600. maybe local baking supplies have it.  It's worth checking, anyway.
  1601.      </p>
  1602.      
  1603. End deselected topic ko (Sodium hydroxide transport prices) -->
  1604.  
  1605.            
  1606. <item>
  1607. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250606-024047</guid>
  1608. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250606-024047</link>
  1609. <category>general</category>
  1610. <category>technology</category>
  1611. <category>opinion</category>
  1612. <title>Speicherstadt transformation</title>
  1613.  <description>
  1614.    <![CDATA[
  1615.    <div align="justify">
  1616.      <p>
  1617. The German TV series <a href="https://www.imdb.com/title/tt0940902">„Notruf
  1618. Hafenkante“</a> is set in the <a href="https://en.wikipedia.org/wiki/Speicherstadt">Speicherstadt</a> in <a href="https://en.wikipedia.org/wiki/Hamburg">Hamburg</a>.
  1619. It's a fascinating place.  Here a photo from the German Wikipedia:
  1620.      </p>
  1621.  
  1622.      <a href="https://upload.wikimedia.org/wikipedia/commons/thumb/c/ce/The_Wasserschloss_at_sunset.jpg/500px-The_Wasserschloss_at_sunset.jpg">
  1623.      <img alt=""
  1624.          title=".  Click to see in original size."
  1625.          src="https://upload.wikimedia.org/wikipedia/commons/thumb/c/ce/The_Wasserschloss_at_sunset.jpg/500px-The_Wasserschloss_at_sunset.jpg"
  1626.          width="300"
  1627.          /></a>
  1628.      <p>
  1629. While watching an episode of „Notruf Hafenkante“ tonight, I suspected—correctly—a
  1630. transposition of a view out of the window.  OK, <a href="https://en.wikipedia.org/wiki/Google_Maps">Google Maps</a>, show me some “street
  1631. views”.  This one certainly stood out:
  1632.      </p>
  1633.  
  1634.        <a id="Photo-13" name="Photo-13"
  1635.          href="diary-jun2025.php?dirdate=20250605&amp;imagesizes=11111111111112&amp;topics=c&amp;edit=0#Photo-13">
  1636.          <img alt="This should be Speicherstadt.jpeg.  Is it missing?" border="0" id="Photo_13"
  1637.               title="Photo Speicherstadt.jpeg.  Click to redisplay larger version of image."
  1638.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250605/small/Speicherstadt.jpeg"
  1639.               width="346" height="195"
  1640.           /></a>
  1641.  
  1642.      <p>
  1643. That's not Hamburg!  It's <a href="https://en.wikipedia.org/wiki/München">München</a>!  Well, it's about as plausible as this image, courtesy of <a href="https://www.natgeotv.com/">National Geographic</a>, which I discovered <a href="http://www.lemis.com/grog/diary-nov2015.php?subtitle=Geographic%20Society:%20not%20international&amp;article=D-20151119-233141#D-20151119-233141">10 years ago</a>:
  1644.      </p>
  1645.  
  1646.        <a id="Photo-14" name="Photo-14"
  1647.          href="diary-jun2025.php?dirdate=20151119&amp;imagesizes=111111111111112&amp;topics=c&amp;edit=0#Photo-14">
  1648.          <img alt="This should be Muenzig.png.  Is it missing?" border="0" id="Photo_14"
  1649.               title="Photo Muenzig.png.  Click to redisplay larger version of image."
  1650.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20151119/small/Muenzig.png"
  1651.               width="343" height="197"
  1652.           /></a>
  1653.  
  1654.      <p>
  1655. That view (of the centre of München) is a real condemnation of National Geographic.  And
  1656. clearly the image in Google Maps is the <a href="https://en.wikipedia.org/wiki/Piazza_San_Marco">Piazza San Marco</a> in <a href="https://en.wikipedia.org/wiki/Venice">Venice</a>, here an image from the Wikipedia
  1657. page:
  1658.      </p>
  1659.  
  1660.      <a href="https://upload.wikimedia.org/wikipedia/commons/thumb/7/75/Venice_Untitled_%28262712813%29.jpeg/960px-Venice_Untitled_%28262712813%29.jpeg">
  1661.      <img alt=""
  1662.          title=".  Click to see in original size."
  1663.          src="https://upload.wikimedia.org/wikipedia/commons/thumb/7/75/Venice_Untitled_%28262712813%29.jpeg/960px-Venice_Untitled_%28262712813%29.jpeg"
  1664.          width="300"
  1665.          /></a>
  1666.      <p>
  1667. But on closer examination, it seems that this is a model, possibly located in the
  1668. Speicherstadt.  What a misleading image!
  1669.      </p>
  1670.      </div>
  1671.    ]]>
  1672.  </description>
  1673.  <dc:creator>Greg Lehey</dc:creator>
  1674.  <dc:date>2025-06-06T02:40:47+00:00</dc:date>
  1675. </item>
  1676.  
  1677.                  
  1678. <item>
  1679. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250607-005228</guid>
  1680. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250607-005228</link>
  1681. <category>technology</category>
  1682. <category>opinion</category>
  1683. <title>Storage woes</title>
  1684.  <description>
  1685.    <![CDATA[
  1686.    <div align="justify">
  1687.      <p>
  1688. I'm running out of storage space on <i>tiwi:/spool</i>, one of the disks on which I store
  1689. videos.  And I'm downloading more.  In the middle of the night I ran out of space,
  1690. terminating a number of video loads.
  1691.      </p>
  1692.  
  1693.      <p>
  1694. Most of the storage space is for series: I keep the episodes after looking at them, and some
  1695. individual series take up over 500 GB of storage.
  1696.      </p>
  1697.  
  1698.      <p>
  1699. What should I do?  I have a choice: delete something or add more storage.  A combination
  1700. would also work.  I don't want to delete them, so more storage is the answer, and I have it,
  1701. currently:
  1702.      </p>
  1703.  
  1704.      <blockquote class="fullwidth">
  1705. <div style="text-align:left">
  1706.  <tt>
  1707. <code><font color="blue">=== grog@tiwi (/dev/pts/1)</font> <font color="red">~</font> <font color="blue">352</font> &#45;&gt; <b><tt>df &#45;c /spool/ /VB2/ /Video/</tt></b></code>
  1708. <br />Filesystem &nbsp; 1048576&#45;blocks &nbsp; &nbsp; &nbsp;Used &nbsp; &nbsp; &nbsp;Avail Capacity &nbsp;Mounted on
  1709. <br />/dev/ada0p4 &nbsp; &nbsp; &nbsp; 7.567.870 7.422.409 &nbsp; &nbsp; 69.782 &nbsp; &nbsp;99% &nbsp; &nbsp;/spool
  1710. <br />/dev/da0p1 &nbsp; &nbsp; &nbsp; &nbsp;5.722.572 4.830.152 &nbsp; &nbsp;835.195 &nbsp; &nbsp;85% &nbsp; &nbsp;/VB2
  1711. <br />hydra:/Video &nbsp; &nbsp; &nbsp;3.815.019 3.341.579 &nbsp; &nbsp;435.289 &nbsp; &nbsp;88% &nbsp; &nbsp;/Video
  1712. <br />total &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;17.105.462 15.594.141 1.340.266 &nbsp; &nbsp;92%
  1713. <br />
  1714.  </tt>
  1715. </div>
  1716. </blockquote>
  1717.  
  1718.      <p>
  1719. Oh for <a href="https://en.wikipedia.org/wiki/Vinum_volume_manager">Vinum</a>!  Yes,
  1720. I could probably do it with <a href="https://en.wikipedia.org/wiki/ZFS">ZFS</a>, but
  1721. I'm scared.  So more analysis:
  1722.      </p>
  1723.  
  1724.      <blockquote class="fullwidth">
  1725. <div style="text-align:left">
  1726.  <tt>
  1727. <code><font color="blue">=== root@tiwi (/dev/pts/4)</font> <font color="red">/VB2/spool/Already/Series</font> <font color="blue">108</font> &#45;&gt; <b><tt>du &#45;sc /spool/*</tt></b></code>
  1728. <br />6766451 /spool/Already
  1729. <br />&nbsp;648727 /spool/Series
  1730. <br />...
  1731. <br />7421146 total
  1732. <br />
  1733.  </tt>
  1734. </div>
  1735. </blockquote>
  1736.  
  1737.      <p>
  1738. There are a couple of other directories, but all relatively small.  The
  1739. directory <i>Already</i>, with all videos, seen and unseen, is over 10 times the size
  1740. of <i>Series</i>, which contains the active episodes.  Time to move some of it elsewhere,
  1741. for example to <i>/VB2</i>.  Started that today:
  1742.      </p>
  1743.  
  1744.      <blockquote class="fullwidth">
  1745. <div style="text-align:left">
  1746.  <tt>
  1747. <code><font color="blue">=== grog@tiwi (/dev/pts/0)</font> <font color="red">/spool/Already/Series</font> <font color="blue">117</font> &#45;&gt; <b><tt>du &#45;sc Um&#45;Himmels&#45;Willen/ WaPo&#45;Bodensee/</tt></b></code>
  1748. <br />408298 &nbsp;Um&#45;Himmels&#45;Willen/
  1749. <br />16453 &nbsp; WaPo&#45;Bodensee/
  1750. <br />424750 &nbsp;total
  1751. <br /><code><font color="blue">=== grog@tiwi (/dev/pts/0)</font> <font color="red">/spool/Already/Series</font> <font color="blue">118</font> &#45;&gt; <b><tt>mv Um&#45;Himmels&#45;Willen/ WaPo&#45;Bodensee/ /VB2/spool/Already/Series/</tt></b></code>
  1752.  </tt>
  1753. </div>
  1754. </blockquote>
  1755.  
  1756.      <p>
  1757. It's not fast: <i>/VB2</i> is a <a href="https://en.wikipedia.org/wiki/USB">USB</a> 2.0 disk running at a maximum of 25 MB/s (why?), and it ran all day.
  1758.      </p>
  1759.  
  1760.      <p>
  1761. In the evening, it hit the magic 400 GB mark.  And continued merrily on, past 480 GB.
  1762. What's going on?  A comparison of the contents of the directories showed that I had—for
  1763. reasons long forgotten—a subdirectory <i>11a</i>.  Normally the subdirectories represent the
  1764. season, in this case <i>01</i> to <i>20</i>.  But <i>11a</i> contained links to some of the
  1765. files in other directories.  And <i>mv</i> merrily copied them as new files: it doesn't
  1766. understand links in this context!  Is this a bug or a misfeature?  All the <a href="https://man.freebsd.org/cgi/man.cgi?query=mv">man page</a> has to say is:
  1767.      </p>
  1768.  
  1769.      <blockquote class="fullwidth">
  1770. <div style="text-align:left">
  1771.  <tt>
  1772. &nbsp;&nbsp; &nbsp; As the rename(2) call does not work across file systems, mv uses cp(1)
  1773. <br />&nbsp;&nbsp; &nbsp; and rm(1) to accomplish the move. &nbsp;The effect is equivalent to:
  1774. <br />
  1775. <br />&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; rm &#45;f destination_path &amp;&amp; \
  1776. <br />&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; cp &#45;pRP source_file destination &amp;&amp; \
  1777. <br />&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; rm &#45;rf source_file
  1778. <br />
  1779.  </tt>
  1780. </div>
  1781. </blockquote>
  1782.  
  1783.      <p>
  1784. Removed <i>11a</i> and let it continue, but it still took its time.  Somehow this all takes
  1785. far too long.
  1786.      </p>
  1787.      </div>
  1788.    ]]>
  1789.  </description>
  1790.  <dc:creator>Greg Lehey</dc:creator>
  1791.  <dc:date>2025-06-07T00:52:28+00:00</dc:date>
  1792. </item>
  1793.  
  1794.            
  1795. <item>
  1796. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250607-020524</guid>
  1797. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250607-020524</link>
  1798. <category>technology</category>
  1799. <category>opinion</category>
  1800. <title>More storage issues</title>
  1801.  <description>
  1802.    <![CDATA[
  1803.    <div align="justify">
  1804.      <p>
  1805. Videos aren't the only thing where storage is running out.  I had replace the 8 TB disk for
  1806. my photos with a 16&nbsp;TB disk <a href="http://www.lemis.com/grog/diary-sep2024.php?subtitle=Disk%20copy%20pain&amp;article=D-20240913-023625#D-20240913-023625">9 months ago</a>, but the backup disks are still only 8 TB, so <a href="http://www.lemis.com/grog/diary-jun2025.php?topics=c&amp;subtitle=More%20storage!&amp;article=D-20250604-014321#D-20250604-014321">on Tuesday</a> I ordered 2 16&nbsp;TB backup disks.  Today they arrived, so to <a href="https://en.wikipedia.org/wiki/Napoleons,_Victoria">Napoleons</a> to pick them up, also
  1807. looking in to <a href="https://en.wikipedia.org/wiki/Sebastopol,_Victoria">Sebastopol</a> to pick up some fruit and vegetables that <a href="http://www.lemis.com/yvonne/">Yvonne</a> forgot on Wednesday.
  1808.      </p>
  1809.  
  1810.      <a name="IBM-3330" id="IBM-3330"></a>
  1811.      <p>
  1812. 32 TB in a small box!  That's the equivalent of 20,000 <a href="https://en.wikipedia.org/wiki/IBM_3330">IBM 3330</a> disk drive systems, the benchmark
  1813. of my youth, each of which required an estimated 10 to 20 m² of floor space, not including
  1814. power and cooling.  So at a conservative estimate, I have saved round 30 ha of floor space.
  1815. But I went through all this <a href="http://www.lemis.com/grog/diary-sep2024.php?subtitle=IBM%203330%20space%20requirements&amp;article=D-20240920-021318#D-20240920-021318">last time</a>, when I thought that the minimum footprint of repeating 3330s would be 11.1
  1816. m².
  1817.      </p>
  1818.  
  1819.      <p>
  1820. I think I'll decide that the area per unit could be 16.4 m².  Then the three disks together
  1821. could replace more area than that of the <a href="https://en.wikipedia.org/wiki/Vatican_City">Vatican City</a>.
  1822.      </p>
  1823.  
  1824.      <p>
  1825. By comparison with the video issues, installing the new backup drives (one first, just to be
  1826. safe) was a breeze.  The only issue was the number of <a href="https://en.wikipedia.org/wiki/Inode">inodes</a>.  The first invocation was:
  1827.      </p>
  1828.  
  1829.      <blockquote class="fullwidth">
  1830. <div style="text-align:left">
  1831.  <tt>
  1832. <code><font color="blue">=== root@eureka (/dev/pts/1)</font> <font color="red">~</font> <font color="blue">58</font> &#45;&gt; <b><tt><del>newfs &#45;L Photobackup12 &#45;O 2 &#45;U &#45;a 4 &#45;b 32768 &#45;d 32768 &#45;e 4096 &#45;f 4096 &#45;g 3145728 &#45;h 64 &#45;i 7405568 &nbsp; &nbsp; &nbsp;&#45;j &#45;k 1152 &#45;m 1 &#45;o space /dev/da2p1</del></tt></b></code>
  1833.  </tt>
  1834. </div>
  1835. </blockquote>
  1836.  
  1837.      <p>
  1838. And that only gave me 2,160,428 inodes.  The <i>/Photos</i> disk is half full and uses
  1839. 1,791,168 inodes already, so clearly that's not enough:
  1840.      </p>
  1841.  
  1842.      <blockquote class="fullwidth">
  1843. <div style="text-align:left">
  1844.  <tt>
  1845. <code><font color="blue">=== root@eureka (/dev/pts/1)</font> <font color="red">~</font> <font color="blue">61</font> &#45;&gt; <b><tt>df &#45;i /Photos /pb1</tt></b></code>
  1846. <br />Filesystem &nbsp;1048576&#45;blocks &nbsp; &nbsp; &nbsp;Used &nbsp; &nbsp; Avail Capacity &nbsp; iused &nbsp; &nbsp; ifree %iused &nbsp;Mounted on
  1847. <br />/dev/ada1p1 &nbsp; &nbsp; 15,257,008 7,488,512 7,615,925 &nbsp; &nbsp;50% 1,791,168 4,694,974 &nbsp; 28% &nbsp; /Photos
  1848. <br />/dev/da2p1 &nbsp; &nbsp; &nbsp;15,258,065 &nbsp; &nbsp; 6,813 15,098,671 &nbsp; 0% &nbsp; &nbsp; &nbsp; &nbsp;338 2,160,428 &nbsp; &nbsp;0% &nbsp; /pb1
  1849. <br />
  1850.  </tt>
  1851. </div>
  1852. </blockquote>
  1853.  
  1854.      <p>
  1855. So try again:
  1856.      </p>
  1857.  
  1858.      <blockquote class="fullwidth">
  1859. <div style="text-align:left">
  1860.  <tt>
  1861. <code><font color="blue">=== root@eureka (/dev/pts/1)</font> <font color="red">~</font> <font color="blue">62</font> &#45;&gt; <b><tt>newfs &#45;L Photobackup12 &#45;O 2 &#45;U &#45;a 4 &#45;b 32768 &#45;d 32768 &#45;e 4096 &#45;f 4096 &#45;g 3145728 &#45;h 64 &#45;i 2469888 &#45;j &#45;k 1152 &#45;m 1 &#45;o space &nbsp;/dev/da2p1</tt></b></code>
  1862. <br /><i>(ridiculous number of cylinder groups)</i>
  1863. <br /><code><font color="blue">=== root@eureka (/dev/pts/1)</font> <font color="red">~</font> <font color="blue">63</font> &#45;&gt; <b><tt>mount /dev/da2p1 /pb1</tt></b></code>
  1864. <br /><code><font color="blue">=== root@eureka (/dev/pts/1)</font> <font color="red">~</font> <font color="blue">64</font> &#45;&gt; <b><tt>df &#45;i /Photos /pb1</tt></b></code>
  1865. <br />Filesystem &nbsp;1048576&#45;blocks &nbsp; &nbsp; &nbsp;Used &nbsp; &nbsp; Avail Capacity &nbsp; iused &nbsp; &nbsp; ifree %iused &nbsp;Mounted on
  1866. <br />/dev/ada1p1 &nbsp; &nbsp; 15,257,008 7,488,512 7,615,925 &nbsp; &nbsp;50% 1,791,168 4,694,974 &nbsp; 28% &nbsp; /Photos
  1867. <br />/dev/da2p1 &nbsp; &nbsp; &nbsp;15,258,065 &nbsp; &nbsp; 6,813 15,098,671 &nbsp; &nbsp; 0% &nbsp; &nbsp; &nbsp; &nbsp;338 &nbsp; &nbsp; 2,160,428 &nbsp; &nbsp;0% &nbsp; /pb1
  1868. <br />
  1869.  </tt>
  1870. </div>
  1871. </blockquote>
  1872.  
  1873.      <p>
  1874. In passing, it's interesting to note that silly things like model numbers are uninteresting
  1875. in this day and age.  The boxes with the disks had no indication of the model number, just
  1876. the storage capacity.
  1877.      </p>
  1878.  
  1879.        <a id="Photo-15" name="Photo-15"
  1880.          href="diary-jun2025.php?dirdate=20250608&amp;imagesizes=1111111111111112&amp;topics=c&amp;edit=0#Photo-15">
  1881.          <img alt="This should be Backup-disk-1.jpeg.  Is it missing?" border="0" id="Photo_15"
  1882.               title="Photo Backup-disk-1.jpeg.  Click to redisplay larger version of image."
  1883.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250608/small/Backup-disk-1.jpeg"
  1884.               width="256" height="263"
  1885.           /></a>
  1886.  
  1887.      <p>
  1888. Oh, no, it's there in tiny print on the bottom of the box:
  1889.      </p>
  1890.  
  1891.        <a id="Photo-16" name="Photo-16"
  1892.          href="diary-jun2025.php?dirdate=20250608&amp;imagesizes=11111111111111112&amp;topics=c&amp;edit=0#Photo-16">
  1893.          <img alt="This should be Backup-disk-2.jpeg.  Is it missing?" border="0" id="Photo_16"
  1894.               title="Photo Backup-disk-2.jpeg.  Click to redisplay larger version of image."
  1895.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250608/small/Backup-disk-2.jpeg"
  1896.               width="432" height="156"
  1897.           /></a>
  1898.        <a id="Photo-17" name="Photo-17"
  1899.          href="diary-jun2025.php?dirdate=20250608&amp;imagesizes=111111111111111112&amp;topics=c&amp;edit=0#Photo-17">
  1900.          <img alt="This should be Backup-disk-2-detail.jpeg.  Is it missing?" border="0" id="Photo_17"
  1901.               title="Photo Backup-disk-2-detail.jpeg.  Click to redisplay larger version of image."
  1902.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250608/small/Backup-disk-2-detail.jpeg"
  1903.               width="480" height="140"
  1904.           /></a>
  1905.  
  1906.      <p>
  1907. But it's <i>wrong</i>!  The probes tell me
  1908.      </p>
  1909.  
  1910.      <blockquote class="fullwidth">
  1911. <div style="text-align:left">
  1912.  <tt>
  1913. Jun &nbsp;4 15:03:39 eureka kernel: da2 at umass&#45;sim2 bus 2 scbus6 target 0 lun 0
  1914. <br />Jun &nbsp;4 15:03:39 eureka kernel: da2: &lt;Seagate Backup+ &nbsp;Desk 040B&gt; Fixed Direct Access SPC&#45;4 SCSI device
  1915. <br />Jun &nbsp;4 15:03:39 eureka kernel: da2: Serial Number NA7HFKNF
  1916. <br />Jun &nbsp;4 15:03:39 eureka kernel: da2: 400.000MB/s transfers
  1917. <br />Jun &nbsp;4 15:03:39 eureka kernel: da2: 7630885MB (15628053167 512 byte sectors: 255H 63S/T 972801C)
  1918. <br />Jun &nbsp;4 15:03:39 eureka kernel: da2: quirks=0x2&lt;NO_6_BYTE&gt;
  1919. <br />
  1920.  </tt>
  1921. </div>
  1922. </blockquote>
  1923.  
  1924.      <p>
  1925. No mention of “Seagate STKP16000400” there, just (presumably) <tt>Seagate Backup+ Desk
  1926. 040B</tt>.  And the serial number is different too.  In that connection, it's interesting to
  1927. note that the storage specification mentioned on the visible part of the box is a sticker.
  1928. Have they changed the details?  Has the seller changed the details?  The disk seems to work
  1929. well, but it's surprising.  I'll look more carefully at the second disk.
  1930.      </p>
  1931.      </div>
  1932.    ]]>
  1933.  </description>
  1934.  <dc:creator>Greg Lehey</dc:creator>
  1935.  <dc:date>2025-06-07T02:05:24+00:00</dc:date>
  1936. </item>
  1937.  
  1938.            
  1939. <item>
  1940. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250607-031216</guid>
  1941. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250607-031216</link>
  1942. <category>multimedia</category>
  1943. <category>technology</category>
  1944. <category>opinion</category>
  1945. <title>Transcode fail</title>
  1946.  <description>
  1947.    <![CDATA[
  1948.    <div align="justify">
  1949.      <p>
  1950. I download my videos with <a href="https://github.com/yt-dlp/yt-dlp"><i>yt-dlp</i></a>.  During the night not one, but all concurrent downloads failed due to lack of disk
  1951. space.
  1952.      </p>
  1953.  
  1954.      <p>
  1955. OK, <i>yt-dlp</i> is good at restarting partial transfers.  Try that and get:
  1956.      </p>
  1957.  
  1958.      
  1959.      <blockquote class="fullwidth">
  1960. <div style="text-align:left">
  1961.  <tt>
  1962. [Merger] Merging formats into "Result.mp4"
  1963. <br />ERROR: Postprocessing: Conversion failed!
  1964. <br />
  1965.  </tt>
  1966. </div>
  1967. </blockquote>
  1968.  
  1969.      
  1970.      <p>
  1971. What's that?  <i>Yet Another</i> bug or incompatibility to chase!
  1972.      </p>
  1973.      </div>
  1974.    ]]>
  1975.  </description>
  1976.  <dc:creator>Greg Lehey</dc:creator>
  1977.  <dc:date>2025-06-07T03:12:16+00:00</dc:date>
  1978. </item>
  1979.  
  1980.            
  1981. <item>
  1982. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250607-052833</guid>
  1983. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250607-052833</link>
  1984. <category>technology</category>
  1985. <category>general</category>
  1986. <category>opinion</category>
  1987. <title>Still more weather station pain</title>
  1988.  <description>
  1989.    <![CDATA[
  1990.    <div align="justify">
  1991.      <p>
  1992. In mid-evening discovered that the weather station hadn't been logging since shortly before
  1993. midday.  Dammit, what's <i>wrong</i> with this system?  I found an endless sequence of
  1994.      </p>
  1995.  
  1996.      <blockquote class="fullwidth">
  1997. <div style="text-align:left">
  1998.  <tt>
  1999. Jun &nbsp;6 19:49:28 tiwi wh1080[23992]: Can't read device: Input/output error or Unknown error (5)
  2000. <br />Jun &nbsp;6 19:49:28 tiwi wh1080[23993]: Can't read device: Device busy or Unknown error (16)
  2001. <br />Jun &nbsp;6 19:49:31 tiwi wh1080[23997]: Can't read device: Device busy or Unknown error (16)
  2002. <br />
  2003.  </tt>
  2004. </div>
  2005. </blockquote>
  2006.  
  2007.      <p>
  2008. Damn this unreliable system!  Tried things that have helped in the past, like disconnecting
  2009. and reconnecting the <a href="https://en.wikipedia.org/wiki/USB">USB</a> cable and
  2010. power cycling the indoor station.  Now I have two stations, so I tried the other.  All in
  2011. vain.
  2012.      </p>
  2013.  
  2014.      <p>
  2015. It took me some time to discover that I had two <i>wh1080</i> processes running, and they
  2016. were treading on their toes.  Stop everything and start again and things started stumbling
  2017. on.  But that doesn't explain the loss of information for the whole afternoon.
  2018.      </p>
  2019.  
  2020.      <p>
  2021. So for once it was my fault.  Should I bother to put in some more tests?
  2022.      </p>
  2023.      </div>
  2024.    ]]>
  2025.  </description>
  2026.  <dc:creator>Greg Lehey</dc:creator>
  2027.  <dc:date>2025-06-07T05:28:33+00:00</dc:date>
  2028. </item>
  2029.  
  2030.            
  2031. <item>
  2032. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250607-060446</guid>
  2033. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250607-060446</link>
  2034. <category>technology</category>
  2035. <category>opinion</category>
  2036. <title>tiwi disk problems?</title>
  2037.  <description>
  2038.    <![CDATA[
  2039.    <div align="justify">
  2040.      <p>
  2041. While looking at <i>tiwi</i>'s log files, saw this:
  2042.      </p>
  2043.  
  2044.      <blockquote class="fullwidth">
  2045. <div style="text-align:left">
  2046.  <tt>
  2047. Jun &nbsp;6 12:15:16 tiwi kernel: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 358465, size: 65536
  2048. <br />Jun &nbsp;6 12:15:16 tiwi kernel: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 290150, size: 4096
  2049. <br />Jun &nbsp;6 12:18:32 tiwi kernel: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 279446, size: 4096
  2050. <br />
  2051.  </tt>
  2052. </div>
  2053. </blockquote>
  2054.  
  2055.      <p>
  2056. That doesn't look good.  That's normally an indication of a dying disk, but normally that
  2057. would be indicated by other error messages as well.  That's all I need.
  2058.      </p>
  2059.      </div>
  2060.    ]]>
  2061.  </description>
  2062.  <dc:creator>Greg Lehey</dc:creator>
  2063.  <dc:date>2025-06-07T06:04:46+00:00</dc:date>
  2064. </item>
  2065.  
  2066.                  
  2067. <item>
  2068. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250608-020950</guid>
  2069. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250608-020950</link>
  2070. <category>technology</category>
  2071. <category>general</category>
  2072. <category>opinion</category>
  2073. <title>More weather station woes</title>
  2074.  <description>
  2075.    <![CDATA[
  2076.    <div align="justify">
  2077.      <p>
  2078. Why do <i>both</i> weather stations fail to communicate at particular times?  I had assumed
  2079. that the old one was gradually dying, but the new one does it too, roughly at the same time
  2080. as the old one.  Surely it can't be the location.  Here's an example:
  2081.      </p>
  2082.  
  2083.        <a id="Photo-18" name="Photo-18"
  2084.          href="diary-jun2025.php?dirdate=20250608&amp;imagesizes=1111111111111111112&amp;topics=c&amp;edit=0#Photo-18">
  2085.          <img alt="This should be Weather-station-7.jpeg.  Is it missing?" border="0" id="Photo_18"
  2086.               title="Photo Weather-station-7.jpeg.  Click to redisplay larger version of image."
  2087.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250608/small/Weather-station-7.jpeg"
  2088.               width="225" height="300"
  2089.           /></a>
  2090.        <a id="Photo-19" name="Photo-19"
  2091.          href="diary-jun2025.php?dirdate=20250608&amp;imagesizes=11111111111111111112&amp;topics=c&amp;edit=0#Photo-19">
  2092.          <img alt="This should be Weather-station-6-detail.jpeg.  Is it missing?" border="0" id="Photo_19"
  2093.               title="Photo Weather-station-6-detail.jpeg.  Click to redisplay larger version of image."
  2094.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250608/small/Weather-station-6-detail.jpeg"
  2095.               width="264" height="256"
  2096.           /></a>
  2097.  
  2098.      <p>
  2099. The weather station is clearly visible about 12 m away.  And the unit is supposed to have a
  2100. range of 100 m.
  2101.      </p>
  2102.  
  2103.      <p>
  2104. What's wrong?  One clue is that it seems to happen to both stations at the same time.  Could
  2105. it be that there is severe <a href="https://en.wikipedia.org/wiki/RFI">RFI</a> from
  2106. time to time?  It can't be anything obvious like our computers, since it is intermittent but
  2107. long-lasting.  I can't make up my mind what it could be.  Potentially it would make a
  2108. difference if I moved the unit to the other side of the house.
  2109.      </p>
  2110.  
  2111.      <p>
  2112. But there are more issues.  The two outside units are next to each other, and one indoor
  2113. unit is connected to each.  Before the communication failed, they displayed markedly
  2114. different temperatures and pressures:
  2115.      </p>
  2116.  
  2117.        <a id="Photo-20" name="Photo-20"
  2118.          href="diary-jun2025.php?dirdate=20250607&amp;imagesizes=111111111111111111112&amp;topics=c&amp;edit=0#Photo-20">
  2119.          <img alt="This should be Weather-station-2.jpeg.  Is it missing?" border="0" id="Photo_20"
  2120.               title="Photo Weather-station-2.jpeg.  Click to redisplay larger version of image."
  2121.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250607/small/Weather-station-2.jpeg"
  2122.               width="297" height="227"
  2123.           /></a>
  2124.        <a id="Photo-21" name="Photo-21"
  2125.          href="diary-jun2025.php?dirdate=20250607&amp;imagesizes=1111111111111111111112&amp;topics=c&amp;edit=0#Photo-21">
  2126.          <img alt="This should be Weather-station-4.jpeg.  Is it missing?" border="0" id="Photo_21"
  2127.               title="Photo Weather-station-4.jpeg.  Click to redisplay larger version of image."
  2128.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250607/small/Weather-station-4.jpeg"
  2129.               width="299" height="225"
  2130.           /></a>
  2131.  
  2132.      <p>
  2133. The first unit is connected to the new station.  The outside temperature is in the second
  2134. line at the left (9.8°, 75% humidity, or 8.6° and 82% humidity).  The barometric prssure is
  2135. on the right of the third line (961.3 mbar or 958.2 mbar).  These photos were taken 10
  2136. seconds apart.  How can I rely on something like that?
  2137.      </p>
  2138.      </div>
  2139.    ]]>
  2140.  </description>
  2141.  <dc:creator>Greg Lehey</dc:creator>
  2142.  <dc:date>2025-06-08T02:09:50+00:00</dc:date>
  2143. </item>
  2144.  
  2145.            
  2146. <item>
  2147. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250608-021003</guid>
  2148. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250608-021003</link>
  2149. <category>technology</category>
  2150. <category>photography</category>
  2151. <title>Photo backup finished</title>
  2152.  <description>
  2153.    <![CDATA[
  2154.    <div align="justify">
  2155.      <p>
  2156. My 8&nbsp;TB photo backup ran smoothly and completed in almost exactly 24 hours:
  2157.      </p>
  2158.  
  2159.      <blockquote class="fullwidth">
  2160. <div style="text-align:left">
  2161.  <tt>
  2162. sent 7,824,233,002,625 bytes &nbsp;received 39,695,113 bytes &nbsp;91,034,429.89 bytes/sec
  2163. <br />total size is 8,657,590,230,554 &nbsp;speedup is 1.11
  2164. <br />Filesystem 1048576&#45;blocks &nbsp; &nbsp; &nbsp;Used &nbsp; &nbsp; Avail Capacity &nbsp; iused &nbsp; &nbsp; ifree %iused &nbsp;Mounted on
  2165. <br />/dev/da2p1 &nbsp; &nbsp; 15,257,008 7,498,588 7,605,849 &nbsp; &nbsp;50% 1,814,798 4,671,344 &nbsp; 28% &nbsp; /pb1
  2166. <br />Fri 6 Jun 2025 16:29:59 AEST Photo backup started
  2167. <br />Sat 7 Jun 2025 16:29:19 AEST Photo backup ended
  2168. <br />
  2169.  </tt>
  2170. </div>
  2171. </blockquote>
  2172.  
  2173.      <p>
  2174. And <i>once again</i> the size of the disks isn't the same:
  2175.      </p>
  2176.  
  2177.      <blockquote class="fullwidth">
  2178. <div style="text-align:left">
  2179.  <tt>
  2180. <code><font color="blue">=== root@eureka (/dev/pts/1)</font> <font color="red">/videobackup</font> <font color="blue">96</font> &#45;&gt; <b><tt>df &#45;i /Photos /pb1/</tt></b></code>
  2181. <br />Filesystem &nbsp;1048576&#45;blocks &nbsp; &nbsp; &nbsp;Used &nbsp; &nbsp; Avail Capacity &nbsp; iused &nbsp; &nbsp; ifree %iused &nbsp;Mounted on
  2182. <br />/dev/ada1p1 &nbsp; &nbsp; 15,257,008 7,507,545 7,596,893 &nbsp; &nbsp;50% 1,791,574 4,694,568 &nbsp; 28% &nbsp; /Photos
  2183. <br />/dev/da2p1 &nbsp; &nbsp; &nbsp;15,257,008 7,498,588 7,605,849 &nbsp; &nbsp;50% 1,814,798 4,671,344 &nbsp; 28% &nbsp; /pb1
  2184. <br />
  2185.  </tt>
  2186. </div>
  2187. </blockquote>
  2188.  
  2189.      <p>
  2190. I see that so often.  What's causing it?  The <i>newfs</i> parameters were identical.  I
  2191. suppose I should check more carefully with the second disk.
  2192.      </p>
  2193.      </div>
  2194.    ]]>
  2195.  </description>
  2196.  <dc:creator>Greg Lehey</dc:creator>
  2197.  <dc:date>2025-06-08T02:10:03+00:00</dc:date>
  2198. </item>
  2199.  
  2200.      
  2201.      
  2202. <!-- topic po not selected
  2203.      <p>
  2204. There's a <a href="https://www.venuslens.net/product/laowa-8-15mm-f-2-8-ff-zoom-fisheye-2/">new fisheye
  2205. zoom lens</a> on the market.  It's for “full frame” cameras, so nothing that I would buy,
  2206. but a statement caught my eye:
  2207.      </p>
  2208.  
  2209.      <blockquote class="fullwidth">
  2210.        <div class="listitemwidth">
  2211.          It delivers a dual fisheye effect...
  2212.        </div>
  2213.      </blockquote>
  2214.  
  2215.      <p>
  2216. Reviewers expanded on this and suggested two different projections.  <a href="https://www.dpreview.com/news/3643955286/fast-and-wide-laowa-unveils-an-8-15mm-f-2p8-zoom-fisheye-lens">DPreview</a> writes
  2217.      </p>
  2218.  
  2219.      <blockquote class="fullwidth">
  2220.        <div class="listitemwidth">
  2221.  Laowa's latest lens offers two types of fisheye perspective with a fast and constant F2.8
  2222.  aperture.
  2223.        </div>
  2224.      </blockquote>
  2225.  
  2226.      <p>
  2227. That would be interesting, since most fisheye makers don't even bother to say what
  2228. projection they're using.  And I was wondering how they change the projection.  But no,
  2229. they're just stating the obvious, that the sensor coverage changes from circular at 8 mm to
  2230. full-frame at 15 mm.  Wow!  And of course the perspective remains identical.  Crop an 8 mm
  2231. image and you'll get exactly the same perspective as an image taken at 15 mm.
  2232.      </p>
  2233.  
  2234.      <p>
  2235. But the claim of circular fisheye is not completely correct.  My field of view program tells
  2236. me that the vertical field of view at 8 mm is 171.9°, not quite the 180° that you'd expect.
  2237. And then there's:
  2238.      </p>
  2239.  
  2240.      <blockquote class="fullwidth">
  2241.        <div class="listitemwidth">
  2242.           It allows for a shallow depth of field,
  2243.        </div>
  2244.      </blockquote>
  2245.  
  2246.      <p>
  2247. This is an f/2.8 lens.  At 15 mm and full aperture, the <a href="https://en.wikipedia.org/wiki/Hyperfocal_distance">hyperfocal distance</a> is 10 m.
  2248. At 1 m the depth of field is 20 cm.  Shallow depth of field indeed!
  2249.      </p>
  2250.      
  2251. End deselected topic po (Variable projection fisheye) -->
  2252.  
  2253.      
  2254.      
  2255. <!-- topic kpo not selected
  2256.      <p>
  2257. <a href="http://www.lemis.com/grog/recipes/tagine-abricots-amandes.php">Tagine d'agneau aux abricots et
  2258. amandes</a> for dinner tonight, a chance to take some more photos.
  2259.      </p>
  2260.  
  2261.      <p>
  2262. The recipe calls for <a href="https://en.wikipedia.org/wiki/Ras-el-hanout">ras-el-hanout</a>.  And we don't have any.  What do I do?  Ask <a href="https://gemini.google.com/">Google Gemini</a>, which suggested a number of things,
  2263. including cloves and cardamom.  That seemed reasonable.
  2264.      </p>
  2265.  
  2266.      <p>
  2267. We also didn't have enough almonds, so we made up for it with <a href="https://en.wikipedia.org/wiki/Pistachio">pistachio</a> kernels.
  2268.      </p>
  2269.  
  2270.      <p>
  2271. And then there were the <a href="https://en.wikipedia.org/wiki/Chick_pea">chick
  2272. peas</a>.  I didn't note anything in the recipe.  Shouldn't they be cooked for a long
  2273. time?  Yes, like beans.  Boiled them for 5 minutes, during which they doubled in size, and
  2274. then put them in at the beginning.  They were edible but still quite firm.  Next time I
  2275. should cook them for an hour or two first.
  2276.      </p>
  2277.  
  2278.      <p>
  2279. How did it taste?  Alright, but it's still missing something.  Quantities: 393 g for me, 173
  2280. for <a href="http://www.lemis.com/yvonne/">Yvonne</a>, a total of 566 g.  We'll eat it again on Tuesday,
  2281. and then we should have weights for freezer portions.
  2282.      </p>
  2283.      
  2284. End deselected topic kpo (Tagine) -->
  2285.  
  2286.                  
  2287. <!-- topic h not selected
  2288.      <p>
  2289. It has been an extremely dry autumn, but that changed today.  Overnight we had 15 mm rain,
  2290. and it rained the whole day.  By evening one of the rain gauges had gone off the scale
  2291. (which means at least another 30 mm).  The usual rain into the house entrance:
  2292.      </p>
  2293.  
  2294.      
  2295.      <p>
  2296. And a test of the relocation of our house water pump:
  2297.      </p>
  2298.  
  2299.      
  2300.      <p>
  2301. <a href="http://www.lemis.com/yvonne/">Yvonne</a> was concerned, but I think it's high enough for water
  2302. to overflow first.
  2303.      </p>
  2304.      
  2305. End deselected topic h (The drought breaks) -->
  2306.  
  2307.            
  2308. <!-- topic po not selected
  2309.      <p>
  2310. My weather station woes continue, so yesterday I took a photo to show how close the inside
  2311. and outside units are to each other.
  2312.      </p>
  2313.  
  2314.      <p>
  2315. Oh:
  2316.      </p>
  2317.  
  2318.      
  2319.      <p>
  2320. The indoor units are at the extreme right and in front of the glass cabinet.  But where are
  2321. the outside units?  I had chosen this view to show them, but there were other issues.
  2322. First, the angle of view, which required a very wide angle.  And then the difference in
  2323. brightness between inside and outside, and also the difference in distance, which required
  2324. both <a href="https://en.wikipedia.org/wiki/High-dynamic-range_imaging">HDR</a> and
  2325. <a href="https://en.wikipedia.org/wiki/Focus_stacking">focus stacking</a>.  So I put
  2326. the camera on a tripod and took a number of photos.  What do I process it with?  <a href="http://www.hdrsoft.com/">Photomatix</a> creates HDR images, <a href="https://zerenesystems.com">Zerene</a> does focus stacking.  But in this case it's
  2327. relatively clear: the images were 4.3 <a href="https://en.wikipedia.org/wiki/Exposure_value">EV</a> apart, so there wasn't much
  2328. choice in focus.  And sure enough, it came out sharp enough, though not as needle sharp as I
  2329. had expected from the originals.
  2330.      </p>
  2331.  
  2332.      <p>
  2333. But I had made the mistake of not raising the tripod to my eye height, so the weather
  2334. stations disappeared behind the palisade.  Don't do that, then.
  2335.      </p>
  2336.  
  2337.      <p>
  2338. Try again today.  In the meantime, the inside units had failed completely.  Due to the rain?
  2339. I haven't seen any connection before.  So I put one up against the window, where the
  2340. distance was even less, and the angle of view as well:
  2341.      </p>
  2342.  
  2343.      
  2344.      <p>
  2345. And this time I cheated by using the indoor flash, which worked up to a point.  There were
  2346. reflections in the window, and the indoor unit was still underexposed:
  2347.      </p>
  2348.  
  2349.      
  2350.      <p>
  2351. So yes, HDR seems to be the way to go, but I've expended enough on the matter.
  2352.      </p>
  2353.  
  2354.      <p>
  2355. I didn't notice this detail until after processing the images:
  2356.      </p>
  2357.  
  2358.      
  2359.      <p>
  2360. That's <a href="http://www.lemis.com/grog/Albums/Animals/Bruno.php">Bruno</a>, who was polite enough to
  2361. remain effectively still during the 70 seconds between my composite images.
  2362.      </p>
  2363.  
  2364.      <p>
  2365. And the weather station?  I've repositioned the new one on the table on the verandah, where
  2366. it works.  But why are things so bad?  Can it be the metal plant frame between the units?
  2367. That shouldn't make any difference, but I can check by moving the indoor unit.  Somehow it
  2368. seems as if there's some environmental issue, so just replacing the unit won't help.
  2369.      </p>
  2370.      
  2371. End deselected topic po (How to take a photo) -->
  2372.  
  2373.            
  2374. <item>
  2375. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250609-030409</guid>
  2376. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250609-030409</link>
  2377. <category>photography</category>
  2378. <category>technology</category>
  2379. <category>opinion</category>
  2380. <title>OM-1 firmware bug</title>
  2381.  <description>
  2382.    <![CDATA[
  2383.    <div align="justify">
  2384.      <p>
  2385. While planning the photos of the weather stations, tried taking a photo with the <a href="https://en.wikipedia.org/wiki/OM_System_OM-1_Mark_II">OM System OM-1 Mark II</a> and
  2386. the <a href="https://www.panasonic.com/au/consumer/lumix-cameras-video-cameras/lumix-camera-lenses/lumix-g-lenses/h-x015gc9-k.html">Leica DG Summilux 15 mm f/1.7 <b>ASPH.</b></a>.  I couldn't autofocus!  Much examination
  2387. showed that there's some compatibility issue between camera and lens.  The lens works fine
  2388. on the <a href="https://en.wikipedia.org/wiki/Olympus_OM-D_E-M5_Mark_III">Olympus OM-D
  2389. E-M5 Mark III</a>, the <a href="https://en.wikipedia.org/wiki/Olympus_OM-D_E-M1_Mark_II">Olympus OM-D E-M1 Mark II</a> and the <a href="https://www.dpreview.com/products/olympus/slrs/oly_epm2/review">Olympus E-PM2</a>, and it works with the OM-1 Mark III as long as it's not set on C-AF autofocus.
  2390.      </p>
  2391.  
  2392.      <p>
  2393. Why?  The Summilux is unique amongst my <a href="https://en.wikipedia.org/wiki/Micro_Four_Thirds_system">Micro Four Thirds system</a>        lenses because it has an aperture ring.  It also has an AF/MF switch, but others have that
  2394.        too.  And all works as expected on Olympus/OM System cameras.  But somehow the OM-1 Mark II
  2395.        (and presumably Mark I as well) has an issue.
  2396.      </p>
  2397.  
  2398.      <p>
  2399. How do I report firmware bugs to OM System?
  2400.      </p>
  2401.      </div>
  2402.    ]]>
  2403.  </description>
  2404.  <dc:creator>Greg Lehey</dc:creator>
  2405.  <dc:date>2025-06-09T03:04:09+00:00</dc:date>
  2406. </item>
  2407.  
  2408.                  
  2409. <!-- topic ho not selected
  2410.      <p>
  2411. It's been intolerably dry for months now, and we've been waiting for rain.  Finally it has
  2412. come: 15 mm yesterday, 63 mm today.  78 mm in a little over 24 hours, coming close to the 24
  2413. hour value of 69 mm that we had <a href="http://www.lemis.com/grog/diary-feb2008.php#6">17 years
  2414. ago</a>.
  2415.      </p>
  2416.  
  2417.      <p>
  2418. Interestingly, the rainfall in <a href="http://www.bom.gov.au/climate/averages/tables/cw_089002_All.shtml">Ballarat</a>, only
  2419. 30 km away, was considerably less, only 35.4 mm.  It seems that the highest daily June
  2420. rainfall there was only 46.2 mm, on <a href="http://www.lemis.com/grog/diary-jun2023.php?topics=c#8">8 June 2023</a>, a day where we only
  2421. had 28 mm.  Still, <i>finally</i> it seems that the drought has broken.
  2422.      </p>
  2423.  
  2424.      <p>
  2425. Or, as <a href="https://en.wikipedia.org/wiki/ABC">ABC</a> reported this morning (as
  2426. of 8:27),
  2427.      </p>
  2428.  
  2429.      
  2430.      <p>
  2431. There's nothing like up-to-date news. Yes, that's nothing like up-to-date news.
  2432.      </p>
  2433.      
  2434. End deselected topic ho (Rain!) -->
  2435.  
  2436.            
  2437. <!-- topic ah not selected
  2438.      <p>
  2439. Deirdre MacIntosh along today with husband Don, son Jake and a gift: <a href="http://www.lemis.com/grog/Albums/Animals/Morena.php">AuSome Morena</a>, a <a href="https://en.wikipedia.org/wiki/Paso_Fino">Paso Fino</a>/<a href="https://en.wikipedia.org/wiki/Paso_peruano">Paso peruano</a> mare bred by Jorge de
  2440. Moya.
  2441.      </p>
  2442.  
  2443.            
  2444.      <p>
  2445. They didn't stay long: they had come from <a href="https://en.wikipedia.org/wiki/Flowerdale,_Victoria">Flowerdale</a>, an <a href="http://www.lemis.com/grog/warstories/police.php">important place</a> in my mother's
  2446. past, and they wanted to get back.
  2447.      </p>
  2448.      
  2449. End deselected topic ah (Ausome!  Morena!) -->
  2450.  
  2451.            
  2452. <item>
  2453. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250609-232007</guid>
  2454. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250609-232007</link>
  2455. <category>technology</category>
  2456. <category>photography</category>
  2457. <title>Testing JPEG integrity</title>
  2458.  <description>
  2459.    <![CDATA[
  2460.    <div align="justify">
  2461.      <p>
  2462. So I have migrated one of my backup disks to the new 16&nbsp;TB drive.  The old 8&nbsp;TB is
  2463. free for other purposes, and I have it earmarked for videos.
  2464.      </p>
  2465.  
  2466.      <p>
  2467. But what if some of the images on the new disk are corrupt, and they're good on the old
  2468. disk.  That could happen, since many of the files on the old disk have been there for years,
  2469. and it's not beyond the bounds of possibility that they could have been damaged on the main
  2470. disk.  How do I check them?  <a href="https://gemini.google.com/">Google Gemini</a> to my aid.  It came up with some interesting stuff: <a href="https://github.com/tjko/jpeginfo"><i>jpeginfo</i></a>, of which I had never heard, and
  2471. also information that <a href="https://en.wikipedia.org/wiki/ImageMagick">ImageMagick</a>'s <i>identify</i> command will provide information with
  2472. the <tt>-verbose</tt> flag, and <a href="https://en.wikipedia.org/wiki/Exiftool"><i>exiftool</i></a> has a <tt>-validate</tt> option.
  2473.      </p>
  2474.  
  2475.      <p>
  2476. Installed <i>jpeginfo</i>, which is in the <a href="https://www.freebsd.org/">FreeBSD</a> Ports Collection, and it seems to do what I want.  Now I just need to run it
  2477. against my hundreds of thousands of files.  And it still doesn't address the issue of
  2478. corrupt raw files, which, I suspect, is a lost cause.
  2479.      </p>
  2480.      </div>
  2481.    ]]>
  2482.  </description>
  2483.  <dc:creator>Greg Lehey</dc:creator>
  2484.  <dc:date>2025-06-09T23:20:07+00:00</dc:date>
  2485. </item>
  2486.  
  2487.            
  2488. <item>
  2489. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250609-234329</guid>
  2490. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250609-234329</link>
  2491. <category>technology</category>
  2492. <category>opinion</category>
  2493. <title>Favourite Unix artefacts</title>
  2494.  <description>
  2495.    <![CDATA[
  2496.    <div align="justify">
  2497.      <p>
  2498. “segaloco”, one of the more active participants on the <a href="https://www.tuhs.org/">Unix Heritage Society</a> <a href="https://www.tuhs.org/pipermail/tuhs/">mailing
  2499. list</a>, came up with a question: <a href="https://www.tuhs.org/pipermail/tuhs/2025-June/032020.html">“Your Most Prized UNIX
  2500. Artifacts?”</a>.
  2501.      </p>
  2502.  
  2503.      <p>
  2504. Interesting question.  Unix is software.  What can you keep?  Source trees?  The freely
  2505. available ones are on <a href="https://www.tuhs.org/cgi-bin/utree.pl">the TUHS site</a>.  People won't admit to keeping clandestine copies of copyrighted material.  And of
  2506. course none of the replies referred to source trees.  The single most mentioned artefact was
  2507. the UNIX “Live free or die” registration plate.
  2508.      </p>
  2509.  
  2510.      <p>
  2511. And for me?  From my reply, with additions:
  2512.      </p>
  2513.  
  2514.      <ul>
  2515.        <li class="fullwidth">
  2516.          <div class="listitemwidth">
  2517.             UNIX registration plate.  Yes, one of the very last, with COMPAQ written on it.  I
  2518.     picked it up at the USENIX ATC in Boston, 2001.
  2519.          </div>
  2520.        </li>
  2521.  
  2522.        <li class="fullwidth">
  2523.          <div class="listitemwidth">
  2524.             Lions Commentary.  Yes, I got a copy of it some time round 1990, and sadly lost it
  2525.     again.  But then Warren Toomey posted the TeX sources of a scanned version
  2526.     on <tt>alt.foklore.computers</tt> in May 1994, and I formatted them put them up on the
  2527.     web at <a href="http://www.lemis.com/grog/Documentation/Lions/">http://www.lemis.com/grog/Documentation/Lions/</a>, where
  2528.     they're still accessible.
  2529.          </div>
  2530.        </li>
  2531.  
  2532.        <li class="fullwidth">
  2533.          <div class="listitemwidth">
  2534.             Lots of other books.  Where do I start?  I have two bookshelves full of books, but none
  2535.     that I'd consider "most prized".  I have two copies of "The Magic Garden Explained" by
  2536.     Berny Goodheart (who didn't sign his copy) and James Cox (who did).  This book is
  2537.     interesting because it grew out of the environment in which I had worked at Tandem
  2538.     Computers.
  2539.          </div>
  2540.        </li>
  2541.  
  2542.        <li class="fullwidth">
  2543.          <div class="listitemwidth">
  2544.             What I <i>do</i> have and "prize" is mainly hardware.  To the right of my desktop I
  2545.     have, in increasing order of rarity, a microVAX that I think runs some version of Unix,
  2546.     a Control Data Cyber 910 that ran Irix 5.2 and a Tandem LXN (based on a Motorola 68020)
  2547.     that ran System V.2.  I think the LXN might be the only one that still exists.  Its
  2548.     name was <i>solo</i> (only 1 CPU) in contrast with our "real" Unix box, a <a href="https://www.techmonitor.ai/technology/tandem_promises_unix_system_v4_on_new_integrity_s2_machine_as_soon_as_it_is_stable">Tandem Integrity S2</a> which had 3 lock-step processors and was thus called trio.
  2549.     The Magic Garden contains a reference *somewhere* to a machine called quattro, for
  2550.     reason that evade me, but were clearly intended to fit into this naming scheme.
  2551.          </div>
  2552.        </li>
  2553.  
  2554.        <li class="fullwidth">
  2555.          <div class="listitemwidth">
  2556.            The T-shirt with the deflated AT&amp;T death star on the points of the <a href="https://en.wikipedia.org/wiki/BSD">BSD</a> daemon trident, the one that <a href="https://en.wikipedia.org/wiki/Dennis_Ritchie">dmr</a> got so upset about at the
  2557.            start of the <a href="https://en.wikipedia.org/wiki/Unix_wars">Unix wars</a>.  I
  2558.            got it from <a href="https://en.wikipedia.org/wiki/Kirk_McKusick">Kirk McKusick</a> on <a href="http://www.lemis.com/grog/diary-sep1993.php?topics=c#27">27 September 1993</a>.
  2559.          </div>
  2560.        </li>
  2561.      </ul>
  2562.  
  2563.      <p>
  2564. One of the more unexpected <a href="https://www.tuhs.org/pipermail/tuhs/2025-June/032027.html">replies</a> was from Pete
  2565. Wright:
  2566.      </p>
  2567.  
  2568.      <blockquote class="fullwidth">
  2569.        <div class="listitemwidth">
  2570.  A print of a draft of The Complete FreeBSD 4th ed. signed by Greg Lehey.  Still sitting in
  2571.  its original manila envelope by my desk.
  2572.        </div>
  2573.  
  2574. <p class="listitemwidth">
  2575.  A friend (thanks .ike!) got it and gifted it to me when I ended up in the hospital the
  2576.  night before I was supposed to attend BSDCan '05 and couldn't attend.  Lots of sentimental
  2577.  value for me in that one for me.
  2578. </p>
  2579.      </blockquote>
  2580.  
  2581.      <p>
  2582. What an honour.  I was one of the very few living people mentioned by name.
  2583.      </p>
  2584.      </div>
  2585.    ]]>
  2586.  </description>
  2587.  <dc:creator>Greg Lehey</dc:creator>
  2588.  <dc:date>2025-06-09T23:43:29+00:00</dc:date>
  2589. </item>
  2590.  
  2591.            
  2592. <item>
  2593. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250610-024920</guid>
  2594. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250610-024920</link>
  2595. <category>technology</category>
  2596. <category>photography</category>
  2597. <category>opinion</category>
  2598. <title>eBay lies, or, where's my lens?</title>
  2599.  <description>
  2600.    <![CDATA[
  2601.    <div align="justify">
  2602.      <p>
  2603. Exchanged email with <a href="http://www.lemis.com/yana/">Yana</a> this morning.  How's the new lens
  2604. that I bought for her <a href="http://www.lemis.com/grog/diary-may2025.php?subtitle=Another%20new%20Summilux?&amp;article=D-20250528-023530#D-20250528-023530">nearly 2 weeks ago</a>?  Send me some sample images.  I hadn't told her about the
  2605. purchase, but she picked it up from the post office last Wednesday, and for some reason
  2606. didn't comment.
  2607.      </p>
  2608.  
  2609.      <p>
  2610. She sent me some sample images—from the <a href="https://www.panasonic.com/au/consumer/lumix-cameras-video-cameras/lumix-camera-lenses/lumix-g-lenses/h-x015gc9-k.html">Leica DG Summilux 15 mm f/1.7 <b>ASPH.</b></a> that I bought for her <a href="http://www.lemis.com/grog/diary-may2025.php?subtitle=eBay%20payment%20pain&amp;article=D-20250503-015000#D-20250503-015000">over a month ago</a>.  And the new lens?  What new lens?
  2611.      </p>
  2612.  
  2613.      <p>
  2614. This one:
  2615.      </p>
  2616.  
  2617.        <a id="Photo-22" name="Photo-22"
  2618.          href="diary-jun2025.php?dirdate=20250604&amp;imagesizes=11111111111111111111112&amp;topics=c&amp;edit=0#Photo-22">
  2619.          <img alt="This should be eBay-2-detail.jpeg.  Is it missing?" border="0" id="Photo_22"
  2620.               title="Photo eBay-2-detail.jpeg.  Click to redisplay larger version of image."
  2621.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250604/small/eBay-2-detail.jpeg"
  2622.               width="298" height="227"
  2623.           /></a>
  2624.  
  2625.      <p>
  2626. Ha ha, only joking.  <a href="https://en.wikipedia.org/wiki/Australia_Post">Australia
  2627. Post</a> couldn't deliver it, so they took it to the post office for pickup, and didn't
  2628. bother leaving a notification.  So it's still there!
  2629.      </p>
  2630.  
  2631.      <p>
  2632. I've had issues with tracking and delivery with eBay and Auspost, but this really takes the
  2633. cake.
  2634.      </p>
  2635.      </div>
  2636.    ]]>
  2637.  </description>
  2638.  <dc:creator>Greg Lehey</dc:creator>
  2639.  <dc:date>2025-06-10T02:49:20+00:00</dc:date>
  2640. </item>
  2641.  
  2642.                  
  2643. <!-- topic h not selected
  2644.      <p>
  2645. Somehow the last few days have been particularly busy.  Finally I had time to catch up today
  2646. and address most of the mail that has been waiting for me.  I still didn't make it all.
  2647.      </p>
  2648.      
  2649. End deselected topic h (Catching up) -->
  2650.  
  2651.            
  2652. <!-- topic a not selected
  2653.      <p>
  2654. Seen in the paddock to the south of Grassy Gully Road:
  2655.      </p>
  2656.  
  2657.      
  2658.      <p>
  2659. Clearly John has arrived behind the hill to feed them.
  2660.      </p>
  2661.      
  2662. End deselected topic a (Feeding time) -->
  2663.  
  2664.                  
  2665. <item>
  2666. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250612-023507</guid>
  2667. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250612-023507</link>
  2668. <category>technology</category>
  2669. <category>opinion</category>
  2670. <title>Google Maps and Android: what a pair!</title>
  2671.  <description>
  2672.    <![CDATA[
  2673.    <div align="justify">
  2674.      <p>
  2675. Into town today.  Apart from a haircut and a visit to the <a href="https://www.facebook.com/Fruits.shack.Wendouree/">Fruit Shack</a>, <a href="http://www.lemis.com/yvonne/">Yvonne</a> wanted to look at a carpet for sale in <a href="https://en.wikipedia.org/wiki/Mount_Clear">Mount Clear</a>.  We were to meet there.
  2676. OK, get the directions from <a href="https://en.wikipedia.org/wiki/Google_Maps">Google
  2677. Maps</a> and send them to my phone.  See that the notification arrived, head off.  Enable
  2678. the route.  It's gone!  For no obvious reason, the notification had disappeared.  And the
  2679. only way to get the information, including the all-important address, would have been to go
  2680. back inside to a Real Computer and send it again.
  2681.      </p>
  2682.  
  2683.      <p>
  2684. No time for that.  But Yvonne had told me: down to the roundabout, first left, first left.
  2685. So I tried that.  It wasn't nearly as obvious as it sounded, and I found myself driving
  2686. around for a while.  But Yvonne was there: find her on the map and go to her.  And how about
  2687. that, I found her in <del>Cartilage</del> Cartledge Avenue.  I recognized that name: the
  2688. house is there.  But she went straight across the road and back the way I had come from.
  2689. OK, follow her.  After a while she stopped, leaving me blocking an intersection, and told me
  2690. that her phone had claimed she had arrived when she was 500 m from the destination.
  2691. Fortunately, round that time, the people we want to visit called and gave us the exact
  2692. address.
  2693.      </p>
  2694.  
  2695.      <p>
  2696. The carpet itself was a disappointment, but I discovered that there was a much easier way
  2697. back to <a href="https://en.wikipedia.org/wiki/Sebastopol,_Victoria">Sebastopol</a>:
  2698. just head up west on Cartledge Avenue, turn left onto Tinworth Avenue and we'd hit
  2699. Whitehorse Road, the road to Sebastopol.  In Tinworth Avenue I asked Google Maps to take me
  2700. to <a href="https://www.arabellahairdesign.au/">Arabella</a>.  But instead of giving
  2701. me a route, it held a lecture about where it might be.  When I finally got it to shut up, it
  2702. disagreed with my route.  Turn back and go down Cartledge Avenue, 1.1 km further.  Ignored
  2703. that and headed onwards, where there were no issues beyond traffic on Whitehorse Road.
  2704.      </p>
  2705.  
  2706.      <p>
  2707. Done?  Not at all.  Driving on to the Fruit Shack, it lost its mind, or at least its vision:
  2708.      </p>
  2709.  
  2710.        <a id="Photo-23" name="Photo-23"
  2711.          href="diary-jun2025.php?dirdate=20250611&amp;imagesizes=111111111111111111111112&amp;topics=c&amp;edit=0#Photo-23">
  2712.          <img alt="This should be Google-Maps-fail-2.jpeg.  Is it missing?" border="0" id="Photo_23"
  2713.               title="Photo Google-Maps-fail-2.jpeg.  Click to redisplay larger version of image."
  2714.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250611/small/Google-Maps-fail-2.jpeg"
  2715.               width="387" height="174"
  2716.           /></a>
  2717.        <a id="Photo-24" name="Photo-24"
  2718.          href="diary-jun2025.php?dirdate=20250611&amp;imagesizes=1111111111111111111111112&amp;topics=c&amp;edit=0#Photo-24">
  2719.          <img alt="This should be Google-Maps-fail-3.jpeg.  Is it missing?" border="0" id="Photo_24"
  2720.               title="Photo Google-Maps-fail-3.jpeg.  Click to redisplay larger version of image."
  2721.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250611/small/Google-Maps-fail-3.jpeg"
  2722.               width="387" height="174"
  2723.           /></a>
  2724.  
  2725.      <p>
  2726. OK, maybe the app has got confused.  Stop, restart.
  2727.      </p>
  2728.  
  2729.        <a id="Photo-25" name="Photo-25"
  2730.          href="diary-jun2025.php?dirdate=20250611&amp;imagesizes=11111111111111111111111112&amp;topics=c&amp;edit=0#Photo-25">
  2731.          <img alt="This should be Google-Maps-fail-5.jpeg.  Is it missing?" border="0" id="Photo_25"
  2732.               title="Photo Google-Maps-fail-5.jpeg.  Click to redisplay larger version of image."
  2733.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250611/small/Google-Maps-fail-5.jpeg"
  2734.               width="387" height="174"
  2735.           /></a>
  2736.  
  2737.      <p>
  2738. Still no map, but it had decided that I should go by foot!  How do I change that?  It took
  2739. me 5 minutes to find that it had hidden the choice of transport down some unlikely menu at
  2740. bottom left.  Finally I briefly emerged from the darkness:
  2741.      </p>
  2742.  
  2743.        <a id="Photo-26" name="Photo-26"
  2744.          href="diary-jun2025.php?dirdate=20250611&amp;imagesizes=111111111111111111111111112&amp;topics=c&amp;edit=0#Photo-26">
  2745.          <img alt="This should be Google-Maps-fail-7.jpeg.  Is it missing?" border="0" id="Photo_26"
  2746.               title="Photo Google-Maps-fail-7.jpeg.  Click to redisplay larger version of image."
  2747.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250611/small/Google-Maps-fail-7.jpeg"
  2748.               width="387" height="174"
  2749.           /></a>
  2750.  
  2751.      <p>
  2752. But that went away again, and it was still like that after I finished my shopping.  OK,
  2753. reboot the phone.  Then things worked.
  2754.      </p>
  2755.  
  2756.      <p>
  2757. Google, what a pair you have created!
  2758.      </p>
  2759.      </div>
  2760.    ]]>
  2761.  </description>
  2762.  <dc:creator>Greg Lehey</dc:creator>
  2763.  <dc:date>2025-06-12T02:35:07+00:00</dc:date>
  2764. </item>
  2765.  
  2766.            
  2767. <item>
  2768. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250612-031546</guid>
  2769. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250612-031546</link>
  2770. <category>technology</category>
  2771. <category>photography</category>
  2772. <category>opinion</category>
  2773. <title>Photo backups: the other shoe</title>
  2774.  <description>
  2775.    <![CDATA[
  2776.    <div align="justify">
  2777.      <p>
  2778. Backups to my first new disk went well.  Today's the day for the weekly swap, so put in the
  2779. second disk.  First, connect to <i>distress</i> to save the disk contents (one
  2780. Microsoft <i>Start_Here_Win.exe</i> and a whole slew of programs
  2781. in <i>Start_Here_Mac.app</i>).  That was a pain: to be on the safe side, I was running
  2782. the <i>CMD.EXE</i> as administrator, with the unexpected result that it didn't see any of my
  2783. “<a href="https://en.wikipedia.org/wiki/Network_share">network shares</a>”, and it
  2784. took me a while to work out what was wrong this time.
  2785.      </p>
  2786.  
  2787.      <p>
  2788. Preparing the disk for <a href="https://www.freebsd.org/">FreeBSD</a> was easier,
  2789. but not as easy as it should have been: I wrote down the steps <a href="http://www.lemis.com/grog/diary-jun2025.php?subtitle=More%20storage%20issues&amp;article=D-20250607-020524#D-20250607-020524">last week</a>, but I got them wrong (now corrected).  Here what I did today:
  2790.      </p>
  2791.  
  2792.      <p>
  2793. Get the <i>newfs</i> parameters from <i>/Photos</i> and use them to create the new file
  2794. system:
  2795.      </p>
  2796.  
  2797.      <blockquote class="fullwidth">
  2798. <div style="text-align:left">
  2799.  <tt>
  2800. <code><font color="blue">=== root@eureka (/dev/pts/0)</font> <font color="red">/videobackup/spool</font> <font color="blue">102</font> &#45;&gt; <b><tt>dumpfs &#45;m /Photos/</tt></b></code>
  2801. <br /># newfs command for /Photos/ (/dev/ada1p1)
  2802. <br />newfs &#45;L Photos &#45;O 2 &#45;U &#45;a 4 &#45;b 32768 &#45;d 32768 &#45;e 4096 &#45;f 4096 &#45;g 3145728 &#45;h 64 &#45;i 2469888 &#45;j &#45;k 1152 &#45;m 1 &#45;o space &#45;s 31251759024 /dev/ada1p1
  2803. <br /><code><font color="blue">=== root@eureka (/dev/pts/0)</font> <font color="red">/videobackup/spool</font> <font color="blue">102</font> &#45;&gt; <b><tt>newfs &#45;L Photobackup13 &#45;O 2 &#45;U &#45;a 4 &#45;b 32768 &#45;d 32768 &#45;e 4096 &#45;f 4096 &#45;g 3145728 &#45;h 64 &#45;i 2469888 &#45;j &#45;k 1152 &#45;m 1 &#45;o space &nbsp;/dev/da2p1</tt></b></code>
  2804. <br /><code><font color="blue">=== root@eureka (/dev/pts/0)</font> <font color="red">/videobackup/spool</font> <font color="blue">103</font> &#45;&gt; <b><tt>mount /dev/da2p1 /pb1</tt></b></code>
  2805.  </tt>
  2806. </div>
  2807. </blockquote>
  2808.  
  2809.      <p>
  2810. Create the file <i>Iam</i> in the root directory.  <i>syncphotos</i> uses this to identify
  2811. the drive.  Then run the backup:
  2812.      </p>
  2813.  
  2814.      <blockquote class="fullwidth">
  2815. <div style="text-align:left">
  2816.  <tt>
  2817. <code><font color="blue">=== root@eureka (/dev/pts/0)</font> <font color="red">/videobackup/spool</font> <font color="blue">112</font> &#45;&gt; <b><tt>cat > /pb1/Iam</tt></b></code>
  2818. <br />Greg's photo backup 13
  2819. <br /><code><font color="blue">=== root@eureka (/dev/pts/0)</font> <font color="red">/videobackup/spool</font> <font color="blue">113</font> &#45;&gt; <b><tt>mailme syncphotos /pb1</tt></b></code>
  2820. <br />Wed 11 Jun 2025 11:33:58 AEST Greg's photo backup 13
  2821. <br />&#45;rw&#45;r&#45;&#45;r&#45;&#45; &nbsp;1 root &nbsp;wheel &nbsp;23 11 Jun 11:33:53 2025 /pb1/Iam
  2822. <br />Filesystem 1048576&#45;blocks Used &nbsp; &nbsp; &nbsp;Avail Capacity iused &nbsp; &nbsp; ifree %iused &nbsp;Mounted on
  2823. <br />/dev/da2p1 &nbsp; &nbsp; 15,257,008 &nbsp; 32 15,104,406 &nbsp; &nbsp; 0% &nbsp; &nbsp; &nbsp; 4 6,486,138 &nbsp; &nbsp;0% &nbsp; /pb1
  2824. <br />
  2825.  </tt>
  2826. </div>
  2827. </blockquote>
  2828.  
  2829.      <p>
  2830. And that ran fine.  The only interesting thing was when I wanted to process a photo with
  2831. <a href="https://www.dxo.com/dxo-photolab/">DxO PhotoLab</a>:
  2832.      </p>
  2833.  
  2834.        <a id="Photo-27" name="Photo-27"
  2835.          href="diary-jun2025.php?dirdate=20250611&amp;imagesizes=1111111111111111111111111112&amp;topics=c&amp;edit=0#Photo-27">
  2836.          <img alt="This should be DxO.jpeg.  Is it missing?" border="0" id="Photo_27"
  2837.               title="Photo DxO.jpeg.  Click to redisplay larger version of image."
  2838.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250611/small/DxO.jpeg"
  2839.               width="371" height="182"
  2840.           /></a>
  2841.  
  2842.      <p>
  2843. Instead of the normal 10 seconds, it took DxO 25 <i>minutes</i> to process the image!  My
  2844. guess is that it was performing lots of little transfers, each of which got held up by the
  2845. disk load of the backup.
  2846.      </p>
  2847.  
  2848.      <p>
  2849. Interestingly, this disk identified itself differently.  <a href="http://www.lemis.com/grog/diary-jun2025.php?subtitle=More%20storage%20issues&amp;article=D-20250607-020524#D-20250607-020524">Last week</a> there was no relationship between the serial number on the package and the
  2850. serial number of the disk.  Today the package stated a serial number <tt>NT17MDRZ</tt>,
  2851. which the device expanded to <tt>00000000NT17MDRZ</tt>, and the name was also different:
  2852.      </p>
  2853.  
  2854.      <blockquote class="fullwidth">
  2855. <div style="text-align:left">
  2856.  <tt>
  2857. Jun 11 11:21:09 eureka kernel: da2 at umass&#45;sim2 bus 2 scbus6 target 0 lun 0
  2858. <br />Jun 11 11:21:09 eureka kernel: da2: &lt;Seagate Expansion HDD 1802&gt; Fixed Direct Access SPC&#45;4 SCSI device
  2859. <br />Jun 11 11:21:09 eureka kernel: da2: Serial Number 00000000NT17MDRZ
  2860. <br />Jun 11 11:21:09 eureka kernel: da2: 400.000MB/s transfers
  2861. <br />Jun 11 11:21:09 eureka kernel: da2: 15259647MB (31251759103 512 byte sectors: 255H 63S/T 1945332C)
  2862. <br />Jun 11 11:21:09 eureka kernel: da2: quirks=0x2&lt;NO_6_BYTE&gt;
  2863. <br />
  2864.  </tt>
  2865. </div>
  2866. </blockquote>
  2867.  
  2868.      <p>
  2869. Is that important?  If so, it's documented here.
  2870.      </p>
  2871.      </div>
  2872.    ]]>
  2873.  </description>
  2874.  <dc:creator>Greg Lehey</dc:creator>
  2875.  <dc:date>2025-06-12T03:15:46+00:00</dc:date>
  2876. </item>
  2877.  
  2878.            
  2879. <!-- topic ko not selected
  2880.      <p>
  2881. Shopping at the <a href="https://www.facebook.com/Fruits.shack.Wendouree/">Fruit Shack</a> is always frustrating.  They have lots of good things, some of the time.  Today I found
  2882. even less of the items on my shopping list than normal.  To make the point, I found more of
  2883. them at the nearby Ballarat Asian Grocery, where I normally don't find much.
  2884.      </p>
  2885.  
  2886.      <p>
  2887. As if that wasn't enough, I had had problems with an item I bought <a href="http://www.lemis.com/grog/diary-may2025.php?subtitle=Fruit%20Shack%20again&amp;article=D-20250516-024832#D-20250516-024832">last time</a>:
  2888.      </p>
  2889.  
  2890.      
  2891.      <p>
  2892. I had noted it at the time because it had no identifying label, though clearly it was dòufu
  2893. puffs.  And when I got round to using them about 10 days ago, they had gone mouldy!  The
  2894. use-by date is clear: 11 September.  So I asked the cashier for a refund.  “But they haven't
  2895. expired yet”.  Tried to make it clear that they were mouldy, but I'm not sure she
  2896. understood.  “Why didn't you bring them earlier?”.  “Look, you can call this number” (on the
  2897. receipt).  Neither would have helped if they hadn't been mouldy at the time.  Call the
  2898. manager, please.  Sorry, no manager here.  Finally, as a gesture of good will, she accepted
  2899. it, not before I got seriously angry.  And the query about the cost of some pork balls went
  2900. nowhere, since they were out of stock and I couldn't show them what I bought.  She just said
  2901. “That was a Chinese cashier”, something obvious here where nearly everybody is Chinese.
  2902. Only she is Indian or similar.  Somehow the cashier name on the receipt seems appropriate:
  2903. “Simple”.
  2904.      </p>
  2905.  
  2906.      <p>
  2907. What do I do?  The Fruit Shack is getting more and more on my nerves, but they're a valuable
  2908. resource, and I don't want them to get into trouble.
  2909.      </p>
  2910.      
  2911. End deselected topic ko (Fruit Shack pain) -->
  2912.  
  2913.                  
  2914. <item>
  2915. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250613-031649</guid>
  2916. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250613-031649</link>
  2917. <category>animals</category>
  2918. <category>technology</category>
  2919. <category>opinion</category>
  2920. <title>Dead bird</title>
  2921.  <description>
  2922.    <![CDATA[
  2923.    <div align="justify">
  2924.      <p>
  2925. Somebody left a present in our driveway:
  2926.      </p>
  2927.  
  2928.      <div align="left">
  2929.  <a id="Photo-28" name="Photo-28"
  2930.          href="diary-jun2025.php?dirdate=20250612&amp;imagesizes=11111111111111111111111111112&amp;topics=c&amp;edit=0#Photo-28">
  2931.          <img alt="This should be Bird-1.jpeg.  Is it missing?" border="0" id="Photo_28"
  2932.               title="Photo Bird-1.jpeg.  Click to redisplay larger version of image."
  2933.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250612/small/Bird-1.jpeg"
  2934.               width="300" height="225"
  2935.           /></a>
  2936.  <a id="Photo-29" name="Photo-29"
  2937.          href="diary-jun2025.php?dirdate=20250612&amp;imagesizes=111111111111111111111111111112&amp;topics=c&amp;edit=0#Photo-29">
  2938.          <img alt="This should be Bird-2.jpeg.  Is it missing?" border="0" id="Photo_29"
  2939.               title="Photo Bird-2.jpeg.  Click to redisplay larger version of image."
  2940.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250612/small/Bird-2.jpeg"
  2941.               width="300" height="225"
  2942.           /></a>
  2943.  <a id="Photo-30" name="Photo-30"
  2944.          href="diary-jun2025.php?dirdate=20250612&amp;imagesizes=1111111111111111111111111111112&amp;topics=c&amp;edit=0#Photo-30">
  2945.          <img alt="This should be Bird-4.jpeg.  Is it missing?" border="0" id="Photo_30"
  2946.               title="Photo Bird-4.jpeg.  Click to redisplay larger version of image."
  2947.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250612/small/Bird-4.jpeg"
  2948.               width="225" height="300"
  2949.           /></a>
  2950.  <a id="Photo-31" name="Photo-31"
  2951.          href="diary-jun2025.php?dirdate=20250612&amp;imagesizes=11111111111111111111111111111112&amp;topics=c&amp;edit=0#Photo-31">
  2952.          <img alt="This should be Bird-6.jpeg.  Is it missing?" border="0" id="Photo_31"
  2953.               title="Photo Bird-6.jpeg.  Click to redisplay larger version of image."
  2954.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250612/small/Bird-6.jpeg"
  2955.               width="225" height="300"
  2956.           /></a>
  2957.      </div>
  2958.  
  2959.      <p>
  2960. What is it?  <a href="http://www.lemis.com/yvonne/">Yvonne</a> thought that it was a <a href="https://de.wikipedia.org/wiki/Star_(Art)">Star</a>, or <a href="https://en.wikipedia.org/wiki/Starling">starling</a>, and that seems likely.  But the
  2961. German name „Star“ is somehow appropriate: it's a homonym of „starr“, meaning stiff, and so
  2962. it was.
  2963.      </p>
  2964.  
  2965.      <p>
  2966. How did it die?  Yvonne thought that it might have flown against a windscreen and broken its
  2967. neck, but the neck seemed unaffected.  About the only thing obvious was that one foot was
  2968. held higher than the other.
  2969.      </p>
  2970.      </div>
  2971.    ]]>
  2972.  </description>
  2973.  <dc:creator>Greg Lehey</dc:creator>
  2974.  <dc:date>2025-06-13T03:16:49+00:00</dc:date>
  2975. </item>
  2976.  
  2977.            
  2978. <item>
  2979. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250613-032140</guid>
  2980. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250613-032140</link>
  2981. <category>technology</category>
  2982. <category>opinion</category>
  2983. <title>named for fra</title>
  2984.  <description>
  2985.    <![CDATA[
  2986.    <div align="justify">
  2987.      <p>
  2988. <i>ffm.lemis.com</i> in its old incarnation is gone.  <i>fra.lemis.com</i> has taken over
  2989. the net proxy, but it only occurred to me today that <i>ffm</i> was also a name server.  OK,
  2990. migrate the name servers, in the process changing IP addresses so that <i>ffm</i> is now a
  2991. name for <i>fra</i>, <tt>192.248.184.42</tt>.  Simple: take the configuration
  2992. from <i>lax.lemis.com</i> (in its incarnation as <i>ns1.lemis.com</i>), frob slightly and
  2993. start on <i>fra</i>:
  2994.      </p>
  2995.  
  2996.      <blockquote class="fullwidth">
  2997. <div style="text-align:left">
  2998.  <tt>
  2999. <code><font color="blue">=== root@fra (/dev/pts/2)</font> <font color="red">/usr/local/etc</font> <font color="blue">17</font> &#45;&gt; <b><tt>service named start</tt></b></code>
  3000. <br />/usr/local/etc/namedb/named.conf:7: unix control '/var/run/ndc': not supported
  3001. <br />/usr/local/etc/rc.d/named: ERROR: named&#45;checkconf for /usr/local/etc/namedb/named.conf failed
  3002. <br />
  3003.  </tt>
  3004. </div>
  3005. </blockquote>
  3006.  
  3007.      <p>
  3008. Huh?  What does “not supported” mean?  But I've always had trouble with <i>rndc</i>, and I
  3009. find it easier to restart <i>named</i> with a <i>kill -1</i>.  OK, comment out the reference
  3010. to <i>/var/run/ndc</i>, which proves to be a <a href="https://en.wikipedia.org/wiki/Network_socket">socket</a>.  Try again.
  3011.      </p>
  3012.  
  3013.      <blockquote class="fullwidth">
  3014. <div style="text-align:left">
  3015.  <tt>
  3016. Jun 12 05:57:25 fra named[10112]: the limit on open files is already at the maximum allowed value: 116964
  3017. <br />Jun 12 05:57:25 fra named[10112]: isc_stdio_open '/var/log/named/named&#45;2.log' failed: file not found
  3018. <br />Jun 12 05:57:25 fra named[10112]: configuring logging: file not found
  3019. <br />Jun 12 05:57:25 fra named[10112]: loading configuration: file not found
  3020. <br />Jun 12 05:57:25 fra named[10112]: exiting (due to fatal error)
  3021. <br />Jun 12 05:57:25 fra grog[10116]: /usr/local/etc/rc.d/named: WARNING: failed to start named
  3022. <br />
  3023.  </tt>
  3024. </div>
  3025. </blockquote>
  3026.  
  3027.      <p>
  3028. What does that mean?  Ah, no <i>/var/log/named/</i>?  Create that and try again:
  3029.      </p>
  3030.  
  3031.      <blockquote class="fullwidth">
  3032. <div style="text-align:left">
  3033.  <tt>
  3034. Jun 12 05:58:41 fra named[10134]: isc_stdio_open '/var/log/named/named&#45;2.log' failed: permission denied
  3035. <br />Jun 12 05:58:41 fra named[10134]: configuring logging: permission denied
  3036. <br />Jun 12 05:58:41 fra named[10134]: loading configuration: permission denied
  3037. <br />Jun 12 05:58:41 fra named[10134]: exiting (due to fatal error)
  3038. <br />Jun 12 05:58:41 fra grog[10138]: /usr/local/etc/rc.d/named: WARNING: failed to start named
  3039. <br />
  3040.  </tt>
  3041. </div>
  3042. </blockquote>
  3043.  
  3044.      <p>
  3045. Oh.  <i>/var/log/named</i> belonged to <tt>root</tt>, but <i>named</i> runs
  3046. as <tt>bind</tt>.  Once again:
  3047.      </p>
  3048.  
  3049.      <blockquote class="fullwidth">
  3050. <div style="text-align:left">
  3051.  <tt>
  3052. <code><font color="blue">=== root@fra (/dev/pts/0)</font> <font color="red">/var/log</font> <font color="blue">69</font> &#45;&gt; <b><tt>l &#45;d named</tt></b></code>
  3053. <br />drwxr&#45;xr&#45;x &nbsp;2 root wheel 512 12 Jun 05:58 named
  3054. <br /><code><font color="blue">=== root@fra (/dev/pts/0)</font> <font color="red">/var/log</font> <font color="blue">70</font> &#45;&gt; <b><tt>chown bind:bind named</tt></b></code>
  3055. <br />
  3056.  </tt>
  3057. </div>
  3058. </blockquote>
  3059.  
  3060.      <p>
  3061. And then it ran.  Only one message puzzled me:
  3062.      </p>
  3063.  
  3064.      <blockquote class="fullwidth">
  3065. <div style="text-align:left">
  3066.  <tt>
  3067. Jun 12 06:00:53 fra named[10174]: the limit on open files is already at the maximum allowed value: 116964
  3068.  </tt>
  3069. </div>
  3070. </blockquote>
  3071.  
  3072.      <p>
  3073. What does that mean?
  3074.      </p>
  3075.      </div>
  3076.    ]]>
  3077.  </description>
  3078.  <dc:creator>Greg Lehey</dc:creator>
  3079.  <dc:date>2025-06-13T03:21:40+00:00</dc:date>
  3080. </item>
  3081.  
  3082.            
  3083. <!-- topic po not selected
  3084.      <p>
  3085. Sample photo from <a href="http://www.lemis.com/yana/">Yana</a> taken with her new <a href="https://www.panasonic.com/au/support/product-archives/lumix-cameras-video-cameras/lumix-g-lenses/h-x025e.html">Leica Summilux 25 mm f/1.4</a> lens.  Not good.  I have exactly the same model, so it was
  3086. relatively easy to compare (and confirm that photos of text are a good way to test lenses).
  3087. Here her photo and mine, both taken at f/1.4:
  3088.      </p>
  3089.  
  3090.            
  3091.      <p>
  3092. The brightness isn't important.  It's difficult to get good exposure of a display screen,
  3093. and normally I would correct it.  But the image quality seems much worse than mine.  Here
  3094. top left, centre and bottom right, first Yana's lens, then mine:
  3095.      </p>
  3096.  
  3097.            
  3098.      <p>
  3099. Centre:
  3100.      </p>
  3101.  
  3102.            
  3103.      <p>
  3104. Bottom right:
  3105.      </p>
  3106.  
  3107.            
  3108.      <p>
  3109. On the one hand, both lenses are acceptable.  In the Good Old Days you wouldn't expect
  3110. anything like that good a result.  But clearly the new lens isn't nearly as good as the old
  3111. one?  Should I return it?  That would be a pity.
  3112.      </p>
  3113.      
  3114. End deselected topic po (Is that lens good enough?) -->
  3115.  
  3116.            
  3117. <!-- topic a not selected
  3118.      <p>
  3119. This evening <a href="http://www.lemis.com/grog/Albums/Animals/Bruno.php">Bruno</a> came in via the lounge
  3120. room window, as is his wont recently.  He had something small in his mouth—a moth, I
  3121. thought.  But it proved to be a mouse.  That's certainly a great improvement over <a href="https://en.wikipedia.org/wiki/Fairy_wren">fairy wrens</a>.   I put them in the laundry for Bruno to complete
  3122. his action.  And of course he lost it, far too quickly for him to have eaten it.
  3123.      </p>
  3124.  
  3125.      <p>
  3126. Before going to bed, <a href="http://www.lemis.com/grog/Albums/Animals/Mona.php">Mona</a> showed great
  3127. interest in the sideboard in the dining room.  Left the light on overnight to make it for
  3128. her to catch it.
  3129.      </p>
  3130.      
  3131. End deselected topic a (A mouse!) -->
  3132.  
  3133.                  
  3134. <!-- topic a not selected
  3135.      <p>
  3136. First thing this morning found a dead mouse in the hallway:
  3137.      </p>
  3138.  
  3139.      
  3140.      <p>
  3141. Was that yesterday evening's mouse?  I thought it was much smaller.  And how did it die?  It
  3142. seems that it was a single bite to the throat:
  3143.      </p>
  3144.  
  3145.      
  3146.      <p>
  3147. In the evening, to make his point, Bruno came back with another mouse.  This time I didn't
  3148. let him in; instead Mona went out with him.  When they came back, there was no mouse.
  3149.      </p>
  3150.  
  3151.      <a name="Invisible-Mona" id="Invisible-Mona"></a>
  3152.      <p>
  3153. In passing, it's interesting to note a big difference between Bruno and Mona.  Bruno is
  3154. immediately apparent when he sits on the windowsill in the dark.  Mona is almost invisible.
  3155. This evening I saw Bruno and a disembodied eye, something like a <a href="https://en.wikipedia.org/wiki/Cheshire_cat">Cheshire cat</a>.
  3156.      </p>
  3157.      
  3158. End deselected topic a (Another death) -->
  3159.  
  3160.            
  3161. <!-- topic po not selected
  3162.      <p>
  3163. So how good or bad is <a href="http://www.lemis.com/yana/">Yana's</a> new <a href="https://www.panasonic.com/au/support/product-archives/lumix-cameras-video-cameras/lumix-g-lenses/h-x025e.html">Leica Summilux 25 mm f/1.4</a>?  Time for some comparisons.
  3164.      </p>
  3165.  
  3166.      <p>
  3167. First, fill the screen with numbers.  Start an <i>xterm</i>, make it full screen, and enter:
  3168.      </p>
  3169.  
  3170.      <blockquote class="fullwidth">
  3171. <div style="text-align:left">
  3172.  <tt>
  3173. <code><font color="blue">=== grog@hydra (/dev/pts/35)</font> <font color="red">~</font> <font color="blue">2</font> &#45;&gt; <b><tt>echo `jot 10000 10000`</tt></b></code>
  3174.  </tt>
  3175. </div>
  3176. </blockquote>
  3177.  
  3178.      
  3179.      <p>
  3180. Then the photos.  No fewer than 12 lenses:
  3181.      </p>
  3182.  
  3183.      <ul>
  3184.        <li class="fullwidth">
  3185.          <div class="listitemwidth">
  3186.            <a href="https://www.panasonic.com/au/consumer/lumix-cameras-video-cameras/lumix-camera-lenses/lumix-g-lenses/h-x015gc9-k.html">Leica DG Summilux 15 mm f/1.7 <b>ASPH.</b></a>          </div>
  3187.        </li>
  3188.  
  3189.        <li class="fullwidth">
  3190.          <div class="listitemwidth">
  3191.            <a href="http://www.panasonic.com/au/consumer/lumix-cameras-video-cameras/lumix-g-lenses/h-h020ae.html">Panasonic Lumix G 20 mm f/1.7</a>          </div>
  3192.        </li>
  3193.  
  3194.        <li class="fullwidth">
  3195.          <div class="listitemwidth">
  3196.            <a href="https://www.voigtlaender.de/lenses/mft/25-mm-10-95-nokton-ii/">Voigtländer Nokton 25 mm f/0.95</a>          </div>
  3197.        </li>
  3198.  
  3199.        <li class="fullwidth">
  3200.          <div class="listitemwidth">
  3201.            <a href="https://www.panasonic.com/au/support/product-archives/lumix-cameras-video-cameras/lumix-g-lenses/h-x025e.html">Leica Summilux 25 mm f/1.4</a>          </div>
  3202.        </li>
  3203.  
  3204.        <li class="fullwidth">
  3205.          <div class="listitemwidth">
  3206.            <a href="https://www.dpreview.com/products/olympus/lenses/olympus_m_45_1p8">M.Zuiko Digital 45 mm f/1.8</a>          </div>
  3207.        </li>
  3208.  
  3209.        <li class="fullwidth">
  3210.          <div class="listitemwidth">
  3211.            <a href="http://www.pentaxforums.com/lensreviews/SMC-S-M-C-Super-Takumar-50mm-F1.4.html">Super-Takumar 50 mm f/1.4</a>          </div>
  3212.        </li>
  3213.  
  3214.        <li class="fullwidth">
  3215.          <div class="listitemwidth">
  3216.            <a href="http://camera-wiki.org/wiki/Steinheil">Steinheil</a> Cassar 50 mm f/2.8
  3217.          </div>
  3218.        </li>
  3219.  
  3220.        <li class="fullwidth">
  3221.          <div class="listitemwidth">
  3222.            50 mm f/2.8 <a href="https://en.wikipedia.org/wiki/Tessar">Tessar</a>          </div>
  3223.        </li>
  3224.  
  3225.        <li class="fullwidth">
  3226.          <div class="listitemwidth">
  3227.            50 mm f/3.5 FED lens (<a href="https://en.wikipedia.org/wiki/Elmar_(lens)">Elmar</a> copy)
  3228.          </div>
  3229.        </li>
  3230.  
  3231.        <li class="fullwidth">
  3232.          <div class="listitemwidth">
  3233.            <a href="http://www.photosynthesis.co.nz/nikon/ai5014e.jpg">Nikkor 50 mm f/1.4</a>          </div>
  3234.        </li>
  3235.  
  3236.        <li class="fullwidth">
  3237.          <div class="listitemwidth">
  3238.            <a href="https://www.dpreview.com/products/olympus/lenses/olympus_m_75_1p8">M.Zuiko Digital ED 75 mm f/1.8</a>          </div>
  3239.        </li>
  3240.  
  3241.        <li class="fullwidth">
  3242.          <div class="listitemwidth">
  3243.            <a href="http://www.photosynthesis.co.nz/nikon/ais8514.html">Nikkor 85 mm f/1.4</a>          </div>
  3244.        </li>
  3245.      </ul>
  3246.  
  3247.      <p>
  3248. And with the exception of the Nokton (f/0.95, f/1.4, f/2.8 and f/4), up to three apertures:
  3249. f/1.4 or f/1.7 for the lenses that can do it, f/2.8 and f/4.
  3250.      </p>
  3251.  
  3252.      <p>
  3253. The results: almost useless.  I did them hand-held in the assumption that it would make no
  3254. difference, but it did, very much so.  Firstly, the monitor I chose (a 1920x1080 Acer) is
  3255. sensitive to viewing angle, and though it wasn't obvious to the naked eye, it made a real
  3256. mess of the images:
  3257.      </p>
  3258.  
  3259.      
  3260.      <p>
  3261. Then the fact that the images didn't line up, even for a single lens, meant that I couldn't
  3262. really compare the results at different apertures.  And finally, they all seemed to perform
  3263. better than I had expected.  Here the Super-Takumar at f/1.4, top left and bottom right (on
  3264. the left, with the 25 mm Summicron on the right):
  3265.      </p>
  3266.  
  3267.            
  3268.      <p>
  3269.      </p>
  3270.  
  3271.            
  3272.      <p>
  3273.      </p>
  3274.  
  3275.            
  3276.      <p>
  3277. The difference in image size is due to the difference in focal length.  But that's a far cry
  3278. from what I experienced <a href="http://www.lemis.com/grog/diary-oct2016.php?subtitle=Old%20lenses:%20oldies%20but%20goodies?&amp;article=D-20161027-221903#D-20161027-221903">eight years ago</a>, where the same lens comparison gave me (top left, here at f/1.4 and
  3279. f/8):
  3280.      </p>
  3281.  
  3282.            
  3283.      <p>
  3284.      </p>
  3285.  
  3286.            
  3287.      <p>
  3288. In particular, the Super-Takumar actually appears better than the Summilux at bottom right,
  3289. something that I didn't try on the previous occasion.  Even the lenses that I expected to be
  3290. bottom of the list didn't compare that badly.  Here the Cassar (<a href="https://en.wikipedia.org/wiki/Cooke_triplet">Cooke triplet</a>) at f/2.8, FED
  3291. at f/4, the Summilux at f/1.4 and the Summilux at f/2.8:
  3292.      </p>
  3293.  
  3294.      <div align="left">
  3295.      </div>
  3296.  
  3297.      <p>
  3298.      </p>
  3299.  
  3300.      <div align="left">
  3301.      </div>
  3302.  
  3303.      <p>
  3304.      </p>
  3305.  
  3306.      <div align="left">
  3307.      </div>
  3308.  
  3309.      <p>
  3310. Yes, the Summilux is better at f/2.8, but I was expecting more of a difference.  And of
  3311. course the Super-Takumar, the Cassar and the FED are all “full frame” lenses, so I'm just
  3312. sampling the inner, better part of their field of view.
  3313.      </p>
  3314.  
  3315.      <p>
  3316. So what do I do?  Clearly I need better continuity, but maybe my idea of using text as a
  3317. comparison wasn't so good after all.
  3318.      </p>
  3319.      
  3320. End deselected topic po (More lens comparisons) -->
  3321.  
  3322.            
  3323. <item>
  3324. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250614-020348</guid>
  3325. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250614-020348</link>
  3326. <category>photography</category>
  3327. <category>technology</category>
  3328. <category>opinion</category>
  3329. <title>Cropping with ImageMagick</title>
  3330.  <description>
  3331.    <![CDATA[
  3332.    <div align="justify">
  3333.      <p>
  3334. Part of today's investigations was to generate cropped images, as above.  Not an issue:
  3335. <a href="https://en.wikipedia.org/wiki/ImageMagick">ImageMagick</a> does that.  But
  3336. somehow I keep forgetting how, and the man pages don't help (I can't find a description of
  3337. “geometry” anywhere).  OK, dig in my scripts:
  3338.      </p>
  3339.  
  3340.      <blockquote class="fullwidth">
  3341. <div style="text-align:left">
  3342.  <tt>
  3343. /Photos/Tools/jpegcompare&#45;detail: ensureconvert $COMPPHOTO $TMPDIR/after&#45;$i&#45;bottom&#45;right.jpeg &#45;crop 300x225+0+0 &#45;gravity south&#45;east
  3344.  </tt>
  3345. </div>
  3346. </blockquote>
  3347.  
  3348.      <p>
  3349. OK, I can do that.  But it doesn't work!  After some searching I discovered
  3350. that <i>convert</i> is (now) sensitive to the order of arguments, and it seems that an
  3351. obvious geometry like <tt>300x225-0-0</tt> doesn't work.  In the end I ended up writing a
  3352. new script with the payload
  3353.      </p>
  3354.  
  3355.      <blockquote class="fullwidth">
  3356. <div style="text-align:left">
  3357.  <tt>
  3358. for i in $*; do
  3359. <br />&nbsp;&nbsp;IMAGE=`basename $i .jpeg`
  3360. <br />&nbsp;&nbsp;convert $i &#45;gravity north&#45;west &#45;crop 600x450+0+0 $IMAGE&#45;topleft.jpeg
  3361. <br />&nbsp;&nbsp;convert $i &#45;gravity center &#45;crop 600x450&#45;0&#45;0 $IMAGE&#45;centre.jpeg
  3362. <br />&nbsp;&nbsp;convert $i &#45;gravity south&#45;east &#45;crop 600x450&#45;0&#45;0 $IMAGE&#45;bottomright.jpeg
  3363. <br />&nbsp;&nbsp;touch &#45;r $i $IMAGE&#45;topleft.jpeg $IMAGE&#45;centre.jpeg $IMAGE&#45;bottomright.jpeg
  3364. <br />done
  3365. <br />
  3366.  </tt>
  3367. </div>
  3368. </blockquote>
  3369.  
  3370.      <p>
  3371. But I should check <i>jpegcompare-detail</i>.  It seems to be intended to do the same thing.
  3372.      </p>
  3373.      </div>
  3374.    ]]>
  3375.  </description>
  3376.  <dc:creator>Greg Lehey</dc:creator>
  3377.  <dc:date>2025-06-14T02:03:48+00:00</dc:date>
  3378. </item>
  3379.  
  3380.            
  3381. <item>
  3382. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250614-021733</guid>
  3383. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250614-021733</link>
  3384. <category>technology</category>
  3385. <category>opinion</category>
  3386. <title>Another bind</title>
  3387.  <description>
  3388.    <![CDATA[
  3389.    <div align="justify">
  3390.      <p>
  3391. Mail from Stephen Rothwell today.  Error messages from his name server
  3392. (<i>ns1.ozlabs.org</i>, one of my name servers):
  3393.      </p>
  3394.  
  3395.      <blockquote class="fullwidth">
  3396. <div style="text-align:left">
  3397.  <tt>
  3398. 2025&#45;06&#45;13T10:54:04.461783+10:00 gandalf named[32356]: zone lemis.com/IN: refresh: retry limit for primary 45.63.116.55#53 exceeded (source 150.107.74.76#0)
  3399. <br />2025&#45;06&#45;13T10:54:34.471975+10:00 gandalf named[32356]: transfer of 'lemis.com/IN' from 45.63.116.55#53: failed to connect: timed out
  3400. <br />2025&#45;06&#45;13T10:54:34.472173+10:00 gandalf named[32356]: transfer of 'lemis.com/IN' from 45.63.116.55#53: Transfer status: timed out
  3401.  </tt>
  3402. </div>
  3403. </blockquote>
  3404.  
  3405.      <p>
  3406. Oh.  Yes, of course, it's not enough to update the zone.  I also have to update
  3407. my <i>named.conf</i>, which was still pointing to the old address for <i>ffm.lemis.com</i>.
  3408. Now I have:
  3409.      </p>
  3410.  
  3411.      <blockquote class="fullwidth">
  3412. <div style="text-align:left">
  3413.  <tt>
  3414. // &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ns1 &nbsp; &nbsp; &nbsp; &nbsp; ns3 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ns6.gandi.net &nbsp;ns0.krpservers.com &nbsp;ns.ozlabs.org
  3415. <br /> allow&#45;transfer {45.32.70.18; 192.248.184.42; 217.70.177.42; 62.13.128.200; 150.107.74.76; };
  3416. <br />
  3417.  </tt>
  3418. </div>
  3419. </blockquote>
  3420.  
  3421.      <p>
  3422. While I was at it, also added <i>ns3.lemis.com</i> (<i>fra</i>/<i>ffm</i>) to the list at
  3423. <a href="https://en.wikipedia.org/wiki/Gandi">Gandi</a>, not without pain.  I must
  3424. remember that name servers in the same zone require <a href="https://en.wikipedia.org/wiki/Glue_record">glue records</a>.  The error message I got
  3425. doesn't really help:
  3426.      </p>
  3427.  
  3428.      <blockquote class="fullwidth">
  3429. <div style="text-align:left">
  3430.  <tt>
  3431. ns3.lemis.com has no IP address but is a glue record
  3432.  </tt>
  3433. </div>
  3434. </blockquote>
  3435.  
  3436.      <p>
  3437. Of course <i>ns3.lemis.com</i> has an IP address:
  3438.      </p>
  3439.  
  3440.      <blockquote class="fullwidth">
  3441. <div style="text-align:left">
  3442.  <tt>
  3443. <code><font color="blue">=== grog@freefall (/dev/pts/24)</font> <font color="red">~</font> <font color="blue">3</font> &#45;&gt; <b><tt>host ns3.lemis.com</tt></b></code>
  3444. <br />ns3.lemis.com has address 192.248.184.42
  3445. <br />
  3446.  </tt>
  3447. </div>
  3448. </blockquote>
  3449.  
  3450.      <p>
  3451. What it wanted was for me to create a glue record elsewhere in the menu tree.  It could have
  3452. done so too and asked for confirmation, but why make things easy?
  3453.      </p>
  3454.      </div>
  3455.    ]]>
  3456.  </description>
  3457.  <dc:creator>Greg Lehey</dc:creator>
  3458.  <dc:date>2025-06-14T02:17:33+00:00</dc:date>
  3459. </item>
  3460.  
  3461.                  
  3462. <item>
  3463. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250615-014509</guid>
  3464. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250615-014509</link>
  3465. <category>photography</category>
  3466. <category>technology</category>
  3467. <category>opinion</category>
  3468. <title>Optimize your mobile phone camera</title>
  3469.  <description>
  3470.    <![CDATA[
  3471.    <div align="justify">
  3472.      <p>
  3473. Saw an article today on <a href="https://en.wikipedia.org/wiki/Digital_Photography_Review">DPreview</a>: <a href="https://www.dpreview.com/learn/2896139411/six-essential-camera-settings-to-improve-your-phone-photos">Six essential camera settings to improve your phone photos</a>.  Never mind that
  3474. “improve” and “essential” are not compatible, nor that I don't really use my phone for
  3475. photos if I can possibly avoid it: it might be interesting reading.
  3476.      </p>
  3477.  
  3478.      <p>
  3479. And of course <a href="https://en.wikipedia.org/wiki/Android_(operating_system)">Android</a> made it impossible.  There was almost nothing on <i>albo</i>, my <a href="https://m.gsmarena.com/xiaomi_redmi_note_13-12776.php">Xiaomi Redmi Note 13</a>, that
  3480. matched anything in the article.  About the only thing that I found was the suggestion to
  3481. set the image format to the match the sensor format.  But while searching through the maze
  3482. of twisty little menus, found this:
  3483.      </p>
  3484.  
  3485.        <a id="Photo-32" name="Photo-32"
  3486.          href="diary-jun2025.php?dirdate=20250614&amp;imagesizes=111111111111111111111111111111112&amp;topics=c&amp;edit=0#Photo-32">
  3487.          <img alt="This should be Xiaomi-camera-settings.jpeg.  Is it missing?" border="0" id="Photo_32"
  3488.               title="Photo Xiaomi-camera-settings.jpeg.  Click to redisplay larger version of image."
  3489.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250614/small/Xiaomi-camera-settings.jpeg"
  3490.               width="174" height="387"
  3491.           /></a>
  3492.  
  3493.      <p>
  3494. What is it?  A series of icons.  And a typical mobile phone explanation:
  3495.      </p>
  3496.  
  3497.        <a id="Photo-33" name="Photo-33"
  3498.          href="diary-jun2025.php?dirdate=20250614&amp;imagesizes=1111111111111111111111111111111112&amp;topics=c&amp;edit=0#Photo-33">
  3499.          <img alt="This should be Xiaomi-camera-settings-detail.jpeg.  Is it missing?" border="0" id="Photo_33"
  3500.               title="Photo Xiaomi-camera-settings-detail.jpeg.  Click to redisplay larger version of image."
  3501.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250614/small/Xiaomi-camera-settings-detail.jpeg"
  3502.               width="373" height="181"
  3503.           /></a>
  3504.  
  3505.      <p>
  3506. I couldn't get it to expand the text, though there's plenty of space.  It should never have
  3507. been truncated in the first place, but I suppose that's <i>modern</i>.  Pressing on the
  3508. icons does nothing.  As far as I can tell, the whole purpose of the page is to change the
  3509. order in which these icons are displayed <i>somewhere</i>.
  3510.      </p>
  3511.      </div>
  3512.    ]]>
  3513.  </description>
  3514.  <dc:creator>Greg Lehey</dc:creator>
  3515.  <dc:date>2025-06-15T01:45:09+00:00</dc:date>
  3516. </item>
  3517.  
  3518.            
  3519. <!-- topic go not selected
  3520.      <p>
  3521. Jesse Walsh along today.  I had wanted him to look at some stuff in the garden, but first
  3522. <a href="http://www.lemis.com/yvonne/">Yvonne</a> wanted him to plant some self-seeding trees in the
  3523. paddock to the north-west of the house.  After 3 hours we had:
  3524.      </p>
  3525.  
  3526.      <div align="left">
  3527.      </div>
  3528.  
  3529.      <p>
  3530. Two <a href="https://en.wikipedia.org/wiki/Acacia_melanoxylon">Acacia melanoxylon</a> planted in the same hole.  Two <a href="https://en.wikipedia.org/wiki/Eucalypt">eucalypts</a> also planted together about 2 m away.  Each of these trees can grow to
  3531. 20&nbsp;m, like the ones in the paddock to the west:
  3532.      </p>
  3533.  
  3534.      
  3535.      <p>
  3536. We don't need to worry about the <a href="https://en.wikipedia.org/wiki/Casuarina">casuarina</a> to the right: it prefers shade, and will probably die.
  3537.      </p>
  3538.  
  3539.      <p>
  3540. After some discussion, we agreed to plant the eucalypts in the south-west corner of the
  3541. paddock and the second blackwood in the hole left behind:
  3542.      </p>
  3543.  
  3544.            
  3545.      <p>
  3546. I'll keep an eye on that.
  3547.      </p>
  3548.      
  3549. End deselected topic go (Planting trees) -->
  3550.  
  3551.      
  3552.      
  3553. <!-- topic g not selected
  3554.      <p>
  3555. While taking the photos in the paddock, noted a number of other things.  We're in the second
  3556. week of winter, but the <a href="https://en.wikipedia.org/wiki/Hibiscus_rosa-sinensis">Hibiscus rosa-sinensis</a> “Uncle Max” still has buds and a flower that hasn't completely
  3557. dried up:
  3558.      </p>
  3559.  
  3560.            
  3561.      <p>
  3562. I wonder if any of the buds will make it.
  3563.      </p>
  3564.  
  3565.      <p>
  3566. There are a number of mushrooms in the north-west paddock:
  3567.      </p>
  3568.  
  3569.            
  3570.      <p>
  3571. The first spring flowers are showing:
  3572.      </p>
  3573.  
  3574.            
  3575.      <p>
  3576. And Jesse managed to put a bigger fence around the <a href="https://en.wikipedia.org/wiki/Grevillea_robusta">Grevillea robusta</a>, which, after
  3577. <a href="http://www.lemis.com/grog/diary-jun2019.php#robusta">6 years</a> finally looks like it is
  3578. growing:
  3579.      </p>
  3580.  
  3581.      
  3582.      <p>
  3583.      </p>
  3584.      
  3585. End deselected topic g (Random garden views) -->
  3586.  
  3587.      
  3588.      
  3589. <!-- topic po not selected
  3590.      <p>
  3591. <a href="http://www.lemis.com/grog/diary-jun2025.php?subtitle=More%20lens%20comparisons&amp;article=D-20250614-020248#D-20250614-020248">Yesterday's efforts</a> made it clear that my idea of testing lenses with photos of text
  3592. on screen are probably not as good as I had hoped.  But I've been there (many times) before.
  3593. <a href="http://www.lemis.com/grog/diary-may2014.php?subtitle=More%20lens%20quality%20investigation&amp;article=D-20140512-020804#D-20140512-020804">Eleven years ago</a> I used a <a href="https://www.graphics.cornell.edu/~westin/misc/res-chart.html">ISO 12233 lens test
  3594. chart</a> to establish that a lens I had bought was defective.  How about doing that
  3595. again?  The <a href="https://www.graphics.cornell.edu/~westin/misc/ISO_12233-reschart.pdf">chart</a> is
  3596. still available.  Display on the TV (to avoid focus issues with being too close to the
  3597. screen).
  3598.      </p>
  3599.  
  3600.      <p>
  3601. And that will be a whole lot more work, to be done in the evening when there are fewer
  3602. reflections.  Went to test.  And <i>once again</i> I have issues with colour banding:
  3603.      </p>
  3604.  
  3605.      <div align="left">
  3606.      </div>
  3607.  
  3608.      <p>
  3609. What causes that?  It's clearly related to the TV, but it's not repeatable.  In some cases
  3610. it shows up in the viewfinder but not in the final image.  Maybe I should give up on the TV.
  3611. Much of this would be easier, except that I want to give <a href="http://www.lemis.com/yana/">Yana</a> an easy and reliable way of measuring her lenses.
  3612.      </p>
  3613.      
  3614. End deselected topic po (More lens test thoughts) -->
  3615.  
  3616.      
  3617.            
  3618. <item>
  3619. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250615-030511</guid>
  3620. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250615-030511</link>
  3621. <category>technology</category>
  3622. <title>Ports Collection overreach</title>
  3623.  <description>
  3624.    <![CDATA[
  3625.    <div align="justify">
  3626.      <p>
  3627. Time to roll over the log files on <i>fra.lemis.com</i>, which involves restarting the web
  3628. server.  <a href="https://www.freebsd.org/">FreeBSD</a> offers this functionality—I
  3629. think—with the <i>service</i> program, but it's straightforward enough with
  3630. the <i>apachectl</i> program:
  3631.      </p>
  3632.  
  3633.      <blockquote class="fullwidth">
  3634. <div style="text-align:left">
  3635.  <tt>
  3636. <code><font color="blue">=== root@fra (/dev/pts/0)</font> <font color="red">/var/log/www</font> <font color="blue">86</font> &#45;&gt; <b><tt>apachectl graceful</tt></b></code>
  3637. <br />Cannot 'graceful' apache24. Set apache24_enable to YES in /etc/rc.conf or use 'onegraceful' instead of 'graceful'.
  3638. <br /><code><font color="blue">=== root@fra (/dev/pts/0)</font> <font color="red">/var/log/www</font> <font color="blue">87</font> &#45;&gt; <b><tt>apachectl onegraceful</tt></b></code>
  3639. <br />Usage: /usr/local/sbin/httpd [&#45;D name] [&#45;d directory] [&#45;f file]
  3640. <br />...
  3641.  </tt>
  3642. </div>
  3643. </blockquote>
  3644.  
  3645.      <p>
  3646. Oh.  Something has half changed <i>apachectl</i> to require intervention in the FreeBSD
  3647. configuration system.  But <tt>onerestart</tt> (a command that doesn't exist
  3648. in <i>apachectl</i>) hasn't been catered for.  Nothing for it: I <i>must</i> put this
  3649. in <i>/etc/rc.conf</i>:
  3650.      </p>
  3651.  
  3652.      <blockquote class="fullwidth">
  3653. <div style="text-align:left">
  3654.  <tt>
  3655. apache24_enable=YES
  3656.  </tt>
  3657. </div>
  3658. </blockquote>
  3659.  
  3660.      <p>
  3661. The instructions say that I should write <tt>apache24_enable="YES"</tt>, but that's
  3662. silly.  <i>rc.conf</i> is (part of) a shell script, so the quotes are not necessary.
  3663.      </p>
  3664.      </div>
  3665.    ]]>
  3666.  </description>
  3667.  <dc:creator>Greg Lehey</dc:creator>
  3668.  <dc:date>2025-06-15T03:05:11+00:00</dc:date>
  3669. </item>
  3670.  
  3671.            
  3672. <!-- topic G not selected
  3673.      <p>
  3674. Mail from <a href="https://en.wikipedia.org/wiki/BUPA">BUPA</a>, my health insurer,
  3675. today: <a href="https://www.blua.bupa.com.au/">book an online appointment with a
  3676. doctor</a> at any time.  We needed that a few months back, but they were only available
  3677. some of the time.
  3678.      </p>
  3679.  
  3680.      <p>
  3681. But on searching I discover that we had already tried them, but <a href="https://url7072.marketingmsg.bupa.com.au/">couldn't get through</a>.  That was clearly
  3682. an incorrect URL.  The one I have now leads to a registration form which presumably works.
  3683.      </p>
  3684.      
  3685. End deselected topic G (Online doctor) -->
  3686.  
  3687.      
  3688.      
  3689. <!-- topic ap not selected
  3690.      <p>
  3691. At some point I want to get <a href="http://www.lemis.com/grog/Albums/Animals/Mona.php">Mona</a> sitting
  3692. on the window ledge in her <a href="https://en.wikipedia.org/wiki/Cheshire_cat">Cheshire cat</a> persona.  It wasn't tonight—Mona didn't go outside—but I did get
  3693. <a href="http://www.lemis.com/grog/Albums/Animals/Bruno.php">Bruno</a>:
  3694.      </p>
  3695.  
  3696.      
  3697.      <p>
  3698. I'm surprised how strong the reflections are.
  3699.      </p>
  3700.      
  3701. End deselected topic ap (Bruno) -->
  3702.  
  3703.                  
  3704. <item>
  3705. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250616-013256</guid>
  3706. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250616-013256</link>
  3707. <category>history</category>
  3708. <category>technology</category>
  3709. <category>opinion</category>
  3710. <title>25 years SMPng</title>
  3711.  <description>
  3712.    <![CDATA[
  3713.    <div align="justify">
  3714.      <p>
  3715. <a href="http://www.lemis.com/grog/diary-jun2000.php?topics=c#15">Twenty-five years ago today</a> a number of us gathered at
  3716. <a href="https://en.wikipedia.org/wiki/Yahoo!">Yahoo!'s</a> main facility in
  3717. <a href="https://en.wikipedia.org/wiki/Sunnyvale">Sunnyvale</a> to discuss the
  3718. future of the <a href="https://www.freebsd.org/">FreeBSD</a> kernel.  The background
  3719. was a <a href="http://www.mindcraft.com/whitepapers/first-nts4rhlinux.html">benchmark</a> from <a href="https://en.wikipedia.org/wiki/Mindcraft">Mindcraft</a> that showed that Microsoft <a href="http://www.lemis.com/grog/Rant/windows.php">“Windows”</a> NT
  3720. greatly outperformed <a href="https://en.wikipedia.org/wiki/Linux">Linux</a>.
  3721.      </p>
  3722.  
  3723.      <p>
  3724. The reason was the multiprocessor support in each system.  And far from getting up on our
  3725. hind legs and saying “couldn't happen to FreeBSD”, we acknowledged that it could, in fact,
  3726. happen.  In fact, <a href="http://www.lemis.com/grog/diary-jan2004.php#SMPng">over 3 years later</a>, on the only occasion when <a href="https://en.wikipedia.org/wiki/Linus_Torvalds">Linus Torvalds</a> visited us, I demonstrated a FreeBSD system which had such problems
  3727. where Linux didn't.
  3728.      </p>
  3729.  
  3730.      <p>
  3731. So on today's anniversary we came together to discuss how to improve the situation.  I went
  3732. into <a href="http://www.lemis.com/grog/Daemons-advocate/Year-of-BSD.php#SMPng">more detail</a> at the
  3733. time in a <a href="https://www.daemonnews.org/dadvocate.php">Daemon News</a> article.
  3734.      </p>
  3735.  
  3736.      <p>
  3737. How time flies!  I wonder how we compare now.  I have the feeling that if it doesn't worry
  3738. <a href="https://en.wikipedia.org/wiki/Netflix">Netflix</a>, it's not a problem.
  3739.      </p>
  3740.      </div>
  3741.    ]]>
  3742.  </description>
  3743.  <dc:creator>Greg Lehey</dc:creator>
  3744.  <dc:date>2025-06-16T01:32:56+00:00</dc:date>
  3745. </item>
  3746.  
  3747.            
  3748. <!-- topic pHo not selected
  3749.      <p>
  3750. By coincidence, discovered that I had spent considerable time <a href="http://www.lemis.com/grog/diary-jun2024.php?subtitle=Comparing%20lenses&amp;article=D-20240616-003545#D-20240616-003545">a year ago today</a>.  There I was more interested in my “<a href="https://en.wikipedia.org/wiki/Leica_camera">Leica</a>” lenses, the <a href="https://wiki.l-camera-forum.com/leica-wiki.en/index.php/Hektor_f%3D_13.5_cm_1:4.5">Hektor 13.5 cm f/4.5</a> and the <a href="https://camerapedia.fandom.com/wiki/FED_(Original)_(_FED_NKVD,_FED-S,_FED-1)">50 mm
  3751.        f/3.5 FED 1</a>.  There, too, I came to the conclusion that the Hektor was not as bad as I
  3752.        feared, though the FED seems to have performed worse than <a href="http://www.lemis.com/grog/diary-jun2025.php?subtitle=More%20lens%20comparisons&amp;article=D-20250614-020248#D-20250614-020248">on Friday</a>.
  3753.      </p>
  3754.  
  3755.      <p>
  3756. I really must find a better way to compare them.
  3757.      </p>
  3758.      
  3759. End deselected topic pHo (Lens comparisons: a year after) -->
  3760.  
  3761.            
  3762. <!-- topic ko not selected
  3763.      <p>
  3764. <a href="https://en.wikipedia.org/wiki/Spaghetti_alla_puttanesca">Spaghetti alla
  3765. puttanesca</a> is a well-known Neapolitan dish, and I have probably made it before.  But
  3766. it's a lot of work for a pasta course.  Recently I saw <a href="https://cooking.nytimes.com/recipes/1026743-spicy-shrimp-puttanesca">this recipe</a> in the <a href="https://en.wikipedia.org/wiki/New_York_Times">New York Times</a>.
  3767. It turns it into a main course by adding “<a href="https://en.wikipedia.org/wiki/Shrimp">shrimp</a>” (<a href="https://en.wikipedia.org/wiki/Prawns">prawns</a>).
  3768.      </p>
  3769.  
  3770.      <p>
  3771. OK, how hard can it be?  Horrible!  These bizarre old units completely confuse me, and I had
  3772. already put it off once, and I spent some time today to come up with these quantities, which
  3773. still aren't good enough:
  3774.      </p>
  3775.  
  3776.      <h2>Ingredients</h2>
  3777.  
  3778.      <p>
  3779. For 1.5 servings.
  3780.      </p>
  3781.  
  3782.          <table summary="Ingredients">
  3783.        <tr>
  3784.          <td align="right"><b>quantity</b></td>
  3785.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3786.          <td><b>ingredient</b> </td>
  3787.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3788.          <td><b>step</b> </td>
  3789.        </tr>
  3790.  
  3791.       <tr>
  3792.          <td valign="top" align="right">215 g</td>
  3793.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3794.          <td valign="top" align="left">(cooked) spaghetti</td>
  3795.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3796.          <td valign="top" align="right">1</td>
  3797.       </tr>
  3798.       <tr>
  3799.         <td>
  3800.         </td>
  3801.       </tr>
  3802.  
  3803.       <tr>
  3804.          <td valign="top" align="right">12 g</td>
  3805.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3806.          <td valign="top" align="left">olive oil</td>
  3807.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3808.          <td valign="top" align="right">2</td>
  3809.       </tr>
  3810.  
  3811.       <tr>
  3812.          <td valign="top" align="right">15 g</td>
  3813.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3814.          <td valign="top" align="left">garlic</td>
  3815.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3816.          <td valign="top" align="right">2</td>
  3817.       </tr>
  3818.  
  3819.       <tr>
  3820.          <td valign="top" align="right"><del>12 g</del></td>
  3821.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3822.          <td valign="top" align="left">anchovy fillets</td>
  3823.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3824.          <td valign="top" align="right">2</td>
  3825.       </tr>
  3826.       <tr>
  3827.         <td>
  3828.         </td>
  3829.       </tr>
  3830.  
  3831.       <tr>
  3832.          <td valign="top" align="right"><del>30 g</del></td>
  3833.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3834.          <td valign="top" align="left">black olives</td>
  3835.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3836.          <td valign="top" align="right">3</td>
  3837.       </tr>
  3838.  
  3839.       <tr>
  3840.          <td valign="top" align="right"><del>20 g</del></td>
  3841.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3842.          <td valign="top" align="left">capers</td>
  3843.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3844.          <td valign="top" align="right">3</td>
  3845.       </tr>
  3846.  
  3847.       <tr>
  3848.          <td valign="top" align="right">3 g</td>
  3849.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3850.          <td valign="top" align="left">paprika, „edelsüß“</td>
  3851.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3852.          <td valign="top" align="right">3</td>
  3853.       </tr>
  3854.       <tr>
  3855.         <td>
  3856.         </td>
  3857.       </tr>
  3858.  
  3859.       <tr>
  3860.          <td valign="top" align="right">55 g</td>
  3861.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3862.          <td valign="top" align="left">tomatoes</td>
  3863.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3864.          <td valign="top" align="right">4</td>
  3865.       </tr>
  3866.  
  3867.       <tr>
  3868.          <td valign="top" align="right">20 g</td>
  3869.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3870.          <td valign="top" align="left">tomato paste</td>
  3871.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3872.          <td valign="top" align="right">4</td>
  3873.       </tr>
  3874.       <tr>
  3875.         <td>
  3876.         </td>
  3877.       </tr>
  3878.  
  3879.       <tr>
  3880.          <td valign="top" align="right">82 g</td>
  3881.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3882.          <td valign="top" align="left">water</td>
  3883.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3884.          <td valign="top" align="right">5</td>
  3885.       </tr>
  3886.  
  3887.       <tr>
  3888.          <td valign="top" align="right">120 g</td>
  3889.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3890.          <td valign="top" align="left">prawns, 10 g</td>
  3891.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3892.          <td valign="top" align="right">5</td>
  3893.       </tr>
  3894.       <tr>
  3895.         <td>
  3896.         </td>
  3897.       </tr>
  3898.  
  3899.       <tr>
  3900.          <td valign="top" align="right"></td>
  3901.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3902.          <td valign="top" align="left">parsley</td>
  3903.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3904.          <td valign="top" align="right">7</td>
  3905.       </tr>
  3906.       <tr>
  3907.         <td>
  3908.         </td>
  3909.       </tr>
  3910.  
  3911.       <tr>
  3912.          <td valign="top" align="right">0 g</td>
  3913.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3914.          <td valign="top" align="left">oregano</td>
  3915.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3916.          <td valign="top" align="right">8</td>
  3917.       </tr>
  3918.      </table>
  3919.  
  3920.      <h2>
  3921. Preparation
  3922.      </h2>
  3923.  
  3924.      <ol>
  3925.        <li class="fullwidth">
  3926.          <p class="listitemwidth">
  3927.    Cook the spaghetti.
  3928.          </p>
  3929.        </li>
  3930.  
  3931.        <li class="fullwidth">
  3932.          <p class="listitemwidth">
  3933.    Cut the anchovies into small pieces and fry in the oil with the garlic.  The base
  3934.    recipes claim that the anchovies will “dissolve”, but mine are made of sterner stuff.
  3935.          </p>
  3936.        </li>
  3937.  
  3938.        <li class="fullwidth">
  3939.          <p class="listitemwidth">
  3940.            Cut the olives into 3 or 4 pieces.  Add olives, capers and paprika and mix well.
  3941.          </p>
  3942.        </li>
  3943.  
  3944.        <li class="fullwidth">
  3945.          <p class="listitemwidth">
  3946.            Add tomato and tomato paste and heat until about to dry out.
  3947.          </p>
  3948.        </li>
  3949.  
  3950.        <li class="fullwidth">
  3951.          <p class="listitemwidth">
  3952.            Add prawns and water.  Heat until prawns are barely cooked.
  3953.          </p>
  3954.  
  3955.          </li>
  3956.  
  3957.        <li class="fullwidth">
  3958.          <p class="listitemwidth">
  3959.            Add the spaghetti and transfer to a serving dish.
  3960.          </p>
  3961.  
  3962.          </li>
  3963.  
  3964.        <li class="fullwidth">
  3965.          <p class="listitemwidth">
  3966.            Garnish with much parsley.
  3967.          </p>
  3968.  
  3969.          </li>
  3970.  
  3971.        <li class="fullwidth">
  3972.          <p class="listitemwidth">
  3973.            Add oregano.  Oops, forgot the oregano.
  3974.          </p>
  3975.        </li>
  3976.      </ol>
  3977.  
  3978.      <p>
  3979. And the result?  Not bad, but not well balanced.
  3980.      </p>
  3981.  
  3982.      
  3983.      <p>
  3984. There were enough noodles and prawn, but the flavour ingredients were a little
  3985. underrepresented.  <a href="http://www.lemis.com/grog/recipes/Puttanesca.php">Next time</a> I'll use more.
  3986.      </p>
  3987.  
  3988.      <p>
  3989. And it wasn't until I wrote this up that I discovered that I already had a recipe for
  3990. <a href="http://www.lemis.com/grog/recipes/puttanesca.php">puttanesca</a>.  It confirms my quantities.  Why
  3991. didn't I check first?
  3992.      </p>
  3993.      
  3994. End deselected topic ko (Spaghetti alla puttanesca) -->
  3995.  
  3996.                  
  3997. <!-- topic a not selected
  3998.      <p>
  3999. This morning before dawn a transporter came and picked up Carlotta and Dana.  Carlotta is
  4000. going back to Jane Ashhurst again, and Dana is going to Shelly Cooper.  To make up for that,
  4001. Chris Bahlo picked up her mare Pinta, leaving only <a href="http://www.lemis.com/grog/Albums/Animals/Samba.php">Samba</a> and <a href="http://www.lemis.com/grog/Albums/Animals/Morena.php">Morena</a> here.  Samba was not amused: Pinta had
  4002. become her friend, and Morena was the intruder.  She spent all day complaining and avoiding
  4003. Morena.
  4004.      </p>
  4005.      
  4006. End deselected topic a (Changing horses again) -->
  4007.  
  4008.            
  4009. <item>
  4010. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250617-004955</guid>
  4011. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250617-004955</link>
  4012. <category>technology</category>
  4013. <category>opinion</category>
  4014. <title>disdain again</title>
  4015.  <description>
  4016.    <![CDATA[
  4017.    <div align="justify">
  4018.      <p>
  4019. It has been <a href="http://www.lemis.com/grog/diary-feb2025.php?subtitle=disdain%20for%20Microsoft&amp;article=D-20250220-015919#D-20250220-015919">several months</a> since I bought <i>disdain.lemis.com</i>, my first Microsoft <a href="http://www.lemis.com/grog/Rant/windows.php">“Windows”</a> machine.  I did some basic configuration, and then
  4020. left it.
  4021.      </p>
  4022.  
  4023.      <p>
  4024. Why?  I hate Microsoft at the best of times, and they have gone and changed the appearance
  4025. Yet Again.  And I was terrified of the pain I would have to go through to set up “<a href="https://en.wikipedia.org/wiki/File_sharing">file sharing</a>”.  But it has to happen,
  4026. and today I finally got round to it, in the process updating my <a href="http://www.lemis.com/grog/HOWTO/microsoft-setup.php">living with Microsoft</a> page.
  4027.      </p>
  4028.  
  4029.      <p>
  4030. On the whole things weren't that bad.  I've found that it's easier to search for specific
  4031. terms than try to guess where in the menu tree Microsoft might have hidden specific
  4032. configuration functions.  But they don't want to know about “map network drive”:
  4033.      </p>
  4034.  
  4035.        <a id="Photo-34" name="Photo-34"
  4036.          href="diary-jun2025.php?dirdate=20250616&amp;imagesizes=11111111111111111111111111111111112&amp;topics=c&amp;edit=0#Photo-34">
  4037.          <img alt="This should be Microsoft-4.jpeg.  Is it missing?" border="0" id="Photo_34"
  4038.               title="Photo Microsoft-4.jpeg.  Click to redisplay larger version of image."
  4039.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250616/small/Microsoft-4.jpeg"
  4040.               width="463" height="146"
  4041.           /></a>
  4042.  
  4043.      <p>
  4044. Never mind, there's a second search.  But that took me to an <a href="https://www.solveyourtech.com/windows-11-how-to-map-a-network-drive-a-step-by-step-guide/">external web page</a> that starts by telling me
  4045.      </p>
  4046.  
  4047.      <blockquote class="fullwidth">
  4048. <div style="text-align:left">
  4049.  <tt>
  4050. First, open File Explorer from your taskbar.
  4051. <br />
  4052. <br />This is the same tool you use to browse your files and folders. Look for the folder icon, usually pinned to your taskbar. If it’s not there, you can find it by searching “File Explorer” in the Start menu.
  4053. <br />
  4054.  </tt>
  4055. </div>
  4056. </blockquote>
  4057.  
  4058.      <p>
  4059. On <i>disdain</i> the two paragraphs are separated by a whole screen's worth of
  4060. advertisements.  I don't “browse” my files and <a href="http://www.lemis.com/grog/Rant/bad-language.php#folder">folders</a>.  But yes, it's the tab symbol that I know from other versions of Microsoft.
  4061. For some reason they haven't changed it (yet).  That takes me to something that I recall:
  4062.      </p>
  4063.  
  4064.        <a id="Photo-35" name="Photo-35"
  4065.          href="diary-jun2025.php?dirdate=20250616&amp;imagesizes=111111111111111111111111111111111112&amp;topics=c&amp;edit=0#Photo-35">
  4066.          <img alt="This should be Microsoft-6.jpeg.  Is it missing?" border="0" id="Photo_35"
  4067.               title="Photo Microsoft-6.jpeg.  Click to redisplay larger version of image."
  4068.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250616/small/Microsoft-6.jpeg"
  4069.               width="346" height="195"
  4070.           /></a>
  4071.  
  4072.      <p>
  4073. And then it goes on:
  4074.      </p>
  4075.  
  4076.      <blockquote class="fullwidth">
  4077. <div style="text-align:left">
  4078.  <tt>
  4079. In the top toolbar, click on the ‘Map network drive’ option.
  4080.  </tt>
  4081. </div>
  4082. </blockquote>
  4083.  
  4084.      <p>
  4085. But there's no ‘Map network drive’ option in that half-full “top toolbar”.
  4086.      </p>
  4087.  
  4088.        <a id="Photo-36" name="Photo-36"
  4089.          href="diary-jun2025.php?dirdate=20250616&amp;imagesizes=1111111111111111111111111111111111112&amp;topics=c&amp;edit=0#Photo-36">
  4090.          <img alt="This should be Microsoft-6-detail.jpeg.  Is it missing?" border="0" id="Photo_36"
  4091.               title="Photo Microsoft-6-detail.jpeg.  Click to redisplay larger version of image."
  4092.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250616/small/Microsoft-6-detail.jpeg"
  4093.               width="534" height="127"
  4094.           /></a>
  4095.  
  4096.      <p>
  4097. <b>Fool!</b>  You need to click on the <b>...</b> in the middle of the toolbar (the last
  4098. item) and select:
  4099.      </p>
  4100.  
  4101.        <a id="Photo-37" name="Photo-37"
  4102.          href="diary-jun2025.php?dirdate=20250616&amp;imagesizes=11111111111111111111111111111111111112&amp;topics=c&amp;edit=0#Photo-37">
  4103.          <img alt="This should be Microsoft-7.jpeg.  Is it missing?" border="0" id="Photo_37"
  4104.               title="Photo Microsoft-7.jpeg.  Click to redisplay larger version of image."
  4105.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250616/small/Microsoft-7.jpeg"
  4106.               width="339" height="199"
  4107.           /></a>
  4108.  
  4109.      <p>
  4110. Still, modulo obfuscatory menus, it just worked.  I was quite surprised.  Next step is to
  4111. install <a href="https://www.dxo.com/dxo-photolab/">DxO PhotoLab</a> on it,
  4112. complicated by the fact that DxO never forgets a computer and claimed that I was now trying
  4113. to breach the license.  Mail to DxO support, no response today.
  4114.      </p>
  4115.      </div>
  4116.    ]]>
  4117.  </description>
  4118.  <dc:creator>Greg Lehey</dc:creator>
  4119.  <dc:date>2025-06-17T00:49:55+00:00</dc:date>
  4120. </item>
  4121.  
  4122.                  
  4123. <!-- topic a not selected
  4124.      <p>
  4125. <a href="http://www.lemis.com/grog/diary-jun2025.php?subtitle=Changing%20horses%20again&amp;article=D-20250617-004636#D-20250617-004636">Yesterday</a> <a href="http://www.lemis.com/grog/Albums/Animals/Samba.php">Samba</a> was <i>really</i> unhappy being left alone with <a href="http://www.lemis.com/grog/Albums/Animals/Morena.php">Morena</a>, and she spent all day complaining about
  4126. it.  That's over, fortunately:
  4127.      </p>
  4128.  
  4129.      
  4130.      <p>
  4131. That's Samba on the left and Morena on the right.
  4132.      </p>
  4133.      
  4134. End deselected topic a (Samba cools down) -->
  4135.  
  4136.            
  4137. <item>
  4138. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250618-015049</guid>
  4139. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250618-015049</link>
  4140. <category>technology</category>
  4141. <category>photography</category>
  4142. <category>opinion</category>
  4143. <title>DxO for disdain</title>
  4144.  <description>
  4145.    <![CDATA[
  4146.    <div align="justify">
  4147.      <p>
  4148. Mail from <a href="https://www.dxo.com/">DxO</a> support today: I'm already running
  4149. DxO on three machines.  Please tell us which they are <i>and what operating systems they are
  4150. running</i>.
  4151.      </p>
  4152.  
  4153.      <p>
  4154. Well, sorry, can't do that.  I'm running on <i>distress</i> and I had been running it
  4155. on <i>despise</i>, but currently it's not functional.  Both running Microsoft.
  4156.      </p>
  4157.  
  4158.      <p>
  4159. More responses, showing that their license database goes by system name and exact operating
  4160. system: "<a href="http://www.lemis.com/grog/Rant/windows.php">Windows</a>” isn't enough.  10?  11?  “Home”?
  4161. “<b>Pro</b>”?  Gave them that information (“Windows” 10 <b>Pro</b> in each case) and they
  4162. were happy, allowing me to activate on <i>disdain</i>.
  4163.      </p>
  4164.  
  4165.      <p>
  4166. Next, copy my configuration.  DxO offer no help whatsoever here, and though I have written
  4167. down how to do it in various places, there was no document to help.  Started a <a href="http://www.lemis.com/grog/HOWTO/DxO-config.php">HOWTO</a> page today.  That, including the configuration,
  4168. took all afternoon.
  4169.      </p>
  4170.  
  4171.      <p>
  4172. Following up later, it's possible that the files in the <i>Workspaces</i> subdirectory
  4173. contain the missing information.  I'll try that next time.
  4174.      </p>
  4175.  
  4176.      <p>
  4177. Finally I was able to run it.  Things were still not right, and I don't know what I have
  4178. missed.  In particular, the “palettes” were not set the same way as on <i>distress</i>.  The
  4179. Preset Editor was enabled, and a whole lot were not: metadata, light, color, detail,
  4180. Geometry, Viewpoint, Local adjustments.  <a href="https://www.dxo.com/dxo-viewpoint/">Viewpoint</a> is understandable: it wasn't installed.  But even after I enabled them, the
  4181. view on the side panels was different.
  4182.      </p>
  4183.  
  4184.      <p>
  4185. Gave that up for the time being and did some performance testing.  <i>disdain</i> processed
  4186. 13 images in an average of 100 seconds (101, 99, 100).  As expected, <i>distress</i> took
  4187. longer, but not nearly as much longer as I had expected: an average of 110 seconds (111,
  4188. 109, 110).  For that it's not worth it.  I should use the new machine for something else.
  4189. OK, remove the <a href="https://en.wikipedia.org/wiki/SSD">SSD</a>, buy a new one
  4190. and make it the new <i>lagoon</i>.
  4191.      </p>
  4192.  
  4193.      <p>
  4194. Somehow this is too much stress.  I had stomach ache all afternoon.
  4195.      </p>
  4196.      </div>
  4197.    ]]>
  4198.  </description>
  4199.  <dc:creator>Greg Lehey</dc:creator>
  4200.  <dc:date>2025-06-18T01:50:49+00:00</dc:date>
  4201. </item>
  4202.  
  4203.                  
  4204. <item>
  4205. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250619-030538</guid>
  4206. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250619-030538</link>
  4207. <category>photography</category>
  4208. <category>technology</category>
  4209. <title>Checking photo integrity</title>
  4210.  <description>
  4211.    <![CDATA[
  4212.    <div align="justify">
  4213.      <p>
  4214. How do I check whether the photos I have on my backup disks are not corrupted?  There are
  4215. <a href="http://www.lemis.com/grog/diary-jun2025.php?subtitle=Testing%20JPEG%20integrity&amp;article=D-20250609-232007#D-20250609-232007">various check programs</a> for <a href="https://en.wikipedia.org/wiki/JPEG">JPEG</a> images, but do they check for everything?  I'm sure they recognize structural problems,
  4216. but would they recognize a zeroed-out data block in the middle of the image?  And of course
  4217. they only check JPEG, arguably the least interesting of my photo files.
  4218.      </p>
  4219.  
  4220.      <p>
  4221. Take a step back.  If I have corruption somewhere, there are two possibilities: either all
  4222. copies are corrupt, or there's a version that isn't corrupt.  So before I potentially delete
  4223. the last correct version of a file from my myriad backup disks, I should compare them.  How?
  4224. <a href="https://man.freebsd.org/cgi/man.cgi?query=sha1"><i>sha1</i></a> seems the
  4225. obvious choice.  Yes, it's not as secure as more modern versions like <a href="https://man.freebsd.org/cgi/man.cgi?query=sha512"><i>sha512</i></a>, but it's faster,
  4226. and the chances that the corrupt version will have the same fingerprint as the good version
  4227. are vanishingly small.
  4228.      </p>
  4229.  
  4230.      <p>
  4231. So:
  4232.      </p>
  4233.  
  4234.      <blockquote class="fullwidth">
  4235. <div style="text-align:left">
  4236.  <tt>
  4237. <code><font color="blue">=== root@eureka (/dev/pts/0)</font> <font color="red">/photobackup/Photos/grog</font> <font color="blue">152</font> &#45;&gt; <b><tt>find [12]* &#45;print0|xargs &#45;0 sha1 > /Photos/grog/sha1&#45;12 2>/Photos/grog/sha1&#45;12&#45;err</tt></b></code>
  4238.  </tt>
  4239. </div>
  4240. </blockquote>
  4241.  
  4242.      <p>
  4243. We'll see what that looks like tomorrow, or maybe the day after.
  4244.      </p>
  4245.      </div>
  4246.    ]]>
  4247.  </description>
  4248.  <dc:creator>Greg Lehey</dc:creator>
  4249.  <dc:date>2025-06-19T03:05:38+00:00</dc:date>
  4250. </item>
  4251.  
  4252.            
  4253. <item>
  4254. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250619-030931</guid>
  4255. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250619-030931</link>
  4256. <category>technology</category>
  4257. <category>photography</category>
  4258. <title>DxO: the last configuration option</title>
  4259.  <description>
  4260.    <![CDATA[
  4261.    <div align="justify">
  4262.      <p>
  4263. What was missing from <a href="http://www.lemis.com/grog/diary-jun2025.php?subtitle=DxO%20for%20disdain&amp;article=D-20250618-015049#D-20250618-015049">yesterday's</a> copying of <a href="https://www.dxo.com/dxo-photolab/">DxO
  4264. PhotoLab</a> configuration information?  Was it really the subdirectory <i>Workspaces</i>?
  4265. Braved stomachache and tried copying the files in that directory: <i>Myspace.xml</i>,
  4266.        <i>__$$Customize.xml</i> and <i>__$$PhotoLibrary.xml</i>.  Restart DxO.  Yes!  My guess is
  4267. that it's <i>Myspace.xml</i>.  The other two were there on installation, though their
  4268. content differed.  So I have the (hopefully) final piece in my <a href="http://www.lemis.com/grog/HOWTO/DxO-config.php">HOWTO</a>, at least until I install a new version.
  4269.      </p>
  4270.      </div>
  4271.    ]]>
  4272.  </description>
  4273.  <dc:creator>Greg Lehey</dc:creator>
  4274.  <dc:date>2025-06-19T03:09:31+00:00</dc:date>
  4275. </item>
  4276.  
  4277.            
  4278. <item>
  4279. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250619-030933</guid>
  4280. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250619-030933</link>
  4281. <category>technology</category>
  4282. <category>general</category>
  4283. <category>opinion</category>
  4284. <title>Bloody Android!</title>
  4285.  <description>
  4286.    <![CDATA[
  4287.    <div align="justify">
  4288.      <p>
  4289. Looked at <i>albo</i>, my <a href="https://en.wikipedia.org/wiki/Android_(operating_system)">Android</a> phone for some
  4290. reason today.  Two missed calls from <a href="http://www.lemis.com/yvonne/">Yvonne</a>.  Dammit, it has
  4291. been in my pocket all day.  And calls aren't muted.  And when I tried to call her, I got no
  4292. response from the phone, not even a ring tone.
  4293.      </p>
  4294.  
  4295.      <p>
  4296. What's wrong with this bloody thing?  Rebooted it, after which it worked normally.  But why
  4297. are these things so <i>horribly</i> unreliable?
  4298.      </p>
  4299.      </div>
  4300.    ]]>
  4301.  </description>
  4302.  <dc:creator>Greg Lehey</dc:creator>
  4303.  <dc:date>2025-06-19T03:09:33+00:00</dc:date>
  4304. </item>
  4305.  
  4306.            
  4307. <!-- topic kh not selected
  4308.      <p>
  4309. Ran the dishwasher this morning, as always.  But the dishes didn't get clean, and the
  4310. detergent was still in the now-open dispenser.  Dispenser obstructed?  Filter blocked?
  4311. Spray arms obstructed?  That's easy with things like spatulas that can hang through the
  4312. basket.  Checked carefully and ran it again.  No problem.
  4313.      </p>
  4314.  
  4315.      <p>
  4316. Then a second load.  Problem.  The cycle ran normally, but once again the detergent remained
  4317. in the dispenser.  On further investigation discovered that the water in the sump was
  4318. completely clear.  Pump blockage?  Pump failure?  Did some basic checks, including checking
  4319. the filter, and removing the upper basket and checking the waterways, but came up with
  4320. nothing.  So until proof of the contrary it's the recirculating pump.  A good thing that we
  4321. decided to keep the old dishwasher <a href="http://www.lemis.com/grog/diary-may2018.php?subtitle=How%20to%20waste%20a%20day&amp;article=D-20180508-065717#Failsafe-dishwasher">when we installed this one</a>.  But it's Yet Another repair to schedule.
  4322.      </p>
  4323.      
  4324. End deselected topic kh (Dishwasher fail) -->
  4325.  
  4326.      
  4327.      
  4328. <!-- topic a not selected
  4329.      <p>
  4330. <a href="http://www.lemis.com/grog/diary-jun2025.php?subtitle=Another%20death&amp;article=D-20250614-013936#Invisible-Mona">Last week</a> I noted that <a href="http://www.lemis.com/grog/Albums/Animals/Mona.php">Mona</a> is
  4331. almost invisible when she sits on the outside windoill at night.  Here's the proof:
  4332.      </p>
  4333.  
  4334.      
  4335.      <p>
  4336. Bruno is on the right, but where is Mona?  Towards the right side of the left window:
  4337.      </p>
  4338.  
  4339.      
  4340.      <p>
  4341. You really need to look.  But then, Bruno's face is not much more visible.
  4342.      </p>
  4343.      
  4344. End deselected topic a (Hiding Mona) -->
  4345.  
  4346.            
  4347. <!-- topic a not selected
  4348.      <p>
  4349. <a href="http://www.lemis.com/yvonne/">Yvonne</a> had a shopping spree today, and one of the things she
  4350. bought was two new beds for the dogs:
  4351.      </p>
  4352.  
  4353.                  
  4354.      <p>
  4355.      </p>
  4356.      
  4357. End deselected topic a (New beds for the dogs) -->
  4358.  
  4359.                  
  4360. <!-- topic ko not selected
  4361.      <p>
  4362. <a href="http://www.lemis.com/grog/recipes/pad-see-ew.php">Pad see ew</a> for breakfast again today.  It's a
  4363. dark dish, but unlike <a href="http://www.lemis.com/grog/recipes/KL-Hokkien-Mee.php">KL Hokkien mee</a> it
  4364. doesn't look attractive.  Here pad see ew on the left, KL Hokkien mee on the right:
  4365.      </p>
  4366.  
  4367.            
  4368.      <p>
  4369. Part of that comes from frying the meat over high heat right at the start.  So: do the
  4370. <a href="https://en.wikipedia.org/wiki/Gai_lan">Gai lan</a> first.  The result
  4371. didn't look different enough to take a photo, but it did seem better.
  4372.      </p>
  4373.  
  4374.      <p>
  4375. And the wok hei?  I'm still not there.  Put some more oil into the wok to prevent the
  4376. noodles sticking to it, with only limited success.
  4377.      </p>
  4378.  
  4379.      <p>
  4380. About the only real insight was the composition of the sauce.  More fish sauce, more
  4381. vinegar, less soya sauce.
  4382.      </p>
  4383.      
  4384. End deselected topic ko (Refining pad see ew) -->
  4385.  
  4386.                  
  4387. <item>
  4388. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250621-020457</guid>
  4389. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250621-020457</link>
  4390. <category>technology</category>
  4391. <category>photography</category>
  4392. <category>opinion</category>
  4393. <title>Checking photo integrity: first results</title>
  4394.  <description>
  4395.    <![CDATA[
  4396.    <div align="justify">
  4397.      <p>
  4398. Mail from Michael Hughes this morning.  He does something similar to check the integrity of
  4399. his photos, but he stores the results in a database.  Is that worth it?
  4400.      </p>
  4401.  
  4402.      <p>
  4403. Shortly after my <a href="https://man.freebsd.org/cgi/man.cgi?query=sha1"><i>sha1</i></a> run completed.  Compare the results:
  4404.      </p>
  4405.  
  4406.      <blockquote class="fullwidth">
  4407. <div style="text-align:left">
  4408.  <tt>
  4409. <code><font color="blue">=== root@eureka (/dev/pts/0)</font> <font color="red">/Photos/grog</font> <font color="blue">199</font> &#45;&gt; <b><tt>diff &#45;wu sha1 sha1&#45;9|less</tt></b></code>
  4410. <br />&#45;&#45;&#45; sha1 &nbsp; &nbsp; &nbsp; &nbsp;2025&#45;06&#45;20 01:59:10.503960000 +1000
  4411. <br />+++ sha1&#45;9 &nbsp; &nbsp; &nbsp;2025&#45;06&#45;20 09:50:41.603228000 +1000
  4412. <br />@@ &#45;1,22 +1,22 @@
  4413. <br />&#45;SHA1 (19100101) = 4fe15d494fda7d9d31ada156b9dc7c9fd9a9fb45
  4414. <br />&#45;SHA1 (19100101/orig) = 0144154c165dc86f5c13fe432672afee680e9eb3
  4415. <br />+SHA1 (19100101) = 842f2fac8d4907930e8ee206929c367cce6469d2
  4416. <br />+SHA1 (19100101/orig) = 7bd17748fe639f257dad3a26aac111faa8211040
  4417. <br />&#45;SHA1 (19100101/_Ashampoo_Photo_Optimizer_Backup) = 68b6ef4090869108ebecda125669a4a4f6681022
  4418. <br />+SHA1 (19100101/_Ashampoo_Photo_Optimizer_Backup) = 384eec54619f4115ba1d29ced9ce6b6953aca985
  4419. <br />
  4420.  </tt>
  4421. </div>
  4422. </blockquote>
  4423.  
  4424.      <p>
  4425. Oh.  Those are directories.  Yes, of course they can be different.  Repeat the runs looking
  4426. at only files?  First, let's see what the rest looks like, removing some directories:
  4427.      </p>
  4428.  
  4429.      <blockquote class="fullwidth">
  4430. <div style="text-align:left">
  4431.  <tt>
  4432. &#45;SHA1 (19550801/Besut.jpeg) = 8ce614340bc6efa4fdb3a4fa72057696ca9a23d0
  4433. <br />&nbsp;SHA1 (19550801/Pulau&#45;Perhentian&#45;1.jpeg) = e20bd23ecb64b110a17032181aca2b35e3eada0d
  4434. <br />&#45;SHA1 (19550801/Pulau&#45;Perhentian&#45;2.jpeg) = 2a292d311c54587f7236fbfe33fe1868583f7234
  4435. <br />&#45;SHA1 (19550801/Pulau&#45;Perhentian&#45;3.jpeg) = 5ae1cb214b8be9155a4a265baeb419117b173c1b
  4436. <br />&nbsp;SHA1 (19550801/Pulau&#45;Perhentian&#45;4.jpeg) = c198dd795691599aeda639bf5d16ffba268d0748
  4437. <br />+SHA1 (19550801/Pulau&#45;Perhentian&#45;3.jpeg) = 5ae1cb214b8be9155a4a265baeb419117b173c1b
  4438. <br />+SHA1 (19550801/Besut.jpeg) = 8ce614340bc6efa4fdb3a4fa72057696ca9a23d0
  4439. <br />+SHA1 (19550801/Pulau&#45;Perhentian&#45;2.jpeg) = 2a292d311c54587f7236fbfe33fe1868583f7234
  4440. <br />
  4441.  </tt>
  4442. </div>
  4443. </blockquote>
  4444.  
  4445.      <p>
  4446. Despite appearances, there's nothing wrong there.  Only the entries aren't in the same
  4447. sequence.
  4448.      </p>
  4449.  
  4450.      <p>
  4451. Would a database help?  I have a large number of entries:
  4452.      </p>
  4453.  
  4454.      <blockquote class="fullwidth">
  4455. <div style="text-align:left">
  4456.  <tt>
  4457. <code><font color="blue">=== root@eureka (/dev/pts/0)</font> <font color="red">/Photos/grog</font> <font color="blue">202</font> &#45;&gt; <b><tt>l sha1 sha1&#45;9</tt></b></code>
  4458. <br />&#45;rw&#45;r&#45;&#45;r&#45;&#45; &nbsp;1 root &nbsp;lemis &nbsp;83,838,489 20 Jun 01:59 sha1
  4459. <br />&#45;rw&#45;r&#45;&#45;r&#45;&#45; &nbsp;1 root &nbsp;lemis &nbsp;83,670,593 20 Jun 09:50 sha1&#45;9
  4460. <br /><code><font color="blue">=== root@eureka (/dev/pts/0)</font> <font color="red">/Photos/grog</font> <font color="blue">203</font> &#45;&gt; <b><tt>wc &#45;l sha1 sha1&#45;9</tt></b></code>
  4461. <br />&nbsp;1019151 sha1
  4462. <br />&nbsp;1017046 sha1&#45;9
  4463. <br />&nbsp;2036197 total
  4464. <br /><code><font color="blue">=== root@eureka (/dev/pts/0)</font> <font color="red">/Photos/grog</font> <font color="blue">204</font> &#45;&gt; <b><tt>diff &#45;wu sha1 sha1&#45;9 | wc &#45;l</tt></b></code>
  4465. <br />&nbsp;&nbsp;408294
  4466. <br />
  4467.  </tt>
  4468. </div>
  4469. </blockquote>
  4470.  
  4471.      <p>
  4472. More stuff to think about.  About the only thing that I won't need is on of Michael's
  4473. suggestions: write it a in <a href="https://en.wikipedia.org/wiki/C_(programming_language)">C</a>.  The search is I/O
  4474. bound, so I wouldn't gain anything there.
  4475.      </p>
  4476.      </div>
  4477.    ]]>
  4478.  </description>
  4479.  <dc:creator>Greg Lehey</dc:creator>
  4480.  <dc:date>2025-06-21T02:04:57+00:00</dc:date>
  4481. </item>
  4482.  
  4483.            
  4484. <!-- topic k not selected
  4485.      <p>
  4486. I had some cabbage leaves left over.  What do I do with them?  Fry them and eat them with
  4487. noodles.  How about a <a href="http://www.lemis.com/grog/recipes/mee-goreng-mamak.php">mee goreng mamak</a>?
  4488. It doesn't have cabbage, but why not?
  4489.      </p>
  4490.  
  4491.      <p>
  4492. Oh.  An issue that I continually have is that it wants 60 g of cooked potato.  I don't very
  4493. often have cooked potato on hand, and it seems silly to cook 60 g of it.  OK, that's what
  4494. the cabbage replaces.
  4495.      </p>
  4496.  
  4497.      <p>
  4498. And since it's such a mix of cultures, why use Hokkien mee?  For the fun of it, used
  4499. <a href="https://en.wikipedia.org/wiki/Spirali">spirali</a>:
  4500.      </p>
  4501.  
  4502.      
  4503.      <p>
  4504. And how about that, it wasn't bad.
  4505.      </p>
  4506.      
  4507. End deselected topic k (Spirali mamak) -->
  4508.  
  4509.            
  4510. <!-- topic g not selected
  4511.      <p>
  4512. Jesse Walsh along today to tidy up the garden.  I thought we might keep him busy for 2
  4513. hours, but in fact he did a good 5 hours and didn't quite get finished.
  4514.      </p>
  4515.  
  4516.      <p>
  4517. One thing of interest was the incredible dying <a href="https://en.wikipedia.org/wiki/Abutilon">Abutilon</a> by the laundry door: Here photos
  4518. from last month:
  4519.      </p>
  4520.  
  4521.            
  4522.      <p>
  4523. There were multiple branches spread around the bush, but to my surprise they all came from
  4524. one place:
  4525.      </p>
  4526.  
  4527.      
  4528.      <p>
  4529. And there he found some mould, and the wood was rotting away.  There's nothing obvious about
  4530. the mould:
  4531.      </p>
  4532.  
  4533.      <div align="left">
  4534.      </div>
  4535.  
  4536.      <p>
  4537. Did the mould cause the rot, or did the rot attract the mould?  Hopefully it's done now.
  4538.      </p>
  4539.      
  4540. End deselected topic g (Tidying up the garden) -->
  4541.  
  4542.            
  4543. <item>
  4544. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250621-021053</guid>
  4545. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250621-021053</link>
  4546. <category>general</category>
  4547. <category>technology</category>
  4548. <category>opinion</category>
  4549. <title>Anatomy of a parcel delivery</title>
  4550.  <description>
  4551.    <![CDATA[
  4552.    <div align="justify">
  4553.      <p>
  4554. I was expecting a parcel delivery today, so round 11:50 checked <a href="https://auspost.com.au/mypost/track/search">Australia Post tracking</a>.  It told me
  4555. that it spent the night in <a href="https://en.wikipedia.org/wiki/Delacombe">Delacombe</a>, a new location for their tracking reports.  And at 8:32 it was “Unable to
  4556. deliver - Item carded and transferred to post office for collection”.
  4557.      </p>
  4558.  
  4559.      <p>
  4560. I know that.  Though it told me that “It's on its way”, it's really ready for collection.
  4561.      </p>
  4562.  
  4563.      <p>
  4564. OK, what does <a href="https://www.ebay.com.au/">eBay</a> say?
  4565.      </p>
  4566.  
  4567.        <a id="Photo-38" name="Photo-38"
  4568.          href="diary-jun2025.php?dirdate=20250620&amp;imagesizes=111111111111111111111111111111111111112&amp;topics=c&amp;edit=0#Photo-38">
  4569.          <img alt="This should be eBay-tracking.jpeg.  Is it missing?" border="0" id="Photo_38"
  4570.               title="Photo eBay-tracking.jpeg.  Click to redisplay larger version of image."
  4571.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250620/small/eBay-tracking.jpeg"
  4572.               width="200" height="339"
  4573.           /></a>
  4574.        <a id="Photo-39" name="Photo-39"
  4575.          href="diary-jun2025.php?dirdate=20250620&amp;imagesizes=1111111111111111111111111111111111111112&amp;topics=c&amp;edit=0#Photo-39">
  4576.          <img alt="This should be eBay-tracking-detail.jpeg.  Is it missing?" border="0" id="Photo_39"
  4577.               title="Photo eBay-tracking-detail.jpeg.  Click to redisplay larger version of image."
  4578.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250620/small/eBay-tracking-detail.jpeg"
  4579.               width="357" height="189"
  4580.           /></a>
  4581.  
  4582.      <p>
  4583. So it might arrive yesterday?  And now they say that it's at <a href="https://en.wikipedia.org/wiki/Lucas,_Victoria">Lucas</a>.  Why?
  4584.      </p>
  4585.  
  4586.      <p>
  4587. Round 14:00 off to pick up the item without any problems.  Back home and checked the
  4588. tracking information.  Ah, it had been transferred to Lucas at 9:26 and had been waiting for
  4589. me in “NAPOLEON CPA”, Australia Post's inimitable way of spelling “<a href="https://en.wikipedia.org/wiki/Napoleons,_Victoria">Napoleons</a>” since 11:08, nearly
  4590. an hour before I checked the tracking the first time.  Clearly Australia Post has problems
  4591. keeping up to date.
  4592.      </p>
  4593.  
  4594.      <p>
  4595. But better late than never:
  4596.      </p>
  4597.  
  4598.      <blockquote class="fullwidth">
  4599. <div style="text-align:left">
  4600.  <tt>
  4601. From: Australia Post &lt;noreply@notifications.auspost.com.au&gt;
  4602. <br />Subject: Your parcel from Returns is ready to collect
  4603. <br />Date: Fri, 20 Jun 2025 01:51:21 &#45;0600
  4604. <br />
  4605.  </tt>
  4606. </div>
  4607. </blockquote>
  4608.  
  4609.      <p>
  4610. And they still live somewhere in the <a href="https://en.wikipedia.org/wiki/Rocky_Mountains">Rocky Mountains</a>.  Why?  Converting
  4611. that to local time gives me 17:51:21, 4 hours after I picked it up.  By the evening I had no
  4612. email confirmation that it had been collected, though I did get this one an hour later
  4613. referring to another package that I had picked up at the same time:
  4614.      </p>
  4615.  
  4616.      <blockquote class="fullwidth">
  4617. <div style="text-align:left">
  4618.  <tt>
  4619. From: Australia Post &lt;noreply@notifications.auspost.com.au&gt;
  4620. <br />Subject: Your parcel from McLaren Vale Cellars has been collected
  4621. <br />Date: Fri, 20 Jun 2025 02:57:21 &#45;0600
  4622. <br />
  4623.  </tt>
  4624. </div>
  4625. </blockquote>
  4626.  
  4627.      <p>
  4628. We've been living on the Internet for over quarter of a century now.  When are companies
  4629. going to finally catch up with it?
  4630.      </p>
  4631.      </div>
  4632.    ]]>
  4633.  </description>
  4634.  <dc:creator>Greg Lehey</dc:creator>
  4635.  <dc:date>2025-06-21T02:10:53+00:00</dc:date>
  4636. </item>
  4637.  
  4638.                  
  4639. <!-- topic ko not selected
  4640.      <p>
  4641. <a href="http://www.lemis.com/grog/diary-jun2025.php?subtitle=Anatomy%20of%20a%20parcel%20delivery&amp;article=D-20250621-021053#D-20250621-021053">Yesterday's</a> parcel delivery was a set of three cast iron frying pans.
  4642.      </p>
  4643.  
  4644.      <p>
  4645. Why?  Don't I have enough already?  Yes, indeed: about 12 non-stick frying pans, 4 steel
  4646. pans, 3 <a href="https://en.wikipedia.org/wiki/Paellera">paelleras</a>, 3 cast iron
  4647. grill pans and a couple of others, which somehow add up to 26.  So why any more?
  4648.      </p>
  4649.  
  4650.      <p>
  4651. Part of it goes back to my great disappointment with the ceramic pans that I bought
  4652. <a href="http://www.lemis.com/grog/diary-feb2021.php?subtitle=New%20frying%20pan&amp;article=D-20210220-050258#D-20210220-050258">starting 4 years ago</a>.  At the time I was amazed by how good they were.  But it didn't
  4653. take long to be amazed by how quickly they deteriorated.  And <a href="http://www.lemis.com/yvonne/">Yvonne</a> uses an old-fashioned non-stick pan with a black surface:
  4654.      </p>
  4655.  
  4656.            
  4657.      <p>
  4658. That's only about a year old, and it takes forever to get the non-stuck food rests off.  So
  4659. I've been using steel pans for some time now, and basically I'm happy with them.  Only
  4660. they're bigger than I need for some things.  The smallest has a diameter of 24 cm, and I
  4661. wanted things with 20 cm and 16 cm.  And that's (almost) what I got: 3 pans with diameters
  4662. of 15.5 (“16”), 20 and 25 (“26”) cm for a reasonable price: $41.40 and $4 postage.  Why did
  4663. I buy them?  Another seller on <a href="https://www.ebay.com.au/">eBay</a> offers
  4664. the identical set for $39 and free postage.  But this one came with a 20% price reduction,
  4665. to be applied at checkout, so I only paid $36.75.  That's irritating in a sense: it shows
  4666. that you can't rely on the indicated price to get the best deal.
  4667.      </p>
  4668.  
  4669.      <p>
  4670. So, non-stick, are they?
  4671.      </p>
  4672.  
  4673.      
  4674.      <p>
  4675. That the 15.5 cm pan, and it looks particularly rough.  Will things really not stick?  I'll
  4676. see when I try to fry an egg in it.
  4677.      </p>
  4678.  
  4679.      <p>
  4680. Today I used the 25 cm one to prepare breakfast, <a href="http://www.lemis.com/grog/recipes/KL-Hokkien-Mee.php">KL Hokkien Mee</a>.  Two things became apparent: the completely flat bottom, something
  4681. that I haven't really seen in frying pans, and that the handle became too hot to touch after
  4682. frying the pork skin for some time.  I particularly appreciate the flat bottom.  And at the
  4683. end yes, <i>nothing</i> had stuck, which is even better than with the steel pans.  But that
  4684. was with (aqueous) liquid.  We'll see how it goes with straight frying.
  4685.      </p>
  4686.  
  4687.      <p>
  4688. Another thing that I found to be an advantage was that they should go into the dishwasher.
  4689. In principle the steel ones would too, but the handles are too long.  Yes, the pan got clean
  4690. in the dishwasher, but it also showed signs of rust, which I didn't expect.  I'll have to
  4691. see whether I can address that by drying them as soon as the dishwasher is finished.
  4692.      </p>
  4693.      
  4694. End deselected topic ko (New frying pans) -->
  4695.  
  4696.            
  4697. <!-- topic g not selected
  4698.      <p>
  4699. Today was the June solstice, time for my monthly <a href="http://www.lemis.com/grog/Albums/garden/Flowers.php">garden flower photos</a>.  The garden continues to
  4700. decline, and winter isn't the best of times anyway.  Jesse Walsh came on the 20th and tidied
  4701. some stuff up, but about the only thing of interest was the discovery of why some branches
  4702. of the <a href="https://en.wikipedia.org/wiki/Abutilon">Abutilon</a> in front of the
  4703. laundry door died off.  It seems that a part of the root died, possibly as the result of a
  4704. fungus.  Here the stump:
  4705.      </p>
  4706.  
  4707.      
  4708.      <p>
  4709. Our <a href="https://en.wikipedia.org/wiki/Grevillea">Grevilleas</a> have never done
  4710. well, but at the moment two of them are looking better:
  4711.      </p>
  4712.  
  4713.            
  4714.      <p>
  4715. And I'm gradually coming to the conclusion that the <a href="https://en.wikipedia.org/wiki/Solstice">solstice</a> is a good time for <a href="https://en.wikipedia.org/wiki/Hibiscus_rosa-sinensis">Hibiscus rosa-sinensis</a>:
  4716.      </p>
  4717.  
  4718.      <div align="left">
  4719.      </div>
  4720.  
  4721.      <p>
  4722. The first one was grown from a cutting that I made <a href="http://www.lemis.com/grog/diary-jan2025.php?subtitle=Little%20garden%20work&amp;article=D-20250127-014406#D-20250127-014406">only 5 months ago</a>.
  4723.      </p>
  4724.  
  4725.      <p>
  4726. A thing that we have only just noticed now is the <a href="https://en.wikipedia.org/wiki/Callistemon">Callistemon</a> that our neighbour Diane
  4727. had planted on the property boundary:
  4728.      </p>
  4729.  
  4730.            
  4731.      <p>
  4732. It's strange that it should have any flowers at all right now, but it looks as if it has
  4733. flowered multiple times without us noticing.
  4734.      </p>
  4735.      
  4736. End deselected topic g (Garden flowers in mid-winter) -->
  4737.  
  4738.            
  4739. <item>
  4740. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250621-235639</guid>
  4741. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250621-235639</link>
  4742. <category>technology</category>
  4743. <title>Preparing new lagoon</title>
  4744.  <description>
  4745.    <![CDATA[
  4746.    <div align="justify">
  4747.      <p>
  4748. Somehow I have a horror of doing work on computers lately.  I'm continually running into
  4749. unexpected issues.  But it has to be done.  I've ordered a new <a href="https://en.wikipedia.org/wiki/M.2">M.2</a> <a href="https://en.wikipedia.org/wiki/SSD">SSD</a> for what is
  4750. currently <i>disdain.lemis.com</i>.  After <a href="http://www.lemis.com/grog/diary-jun2025.php?topics=c&amp;subtitle=DxO%20for%20disdain&amp;article=D-20250618-015049#D-20250618-015049">discovering</a> that it was barely faster than <i>distress.lemis.com</i>, I decided to
  4751. turn it into a new machine for <a href="http://www.lemis.com/yvonne/">Yvonne</a>.
  4752.      </p>
  4753.  
  4754.      <p>
  4755. OK, but how do I get the old SSD out?  I had had issues with the SSD <a href="http://www.lemis.com/grog/diary-feb2025.php?subtitle=disdain&amp;article=D-20250221-012141#D-20250221-012141">when I got the box</a>: the retaining screw for the SSD couldn't be tightened or
  4756. loosened.  How do I change it?
  4757.      </p>
  4758.  
  4759.      <p>
  4760. More investigation showed that the SSD is mounted on a removable plastic frame:
  4761.      </p>
  4762.  
  4763.      <div align="left">
  4764.  <a id="Photo-40" name="Photo-40"
  4765.          href="diary-jun2025.php?dirdate=20250622&amp;imagesizes=11111111111111111111111111111111111111112&amp;topics=c&amp;edit=0#Photo-40">
  4766.          <img alt="This should be SSD-mounting-1.jpeg.  Is it missing?" border="0" id="Photo_40"
  4767.               title="Photo SSD-mounting-1.jpeg.  Click to redisplay larger version of image."
  4768.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250622/small/SSD-mounting-1.jpeg"
  4769.               width="225" height="300"
  4770.           /></a>
  4771.  <a id="Photo-41" name="Photo-41"
  4772.          href="diary-jun2025.php?dirdate=20250622&amp;imagesizes=111111111111111111111111111111111111111112&amp;topics=c&amp;edit=0#Photo-41">
  4773.          <img alt="This should be SSD-mounting-4.jpeg.  Is it missing?" border="0" id="Photo_41"
  4774.               title="Photo SSD-mounting-4.jpeg.  Click to redisplay larger version of image."
  4775.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250622/small/SSD-mounting-4.jpeg"
  4776.               width="225" height="300"
  4777.           /></a>
  4778.  <a id="Photo-42" name="Photo-42"
  4779.          href="diary-jun2025.php?dirdate=20250622&amp;imagesizes=1111111111111111111111111111111111111111112&amp;topics=c&amp;edit=0#Photo-42">
  4780.          <img alt="This should be SSD-mounting-9.jpeg.  Is it missing?" border="0" id="Photo_42"
  4781.               title="Photo SSD-mounting-9.jpeg.  Click to redisplay larger version of image."
  4782.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250622/small/SSD-mounting-9.jpeg"
  4783.               width="300" height="225"
  4784.           /></a>
  4785.      </div>
  4786.  
  4787.      <p>
  4788. And as I suspected, there's a loose nut on the other side:
  4789.      </p>
  4790.  
  4791.        <a id="Photo-43" name="Photo-43"
  4792.          href="diary-jun2025.php?dirdate=20250622&amp;imagesizes=11111111111111111111111111111111111111111112&amp;topics=c&amp;edit=0#Photo-43">
  4793.          <img alt="This should be SSD-mounting-5.jpeg.  Is it missing?" border="0" id="Photo_43"
  4794.               title="Photo SSD-mounting-5.jpeg.  Click to redisplay larger version of image."
  4795.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250622/small/SSD-mounting-5.jpeg"
  4796.               width="302" height="223"
  4797.           /></a>
  4798.  
  4799.      <p>
  4800. How can that work?  Did the seller do a quick fix?  But then I saw the small hole next to
  4801. the screw hole:
  4802.      </p>
  4803.  
  4804.        <a id="Photo-44" name="Photo-44"
  4805.          href="diary-jun2025.php?dirdate=20250622&amp;imagesizes=111111111111111111111111111111111111111111112&amp;topics=c&amp;edit=0#Photo-44">
  4806.          <img alt="This should be SSD-mounting-4-detail.jpeg.  Is it missing?" border="0" id="Photo_44"
  4807.               title="Photo SSD-mounting-4-detail.jpeg.  Click to redisplay larger version of image."
  4808.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250622/small/SSD-mounting-4-detail.jpeg"
  4809.               width="289" height="233"
  4810.           /></a>
  4811.  
  4812.      <p>
  4813. Is that intended to stop the nut turning?  Yes!
  4814.      </p>
  4815.  
  4816.        <a id="Photo-45" name="Photo-45"
  4817.          href="diary-jun2025.php?dirdate=20250622&amp;imagesizes=1111111111111111111111111111111111111111111112&amp;topics=c&amp;edit=0#Photo-45">
  4818.          <img alt="This should be SSD-mounting-6.jpeg.  Is it missing?" border="0" id="Photo_45"
  4819.               title="Photo SSD-mounting-6.jpeg.  Click to redisplay larger version of image."
  4820.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250622/small/SSD-mounting-6.jpeg"
  4821.               width="300" height="225"
  4822.           /></a>
  4823.        <a id="Photo-46" name="Photo-46"
  4824.          href="diary-jun2025.php?dirdate=20250622&amp;imagesizes=11111111111111111111111111111111111111111111112&amp;topics=c&amp;edit=0#Photo-46">
  4825.          <img alt="This should be SSD-mounting-7.jpeg.  Is it missing?" border="0" id="Photo_46"
  4826.               title="Photo SSD-mounting-7.jpeg.  Click to redisplay larger version of image."
  4827.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250622/small/SSD-mounting-7.jpeg"
  4828.               width="300" height="225"
  4829.           /></a>
  4830.  
  4831.      <p>
  4832. So I <i>can</i> mount a new SSD with no problems.
  4833.      </p>
  4834.  
  4835.      <p>
  4836. In passing, it seems that the frame, but not the motherboard, is designed for two SSDs.
  4837.      </p>
  4838.      </div>
  4839.    ]]>
  4840.  </description>
  4841.  <dc:creator>Greg Lehey</dc:creator>
  4842.  <dc:date>2025-06-21T23:56:39+00:00</dc:date>
  4843. </item>
  4844.  
  4845.            
  4846.            
  4847. <!-- topic ko not selected
  4848.      <p>
  4849. <a href="http://www.lemis.com/grog/recipes/steak-and-kidney.php">Steak and kidney pie</a> tonight.
  4850. <a href="http://www.lemis.com/grog/diary-feb2025.php?subtitle=Steak%20and%20kidney%20again&amp;article=D-20250210-001337#D-20250210-001337">Last time</a> were were quite happy with the results, and this was made from the same
  4851. batch.  But I had forgotten to write down the quantities that we wanted to reduce.  I think
  4852. 120 g for me and 60 g for <a href="http://www.lemis.com/yvonne/">Yvonne</a> would be enough.
  4853.      </p>
  4854.  
  4855.      <p>
  4856. But we both didn't like it!  Last time I had thought that the chuck steak was good enough.
  4857. This time it was almost unpleasant.  Are our steak and kidney days over?
  4858.      </p>
  4859.      
  4860. End deselected topic ko (Steak and kidney revisited) -->
  4861.  
  4862.                  
  4863. <item>
  4864. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250623-020020</guid>
  4865. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250623-020020</link>
  4866. <category>technology</category>
  4867. <category>opinion</category>
  4868. <title>Travelling the world with Google Maps</title>
  4869.  <description>
  4870.    <![CDATA[
  4871.    <div align="justify">
  4872.      <p>
  4873. <a href="https://en.wikipedia.org/wiki/Google_Maps">Google Maps</a> is quite useful
  4874. for a number of things, but Google seems to have a “there can only be one” mentality.  What
  4875. I do in one place (office computers, phone, TV) gets relayed to the others, even to the
  4876. point of changing vehicle or map view.  And it produces nonsense like this:
  4877.      </p>
  4878.  
  4879.        <a id="Photo-47" name="Photo-47"
  4880.          href="diary-jun2025.php?dirdate=20250622&amp;imagesizes=111111111111111111111111111111111111111111111112&amp;topics=c&amp;edit=0#Photo-47">
  4881.          <img alt="This should be Google-Maps-nonsense-detail.jpeg.  Is it missing?" border="0" id="Photo_47"
  4882.               title="Photo Google-Maps-nonsense-detail.jpeg.  Click to redisplay larger version of image."
  4883.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250622/small/Google-Maps-nonsense-detail.jpeg"
  4884.               width="358" height="189"
  4885.           /></a>
  4886.  
  4887.      <p>
  4888. That's in <a href="https://en.wikipedia.org/wiki/Hamburg">Hamburg</a> (and
  4889. coincidentally the title of an <a href="https://www.imdb.com/title/tt0036882/">ancient
  4890. film</a>).  Surely Google Maps, of all apps, should know that I haven't been within 10,000
  4891. km of that location.
  4892.      </p>
  4893.      </div>
  4894.    ]]>
  4895.  </description>
  4896.  <dc:creator>Greg Lehey</dc:creator>
  4897.  <dc:date>2025-06-23T02:00:20+00:00</dc:date>
  4898. </item>
  4899.  
  4900.            
  4901. <!-- topic ko not selected
  4902.      <p>
  4903. To my surprise, <a href="http://www.lemis.com/yvonne/">Yvonne</a> had never heard of <a href="https://en.wikipedia.org/wiki/Pilau">pilau</a>.  OK, make one.  Last week I picked up
  4904. this mixture:
  4905.      </p>
  4906.  
  4907.            
  4908.      <p>
  4909. The usual issues with the instructions, including two different  implicit definition of
  4910. <a href="http://www.lemis.com/grog/recipes/measures.php#cups">cups</a>: 175 ml and 200 ml, neither of which
  4911. come close to the US “cup” (between 236 and 240 ml) or the Australian “cup” (250 ml).  What
  4912. I made of (half of it) was:
  4913.      </p>
  4914.  
  4915.    <h3>Ingredients</h3>
  4916.  
  4917.          <table summary="Ingredients">
  4918.        <tr>
  4919.          <td align="right"><b>quantity</b></td>
  4920.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  4921.          <td><b>ingredient</b> </td>
  4922.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  4923.          <td><b>step</b> </td>
  4924.        </tr>
  4925.  
  4926.       <tr>
  4927.          <td valign="top" align="right">400 g</td>
  4928.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  4929.          <td valign="top" align="left">basmati rice</td>
  4930.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  4931.          <td valign="top" align="right">1</td>
  4932.       </tr>
  4933.       <tr>
  4934.         <td>
  4935.         </td>
  4936.       </tr>
  4937.  
  4938.       <tr>
  4939.          <td valign="top" align="right">450 g</td>
  4940.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  4941.          <td valign="top" align="left">cooked lamb shoulder</td>
  4942.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  4943.          <td valign="top" align="right">2</td>
  4944.       </tr>
  4945.  
  4946.       <tr>
  4947.          <td valign="top" align="right">25 g</td>
  4948.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  4949.          <td valign="top" align="left">ghee</td>
  4950.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  4951.          <td valign="top" align="right">2</td>
  4952.       </tr>
  4953.  
  4954.       <tr>
  4955.          <td valign="top" align="right">25 g</td>
  4956.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  4957.          <td valign="top" align="left">garlic paste</td>
  4958.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  4959.          <td valign="top" align="right">2</td>
  4960.       </tr>
  4961.  
  4962.       <tr>
  4963.          <td valign="top" align="right">15 g</td>
  4964.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  4965.          <td valign="top" align="left">ginger paste</td>
  4966.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  4967.          <td valign="top" align="right">2</td>
  4968.       </tr>
  4969.  
  4970.       <tr>
  4971.          <td valign="top" align="right">25 g (½ packet)</td>
  4972.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  4973.          <td valign="top" align="left">Shan pilau biryani spice mix</td>
  4974.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  4975.          <td valign="top" align="right">2</td>
  4976.       </tr>
  4977.       <tr>
  4978.         <td>
  4979.         </td>
  4980.       </tr>
  4981.  
  4982.       <tr>
  4983.          <td valign="top" align="right">100 g</td>
  4984.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  4985.          <td valign="top" align="left">yoghurt</td>
  4986.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  4987.          <td valign="top" align="right">3</td>
  4988.       </tr>
  4989.       <tr>
  4990.         <td>
  4991.         </td>
  4992.       </tr>
  4993.  
  4994.       <tr>
  4995.          <td valign="top" align="right">700 g</td>
  4996.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  4997.          <td valign="top" align="left">broth</td>
  4998.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  4999.          <td valign="top" align="right">4</td>
  5000.       </tr>
  5001.       <tr>
  5002.         <td>
  5003.         </td>
  5004.       </tr>
  5005.  
  5006.       <tr>
  5007.          <td valign="top" align="right">25 g</td>
  5008.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  5009.          <td valign="top" align="left">almonds, blanched</td>
  5010.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  5011.          <td valign="top" align="right">5</td>
  5012.       </tr>
  5013.  
  5014.       <tr>
  5015.          <td valign="top" align="right">20 g</td>
  5016.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  5017.          <td valign="top" align="left">pistachio kernels</td>
  5018.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  5019.          <td valign="top" align="right">5</td>
  5020.       </tr>
  5021.       <tr>
  5022.         <td>
  5023.         </td>
  5024.       </tr>
  5025.  
  5026.       <tr>
  5027.          <td valign="top" align="right">50 g</td>
  5028.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  5029.          <td valign="top" align="left">onion</td>
  5030.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  5031.          <td valign="top" align="right">6</td>
  5032.       </tr>
  5033.      </table>
  5034.  
  5035.      <h3>
  5036. Preparation
  5037.      </h3>
  5038.  
  5039.      <ol>
  5040.        <li class="fullwidth">
  5041.          <div class="listitemwidth">
  5042.            Wash the rice and leave in water to soak during the other actions.  Heat the oven to
  5043.            200° and place a pan of water at the bottom.
  5044.          </div>
  5045.        </li>
  5046.  
  5047.        <li class="fullwidth">
  5048.          <div class="listitemwidth">
  5049.            Cut the meat into bite-sized pieces and fry with the garlic, ginger and spices in the
  5050.            ghee until hot.
  5051.          </div>
  5052.        </li>
  5053.  
  5054.        <li class="fullwidth">
  5055.          <div class="listitemwidth">
  5056.            Add yoghurt and reserve.
  5057.          </div>
  5058.        </li>
  5059.  
  5060.        <li class="fullwidth">
  5061.          <div class="listitemwidth">
  5062.            Drain the rice, add broth and cook.  When the rice is cooked, put half in a serving
  5063.            dish, add the meat and spice mix, and put the rest on top.  Place in the oven to steam
  5064.            for about 10 minutes.
  5065.          </div>
  5066.        </li>
  5067.  
  5068.        <li class="fullwidth">
  5069.          <div class="listitemwidth">
  5070.            Fry the nuts in the ghee.  Remove and reserve.
  5071.          </div>
  5072.        </li>
  5073.  
  5074.        <li class="fullwidth">
  5075.          <div class="listitemwidth">
  5076.            Cut the onion into strips and fry in the remaining ghee.  Place nuts and onion on top of
  5077.            the rice.  Serve after a few minutes.
  5078.          </div>
  5079.        </li>
  5080.      </ol>
  5081.  
  5082.      <p>
  5083. It didn't taste bad, though the meat was a little tough.  <a href="http://www.lemis.com/grog/recipes/lamb-pilau-biriani.php">Next time</a> I'll do it as intended with raw meat.
  5084.      </p>
  5085.      
  5086. End deselected topic ko (Pilau) -->
  5087.  
  5088.            
  5089. <item>
  5090. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250623-020056</guid>
  5091. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250623-020056</link>
  5092. <category>language</category>
  5093. <category>technology</category>
  5094. <category>photography</category>
  5095. <category>opinion</category>
  5096. <title>Pilau instructions</title>
  5097.  <description>
  5098.    <![CDATA[
  5099.    <div align="justify">
  5100.  
  5101.      <p>
  5102. The instructions for the <a href="http://www.lemis.com/grog/diary-jun2025.php?subtitle=Pilau&amp;article=D-20250623-020023#D-20250623-020023">pilau</a> were interesting for a number of reasons.  Apart from their confusion about the
  5103. size of cups, I had:
  5104.      </p>
  5105.  
  5106.        <a id="Photo-48" name="Photo-48"
  5107.          href="diary-jun2025.php?dirdate=20250617&amp;imagesizes=1111111111111111111111111111111111111111111111112&amp;topics=c&amp;edit=0#Photo-48">
  5108.          <img alt="This should be Pilau-biriani-2-detail.jpeg.  Is it missing?" border="0" id="Photo_48"
  5109.               title="Photo Pilau-biriani-2-detail.jpeg.  Click to redisplay larger version of image."
  5110.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250617/small/Pilau-biriani-2-detail.jpeg"
  5111.               width="258" height="261"
  5112.           /></a>
  5113.  
  5114.      <blockquote class="fullwidth">
  5115. <p class="listitemwidth">
  5116.  Heat 1 cup (175ml) of cooking oil and fry 1 (75g) small, finely liced onion until golden.
  5117. </p>
  5118.  
  5119. <p class="listitemwidth">
  5120.  Use long grain old basmati rice. Beginners must use parboiled/Sayla rice.
  5121. </p>
  5122.      </blockquote>
  5123.  
  5124.      <p>
  5125. Do they really want to (deep) fry 75 g of onion in a 175 ml cup of oil?  Or is this a
  5126. mistake?  I would have thought oil is a mistake: it should be (much less) ghee.  But the
  5127. fact that they mention both “cups” and millilitres suggests that they really mean it.  I'm puzzled.
  5128.      </p>
  5129.  
  5130.      <p>
  5131. To quote these gems, it seemed reasonable to look for a text version of the image.  A bit of
  5132. searching brought me to <a href="https://www.newocr.com/">Free Online OCR</a>, which
  5133. amazed me with its inaccuracy.  Here the complete text, errors highlighted in <font color="red">red</font>:
  5134.      </p>
  5135.  
  5136.      <blockquote class="fullwidth">
  5137. <div style="text-align:left">
  5138.  <tt>
  5139. STEPS OF COOKING
  5140. <br />
  5141. <br />1. Take 1kg (2.2lbs) meat with bones, cut into small portions
  5142. <br />(<font color="red">ChickenyGoat</font>/<font color="red">Beet</font>/Lamb), 1&#45;2 tbsp Shan Garlic Paste, 1&#45;2 tbsp
  5143. <br /><font color="red">shan</font> Ginger Paste and 1 packet Shan Pilau Biryani Mix. Add to
  5144. <br />water (Beef/Goat/Lamb 2 cups; Chicken 1 cup). Cover and cook
  5145. <br />on low heat until meat is tender (about 1 cup of stock should
  5146. <br />remain in the pot).
  5147. <br />
  5148. <br />2. Stir in 1 cup <font color="red">7009</font> of plain, whipped yogurt and keep aside.
  5149. <br />
  5150. <br />3. Separately: Wash <font color="red">3%</font> cups (750g) of Shan Basmati Rice <font color="red">ancHet</font> it
  5151. <br />soak.
  5152. <br />
  5153. <br />Boil 15 cups (3 litres) of water and stir in 2 <font color="red">tosp</font> of Shan Salt and
  5154. <br />the soaked rice. Boil the rice until <font color="red">%th</font> cooked. Remove and drain
  5155. <br />thoroughly.
  5156. <br />
  5157. <br />4. Spread half the rice in a pot and pour the meat curry over it. Top
  5158. <br />with &nbsp;<font color="red">ine</font> remaining rice. Sprinkle <font color="red">%</font> tsp yellow food colour if
  5159. <br />
  5160. <br /><font color="red">esired.</font>
  5161. <br />
  5162. <br />9. Heat 1 cup (175ml) of cooking oil and fry 1 (75g) small, finely
  5163. <br />liced onion until golden. Pour <font color="red">eventy</font> over the <font color="red">nce</font>. Cover and
  5164. <br />cook on low heat until the rice is tender (5&#45;10 mins). Mix before
  5165. <br />serving.
  5166. <br />
  5167. <br />Cooking <font color="red">Tips</font> Use long grain old basmati rice. Beginners must use
  5168. <br /><font color="red">par&nbsp;iled</font>/Sayla rice.
  5169. <br />
  5170. <br /><font color="red">or</font> best results, use meat cuts from the breast and shoulder.
  5171.  </tt>
  5172. </div>
  5173. </blockquote>
  5174.  
  5175.      <p>
  5176. Yes, the photo isn't as sharp as I would have liked (something that I should investigate),
  5177. but it can't excuse these errors.
  5178.      </p>
  5179.      </div>
  5180.    ]]>
  5181.  </description>
  5182.  <dc:creator>Greg Lehey</dc:creator>
  5183.  <dc:date>2025-06-23T02:00:56+00:00</dc:date>
  5184. </item>
  5185.  
  5186.                  
  5187. <!-- topic PHo not selected
  5188.      <p>
  5189. It's been <a href="http://www.lemis.com/grog/diary-mar2003.php#Iraq">22 years</a> since the USA,
  5190. sadly with Australian assistance, started a war against <a href="https://en.wikipedia.org/wiki/Iraq">Iraq</a>, or maybe against the government of
  5191. <a href="https://en.wikipedia.org/wiki/Saddam_Hussein">Saddam Hussein</a>.  They
  5192. had <i>weapons of mass destruction</i>!  Or at least, that's what the aggressors claimed,
  5193. despite no evidence whatsoever.  So they waged a war that destroyed the country and brought
  5194. no useful results, so after 8 years they left again, leaving behind a country in ruins.
  5195. History has not been kind to them.
  5196.      </p>
  5197.  
  5198.      <p>
  5199. But that was over 20 years ago!  And <a href="https://en.wikipedia.org/wiki/Iran">Iran</a> has weapons of mass destruction!  Oh, no, that's an old, worn-out magic word.
  5200. Iran has nukes!  Oh, maybe not, but they can make them.  At least, that's what they say.  In
  5201. contrast to <a href="https://en.wikipedia.org/wiki/Israel">Israel</a>, Iran denies
  5202. any such thing.  And in contrast to Iraq, Iran has allowed inspectors from the <a href="https://en.wikipedia.org/wiki/International_Atomic_Energy_Agency">International Atomic
  5203. Energy Agency</a> to inspect their facilities, and they found nothing pointing in that
  5204. direction.
  5205.      </p>
  5206.  
  5207.      <p>
  5208. So: bomb Israel to get them to stop their nuclear program?  No, Israel is a <i>friend</i>.
  5209. Bomb Iran!  Israel is only too happy to help.
  5210.      </p>
  5211.  
  5212.      <p>
  5213. What's wrong with this picture?  It's easier to ask what's right: nothing.  I read an
  5214. <a href="https://www.abc.net.au/news/2025-06-23/trump-us-iran-war-economy-china/105446938">interesting opinion piece</a> by <a href="https://en.wikipedia.org/wiki/Alan_Kohler">Alan Kohler</a> contrasting the Chinese and the US American approach.  It makes some
  5215. interesting points:
  5216.      </p>
  5217.  
  5218.      <blockquote class="fullwidth">
  5219. <p class="listitemwidth">
  5220.  Iran's regime is now being brought undone by its insistence on enriching uranium for
  5221.  nuclear weapons of war and refusing to give up.
  5222. </p>
  5223.  
  5224. <p class="listitemwidth">
  5225.  China's leaders still work on the old-fashioned idea that economic policy is for improving
  5226.  the prosperity of citizens and strengthening the country, not for conducting ideological
  5227.  culture wars, and that diplomacy is about winning friends and influencing people.
  5228. </p>
  5229.  
  5230. <p class="listitemwidth">
  5231.  Israel's moral foundations and international standing are being destroyed by its levelling
  5232.  of Gaza and refusal to accept a Palestinian state.
  5233. </p>
  5234.  
  5235. <p class="listitemwidth">
  5236.  Wars based on lies (Iraq) or that too long (Vietnam and Afghanistan) or go too far (Gaza)
  5237.  come with a crippling cost, sap morale, divide the country and erode global support.
  5238. </p>
  5239.      </blockquote>
  5240.  
  5241.      <p>
  5242. These are so obvious that I'm surprised I haven't seen them before.  One thing he didn't
  5243. mention is that the USA has left the moral high ground that allowed it to condemn Russia
  5244. over its invasion of Ukraine.  And what's the situation with the current Iranian government?
  5245. It has been a thorn in the collective eye of the West since its inception.  But, like with
  5246. Saddam Hussein, what's the alternative?  More and more I wonder if these people are capable
  5247. of seeing the Big Picture.
  5248.      </p>
  5249.      
  5250. End deselected topic PHo (Here we go again) -->
  5251.  
  5252.            
  5253. <!-- topic po not selected
  5254.      <p>
  5255. I spent some time <a href="http://www.lemis.com/grog/diary-jun2025.php?topics=p&amp;subtitle=More%20lens%20test%20thoughts&amp;article=D-20250615-022258#D-20250615-022258">last week</a> checking the sharpness of <a href="http://www.lemis.com/yana/">Yana's</a> new
  5256. <a href="https://www.panasonic.com/au/support/product-archives/lumix-cameras-video-cameras/lumix-g-lenses/h-x025e.html">Leica Summilux 25 mm f/1.4</a>.  I've put that on ice for the time being until I can find
  5257. a better way to compare lenses.
  5258.      </p>
  5259.  
  5260.      <p>
  5261. But I wasn't expecting to find problems with my own lenses, like this photo that I discussed
  5262. <a href="http://www.lemis.com/grog/diary-jun2025.php?subtitle=Pilau%20instructions&amp;article=D-20250623-020056#D-20250623-020056">yesterday</a>:
  5263.      </p>
  5264.  
  5265.      
  5266.      <p>
  5267. That's a crop from the bottom right of the photo.  But why is it so unsharp?  It was taken
  5268. (with flash) at 1/250 s and f/5.6, so it should be razor sharp.  Is it the lens ( <a href="https://www.dpreview.com/products/olympus/lenses/olympus_12-100_4p0_is_pro">M.Zuiko
  5269. Digital ED 12-100 mm f/4.0 IS <b>PRO</b></a>)?  That's one of my best lenses.
  5270.      </p>
  5271.  
  5272.      <p>
  5273. Today I tried the same photo with three different lenses: the 12-100, the <a href="https://www.dpreview.com/products/olympus/lenses/oly_30_3p5_macro">M.Zuiko Digital ED 30
  5274.        mm f/3.5 Macro</a> and the <a href="https://www.dpreview.com/products/olympus/lenses/olympus_12-200_3p5-6p3">M.Zuiko
  5275.        Digital ED 12-200 mm f/3.5-6.3</a>, all at 1/250 s and f/5.6.  The results in that
  5276.        order:
  5277.      </p>
  5278.  
  5279.                  
  5280.      <p>
  5281. Clearly the macro is the best.  And the other two?  Hard to say, though the results look
  5282. better than last week.  Maybe that's all you can expect of a zoom lens.
  5283.      </p>
  5284.      
  5285. End deselected topic po (Lens sharpness) -->
  5286.  
  5287.            
  5288. <item>
  5289. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250624-030707</guid>
  5290. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250624-030707</link>
  5291. <category>technology</category>
  5292. <category>opinion</category>
  5293. <title>New M.2 SSD</title>
  5294.  <description>
  5295.    <![CDATA[
  5296.    <div align="justify">
  5297.      <p>
  5298. My new 1 TB <a href="https://en.wikipedia.org/wiki/M.2">M.2</a> <a href="https://en.wikipedia.org/wiki/SSD">SSD</a> arrived today.  It looks slightly different
  5299. from the one in ex-<i>disdain</i> (bottom):
  5300.      </p>
  5301.  
  5302.        <a id="Photo-49" name="Photo-49"
  5303.          href="diary-jun2025.php?dirdate=20250624&amp;imagesizes=11111111111111111111111111111111111111111111111112&amp;topics=c&amp;edit=0#Photo-49">
  5304.          <img alt="This should be M.2-SSDs-3.jpeg.  Is it missing?" border="0" id="Photo_49"
  5305.               title="Photo M.2-SSDs-3.jpeg.  Click to redisplay larger version of image."
  5306.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250624/small/M.2-SSDs-3.jpeg"
  5307.               width="324" height="208"
  5308.           /></a>
  5309.  
  5310.      <p>
  5311. What's that?  Reading <a href="https://en.wikipedia.org/wiki/M.2">the Wikipedia
  5312. page</a> explained some of it: the gaps are for keys, B and M.  M gives 4 <a href="https://en.wikipedia.org/wiki/PCI_Express">PCI Express</a> lanes, B only 2.  That's OK
  5313. with me.
  5314.      </p>
  5315.  
  5316.      <p>
  5317. But it doesn't work!  Why?  I can see three possibilities:
  5318.      </p>
  5319.  
  5320.      <ul>
  5321.        <li class="fullwidth">
  5322.          <div class="listitemwidth">
  5323.            B and M devices don't work on motherboards designed for M only.
  5324.          </div>
  5325.        </li>
  5326.  
  5327.        <li class="fullwidth">
  5328.          <div class="listitemwidth">
  5329.            B and M devices don't work on the <a href="https://en.wikipedia.org/wiki/ThinkCentre">ThinkCentre</a> V520S.
  5330.          </div>
  5331.        </li>
  5332.  
  5333.        <li class="fullwidth">
  5334.          <div class="listitemwidth">
  5335.            The device is defective.
  5336.          </div>
  5337.        </li>
  5338.      </ul>
  5339.  
  5340.      <p>
  5341. Which is it?  Ultimately it doesn't make that much difference, only the cost of the postage:
  5342. I can return it without any reason.
  5343.      </p>
  5344.      </div>
  5345.    ]]>
  5346.  </description>
  5347.  <dc:creator>Greg Lehey</dc:creator>
  5348.  <dc:date>2025-06-24T03:07:07+00:00</dc:date>
  5349. </item>
  5350.  
  5351.                  
  5352. <!-- topic ko not selected
  5353.      <p>
  5354. Fried my first egg in the middle one of the cast iron pans I got <a href="http://www.lemis.com/grog/diary-jun2025.php?topics=k&amp;subtitle=New%20frying%20pans&amp;article=D-20250621-235620#D-20250621-235620">on Friday</a>.  Not a success.  The pans retain much more heat, so my normal method of
  5355. heating to 160° didn't work well:
  5356.      </p>
  5357.  
  5358.      
  5359.      <p>
  5360. And the egg <i>did</i> stick to the pan, as I had half expected:
  5361.      </p>
  5362.  
  5363.      
  5364.      <p>
  5365. Would it work better if I hadn't made the pan so hot?  I'll have to experiment, but it looks
  5366. as if this is one area where a conventional non-stick pan would work better.
  5367.      </p>
  5368.      
  5369. End deselected topic ko (Non-stick cast iron pans) -->
  5370.  
  5371.            
  5372. <item>
  5373. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250624-234346</guid>
  5374. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250624-234346</link>
  5375. <category>technology</category>
  5376. <category>photography</category>
  5377. <category>opinion</category>
  5378. <title>I hate the Ports Collection</title>
  5379.  <description>
  5380.    <![CDATA[
  5381.    <div align="justify">
  5382.      <p>
  5383. Somehow I've been fighting the <a href="https://www.freebsd.org/">FreeBSD</a> Ports
  5384. Collection for decades.  The idea is good: a unified method for installing and maintaining
  5385. all ports and their dependencies.  The reality looks different.  I want to update <a href="https://en.wikipedia.org/wiki/ExifTool">exiftool</a>.  Where is it?  You'd expect it
  5386. in <i>/usr/ports/graphics/exiftool</i>.  But no, it's a <a href="https://en.wikipedia.org/wiki/Perl">Perl</a> program, so they have obfuscated the
  5387. name.  But how?
  5388.      </p>
  5389.  
  5390.      <blockquote class="fullwidth">
  5391. <div style="text-align:left">
  5392.  <tt>
  5393. <code><font color="blue">=== root@hydra (/dev/pts/11)</font> <font color="red">~</font> <font color="blue">82</font> &#45;&gt; <b><tt>pkg search exiftool</tt></b></code>
  5394. <br />pkg: repository FreeBSD contains packages for wrong OS version: FreeBSD:13:amd64
  5395. <br /><code><font color="blue">=== root@hydra (/dev/pts/11)</font> <font color="red">~</font> <font color="blue">83</font> &#45;&gt; <b><tt>uname &#45;a</tt></b></code>
  5396. <br />FreeBSD hydra.lemis.com 13.4&#45;PRERELEASE FreeBSD 13.4&#45;PRERELEASE #1 stable/13&#45;n258139&#45;35bde8969eb6&#45;dirty: Sun Jul 28 08:42:07 AEST 2024 &nbsp; &nbsp; grog@hydra.lemis.com:/home/obj/home/src/FreeBSD/git/stable/13/amd64.amd64/sys/GENERIC amd64
  5397. <br />
  5398.  </tt>
  5399. </div>
  5400. </blockquote>
  5401.  
  5402.      <p>
  5403. So what's that about?  Finally I found the name:
  5404. it's <i>/usr/ports/graphics/p5-Image-ExifTool</i>.  But how do I update it?  I rely
  5405. on <i>exiftool</i> for so much, and I don't want to lose it.  OK, try it
  5406. on <i>tiwi.lemis.com</i>, where it's not installed.  Same thing:
  5407.      </p>
  5408.  
  5409.      <blockquote class="fullwidth">
  5410. <div style="text-align:left">
  5411.  <tt>
  5412. <code><font color="blue">=== root@tiwi (/dev/pts/4)</font> <font color="red">/var/tmp</font> <font color="blue">166</font> &#45;&gt; <b><tt>pkg search exiftool</tt></b></code>
  5413. <br />pkg: repository FreeBSD contains packages for wrong OS version: FreeBSD:13:amd64
  5414. <br />You have mail in /var/mail/grog
  5415. <br /><code><font color="blue">=== root@tiwi (/dev/pts/4)</font> <font color="red">/var/tmp</font> <font color="blue">167</font> &#45;&gt; <b><tt>uname &#45;a</tt></b></code>
  5416. <br />FreeBSD tiwi.lemis.com 13.1&#45;STABLE FreeBSD 13.1&#45;STABLE #1 stable/13&#45;n251977&#45;519b3b5b542d: Fri Jul 29 15:27:13 AEST 2022 &nbsp; &nbsp; grog@tiwi.lemis.com:/eureka/home/src/FreeBSD/obj/stable&#45;13/eureka/home/src/FreeBSD/git/stable&#45;13/amd64.amd64/sys/GENERIC amd64
  5417. <br />
  5418.  </tt>
  5419. </div>
  5420. </blockquote>
  5421.  
  5422.      <p>
  5423. This seems to be a new bug in <i>pkg</i>.  OK, install from the source directory.  Wrong
  5424. Perl version!  No, sorry, I'm not going to blow away who knows how many dependencies for a
  5425. test installation.
  5426.      </p>
  5427.  
  5428.      <p>
  5429. No matter: I can ignore the Ports Collection and download and install it directly, (almost)
  5430. following <a href="https://exiftool.org/install.html">these instructions</a>.  But
  5431. they're designed for <a href="https://en.wikipedia.org/wiki/Linux">Linux</a> and are
  5432. rather more complicated than needed.
  5433.      </p>
  5434.  
  5435.      <blockquote class="fullwidth">
  5436. <div style="text-align:left">
  5437.  <tt>
  5438. <code><font color="blue">=== root@tiwi (/dev/pts/4)</font> <font color="red">/var/tmp</font> <font color="blue">155</font> &#45;&gt; <b><tt>fetch https://exiftool.org/Image&#45;ExifTool&#45;13.31.tar.gz</tt></b></code>
  5439. <br /><code><font color="blue">=== root@tiwi (/dev/pts/4)</font> <font color="red">/var/tmp</font> <font color="blue">156</font> &#45;&gt; <b><tt>tar xvf Image&#45;ExifTool&#45;13.31.tar.gz</tt></b></code>
  5440. <br />x Image&#45;ExifTool&#45;13.31/: Cannot restore extended attributes: com.apple.provenance com.apple.provenance: No such file or directory
  5441. <br />x Image&#45;ExifTool&#45;13.31/exiftool: Cannot restore extended attributes: com.apple.provenance com.apple.provenance: No such file or directory
  5442. <br />x Image&#45;ExifTool&#45;13.31/fmt_files/: Cannot restore extended attributes: com.apple.provenance com.apple.provenance: No such file or directory
  5443. <br />...
  5444.  </tt>
  5445. </div>
  5446. </blockquote>
  5447.  
  5448.      <p>
  5449. What's that?  Clearly some Apple-related stuff that shouldn't be there.  Still, they're just
  5450. warnings.  Moving on,
  5451.      </p>
  5452.  
  5453.      <blockquote class="fullwidth">
  5454. <div style="text-align:left">
  5455.  <tt>
  5456. <code><font color="blue">=== root@tiwi (/dev/pts/4)</font> <font color="red">/var/tmp</font> <font color="blue">157</font> &#45;&gt; <b><tt>cd Image&#45;ExifTool&#45;13.31</tt></b></code>
  5457. <br /><code><font color="blue">=== root@tiwi (/dev/pts/4)</font> <font color="red">/var/tmp/Image&#45;ExifTool&#45;13.31</font> <font color="blue">158</font> &#45;&gt; <b><tt>perl Makefile.PL</tt></b></code>
  5458. <br />Checking if your kit is complete...
  5459. <br />Looks good
  5460. <br />Generating a Unix&#45;style Makefile
  5461. <br />Writing Makefile for Image::ExifTool
  5462. <br />Writing MYMETA.yml and MYMETA.json
  5463. <br /><code><font color="blue">=== root@tiwi (/dev/pts/4)</font> <font color="red">/var/tmp/Image&#45;ExifTool&#45;13.31</font> <font color="blue">159</font> &#45;&gt; <b><tt>make test</tt></b></code>
  5464. <br />...
  5465. <br />t/ZISRAW.t ......... ok
  5466. <br />All tests successful.
  5467. <br />Files=111, Tests=595, 43 wallclock secs ( 0.27 usr &nbsp;0.15 sys + 39.59 cusr &nbsp;2.37 csys = 42.38 CPU)
  5468. <br />Result: PASS
  5469. <br /><code><font color="blue">=== root@tiwi (/dev/pts/4)</font> <font color="red">/var/tmp/Image&#45;ExifTool&#45;13.31</font> <font color="blue">161</font> &#45;&gt; <b><tt>make install</tt></b></code>
  5470. <br />Manifying 1 pod document
  5471. <br />Manifying 203 pod documents
  5472. <br />Installing /usr/local/lib/perl5/site_perl/Image/ExifTool.pm
  5473. <br />Installing /usr/local/lib/perl5/site_perl/Image/ExifTool.pod
  5474. <br />...
  5475.  </tt>
  5476. </div>
  5477. </blockquote>
  5478.  
  5479.      <p>
  5480. And that Just Worked, modulo the strange messages.  Somehow the Ports Collection has become
  5481. too fragile.
  5482.      </p>
  5483.      </div>
  5484.    ]]>
  5485.  </description>
  5486.  <dc:creator>Greg Lehey</dc:creator>
  5487.  <dc:date>2025-06-24T23:43:46+00:00</dc:date>
  5488. </item>
  5489.  
  5490.            
  5491. <item>
  5492. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250624-235934</guid>
  5493. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250624-235934</link>
  5494. <category>technology</category>
  5495. <category>opinion</category>
  5496. <title>M.2 SSD woes</title>
  5497.  <description>
  5498.    <![CDATA[
  5499.    <div align="justify">
  5500.      <p>
  5501. More investigation of my <a href="https://en.wikipedia.org/wiki/SSD">SSD</a> problems today.  Jamie Fraser came up with <a href="https://psref.lenovo.com/syspool/Sys/PDF/Lenovo_Desktops/Lenovo_V520S_SFF/Lenovo_V520S_SFF_Spec.PDF">this (PDF) summary</a> of the Lenovo V520S configuration.  The important part is
  5502.      </p>
  5503.  
  5504.      <blockquote class="fullwidth">
  5505.        <div class="listitemwidth">
  5506.          M.2 Solid State Drive (SSD)/PCIe NVMe,PCIe 3.0 x 4,32 Gb/s
  5507.        </div>
  5508.      </blockquote>
  5509.  
  5510.      <p>
  5511. A <a href="https://gemini.google.com/app/af71518d0e44960e">check</a> with <a href="https://gemini.google.com/">Google Gemini</a> confirms:
  5512.      </p>
  5513.  
  5514.      <blockquote class="fullwidth">
  5515.        <div class="listitemwidth">
  5516.          Protocols/Interfaces: This is the crucial part. The keying only dictates the physical
  5517.          shape. The actual communication protocol is what matters for functionality:
  5518.  
  5519.  <ul>
  5520.        <li class="fullwidth">
  5521.          <div class="list2width">
  5522.            M-key slots are typically designed for PCIe x4 (NVMe) SSDs, offering the highest
  5523.            speeds. They can sometimes also support SATA, but this depends on the motherboard.
  5524.          </div>
  5525.        </li>
  5526.  
  5527.        <li class="fullwidth">
  5528.          <div class="list2width">
  5529.  
  5530.    B-key slots are typically designed for SATA SSDs or PCIe x2 SSDs.
  5531.          </div>
  5532.        </li>
  5533.  
  5534.        <li class="fullwidth">
  5535.          <div class="list2width">
  5536.  
  5537.    B+M keyed SSDs can use either the SATA protocol or the PCIe x2 protocol.
  5538.          </div>
  5539.        </li>
  5540.  </ul>
  5541.        </div>
  5542.      </blockquote>
  5543.  
  5544.      <p>
  5545. Both <b>B</b> and <b>M</b> can support <a href="https://en.wikipedia.org/wiki/SATA">SATA</a>, but the V520S doesn't.  That makes sense: PCIe x 4 is much faster.  But the new
  5546. SSD is specifically marked <b>SATA</b>.  So they're not compatible.
  5547.      </p>
  5548.  
  5549.      <p>
  5550. I had hoped that this kind of incompatibility would be a thing of the past.  What other
  5551. dangers are lurking?
  5552.      </p>
  5553.      </div>
  5554.    ]]>
  5555.  </description>
  5556.  <dc:creator>Greg Lehey</dc:creator>
  5557.  <dc:date>2025-06-24T23:59:34+00:00</dc:date>
  5558. </item>
  5559.  
  5560.            
  5561. <!-- topic GPho not selected
  5562.      <p>
  5563. I've been keeping up with international news in some detail for years now, but the news is
  5564. getting worse all the time.  It's having its effect: today I had a stress stomach ache for
  5565. much of the afternoon.  I can't change what's going on; I should try not to follow it in as
  5566. much detail.  About the only good news today was that <a href="https://en.wikipedia.org/wiki/Donald_Trump">Donald Trump</a> swore at <a href="https://en.wikipedia.org/wiki/Benjamin_Netanyahu">Bibi</a> for his aggressive
  5567. behaviour.  Could this be the start of a change in heart?
  5568.      </p>
  5569.      
  5570. End deselected topic GPho (News: bad for health) -->
  5571.  
  5572.                  
  5573. <!-- topic G not selected
  5574.      <p>
  5575. I had some back pain a few days ago in an area that seemed like the same as I had with my
  5576. <a href="https://en.wikipedia.org/wiki/Slipped_disk">slipped disk</a> <a href="http://www.lemis.com/grog/diary-jun2023.php?subtitle=Pain!&amp;article=D-20230609-025722#D-20230609-025722">two years ago</a>.  I'm in no pain now, but I want it to stay that way, so into town this
  5577. morning to see Heather Dalman again, the first time in <a href="http://www.lemis.com/grog/diary-sep2023.php#D-20230907-020259">nearly two years</a>.  She has
  5578. <a href="https://www.chhn.com.au/">changed employers</a> since then.
  5579.      </p>
  5580.  
  5581.      <p>
  5582. Yes, good that I came, and I had some particularly hard knots in the muscles in that area.
  5583. She gave me some new “isometric” exercises to do, mercifully less obnoxious than the old
  5584. ones.  She also reminded me to stop crossing my legs, something that <a href="http://www.lemis.com/grog/diary-jun2023.php?subtitle=Next%20back%20pain%20procedure&amp;article=D-20230621-030929#D-20230621-030929">she had mentioned before</a>, but which seems to be generally a bad idea.  Hopefully that
  5585. will be the end of it.
  5586.      </p>
  5587.      
  5588. End deselected topic G (More physiotherapy) -->
  5589.  
  5590.            
  5591. <!-- topic ho not selected
  5592.      <p>
  5593. Is it worth repairing our dishwasher?  It's <a href="http://www.lemis.com/grog/diary-may2018.php?subtitle=Dish%20washer,%20day%202&amp;article=D-20180509-014944#D-20180509-014944">7 years old</a>, and the repair will probably cost at least $200.  We paid $398 for it at
  5594. the time, and as it happens we're coming to the end of the financial year, where there are
  5595. lots of specials at <a href="https://www.thegoodguys.com.au/">The Good Guys</a>,
  5596. including dishwashers from $369, and offering discounts of $40 to $60.  Should we maybe
  5597. replace the old one?  While in town dropped in to take a look at what they had.
  5598.      </p>
  5599.  
  5600.      <p>
  5601. No.  I've found various issues with dishwashers over the years, and none of the three models
  5602. I saw came close to addressing them.  In fact, I was left with the feeling that I would have
  5603. the same issues with a $1000 dishwasher.  So we'll repair the old one.
  5604.      </p>
  5605.      
  5606. End deselected topic ho (A new dishwasher?) -->
  5607.  
  5608.            
  5609. <!-- topic Go not selected
  5610.      <p>
  5611. While at the <a href="https://www.thegoodguys.com.au/">The Good Guys</a>, discovered
  5612. that I had left my glasses behind at the physiotherapists.  Not a big deal: I had to go back
  5613. and get them.  But that would never have happened before my cataract surgery.
  5614.      </p>
  5615.      
  5616. End deselected topic Go (The downside of cataract surgery) -->
  5617.  
  5618.      
  5619.      
  5620. <item>
  5621. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250626-005143</guid>
  5622. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250626-005143</link>
  5623. <category>technology</category>
  5624. <category>opinion</category>
  5625. <title>Bloody Android!</title>
  5626.  <description>
  5627.    <![CDATA[
  5628.    <div align="justify">
  5629.      <p>
  5630. More fun with <a href="https://en.wikipedia.org/wiki/Android">Android</a> devices
  5631. today.  I've noticed that the <a href="https://en.wikipedia.org/wiki/Google_Maps">Google Maps</a> speed display on my phone briefly drops out from time to time.  Why?
  5632. Problems with the <a href="https://en.wikipedia.org/wiki/GPS">GPS</a> receiver?
  5633. With the phone?  With the app?  Who can tell?
  5634.      </p>
  5635.  
  5636.      <p>
  5637. When I got home, checked where <a href="http://www.lemis.com/yvonne/">Yvonne</a> was.  Somewhere in
  5638. town, but “she” had stopped sharing her location with me.  That wasn't her choice, I'm sure.
  5639. Google Maps had decided it for some reason.
  5640.      </p>
  5641.  
  5642.      <p>
  5643. When she got home, she had a tale of woe to tell, not just with her phone.  She had tried to
  5644. call me, but the call didn't go through: it was just dead.  And she couldn't enable mobile
  5645. data:
  5646.      </p>
  5647.  
  5648.        <a id="Photo-50" name="Photo-50"
  5649.          href="diary-jun2025.php?dirdate=20250625&amp;imagesizes=111111111111111111111111111111111111111111111111112&amp;topics=c&amp;edit=0#Photo-50">
  5650.          <img alt="This should be Android-fail-detail.jpeg.  Is it missing?" border="0" id="Photo_50"
  5651.               title="Photo Android-fail-detail.jpeg.  Click to redisplay larger version of image."
  5652.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250625/small/Android-fail-detail.jpeg"
  5653.               width="490" height="138"
  5654.           /></a>
  5655.  
  5656.      <p>
  5657. That remained, and I spent something like 20 minutes trying to localize the fault.
  5658. Defective <a href="https://en.wikipedia.org/wiki/SIM">SIM</a>?  Defective phone?
  5659. Tried it in <i>enzian.lemis.com</i>, which seems much slower than ever before, but no, no
  5660. problems with mobile data, though making a call was an issue.
  5661.      </p>
  5662.  
  5663.      <p>
  5664. What else can it be?  Put the SIM back in <i>fossil</i> and spent a lot of time trying to
  5665. find my way through the greyed-out configuration entries.  Still can't make a call.  Still
  5666. can't enable mobile data.  Reboot <i>again</i>, maybe?
  5667.      </p>
  5668.  
  5669.      <p>
  5670. And then I saw a fleeting message on boot: “Airplane <i>[sic] mode enabled</i>.  And yes,
  5671. the symbol in the settings page was relatively clear:
  5672.      </p>
  5673.  
  5674.        <a id="Photo-51" name="Photo-51"
  5675.          href="diary-jun2025.php?dirdate=20250625&amp;imagesizes=1111111111111111111111111111111111111111111111111112&amp;topics=c&amp;edit=0#Photo-51">
  5676.          <img alt="This should be Android-fail-detail-2.jpeg.  Is it missing?" border="0" id="Photo_51"
  5677.               title="Photo Android-fail-detail-2.jpeg.  Click to redisplay larger version of image."
  5678.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250625/small/Android-fail-detail-2.jpeg"
  5679.               width="263" height="256"
  5680.           /></a>
  5681.  
  5682.      <p>
  5683. Turn that off and all was well.  Well, it worked, and location sharing came up
  5684. automatically.
  5685.      </p>
  5686.  
  5687.      <p>
  5688. And what did it disable?  Mobile data, clearly, also Wi-Fi (though I was able to turn that
  5689. back on again), apparently phones (and the app was too polite to complain and went through
  5690. the motions anyway), Google Maps location sharing.  What else?
  5691.      </p>
  5692.  
  5693.      <p>
  5694. But how much pain does airplane mode cause?  Wouldn't a simple change of text help?  Instead
  5695. of “Not available”, “Not available in airplane mode”?  And why can't the phone app report
  5696. problems instead of going through the motions?
  5697.      </p>
  5698.      </div>
  5699.    ]]>
  5700.  </description>
  5701.  <dc:creator>Greg Lehey</dc:creator>
  5702.  <dc:date>2025-06-26T00:51:43+00:00</dc:date>
  5703. </item>
  5704.  
  5705.      
  5706.      
  5707. <!-- topic h not selected
  5708.      <p>
  5709. We've finally had some rain, 14 mm of it in the 24 hours to 9:00 today, and more came today.
  5710. And hail, the first I recall seeing since we moved to Stones Road <a href="http://www.lemis.com/grog/diary-may2015.php?subtitle=Moving%20house,%20day%202&amp;article=D-20150509-082924#D-20150509-082924">10 years ago</a>:
  5711.      </p>
  5712.  
  5713.      <div align="left">
  5714.      </div>
  5715.  
  5716.      <p>
  5717. What we really need is much more rain.
  5718.      </p>
  5719.      
  5720. End deselected topic h (Hail!) -->
  5721.  
  5722.                  
  5723. <item>
  5724. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250627-002452</guid>
  5725. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250627-002452</link>
  5726. <category>photography</category>
  5727. <category>technology</category>
  5728. <title>Revisiting old photos</title>
  5729.  <description>
  5730.    <![CDATA[
  5731.    <div align="justify">
  5732.      <p>
  5733. <a href="http://www.lemis.com/grog/diary-jun2010.php?subtitle=Who%20are%20automatic%20settings%20good%20for?&amp;article=D26-2#D26-2">Fifteen years ago</a> we took some photos of <a href="http://www.lemis.com/grog/Albums/Nemo.php">Nemo</a> during puppy training.  The results weren't good.  We were using
  5734. my <a href="http://en.wikipedia.org/wiki/Olympus_E-30">E-30</a>, and for <a href="http://www.lemis.com/yvonne/">Yvonne</a> I set it to the <b>AUTO</b> exposure method, and for some reason
  5735. (probably inappropriate metering including the sky), all the images came out underexposed.
  5736.      </p>
  5737.  
  5738.      <p>
  5739. <a href="http://www.lemis.com/grog/diary-mar2017.php#D-20170306-230316">A few years later</a> I did
  5740. some comparisons between the various processing methods that I was using at that time.  But
  5741. that, too, was 8 years ago.  What do things look like now?  In particular, how much do my
  5742. modified <a href="https://www.dxo.com/dxo-photolab/">DxO PhotoLab</a> settings and
  5743. <a href="https://eyeq.photos/perfectlyclear">“Perfectly Clear“</a> improve things?
  5744. Today I tried a five-way comparison: original, processed with <a href="http://ufraw.sourceforge.net/">UFRaw</a> (a package that hasn't been updated in 10
  5745. years), my DxO processing of 7 years ago, the same image optimized with Perfectly Clear, and
  5746. finally my current processing:
  5747.      </p>
  5748.  
  5749.      <div align="left">
  5750.  <a id="Photo-52" name="Photo-52"
  5751.          href="diary-jun2025.php?dirdate=20100626&amp;imagesizes=11111111111111111111111111111111111111111111111111112&amp;topics=c&amp;edit=0#Photo-52">
  5752.          <img alt="This should be dog-training-66-orig.jpeg.  Is it missing?" border="0" id="Photo_52"
  5753.               title="Photo dog-training-66-orig.jpeg.  Click to redisplay larger version of image."
  5754.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20100626/small/dog-training-66-orig.jpeg"
  5755.               width="300" height="225"
  5756.           /></a>
  5757.          <a id="Photo-53" name="Photo-53"
  5758.          href="diary-jun2025.php?dirdate=20100626&amp;imagesizes=111111111111111111111111111111111111111111111111111112&amp;topics=c&amp;edit=0#Photo-53">
  5759.          <img alt="This should be dog-training-66-ufraw.jpeg.  Is it missing?" border="0" id="Photo_53"
  5760.               title="Photo dog-training-66-ufraw.jpeg.  Click to redisplay larger version of image."
  5761.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20100626/small/dog-training-66-ufraw.jpeg"
  5762.               width="300" height="226"
  5763.           /></a>
  5764.  <a id="Photo-54" name="Photo-54"
  5765.          href="diary-jun2025.php?dirdate=20100626&amp;imagesizes=1111111111111111111111111111111111111111111111111111112&amp;topics=c&amp;edit=0#Photo-54">
  5766.          <img alt="This should be dog-training-66-DxO-orig.jpeg.  Is it missing?" border="0" id="Photo_54"
  5767.               title="Photo dog-training-66-DxO-orig.jpeg.  Click to redisplay larger version of image."
  5768.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20100626/small/dog-training-66-DxO-orig.jpeg"
  5769.               width="300" height="225"
  5770.           /></a>
  5771.  <a id="Photo-55" name="Photo-55"
  5772.          href="diary-jun2025.php?dirdate=20100626&amp;imagesizes=11111111111111111111111111111111111111111111111111111112&amp;topics=c&amp;edit=0#Photo-55">
  5773.          <img alt="This should be dog-training-66-DxO.jpeg.  Is it missing?" border="0" id="Photo_55"
  5774.               title="Photo dog-training-66-DxO.jpeg.  Click to redisplay larger version of image."
  5775.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20100626/small/dog-training-66-DxO.jpeg"
  5776.               width="300" height="225"
  5777.           /></a>
  5778.  <a id="Photo-56" name="Photo-56"
  5779.          href="diary-jun2025.php?dirdate=20100626&amp;imagesizes=111111111111111111111111111111111111111111111111111111112&amp;topics=c&amp;edit=0#Photo-56">
  5780.          <img alt="This should be dog-training-66.jpeg.  Is it missing?" border="0" id="Photo_56"
  5781.               title="Photo dog-training-66.jpeg.  Click to redisplay larger version of image."
  5782.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20100626/small/dog-training-66.jpeg"
  5783.               width="300" height="225"
  5784.           /></a>
  5785.      </div>
  5786.  
  5787.      <p>
  5788. The strange thing is the colour of my current processing.  On the whole the results of 7
  5789. years ago look better.  But once again I'm puzzled by the underexposure of the <b>AUTO</b>
  5790. setting (which the <a href="https://en.wikipedia.org/wiki/Exif">Exif</a> data report
  5791. as “ESP Creative (Slow Speed)”).  It's <a href="https://en.wikipedia.org/wiki/Exposure_value">EV</a> 14.3, fully 2 stops less than
  5792. the <b>P</b> (“Center-weighted average Program AE”) setting that I was using.  It may be no
  5793. coincidence that later models dropped the <b>AUTO</b> setting altogether.
  5794.      </p>
  5795.      </div>
  5796.    ]]>
  5797.  </description>
  5798.  <dc:creator>Greg Lehey</dc:creator>
  5799.  <dc:date>2025-06-27T00:24:52+00:00</dc:date>
  5800. </item>
  5801.  
  5802.            
  5803. <!-- topic ho not selected
  5804.      <p>
  5805. After <a href="http://www.lemis.com/grog/diary-jun2025.php?subtitle=A%20new%20dishwasher?&amp;article=D-20250626-001813#D-20250626-001813">yesterday's</a> investigations, it was clear that we will keep our current dishwasher and
  5806. have it repaired.  Called up Brett Younger of Vic Country Appliance Repair (phone +61 419
  5807. 980 987), whom somebody had recommended to <a href="http://www.lemis.com/yvonne/">Yvonne</a>, and
  5808. discussed the matter.  Sent him the details of the dishwasher, and he called back to say
  5809. that the pump would cost over $400, more than we paid for the dishwasher—<i>if</i> we could
  5810. find one.  And of course there's labour on top of that.
  5811.      </p>
  5812.  
  5813.      <p>
  5814. OK, that's a whole different situation.  We'll need a new dishwasher, then, just not one of
  5815. the el-cheapo ones that I was looking at yesterday (and which Brett, not knowing what I had
  5816. been looking at, mentioned by name as ones to avoid).  He recommends <a href="https://www.lg.com/au/dishwashers/">LG</a> or <a href="https://www.bosch-home.com.au/en/mkt-category/dishwashing">Bosch</a>, and yes, he can
  5817. deliver and install one next Friday.
  5818.      </p>
  5819.  
  5820.      <p>
  5821. Damn!  Not so much for the cost as for the research needed to decide which to buy.  The
  5822. Bosch models I looked at look pretty much like the one we have.  And it's <i>noisy</i>.
  5823. Have things improved?  Brett guesses “yes”, but it's just a guess.  The LG specs mention
  5824. noise (44 <a href="https://en.wikipedia.org/wiki/dB(A)">dB(A)</a>), but Bosch
  5825. doesn't.  For good reason?  However, <a href="https://gemini.google.com/">Google
  5826. Gemini</a> tells me that the noise from Bosch dishwashers (no model stated) ranges from 42
  5827. to 46 dB(A), so there seems not to be much difference from LG.
  5828.      </p>
  5829.      
  5830. End deselected topic ho (Dishwasher: no?  yes?) -->
  5831.  
  5832.                  
  5833. <!-- topic ho not selected
  5834.      <p>
  5835. So which dishwasher do I buy?  <a href="http://www.lemis.com/yvonne/">Yvonne</a> had suggested
  5836. <a href="https://en.wikipedia.org/wiki/Miele">Míele</a>, and admittedly our
  5837. longest-lasting dishwasher was a Míele, which we bought shop-soiled in 1991 and which lasted
  5838. until <a href="http://www.lemis.com/grog/diary-may2011.php?subtitle=Dead%20dishwasher&amp;article=D-20110523-005411#D-20110523-005411">2011</a>, also with pump problems.  But that was a commercial model, and all subsequent
  5839. machines have been normal domestic ones.  And Míele is far more expensive than the others.
  5840.      </p>
  5841.  
  5842.      <p>
  5843. So: what's the difference between the Bosch and LG dishwashers?  The only thing that stands
  5844. out is the noise that our current Bosch machine makes.  <a href="https://gemini.google.com/">Google Gemini</a> to the rescue, with a lot of detail, but
  5845. a summary:
  5846.      </p>
  5847.  
  5848.      <blockquote class="fullwidth">
  5849. <p class="listitemwidth">
  5850.          Choose Bosch Series 4 if: You prioritize extremely quiet operation, classic German
  5851.          engineering and reliability, efficient condensation drying, and a solid range of core
  5852.          washing programs with some smart features.
  5853. </p>
  5854.  
  5855. <p class="listitemwidth">
  5856.  Choose LG if: You value advanced cleaning technologies like QuadWash and TrueSteam,
  5857.  superior drying performance (especially for plastics), extensive smart features and app
  5858.  connectivity, and a modern design aesthetic.
  5859. </p>
  5860.      </blockquote>
  5861.  
  5862.      <p>
  5863. “Choose Bosch if you believe that German is better”.  These machines are made in Turkey.
  5864. “Choose LG if you value buzzwords”.  But superior drying performance sounds good.  But
  5865. superior drying can't be wrong, and they're also over $100 cheaper, so it'll probably be an
  5866. LG.  But what a lot of time it takes to research this stuff!
  5867.      </p>
  5868.      
  5869. End deselected topic ho (A day spent buying a dishwasher) -->
  5870.  
  5871.            
  5872. <item>
  5873. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250628-032655</guid>
  5874. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250628-032655</link>
  5875. <category>technology</category>
  5876. <category>opinion</category>
  5877. <title>Saving Google Gemini output</title>
  5878.  <description>
  5879.    <![CDATA[
  5880.    <div align="justify">
  5881.      <p>
  5882. How do I save my <a href="https://gemini.google.com/">Google Gemini</a> answers?  So
  5883. far I have been copying and pasting, but there must be a better way.  OK, Gemini, How do I
  5884. save Google Gemini answers?
  5885.      </p>
  5886.  
  5887.      <p>
  5888. Oh, you just want to save it?  No, this is a modern program.  You can export to <a href="https://en.wikipedia.org/wiki/Google_Docs">Google Docs</a>, send them as a draft in
  5889. <a href="https://en.wikipedia.org/wiki/Gmail">Gmail</a>, export to <a href="https://en.wikipedia.org/wiki/Google_Sheets">Google Sheets</a>, or “For code snippets,
  5890. you might have options to "Export to Colab" (Google Colaboratory) or "Export to Replit."”.
  5891.      </p>
  5892.  
  5893.      <p>
  5894. Why does this have to be so complicated?
  5895.      </p>
  5896.      </div>
  5897.    ]]>
  5898.  </description>
  5899.  <dc:creator>Greg Lehey</dc:creator>
  5900.  <dc:date>2025-06-28T03:26:55+00:00</dc:date>
  5901. </item>
  5902.  
  5903.                  
  5904. <item>
  5905. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250629-014025</guid>
  5906. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250629-014025</link>
  5907. <category>general</category>
  5908. <category>technology</category>
  5909. <category>opinion</category>
  5910. <title>Good Guys?  Bad Guys!</title>
  5911.  <description>
  5912.    <![CDATA[
  5913.    <div align="justify">
  5914.      <p>
  5915. So I've finally decided on a new dishwasher: the LG XD5B14PS.  The <a href="https://thegoodguys.com.au/">Good Guys</a> offer it for $799, but if you look
  5916. carefully and click in the right place, it's only $733.  OK, fill out the web form and pay
  5917. for it.  But they have me on record, only not online.  OK, sign up.
  5918.      </p>
  5919.  
  5920.      <p>
  5921. Their web programmers don't seem to be the best:
  5922.      </p>
  5923.  
  5924.        <a id="Photo-57" name="Photo-57"
  5925.          href="diary-jun2025.php?dirdate=20250628&amp;imagesizes=1111111111111111111111111111111111111111111111111111111112&amp;topics=c&amp;edit=0#Photo-57">
  5926.          <img alt="This should be Bad-Guys-2-detail-2.jpeg.  Is it missing?" border="0" id="Photo_57"
  5927.               title="Photo Bad-Guys-2-detail-2.jpeg.  Click to redisplay larger version of image."
  5928.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250628/small/Bad-Guys-2-detail-2.jpeg"
  5929.               width="400" height="418.89763779528"
  5930.           /></a>
  5931.  
  5932.      <p>
  5933. But the next thing I ran into was a <a href="https://en.wikipedia.org/wiki/CAPTCHA">CAPTCHA</a> requiring understanding of US American terms:
  5934.      </p>
  5935.  
  5936.        <a id="Photo-58" name="Photo-58"
  5937.          href="diary-jun2025.php?dirdate=20250628&amp;imagesizes=11111111111111111111111111111111111111111111111111111111112&amp;topics=c&amp;edit=0#Photo-58">
  5938.          <img alt="This should be Bad-Guys-2-detail.jpeg.  Is it missing?" border="0" id="Photo_58"
  5939.               title="Photo Bad-Guys-2-detail.jpeg.  Click to redisplay larger version of image."
  5940.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250628/small/Bad-Guys-2-detail.jpeg"
  5941.               width="234" height="288"
  5942.           /></a>
  5943.  
  5944.      <p>
  5945. Damn you, “Good” Guys!  Do you want to sell merchandise or annoy potential customers?  A
  5946. good thing that I don't need to submit to this insult to purchase the item.  Back to the
  5947. other tab, finished the order, and received an immediate confirmation from <a href="https://en.wikipedia.org/wiki/PayPal">PayPal</a>.
  5948.      </p>
  5949.  
  5950.      <p>
  5951. And nothing from the “Good” Guys.  More searching on their web site produced this FAQ:
  5952.      </p>
  5953.  
  5954.        <a id="Photo-59" name="Photo-59"
  5955.          href="diary-jun2025.php?dirdate=20250628&amp;imagesizes=111111111111111111111111111111111111111111111111111111111112&amp;topics=c&amp;edit=0#Photo-59">
  5956.          <img alt="This should be Bad-Guys-3-detail.jpeg.  Is it missing?" border="0" id="Photo_59"
  5957.               title="Photo Bad-Guys-3-detail.jpeg.  Click to redisplay larger version of image."
  5958.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250628/small/Bad-Guys-3-detail.jpeg"
  5959.               width="500" height="194.71153846154"
  5960.           /></a>
  5961.  
  5962.      <blockquote class="fullwidth">
  5963.        <div class="listitemwidth">
  5964.          You <i>should</i> receive an Online Order Confirmation email within 24hrs <i>[sic]</i> of
  5965.  placing your order.
  5966.        </div>
  5967.      </blockquote>
  5968.  
  5969.      <p>
  5970. Now doesn't that fill you with confidence, especially since they had claimed I could pick it
  5971. up within an hour?  Something's seriously wrong with their web site.  And I didn't hear from
  5972. you by the end of the day.
  5973.      </p>
  5974.  
  5975.      <p>
  5976. I've been working on this for three days!  Why is it all such a pain?
  5977.      </p>
  5978.      </div>
  5979.    ]]>
  5980.  </description>
  5981.  <dc:creator>Greg Lehey</dc:creator>
  5982.  <dc:date>2025-06-29T01:40:25+00:00</dc:date>
  5983. </item>
  5984.  
  5985.                        
  5986. <item>
  5987. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-jun2025.php#D-20250630-042830</guid>
  5988. <link>http://www.lemis.com/grog/diary-jun2025.php?topics=c#D-20250630-042830</link>
  5989. <category>general</category>
  5990. <category>technology</category>
  5991. <category>opinion</category>
  5992. <title>Where's my dishwasher?</title>
  5993.  <description>
  5994.    <![CDATA[
  5995.    <div align="justify">
  5996.      <p>
  5997. So I have waited the astoundingly long time (24 hours) for <a href="https://www.thegoodguys.com.au/">The Good Guys</a> to confirm the purchase of my
  5998. dishwasher.  No confirmation.  Problems sending email to me?  No, nothing in the server
  5999. logs.
  6000.      </p>
  6001.  
  6002.      <p>
  6003. OK, contact customer support, a “chat” with Sabrina.  PayPal transaction number, please?
  6004. Gave that, then:
  6005.      </p>
  6006.  
  6007.      <blockquote class="fullwidth">
  6008.        <div class="listitemwidth">
  6009.          <b>Sabrina:</b> We have located your payment from Paypal. We will need to send this to our
  6010.          IT team to have manually push through to our system, this can take a few hours. You will
  6011.          receive an email confirmation once this have been done.
  6012.        </div>
  6013.  
  6014. <div class="listitemwidth">
  6015.  <b>Me:</b> Thank you. Can I expect this today?  And what went wrong?
  6016. </div>
  6017. <div class="listitemwidth">
  6018.  <b>Sabrina:</b> There might be a technical glitch, sometimes it happens with Paypal
  6019.  payments.
  6020. </div>
  6021. <div class="listitemwidth">
  6022.  <b>Me:</b> But it must be on your side, right?
  6023. </div>
  6024. <div class="listitemwidth">
  6025.  <b>Sabrina:</b> Yes, we should be able to push it into the system today.
  6026. </div>
  6027.      </blockquote>
  6028.  
  6029.      <p>
  6030. And try as I might, I couldn't get her to address the underlying problem.  I got the
  6031. impression that they just don't care.  And of course I didn't get any email today.
  6032.      </p>
  6033.      </div>
  6034.    ]]>
  6035.  </description>
  6036.  <dc:creator>Greg Lehey</dc:creator>
  6037.  <dc:date>2025-06-30T04:28:30+00:00</dc:date>
  6038. </item>
  6039.  
  6040.            
  6041. <!-- topic k not selected
  6042.      <p>
  6043. A new recipe for dinner today: <a href="http://www.lemis.com/grog/recipes/Falscher-Hase.php">„Falscher Hase“</a> (“false hare”), a kind of <a href="https://en.wikipedia.org/wiki/Meat_loaf">meat
  6044. loaf</a>:
  6045.      </p>
  6046.  
  6047.      <div align="left">
  6048.      </div>
  6049.  
  6050.      <p>
  6051. I've never eaten it before, but it tasted surprisingly good.  We should experiment with
  6052. other similar dishes.
  6053.      </p>
  6054.      
  6055. End deselected topic k (False hare) -->
  6056.  
  6057.      </channel>
  6058. </rss>
  6059.  

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