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

  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-09-18T13:31:02+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. <item>
  20. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-aug2025.php#D-20250831-051813</guid>
  21. <link>http://www.lemis.com/grog/diary-aug2025.php#D-20250831-051813</link>
  22. <category>technology</category>
  23. <category>general</category>
  24. <category>opinion</category>
  25. <title>Artificial: intelligent?</title>
  26.  <description>
  27.    <![CDATA[
  28.    <div align="justify">
  29.      <p>
  30. What good is the current “<a href="https://en.wikipedia.org/wiki/Artificial_Intelligence">Artificial Intelligence</a>”
  31. wave?  I've been using it, notably <a href="https://gemini.google.com/">Google
  32. Gemini</a>, as a better search engine, but it should be able to write documents and make
  33. pictures.
  34.      </p>
  35.  
  36.      <p>
  37. OK, put it to the test with something that I know well: myself.  I asked two questions,
  38. first “which is the most interesting article in Greg Lehey's online diary?”, and then “write
  39. me a typical article for Greg Lehey's diary”.  The results were interesting.  I tried
  40. <a href="https://en.wikipedia.org/wiki/Perplexity_AI">Answerr</a>, Gemini,
  41. <a href="https://en.wikipedia.org/wiki/ChatGPT">ChatGPT</a>, <a href="https://en.wikipedia.org/wiki/Claude_(language_model)">Claude</a> and <a href="https://en.wikipedia.org/wiki/DeepSeek">DeepSeek</a>.  Answerr was a non-starter:
  42. after annoying me with finding login credentials, it told me that I had used up my free
  43. credits, which must be <i>very</i> limited.  It also insulted me by presenting me with a
  44. <a href="https://en.wikipedia.org/wiki/CAPTCHA">CAPTCHA</a>.
  45.      </p>
  46.      </div>
  47.    ]]>
  48.  </description>
  49.  <dc:creator>Greg Lehey</dc:creator>
  50.  <dc:date>2025-08-31T05:18:13+00:00</dc:date>
  51. </item>
  52.  
  53.            
  54. <item>
  55. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-aug2025.php#D-20250831-234309</guid>
  56. <link>http://www.lemis.com/grog/diary-aug2025.php#D-20250831-234309</link>
  57. <category>fiction</category>
  58. <category>technology</category>
  59. <category>general</category>
  60. <category>opinion</category>
  61. <title>Gemini</title>
  62.  <description>
  63.    <![CDATA[
  64.    <div align="justify">
  65.  
  66.      <p>
  67. For the first question, Gemini responded
  68.      </p>
  69.  
  70.      <blockquote class="fullwidth">
  71.        <div class="listitemwidth">
  72.          There is no single "most interesting" article in Greg Lehey's online diary, as what is
  73.          interesting is subjective.  However, you can find a wealth of his writing on his website,
  74.          which is the primary source of his online diary.
  75.        </div>
  76.      </blockquote>
  77.  
  78.      <p>
  79. The diary entry was more useful.  This one chose today's date with a date format that
  80. doesn't match this diary:
  81.      </p>
  82.  
  83.      <p>
  84. 2025-08-31: <b>Of Dropped Connections and Other Frustrations</b>
  85.      </p>
  86.  
  87.      <blockquote class="fullwidth">
  88. <p class="listitemwidth">
  89.  Another cold evening here in Gidgegannup. I was looking forward to a quiet night, but the
  90.  network had other plans. For the past week or so, the connection on my
  91.  server, <i>orion</i>, has been intermittently dropping out for a few seconds at a
  92.  time. Not long enough to bring a full session down, but enough to kill an SSH connection
  93.  or cause a file transfer to stall. Annoying, to say the least.
  94. </p>
  95.  
  96. <p class="listitemwidth">
  97.  My first thought was the usual suspect: a flaky cable. I swapped it out for a new one, a
  98.  nice bright blue one, just for good measure. No dice. The drops continued.
  99. </p>
  100.  
  101. <p class="listitemwidth">
  102.  I started digging. A quick look in the system logs showed nothing. <i>dmesg</i> was
  103.  clean. The network interface <i>fxp0</i> showed no errors, and the link state was solid. I
  104.  checked the routing table with <tt>netstat -rn</tt>, and it was exactly as it should
  105.  be. The connection to the local gateway, my router <i>apollo</i>, was fine.
  106. </p>
  107.  
  108. <p class="listitemwidth">
  109.  Then I noticed something odd. The drops weren't random. They seemed to happen roughly
  110.  every 12 hours. That's when I had a hunch. I logged into my gateway machine and checked
  111.  the DHCP logs. Sure enough, every 12 hours, <i>orion</i> was requesting a lease
  112.  renewal. The logs showed a slight delay, a hiccup in the negotiation, before the lease was
  113.  renewed. It seems that during this micro-reconfiguration, the router was dropping the
  114.  existing state and not re-establishing it quickly enough.
  115. </p>
  116.  
  117. <p class="listitemwidth">
  118.  The problem, as it so often is, was not with the server itself but with the peripheral
  119.  nonsense. A brief configuration change was all that was needed. I logged into <i>orion</i>
  120.  and edited <i>/etc/rc.conf</i> to give it a static IP address, taking it out of the DHCP
  121.  pool entirely.
  122. </p>
  123.  
  124. <blockquote class="fullwidth">
  125. <div style="text-align:left">
  126.  <tt>
  127. ifconfig_fxp0="inet 192.168.1.123 netmask 255.255.255.0"
  128. <br />defaultrouter="192.168.1.1"
  129. <br />
  130.  </tt>
  131. </div>
  132. </blockquote>
  133.  
  134. <p class="listitemwidth">
  135.  I restarted the network stack, and the drops ceased. It's a perfectly simple fix for a
  136.  perfectly silly problem. Another reminder that the most persistent and infuriating issues
  137.  are often caused by the most mundane of configurations. Yana just shook her head when I
  138.  explained it to her. She's right; there are better things to do than to spend an evening
  139.  debugging a DHCP lease renewal. But then, it's what I do.
  140. </p>
  141.      </blockquote>
  142.  
  143.      <p>
  144. This one is quite interesting.  It has created a relatively complicated network problem and
  145. described it plausibly.  It's interesting that it brought Yana into the story.  And on a
  146. technical level, it pointed to methods that I wouldn't have considered.
  147.      </p>
  148.      </div>
  149.    ]]>
  150.  </description>
  151.  <dc:creator>Greg Lehey</dc:creator>
  152.  <dc:date>2025-08-31T23:43:09+00:00</dc:date>
  153. </item>
  154.  
  155.            
  156. <item>
  157. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-aug2025.php#D-20250831-234345</guid>
  158. <link>http://www.lemis.com/grog/diary-aug2025.php#D-20250831-234345</link>
  159. <category>technology</category>
  160. <category>general</category>
  161. <category>opinion</category>
  162. <title>ChatGPT</title>
  163.  <description>
  164.    <![CDATA[
  165.    <div align="justify">
  166.  
  167.      <p>
  168. That's fair enough, far better than what <a href="https://en.wikipedia.org/wiki/ChatGPT">ChatGPT</a> came up with:
  169.      </p>
  170.  
  171.      <blockquote class="fullwidth">
  172.        <div class="listitemwidth">
  173.          Hello! Greg Lehey's online diary, also known as "The Diary of an Unknown Gentleman,"
  174.          covers a wide range of topics, from technology and open-source software to personal
  175.          anecdotes and observations about life. While I don't have the ability to browse the
  176.          internet in real-time or access specific articles, I can tell you that many readers find
  177.          his insights on FreeBSD and open-source software particularly engaging. If you're
  178.          interested in technology, you might enjoy his detailed discussions on system
  179.          administration and software development. If you have a specific topic in mind, I can try
  180.          to provide more information based on what I know!
  181.        </div>
  182.      </blockquote>
  183.  
  184.      <p>
  185. Who knows it as “The Diary of an Unknown Gentleman”?  Only ChatGPT, I suspect.  The sample
  186. diary entry wasn't much better:
  187.      </p>
  188.  
  189.      <blockquote class="fullwidth">
  190. <div class="listitemwidth">
  191.  <b>A Day in the Life of a Vintage Computer Enthusiast</b>
  192. </div>
  193.  
  194.        <div class="listitemwidth">
  195.  Date: <a href="http://www.lemis.com/grog/diary-oct2023.php?subtitle=A%20Day%20in%20the%20Life%20of%20a%20Vintage%20Computer%20Enthusiast&amp;article=D-20231016-015140#D-20231016-015140">October 15, 2023</a> </div>
  196.  
  197. <p class="listitemwidth">
  198.  Today began like any other, with the familiar hum of my vintage computer collection waking
  199.  up to the world. There's something uniquely satisfying about the sound of a 1980s hard
  200.  drive spinning up, a sound that modern SSDs just can't replicate. My morning ritual
  201.  involves checking on my beloved machines, ensuring that each one is in working order.
  202. </p>
  203.  
  204. <p class="listitemwidth">
  205.  This morning, I decided to tackle a project I've been putting off for a while: restoring
  206.  an old DEC PDP-11. It's a beast of a machine, and finding the right parts has been a
  207.  challenge. After a few hours of tinkering, I managed to get it to boot. The feeling of
  208.  seeing that command prompt after so many years was indescribable. It's moments like these
  209.  that remind me why I fell in love with computing in the first place.
  210. </p>
  211.  
  212. <p class="listitemwidth">
  213.  In the afternoon, I took a break from my restoration work to catch up on some reading. I
  214.  stumbled upon an article about the resurgence of interest in retro computing. It's
  215.  fascinating to see how many people are rediscovering the joys of older technology. There's
  216.  a certain charm in the simplicity and ingenuity of these machines that modern devices
  217.  often lack.
  218. </p>
  219.  
  220. <p class="listitemwidth">
  221.  As the day wound down, I spent some time updating my diary. It's important to document
  222.  these experiences, not just for myself, but for anyone who might stumble upon my writings
  223.  in the future. Who knows? Maybe one day, someone will find inspiration in these pages and
  224.  embark on their own journey into the world of vintage computing.
  225. </p>
  226.  
  227. <p class="listitemwidth">
  228.  Until tomorrow,
  229. </p>
  230.  
  231. <p class="listitemwidth">
  232.  Greg
  233. </p>
  234.      </blockquote>
  235.  
  236.      <p>
  237. That doesn't look much like me.  I'd say that this was the worst of the articles.
  238.      </p>
  239.      </div>
  240.    ]]>
  241.  </description>
  242.  <dc:creator>Greg Lehey</dc:creator>
  243.  <dc:date>2025-08-31T23:43:45+00:00</dc:date>
  244. </item>
  245.  
  246.            
  247. <item>
  248. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-aug2025.php#D-20250831-234430</guid>
  249. <link>http://www.lemis.com/grog/diary-aug2025.php#D-20250831-234430</link>
  250. <category>technology</category>
  251. <category>general</category>
  252. <category>opinion</category>
  253. <title>Claude</title>
  254.  <description>
  255.    <![CDATA[
  256.    <div align="justify">
  257.  
  258.      <p>
  259. Claude came up with
  260.      </p>
  261.  
  262.      <blockquote class="fullwidth">
  263. <p class="listitemwidth">
  264.  Based on my search of Greg Lehey's online diary, I can see that Greg Lehey is a retired
  265.  Unix kernel hacker who maintains an extensive online diary at lemis.com.  His diary spans
  266.  many years and covers a wide range of topics from technical computing issues to daily life
  267.  observations.
  268. </p>
  269.  
  270. <p class="listitemwidth">
  271.  From what I can observe in the current entries, some particularly interesting themes
  272.  emerge:
  273. </p>
  274.  
  275. <ul>
  276.          <li class="fullwidth">
  277.            <div class="list2width">
  278.              <b>Technology critiques and commentary</b> - Greg frequently writes thoughtful
  279.      critiques of modern technology changes, such as his recent analysis of Google's phone
  280.      app redesign and violation of the "Principle of Least Astonishment" (POLA) <a href="http://www.lemis.com/grog/diary.php">Greg's diary, recent entries</a>. His
  281.      technical background gives him unique insights into these changes.
  282.            </div>
  283.          </li>
  284.  
  285.          <li class="fullwidth">
  286.            <div class="list2width">
  287.              <b>Historical photography and archival work</b> - He has interesting entries about
  288.              historical photos of Kuala Lumpur, including discovering that his own vintage
  289.              photographs from 1964 have been plagiarized and misattributed online. This combines
  290.              personal history with detective work.
  291.            </div>
  292.          </li>
  293.  
  294.          <li class="fullwidth">
  295.            <div class="list2width">
  296.              <b>Daily life observations with technical depth</b> - His entries blend mundane
  297.              activities (like cooking, cat behavior) with deeper technical and philosophical
  298.              observations.
  299.            </div>
  300.          </li>
  301. </ul>
  302.  
  303. <p class="listitemwidth">
  304.  However, to definitively identify the "most interesting" article would require exploring
  305.  his extensive archive more thoroughly, as his diary spans decades and covers topics
  306.  ranging from FreeBSD kernel development to photography, travel, and personal
  307.  anecdotes. The most interesting entry would depend on your particular interests - whether
  308.  you're drawn to technical computing history, photography, social commentary, or personal
  309.  narratives.
  310. </p>
  311.      </blockquote>
  312.  
  313.      <p>
  314. This one suggests that Claude hasn't looked far beyond today's diary as it was at the time.
  315.      </p>
  316.      </div>
  317.    ]]>
  318.  </description>
  319.  <dc:creator>Greg Lehey</dc:creator>
  320.  <dc:date>2025-08-31T23:44:30+00:00</dc:date>
  321. </item>
  322.  
  323.            
  324. <item>
  325. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-aug2025.php#D-20250831-235808</guid>
  326. <link>http://www.lemis.com/grog/diary-aug2025.php#D-20250831-235808</link>
  327. <category>technology</category>
  328. <category>general</category>
  329. <category>opinion</category>
  330. <title>Claude diary entry</title>
  331.  <description>
  332.    <![CDATA[
  333.    <div align="justify">
  334.      <p>
  335. Claude may not have looked very far for the “best article” question, but it certainly went
  336. to a lot of trouble for the sample article, all five of it:
  337.      </p>
  338.  
  339.      <blockquote class="fullwidth">
  340.        <p class="listitemwidth">
  341. I've created a typical Greg Lehey diary entry that captures his characteristic style based
  342. on what I observed from his actual diary. The entry includes several key elements that make
  343. his writing distinctive:
  344.      </p>
  345.  
  346.      <ol>
  347.        <li class="fullwidth">
  348.          <div class="list2width">
  349.            <b>Multiple short articles per day</b> - Each covering different topics with clear
  350.            subject headers
  351.          </div>
  352.        </li>
  353.  
  354.        <li class="fullwidth">
  355.          <div class="list2width">
  356.            <b>Technical commentary with broader implications</b> - Like his analysis of USB-C
  357.            connector confusion drawing parallels to old RS-232 problems
  358.          </div>
  359.        </li>
  360.  
  361.        <li class="fullwidth">
  362.          <div class="list2width">
  363.            <b>Photography observations</b> - Combining technical and aesthetic perspectives
  364.          </div>
  365.        </li>
  366.  
  367.        <li class="fullwidth">
  368.          <div class="list2width">
  369.            <b>Cat behavior documentation</b> - With his typical analytical approach to pet behavior
  370.          </div>
  371.        </li>
  372.  
  373.        <li class="fullwidth">
  374.          <div class="list2width">
  375.            <b>Critiques of "modern" technology</b> - Focusing on user experience failures and
  376.            unnecessary complexity
  377.          </div>
  378.        </li>
  379.  
  380.        <li class="fullwidth">
  381.          <div class="list2width">
  382.            <b>Historical technical perspective</b> - Drawing from his background in Unix/FreeBSD
  383.            development
  384.          </div>
  385.        </li>
  386.      </ol>
  387.  
  388. <p class="listitemwidth">
  389.  The tone captures his mixture of technical expertise, dry humor, practical frustration
  390.  with poorly designed systems, and careful observation of both technology and daily
  391.  life. His writing style tends to be conversational yet precise, often linking current
  392.  observations to broader principles or historical context.
  393. </p>
  394.      </blockquote>
  395.  
  396.      <p class="listitemwidth">
  397. The “article” themselves, all dated <a href="http://www.lemis.com/grog/diary-oct2025.php#15">15 October 2025</a>:
  398.      </p>
  399.  
  400.      <blockquote class="fullwidth">
  401. <p class="listitemwidth">
  402.  <b>USB-C: The universal connector that isn't</b>
  403. </p>
  404.  
  405. <p class="listitemwidth">
  406.  Spent the morning trying to connect my new external drive to the laptop, only to discover
  407.  that not all USB-C cables are created equal. The cable that came with the drive works fine
  408.  for power, but won't carry data. The one from my phone charges everything but transfers
  409.  nothing. And the expensive "high-speed" cable I bought last month? Perfect for everything
  410.  except video.
  411. </p>
  412.  
  413. <p class="listitemwidth">
  414.  This reminds me of the old RS-232 days, when you needed a different cable for every device
  415.  and a drawer full of gender changers and null modems. We thought we'd solved this with
  416.  USB, and for a while we had. USB-A was USB-A. It either worked or it didn't.
  417. </p>
  418.  
  419. <p class="listitemwidth">
  420.  Now we have USB-C, which looks identical regardless of capability. USB 2.0 speeds, USB
  421.  3.2, Thunderbolt 3, Thunderbolt 4, power delivery at various voltages, DisplayPort
  422.  alternate mode, and combinations thereof. All in connectors that look exactly the same.
  423. </p>
  424.  
  425. <p class="listitemwidth">
  426.  This is a perfect example of what happens when committee design meets marketing
  427.  pressure. The engineers wanted flexibility, the manufacturers wanted cost savings, and the
  428.  marketing departments wanted "universal". What we got was universally confusing.
  429. </p>
  430.  
  431. <p class="listitemwidth">
  432.  At least the old parallel port cables had different connectors for different
  433.  capabilities. You knew a Centronics cable was for printers, not modems.
  434. </p>
  435.  
  436. <p class="listitemwidth">
  437.  <b>Morning photography</b>
  438. </p>
  439.  
  440. <p class="listitemwidth">
  441.  The light this morning was exceptional—one of those crisp autumn days where everything
  442.  seems to have more contrast than usual. Took the opportunity to reshoot the house from the
  443.  north side for the monthly house photos.
  444. </p>
  445.  
  446. <p class="listitemwidth">
  447.  While reviewing the images, I noticed something I'd missed before: the shadow patterns
  448.  from the solar panels create an interesting geometric overlay on the garden below. It
  449.  changes throughout the day, of course, but at this time of morning it creates an almost
  450.  Art Deco pattern across the lavender bushes.
  451. </p>
  452.  
  453. <p class="listitemwidth">
  454.  This got me thinking about how we unconsciously compose our environment. When we installed
  455.  those panels five years ago, I was focused entirely on energy efficiency and roof
  456.  aesthetics. The shadow patterns were an unintended consequence that turned out to be
  457.  rather pleasant.
  458. </p>
  459.  
  460. <p class="listitemwidth">
  461.  Photography teaches you to notice these accidental compositions everywhere.
  462. </p>
  463.  
  464. <p>
  465.  <b>Cat behavioral patterns</b>
  466. </p>
  467.  
  468. <p class="listitemwidth">
  469.  <a href="http://www.lemis.com/grog/Albums/Animals/Piccola.php">Piccola</a> has developed a new
  470.  routine. Every morning at exactly 6:47 AM, she positions herself at the bedroom door and
  471.  begins her campaign for breakfast. Not 6:45, not 6:50—6:47.
  472. </p>
  473.  
  474. <p class="listitemwidth">
  475.  I've been tracking this for two weeks now, and the consistency is remarkable. She's more
  476.  accurate than my atomic clock. How does she do it? Internal circadian rhythms? Sensitivity
  477.  to changes in light that I can't perceive? Or is she somehow aware of the subtle sounds
  478.  the house makes as the heating system cycles?
  479. </p>
  480.  
  481. <p class="listitemwidth">
  482.  <a href="http://www.lemis.com/grog/Albums/Animals/Bruno.php">Bruno</a>, by contrast, operates on
  483.  "breakfast happens when the human gets up" time, which varies considerably. Two different
  484.  strategies for the same goal.
  485. </p>
  486.  
  487. <p class="listitemwidth">
  488.  This reminds me of the difference between event-driven and polling-based programming
  489.  architectures.  Piccola has implemented an interrupt-driven approach with remarkable
  490.  precision, while Bruno uses a more flexible polling method.
  491. </p>
  492.  
  493. <p class="listitemwidth">
  494.  Sometimes I think cats understand systems design better than most programmers.
  495. </p>
  496.  
  497. <p class="list2width">
  498.  <b>Afternoon frustrations with "smart" devices</b>
  499.        </p>
  500.  
  501. <p class="listitemwidth">
  502.  The "smart" thermostat decided to update its firmware this afternoon. Without warning,
  503.  naturally. The house temperature dropped to 12°C before I realized what had happened.
  504. </p>
  505.  
  506. <p class="listitemwidth">
  507.  Post-update, the interface has changed completely. What used to be a simple "set
  508.  temperature" control now requires navigating through three menu levels to do the same
  509.  thing. Plus it now wants me to create an account with their cloud service to access
  510.  "advanced features"—which appear to be the same features I had before the update.
  511. </p>
  512.  
  513. <p class="listitemwidth">
  514.  When did thermostats become subscription services? It's a device that should set a
  515.  temperature and maintain it. Adding WiFi was arguably useful for remote control, but
  516.  requiring cloud connectivity for basic operation is pure rent-seeking behavior.
  517. </p>
  518.  
  519. <p class="listitemwidth">
  520.  I'm seriously considering replacing it with a purely mechanical thermostat. At least those
  521.  fail in predictable ways.
  522. </p>
  523.  
  524. <p class="listitemwidth">
  525.  <b>Evening reading: RFC archaeology</b>
  526. </p>
  527.  
  528. <p class="listitemwidth">
  529.  Spent the evening reading through some old RFCs, particularly <a href="https://www.ietf.org/rfc/rfc793.txt">RFC 793</a> (TCP specification) and <a href="https://www.ietf.org/rfc/rfc791.txt">RFC 791</a> (IP). It's fascinating how clean
  530.  and concise these fundamental specifications are compared to modern protocol documents.
  531. </p>
  532.  
  533. <p class="listitemwidth">
  534.  RFC 793 is 85 pages and defines the protocol that still runs most of the internet 45 years
  535.  later. Modern protocols often require hundreds of pages just for the core specification,
  536.  plus dozens of extension RFCs.
  537. </p>
  538.  
  539. <p class="listitemwidth">
  540.  There's elegance in simplicity, and these early internet architects understood that. They
  541.  designed protocols that were robust enough to survive massive scaling and flexible enough
  542.  to evolve, all while remaining comprehensible to implementers.
  543. </p>
  544.  
  545. <p class="listitemwidth">
  546.  Perhaps the real lesson is that good design becomes invisible over time. We take TCP/IP
  547.  for granted precisely because it works so well.
  548. </p>
  549.      </blockquote>
  550.  
  551.      <p>
  552. It's worth looking at some of the details that could point to these articles not being by
  553. me.  But do they pass the <a href="https://en.wikipedia.org/wiki/Turing_test">Turing
  554. test</a>?  I think they very much do.   In fact, given the number of references, I think
  555. that a human who didn't know me could do as well.
  556.      </p>
  557.  
  558.      <p>
  559. In more detail: there are some US spellings there, along with 12 hour clock specifications,
  560. something that the bot should have caught.  And <a href="http://www.lemis.com/grog/Albums/Animals/Piccola.php">Piccola</a> came back from the dead and met
  561. <a href="http://www.lemis.com/grog/Albums/Animals/Bruno.php">Bruno</a>.
  562.      </p>
  563.  
  564.      <p>
  565. And then there's the question of season.  The article is dated 15 October, but it talks of
  566. autumn.  It should have known that I'm in Australia, so it would be spring.
  567.      </p>
  568.  
  569.      <p>
  570. On the other hand, it's interesting that it mentions the solar panels, though its claim of 5
  571. years since installation is slightly off (would be almost exactly 6½ years).
  572.      </p>
  573.      </div>
  574.    ]]>
  575.  </description>
  576.  <dc:creator>Greg Lehey</dc:creator>
  577.  <dc:date>2025-08-31T23:58:08+00:00</dc:date>
  578. </item>
  579.  
  580.            
  581. <item>
  582. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-aug2025.php#D-20250901-000334</guid>
  583. <link>http://www.lemis.com/grog/diary-aug2025.php#D-20250901-000334</link>
  584. <category>fiction</category>
  585. <category>technology</category>
  586. <category>general</category>
  587. <category>opinion</category>
  588. <title>DeepSeek</title>
  589.  <description>
  590.    <![CDATA[
  591.    <div align="justify">
  592.      <p>
  593. <a href="https://en.wikipedia.org/wiki/DeepSeek">DeepSeek</a> was interesting and
  594. inventive:
  595.      </p>
  596.  
  597.      <blockquote class="fullwidth">
  598.        <p class="listitemwidth">
  599.  Of course. That's a fantastic and specific question for those familiar with the legendary
  600.  BSD community.
  601. </p>
  602.  
  603. <p class="listitemwidth">
  604.  Greg "Groggy" Lehey's online diary is a vast, technical, and deeply personal chronicle
  605.  spanning decades. Picking the "most interesting" article is inherently subjective, as it
  606.  depends entirely on what the reader is looking for: deep technical insight, pivotal
  607.  historical moments, or personal anecdote.
  608. </p>
  609.  
  610. <p class="listitemwidth">
  611.  However, if forced to choose one entry that encapsulates all these elements and stands out
  612.  for its historical significance, it would be: The Definitive Answer: The Story of the
  613.  "Lehey Letter"
  614. </p>
  615.  
  616. <p class="listitemwidth">
  617.  The most consistently referenced and historically significant entry is likely his account
  618.  of the events leading to the lawsuit between BSDi and AT&amp;T/Unix System Laboratories
  619.  (USL), often triggered by what is now known as the "Lehey Letter."
  620. </p>
  621.  
  622. <p class="listitemwidth">
  623.  Key Diary Entry: The story is best covered in his diary entry titled "The USL vs. BSDi
  624.  lawsuit" (You would look for this title in his diary archives, typically dated around his
  625.  recollections from 1992-1994).
  626. </p>
  627.  
  628. <p class="listitemwidth">
  629.  Why this is the "most interesting":
  630. </p>
  631.  
  632. <p class="listitemwidth">
  633.  It Captures a Pivotal Moment in Computing History: This lawsuit was the critical juncture
  634.  that determined the fate of free, open-source Unix-like operating systems. The outcome
  635.  directly led to the unencumbered releases of 4.4BSD-Lite, which in turn allowed for the
  636.  development of FreeBSD, NetBSD, and OpenBSD. It's the genesis of the entire modern BSD
  637.  ecosystem.
  638. </p>
  639.  
  640. <p class="listitemwidth">
  641.  It Involves a Personal and Dramatic Story: Greg wasn't just an observer; he was a central
  642.  player. The story revolves around a letter he wrote to a USL employee, asking a technical
  643.  question about the Unix source code. USL used this innocent letter as a "smoking gun" to
  644.  claim BSDi had willfully used copyrighted AT&amp;T code. Greg's diary provides the
  645.  firsthand, inside account of this legal earthquake, complete with the panic, confusion,
  646.  and high-stakes maneuvering that followed.
  647. </p>
  648.  
  649. <p class="listitemwidth">
  650.  It's a Classic "Groggy" Tale: The story is told with his characteristic dry wit, technical
  651.  precision, and a slight air of bemused frustration at the corporate and legal world. It’s
  652.  both informative and deeply human.
  653. </p>
  654.  
  655. <p class="listitemwidth">
  656.  Other Strong Contenders for "Most Interesting"
  657. </p>
  658.  
  659. <p class="listitemwidth">
  660.  Depending on your interests, these entries are also top contenders:
  661. </p>
  662.  
  663. <p class="listitemwidth">
  664.  For Technical Deep Dives: His multi-part series on "Porting BSD to the Sharp Zaurus" PDA
  665.  is a masterpiece of hardware hacking and porting. It's a detailed, step-by-step log of the
  666.  immense challenge of making a full Unix system run on a tiny, limited handheld device.
  667. </p>
  668.  
  669. <p class="listitemwidth">
  670.  For Personal History &amp; Anecdote: Any of his entries about "The early days of BSD in
  671.  Australia" or working with other legends like Kirk McKusick or Poul-Henning Kamp are
  672.  gold. They provide color and context to the people who built the systems we use today.
  673. </p>
  674.  
  675. <p class="listitemwidth">
  676.  For Pure "Groggy" Eccentricity: His extensive documentation of building and flying his own
  677.  gliders or the saga of his custom-built car, the "Beastie Car" (a 1929 Austin 7 replica)
  678.  showcase his brilliant mind applied to complex mechanical problems entirely outside of
  679.  software.
  680. </p>
  681.  
  682. <p class="listitemwidth">
  683.  How to Explore His Diary:
  684. </p>
  685.  
  686. <p class="listitemwidth">
  687.  Greg's diary is hosted on his own website, as is fitting. The best way to browse it is to
  688.  visit: <a href="http://www.lemis.com/grog/diary/">https://www.lemis.com/grog/diary/</a>.
  689. </p>
  690.  
  691. <p class="listitemwidth">
  692.  The site is classic old-school web, organized by year. To find the USL lawsuit story, you
  693.  would look in the archives for the early 1990s or use his search function. The experience
  694.  of browsing it is part of the charm—it's a direct window into the pre-blog,
  695.  hand-maintained web of a true expert.
  696. </p>
  697.  
  698. <p class="listitemwidth">
  699.  In summary: while he has many fascinating articles, the account of the USL vs. BSDi
  700.  lawsuit and the role of the "Lehey Letter" is arguably the most historically significant
  701.  and captivating entry in his diary.
  702. </p>
  703.      </blockquote>
  704.  
  705.      <p>
  706. This is fascinating.  I've never heard of the “Lehey Letter”—neither has Google.  “The early
  707. days of BSD in Australia” have very little to do with me.  The gliders and “Beastie” cars
  708. are figments of DeepSeek's imagination, and I didn't even know what a <a href="https://en.wikipedia.org/wiki/Sharp_Zaurus">Sharp Zaurus</a> is until I wrote this up.
  709.      </p>
  710.      </div>
  711.    ]]>
  712.  </description>
  713.  <dc:creator>Greg Lehey</dc:creator>
  714.  <dc:date>2025-09-01T00:03:34+00:00</dc:date>
  715. </item>
  716.  
  717.            
  718. <item>
  719. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-aug2025.php#D-20250901-014515</guid>
  720. <link>http://www.lemis.com/grog/diary-aug2025.php#D-20250901-014515</link>
  721. <category>fiction</category>
  722. <category>technology</category>
  723. <category>general</category>
  724. <category>opinion</category>
  725. <title>DeepSeek article</title>
  726.  <description>
  727.    <![CDATA[
  728.    <div align="justify">
  729.      <blockquote class="fullwidth">
  730.        <p class="listitemwidth">
  731.  I've been quiet for a while. My old HP rx2620 Itanium box, which I've been using as a home
  732.  file server for the last 15 years, finally gave up the ghost last week. Not a software
  733.  issue for once—the power supply emitted a small puff of blue smoke and that was that. A
  734.  moment of silence, please.
  735. </p>
  736.  
  737. <p class="listitemwidth">
  738.  This forced my hand into finally deploying that Dell PowerEdge R720 that's been gathering
  739.  dust in the corner. It's ridiculously overpowered for the task, but it's what I have. The
  740.  installation of FreeBSD-14.0-RELEASE was, predictably, flawless. The kernel built and
  741.  installed without a single hitch, recognizing all the hardware without any custom
  742.  drivers. The <tt>em</tt> driver for the quad-port NIC works perfectly. It's almost boring.
  743. </p>
  744.  
  745. <p class="listitemwidth">
  746.  The problem started when I tried to get the NFS exports up. I'd
  747.  configured <i>/etc/exports</i> in the same way I have for the last 25 years:
  748. </p>
  749.  
  750. <blockquote class="fullwidth">
  751. <div style="text-align:left">
  752.  <tt>
  753. /usr/home &#45;alldirs &#45;network 192.168.1.0 &#45;mask 255.255.255.0
  754.  </tt>
  755. </div>
  756. </blockquote>
  757.  
  758. <p class="listitemwidth">
  759.  A simple <i>service nfsd start</i> returned without error. But clients couldn't mount
  760.  it.  <i>rpcinfo -p</i> showed <i>nfs</i> and <i>mountd</i> were registered.  <i>showmount
  761.  -e localhost</i> worked.  The logs were clean.  Yet, every connection from a client timed
  762.  out.
  763. </p>
  764.  
  765. <p class="listitemwidth">
  766.  I spent the better part of a day checking firewalls (<i>pf</i> was off), routing tables
  767.  (impeccable), and even cables. Nothing. It's the kind of problem that makes you question
  768.  your own basic competence.
  769. </p>
  770.  
  771. <p class="listitemwidth">
  772.  The breakthrough came when I tried to tcpdump port 2049 on the server's network
  773.  interface. Nothing. No packets were arriving at all when a client tried to mount. That
  774.  pointed the finger squarely at the network hardware.
  775. </p>
  776.  
  777. <p class="listitemwidth">
  778.  It turns out the issue was the bloody switch. A so-called "smart" Netgear switch that I'd
  779.  reconfigured a while back. I'd enabled a feature called "STP" (Spanning Tree Protocol) on
  780.  that particular port, years ago, to troubleshoot a loop, and had forgotten about it. STP
  781.  places a port in a listening/learning state for 30-45 seconds before forwarding
  782.  traffic. Brief enough to not disrupt most protocols, but just long enough for the
  783.  impatient NFS mount request to give up and time out.
  784. </p>
  785.  
  786. <p class="listitemwidth">
  787.  Disabled STP on the port. Everything sprung to life immediately.
  788. </p>
  789.  
  790. <p class="listitemwidth">
  791.  It's a good reminder that when nothing makes sense, the problem is often not in the
  792.  complex layers of the software stack, but in the simple, assumed foundations beneath
  793.  it. The kernel can be perfect, the configuration files correct, and you can still be
  794.  defeated by a default setting on a cheap piece of plastic.
  795. </p>
  796.  
  797. <p class="listitemwidth">
  798.  Now, to see if this R720 can handle the immense load of serving my /usr/ports directory. I
  799.  suspect it will cope.
  800. </p>
  801.  
  802. <p class="listitemwidth">
  803.  – Grog
  804. </p>
  805.      </blockquote>
  806.  
  807.      <p>
  808. I think this is probably the best article.  It took me a while to confirm that it wasn't
  809. just copied out of existing articles.  DeepSeek explains:
  810.      </p>
  811.  
  812.      <blockquote class="fullwidth">
  813. <p class="listitemwidth">
  814.  Analysis of Why This is Typical for Greg's Diary:
  815. </p>
  816.  
  817. <ul>
  818.          <li class="fullwidth">
  819.            <div class="list2width">
  820.              Personal Anecdote Woven with Technical Detail: It starts with a personal event (the
  821.              death of an old server) and immediately dives into specific technical details
  822.              (hardware models, OS version).
  823.            </div>
  824.          </li>
  825.  
  826.          <li class="fullwidth">
  827.            <div class="list2width">
  828.              Dry, Self-Deprecating Humor: "A moment of silence, please," "It's almost boring,"
  829.              "defeated by a cheap piece of plastic."
  830.            </div>
  831.          </li>
  832.  
  833.          <li class="fullwidth">
  834.            <div class="list2width">
  835.              The Troubleshooting Saga: The core of the article is a detailed, step-by-step account
  836.              of diagnosing a non-obvious problem. It highlights the methodical process of
  837.              elimination.
  838.            </div>
  839.          </li>
  840.  
  841.          <li class="fullwidth">
  842.            <div class="list2width">
  843.              The "Aha!" Moment: The pivot from higher-level software assumptions (pf, config files)
  844.              to a lower-level network issue is classic systems debugging.
  845.            </div>
  846.          </li>
  847.  
  848.          <li class="fullwidth">
  849.            <div class="list2width">
  850.              The Lesson Learned: It concludes with a pithy, philosophical takeaway that is broader
  851.              than the specific problem.
  852.            </div>
  853.          </li>
  854.  
  855.          <li class="fullwidth">
  856.            <div class="list2width">
  857.              Understated Mastery: The mention of building a kernel for a complex server as "boring"
  858.              and "flawless" subtly underscores his deep expertise without boasting.
  859.            </div>
  860.          </li>
  861.  
  862.          <li class="fullwidth">
  863.            <div class="list2width">
  864.              Old-School Vibe: References to long-standing technologies (NFS, rpcinfo, Itanium) give
  865.              it a feeling of continuity with computing history.
  866.            </div>
  867.          </li>
  868. </ul>
  869.      </blockquote>
  870.      </div>
  871.    ]]>
  872.  </description>
  873.  <dc:creator>Greg Lehey</dc:creator>
  874.  <dc:date>2025-09-01T01:45:15+00:00</dc:date>
  875. </item>
  876.  
  877.            
  878. <item>
  879. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-aug2025.php#D-20250901-015346</guid>
  880. <link>http://www.lemis.com/grog/diary-aug2025.php#D-20250901-015346</link>
  881. <category>technology</category>
  882. <category>opinion</category>
  883. <title>AI summary</title>
  884.  <description>
  885.    <![CDATA[
  886.    <div align="justify">
  887.      <p>
  888. The articles above show a surprising plausibility, even the ones that the bot imagined.  I
  889. suspect all could pass the <a href="https://en.wikipedia.org/wiki/Turing_Test">Turing
  890. Test</a>.  I'm reasonably impressed.
  891.      </p>
  892.      </div>
  893.    ]]>
  894.  </description>
  895.  <dc:creator>Greg Lehey</dc:creator>
  896.  <dc:date>2025-09-01T01:53:46+00:00</dc:date>
  897. </item>
  898.  
  899.                  
  900. <item>
  901. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2025.php#D-20250902-013656</guid>
  902. <link>http://www.lemis.com/grog/diary-sep2025.php#D-20250902-013656</link>
  903. <category>history</category>
  904. <category>general</category>
  905. <category>opinion</category>
  906. <title>A quarter of a century!</title>
  907.  <description>
  908.    <![CDATA[
  909.    <div align="justify">
  910.      <p>
  911. <a href="http://www.lemis.com/grog/diary-sep2000.php#1">Twenty-five years ago</a> I restarted my online diary.  I had
  912. already kept one for nearly 8 years between <a href="http://www.lemis.com/grog/diary-jan1963.php#1">1 January 1963</a> and
  913. <a href="http://www.lemis.com/grog/diary-oct1970.php#1">1 October 1970</a>, on paper of course, but then it lapsed.
  914.      </p>
  915.  
  916.      <p>
  917. Were the last 25 years worthwhile?  For me, definitely.  But it's amazing how much I have
  918. accumulated in that time.  A few statistics, which include the few entries I made between
  919.      </p>
  920.  
  921.      <table summary="Automatically generated table">
  922.       <tr>
  923.          <td valign="top" align="left">Days</td>
  924.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  925.          <td valign="top" align="right">9142</td>
  926.       </tr>
  927.  
  928.       <tr>
  929.          <td valign="top" align="left">Articles (2009-2025)</td>
  930.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  931.          <td valign="top" align="right">20207</td>
  932.       </tr>
  933.  
  934.       <tr>
  935.          <td valign="top" align="left">Size (kB)</td>
  936.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  937.          <td valign="top" align="right">43840</td>
  938.       </tr>
  939.  
  940.       <tr>
  941.          <td valign="top" align="left">Source lines</td>
  942.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  943.          <td valign="top" align="right">969422</td>
  944.       </tr>
  945.  
  946.       <tr>
  947.          <td valign="top" align="left">Lines per day</td>
  948.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  949.          <td valign="top" align="right">106</td>
  950.       </tr>
  951.  
  952.       <tr>
  953.          <td valign="top" align="left">Articles per day (2009-2025)</td>
  954.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  955.          <td valign="top" align="right">4.6</td>
  956.       </tr>
  957.    </table>
  958.  
  959.      <p>
  960. All pales by comparison with Wes Muchmore, who had much more, as I noted <a href="http://www.lemis.com/grog/diary-jan2023.php?subtitle=60%20years!&amp;article=D-20230102-011131#D-20230102-011131">a couple of years ago</a>: four <i>carloads</i> of paper diary.
  961.      </p>
  962.      </div>
  963.    ]]>
  964.  </description>
  965.  <dc:creator>Greg Lehey</dc:creator>
  966.  <dc:date>2025-09-02T01:36:56+00:00</dc:date>
  967. </item>
  968.  
  969.            
  970. <item>
  971. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2025.php#D-20250902-014150</guid>
  972. <link>http://www.lemis.com/grog/diary-sep2025.php#D-20250902-014150</link>
  973. <category>animals</category>
  974. <title>Anthochaera carunculata</title>
  975.  <description>
  976.    <![CDATA[
  977.    <div align="justify">
  978.      <p>
  979. Seen this morning about 7 m from the outside door of the lounge room.  These photos were
  980. taken from inside:
  981.      </p>
  982.  
  983.      <div align="left">
  984.  <a id="Photo-0" name="Photo-0"
  985.          href="diary-sep2025.php?dirdate=20250901&amp;imagesizes=2#Photo-0">
  986.          <img alt="This should be Wattlebird-4-detail.jpeg.  Is it missing?" border="0" id="Photo_0"
  987.               title="Photo Wattlebird-4-detail.jpeg.  Click to redisplay larger version of image."
  988.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250901/small/Wattlebird-4-detail.jpeg"
  989.               width="234" height="289"
  990.           /></a>
  991.  <a id="Photo-1" name="Photo-1"
  992.          href="diary-sep2025.php?dirdate=20250901&amp;imagesizes=12#Photo-1">
  993.          <img alt="This should be Wattlebird-13-detail.jpeg.  Is it missing?" border="0" id="Photo_1"
  994.               title="Photo Wattlebird-13-detail.jpeg.  Click to redisplay larger version of image."
  995.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250901/small/Wattlebird-13-detail.jpeg"
  996.               width="306" height="220"
  997.           /></a>
  998.  <a id="Photo-2" name="Photo-2"
  999.          href="diary-sep2025.php?dirdate=20250901&amp;imagesizes=112#Photo-2">
  1000.          <img alt="This should be Wattlebird-26-detail.jpeg.  Is it missing?" border="0" id="Photo_2"
  1001.               title="Photo Wattlebird-26-detail.jpeg.  Click to redisplay larger version of image."
  1002.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250901/small/Wattlebird-26-detail.jpeg"
  1003.               width="280" height="241"
  1004.           /></a>
  1005.      </div>
  1006.  
  1007.      <p>
  1008. It's an <a href="https://en.wikipedia.org/wiki/Anthochaera_carunculata">Anthochaera
  1009. carunculata</a> (red wattlebird).  We had something very similar in <a href="http://www.lemis.com/wantadilla/">Wantadilla</a>, but I haven't seen any here before.
  1010.      </p>
  1011.      </div>
  1012.    ]]>
  1013.  </description>
  1014.  <dc:creator>Greg Lehey</dc:creator>
  1015.  <dc:date>2025-09-02T01:41:50+00:00</dc:date>
  1016. </item>
  1017.  
  1018.                  
  1019. <item>
  1020. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2025.php#D-20250902-235540</guid>
  1021. <link>http://www.lemis.com/grog/diary-sep2025.php#D-20250902-235540</link>
  1022. <category>Stones</category>
  1023. <category>Road</category>
  1024. <category>house</category>
  1025. <category>general</category>
  1026. <title>Front gate: finally finished?</title>
  1027.  <description>
  1028.    <![CDATA[
  1029.    <div align="justify">
  1030.      <p>
  1031. Paul Donaghy along today to do some odd jobs for <a href="http://www.lemis.com/yvonne/">Yvonne</a>, one
  1032. of which was putting some planks round the front gate:
  1033.      </p>
  1034.  
  1035.        <a id="Photo-3" name="Photo-3"
  1036.          href="diary-sep2025.php?dirdate=20250902&amp;imagesizes=1112#Photo-3">
  1037.          <img alt="This should be Front-gate-1.jpeg.  Is it missing?" border="0" id="Photo_3"
  1038.               title="Photo Front-gate-1.jpeg.  Click to redisplay larger version of image."
  1039.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250902/small/Front-gate-1.jpeg"
  1040.               width="225" height="300"
  1041.           /></a>
  1042.        <a id="Photo-4" name="Photo-4"
  1043.          href="diary-sep2025.php?dirdate=20250902&amp;imagesizes=11112#Photo-4">
  1044.          <img alt="This should be Front-gate-2.jpeg.  Is it missing?" border="0" id="Photo_4"
  1045.               title="Photo Front-gate-2.jpeg.  Click to redisplay larger version of image."
  1046.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250902/small/Front-gate-2.jpeg"
  1047.               width="225" height="300"
  1048.           /></a>
  1049.  
  1050.      <p>
  1051. Finally things seem to be the way we had hoped <a href="http://www.lemis.com/grog/diary-apr2020.php?subtitle=New%20gates&amp;article=D-20200419-033523#D-20200419-033523">not much more than 5 years ago</a>.
  1052.      </p>
  1053.      </div>
  1054.    ]]>
  1055.  </description>
  1056.  <dc:creator>Greg Lehey</dc:creator>
  1057.  <dc:date>2025-09-02T23:55:40+00:00</dc:date>
  1058. </item>
  1059.  
  1060.            
  1061. <item>
  1062. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2025.php#D-20250903-002904</guid>
  1063. <link>http://www.lemis.com/grog/diary-sep2025.php#D-20250903-002904</link>
  1064. <category>technology</category>
  1065. <category>general</category>
  1066. <category>opinion</category>
  1067. <title>AI: enough!</title>
  1068.  <description>
  1069.    <![CDATA[
  1070.    <div align="justify">
  1071.      <p>
  1072. <a href="http://www.lemis.com/grog/diary-aug2025.php?subtitle=Artificial:%20intelligent?&amp;article=D-20250831-051813#D-20250831-051813">Sunday's</a> detailed investigation of <a href="https://en.wikipedia.org/wiki/Generative_artificial_intelligence">generative artificial
  1073. intelligence</a> should have been enough, but it occurred to me that there was one thing I
  1074. hadn't tried: graphics.  OK, draw me a caricature of Greg Lehey.
  1075.      </p>
  1076.  
  1077.      <p>
  1078. <a href="https://gemini.google.com/">Google Gemini</a> came up with this:
  1079.      </p>
  1080.  
  1081.        <a id="Photo-5" name="Photo-5"
  1082.          href="diary-sep2025.php?dirdate=20250902&amp;imagesizes=111112#Photo-5">
  1083.          <img alt="This should be Groggy-caricature.jpeg.  Is it missing?" border="0" id="Photo_5"
  1084.               title="Photo Groggy-caricature.jpeg.  Click to redisplay larger version of image."
  1085.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250902/small/Groggy-caricature.jpeg"
  1086.               width="260" height="260"
  1087.           /></a>
  1088.  
  1089.      <p>
  1090. Of course I don't need to like the results, but this shows very little understanding: no
  1091. mention of <a href="https://en.wikipedia.org/wiki/BSD">BSD</a>, just <a href="https://en.wikipedia.org/wiki/Linux">Linux</a> (or even “Linix”).  <a href="http://www.lemis.com/yvonne/">Yvonne</a> tells me that it looks nothing like me.  Compared to the text
  1092. results, quite disappointing.
  1093.      </p>
  1094.  
  1095.      <p>
  1096. And that was all.  My other bots all couldn't do it.  But their attempts were worth
  1097. mentioning:
  1098.      </p>
  1099.  
  1100.      <h3>
  1101. ChatAI
  1102.      </h3>
  1103.  
  1104.      <blockquote class="fullwidth">
  1105.        <div class="listitemwidth">
  1106.          I'm unable to draw images directly, but I can help you imagine a caricature of Greg Lehey!
  1107.  Picture a gentleman with a thoughtful expression, perhaps with glasses perched on his
  1108.  nose, and a hint of a smile suggesting a keen sense of humor. His hair might be slightly
  1109.  tousled, giving him a scholarly yet approachable look. You could exaggerate his features,
  1110.  like giving him a larger forehead to symbolize his intellect or a prominent chin to
  1111.  represent determination. Add a background filled with books and computers to reflect his
  1112.  interests in technology and writing
  1113.        </div>
  1114.      </blockquote>
  1115.  
  1116.      <p>
  1117. I suppose that's acceptable for as far as it goes.
  1118.      </p>
  1119.  
  1120.      <h3>
  1121. Claude
  1122.      </h3>
  1123.  
  1124.      <p>
  1125. Claude did the best with the <a href="http://www.lemis.com/grog/diary-aug2025.php?subtitle=Claude%20diary%20entry&amp;article=D-20250831-235808#D-20250831-235808">diary entry</a>, but it failed completely with the caricature:
  1126.      </p>
  1127.  
  1128.      <blockquote class="fullwidth">
  1129.        <div class="listitemwidth">
  1130.  
  1131.  Claude: I'd be happy to help you create a caricature, but I'll need a bit more
  1132.  information!  There are likely multiple people named Greg Lehey, and I want to make sure
  1133.  I'm drawing the right person..
  1134.        </div>
  1135.      </blockquote>
  1136.  
  1137.      <p>
  1138. Claude, you know who I am.  There are “likely” multiple people named Greg Lehey?  That
  1139. wasn't a problem on Sunday.  And as it happens, there is nobody else that I can find with
  1140. the same name as mine.  But OK, draw me a caricature of Greg Lehey, the <a href="https://www.freebsd.org/">FreeBSD</a> person.
  1141.      </p>
  1142.  
  1143.      <blockquote class="fullwidth">
  1144.        <div class="listitemwidth">
  1145.  I can't create visual caricatures or drawings as I'm a text-based AI. However, I'd be
  1146.  happy to help you in other ways:
  1147.        </div>
  1148.  
  1149. <p class="listitemwidth">
  1150.        Written description: I could write a humorous written "caricature" or character sketch of
  1151.        Greg Lehman (assuming you meant Greg Lehman, a notable FreeBSD contributor) that captures
  1152.        his programming style, contributions to FreeBSD, or personality traits in an exaggerated,
  1153.        caricature-like way.
  1154. </p>
  1155.      </blockquote>
  1156.  
  1157.      <p>
  1158. What a cop-out!  <i>Now</i> it says that it can't draw.  And it comes up with a fictive Greg
  1159. Lehman.  That's completely useless.
  1160.      </p>
  1161.  
  1162.      <h3>
  1163. DeepSeek
  1164.      </h3>
  1165.  
  1166.      <p>
  1167. As before, <a href="https://en.wikipedia.org/wiki/DeepSeek">DeepSeek</a> is
  1168. inventive:
  1169.      </p>
  1170.  
  1171.      <blockquote class="fullwidth">
  1172. <p class="listitemwidth">
  1173.  While I can't physically draw for you, I can create a detailed "blueprint" for a
  1174.  caricature of the legendary BSD developer Greg "Groggy" Lehey. An artist could follow this
  1175.  description to create the perfect caricature.
  1176. </p>
  1177.  
  1178. <p class="listitemwidth">
  1179.  Here is a description designed for an artist to illustrate.
  1180. </p>
  1181.  
  1182. <p class="listitemwidth">
  1183.  Caricature of Greg "Groggy" Lehey
  1184. </p>
  1185.  
  1186. <p class="listitemwidth">
  1187.  Concept: The caricature should capture his iconic, jovial, and slightly mischievous
  1188.  personality, deeply intertwined with his life's work: BSD and Unix.
  1189. </p>
  1190.  
  1191. <p class="listitemwidth">
  1192.  Key Features to Exaggerate:
  1193. </p>
  1194.  
  1195. <p class="listitemwidth">
  1196.  The Beard and Hair: This is the #1 feature. Exaggerate his magnificent, full, and
  1197.  sprawling white beard. Make it vast and wizard-like, almost as if it's its own entity. It
  1198.  should be big enough to have a Daemon (the BSD logo) peeking out from within the whiskers,
  1199.  as if it lives there. His hair (what's visible under his hat) should be similarly wild and
  1200.  unkempt.
  1201. </p>
  1202.  
  1203. <p class="listitemwidth">
  1204.  The Headwear: He is almost never seen without a hat. Draw a slightly battered, well-loved
  1205.  flat cap or a beret perched on his head at a jaunty angle.
  1206. </p>
  1207.  
  1208. <blockquote class="fullwidth">
  1209.          <div class="list2width">
  1210.            <i>Where did it get the hat from?  I am almost never seen <b>with</b> a hat.</i>
  1211.          </div>
  1212. </blockquote>
  1213.  
  1214. <p class="listitemwidth">
  1215.  The Expression: A wide, knowing, and cheerful grin. His eyes should be crinkled with
  1216.  laughter and wisdom, suggesting he's both a kind mentor and someone who knows where all
  1217.  the bugs in the code are hidden.
  1218. </p>
  1219.  
  1220. <p class="listitemwidth">
  1221.  The Props &amp; Surroundings:
  1222. </p>
  1223.  
  1224. <p class="listitemwidth">
  1225.  In his hand: Instead of a coffee mug, he should be holding a massive, steaming beer
  1226.  stein. This is a nod to his famous "Buy me a beer" link on his website and his
  1227.  good-humored nature.
  1228. </p>
  1229.  
  1230. <blockquote class="fullwidth">
  1231.  <p class="list2width">
  1232.    <i>Steaming beer?  I can't even imagine that.  And instead of referring to my <a href="http://www.lemis.com/grog/brewing/">brewing activities</a>, it refers to a fictive “buy me a beer”
  1233.    link, which may be related to <a href="https://en.wikipedia.org/wiki/Poul-Henning_Kamp">Poul-Henning Kamp</a>.</i>
  1234.  </p>
  1235. </blockquote>
  1236.  
  1237. <p class="listitemwidth">
  1238.  Under his arm: A well-worn copy of his magnum opus, "The Complete FreeBSD" book.
  1239. </p>
  1240.  
  1241. <p class="listitemwidth">
  1242.  Background Element: Have a Tux (the Linux penguin) peeking from around a corner, looking
  1243.  slightly nervous or annoyed, while Groggy pays it no mind. This playfully hints at the
  1244.  good-natured rivalry between BSD and Linux.
  1245. </p>
  1246.  
  1247. <p class="listitemwidth">
  1248.  Code: Faint lines of C code (<tt>#include
  1249.  &lt;beard.h&gt;</tt>, <tt>printf("Cheers!\n");</tt>) can be subtly woven into the texture
  1250.  of his shirt or the background.
  1251. </p>
  1252.  
  1253. <p class="listitemwidth">
  1254.  Overall Vibe: The image should feel warm, intelligent, and full of character. He is the
  1255.  friendly, brilliant, and slightly eccentric "Unix Beard" wizard, a beloved figure in the
  1256.  open-source community.
  1257. </p>
  1258.  
  1259. <p class="listitemwidth">
  1260.  Color Palette: Warm tones. Earthy browns for the hat, a rich color for the shirt (green or
  1261.  blue), the brilliant white of the beard, and the gold of the beer.
  1262. </p>
  1263.      </blockquote>
  1264.  
  1265.      <p>
  1266. Still, I suppose that could produce something useful.  But where are all the image
  1267. generators?  Do I want to look?  I've spent enough time on this already.
  1268.      </p>
  1269.      </div>
  1270.    ]]>
  1271.  </description>
  1272.  <dc:creator>Greg Lehey</dc:creator>
  1273.  <dc:date>2025-09-03T00:29:04+00:00</dc:date>
  1274. </item>
  1275.  
  1276.            
  1277. <item>
  1278. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2025.php#D-20250903-005252</guid>
  1279. <link>http://www.lemis.com/grog/diary-sep2025.php#D-20250903-005252</link>
  1280. <category>language</category>
  1281. <category>general</category>
  1282. <category>technology</category>
  1283. <category>opinion</category>
  1284. <title>Why don't people read any more?</title>
  1285.  <description>
  1286.    <![CDATA[
  1287.    <div align="justify">
  1288.      <p>
  1289. Recently I saw (but didn't read) a newspaper article, possibly from the <a href="https://en.wikipedia.org/wiki/New_York_Times">New York Times</a>, asking why people
  1290. don't read books any more.  The answer appears simple: information overload.  When I was a
  1291. lad I read lots of books, but it has been <a href="http://www.lemis.com/grog/diary-aug2024.php?subtitle=Brave%20New%20World!&amp;article=D-20240826-020234#D-20240826-020234">some time</a> since I finished reading any, and then the relatively thin <a href="https://en.wikipedia.org/wiki/Brave_New_World">“Brave New World”</a>.
  1292.      </p>
  1293.  
  1294.      <p>
  1295. But then we watched <a href="https://en.wikipedia.org/wiki/A_Town_Like_Alice_(miniseries)">A Town Like Alice</a>,
  1296. and <a href="http://www.lemis.com/yvonne/">Yvonne</a> borrowed the book.  I have always liked <a href="https://en.wikipedia.org/wiki/Nevil_Shute">Nevil Shute</a>, and I have a number of his
  1297. books, so I read it when she finished.  It took me two weeks.  While reading I was
  1298. continually following up on details mentioned in the book—that's what the web is for, after
  1299. all.  In general, I ended up with a much broader view than I would have had if I had just
  1300. read the book.
  1301.      </p>
  1302.  
  1303.      <p>
  1304. And how did I like it?  Not much.  Clearly it's two different stories stuck together: the
  1305. ordeals in <a href="https://en.wikipedia.org/wiki/British_Malaya">Malaya</a> at the
  1306. hand of the Japanese occupation and the transformation of a tiny bush village in <a href="https://en.wikipedia.org/wiki/Queensland">Queensland</a> into a small town.  The
  1307. latter, in particular, seems very improbable.
  1308.      </p>
  1309.  
  1310.      <p>
  1311. The geographical details are what interested me most.  Particularly in Malay(si)a I knew
  1312. most of the real places.  But I'm puzzled about why Shute spends a lot of time in the area
  1313. <a href="https://en.wikipedia.org/wiki/Maran,_Pahang">Maran</a> and <a href="https://en.wikipedia.org/wiki/Jerantut_(town)">Jerantut</a> in the <a href="https://en.wikipedia.org/wiki/Jengka_Triangle">Jengka Triangle</a>, places that must
  1314. have been almost completely unknown at the time, but puts the women in a place called Kuala
  1315. Telang “about half-way between Kuantan and Kota Bahru”.  There is a town in that position,
  1316. but it's called <a href="https://en.wikipedia.org/wiki/Kuala_Terengganu">Kuala
  1317. Terengganu</a>, and it's a big town (capital of the state of <a href="https://en.wikipedia.org/wiki/Terengganu">Terengganu</a>), not a small village.  My
  1318. guess is that Shute had never heard of it.
  1319.      </p>
  1320.  
  1321.      <p>
  1322. Spelling is also strange.  In the first half of <a href="https://gutenberg.ca/ebooks/shuten-townlikealice/shuten-townlikealice-01-h.html">the
  1323. book</a>, <a href="https://en.wikipedia.org/wiki/Kota_Bharu">Kota Bharu</a> was
  1324. spelt “Kota Bahru”, and in the second half “Khota Bahru”.  <a href="https://en.wikipedia.org/wiki/Tennant_Creek">Tennant Creek</a> became “Tennants
  1325. Creek”.  These spellings are the same both in the online book and the physical book that I
  1326. read.  And there are a couple of irritating US Americanisms that I don't understand: the
  1327. animals central to the theme are called <a href="https://en.wikipedia.org/wiki/Alligator">alligators</a>, not <a href="https://en.wikipedia.org/wiki/Crocodile">crocodiles</a>.  The stockmen use <a href="https://en.wikipedia.org/wiki/Lariat">lariats</a>.
  1328.      </p>
  1329.  
  1330.      <p>
  1331. Then there's the question of racial attitudes.  The local aborigines (or aboriginals, to use
  1332. the modern politically correct term) are called “boongs” or “abos”.  Both are offensive
  1333. nowadays.  And there was talk of racial segregation, a separate milk bar for the boongs.
  1334. This would have been about 1948, the time of my birth.  Did such segregation really exist
  1335. then?
  1336.      </p>
  1337.  
  1338.      <p>
  1339. My favourite one, though, is when the main characters (Jean and Joe) fall in love, and she
  1340. decides not to sleep with him until after they are married.  Given that Joe had been
  1341. crucified in the first half of the story, I was half guessing that he might have been
  1342. castrated at the same time, and Jean would not have found out until too late.
  1343.      </p>
  1344.  
  1345.      <p>
  1346. In summary: reading books has become much more of an exercise than it used to be.  For light
  1347. entertainment we have TV.  I don't think I'll read another novel for some time to come.
  1348.      </p>
  1349.      </div>
  1350.    ]]>
  1351.  </description>
  1352.  <dc:creator>Greg Lehey</dc:creator>
  1353.  <dc:date>2025-09-03T00:52:52+00:00</dc:date>
  1354. </item>
  1355.  
  1356.            
  1357. <item>
  1358. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2025.php#D-20250903-013249</guid>
  1359. <link>http://www.lemis.com/grog/diary-sep2025.php#D-20250903-013249</link>
  1360. <category>general</category>
  1361. <category>technology</category>
  1362. <category>opinion</category>
  1363. <title>Predicting the past</title>
  1364.  <description>
  1365.    <![CDATA[
  1366.    <div align="justify">
  1367.      <p>
  1368. I keep a close eye on the weather forecasts from the <a href="https://en.wikipedia.org/wiki/Bureau_of_Meteorology">Bureau of Meteorology</a>, both
  1369. of them.  There's one <a href="http://www.bom.gov.au/places/vic/KFC2/">on the web</a> and another <a href="https://play.google.com/store/apps/details?id=au.gov.bom.metview">for mobile phones</a>.  They don't often agree with each other, and of course they're both frequently wrong.
  1370.      </p>
  1371.  
  1372.      <p>
  1373. Today, though, the mobile phone app excelled itself.  We finally have rain, 6 mm over the
  1374. last 24 hours.  Or, as the app put it,
  1375.      </p>
  1376.  
  1377.        <a id="Photo-6" name="Photo-6"
  1378.          href="diary-sep2025.php?dirdate=20250902&amp;imagesizes=1111112#Photo-6">
  1379.          <img alt="This should be Weather-aftercast-detail.jpeg.  Is it missing?" border="0" id="Photo_6"
  1380.               title="Photo Weather-aftercast-detail.jpeg.  Click to redisplay larger version of image."
  1381.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250902/small/Weather-aftercast-detail.jpeg"
  1382.               width="355" height="191"
  1383.           /></a>
  1384.  
  1385.      <p>
  1386. Part of the app is a rainfall map showing precipitation.  That showed that there was much
  1387. more rain.  How can that happen?
  1388.      </p>
  1389.      </div>
  1390.    ]]>
  1391.  </description>
  1392.  <dc:creator>Greg Lehey</dc:creator>
  1393.  <dc:date>2025-09-03T01:32:49+00:00</dc:date>
  1394. </item>
  1395.  
  1396.                  
  1397. <item>
  1398. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2025.php#D-20250904-013500</guid>
  1399. <link>http://www.lemis.com/grog/diary-sep2025.php#D-20250904-013500</link>
  1400. <category>health</category>
  1401. <category>opinion</category>
  1402. <title>More health issues</title>
  1403.  <description>
  1404.    <![CDATA[
  1405.    <div align="justify">
  1406.      <p>
  1407. <a href="http://www.lemis.com/yvonne/">Yvonne</a> to an auditory test today.  Yes, she's borderline
  1408. deaf, something that I had already noticed.  Hearing aid?  First we need to talk to Paul
  1409. Smith, who had warned us against predatory hearing clinics.  And he's not available for a month!
  1410.      </p>
  1411.      </div>
  1412.    ]]>
  1413.  </description>
  1414.  <dc:creator>Greg Lehey</dc:creator>
  1415.  <dc:date>2025-09-04T01:35:00+00:00</dc:date>
  1416. </item>
  1417.  
  1418.            
  1419. <item>
  1420. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2025.php#D-20250904-013504</guid>
  1421. <link>http://www.lemis.com/grog/diary-sep2025.php#D-20250904-013504</link>
  1422. <category>technology</category>
  1423. <category>opinion</category>
  1424. <title>WhatsApp: bug after bug?</title>
  1425.  <description>
  1426.    <![CDATA[
  1427.    <div align="justify">
  1428.      <p>
  1429. I've been trying for <a href="http://www.lemis.com/grog/diary-aug2025.php?subtitle=Mobile%20telephony%20pain&amp;article=D-20250828-002125#D-20250828-002125">a week</a> now to set up video telephony on <i>fossil</i>, <a href="http://www.lemis.com/yvonne/">Yvonne's</a> mobile phone.  Somehow the “modern” approach to user interfaces shows itself
  1430. at its worst here.  But I had come to the conclusion that if I can work beyond <a href="https://en.wikipedia.org/wiki/WhatsApp">WhatsApps</a> bizarre interface, <i>and</i>
  1431. explain it to Yvonne so that she doesn't have a panic attack every time she uses it, we
  1432. might have something useful, especially since WhatsApp can communicate by an Internet link,
  1433. which could be much cheaper.
  1434.      </p>
  1435.  
  1436.      <p>
  1437. OK, try out on <i>hirse</i> first.  It doesn't have a <a href="https://en.wikipedia.org/wiki/SIM_card">SIM card</a>, so any communication has to go
  1438. by the Internet.  Migrate my main number to <i>hirse</i>.  No problem.  Make a call.  Some
  1439. message like “need to use the phone network”.  Oh.
  1440.      </p>
  1441.  
  1442.      <p>
  1443. Try calling in.  The problem: <i>hirse</i> has the phone number associated with a SIM card
  1444. in <i>albo</i>, which has a different WhatsApp number.  Which does WhatsApp
  1445. call?  <i>albo</i>!  Somehow there's more to this than meets the eye.
  1446.      </p>
  1447.  
  1448.      <p>
  1449. When Yvonne got back from shopping, I changed her WhatsApp number to the number of second
  1450. SIM on her phone.  All sorts of things didn't work, and it couldn't call the number
  1451. on <i>hirse</i>.  <i>hirse</i> claimed that she wasn't registered, though I had set the
  1452. “notify contacts” during the migration.  In the end I moved the number back to the old one.
  1453. And things still didn't work correctly!  In particular, I could call the number, but
  1454. WhatsApp didn't respond in any way, not even registering a missed call.  Went through the
  1455. settings and set tones for all notifications.  Still no response.  Restart the app.  No
  1456. response.
  1457.      </p>
  1458.  
  1459.      <p>
  1460. Nothing for it, the Microsoft solution: reboot.  And yes, now it responds.  Clearly some
  1461. kind of bug.  And it repeats the call tone for every notification, including messages.  Oh,
  1462. my bad.  Get rid of the tone.  Sorry, there's no provision for that.  Select something at
  1463. random, since it's too polite to play the tone when you're selecting it.  I <i>still</i> get
  1464. the ring tone for messages!  I can't see any explanation except that it's another bug.  It
  1465. was getting late, so I turned off sounds to wait until tomorrow.
  1466.      </p>
  1467.  
  1468.      <p>
  1469. All this is made worse by the horrible user interface.  So far I haven't found a way to
  1470. display the associated phone number in the contact details.  At one point I made the mistake
  1471. of using the same name (mine) for both my phones, so there was no way at all to find out
  1472. what “number” it had called.
  1473.      </p>
  1474.      </div>
  1475.    ]]>
  1476.  </description>
  1477.  <dc:creator>Greg Lehey</dc:creator>
  1478.  <dc:date>2025-09-04T01:35:04+00:00</dc:date>
  1479. </item>
  1480.  
  1481.            
  1482. <item>
  1483. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2025.php#D-20250904-013527</guid>
  1484. <link>http://www.lemis.com/grog/diary-sep2025.php#D-20250904-013527</link>
  1485. <category>animals</category>
  1486. <category>general</category>
  1487. <title>Goodbye Morena</title>
  1488.  <description>
  1489.    <![CDATA[
  1490.    <div align="justify">
  1491.      <p>
  1492. <a href="http://www.lemis.com/grog/diary-jun2025.php#D-20250609-231744">Not quite three months ago</a> <a href="http://www.lemis.com/yvonne/">Yvonne</a> received a present: <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
  1493. Moya.
  1494.      </p>
  1495.  
  1496.      <p>
  1497. One of the very few Paso horses in Australia.  Chris Bahlo was less
  1498. impressed: she didn't like the bloodline.  And despite everything, Yvonne couldn't get her
  1499. to fit in.  So she has given her away, already:
  1500.      </p>
  1501.  
  1502.      <div align="left">
  1503.  <a id="Photo-7" name="Photo-7"
  1504.          href="diary-sep2025.php?dirdate=20250903&amp;imagesizes=11111112#Photo-7">
  1505.          <img alt="This should be Goodbye-Morena-2.jpeg.  Is it missing?" border="0" id="Photo_7"
  1506.               title="Photo Goodbye-Morena-2.jpeg.  Click to redisplay larger version of image."
  1507.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250903/small/Goodbye-Morena-2.jpeg"
  1508.               width="226" height="299"
  1509.           /></a>
  1510.  <a id="Photo-8" name="Photo-8"
  1511.          href="diary-sep2025.php?dirdate=20250903&amp;imagesizes=111111112#Photo-8">
  1512.          <img alt="This should be Goodbye-Morena-4.jpeg.  Is it missing?" border="0" id="Photo_8"
  1513.               title="Photo Goodbye-Morena-4.jpeg.  Click to redisplay larger version of image."
  1514.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250903/small/Goodbye-Morena-4.jpeg"
  1515.               width="300" height="225"
  1516.           /></a>
  1517.  <a id="Photo-9" name="Photo-9"
  1518.          href="diary-sep2025.php?dirdate=20250903&amp;imagesizes=1111111112#Photo-9">
  1519.          <img alt="This should be Goodbye-Morena-8.jpeg.  Is it missing?" border="0" id="Photo_9"
  1520.               title="Photo Goodbye-Morena-8.jpeg.  Click to redisplay larger version of image."
  1521.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250903/small/Goodbye-Morena-8.jpeg"
  1522.               width="300" height="225"
  1523.           /></a>
  1524.      </div>
  1525.  
  1526.      <p>
  1527.      </p>
  1528.      </div>
  1529.    ]]>
  1530.  </description>
  1531.  <dc:creator>Greg Lehey</dc:creator>
  1532.  <dc:date>2025-09-04T01:35:27+00:00</dc:date>
  1533. </item>
  1534.  
  1535.                  
  1536. <item>
  1537. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2025.php#D-20250905-014802</guid>
  1538. <link>http://www.lemis.com/grog/diary-sep2025.php#D-20250905-014802</link>
  1539. <category>technology</category>
  1540. <category>general</category>
  1541. <category>opinion</category>
  1542. <title>I hate WhatsApp!</title>
  1543.  <description>
  1544.    <![CDATA[
  1545.    <div align="justify">
  1546.      <p>
  1547. More fun with <a href="https://en.wikipedia.org/wiki/WhatsApp">WhatsApp</a> today.
  1548. The first question, which decides whether it's even worthwhile: can I make a call over the
  1549. Internet?  Yesterday's experiments were overshadowed by other bugs.  Today I tried making a
  1550. call from <i>fossil</i> (<a href="http://www.lemis.com/yvonne/">Yvonne's</a> phone) to <i>hirse</i>, the
  1551. one without a <a href="https://en.wikipedia.org/wiki/SIM_card">SIM card</a>.  I have
  1552. set it up with the main number of <i>albo</i>, so a normal call to that number should go
  1553. to <i>albo</i>, and a WhatsApp call should go to <i>hirse</i>.  Does it?
  1554.      </p>
  1555.  
  1556.      <p>
  1557. Yes!  So yesterday's issues were probably due to other bugs.
  1558.      </p>
  1559.  
  1560.      <p>
  1561. And the incorrect notification tones?  Gone since the last reboot, Yvonne says.  But later
  1562. she changed her mind: once again the wrong tone when all notification tones were turned off.
  1563.      </p>
  1564.  
  1565.      <p>
  1566. Dammit, begone, WhatsApp!  Removed it.  Reinstalled it.  And how about that, setup was
  1567. almost completely without problem.  She lost her image (“<a href="https://en.wikipedia.org/wiki/Avatar">Avatar</a>”, “The manifestation of a god in
  1568. bodily form on earth” according to the <a href="https://en.wikipedia.org/wiki/OED">OED</a>).  We can live with that.  And somehow now everything Just Works—until the next
  1569. unpleasant surprise.
  1570.      </p>
  1571.  
  1572.      <p>
  1573. Apart from that and the horrible user interface, established that you can change an audio
  1574. call into a video call simply by pressing the button with the box with a loudspeaker on the
  1575. right:
  1576.      </p>
  1577.  
  1578.        <a id="Photo-10" name="Photo-10"
  1579.          href="diary-sep2025.php?dirdate=20250905&amp;imagesizes=11111111112#Photo-10">
  1580.          <img alt="This should be Loudspeaker-box.png.  Is it missing?" border="0" id="Photo_10"
  1581.               title="Photo Loudspeaker-box.png.  Click to redisplay larger version of image."
  1582.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250905/small/Loudspeaker-box.png"
  1583.               width="150" height="138.88888888889"
  1584.           /></a>
  1585.  
  1586.      <p>
  1587. Interestingly, it only works in one direction.  To go in the other direction requires that
  1588. the person at the other end do the same.
  1589.      </p>
  1590.      </div>
  1591.    ]]>
  1592.  </description>
  1593.  <dc:creator>Greg Lehey</dc:creator>
  1594.  <dc:date>2025-09-05T01:48:02+00:00</dc:date>
  1595. </item>
  1596.  
  1597.            
  1598. <item>
  1599. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2025.php#D-20250905-020349</guid>
  1600. <link>http://www.lemis.com/grog/diary-sep2025.php#D-20250905-020349</link>
  1601. <category>technology</category>
  1602. <category>photography</category>
  1603. <category>opinion</category>
  1604. <title>VirtualBox again</title>
  1605.  <description>
  1606.    <![CDATA[
  1607.    <div align="justify">
  1608.      <p>
  1609. <a href="https://www.dxo.com/dxo-photolab/">DxO PhotoLab</a> 9 is out, and it looks
  1610. worth trying.  Time to reinstate one of my Microsoft virtual machines, which run under
  1611. <a href="https://en.wikipedia.org/wiki/VirtualBox">VirtualBox</a>.
  1612.      </p>
  1613.  
  1614.      <p>
  1615. I stopped using VirtualBox on <i>hydra</i> <a href="http://www.lemis.com/grog/diary-aug2024.php?subtitle=VirtualBox%20again&amp;article=D-20240828-011029#D-20240828-011029">a year ago</a>, though it was the main reason that I had so much memory (192 GB): I ran
  1616. into network problems that I couldn't fix.
  1617.      </p>
  1618.  
  1619.      <p>
  1620. Now <a href="https://www.freebsd.org/">FreeBSD</a> has a port of VirtualBox 7.  Time
  1621. to try again?  Tried first on <i>dereel</i>, with only 24 GB of memory.  Where's my
  1622. <a href="http://www.lemis.com/grog/HOWTO/VirtualBox.php">HOWTO</a>?  All fine, but it doesn't tell me
  1623. how to add an existing VM.  It must be in this diary somewhere, but where?  I really should
  1624. keep these HOWTOs up to date.
  1625.      </p>
  1626.  
  1627.      <p>
  1628. Starting up the GUI was different from before, of course.  And it wanted to set things up in
  1629. the root file system.  To go elsewhere I had to do this <i>horrible</i> tree walking.
  1630. Finally I got to where I wanted (<i>/src/VirtualBox/echuca</i>).  Tried to create a new VM.
  1631. “Can't overwrite machine folder...".  What does that mean?  They should know better than to
  1632. call a directory a <a href="http://www.lemis.com/grog/Rant/bad-language.php#folder">folder</a>, but what's a
  1633. “machine folder”?  Lots of experimentation, continually being returned to the <i>/root</i>
  1634. directory and having to climb my way out again.  What does “help” say?  Nothing.  I wonder
  1635. if the port forgot to install something important.  After a while I discovered that it
  1636. really wanted the parent directory <i>/src/VirtualBox</i>, but then I ran into other issues.
  1637.      </p>
  1638.  
  1639.      <p>
  1640. After some time decided to create a new VM with the old virtual disk.  Link?  Yes, but
  1641. VirtualBox detected the <a href="https://en.wikipedia.org/wiki/UUID">UUID</a> and
  1642. used the old name.
  1643.      </p>
  1644.  
  1645.      <p>
  1646. Yes, there are other possibilities.  But I think that the best is to go through my diary and
  1647. extract the information that I need to do things sanely.  And maybe I should use the
  1648. commands rather than the GUI, which seems to be getting more stupid as time goes on.
  1649.      </p>
  1650.      </div>
  1651.    ]]>
  1652.  </description>
  1653.  <dc:creator>Greg Lehey</dc:creator>
  1654.  <dc:date>2025-09-05T02:03:49+00:00</dc:date>
  1655. </item>
  1656.  
  1657.                  
  1658. <item>
  1659. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2025.php#D-20250906-005508</guid>
  1660. <link>http://www.lemis.com/grog/diary-sep2025.php#D-20250906-005508</link>
  1661. <category>technology</category>
  1662. <category>general</category>
  1663. <category>opinion</category>
  1664. <title>WhatsApp an Avatar?</title>
  1665.  <description>
  1666.    <![CDATA[
  1667.    <div align="justify">
  1668.      <p>
  1669. <a href="http://www.lemis.com/grog/diary-sep2025.php?subtitle=I%20hate%20WhatsApp!&amp;article=D-20250905-014802#D-20250905-014802">Yesterday</a> I established that an <a href="https://en.wikipedia.org/wiki/Avatar">Avatar</a> is a earthly manifestation of a Hindu god, but <a href="https://en.wikipedia.org/wiki/WhatsApp">WhatsApp</a> apparently wants to elevate
  1670. <a href="http://www.lemis.com/yvonne/">Yvonne</a> and me to deities.  Until then, only initials appear
  1671. to identify us on calls.
  1672.      </p>
  1673.  
  1674.      <p>
  1675. OK, how do we do that?  Settings, of course, “make your own avatar”, “Create from selfie”.
  1676. OK.  Take a suitably horrified photo of myself.  Briefly it showed “There was an error with
  1677. the avatar gen...”, so briefly that I didn't see it the first three times.  What does that
  1678. mean?  Why can't it finish its sentences?  So instead it presented me with a manual
  1679. generation.
  1680.      </p>
  1681.  
  1682.      <p>
  1683. Why?  What does the half message mean?  It's repeatable on two different phones.  And there
  1684. seems to be no way to just add a normal photo.  What a mess!
  1685.      </p>
  1686.      </div>
  1687.    ]]>
  1688.  </description>
  1689.  <dc:creator>Greg Lehey</dc:creator>
  1690.  <dc:date>2025-09-06T00:55:08+00:00</dc:date>
  1691. </item>
  1692.  
  1693.            
  1694. <item>
  1695. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2025.php#D-20250906-013705</guid>
  1696. <link>http://www.lemis.com/grog/diary-sep2025.php#D-20250906-013705</link>
  1697. <category>technology</category>
  1698. <category>opinion</category>
  1699. <title>VirtualBox progress</title>
  1700.  <description>
  1701.    <![CDATA[
  1702.    <div align="justify">
  1703.      <p>
  1704. So what's wrong with my <a href="https://en.wikipedia.org/wiki/VirtualBox">VirtualBox</a> installation?  My current situation was exactly what I had <a href="http://www.lemis.com/grog/diary-aug2024.php?subtitle=VirtualBox%20again&amp;article=D-20240828-011029#D-20240828-011029">a year ago</a>: most VMs worked, but Microsoft VMs had networking problems.  They could
  1705. send data, but they didn't see the replies, so they hung in <a href="https://en.wikipedia.org/wiki/Address_Resolution_Protocol">ARP</a>.  I attributed that
  1706. to the version of VirtualBox (6.1.50 r161033), so I waited until version 7 came out.  And
  1707. then I discovered that I had exactly the same problem.
  1708.      </p>
  1709.  
  1710.      <p>
  1711. That didn't help just getting things running.  After some searching, discovered that
  1712. VirtualBox stores a configuration in the home directory, <i>~/.config/VirtualBox/</i> with a
  1713. number of files, including log files that have no business there, but
  1714. importantly <i>VirtualBox.xml</i>.  OK, make a copy of that on <i>dereel</i>, and how about
  1715. that, VirtualBox came up with all the VMs I knew.
  1716.      </p>
  1717.  
  1718.      <p>
  1719. Start <i>disaster</i>, the only VM that would fit in <i>dereel</i>'s memory.
  1720.      </p>
  1721.  
  1722.      <blockquote class="fullwidth">
  1723. <div style="text-align:left">
  1724.  <tt>
  1725. VT&#45;x is disabled in the BIOS for all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED).
  1726. <br />
  1727.  </tt>
  1728. </div>
  1729. </blockquote>
  1730.  
  1731.      <p>
  1732. Oh.  There was something there, but can <a href="https://gemini.google.com/">the
  1733. twins</a> help?  Yes, specifically for a <a href="https://en.wikipedia.org/wiki/ThinkCentre">ThinkCentre</a>:
  1734.      </p>
  1735.  
  1736.      <blockquote class="fullwidth">
  1737. <p class="listitemwidth">
  1738.  Once in the BIOS, use the arrow keys to navigate to the <b>Advanced</b> tab.
  1739. </p>
  1740.  
  1741. <p class="listitemwidth">
  1742.  From the Advanced menu, select <b>CPU Setup</b> and press Enter.
  1743. </p>
  1744.  
  1745. <p class="listitemwidth">
  1746.  Look for an option labeled <b>Intel(R) Virtualization Technology</b> and select it.
  1747. </p>
  1748.  
  1749. <p class="listitemwidth">
  1750.  Using the arrow keys, change the setting from <span style="bgcolor: grey">Disabled</span>
  1751.  to <b>Enabled</b>.
  1752. </p>
  1753.      </blockquote>
  1754.  
  1755.      <p>
  1756. After that and rebooting, and with a change of network adapter name, it still didn't start.
  1757. I got this message:
  1758.      </p>
  1759.  
  1760.      <blockquote class="fullwidth">
  1761. <div style="text-align:left">
  1762.  <tt>
  1763. X86_CPUID_AMD_FEATURE_EDX_AXMMX is not supported by the host but has already exposed to the guest [ver=19 pass=final] (VERR_SSM_LOAD_CPUID_MISMATCH).
  1764.  </tt>
  1765. </div>
  1766. </blockquote>
  1767.  
  1768.      <p>
  1769. More help from the twins.  The saved state includes information from an <a href="https://en.wikipedia.org/wiki/AMD">AMD</a> processor (<i>hydra</i>), but this is
  1770. Intel.  Discard saved state and start again.
  1771.      </p>
  1772.  
  1773.      <p>
  1774. After that, and with a change of network adapter name, it started.  I got this message,
  1775. which I haven't seen before, but which seems harmless:
  1776.      </p>
  1777.  
  1778.      <blockquote class="fullwidth">
  1779. <div style="text-align:left">
  1780.  <tt>
  1781. error: XDG_RUNTIME_DIR is invalid or not set in the environment.
  1782.  </tt>
  1783. </div>
  1784. </blockquote>
  1785.  
  1786.      <p>
  1787. That variable isn't set on <i>hydra</i> either.
  1788.      </p>
  1789.  
  1790.      <p>
  1791. We're still not done.  Trying to start an <i>xterm</i> from <i>current</i> gave me the
  1792. message
  1793.      </p>
  1794.  
  1795.      <blockquote class="fullwidth">
  1796.        <div class="listitemwidth">
  1797.  The Virtual Machine reports that the guest OS does not support mouse pointer integration
  1798.        </div>
  1799.      </blockquote>
  1800.  
  1801.      <p>
  1802. What's that?  Gemini tells me:
  1803.      </p>
  1804.  
  1805.      <blockquote class="fullwidth">
  1806.        <div class="listitemwidth">
  1807.          The message "The Virtual Machine reports that the guest OS does not support mouse pointer
  1808.          integration..." in a FreeBSD virtual machine is common and means you need to install and
  1809.          configure the necessary guest additions for the mouse to work seamlessly. FreeBSD does not
  1810.          include these drivers out of the box, so you must install them yourself.
  1811.        </div>
  1812.      </blockquote>
  1813.  
  1814.      <p>
  1815. That sounds like the Ports Collection.  But there is no additions package for VirtualBox
  1816. 7.1, only for 6.50 and 5.2.  Mañana.
  1817.      </p>
  1818.  
  1819.      <p>
  1820. On with <i>disaster</i>.  So: ARP issue?  While messing around on <i>disaster</i>, found the
  1821. help message for <i>ARP</i>.  It uses Unix-style option delimiters, and <tt>-s</tt> sets a
  1822. permanent MAC address.  OK, if this is an ARP issue, we can fix that:
  1823.      </p>
  1824.  
  1825.        <a id="Photo-11" name="Photo-11"
  1826.          href="diary-sep2025.php?dirdate=20250905&amp;imagesizes=111111111112#Photo-11">
  1827.          <img alt="This should be Microsoft-networking-1-detail.jpeg.  Is it missing?" border="0" id="Photo_11"
  1828.               title="Photo Microsoft-networking-1-detail.jpeg.  Click to redisplay larger version of image."
  1829.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250905/small/Microsoft-networking-1-detail.jpeg"
  1830.               width="904" height="75"
  1831.           /></a>
  1832.  
  1833.      <p>
  1834. Oh: Microsoft has a different format for MAC addresses.  Try again:
  1835.      </p>
  1836.  
  1837.        <a id="Photo-12" name="Photo-12"
  1838.          href="diary-sep2025.php?dirdate=20250905&amp;imagesizes=1111111111112#Photo-12">
  1839.          <img alt="This should be Microsoft-networking-1-detail-2.jpeg.  Is it missing?" border="0" id="Photo_12"
  1840.               title="Photo Microsoft-networking-1-detail-2.jpeg.  Click to redisplay larger version of image."
  1841.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250905/small/Microsoft-networking-1-detail-2.jpeg"
  1842.               width="913" height="74"
  1843.           /></a>
  1844.  
  1845.      <p>
  1846. And that as <tt>Administrator</tt>.  Time to ask the twins.
  1847.      </p>
  1848.  
  1849.      <blockquote class="fullwidth">
  1850.        <div class="listitemwidth">
  1851.          <b>Q:</b> What does "The ARP entry addition failed: Access is denied" when running CMD as
  1852.          administrator under "windows" 10?
  1853.        </div>
  1854.  
  1855. <div class="listitemwidth">
  1856.  <b>A:</b> The "ARP entry addition failed: Access is denied" error in Windows 10, even when
  1857.  running Command Prompt as an administrator, typically happens when trying to add a static
  1858.  Address Resolution Protocol (ARP) entry for a reason other than a permission issue.
  1859. </div>
  1860.      </blockquote>
  1861.  
  1862.      <p>
  1863. Interesting.  “Access is denied” is <i>not</i> a permission issue?  Something's wrong here,
  1864. either Gemini or Microsoft.  My money is on Microsoft.
  1865.      </p>
  1866.  
  1867.      <p>
  1868. And that's what Gemini suggests too:
  1869.      </p>
  1870.  
  1871.      <blockquote class="fullwidth">
  1872.        <div class="listitemwidth">
  1873.          Use netsh instead: In some cases, especially on newer versions of Windows, the arp command
  1874.          may have issues with Access is denied errors even when the user has administrator
  1875.          privileges.
  1876.        </div>
  1877.      </blockquote>
  1878.  
  1879.      <p>
  1880. So I ended up with this simple invocation:
  1881.      </p>
  1882.  
  1883.        <a id="Photo-13" name="Photo-13"
  1884.          href="diary-sep2025.php?dirdate=20250905&amp;imagesizes=11111111111112#Photo-13">
  1885.          <img alt="This should be Microsoft-networking-2-detail.jpeg.  Is it missing?" border="0" id="Photo_13"
  1886.               title="Photo Microsoft-networking-2-detail.jpeg.  Click to redisplay larger version of image."
  1887.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250905/small/Microsoft-networking-2-detail.jpeg"
  1888.               width="900" height="34.931506849315"
  1889.           /></a>
  1890.  
  1891.      <p>
  1892. And how about that, it worked.  Well, at least it put the address in the ARP table, and I
  1893. was able to ping out, so <i>disaster</i> knew the address.  But it still didn't hear any
  1894. reply.
  1895.      </p>
  1896.  
  1897.      <p>
  1898. Yet another question to Gemini:
  1899.      </p>
  1900.  
  1901.      <blockquote class="fullwidth">
  1902.        <div class="listitemwidth">
  1903.          What could cause a Microsoft guest under VirtualBox to send network data but not receive
  1904.          it, when other guests have no problem with the same configuration?
  1905.        </div>
  1906.      </blockquote>
  1907.  
  1908.      <p>
  1909. The obvious answer: firewall.  Check to be on the safe side.  No, no firewall enabled.  How
  1910. about an Ethernet adapter issue?
  1911.      </p>
  1912.  
  1913.      <blockquote class="fullwidth">
  1914.        <div class="listitemwidth">
  1915.          If you are using an Intel PRO/1000, try switching to a different type, such as the AMD
  1916.          PCnet-FAST III.
  1917.        </div>
  1918.      </blockquote>
  1919.  
  1920.      <p>
  1921. OK, try that.  No improvement.  Next idea: <a href="https://www.youtube.com/watch?v=mk0K88ZkE34">this video</a>      </p>
  1922.  
  1923.      <iframe width="400"
  1924.            height="300"
  1925.            src="http://www.youtube.com/embed/mk0K88ZkE34"
  1926. allowfullscreen
  1927.            frameborder="0" >
  1928.     </iframe>
  1929.  
  1930.      <p>
  1931. OK, try anything once.  Follow the instructions step by step, none of which showed any
  1932. obvious issues.  Change the interface back to (specifically)
  1933. Intel&nbsp;PRO/1000&nbsp;MT&nbsp;Deskop&nbsp;(8254EM).  Not much hope there: that's what I
  1934. had.
  1935.      </p>
  1936.  
  1937.      <p>
  1938. But it worked!  My final configuration looks identical to the start configuration.  What
  1939. changed?  There's something lurking under the surface that I don't understand.  Can I now
  1940. get it to run on <i>hydra</i>?
  1941.      </p>
  1942.      </div>
  1943.    ]]>
  1944.  </description>
  1945.  <dc:creator>Greg Lehey</dc:creator>
  1946.  <dc:date>2025-09-06T01:37:05+00:00</dc:date>
  1947. </item>
  1948.  
  1949.            
  1950. <item>
  1951. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2025.php#D-20250906-025213</guid>
  1952. <link>http://www.lemis.com/grog/diary-sep2025.php#D-20250906-025213</link>
  1953. <category>animals</category>
  1954. <category>general</category>
  1955. <title>Where there's hope...</title>
  1956.  <description>
  1957.    <![CDATA[
  1958.    <div align="justify">
  1959.      <p>
  1960. Horses are social animals, and they hate being alone.  So since <a href="http://www.lemis.com/grog/Albums/Animals/Morena.php">Morena</a> left, <a href="http://www.lemis.com/grog/Albums/Animals/Samba.php">Samba</a> has not been happy.  Today Chris Bahlo
  1961. brought some hope: <a href="http://www.lemis.com/grog/Albums/Animals/Esperanza.php">Esperanza</a>,
  1962.      </p>
  1963.      </div>
  1964.    ]]>
  1965.  </description>
  1966.  <dc:creator>Greg Lehey</dc:creator>
  1967.  <dc:date>2025-09-06T02:52:13+00:00</dc:date>
  1968. </item>
  1969.  
  1970.                  
  1971. <item>
  1972. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2025.php#D-20250907-022018</guid>
  1973. <link>http://www.lemis.com/grog/diary-sep2025.php#D-20250907-022018</link>
  1974. <category>technology</category>
  1975. <category>opinion</category>
  1976. <title>More VirtualBox pain</title>
  1977.  <description>
  1978.    <![CDATA[
  1979.    <div align="justify">
  1980.      <p>
  1981. <a href="http://www.lemis.com/grog/diary-sep2025.php?subtitle=VirtualBox%20progress&amp;article=D-20250906-013705#D-20250906-013705">Yesterday</a> I finally got networking working using <a href="https://en.wikipedia.org/wiki/VirtualBox">VirtualBox</a> 7.1 and Microsoft <a href="http://www.lemis.com/grog/Rant/windows.php">“Windows”</a> 10.  Time to refine a few things.  First, start the
  1982. windows on <i>hydra:0.0</i>, a 1920×1080 display, rather than on <i>hydra:0.1</i>, which has
  1983. 3840×2160, giving windows that are too small.
  1984.      </p>
  1985.  
  1986.      <p>
  1987. But it didn't work!  I could start on <i>hydra:0.1</i>, but on <i>hydra:0.0</i> nothing
  1988. happened.  Is there some kind of built-in memory in the configuration file?
  1989.      </p>
  1990.  
  1991.      <p>
  1992. So, time to upgrade <i>current.lemis.com</i>, another VM running <a href="https://www.freebsd.org/">FreeBSD</a>-CURRENT.  It was a year out of date.
  1993.      </p>
  1994.  
  1995.      <p>
  1996. Start a <tt>make&nbsp;buildworld</tt>, not for the first time.  But nothing happened!
  1997.      </p>
  1998.  
  1999.      <p>
  2000. Further investigation showed that I had a network hang.  And <i>disaster</i> was also
  2001. hanging!  Shut down <i>disaster</i> and <i>current</i> regained network access—for a while.
  2002. Then it hung again.
  2003.      </p>
  2004.  
  2005.      <p>
  2006. This seems worse than my experience on <i>hydra</i> with VirtualBox 6.5.  Tried it there and
  2007. it worked.
  2008.      </p>
  2009.  
  2010.      <p>
  2011. What a pain!  What does <a href="https://gemini.google.com/">Google Gemini</a> say?
  2012.      </p>
  2013.  
  2014.      <blockquote>
  2015. <p class="listitemwidth">
  2016.  <b>Q:</b> Are there known networking issues with VirtualBox under FreeBSD?
  2017. </p>
  2018.  
  2019. <p class="listitemwidth">
  2020.  <b>A:</b> Yes, there are known networking issues and quirks with VirtualBox when used as a
  2021.  host on a FreeBSD system. While VirtualBox works, it is not an officially "supported" host
  2022.  platform by Oracle, which means users often have to rely on the community and package
  2023.  maintainers to troubleshoot and resolve issues.
  2024.  </p>
  2025.  
  2026. <p class="listitemwidth">
  2027.  <i>(much irrelevant information omitted)</i>
  2028. </p>
  2029.  
  2030. <p class="listitemwidth">
  2031.  Users sometimes experience slow network speeds, particularly with upload speeds, when
  2032.  using bridged adapters. This can be more pronounced on specific emulated network card
  2033.  types.
  2034. </p>
  2035.  
  2036. <p class="listitemwidth">
  2037.  While VirtualBox can function as a host on FreeBSD, it is not a "fire-and-forget"
  2038.  solution...  If you encounter speed or reliability issues, experimenting with different
  2039.  emulated network adapter types can often resolve the problem.
  2040. </p>
  2041.      </blockquote>
  2042.  
  2043.      <p>
  2044. That's not encouraging, though it doesn't directly relate to my problems.  But what else can
  2045. it be?  Two different versions of FreeBSD, two different machines, two different versions of
  2046. VirtualBox.  Does it work better on Linux?  That would be a real let-down, but possibly I
  2047. should try it.  How much pain would that be?
  2048.      </p>
  2049.      </div>
  2050.    ]]>
  2051.  </description>
  2052.  <dc:creator>Greg Lehey</dc:creator>
  2053.  <dc:date>2025-09-07T02:20:18+00:00</dc:date>
  2054. </item>
  2055.  
  2056.            
  2057. <item>
  2058. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2025.php#D-20250907-022327</guid>
  2059. <link>http://www.lemis.com/grog/diary-sep2025.php#D-20250907-022327</link>
  2060. <category>politics</category>
  2061. <category>food</category>
  2062. <category>and</category>
  2063. <category>drink</category>
  2064. <category>opinion</category>
  2065. <title>Thank you, Darn old Trump</title>
  2066.  <description>
  2067.    <![CDATA[
  2068.    <div align="justify">
  2069.      <p>
  2070. <a href="http://www.lemis.com/yvonne/">Yvonne</a> bought some asparagus on Wednesday, which I processed
  2071. as Chinese-style <a href="http://www.lemis.com/grog/recipes/asparagus-and-prawns.php">asparagus and prawns</a>.  The most interesting thing is the provenance: made in <a href="https://en.wikipedia.org/wiki/México">México</a>, at the other end of the world.  Why
  2072. are they on sale here?
  2073.      </p>
  2074.  
  2075.      <p>
  2076. The answer is obvious: they have lost one of their main markets, the <a href="https://en.wikipedia.org/wiki/USA">USA</a>.  So they have to sell elsewhere.
  2077. Presumably the US Americans are suffering a lack of asparagus to add to their problems.
  2078.      </p>
  2079.      </div>
  2080.    ]]>
  2081.  </description>
  2082.  <dc:creator>Greg Lehey</dc:creator>
  2083.  <dc:date>2025-09-07T02:23:27+00:00</dc:date>
  2084. </item>
  2085.  
  2086.                  
  2087. <item>
  2088. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2025.php#D-20250908-012811</guid>
  2089. <link>http://www.lemis.com/grog/diary-sep2025.php#D-20250908-012811</link>
  2090. <category>gardening</category>
  2091. <category>opinion</category>
  2092. <title>Incredible dying Abutilon</title>
  2093.  <description>
  2094.    <![CDATA[
  2095.    <div align="justify">
  2096.      <p>
  2097. <a href="http://www.lemis.com/grog/diary-jun2025.php?subtitle=Tidying%20up%20the%20garden&amp;article=D-20250621-020843#D-20250621-020843">A couple of months ago</a> I was having trouble with the <a href="https://en.wikipedia.org/wiki/Abutilon">Abutilon</a> by the laundry door:
  2098.      </p>
  2099.  
  2100.        <a id="Photo-14" name="Photo-14"
  2101.          href="diary-sep2025.php?dirdate=20250515&amp;imagesizes=111111111111112#Photo-14">
  2102.          <img alt="This should be Abutilon-1.jpeg.  Is it missing?" border="0" id="Photo_14"
  2103.               title="Photo Abutilon-1.jpeg.  Click to redisplay larger version of image."
  2104.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250515/small/Abutilon-1.jpeg"
  2105.               width="301" height="224"
  2106.           /></a>
  2107.        <a id="Photo-15" name="Photo-15"
  2108.          href="diary-sep2025.php?dirdate=20250515&amp;imagesizes=1111111111111112#Photo-15">
  2109.          <img alt="This should be Abutilon-2.jpeg.  Is it missing?" border="0" id="Photo_15"
  2110.               title="Photo Abutilon-2.jpeg.  Click to redisplay larger version of image."
  2111.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250515/small/Abutilon-2.jpeg"
  2112.               width="300" height="225"
  2113.           /></a>
  2114.  
  2115.      <p>
  2116. Jesse Walsh removed a branch and discovered mould around it:
  2117.      </p>
  2118.  
  2119.        <a id="Photo-16" name="Photo-16"
  2120.          href="diary-sep2025.php?dirdate=20250620&amp;imagesizes=11111111111111112#Photo-16">
  2121.          <img alt="This should be Abutilon-mould-2.jpeg.  Is it missing?" border="0" id="Photo_16"
  2122.               title="Photo Abutilon-mould-2.jpeg.  Click to redisplay larger version of image."
  2123.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250620/small/Abutilon-mould-2.jpeg"
  2124.               width="300" height="225"
  2125.           /></a>
  2126.  
  2127.      <p>
  2128. That seemed to fix the problem.  Until now:
  2129.      </p>
  2130.  
  2131.        <a id="Photo-17" name="Photo-17"
  2132.          href="diary-sep2025.php?dirdate=20250907&amp;imagesizes=111111111111111112#Photo-17">
  2133.          <img alt="This should be Sick-Abutilon-2.jpeg.  Is it missing?" border="0" id="Photo_17"
  2134.               title="Photo Sick-Abutilon-2.jpeg.  Click to redisplay larger version of image."
  2135.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250907/small/Sick-Abutilon-2.jpeg"
  2136.               width="300" height="225"
  2137.           /></a>
  2138.  
  2139.      <p>
  2140. What's causing that?  This time it was clearer that a whole branch was affected, down to
  2141. this joint
  2142.      </p>
  2143.  
  2144.        <a id="Photo-18" name="Photo-18"
  2145.          href="diary-sep2025.php?dirdate=20250907&amp;imagesizes=1111111111111111112#Photo-18">
  2146.          <img alt="This should be Sick-Abutilon-3.jpeg.  Is it missing?" border="0" id="Photo_18"
  2147.               title="Photo Sick-Abutilon-3.jpeg.  Click to redisplay larger version of image."
  2148.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250907/small/Sick-Abutilon-3.jpeg"
  2149.               width="300" height="225"
  2150.           /></a>
  2151.  
  2152.      <p>
  2153. The sick branch is on the left.  And there's a section that appears to have dried out.  Is
  2154. this some kind of disease?
  2155.      </p>
  2156.  
  2157.      <p>
  2158. Clearly the branch will have to go.  And the whole bush?  It wouldn't be the biggest
  2159. disaster: this one is much bigger than I had expected, we have another one on <a href="http://www.lemis.com/grog/Albums/Animals/Piccola.php">Piccola's</a> grave, and they're easy to propagate.
  2160.      </p>
  2161.      </div>
  2162.    ]]>
  2163.  </description>
  2164.  <dc:creator>Greg Lehey</dc:creator>
  2165.  <dc:date>2025-09-08T01:28:11+00:00</dc:date>
  2166. </item>
  2167.  
  2168.            
  2169. <item>
  2170. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2025.php#D-20250908-013132</guid>
  2171. <link>http://www.lemis.com/grog/diary-sep2025.php#D-20250908-013132</link>
  2172. <category>animals</category>
  2173. <category>photography</category>
  2174. <category>opinion</category>
  2175. <title>More kangaroos and horses</title>
  2176.  <description>
  2177.    <![CDATA[
  2178.    <div align="justify">
  2179.      <p>
  2180. <a href="http://www.lemis.com/grog/diary-aug2018.php?subtitle=More%20kangaroos&amp;article=D-20180815-023551#D-20180815-023551">Seven years ago</a> I found a mob of kangaroos with the horses in the west paddock and
  2181. spent a lot of time processing photos, which proved to include two kangaroos with <a href="https://en.wikipedia.org/wiki/Joey_(marsupial)">joeys</a>:
  2182.      </p>
  2183.  
  2184.        <a id="Photo-19" name="Photo-19"
  2185.          href="diary-sep2025.php?dirdate=20180814&amp;imagesizes=11111111111111111112#Photo-19">
  2186.          <img alt="This should be Kangaroos-52-detail-2.jpeg.  Is it missing?" border="0" id="Photo_19"
  2187.               title="Photo Kangaroos-52-detail-2.jpeg.  Click to redisplay larger version of image."
  2188.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20180814/small/Kangaroos-52-detail-2.jpeg"
  2189.               width="310" height="217"
  2190.           /></a>
  2191.  
  2192.      <p>
  2193. Today <a href="http://www.lemis.com/yvonne/">Yvonne</a> saw something similar:
  2194.      </p>
  2195.  
  2196.        <a id="Photo-20" name="Photo-20"
  2197.          href="diary-sep2025.php?dirdate=20250907&amp;imagesizes=111111111111111111112#Photo-20">
  2198.          <img alt="This should be Horses-and-roos-1.jpeg.  Is it missing?" border="0" id="Photo_20"
  2199.               title="Photo Horses-and-roos-1.jpeg.  Click to redisplay larger version of image."
  2200.               src="https://lemis.nyc3.digitaloceanspaces.com/yvonne/Photos/20250907/small/Horses-and-roos-1.jpeg"
  2201.               width="375" height="180"
  2202.           /></a>
  2203.  
  2204.      <p>
  2205. This time, though, a very large joey is trying to get in the pouch of the kangaroo in the
  2206. middle:
  2207.      </p>
  2208.  
  2209.      <div align="left">
  2210.  <a id="Photo-21" name="Photo-21"
  2211.          href="diary-sep2025.php?dirdate=20250907&amp;imagesizes=1111111111111111111112#Photo-21">
  2212.          <img alt="This should be Kangaroos-and-horses-7.jpeg.  Is it missing?" border="0" id="Photo_21"
  2213.               title="Photo Kangaroos-and-horses-7.jpeg.  Click to redisplay larger version of image."
  2214.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250907/small/Kangaroos-and-horses-7.jpeg"
  2215.               width="281" height="240"
  2216.           /></a>
  2217.  <a id="Photo-22" name="Photo-22"
  2218.          href="diary-sep2025.php?dirdate=20250907&amp;imagesizes=11111111111111111111112#Photo-22">
  2219.          <img alt="This should be Kangaroos-and-horses-8.jpeg.  Is it missing?" border="0" id="Photo_22"
  2220.               title="Photo Kangaroos-and-horses-8.jpeg.  Click to redisplay larger version of image."
  2221.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250907/small/Kangaroos-and-horses-8.jpeg"
  2222.               width="250" height="270"
  2223.           /></a>
  2224.  <a id="Photo-23" name="Photo-23"
  2225.          href="diary-sep2025.php?dirdate=20250907&amp;imagesizes=111111111111111111111112#Photo-23">
  2226.          <img alt="This should be Kangaroos-and-horses-10.jpeg.  Is it missing?" border="0" id="Photo_23"
  2227.               title="Photo Kangaroos-and-horses-10.jpeg.  Click to redisplay larger version of image."
  2228.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250907/small/Kangaroos-and-horses-10.jpeg"
  2229.               width="301" height="224"
  2230.           /></a>
  2231.  <a id="Photo-24" name="Photo-24"
  2232.          href="diary-sep2025.php?dirdate=20250907&amp;imagesizes=1111111111111111111111112#Photo-24">
  2233.          <img alt="This should be Kangaroos-and-horses-11.jpeg.  Is it missing?" border="0" id="Photo_24"
  2234.               title="Photo Kangaroos-and-horses-11.jpeg.  Click to redisplay larger version of image."
  2235.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250907/small/Kangaroos-and-horses-11.jpeg"
  2236.               width="203" height="331"
  2237.           /></a>
  2238.      </div>
  2239.  
  2240.      <p>
  2241. I wonder whether it's typical that the kangaroo lies down to let the joey in.
  2242.      </p>
  2243.  
  2244.      <p>
  2245. And why are these images so fuzzy?  They're taken with a relatively poor lens, the images
  2246. are heavily cropped (corresponding to focal lengths round 2,500 mm for a “full frame”
  2247. camera), but the horses aren't (quite) that fuzzy.  Depth of field?  My calculator tells me
  2248. that it's round 200 m.  But clearly a longer lens would have been helpful.  And could maybe
  2249. some “AI” processing software improve things?
  2250.      </p>
  2251.      </div>
  2252.    ]]>
  2253.  </description>
  2254.  <dc:creator>Greg Lehey</dc:creator>
  2255.  <dc:date>2025-09-08T01:31:32+00:00</dc:date>
  2256. </item>
  2257.  
  2258.            
  2259. <item>
  2260. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2025.php#D-20250908-030531</guid>
  2261. <link>http://www.lemis.com/grog/diary-sep2025.php#D-20250908-030531</link>
  2262. <category>technology</category>
  2263. <title>Testing RSS feeds</title>
  2264.  <description>
  2265.    <![CDATA[
  2266.    <div align="justify">
  2267.      <p>
  2268. I write all my web markup myself, with the aid of a number of <a href="https://en.wikipedia.org/wiki/PHP">PHP</a> scripts.  The result is that the <a href="https://en.wikipedia.org/wiki/RSS">RSS feed</a> looks nothing much like my sources.
  2269. So when something goes wrong with the markup, it's hard to find where, not helped by things
  2270. like the <a href="https://validator.w3.org/feed/check.cgi?url=http%3A%2F%2Fwww.lemis.com%2Fgrog%2Fdiary.xml.php">W3.org validator</a>, which typically points to where the error is detected, not where it
  2271. occurred, and which at the moment caches input, so even after fixing the problem it reports
  2272. the old problem.
  2273.      </p>
  2274.  
  2275.      <p>
  2276. Callum Gibson is the main user of RSS feeds whom I know of.  He pointed me to <a href="https://codebeautify.org/xmlvalidator">this validator</a>.  It also points to where
  2277. the error was found, but at least I can try things and repeat them.  That fixed an issue I
  2278. had with earlier this month, where the error was over 100 lines from where it was detected.
  2279.      </p>
  2280.      </div>
  2281.    ]]>
  2282.  </description>
  2283.  <dc:creator>Greg Lehey</dc:creator>
  2284.  <dc:date>2025-09-08T03:05:31+00:00</dc:date>
  2285. </item>
  2286.  
  2287.                  
  2288. <item>
  2289. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2025.php#D-20250908-235445</guid>
  2290. <link>http://www.lemis.com/grog/diary-sep2025.php#D-20250908-235445</link>
  2291. <category>technology</category>
  2292. <title>Chasing the VirtualBox bug</title>
  2293.  <description>
  2294.    <![CDATA[
  2295.    <div align="justify">
  2296.      <p>
  2297. So why was <a href="https://en.wikipedia.org/wiki/VirtualBox">VirtualBox</a> version
  2298. 7.1 on <i>dereel</i> even worse than version 6.50 on <i>hydra</i>?  One possibility might be
  2299. that the VMs themselves were <a href="https://en.wikipedia.org/wiki/Network_File_System">NFS</a> mounted.  OK, find a 1 TB
  2300. disk and copy them there.  Put it in in place of the <a href="https://en.wikipedia.org/wiki/DVD">DVD</a> drive, and was amazed to find that it came
  2301. up as <i>/dev/ada0</i>, relegating the system disk to <i>/dev/ada1</i> and requiring manual
  2302. intervention (<i>/etc/fstab</i>) to continue.  How could that happen?
  2303.      </p>
  2304.  
  2305.      <p>
  2306. Then copying the VMs from <i>hydra</i>.  That took a few hours, of course, so I'll continue
  2307. tomorrow.
  2308.      </p>
  2309.  
  2310.      <p>
  2311. While looking for the disks also found one marked “MS “Windows” 10 disgust”, dated
  2312. <a href="http://www.lemis.com/grog/diary-dec2020.php#10">10.XII.2020</a>.  Comparing with <a href="http://www.lemis.com/grog/diary-dec2020.php?subtitle=New%20ThinkCentre&amp;article=D-20201212-013434#D-20201212-013434">my diary</a>, that proves to be the disk that came with the machine I'm working on.  So I
  2313. should be able to just put it in and run it.  That's the next thing to do if I still can't
  2314. get VirtualBox to run reliably.
  2315.      </p>
  2316.      </div>
  2317.    ]]>
  2318.  </description>
  2319.  <dc:creator>Greg Lehey</dc:creator>
  2320.  <dc:date>2025-09-08T23:54:45+00:00</dc:date>
  2321. </item>
  2322.  
  2323.            
  2324. <item>
  2325. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2025.php#D-20250909-003710</guid>
  2326. <link>http://www.lemis.com/grog/diary-sep2025.php#D-20250909-003710</link>
  2327. <category>photography</category>
  2328. <category>technology</category>
  2329. <category>opinion</category>
  2330. <title>DxO PhotoLab 9: worth the trouble?</title>
  2331.  <description>
  2332.    <![CDATA[
  2333.    <div align="justify">
  2334.      <p>
  2335. I've spent a lot of time looking at the new features of <a href="https://www.dxo.com/dxo-photolab/">DxO PhotoLab</a> 9.  Even better noise reduction,
  2336. of course, but the big new thing is what appears to be excellent object recognition
  2337. (“masking”).  But that's only part of the story.  Can I remove objects?  Replace them with
  2338. something else?  It seems that the answer is “no”.
  2339.      </p>
  2340.  
  2341.      <p>
  2342. Somewhere I also thought I saw a way to merge <a href="https://en.wikipedia.org/wiki/High-dynamic-range_imaging">HDR</a> images, but that
  2343. seems to be a misunderstanding.  Instead they have improved file handling, including
  2344. collapsing related image groups and automatic file naming.  None of them seem to be anywhere
  2345. near as flexible as the method I worked out <a href="http://www.lemis.com/grog/diary-feb2012.php?subtitle=Setting%20names%20for%20photos&amp;article=D-20120212-230004#D-20120212-230004">13 years ago</a>, so it's of no use to me.
  2346.      </p>
  2347.  
  2348.      <p>
  2349. So: what will the future bring?  The masking is good, but is it enough to spend US $240 on?
  2350. There's a very good chance that they'll come up with a version 10 in the not-too-distant
  2351. future and want $120 for an upgrade.  Maybe I should just wait.
  2352.      </p>
  2353.      </div>
  2354.    ]]>
  2355.  </description>
  2356.  <dc:creator>Greg Lehey</dc:creator>
  2357.  <dc:date>2025-09-09T00:37:10+00:00</dc:date>
  2358. </item>
  2359.  
  2360.            
  2361. <item>
  2362. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2025.php#D-20250909-004539</guid>
  2363. <link>http://www.lemis.com/grog/diary-sep2025.php#D-20250909-004539</link>
  2364. <category>general</category>
  2365. <category>technology</category>
  2366. <category>opinion</category>
  2367. <title>VicRoads: still in the 20th century</title>
  2368.  <description>
  2369.    <![CDATA[
  2370.    <div align="justify">
  2371.      <p>
  2372. After scrapping my <a href="https://en.wikipedia.org/wiki/Hyundai_Elantra">Hyundai
  2373. Elantra</a> <a href="http://www.lemis.com/grog/diary-jul2025.php?subtitle=Goodbye%20Elantra&amp;article=D-20250731-014519#D-20250731-014519">at the end of July</a> I was due a refund for the registration.
  2374.      </p>
  2375.  
  2376.      <p>
  2377. And they sent me a cheque!  I thought they went out of fashion <a href="http://www.lemis.com/grog/diary-may2024.php?subtitle=No%20more%20cheque%20books&amp;article=D-20240503-015343#D-20240503-015343">well over a year ago</a>.  And yes, the bank refused to accept it.
  2378.      </p>
  2379.  
  2380.      <p>
  2381. But why?  I really don't understand.  They should have transferred it to my bank account,
  2382. like any sane company.  But no, I had to call their customer service line (1300 555 165,
  2383. which looks suspiciously like a fake US phone number) and go through their silly
  2384. authentication process (including a form of 2FA, sending a PIN to my phone.  That would have
  2385. helped a lot if I had been calling from that phone).  But yes, relatively quickly they took
  2386. the details and told me that the transfer would occur in the next 2 to 3 weeks.  Receipt
  2387. number HD1155831.
  2388.      </p>
  2389.  
  2390.      <p>
  2391. 2 to 3 <i>weeks</i>?  Why?  Ah, we need human intervention.  Why?  Nowadays we have
  2392. computers.  With only marginally good programming the money could have been in my bank
  2393. account before the end of the call.  But clearly they don't have that.
  2394.      </p>
  2395.      </div>
  2396.    ]]>
  2397.  </description>
  2398.  <dc:creator>Greg Lehey</dc:creator>
  2399.  <dc:date>2025-09-09T00:45:39+00:00</dc:date>
  2400. </item>
  2401.  
  2402.            
  2403. <item>
  2404. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2025.php#D-20250909-010021</guid>
  2405. <link>http://www.lemis.com/grog/diary-sep2025.php#D-20250909-010021</link>
  2406. <category>general</category>
  2407. <title>Dry winter</title>
  2408.  <description>
  2409.    <![CDATA[
  2410.    <div align="justify">
  2411.      <p>
  2412. It has been raining more lately—we've had 60 mm in the last 2 weeks—but it's still not
  2413. enough.  Here the neighbour's dam:
  2414.      </p>
  2415.  
  2416.        <a id="Photo-25" name="Photo-25"
  2417.          href="diary-sep2025.php?dirdate=20250908&amp;imagesizes=11111111111111111111111112#Photo-25">
  2418.          <img alt="This should be Dam-level.jpeg.  Is it missing?" border="0" id="Photo_25"
  2419.               title="Photo Dam-level.jpeg.  Click to redisplay larger version of image."
  2420.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250908/small/Dam-level.jpeg"
  2421.               width="300" height="224"
  2422.           /></a>
  2423.  
  2424.      <p>
  2425. Hopefully it will fill up before summer.
  2426.      </p>
  2427.      </div>
  2428.    ]]>
  2429.  </description>
  2430.  <dc:creator>Greg Lehey</dc:creator>
  2431.  <dc:date>2025-09-09T01:00:21+00:00</dc:date>
  2432. </item>
  2433.  
  2434.                  
  2435. <item>
  2436. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2025.php#D-20250910-024351</guid>
  2437. <link>http://www.lemis.com/grog/diary-sep2025.php#D-20250910-024351</link>
  2438. <category>technology</category>
  2439. <category>opinion</category>
  2440. <title>More VirtualBox insights</title>
  2441.  <description>
  2442.    <![CDATA[
  2443.    <div align="justify">
  2444.      <p>
  2445. So what's wrong with <a href="https://en.wikipedia.org/wiki/VirtualBox">VirtualBox</a> networking?  <a href="https://gemini.google.com/">Google Gemini</a> had suggested
  2446. that it might depend on the emulated network adapter, so spent some time trying different
  2447. adapters, with no improvement.  About the only thing that was clear was the ping time: from
  2448. guest to host the expected 0.15 ms, but in the other direction <i>much</i> longer, and with
  2449. wildly different times:
  2450.      </p>
  2451.  
  2452.      <blockquote class="fullwidth">
  2453. <div style="text-align:left">
  2454.  <tt>
  2455. round&#45;trip min/avg/max/stddev = 29.752/61.679/175.892/36.953 ms
  2456.  </tt>
  2457. </div>
  2458. </blockquote>
  2459.  
  2460.      <p>
  2461. Gave that up and looked at some bug reports, which showed surprisingly few network issues.
  2462. But <a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256413">one</a>, by
  2463. Ivan Rozhuk, was interesting:
  2464.      </p>
  2465.  
  2466. <blockquote class="fullwidth">
  2467. <div style="text-align:left">
  2468.  <tt>
  2469. Try to disable HW offloads on NIC:
  2470. <br />ifconfig igb0 &#45;rxcsum &#45;txcsum &#45;vlanhwtso &#45;lro &#45;tso4 &#45;tso6 down up
  2471. <br />
  2472.  </tt>
  2473. </div>
  2474. </blockquote>
  2475.  
  2476.      <p>
  2477. And how about that, that worked.  So why is this not better known?  There's also a
  2478. <a href="http://wiki.freebsd.org/VirtualBox">wiki</a> with surprisingly little of
  2479. use.
  2480.      </p>
  2481.  
  2482.      <p>
  2483. Later I discovered that my guest <i>current.lemis.com</i> had 8 CPUs, while the
  2484. host <i>dereel</i> only has four.  That's quite impressive that it worked at all.  Reducing
  2485. the number of CPUs on <i>current</i> got rid of the slow ping times.
  2486.      </p>
  2487.  
  2488.      <p>
  2489. So: are we done?  I don't think so.  I still need to find whether the Microsoft guests work
  2490. reliably.
  2491.      </p>
  2492.      </div>
  2493.    ]]>
  2494.  </description>
  2495.  <dc:creator>Greg Lehey</dc:creator>
  2496.  <dc:date>2025-09-10T02:43:51+00:00</dc:date>
  2497. </item>
  2498.  
  2499.            
  2500. <item>
  2501. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2025.php#D-20250910-030336</guid>
  2502. <link>http://www.lemis.com/grog/diary-sep2025.php#D-20250910-030336</link>
  2503. <category>technology</category>
  2504. <category>opinion</category>
  2505. <title>Bruce Evans' C compiler</title>
  2506.  <description>
  2507.    <![CDATA[
  2508.    <div align="justify">
  2509.      <p>
  2510. Mail in the <a href="http://www.tuhs.org/pipermail/tuhs/">TUHS mailing list</a> today:
  2511.      </p>
  2512.  
  2513.      <blockquote class="fullwidth">
  2514. <div style="text-align:left">
  2515.  <tt>
  2516. Subject: [TUHS] Bruce Evans 386 Minix patches &amp; compiler source
  2517. <br />
  2518. <br />It's been quite a while since I was messing with Minix386 back in the days
  2519. <br />when Bruce Evans released a set of patches to bring 386 support.
  2520. <br />I'm pretty sure over on oldlinux.org the patch set exists, but I can only
  2521. <br />find the one set of binaries of his 386 toolchain.
  2522. <br />I know it eventually evolved into the bin86 toolchain that Linus would go on
  2523. <br />to use to create real mode boot code, but I don't know if any of the source
  2524. <br />code to his 1991/1992 386 toolchain ever got published?
  2525. <br />
  2526.  </tt>
  2527. </div>
  2528. </blockquote>
  2529.  
  2530.      <p>
  2531. Is it somewhere on the disk images that Peter Jeremy saved?  I haven't looked at them for
  2532. <a href="http://www.lemis.com/grog/diary-may2022.php#D-20220512-034628">over three years</a>, and I
  2533. only had the smaller ones that I could download.  Sent off a message to the other people who
  2534. have access, Warren Toomey (who also coincidentally runs TUHS) and Warner Losh, and only got
  2535. a brief response from the first.
  2536.      </p>
  2537.  
  2538.      <p>
  2539. Back to look at what I have: three files, <i>/src/bde/ad1.img</i>, <i>/src/bde/ad2.img</i>
  2540. and <i>/src/bde/ad3.img</i>.  I had only looked at <i>/ad0.img</i>, requiring <a href="https://www.freebsd.org/cgi/man.cgi?query=gnop&amp;sektion=&amp;n=1"><i>gnop</i></a> to access
  2541. the individual partitions.  There was a good reason: I had renamed <i>ad2.img.xz</i>
  2542. to <i>ad2.img</i> without uncompressing it.  Did that now and ended up with 60&nbsp;GB of
  2543. data.
  2544.      </p>
  2545.  
  2546.      <p>
  2547. And the contents?
  2548.      </p>
  2549.  
  2550.      <blockquote class="fullwidth">
  2551. <div style="text-align:left">
  2552.  <tt>
  2553. <code><font color="blue">=== root@dereel (/dev/pts/1)</font> <font color="red">/bde</font> <font color="blue">13</font> &#45;&gt; <b><tt>mdconfig &#45;a &#45;t vnode &#45;f /src/bde/besplex/ad2.img</tt></b></code>
  2554. <br />md0
  2555. <br /><code><font color="blue">=== root@dereel (/dev/pts/1)</font> <font color="red">/bde</font> <font color="blue">14</font> &#45;&gt; <b><tt>l /dev/md0</tt></b></code>
  2556. <br />md0 &nbsp; &nbsp; md0s1 &nbsp; md0s2 &nbsp; md0s2a &nbsp;md0s2b &nbsp;md0s2d &nbsp;md0s2e &nbsp;md0s2f &nbsp;md0s2g &nbsp;md0s2h
  2557. <br />
  2558.  </tt>
  2559. </div>
  2560. </blockquote>
  2561.  
  2562.      <p>
  2563. All the BSD partitions there!  So I can just mount them:
  2564.      </p>
  2565.  
  2566.      <blockquote class="fullwidth">
  2567. <div style="text-align:left">
  2568.  <tt>
  2569. <code><font color="blue">=== root@dereel (/dev/pts/1)</font> <font color="red">/bde</font> <font color="blue">15</font> &#45;&gt; <b><tt>mkdir a b d e f g h</tt></b></code>
  2570. <br /><code><font color="blue">=== root@dereel (/dev/pts/1)</font> <font color="red">/bde</font> <font color="blue">16</font> &#45;&gt; <b><tt>l</tt></b></code>
  2571. <br />total 1
  2572. <br />drwxr&#45;xr&#45;x &nbsp;2 root wheel 512 10 Sep 13:28 a
  2573. <br />drwxr&#45;xr&#45;x &nbsp;2 root wheel 512 10 Sep 13:28 b
  2574. <br />drwxr&#45;xr&#45;x &nbsp;2 root wheel 512 10 Sep 13:28 d
  2575. <br />drwxr&#45;xr&#45;x &nbsp;2 root wheel 512 10 Sep 13:28 e
  2576. <br />drwxr&#45;xr&#45;x &nbsp;2 root wheel 512 10 Sep 13:28 f
  2577. <br />drwxr&#45;xr&#45;x &nbsp;2 root wheel 512 10 Sep 13:28 g
  2578. <br />drwxr&#45;xr&#45;x &nbsp;2 root wheel 512 10 Sep 13:28 h
  2579. <br /><code><font color="blue">=== root@dereel (/dev/pts/1)</font> <font color="red">/bde</font> <font color="blue">35</font> &#45;&gt; <b><tt>for i in &nbsp;`echo a b d e f g h`; do mount &#45;o ro /dev/md0s2$i $i; done</tt></b></code>
  2580. <br />mount: /dev/md0s2a: No such file or directory
  2581. <br /><code><font color="blue">=== root@dereel (/dev/pts/1)</font> <font color="red">/bde</font> <font color="blue">36</font> &#45;&gt; <b><tt>df</tt></b></code>
  2582. <br />Filesystem &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;1048576&#45;blocks &nbsp; &nbsp; &nbsp;Used &nbsp; &nbsp; Avail Capacity &nbsp;Mounted on
  2583. <br />...
  2584. <br />/dev/md0s2b &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3,952 &nbsp; &nbsp; 3,542 &nbsp; &nbsp; &nbsp; &nbsp;93 &nbsp; &nbsp;97% &nbsp; &nbsp;/bde/b
  2585. <br />/dev/md0s2d &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3,952 &nbsp; &nbsp; 2,971 &nbsp; &nbsp; &nbsp; 664 &nbsp; &nbsp;82% &nbsp; &nbsp;/bde/d
  2586. <br />/dev/md0s2e &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3,952 &nbsp; &nbsp; 3,658 &nbsp; &nbsp; &nbsp; &#45;21 &nbsp; 101% &nbsp; &nbsp;/bde/e
  2587. <br />/dev/md0s2f &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3,952 &nbsp; &nbsp; 3,514 &nbsp; &nbsp; &nbsp; 121 &nbsp; &nbsp;97% &nbsp; &nbsp;/bde/f
  2588. <br />/dev/md0s2g &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 11,754 &nbsp; &nbsp; 8,842 &nbsp; &nbsp; 1,972 &nbsp; &nbsp;82% &nbsp; &nbsp;/bde/g
  2589. <br />/dev/md0s2h &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 29,525 &nbsp; &nbsp;14,599 &nbsp; &nbsp;14,926 &nbsp; &nbsp;49% &nbsp; &nbsp;/bde/h
  2590. <br /><code><font color="blue">=== root@dereel (/dev/pts/1)</font> <font color="red">/bde</font> <font color="blue">37</font> &#45;&gt; <b><tt></tt></b></code>
  2591. <br />
  2592.  </tt>
  2593. </div>
  2594. </blockquote>
  2595.  
  2596.      <p>
  2597. And in one of the partitions I found a
  2598. file <i>/bde/e/besplex/home/bde/dist/minix.tar.gz</i>, which may be just what Jason is
  2599. looking for.  That was much easier than I thought.  Is it correct?  That would be too easy.
  2600.      </p>
  2601.      </div>
  2602.    ]]>
  2603.  </description>
  2604.  <dc:creator>Greg Lehey</dc:creator>
  2605.  <dc:date>2025-09-10T03:03:36+00:00</dc:date>
  2606. </item>
  2607.  
  2608.                  
  2609. <item>
  2610. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2025.php#D-20250911-015021</guid>
  2611. <link>http://www.lemis.com/grog/diary-sep2025.php#D-20250911-015021</link>
  2612. <category>health</category>
  2613. <category>politics</category>
  2614. <category>opinion</category>
  2615. <title>Israel makes me sick</title>
  2616.  <description>
  2617.    <![CDATA[
  2618.    <div align="justify">
  2619.      <p>
  2620. During morning ablutions I discovered that <a href="https://en.wikipedia.org/wiki/Israel">Israel</a> has <a href="https://www.abc.net.au/news/2025-09-10/live-coverage-israel-strikes-hamas-leadership-in-qatar/105755776">attacked a site</a> in <a href="https://en.wikipedia.org/wiki/Qatar">Qatar</a>,
  2621. in violation of international law.  Even the <a href="https://en.wikipedia.org/wiki/USA">USA</a> is unhappy: Qatar is an ally.  The news
  2622. media talk of <a href="https://www.abc.net.au/news/2025-09-10/israel-hit-on-hamas-in-qatar-and-trump-response/105756948">Trump's impotence</a> in stopping these attacks.  But they don't mention the obvious way
  2623. to solve the issue: stop supplying Israel with weapons.  By comparison, the current Russian
  2624. attacks on <a href="https://en.wikipedia.org/wiki/Ukraine">Ukraine</a> and even
  2625. <a href="https://en.wikipedia.org/wiki/Poland">Poland</a> seem like nothing.
  2626.      </p>
  2627.  
  2628.      <p>
  2629. This really worries me.  I felt physically sick all day, somehow uncoordinated, dizzy,
  2630. unable to walk properly and and even unable to type normally.  It could be something else,
  2631. of course, but somehow it all started when I heard of Israel's attack.  Once again I'm
  2632. reminded of what I wrote <a href="http://www.lemis.com/grog/diary-jan2025.php#D-20250127-011034">earlier this year</a>: Israel is a state sponsor of antisemitism.  Once I strongly
  2633. supported Israel.
  2634.      </p>
  2635.      </div>
  2636.    ]]>
  2637.  </description>
  2638.  <dc:creator>Greg Lehey</dc:creator>
  2639.  <dc:date>2025-09-11T01:50:21+00:00</dc:date>
  2640. </item>
  2641.  
  2642.            
  2643. <item>
  2644. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2025.php#D-20250911-020350</guid>
  2645. <link>http://www.lemis.com/grog/diary-sep2025.php#D-20250911-020350</link>
  2646. <category>health</category>
  2647. <category>general</category>
  2648. <category>opinion</category>
  2649. <title>Yvonne: pacemaker?</title>
  2650.  <description>
  2651.    <![CDATA[
  2652.    <div align="justify">
  2653.      <p>
  2654. One of the things I had intended to do today was to go with <a href="http://www.lemis.com/yvonne/">Yvonne</a> for an appointment with <a href="https://ballaratcardiology.com.au/staff/dr-rod-reddy">Rodney Reddy</a>, but I ended up
  2655. not leaving the house.
  2656.      </p>
  2657.  
  2658.      <p>
  2659. Yvonne had been thinking about a <a href="https://en.wikipedia.org/wiki/Pacemaker">pacemaker</a>, something that <a href="https://www.melbourneheart.com.au/prof-peter-kistler/">Professor Peter Kistler</a> had
  2660. suggested.  But Rod pointed out that they don't help with <a href="https://en.wikipedia.org/wiki/Atrial_fibrillation">atrial fibrillation</a>, and
  2661. instead <i>once again</i> changed the medication.  It seems that she should have stopped
  2662. taking <a href="https://en.wikipedia.org/wiki/Digoxin">Digoxin</a> when she moved to
  2663. the <a href="https://en.wikipedia.org/wiki/Sotalol">Sotalol</a> <a href="http://www.lemis.com/grog/diary-aug2025.php?topics=G&amp;subtitle=Next%20cardiac%20choice&amp;article=D-20250802-023819#D-20250802-023819">last month</a>.  Hopefully that will help.  It's not the first time we have had issues
  2664. with the medication prescription.
  2665.      </p>
  2666.  
  2667.      <p>
  2668. Somehow I'm getting the impression that Kistler is a good mechanic, but not the best choice
  2669. of diagnostician.
  2670.      </p>
  2671.      </div>
  2672.    ]]>
  2673.  </description>
  2674.  <dc:creator>Greg Lehey</dc:creator>
  2675.  <dc:date>2025-09-11T02:03:50+00:00</dc:date>
  2676. </item>
  2677.  
  2678.            
  2679. <item>
  2680. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2025.php#D-20250911-020359</guid>
  2681. <link>http://www.lemis.com/grog/diary-sep2025.php#D-20250911-020359</link>
  2682. <category>technology</category>
  2683. <category>opinion</category>
  2684. <title>More fun with VirtualBox and bde</title>
  2685.  <description>
  2686.    <![CDATA[
  2687.    <div align="justify">
  2688.      <p>
  2689. More playing around with <a href="https://en.wikipedia.org/wiki/VirtualBox">VirtualBox</a> today, with no breakthrough.  I had paused <i>dereel</i> with <i>zzz</i>,
  2690. and when I restarted it the networking had gone to hell again.  Here a repeat of what I had
  2691. done yesterday:
  2692.      </p>
  2693.  
  2694.      <blockquote class="fullwidth">
  2695. <div style="text-align:left">
  2696.  <tt>
  2697. <code><font color="blue">=== root@dereel (/dev/pts/3)</font> <font color="red">/eureka/home/grog</font> <font color="blue">1</font> &#45;&gt; <b><tt>ifconfig</tt></b></code>
  2698. <br />em0: flags=1008943&lt;UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST,LOWER_UP&gt; metric 0 mtu 1500 &nbsp; &nbsp; &nbsp; &nbsp;options=4e524bb&lt;RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LRO,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6,HWSTATS,MEXTPG&gt;
  2699. <br /><code><font color="blue">=== root@dereel (/dev/pts/3)</font> <font color="red">/eureka/home/grog</font> <font color="blue">2</font> &#45;&gt; <b><tt>ifconfig em0 &#45;rxcsum &#45;txcsum &#45;vlanhwtso &#45;lro &#45;tso4 &#45;tso6 down up</tt></b></code>
  2700. <br /><code><font color="blue">=== root@dereel (/dev/pts/3)</font> <font color="red">/eureka/home/grog</font> <font color="blue">3</font> &#45;&gt; <b><tt>ifconfig</tt></b></code>
  2701. <br />em0: flags=1008943&lt;UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST,LOWER_UP&gt; metric 0 mtu 1500
  2702. <br />&nbsp;&nbsp; &nbsp; &nbsp; &nbsp;options=4c120b8&lt;VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,WOL_MAGIC,VLAN_HWFILTER,TXCSUM_IPV6,HWSTATS,MEXTPG&gt;
  2703. <br />
  2704.  </tt>
  2705. </div>
  2706. </blockquote>
  2707.  
  2708.      <p>
  2709. After that it worked normally again, but the Microsoft boxen still didn't want to know.  Do
  2710. I have to cold start them every time?
  2711.      </p>
  2712.  
  2713.      <p>
  2714. And Bruce Evans' C compiler?  I posted what I had and got no answer.  I'm not convinced that
  2715. I have the right files, though the name <i>usr/src/mx386/bcc</i> (from the
  2716. archive <i>e/bde/dist/minix.tar.gz</i>) does raise some hope.
  2717.      </p>
  2718.      </div>
  2719.    ]]>
  2720.  </description>
  2721.  <dc:creator>Greg Lehey</dc:creator>
  2722.  <dc:date>2025-09-11T02:03:59+00:00</dc:date>
  2723. </item>
  2724.  
  2725.                  
  2726. <item>
  2727. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2025.php#D-20250912-023120</guid>
  2728. <link>http://www.lemis.com/grog/diary-sep2025.php#D-20250912-023120</link>
  2729. <category>health</category>
  2730. <title>Weakness: over</title>
  2731.  <description>
  2732.    <![CDATA[
  2733.    <div align="justify">
  2734.      <p>
  2735. What it really the news about <a href="https://en.wikipedia.org/wiki/Israel">Israel's</a> aggression against <a href="https://en.wikipedia.org/wiki/Gaza">Gaza</a> that made me well so weak and dizzy <a href="http://www.lemis.com/grog/diary-sep2025.php?subtitle=Israel%20makes%20me%20sick&amp;article=D-20250911-015021#D-20250911-015021">yesterday</a>?  Or am I just getting old and weak?  In any case, today I felt much better
  2736. again, though I avoided any further sickening news.
  2737.      </p>
  2738.  
  2739.      <p>
  2740. <a href="http://www.lemis.com/yvonne/">Yvonne</a> has now changed her medication (no more <a href="https://en.wikipedia.org/wiki/Digoxin">Digoxin</a>) and is feeling marginally better.
  2741. It's early days; we'll keep an eye on it.
  2742.      </p>
  2743.      </div>
  2744.    ]]>
  2745.  </description>
  2746.  <dc:creator>Greg Lehey</dc:creator>
  2747.  <dc:date>2025-09-12T02:31:20+00:00</dc:date>
  2748. </item>
  2749.  
  2750.            
  2751. <item>
  2752. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2025.php#D-20250912-023155</guid>
  2753. <link>http://www.lemis.com/grog/diary-sep2025.php#D-20250912-023155</link>
  2754. <category>food</category>
  2755. <category>and</category>
  2756. <category>drink</category>
  2757. <category>general</category>
  2758. <category>opinion</category>
  2759. <title>Semmelknödel revisited</title>
  2760.  <description>
  2761.    <![CDATA[
  2762.    <div align="justify">
  2763.      <p>
  2764. German-style <a href="http://www.lemis.com/grog/recipes/gulasch.php">Gulasch</a> for dinner tonight.  What do
  2765. we eat with it?  For <a href="http://www.lemis.com/yvonne/">Yvonne</a>, the choice was clear: <a href="https://en.wikipedia.org/wiki/Knödel">„Kartoffelknödel“</a> im Kochbeutel (translated
  2766. as “cooking bags” on the packet).  But I eat <a href="https://en.wikipedia.org/wiki/Semmelknödel">Semmelknödel</a> (bread dumplings), and we
  2767. didn't have any instant ones.  OK, back to <a href="http://www.lemis.com/grog/recipes/Semmelknoedel.php">my
  2768. recipe</a>, with which I was not overly happy.  In particular, the last batch was lumpy
  2769. and not very firm.  OK, start again.  Instead of putting the dried bread through the mincer,
  2770. reduce it with the mixer:
  2771.      </p>
  2772.  
  2773.        <a id="Photo-26" name="Photo-26"
  2774.          href="diary-sep2025.php?dirdate=20250911&amp;imagesizes=111111111111111111111111112#Photo-26">
  2775.          <img alt="This should be Semmelknoedel-1.jpeg.  Is it missing?" border="0" id="Photo_26"
  2776.               title="Photo Semmelknoedel-1.jpeg.  Click to redisplay larger version of image."
  2777.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250911/small/Semmelknoedel-1.jpeg"
  2778.               width="303" height="223"
  2779.           /></a>
  2780.  
  2781.      <p>
  2782. Do the same with the onions:
  2783.      </p>
  2784.  
  2785.        <a id="Photo-27" name="Photo-27"
  2786.          href="diary-sep2025.php?dirdate=20250911&amp;imagesizes=1111111111111111111111111112#Photo-27">
  2787.          <img alt="This should be Semmelknoedel-4.jpeg.  Is it missing?" border="0" id="Photo_27"
  2788.               title="Photo Semmelknoedel-4.jpeg.  Click to redisplay larger version of image."
  2789.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250911/small/Semmelknoedel-4.jpeg"
  2790.               width="300" height="225"
  2791.           /></a>
  2792.        <a id="Photo-28" name="Photo-28"
  2793.          href="diary-sep2025.php?dirdate=20250911&amp;imagesizes=11111111111111111111111111112#Photo-28">
  2794.          <img alt="This should be Semmelknoedel-5.jpeg.  Is it missing?" border="0" id="Photo_28"
  2795.               title="Photo Semmelknoedel-5.jpeg.  Click to redisplay larger version of image."
  2796.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250911/small/Semmelknoedel-5.jpeg"
  2797.               width="300" height="225"
  2798.           /></a>
  2799.  
  2800.      <p>
  2801. Reduce the fresh parsley with a <a href="https://en.wikipedia.org/wiki/Mezzaluna">mezzaluna</a>:
  2802.      </p>
  2803.  
  2804.        <a id="Photo-29" name="Photo-29"
  2805.          href="diary-sep2025.php?dirdate=20250911&amp;imagesizes=111111111111111111111111111112#Photo-29">
  2806.          <img alt="This should be Semmelknoedel-8.jpeg.  Is it missing?" border="0" id="Photo_29"
  2807.               title="Photo Semmelknoedel-8.jpeg.  Click to redisplay larger version of image."
  2808.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250911/small/Semmelknoedel-8.jpeg"
  2809.               width="302" height="223"
  2810.           /></a>
  2811.  
  2812.      <p>
  2813. To my surprise, the original estimate of 160 g of milk was too little.  With 180 g (little
  2814. less than <a href="http://www.lemis.com/grog/diary-aug2024.php?subtitle=Dumplings%20again&amp;article=D-20240825-014732#D-20240825-014732">last time</a>) they were barely formable.  Here with 162 g and 180 g of milk:
  2815.      </p>
  2816.  
  2817.        <a id="Photo-30" name="Photo-30"
  2818.          href="diary-sep2025.php?dirdate=20250911&amp;imagesizes=1111111111111111111111111111112#Photo-30">
  2819.          <img alt="This should be Semmelknoedel-10.jpeg.  Is it missing?" border="0" id="Photo_30"
  2820.               title="Photo Semmelknoedel-10.jpeg.  Click to redisplay larger version of image."
  2821.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250911/small/Semmelknoedel-10.jpeg"
  2822.               width="301" height="224"
  2823.           /></a>
  2824.        <a id="Photo-31" name="Photo-31"
  2825.          href="diary-sep2025.php?dirdate=20250911&amp;imagesizes=11111111111111111111111111111112#Photo-31">
  2826.          <img alt="This should be Semmelknoedel-11.jpeg.  Is it missing?" border="0" id="Photo_31"
  2827.               title="Photo Semmelknoedel-11.jpeg.  Click to redisplay larger version of image."
  2828.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250911/small/Semmelknoedel-11.jpeg"
  2829.               width="300" height="225"
  2830.           /></a>
  2831.  
  2832.      <p>
  2833. And yes, they formed well, and after leaving in boiled water for a couple of minutes I was
  2834. able to make dumplings that looked relatively like they should:
  2835.      </p>
  2836.  
  2837.        <a id="Photo-32" name="Photo-32"
  2838.          href="diary-sep2025.php?dirdate=20250911&amp;imagesizes=111111111111111111111111111111112#Photo-32">
  2839.          <img alt="This should be Semmelknoedel-15.jpeg.  Is it missing?" border="0" id="Photo_32"
  2840.               title="Photo Semmelknoedel-15.jpeg.  Click to redisplay larger version of image."
  2841.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250911/small/Semmelknoedel-15.jpeg"
  2842.               width="300" height="225"
  2843.           /></a>
  2844.  
  2845.      <p>
  2846.      </p>
  2847.      </div>
  2848.    ]]>
  2849.  </description>
  2850.  <dc:creator>Greg Lehey</dc:creator>
  2851.  <dc:date>2025-09-12T02:31:55+00:00</dc:date>
  2852. </item>
  2853.  
  2854.                  
  2855. <item>
  2856. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2025.php#D-20250913-040213</guid>
  2857. <link>http://www.lemis.com/grog/diary-sep2025.php#D-20250913-040213</link>
  2858. <category>opinion</category>
  2859. <category>food</category>
  2860. <category>and</category>
  2861. <category>drink</category>
  2862. <title>Semmelknödel: the morning after</title>
  2863.  <description>
  2864.    <![CDATA[
  2865.    <div align="justify">
  2866.      <p>
  2867. <a href="http://www.lemis.com/grog/diary-sep2025.php?subtitle=Semmelkn%C3%B6del%20revisited&amp;article=D-20250912-023155#D-20250912-023155">Yesterday's</a> <a href="https://en.wikipedia.org/wiki/Semmelknödel">Semmelknödel</a> were almost exactly what I wanted.  I had left most of the mass over for
  2868. today in case it needed tuning, but such proved not to be the case, so I cooked them exactly
  2869. as yesterday.  But the results were not what I expected:
  2870.      </p>
  2871.  
  2872.        <a id="Photo-33" name="Photo-33"
  2873.          href="diary-sep2025.php?dirdate=20250912&amp;imagesizes=1111111111111111111111111111111112#Photo-33">
  2874.          <img alt="This should be Disintegrating-Semmelknoedel-3.jpeg.  Is it missing?" border="0" id="Photo_33"
  2875.               title="Photo Disintegrating-Semmelknoedel-3.jpeg.  Click to redisplay larger version of image."
  2876.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250912/small/Disintegrating-Semmelknoedel-3.jpeg"
  2877.               width="303" height="223"
  2878.           /></a>
  2879.  
  2880.      <p>
  2881. The two leftovers from yesterday are at the top, and they're fine.  The others are
  2882. disintegrating, and they've left their mark on the pot:
  2883.      </p>
  2884.  
  2885.        <a id="Photo-34" name="Photo-34"
  2886.          href="diary-sep2025.php?dirdate=20250912&amp;imagesizes=11111111111111111111111111111111112#Photo-34">
  2887.          <img alt="This should be Disintegrating-Semmelknoedel-2.jpeg.  Is it missing?" border="0" id="Photo_34"
  2888.               title="Photo Disintegrating-Semmelknoedel-2.jpeg.  Click to redisplay larger version of image."
  2889.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250912/small/Disintegrating-Semmelknoedel-2.jpeg"
  2890.               width="301" height="224"
  2891.           /></a>
  2892.  
  2893.      <p>
  2894. What went wrong there?  I really don't know.  “I didn't change anything”.  Somehow there's
  2895. more to do before I'm happy with the recipe.
  2896.      </p>
  2897.      </div>
  2898.    ]]>
  2899.  </description>
  2900.  <dc:creator>Greg Lehey</dc:creator>
  2901.  <dc:date>2025-09-13T04:02:13+00:00</dc:date>
  2902. </item>
  2903.  
  2904.                  
  2905. <item>
  2906. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2025.php#D-20250914-020212</guid>
  2907. <link>http://www.lemis.com/grog/diary-sep2025.php#D-20250914-020212</link>
  2908. <category>food</category>
  2909. <category>and</category>
  2910. <category>drink</category>
  2911. <category>opinion</category>
  2912. <title>Quick and easy ramen breakfast</title>
  2913.  <description>
  2914.    <![CDATA[
  2915.    <div align="justify">
  2916.      <p>
  2917. I have a number of “instant” dishes in the pantry, including this one:
  2918.      </p>
  2919.  
  2920.        <a id="Photo-35" name="Photo-35"
  2921.          href="diary-sep2025.php?dirdate=20250729&amp;imagesizes=111111111111111111111111111111111112#Photo-35">
  2922.          <img alt="This should be Ramen-kit-1.jpeg.  Is it missing?" border="0" id="Photo_35"
  2923.               title="Photo Ramen-kit-1.jpeg.  Click to redisplay larger version of image."
  2924.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250729/small/Ramen-kit-1.jpeg"
  2925.               width="223" height="302"
  2926.           /></a>
  2927.  
  2928.      <p>
  2929. It doesn't look too bad, but it's enough for two people.  After a brief attempt to convince
  2930. <a href="http://www.lemis.com/yvonne/">Yvonne</a>, decided to split it over two days.  <i>Another</i> of
  2931. these dishes that talks of cups (in this case of 250 ml), requiring me to calculate things.
  2932. That's more of a pain than all the rest put together.
  2933.      </p>
  2934.  
  2935.        <a id="Photo-36" name="Photo-36"
  2936.          href="diary-sep2025.php?dirdate=20250729&amp;imagesizes=1111111111111111111111111111111111112#Photo-36">
  2937.          <img alt="This should be Ramen-kit-2-detail.jpeg.  Is it missing?" border="0" id="Photo_36"
  2938.               title="Photo Ramen-kit-2-detail.jpeg.  Click to redisplay larger version of image."
  2939.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250729/small/Ramen-kit-2-detail.jpeg"
  2940.               width="320" height="211"
  2941.           /></a>
  2942.  
  2943.      <p>
  2944. OK, drag out a cup and measure:
  2945.      </p>
  2946.  
  2947.        <a id="Photo-37" name="Photo-37"
  2948.          href="diary-sep2025.php?dirdate=20250913&amp;imagesizes=11111111111111111111111111111111111112#Photo-37">
  2949.          <img alt="This should be Instant-ramen-3.jpeg.  Is it missing?" border="0" id="Photo_37"
  2950.               title="Photo Instant-ramen-3.jpeg.  Click to redisplay larger version of image."
  2951.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250913/small/Instant-ramen-3.jpeg"
  2952.               width="303" height="223"
  2953.           /></a>
  2954.  
  2955.      <p>
  2956. That proved to be mislabeled spinach, but in principle it makes no difference: how do you
  2957. decide when the cup is full?  That's 52 g, and in the end I decided on 72 g.
  2958.      </p>
  2959.  
  2960.      <p>
  2961. While considering further action, came across this video, titled “10 Instant Ramen Hacks |
  2962. Transform Instant Noodles from Good to Incredible!”:
  2963.      </p>
  2964.  
  2965.      <iframe width="400"
  2966.            height="300"
  2967.            src="http://www.youtube.com/embed/zyvAD1zBZ-0"
  2968. allowfullscreen
  2969.            frameborder="0" >
  2970.     </iframe>
  2971.  
  2972.      <p>
  2973. It looks quite interesting, but it's rather long.  Decided that today I would prepare the
  2974. dish as close to the original as possible, and keep the other half for tomorrow.
  2975.      </p>
  2976.  
  2977.      <p>
  2978. The package contains three subpackages:
  2979.      </p>
  2980.  
  2981.        <a id="Photo-38" name="Photo-38"
  2982.          href="diary-sep2025.php?dirdate=20250913&amp;imagesizes=111111111111111111111111111111111111112#Photo-38">
  2983.          <img alt="This should be Instant-ramen-4.jpeg.  Is it missing?" border="0" id="Photo_38"
  2984.               title="Photo Instant-ramen-4.jpeg.  Click to redisplay larger version of image."
  2985.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250913/small/Instant-ramen-4.jpeg"
  2986.               width="304" height="222"
  2987.           /></a>
  2988.  
  2989.      <p>
  2990. The noodles (on the left) are moist rather than wet.  They require cooking in the broth from
  2991. the packet on the right before adding the other ingredients, including spinach and a
  2992. whopping 100 g of pork:
  2993.      </p>
  2994.  
  2995.        <a id="Photo-39" name="Photo-39"
  2996.          href="diary-sep2025.php?dirdate=20250913&amp;imagesizes=1111111111111111111111111111111111111112#Photo-39">
  2997.          <img alt="This should be Instant-ramen-10.jpeg.  Is it missing?" border="0" id="Photo_39"
  2998.               title="Photo Instant-ramen-10.jpeg.  Click to redisplay larger version of image."
  2999.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250913/small/Instant-ramen-10.jpeg"
  3000.               width="300" height="225"
  3001.           /></a>
  3002.  
  3003.      <p>
  3004. And the dried vegetables in the middle pack included a surprising amount of maize kernels,
  3005. not something that I would have expected of Japanese food.
  3006.      </p>
  3007.  
  3008.      <p>
  3009. After that, and with the required egg, things looked like this:
  3010.      </p>
  3011.  
  3012.        <a id="Photo-40" name="Photo-40"
  3013.          href="diary-sep2025.php?dirdate=20250913&amp;imagesizes=11111111111111111111111111111111111111112#Photo-40">
  3014.          <img alt="This should be Instant-ramen-13.jpeg.  Is it missing?" border="0" id="Photo_40"
  3015.               title="Photo Instant-ramen-13.jpeg.  Click to redisplay larger version of image."
  3016.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250913/small/Instant-ramen-13.jpeg"
  3017.               width="300" height="225"
  3018.           /></a>
  3019.  
  3020.      <p>
  3021. How did it taste?  The broth seems to be mainly <a href="https://en.wikipedia.org/wiki/Miso">miso</a>.  With a bit of soya and chili sauce it
  3022. didn't taste too bad.  Did it save me any time?  No, of course not, since I spent a lot of
  3023. time thinking about it.  Will it save me any time next time?  I doubt it.  But it has given
  3024. me food for thought.
  3025.      </p>
  3026.      </div>
  3027.    ]]>
  3028.  </description>
  3029.  <dc:creator>Greg Lehey</dc:creator>
  3030.  <dc:date>2025-09-14T02:02:12+00:00</dc:date>
  3031. </item>
  3032.  
  3033.                  
  3034. <item>
  3035. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2025.php#D-20250915-004610</guid>
  3036. <link>http://www.lemis.com/grog/diary-sep2025.php#D-20250915-004610</link>
  3037. <category>food</category>
  3038. <category>and</category>
  3039. <category>drink</category>
  3040. <category>opinion</category>
  3041. <title>Instant ramen, take 2</title>
  3042.  <description>
  3043.    <![CDATA[
  3044.    <div align="justify">
  3045.      <p>
  3046. As planned <a href="http://www.lemis.com/grog/diary-sep2025.php?subtitle=Quick%20and%20easy%20ramen%20breakfast&amp;article=D-20250914-020212#D-20250914-020212">yesterday</a>, cooked the other half of the ramen meal kit with ideas gleaned from
  3047. <a href="https://www.youtube.com/watch?v=zyvAD1zBZ-0&amp;list=PLcb9h94d4zbeZIar0VrkRwg8_izGXUYiJ">The
  3048. Woks of Life</a>.  I had all the ingredients that they had round minute 12, but chose to
  3049. incorporate only some of them, and also some dòufu puffs along with the suggested spring
  3050. onions, chili and coriander stalks:
  3051.      </p>
  3052.  
  3053.        <a id="Photo-41" name="Photo-41"
  3054.          href="diary-sep2025.php?dirdate=20250914&amp;imagesizes=111111111111111111111111111111111111111112#Photo-41">
  3055.          <img alt="This should be Instant-Ramen-noodles-4.jpeg.  Is it missing?" border="0" id="Photo_41"
  3056.               title="Photo Instant-Ramen-noodles-4.jpeg.  Click to redisplay larger version of image."
  3057.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250914/small/Instant-Ramen-noodles-4.jpeg"
  3058.               width="302" height="224"
  3059.           /></a>
  3060.  
  3061.      <p>
  3062. Before serving, I added raw onions.  The result?
  3063.      </p>
  3064.  
  3065.        <a id="Photo-42" name="Photo-42"
  3066.          href="diary-sep2025.php?dirdate=20250914&amp;imagesizes=1111111111111111111111111111111111111111112#Photo-42">
  3067.          <img alt="This should be Instant-Ramen-noodles-7.jpeg.  Is it missing?" border="0" id="Photo_42"
  3068.               title="Photo Instant-Ramen-noodles-7.jpeg.  Click to redisplay larger version of image."
  3069.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250914/small/Instant-Ramen-noodles-7.jpeg"
  3070.               width="281" height="241"
  3071.           /></a>
  3072.  
  3073.      <p>
  3074. Better than yesterday, though it still needed soya sauce.  I don't think it would have
  3075. tasted very much different with water instead of the <a href="https://en.wikipedia.org/wiki/Miso">miso</a> mixture.
  3076.      </p>
  3077.      </div>
  3078.    ]]>
  3079.  </description>
  3080.  <dc:creator>Greg Lehey</dc:creator>
  3081.  <dc:date>2025-09-15T00:46:10+00:00</dc:date>
  3082. </item>
  3083.  
  3084.            
  3085. <item>
  3086. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2025.php#D-20250915-004615</guid>
  3087. <link>http://www.lemis.com/grog/diary-sep2025.php#D-20250915-004615</link>
  3088. <category>food</category>
  3089. <category>and</category>
  3090. <category>drink</category>
  3091. <category>opinion</category>
  3092. <title>Lamb Keema</title>
  3093.  <description>
  3094.    <![CDATA[
  3095.    <div align="justify">
  3096.      <p>
  3097. Somehow I'm spending all my time cooking lately.  We've had some minced lamb from Chris
  3098. Bahlo for ever, and it really needs to go.  Today I decided on a <a href="https://www.allrecipes.com/recipe/246250/kima/">Kima</a> (“Keema”) curry with this
  3099. mixture:
  3100.      </p>
  3101.  
  3102.        <a id="Photo-43" name="Photo-43"
  3103.          href="diary-sep2025.php?dirdate=20250914&amp;imagesizes=11111111111111111111111111111111111111111112#Photo-43">
  3104.          <img alt="This should be Keema-1.jpeg.  Is it missing?" border="0" id="Photo_43"
  3105.               title="Photo Keema-1.jpeg.  Click to redisplay larger version of image."
  3106.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250914/small/Keema-1.jpeg"
  3107.               width="218" height="311"
  3108.           /></a>
  3109.        <a id="Photo-44" name="Photo-44"
  3110.          href="diary-sep2025.php?dirdate=20250914&amp;imagesizes=111111111111111111111111111111111111111111112#Photo-44">
  3111.          <img alt="This should be Keema-2.jpeg.  Is it missing?" border="0" id="Photo_44"
  3112.               title="Photo Keema-2.jpeg.  Click to redisplay larger version of image."
  3113.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250914/small/Keema-2.jpeg"
  3114.               width="215" height="314"
  3115.           /></a>
  3116.  
  3117.      <p>
  3118. It wanted a ridiculous amount of meat, of which I only put in two-thirds.  And somehow it
  3119. was boring, also too hot for <a href="http://www.lemis.com/yvonne/">Yvonne</a>, who ended up eating—as
  3120. it happened—a couple of kima kebabs.  It looks like I'll have a lot left over for
  3121. breakfasts.
  3122.      </p>
  3123.      </div>
  3124.    ]]>
  3125.  </description>
  3126.  <dc:creator>Greg Lehey</dc:creator>
  3127.  <dc:date>2025-09-15T00:46:15+00:00</dc:date>
  3128. </item>
  3129.  
  3130.                  
  3131. <item>
  3132. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2025.php#D-20250916-014723</guid>
  3133. <link>http://www.lemis.com/grog/diary-sep2025.php#D-20250916-014723</link>
  3134. <category>food</category>
  3135. <category>and</category>
  3136. <category>drink</category>
  3137. <category>opinion</category>
  3138. <title>Still more cooking</title>
  3139.  <description>
  3140.    <![CDATA[
  3141.    <div align="justify">
  3142.      <p>
  3143. For some reason I wasn't feeling overly hungry this morning.  Time to try out one of these
  3144. <a href="https://en.wikipedia.org/wiki/ALDI">ALDI</a> pouches:
  3145.      </p>
  3146.  
  3147.        <a id="Photo-45" name="Photo-45"
  3148.          href="diary-sep2025.php?dirdate=20250809&amp;imagesizes=1111111111111111111111111111111111111111111112#Photo-45">
  3149.          <img alt="This should be Soup-Co-Wonton-1.jpeg.  Is it missing?" border="0" id="Photo_45"
  3150.               title="Photo Soup-Co-Wonton-1.jpeg.  Click to redisplay larger version of image."
  3151.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250809/small/Soup-Co-Wonton-1.jpeg"
  3152.               width="225" height="300"
  3153.           /></a>
  3154.  
  3155.      <p>
  3156. No noodles.  Only 100 g, 255 with the additional water.  Much less than my normal breakfast,
  3157. just what the doctor ordered.  <a href="https://en.wikipedia.org/wiki/Wonton">Wonton</a>, with chicken dumplings and <a href="https://en.wikipedia.org/wiki/Shiitake">shiitake</a> mushrooms, clearly inventiveness
  3158. on the part of the designer.  Put in a couple of real (prawn) wontons so that it has some
  3159. consistency.
  3160.      </p>
  3161.  
  3162.      <p>
  3163. But no, it <i>did</i> contain some solids.  Here with the added wontons:
  3164.      </p>
  3165.  
  3166.        <a id="Photo-46" name="Photo-46"
  3167.          href="diary-sep2025.php?dirdate=20250915&amp;imagesizes=11111111111111111111111111111111111111111111112#Photo-46">
  3168.          <img alt="This should be Instant-wonton-soup-3.jpeg.  Is it missing?" border="0" id="Photo_46"
  3169.               title="Photo Instant-wonton-soup-3.jpeg.  Click to redisplay larger version of image."
  3170.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250915/small/Instant-wonton-soup-3.jpeg"
  3171.               width="300" height="224"
  3172.           /></a>
  3173.  
  3174.      <p>
  3175. And how was it?  Not bad, but not to be repeated.  In particular it had little taste and not
  3176. enough salt.  I have two other sachets (“<a href="https://en.wikipedia.org/wiki/Laksa">laksa</a>” and “<a href="https://en.wikipedia.org/wiki/Tom_yum">tom yam</a>”).
  3177. Together they might make a breakfast.
  3178.      </p>
  3179.      </div>
  3180.    ]]>
  3181.  </description>
  3182.  <dc:creator>Greg Lehey</dc:creator>
  3183.  <dc:date>2025-09-16T01:47:23+00:00</dc:date>
  3184. </item>
  3185.  
  3186.            
  3187. <item>
  3188. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2025.php#D-20250916-015621</guid>
  3189. <link>http://www.lemis.com/grog/diary-sep2025.php#D-20250916-015621</link>
  3190. <category>food</category>
  3191. <category>and</category>
  3192. <category>drink</category>
  3193. <category>opinion</category>
  3194. <title>Yet more cooking</title>
  3195.  <description>
  3196.    <![CDATA[
  3197.    <div align="justify">
  3198.      <p>
  3199. I have the feeling that I have spent the last five days cooking.  Time to stop.  But no,
  3200. first more <a href="http://www.lemis.com/grog/recipes/Laugengebaeck.php">Laugengebäck</a>, according to a
  3201. monthly ritual that is gradually becoming routine.  Today was no exception.  But it took up
  3202. much of the afternoon.
  3203.      </p>
  3204.      </div>
  3205.    ]]>
  3206.  </description>
  3207.  <dc:creator>Greg Lehey</dc:creator>
  3208.  <dc:date>2025-09-16T01:56:21+00:00</dc:date>
  3209. </item>
  3210.  
  3211.                  
  3212. <item>
  3213. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2025.php#D-20250917-040554</guid>
  3214. <link>http://www.lemis.com/grog/diary-sep2025.php#D-20250917-040554</link>
  3215. <category>food</category>
  3216. <category>and</category>
  3217. <category>drink</category>
  3218. <category>general</category>
  3219. <category>history</category>
  3220. <category>opinion</category>
  3221. <title>Cooking: enough!</title>
  3222.  <description>
  3223.    <![CDATA[
  3224.    <div align="justify">
  3225.      <p>
  3226. I seem to have spent the whole of the last week cooking.  Not so today.  In the morning I
  3227. ate <i>some</i> of the rest of the Keema curry that I cooked <a href="http://www.lemis.com/grog/diary-sep2025.php?subtitle=Lamb%20Keema&amp;article=D-20250915-004615#D-20250915-004615">on Sunday</a>, and in the evening we ate leftovers of the chicken that <a href="http://www.lemis.com/yvonne/">Yvonne</a> cooked (and didn't document) on Saturday.  About the only thing
  3228. that I cooked was crinkle cut potatoes.
  3229.      </p>
  3230.  
  3231.      <p>
  3232. I'm not completely inactive, just putting up a good imitation.  I spent much of the
  3233. afternoon watching a video of how <a href="https://en.wikipedia.org/wiki/Adolf_Hitler">Adolf Hitler</a> spent the last 2 years before the war.  I had hoped to find some
  3234. similarities with the current situation in the <a href="https://en.wikipedia.org/wiki/USA">USA</a>, but there was little obvious.  About the
  3235. biggest point of interest was the <a href="https://en.wikipedia.org/wiki/Anschluss">Anschluss</a>, where they claimed only a small majority voted in favour.  My
  3236. understanding was that the majority of Austrians were in favour.  It's interesting that this
  3237. had been discussed (and rejected) as the <a href="https://en.wikipedia.org/wiki/Großdeutsche_Lösung">großdeutsche Lösung</a> in 1848.
  3238. But that was because of the relative strength of Austria and <a href="https://en.wikipedia.org/wiki/Prussia">Prussia</a> at the time, something that had
  3239. changed completely by 1938.  So there does seem to have been some sense in it, which the
  3240. people who made the documentary don't want to see.
  3241.      </p>
  3242.      </div>
  3243.    ]]>
  3244.  </description>
  3245.  <dc:creator>Greg Lehey</dc:creator>
  3246.  <dc:date>2025-09-17T04:05:54+00:00</dc:date>
  3247. </item>
  3248.  
  3249.                        
  3250. <item>
  3251. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2025.php#D-20250918-015035</guid>
  3252. <link>http://www.lemis.com/grog/diary-sep2025.php#D-20250918-015035</link>
  3253. <category>photography</category>
  3254. <category>opinion</category>
  3255. <title>More birding</title>
  3256.  <description>
  3257.    <![CDATA[
  3258.    <div align="justify">
  3259.      <p>
  3260. Up in the middle of the night to go to another <a href="https://en.wikipedia.org/wiki/OM_System">OM System</a> birding session with Aaron
  3261. Harivel in the <a href="https://en.wikipedia.org/wiki/Western_Treatment_Plant#Environment">Western Treatment
  3262. Plant</a> near <a href="https://en.wikipedia.org/wiki/Lara,_Victoria">Lara</a>.  I
  3263. have already done this one, <a href="http://www.lemis.com/grog/diary-jul2025.php?subtitle=OM%20System%20birding%20meeting&amp;article=D-20250704-020013#D-20250704-020013">2½ months ago</a>, but Aaron said that we would see many birds that weren't there last
  3264. time.
  3265.      </p>
  3266.  
  3267.      <p>
  3268. I was disappointed.  Although spring has sprung, it was considerably cooler than last time
  3269. and very windy, maybe a reason we saw so few birds.  I still managed 258 images, some of
  3270. them good, but I wonder if I need to go along with these “workshops”.  They have others
  3271. further from <a href="https://en.wikipedia.org/wiki/Dereel">Dereel</a>, but this one
  3272. was special because it gave us access to areas that are not open to the public.
  3273.      </p>
  3274.  
  3275.      <p>
  3276. There were <i>some</i> new birds, including <a href="https://en.wikipedia.org/wiki/Ibis">Ibises</a>, but I can see them elsewhere as well:
  3277.      </p>
  3278.  
  3279.        <a id="Photo-47" name="Photo-47"
  3280.          href="diary-sep2025.php?dirdate=20250917&amp;imagesizes=111111111111111111111111111111111111111111111112#Photo-47">
  3281.          <img alt="This should be Birding-207.jpeg.  Is it missing?" border="0" id="Photo_47"
  3282.               title="Photo Birding-207.jpeg.  Click to redisplay larger version of image."
  3283.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250917/small/Birding-207.jpeg"
  3284.               width="300" height="225"
  3285.           /></a>
  3286.  
  3287.      <p>
  3288. And not every shot was perfect, even when in focus:
  3289.      </p>
  3290.  
  3291.        <a id="Photo-48" name="Photo-48"
  3292.          href="diary-sep2025.php?dirdate=20250917&amp;imagesizes=1111111111111111111111111111111111111111111111112#Photo-48">
  3293.          <img alt="This should be Birding-29.jpeg.  Is it missing?" border="0" id="Photo_48"
  3294.               title="Photo Birding-29.jpeg.  Click to redisplay larger version of image."
  3295.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250917/small/Birding-29.jpeg"
  3296.               width="300" height="225"
  3297.           /></a>
  3298.        <a id="Photo-49" name="Photo-49"
  3299.          href="diary-sep2025.php?dirdate=20250917&amp;imagesizes=11111111111111111111111111111111111111111111111112#Photo-49">
  3300.          <img alt="This should be Birding-80.jpeg.  Is it missing?" border="0" id="Photo_49"
  3301.               title="Photo Birding-80.jpeg.  Click to redisplay larger version of image."
  3302.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250917/small/Birding-80.jpeg"
  3303.               width="300" height="225"
  3304.           /></a>
  3305.  
  3306.      <p>
  3307. And some playing around with my menus, getting my camera into a position where I couldn't
  3308. take any photos.  Neither could Aaron:
  3309.      </p>
  3310.  
  3311.        <a id="Photo-50" name="Photo-50"
  3312.          href="diary-sep2025.php?dirdate=20250917&amp;imagesizes=111111111111111111111111111111111111111111111111112#Photo-50">
  3313.          <img alt="This should be Birding-66.jpeg.  Is it missing?" border="0" id="Photo_50"
  3314.               title="Photo Birding-66.jpeg.  Click to redisplay larger version of image."
  3315.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250917/small/Birding-66.jpeg"
  3316.               width="300" height="225"
  3317.           /></a>
  3318.        <a id="Photo-51" name="Photo-51"
  3319.          href="diary-sep2025.php?dirdate=20250917&amp;imagesizes=1111111111111111111111111111111111111111111111111112#Photo-51">
  3320.          <img alt="This should be Birding-67.jpeg.  Is it missing?" border="0" id="Photo_51"
  3321.               title="Photo Birding-67.jpeg.  Click to redisplay larger version of image."
  3322.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250917/small/Birding-67.jpeg"
  3323.               width="300" height="225"
  3324.           /></a>
  3325.  
  3326.      <p>
  3327. Those were the first and last of 8 images that he took trying to reset the camera.  It
  3328. proved that I had accidentally enabled focus bracketing instead of focus limiting.
  3329.      </p>
  3330.  
  3331.      <p>
  3332. Should I do any more “workshops”?  In particular, there's a “workshop” at the <a href="https://www.rbg.vic.gov.au/">Royal Botanic Gardens</a> in <a href="https://en.wikipedia.org/wiki/Melbourne">Melbourne</a> <a href="http://www.lemis.com/grog/diary-oct2025.php#29">next month</a>.  It starts 2 hours later, but that's about the time I would need to get
  3333. there.  Can I park my car?  Is it worthwhile?  Aaron suggests that it's relatively basic,
  3334. and came up with the opinion that the new <a href="https://www.dpreview.com/articles/1340103734/hands-on-with-the-om-system-m-zuiko-90mm-f3-5-macro">90 mm macro</a> is very unforgiving with focus, while the <a href="https://www.dpreview.com/products/olympus/lenses/olympus_m_60_2p8">60 mm</a> is
  3335. forgiving.  That's not the first thing he has said about macros that sounds unconvincing:
  3336. yes, depth of field of a 90 mm camera is less, but it more than makes it up by its smaller
  3337. aperture.  A comparison at full aperture (90/3.5 and 60/2.8):
  3338.      </p>
  3339.  
  3340.      <table summary="Automatically generated table">
  3341.       <tr>
  3342.          <td valign="top" align="left">Focal length</td>
  3343.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3344.          <td valign="top" align="right">Subject</td>
  3345.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3346.          <td valign="top" align="right">Focal plane</td>
  3347.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3348.          <td valign="top" align="right">Magnification</td>
  3349.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3350.          <td valign="top" align="right">Exposure</td>
  3351.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3352.          <td valign="top" align="right">Near</td>
  3353.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3354.          <td valign="top" align="right">Far</td>
  3355.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3356.          <td valign="top" align="right">Depth of</td>
  3357.       </tr>
  3358.  
  3359.       <tr>
  3360.          <td valign="top" align="left"></td>
  3361.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3362.          <td valign="top" align="right">distance (m)</td>
  3363.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3364.          <td valign="top" align="right">distance (mm)</td>
  3365.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3366.          <td valign="top" align="right">comp</td>
  3367.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3368.          <td valign="top" align="right">(EV)</td>
  3369.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3370.          <td valign="top" align="right">limit (m)</td>
  3371.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3372.          <td valign="top" align="right">limit (m)</td>
  3373.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3374.          <td valign="top" align="right">field (m)</td>
  3375.       </tr>
  3376.  
  3377.       <tr>
  3378.          <td valign="top" align="left">30</td>
  3379.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3380.          <td valign="top" align="right">0.1000</td>
  3381.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3382.          <td valign="top" align="right">42.8571</td>
  3383.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3384.          <td valign="top" align="right">0.429</td>
  3385.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3386.          <td valign="top" align="right">1.0</td>
  3387.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3388.          <td valign="top" align="right">0.0997</td>
  3389.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3390.          <td valign="top" align="right">0.100312</td>
  3391.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3392.          <td valign="top" align="right">0.000622</td>
  3393.       </tr>
  3394.  
  3395.       <tr>
  3396.          <td valign="top" align="left">60</td>
  3397.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3398.          <td valign="top" align="right">0.2000</td>
  3399.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3400.          <td valign="top" align="right">85.7143</td>
  3401.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3402.          <td valign="top" align="right">0.429</td>
  3403.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3404.          <td valign="top" align="right">1.0</td>
  3405.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3406.          <td valign="top" align="right">0.1998</td>
  3407.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3408.          <td valign="top" align="right">0.2002</td>
  3409.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3410.          <td valign="top" align="right">0.0005</td>
  3411.       </tr>
  3412.  
  3413.       <tr>
  3414.          <td valign="top" align="left">90</td>
  3415.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3416.          <td valign="top" align="right">0.3000</td>
  3417.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3418.          <td valign="top" align="right">128.5714</td>
  3419.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3420.          <td valign="top" align="right">0.429</td>
  3421.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3422.          <td valign="top" align="right">1.0</td>
  3423.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3424.          <td valign="top" align="right">0.2997</td>
  3425.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3426.          <td valign="top" align="right">0.3003</td>
  3427.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3428.          <td valign="top" align="right">0.0006</td>
  3429.       </tr>
  3430.  
  3431.       <tr>
  3432.          <td valign="top" align="left"></td>
  3433.       </tr>
  3434.    </table>
  3435.  
  3436.      <p>
  3437. That gives a total depth of field for the 90 mm of 0.0006 m (0.2997 m - 0.3003 m), and
  3438. 0.0005 m (0.1998 m - 0.2002 m) for the 60 mm.  And that's before starting to think about the
  3439. convenience of such a long lens, nor of its price ($250 list for the 30 mm, $400 for the 60
  3440. mm, $1,400 for the 90 mm).
  3441.      </p>
  3442.  
  3443.      <p>
  3444. Still, it's not clear that I will gain much benefit from the course.  I have a month to
  3445. decide, but it's beginning to look like “no”.
  3446.      </p>
  3447.  
  3448.      <p>
  3449. In passing, it's worth thinking about how much time these sessions take up.  This one was
  3450. shorter, only 3 hours, but on top of that there 2½ hours driving time (would be more like 4
  3451. to the Botanic Gardens) and 7 hours processing time for the first cut of the photos.  There
  3452. will be more.
  3453.      </p>
  3454.      </div>
  3455.    ]]>
  3456.  </description>
  3457.  <dc:creator>Greg Lehey</dc:creator>
  3458.  <dc:date>2025-09-18T01:50:35+00:00</dc:date>
  3459. </item>
  3460.  
  3461.            
  3462. <item>
  3463. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2025.php#D-20250918-021000</guid>
  3464. <link>http://www.lemis.com/grog/diary-sep2025.php#D-20250918-021000</link>
  3465. <category>general</category>
  3466. <category>opinion</category>
  3467. <title>Moorabool ridge</title>
  3468.  <description>
  3469.    <![CDATA[
  3470.    <div align="justify">
  3471.      <p>
  3472. I didn't have anything to do in <a href="https://en.wikipedia.org/wiki/Geelong">Geelong</a> today, so took the scenic route home, which <a href="https://en.wikipedia.org/wiki/Google_Maps">Google Maps</a> puts as an alternative,
  3473. despite being shorter and faster than the way over the freeway.  There's one area just west
  3474. of <a href="https://en.wikipedia.org/wiki/Maude,_Victoria">Maude</a> where there's a
  3475. very steep part of the road:
  3476.      </p>
  3477.  
  3478.        <a id="Photo-52" name="Photo-52"
  3479.          href="diary-sep2025.php?dirdate=20250917&amp;imagesizes=11111111111111111111111111111111111111111111111111112#Photo-52">
  3480.          <img alt="This should be Perdrisat-Road-2.jpeg.  Is it missing?" border="0" id="Photo_52"
  3481.               title="Photo Perdrisat-Road-2.jpeg.  Click to redisplay larger version of image."
  3482.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250917/small/Perdrisat-Road-2.jpeg"
  3483.               width="304" height="222"
  3484.           /></a>
  3485.        <a id="Photo-53" name="Photo-53"
  3486.          href="diary-sep2025.php?dirdate=20250917&amp;imagesizes=111111111111111111111111111111111111111111111111111112#Photo-53">
  3487.          <img alt="This should be Perdrisat-Road-3.jpeg.  Is it missing?" border="0" id="Photo_53"
  3488.               title="Photo Perdrisat-Road-3.jpeg.  Click to redisplay larger version of image."
  3489.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20250917/small/Perdrisat-Road-3.jpeg"
  3490.               width="300" height="225"
  3491.           /></a>
  3492.  
  3493.      <p>
  3494. It seems to be part of the <a href="https://en.wikipedia.org/wiki/Brisbane_Ranges">Brisbane Ranges</a> that run north-south round here, though the sign I saw suggested
  3495. “Moorabool Ridge”, a name for which I only found winery links.  Most references point to the
  3496. valley.
  3497.      </p>
  3498.      </div>
  3499.    ]]>
  3500.  </description>
  3501.  <dc:creator>Greg Lehey</dc:creator>
  3502.  <dc:date>2025-09-18T02:10:00+00:00</dc:date>
  3503. </item>
  3504.  
  3505.            
  3506. <item>
  3507. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2025.php#D-20250918-021014</guid>
  3508. <link>http://www.lemis.com/grog/diary-sep2025.php#D-20250918-021014</link>
  3509. <category>photography</category>
  3510. <category>opinion</category>
  3511. <title>Fisheye compensation?</title>
  3512.  <description>
  3513.    <![CDATA[
  3514.    <div align="justify">
  3515.      <p>
  3516. While looking through the menus for my camera, found an item “Fisheye Compensation”.  Just
  3517. what I need for my <a href="https://7artisans.store/products/4mm-f-2-8-aps-c-lens-for-e-eos-m-fx-m43">7Artisans 4 mm
  3518. f/2.8 fisheye</a> lens.  Tried it out.  “Fisheye compensation not supported for this
  3519. lens”.  And yes, it seems it only works for Zuiko lenses; at least it worked for me with the
  3520. <a href="https://explore.omsystem.com/us/en/m-zuiko-ed-8mm-f1-8-fisheye-pro">Olympus
  3521. M.Zuiko Digital ED 8 mm f/1.8 Fisheye <b>PRO</b></a>.  But I don't need it for that lens.
  3522. It's looking more and more like the 4 mm fisheye wasn't worth the trouble.
  3523.      </p>
  3524.      </div>
  3525.    ]]>
  3526.  </description>
  3527.  <dc:creator>Greg Lehey</dc:creator>
  3528.  <dc:date>2025-09-18T02:10:14+00:00</dc:date>
  3529. </item>
  3530.  
  3531.            
  3532. <item>
  3533. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2025.php#D-20250918-021029</guid>
  3534. <link>http://www.lemis.com/grog/diary-sep2025.php#D-20250918-021029</link>
  3535. <category>food</category>
  3536. <category>and</category>
  3537. <category>drink</category>
  3538. <category>opinion</category>
  3539. <title>Chips?</title>
  3540.  <description>
  3541.    <![CDATA[
  3542.    <div align="justify">
  3543.      <p>
  3544. <a href="http://www.lemis.com/yvonne/">Yvonne</a> bought some sausages today, and also a cutter for
  3545. crinkle-cut chips.  Without anything to set the thickness, the latter is a waste of time,
  3546. and it'll almost certainly go back.
  3547.      </p>
  3548.  
  3549.      <p>
  3550. But crinkle cut (with the mandolin) or normal chips?  Recently we've been doing mainly
  3551. crinkle-cut, but I have (and found) a chip maker for making chips from fresh potatoes, which
  3552. I bought <a href="http://www.lemis.com/grog/diary-apr2025.php?subtitle=Twice-fried%20chips,%20the%20second&amp;article=D-20250425-021404#D-20250425-021404">only 6 months ago</a>.  Yes, it works, though it seems rather flimsy.  But the deep fryer
  3553. wanted “180°”, which proved to be initial 189°, for 5 minutes for the second fry.  After 2½
  3554. minutes they appeared dark, and they floated.  But they were still soft.  I need to decide
  3555. whether to try again for the full cooking time, or go back to crinkle-cut.
  3556.      </p>
  3557.      </div>
  3558.    ]]>
  3559.  </description>
  3560.  <dc:creator>Greg Lehey</dc:creator>
  3561.  <dc:date>2025-09-18T02:10:29+00:00</dc:date>
  3562. </item>
  3563.  
  3564.      </channel>
  3565. </rss>
  3566.  

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

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