Congratulations!

[Valid RSS] This is a valid RSS feed.

Recommendations

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

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

  1. <?xml version='1.0' encoding='UTF-8' ?>
  2. <rss version="2.0"
  3.    xmlns:atom="http://www.w3.org/2005/Atom"
  4.    xmlns:dc="http://purl.org/dc/elements/1.1/"
  5.    xmlns:sy="http://purl.org/rss/1.0/modules/syndication/">
  6.  
  7. <channel>
  8. <title>Greg's diary</title>
  9. <link>http://www.lemis.com/grog/diary.php</link>
  10. <atom:link href="http://www.lemis.com/grog/diary.xml.php"
  11. rel="self" type="application/rss+xml" />
  12. <description>Greg Lehey's online diary</description>
  13. <dc:creator />
  14. <dc:date>2024-09-28T14:02:58+10:00</dc:date>
  15. <dc:rights>Copyright 2015, 2016, 2017, 2018 Greg Lehey</dc:rights>
  16. <!-- for Emacs, this is a -*- mode: fundamental; coding: utf-8 -*- document -->
  17. <!-- temporary file, entries for last 7 days of previous month, used for RSS version -->
  18.                  
  19. <!-- topic po not selected
  20.      <p>
  21. It's no secret that I have lots of cameras:
  22.      </p>
  23.  
  24.      
  25.      <p>
  26. But I hardly use any of them.  In principle I could get by with the <a href="https://en.wikipedia.org/wiki/Olympus_OM-D_E-M1_Mark_II">Olympus OM-D E-M1 Mark II</a>, but since I have others, it's convenient to use them too.  I use the E-M1 Mark II for
  27. more complicated things, including the weekly <a href="http://www.lemis.com/grog/stones-road/exterior.php">house photos</a>, while I keep the <a href="https://en.wikipedia.org/wiki/Olympus_OM-D_E-M1">OM-D E-M1 Mark I</a> with the
  28. <a href="https://www.dpreview.com/products/olympus/lenses/olympus_12-200_3p5-6p3">M.Zuiko 12-200 mm f/3.5-6.3</a> zoom lens for less demanding photos.  And then there's
  29. the <a href="https://en.wikipedia.org/wiki/Olympus_PEN_E-PM2">E-PM2</a> that I carry
  30. in my handbag for unexpected shots, and <a href="http://www.lemis.com/yvonne/">Yvonne's</a> <a href="https://en.wikipedia.org/wiki/Olympus_OM-D_E-M5_Mark_III">OM-D E-M5 Mark III</a>.
  31.      </p>
  32.  
  33.      <p>
  34. Enough?  Well, of course, but things could be improved.  I have been keeping the E-M1 (Mark
  35. I) in the lounge room for cat photos like this one:
  36.      </p>
  37.  
  38.      
  39.      <p>
  40. Not the best of results.  It was relatively dark, and the lens limited maximum aperture to
  41. f/6.1, requiring 1/5 s at 3200/36° ISO, and I haven't been able to get rid of the colour
  42. artefacts.  I could have got another lens, but then I could have missed the shot, as this
  43. attempt (with flash, only 2 minutes later) shows:
  44.      </p>
  45.  
  46.      
  47.      <p>
  48. What I need is a wide aperture lens.  And of course I have at least two, the <a href="https://www.panasonic.com/au/support/product-archives/lumix-cameras-video-cameras/lumix-g-lenses/h-x025e.html">Leica Summilux 25 mm f/1.4</a> and the <a href="https://www.voigtlaender.de/lenses/mft/25-mm-10-95-nokton-ii/">Voigtländer Nokton 25 mm
  49.        f/0.95</a>.  The Voigtländer has the disadvantage of manual focus, so I chose the
  50.        Summilux.  I just need another camera, and for that I chose the E-PM2, which I replaced in
  51.        my handbag with an <a href="https://en.wikipedia.org/wiki/Olympus_PEN_E-PM1">E-PM1</a>.  And with the Summilux I could have taken the same image (still at 1/6 s, but f/1.4) at
  52.        200/24° ISO.
  53.      </p>
  54.  
  55.      <p>
  56. OK, do that, test:
  57.      </p>
  58.  
  59.      
  60.      <p>
  61. Yes, that works better, but look at that depth of field!
  62.      </p>
  63.  
  64.      <div align="left">
  65.      </div>
  66.  
  67.      <p>
  68. Yvonne's face is in focus, but even the power point, only slightly closer, is clearly fuzzy.
  69. I'll have to pay particular attention to the focus point.
  70.      </p>
  71.      
  72. End deselected topic po (Yet another camera!) -->
  73.  
  74.            
  75. <!-- topic ko not selected
  76.      <p>
  77. Another attempt today at “jing mian” (capital noodles), an attempt to merge <a href="http://www.lemis.com/grog/recipes/Beijing-fried-sauce-noodles.php">Beijing “fried sauce” noodles</a> and
  78. <a href="http://www.lemis.com/grog/recipes/KL-Hokkien-Mee.php">KL Hokkien Mee</a>:
  79.      </p>
  80.  
  81.      
  82.      <p>
  83. Not much difference: forget the <a href="https://en.wikipedia.org/wiki/Michiu">michiu</a>, use less water.  And I'm still not convinced.
  84.      </p>
  85.      
  86. End deselected topic ko (Jing mian again) -->
  87.  
  88.            
  89. <item>
  90. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-aug2024.php#D-20240828-011029</guid>
  91. <link>http://www.lemis.com/grog/diary-aug2024.php?topics=c#D-20240828-011029</link>
  92. <category>technology</category>
  93. <category>opinion</category>
  94. <title>VirtualBox again</title>
  95.  <description>
  96.    <![CDATA[
  97.    <div align="justify">
  98.      <p>
  99. It's been a while since I last tried to use my <a href="https://en.wikipedia.org/wiki/VirtualBox">VirtualBox</a> VMs.  But I have this
  100. <a href="https://en.wikipedia.org/wiki/Ubuntu">Ubuntu</a> system that I installed
  101. <a href="http://www.lemis.com/grog/diary-jun2024.php?subtitle=Ubuntu%20again&amp;article=D-20240623-021811#D-20240623-021811">a couple of months ago</a>, and I wanted to look at the <a href="https://www.x.org/">X</a> fonts.  Fired it up and... no networking!
  102.      </p>
  103.  
  104.      <p>
  105. What went wrong there?  Did I forget to load the <a href="https://en.wikipedia.org/wiki/Loadable_kernel_module">KLDs</a>?  No:
  106.      </p>
  107.  
  108.      <blockquote class="fullwidth">
  109. <div style="text-align:left">
  110.  <tt>
  111. <code><font color="blue">=== root@hydra (/dev/pts/12)</font> <font color="red">~</font> <font color="blue">23</font> &#45;&gt; <b><tt>kldstat | grep vbox</tt></b></code>
  112. <br />&nbsp;6 &nbsp; &nbsp;3 0xffffffff82c14000 &nbsp; &nbsp;590d0 vboxdrv.ko
  113. <br />&nbsp;7 &nbsp; &nbsp;2 0xffffffff82c6e000 &nbsp; &nbsp; 4210 vboxnetflt.ko
  114. <br />10 &nbsp; &nbsp;1 0xffffffff82c82000 &nbsp; &nbsp; 55b0 vboxnetadp.ko
  115. <br />
  116.  </tt>
  117. </div>
  118. </blockquote>
  119.  
  120.      <p>
  121. That's all I need.  Try again with <i>tweedledum</i>, a <a href="https://www.freebsd.org/">FreeBSD</a> machine.  No problems.  And Microsoft?  Fired
  122. up <i>disaster</i> and found:
  123.      </p>
  124.  
  125.      <blockquote class="fullwidth">
  126. <div style="text-align:left">
  127.  <tt>
  128. <code><font color="blue">=== grog@hydra (/dev/pts/10)</font> <font color="red">~</font> <font color="blue">278</font> &#45;&gt; <b><tt>ping disaster</tt></b></code>
  129. <br />PING disaster.lemis.com (192.109.197.168): 56 data bytes
  130. <br />64 bytes from 192.109.197.168: icmp_seq=0 ttl=128 time=0.181 ms
  131. <br />64 bytes from 192.109.197.168: icmp_seq=1 ttl=128 time=0.325 ms
  132. <br />...
  133. <br />
  134.  </tt>
  135. </div>
  136. </blockquote>
  137.  
  138.      <p>
  139. That was the good news.  But somehow it had decided to perform an update, something that I
  140. definitely didn't want.  And when that was done, networking had gone away!
  141.      </p>
  142.  
  143.      <blockquote class="fullwidth">
  144. <div style="text-align:left">
  145.  <tt>
  146. <code><font color="blue">=== grog@hydra (/dev/pts/10)</font> <font color="red">~</font> <font color="blue">281</font> &#45;&gt; <b><tt>ping disaster</tt></b></code>
  147. <br />PING disaster.lemis.com (192.109.197.168): 56 data bytes
  148. <br />^C
  149. <br />&#45;&#45;&#45; disaster.lemis.com ping statistics &#45;&#45;&#45;
  150. <br />3 packets transmitted, 0 packets received, 100.0% packet loss
  151. <br /><code><font color="blue">=== grog@hydra (/dev/pts/10)</font> <font color="red">~</font> <font color="blue">282</font> &#45;&gt; <b><tt>arp disaster</tt></b></code>
  152. <br />disaster.lemis.com (192.109.197.168) at 08:00:27:d4:23:94 on re0 expires in 1199 seconds [ethernet]
  153. <br />
  154.  </tt>
  155. </div>
  156. </blockquote>
  157.  
  158.      <p>
  159. And somehow <i>arp(8)</i> kept showing expiry times of 1200 or 1199 seconds, suggesting that
  160. there had been some activity.  Yes: <i>tcpdump(8)</i> showed continuous
  161.      </p>
  162.  
  163.      <blockquote class="fullwidth">
  164. <div style="text-align:left">
  165.  <tt>
  166. 15:36:07.573601 ARP, Request who&#45;has eureka.lemis.com tell disaster.lemis.com, length 46
  167. <br />15:36:07.573605 ARP, Reply eureka.lemis.com is&#45;at bc:5f:f4:c9:9b:bf (oui Unknown), length 28
  168. <br />
  169.  </tt>
  170. </div>
  171. </blockquote>
  172.  
  173.      <p>
  174. Clearly <i>disaster</i> isn't receiving the reply from <i>eureka</i>.  I've <a href="http://www.lemis.com/grog/diary-jun2024.php?subtitle=More%20Microsoft%20on%20VirtualBox%20investigation&amp;article=D-20240626-012332#D-20240626-012332">seen this before</a>.  What did I do then?  Gave up.
  175.      </p>
  176.  
  177.      <p>
  178. Somehow there's something very strange about VirtualBox networking.  All the problems I have
  179. are also network-related.
  180.      </p>
  181.      </div>
  182.    ]]>
  183.  </description>
  184.  <dc:creator>Greg Lehey</dc:creator>
  185.  <dc:date>2024-08-28T01:10:29+00:00</dc:date>
  186. </item>
  187.  
  188.            
  189. <!-- topic ao not selected
  190.      <p>
  191. Clearly this horribly expensive “natural rat bait” doesn't kill rats.  There are plenty of
  192. people who specialize in that, so did a web search and called up <a href="https://www.southernandbeyondpc.com/">Southern and Beyond pest control</a> in
  193. <a href="https://en.wikipedia.org/wiki/Sebastopol,_Victoria">Sebastopol</a>, mainly
  194. because they're the closest.  The prognosis is not good: they'd just put in rat bait, though
  195. presumably the more effective poisonous kind.
  196.      </p>
  197.  
  198.      <p>
  199. I can do that too, of course.  But yes, they confirmed that the poison can kill cats who eat
  200. the dead rats.  But they can't get up into the ceiling.  Never mind, maybe the rats come
  201. down from time to time.  That would explain the droppings in the garage, and of course the
  202. cats' great interest in the garage.
  203.      </p>
  204.  
  205.      <p>
  206. So: I'm no further.  How about a rat version of the cage that I have somewhere, and in which
  207. I once caught a mouse?  Oh.  I also once had a rat cage and <a href="http://www.lemis.com/grog/diary-jul2011.php?subtitle=Caught%20a%20rat&amp;article=D-20110727-010407#D-20110727-010407">caught a rat</a> in it:
  208.      </p>
  209.  
  210.            
  211.      <p>
  212. Where is the cage?  That was 13 years ago, and I can't recall having seen it since.  Still,
  213. I should be able to find a new one.
  214.      </p>
  215.      
  216. End deselected topic ao (Begone foul rat) -->
  217.  
  218.            
  219. <item>
  220. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-aug2024.php#D-20240828-024028</guid>
  221. <link>http://www.lemis.com/grog/diary-aug2024.php?topics=c#D-20240828-024028</link>
  222. <category>multimedia</category>
  223. <category>technology</category>
  224. <category>opinion</category>
  225. <title>Chasing down the video flashing</title>
  226.  <description>
  227.    <![CDATA[
  228.    <div align="justify">
  229.      <p>
  230. Another video with “flashing” this evening, this time not from <a href="https://en.wikipedia.org/wiki/ZDF">ZDF</a> but from <a href="https://en.wikipedia.org/wiki/ARD_(broadcaster)">ARD</a>.  Just what <a href="http://www.lemis.com/grog/diary-aug2024.php?topics=tc&amp;subtitle=More%20system%20upgrades&amp;article=D-20240814-012416#D-20240814-012416">I've been waiting for</a>.  Switch over to server <tt>1:</tt>, running the <i>nv</i>
  231. driver and not the <i>nvidia</i> driver, view the same video at the same position.  It
  232. flashes!
  233.      </p>
  234.  
  235.      <p>
  236. Oh.  That's not what I had expected.  But at least I have eliminated one potential culprit.
  237. What am I left with?  It only ever happens on my TV and with some (mainly older) German
  238. videos.  So we're left with three potential culprits: my <a href="https://hisense.com.au/product/55-uhd-4k-tv-series-a7g/">Hisense A7G</a> TV, the
  239. German videos and <a href="https://en.wikipedia.org/wiki/mpv_(media_player)">mpv</a>, the video player.  At least two of them must be in collusion, but which?  I suppose I
  240. should install an unrelated video player (so <a href="https://en.wikipedia.org/wiki/MPlayer">MPlayer</a> is eliminated) and see if that
  241. helps.
  242.      </p>
  243.      </div>
  244.    ]]>
  245.  </description>
  246.  <dc:creator>Greg Lehey</dc:creator>
  247.  <dc:date>2024-08-28T02:40:28+00:00</dc:date>
  248. </item>
  249.  
  250.                  
  251. <item>
  252. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-aug2024.php#D-20240829-023448</guid>
  253. <link>http://www.lemis.com/grog/diary-aug2024.php?topics=c#D-20240829-023448</link>
  254. <category>technology</category>
  255. <category>opinion</category>
  256. <title>More VirtualBox fun</title>
  257.  <description>
  258.    <![CDATA[
  259.    <div align="justify">
  260.      <p>
  261. <a href="http://www.lemis.com/grog/diary-aug2024.php?subtitle=VirtualBox%20again&amp;article=D-20240828-011029#D-20240828-011029">Yesterday</a> I was left with puzzles about the networking of my <a href="https://en.wikipedia.org/wiki/VirtualBox">VirtualBox</a> VMs.  Today I tried to track
  262. it down.
  263.      </p>
  264.  
  265.      <p>
  266. I failed.  Everything just worked.  So what went wrong yesterday?  I discovered that today I
  267. had booted from the “<a href="https://en.wikipedia.org/wiki/DVD">DVD</a>”, but that
  268. shouldn't have made any difference.  OK, reinstall.
  269.      </p>
  270.  
  271.      <p>
  272. And how about that, it installed a second copy of Ubuntu with differences that I don't
  273. understand.  But the networking continued to be available, and with a bit of messing around
  274. I was able to install such basics as <i>ifconfig</i>, <i>rwhod</i> and <a href="https://en.wikipedia.org/wiki/Network_File_System">NFS</a>.  Now I can look at those
  275. <a href="https://www.x.org/">X</a> fonts.
  276.      </p>
  277.  
  278.      <p>
  279. Oh.  Once <a href="https://en.wikipedia.org/wiki/Linux">Linux</a> and <a href="https://www.freebsd.org/">FreeBSD</a> had relatively similar file hierarchies, but no
  280. longer.  I wasn't even able to establish if the X server logged anywhere; certainly the way
  281. it was started looked very different:
  282.      </p>
  283.  
  284.      <blockquote class="fullwidth">
  285. <div style="text-align:left">
  286.  <tt>
  287. &nbsp;&nbsp; &nbsp; &nbsp;1 &nbsp; &nbsp;1651 &nbsp; &nbsp;1651 &nbsp; &nbsp;1651 ? &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &#45;1 Ssl &nbsp; &nbsp; &nbsp;0 &nbsp; 0:00 /usr/sbin/gdm3
  288. <br />&nbsp;&nbsp; 1651 &nbsp; &nbsp;1657 &nbsp; &nbsp;1651 &nbsp; &nbsp;1651 ? &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &#45;1 Sl &nbsp; &nbsp; &nbsp; 0 &nbsp; 0:00 &nbsp;\_ gdm&#45;session&#45;worker [pam/gdm&#45;autologin]
  289. <br />&nbsp;&nbsp; 1657 &nbsp; &nbsp;1700 &nbsp; &nbsp;1700 &nbsp; &nbsp;1700 tty2 &nbsp; &nbsp; &nbsp; &nbsp;1700 Ssl+ &nbsp;1000 &nbsp; 0:00 &nbsp; &nbsp; &nbsp;\_ /usr/libexec/gdm&#45;x&#45;session &#45;&#45;run&#45;script env GNOME_SHELL_SESSION_MODE=ubuntu /usr/bin/gnome&#45;session &#45;&#45;session=ubuntu
  290. <br />&nbsp;&nbsp; 1700 &nbsp; &nbsp;1704 &nbsp; &nbsp;1700 &nbsp; &nbsp;1700 tty2 &nbsp; &nbsp; &nbsp; &nbsp;1700 Sl+ &nbsp; 1000 &nbsp; 0:02 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;\_ /usr/lib/xorg/Xorg vt2 &#45;displayfd 3 &#45;auth /run/user/1000/gdm/Xauthority &#45;nolisten tcp &#45;background none &#45;noreset &#45;keeptty &#45;novtswitch &#45;verbose 3
  291. <br />&nbsp;&nbsp; 1700 &nbsp; &nbsp;1754 &nbsp; &nbsp;1700 &nbsp; &nbsp;1700 tty2 &nbsp; &nbsp; &nbsp; &nbsp;1700 Sl+ &nbsp; 1000 &nbsp; 0:00 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;\_ /usr/libexec/gnome&#45;session&#45;binary &#45;&#45;session=ubuntu
  292. <br />
  293.  </tt>
  294. </div>
  295. </blockquote>
  296.  
  297.      <p>
  298. But after some searching found a directory <i>/usr/share/fonts</i>, which appears to have
  299. the kind of fonts I was looking for.  Where do I put
  300. them?  <i>/usr/local/share/fonts/Ubuntu/</i> for the time being.  Then to review the current
  301. way of making them visible to X, another thing that I have forgotten.
  302.      </p>
  303.      </div>
  304.    ]]>
  305.  </description>
  306.  <dc:creator>Greg Lehey</dc:creator>
  307.  <dc:date>2024-08-29T02:34:48+00:00</dc:date>
  308. </item>
  309.  
  310.                  
  311. <item>
  312. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-aug2024.php#D-20240830-004507</guid>
  313. <link>http://www.lemis.com/grog/diary-aug2024.php?topics=c#D-20240830-004507</link>
  314. <category>technology</category>
  315. <category>opinion</category>
  316. <title>X font progress</title>
  317.  <description>
  318.    <![CDATA[
  319.    <div align="justify">
  320.      <p>
  321. So now I have the <a href="https://en.wikipedia.org/wiki/Ubuntu">Ubuntu</a> <a href="https://www.x.org/">X</a> fonts in <i>/usr/local/share/fonts/Ubuntu/</i>.
  322. How do I tell X about them?  There used to be something you needed to do, but I forget.
  323.      </p>
  324.  
  325.      <p>
  326. What I <a href="http://www.lemis.com/grog/diary-oct2023.php?subtitle=Fonts:%20Microsoft%20beats%20X!&amp;article=D-20231029-012114#D-20231029-012114">did recall</a> was the <a href="https://www.gnu.org/software/emacs/"><i>Emacs</i></a> function <tt>view-hello-file</tt>, which shows the expression for
  327. “Hello” in many languages and scripts.  Last October it showed, inter alia,
  328.      </p>
  329.  
  330.        <a id="Photo-0" name="Photo-0"
  331.          href="diary-aug2024.php?dirdate=20231028&amp;imagesizes=2&amp;topics=c#Photo-0">
  332.          <img alt="This should be Emacs-fonts.png.  Is it missing?" border="0" id="Photo_0"
  333.               title="Photo Emacs-fonts.png.  Click to redisplay larger version of image."
  334.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20231028/small/Emacs-fonts.png"
  335.               width="480" height="141"
  336.           /></a>
  337.  
  338.      <p>
  339. Check up.  The fonts are all there!  Well, nearly all of them.  <a href="https://en.wikipedia.org/wiki/Makasar_script">Makasar</a> is still not there, possibly
  340. also not on Ubuntu.  In fact, it's not even there in older versions of <i>Emacs</i>.
  341. Nothing to worry about right yet.
  342.      </p>
  343.  
  344.      <p>
  345. It almost seems that I just needed to put the fonts in the directory hierarchy and the
  346. clients find them automatically.  Even <a href="https://de.quora.com/Den-deutschen-Substantiven-H%C3%B6he-F%C3%A4che-Tiefe-entspricht-im-Niederl%C3%A4ndischen-hoogte-vlakte-diepte-Ist-hier-im-Deutschen-ein-t-ausgefallen/answer/Stefan-Speck-1">Stefan Speck's Gothic examples</a> are represented.  And the saved email messages that I
  347. commented about <a href="http://www.lemis.com/grog/diary-oct2023.php?subtitle=More%20font%20pain&amp;article=D-20231028-041128#D-20231028-041128">earlier</a> also render correctly.  Only <a href="https://www.mozilla.org/firefox"><i>firefox</i></a> didn't.  Oh.  Restart it, and that worked too.
  348.      </p>
  349.  
  350.      <p>
  351. Great.  Copy the fonts to my other machines and continue.  But at this point, <i>Emacs</i>
  352. on <i>eureka</i> crashed:
  353.      </p>
  354.  
  355.      <blockquote class="fullwidth">
  356. <div style="text-align:left">
  357.  <tt>
  358. <code><font color="blue">=== grog@eureka (/dev/pts/8)</font> <font color="red">~</font> <font color="blue">3</font> &#45;&gt; <b><tt></tt></b></code>
  359. <br />Backtrace:
  360. <br />0x51126e &lt;???&gt; at /usr/local/bin/emacs
  361. <br />0x50fc33 &lt;???&gt; at /usr/local/bin/emacs
  362. <br />0x802a38b6a &lt;pthread_sigmask+0x51a&gt; at /lib/libthr.so.3
  363. <br />0x802a3824c &lt;pthread_getspecific+0xe1c&gt; at /lib/libthr.so.3
  364. <br />emacs &#45;display hydra:0.2 &amp;
  365. <br />[3] 15695
  366. <br />You have new mail in /var/mail/grog
  367. <br />[1] &nbsp; Segmentation fault &nbsp; &nbsp; &nbsp;(core dumped) emacs public_html/diary.php
  368. <br /><code><font color="blue">=== grog@eureka (/dev/pts/8)</font> <font color="red">~</font> <font color="blue">4</font> &#45;&gt; <b><tt></tt></b></code>
  369. <br />
  370.  </tt>
  371. </div>
  372. </blockquote>
  373.  
  374.      <p>
  375. It kept on crashing.  After some examination, it seems that the fonts were to blame.  Remove
  376. them and all was well.  It didn't happen on the other systems, so I assume that the system
  377. on <i>eureka</i> was just too old.  Still, a great improvement.
  378.      </p>
  379.      </div>
  380.    ]]>
  381.  </description>
  382.  <dc:creator>Greg Lehey</dc:creator>
  383.  <dc:date>2024-08-30T00:45:07+00:00</dc:date>
  384. </item>
  385.  
  386.            
  387. <!-- topic g not selected
  388.      <p>
  389. Seen while walking the dogs today:
  390.      </p>
  391.  
  392.            
  393.      <p>
  394. Particularly the first one, with a <a href="https://en.wikipedia.org/wiki/Grevillea_rosmarinifolia">Grevillea rosmarinifolia</a> and some unspecified <a href="https://en.wikipedia.org/wiki/Acacia">Acacia</a>,
  395. caught my eye.
  396.      </p>
  397.      
  398. End deselected topic g (Spring on its way) -->
  399.  
  400.            
  401. <item>
  402. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-aug2024.php#D-20240830-021500</guid>
  403. <link>http://www.lemis.com/grog/diary-aug2024.php?topics=c#D-20240830-021500</link>
  404. <category>technology</category>
  405. <title>hydra crash</title>
  406.  <description>
  407.    <![CDATA[
  408.    <div align="justify">
  409.      <p>
  410. For no particularly good reason, I ran <i>nmap</i> against my /24 today.  <i>hydra</i>
  411. crashed!  It's not clear why; there was no evidence of a dump or anything.  But somehow it's
  412. another indication that all is not well with the networking, and this time <a href="https://en.wikipedia.org/wiki/VirtualBox">VirtualBox</a> wasn't involved.
  413.      </p>
  414.      </div>
  415.    ]]>
  416.  </description>
  417.  <dc:creator>Greg Lehey</dc:creator>
  418.  <dc:date>2024-08-30T02:15:00+00:00</dc:date>
  419. </item>
  420.  
  421.            
  422. <item>
  423. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-aug2024.php#D-20240830-021914</guid>
  424. <link>http://www.lemis.com/grog/diary-aug2024.php?topics=c#D-20240830-021914</link>
  425. <category>technology</category>
  426. <category>general</category>
  427. <category>opinion</category>
  428. <title>PoS pain</title>
  429.  <description>
  430.    <![CDATA[
  431.    <div align="justify">
  432.      <p>
  433. <a href="http://www.lemis.com/yvonne/">Yvonne</a> forgot some things on her shopping trip yesterday, and
  434. she was going to go in again today to pick up the remainder.  But some of the purchases, at
  435. the <a href="https://www.facebook.com/Fruits.shack.Wendouree/">Fruit Shack</a>, were
  436. things that I was interested in choosing, so I went instead.
  437.      </p>
  438.  
  439.      <p>
  440. First to <a href="https://en.wikipedia.org/wiki/Bunnings">Bunnings</a> in <a href="https://en.wikipedia.org/wiki/Delacombe">Delacombe</a> to look at rat traps, and only
  441. remembered that I had looked online yesterday and decided that they were far too expensive
  442. (by a factor of 2 to 3).  On to the Fruit Shack, passing <a href="https://en.wikipedia.org/wiki/ALDI">ALDI</a> on the way, so did the remainder of the
  443. shopping there.
  444.      </p>
  445.  
  446.      <p>
  447. ALDI has self-serve checkout, and I've used <a href="http://www.lemis.com/grog/diary-sep2023.php?subtitle=ALDI%20self-checkout&amp;article=D-20230907-021810#D-20230907-021810">it in the past</a>.  But this time it really showed itself from its worst side.  I tried
  448. to pay with “savings”, and it went through the whole rigmarole, including <a href="https://en.wikipedia.org/wiki/Personal_identification_number">PIN</a> entry and card
  449. removal, before declining the transaction: no linked “savings” account.  And as punishment I
  450. couldn't choose anything else.  I needed an assistant to come and reset something.
  451.      </p>
  452.  
  453.      <p>
  454. OK, start paying.  “INACTIVITY TIMEOUT”.  Another assistant, who stayed there long enough to
  455. see a second timeout.
  456.      </p>
  457.  
  458.        <a id="Photo-1" name="Photo-1"
  459.          href="diary-aug2024.php?dirdate=20240829&amp;imagesizes=12&amp;topics=c#Photo-1">
  460.          <img alt="This should be ALDI-receipt.png.  Is it missing?" border="0" id="Photo_1"
  461.               title="Photo ALDI-receipt.png.  Click to redisplay larger version of image."
  462.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20240829/small/ALDI-receipt.png"
  463.               width="276" height="245"
  464.           /></a>
  465.  
  466.      <p>
  467. How long were the timeouts?  30 seconds at the most, possibly only 10 or 15.  Finally I paid
  468. by credit card, accepting their 0.5% surcharge.  And as a bonus security measure, the
  469. printout included my PIN in plain text, displayed as “Card number”.  My guess is that
  470. they're still trying to debug the device.
  471.      </p>
  472.      </div>
  473.    ]]>
  474.  </description>
  475.  <dc:creator>Greg Lehey</dc:creator>
  476.  <dc:date>2024-08-30T02:19:14+00:00</dc:date>
  477. </item>
  478.  
  479.                  
  480. <!-- topic aho not selected
  481.      <p>
  482. We've had <a href="http://www.lemis.com/grog/Albums/Animals/Bruno.php">Bruno</a> for nearly 1½ years
  483. now, and <a href="http://www.lemis.com/grog/Albums/Animals/Mona.php">Mona</a> for over 4 months.
  484. They've been particularly in our sights because they're not allowed outside (though Bruno
  485. keeps escaping for up to a minute or two).
  486.      </p>
  487.  
  488.      <p>
  489. I think we made a mistake when we got Mona: we put both cats in the lounge room overnight to
  490. accustomize them to each other.  That works, but how do we now move them to the laundry,
  491. where we really want to keep them?  If we do that, it won't be in the immediate future.  And
  492. in particular <a href="http://www.lemis.com/grog/Albums/Animals/Bruno.php">Bruno</a> seems unhappy.
  493. Though they lie together at lot of the time, he wakes up frequently and meows loudly.
  494.      </p>
  495.  
  496.      <p>
  497. What should we do?  He used to sleep in <a href="http://www.lemis.com/yvonne/">Yvonne's</a> bedroom, in
  498. a cage to keep him from annoying her.  Would he be happy in my bedroom, without a cage?
  499. Maybe, but there's still the annoyance factor.  I tried it with the expected outcome: he was
  500. happy for a while, but then started investigating things.  After a while I decided against
  501. it and put him outside again.
  502.      </p>
  503.  
  504.      <p>
  505. That didn't last long.  Round 4:00 he was meowing again.  OK, into the garage?  Yes, please.
  506. For another couple of hours, and then he meowed again, proving in the process that the
  507. garage isn't overly sound-proof.
  508.      </p>
  509.  
  510.      <p>
  511. We're still not there, but it would be interesting to understand <i>why</i> he's so unhappy.
  512. Clearly the cats wake relatively early, 5:00 or so, when I frequently find them in front of
  513. the bedroom door.  And their interest in the garage suggests that there could be mice in
  514. there.  Can I leave them in there overnight?
  515.      </p>
  516.      
  517. End deselected topic aho (Cat insight) -->
  518.  
  519.            
  520. <item>
  521. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-aug2024.php#D-20240831-020026</guid>
  522. <link>http://www.lemis.com/grog/diary-aug2024.php?topics=c#D-20240831-020026</link>
  523. <category>technology</category>
  524. <category>photography</category>
  525. <title>More Microsoft insights</title>
  526.  <description>
  527.    <![CDATA[
  528.    <div align="justify">
  529.      <p>
  530. Did some photo processing today.  Try to fire up <i>distress</i>.  Nothing happened.
  531.      </p>
  532.  
  533.      <p>
  534. That's from an <a href="https://en.wikipedia.org/wiki/fvwm"><i>fvwm</i></a> menu,
  535. which, like all such things, is too polite to complain.  Try starting the underlying script:
  536.      </p>
  537.  
  538.      <blockquote class="fullwidth">
  539. <div style="text-align:left">
  540.  <tt>
  541. <code><font color="blue">=== grog@hydra (/dev/pts/11)</font> <font color="red">~</font> <font color="blue">8</font> &#45;&gt; <b><tt>/home/local/bin/dordesktop distress 3790x2110+0</tt></b></code>
  542. <br />Connecting to distress
  543. <br />
  544. <br />ATTENTION! Found a certificate stored for host 'distress', but it does not match the certificate
  545. <br />received from server.
  546. <br />Review the following certificate info before you trust it to be added as an exception.
  547. <br />If you do not trust the certificate the connection atempt will be aborted:
  548. <br />
  549. <br />&nbsp;&nbsp; &nbsp;Subject: CN=distress
  550. <br />&nbsp;&nbsp; &nbsp; Issuer: CN=distress
  551. <br />&nbsp;Valid From: Thu Aug 29 09:44:00 2024
  552. <br />&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; To: Fri Feb 28 10:44:00 2025
  553. <br />
  554. <br />&nbsp;&nbsp;Certificate fingerprints:
  555. <br />
  556. <br />&nbsp;&nbsp; &nbsp; &nbsp; sha1: 6997782949cdf6f8e1db8a8056ebb46ae4506d11
  557. <br />&nbsp;&nbsp; &nbsp; sha256: 09225dcd1ca45eba670dfd3ac99f3271e4ea23bc4bce9b737f77a7109f16723a
  558. <br />
  559. <br />Do you trust this certificate (yes/no)? <b>yes</b>
  560. <br />
  561.  </tt>
  562. </div>
  563. </blockquote>
  564.  
  565.      <p>
  566. And after that things ran normally.  That must have something to do with <a href="http://www.lemis.com/grog/diary-aug2024.php?subtitle=hydra%20crash&amp;article=D-20240830-021500#D-20240830-021500">yesterday's crash</a>.  But where does the certificate come from?  Where is it stored?
  567. Why is it a problem when <i>hydra</i> reboots?  Why, <i>is</i> it a problem
  568. when <i>hydra</i> reboots?  Yet another borderline issue.
  569.      </p>
  570.      </div>
  571.    ]]>
  572.  </description>
  573.  <dc:creator>Greg Lehey</dc:creator>
  574.  <dc:date>2024-08-31T02:00:26+00:00</dc:date>
  575. </item>
  576.  
  577.            
  578. <!-- topic k not selected
  579.      <p>
  580. I had planned to cook some chicken with this spice paste today:
  581.      </p>
  582.  
  583. `      
  584.      <p>
  585. It requires broccoli, so <a href="http://www.lemis.com/yvonne/">Yvonne</a> had bought some on Wednesday.
  586. But not enough.  So we needed to do something—almost anything—else.  But I had already
  587. prepared the raw chicken, so it had to be something compatible.
  588.      </p>
  589.  
  590.      <p>
  591. To my own surprise, I managed to make <a href="http://www.lemis.com/grog/recipes/chicken-with-cashews.php">chicken with cashew nuts</a>, which I once considered one of my most complicated dishes:
  592.      </p>
  593.  
  594.      
  595.      <p>
  596. About the only thing of interest was a detail in the recipe:
  597.      </p>
  598.  
  599.      <blockquote class="fullwidth">
  600.        <p class="listitemwidth">
  601.  Start 45 minutes before serving.
  602.        </p>
  603.  
  604. <p class="listitemwidth">
  605.  Put the shiitake in boiling water and soak for an hour or more.
  606. </p>
  607.      </blockquote>
  608.  
  609.      <p>
  610. But even that wasn't an issue in my timing.
  611.      </p>
  612.      
  613. End deselected topic k (Recipe refinement) -->
  614.  
  615.                        
  616. <!-- topic aho not selected
  617.      <p>
  618. Over to visit Pene Kirk this morning, and I took the fuzz from the ceiling for a vet's
  619. expert opinion:
  620.      </p>
  621.  
  622.            
  623.      <p>
  624. Her verdict: polyester.  No animal content.  And the dirt in the fuzz was just that, dirt,
  625. not mouse or rat droppings.
  626.      </p>
  627.  
  628.      <p>
  629. Oh.  I suppose that makes sense, though, and it fits with my hypothesis that the rodents
  630. chewed their way through the ducting.  The hole that they would have left is hardly worth
  631. worrying about.  And Pene still didn't have a good solution to how to get rid of them (“good
  632. luck then”).  She had used rat bait, but only because she knows that her cats wouldn't get
  633. near them.
  634.      </p>
  635.      
  636. End deselected topic aho (Rats in the roof: Pene's verdict) -->
  637.  
  638.            
  639. <item>
  640. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-aug2024.php#D-20240901-023712</guid>
  641. <link>http://www.lemis.com/grog/diary-aug2024.php?topics=c#D-20240901-023712</link>
  642. <category>technology</category>
  643. <category>opinion</category>
  644. <title>Skittish rodents?</title>
  645.  <description>
  646.    <![CDATA[
  647.    <div align="justify">
  648.      <p>
  649. We've had enough issues with mice and rats in the house lately, but there are more.  One of
  650. the many outstanding issues in my transition to <i>hydra</i> is the mouse: for reasons I
  651. don't understand, it seems to work intermittently.  When marking text (left button down,
  652. move the mouse) it seems to reset the start point from time to time.
  653.      </p>
  654.  
  655.      <p>
  656. My fault?  I was beginning to think so, but lately there has been a second issue: suddenly
  657. the mouse pointer will jump <i>to another screen</i>.  That's not my fault, but whose fault
  658. is it?  The mouse?  <a href="https://www.x.org/">X</a>?  The <a href="https://en.wikipedia.org/wiki/Nvidia">Nvidia</a> driver?  Even potentially <a href="https://en.wikipedia.org/wiki/fvwm">fvwm</a>?
  659.      </p>
  660.      </div>
  661.    ]]>
  662.  </description>
  663.  <dc:creator>Greg Lehey</dc:creator>
  664.  <dc:date>2024-09-01T02:37:12+00:00</dc:date>
  665. </item>
  666.  
  667.            
  668. <item>
  669. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-aug2024.php#D-20240901-024029</guid>
  670. <link>http://www.lemis.com/grog/diary-aug2024.php?topics=c#D-20240901-024029</link>
  671. <category>technology</category>
  672. <category>photography</category>
  673. <category>opinion</category>
  674. <title>distress despair</title>
  675.  <description>
  676.    <![CDATA[
  677.    <div align="justify">
  678.      <p>
  679. <a href="http://www.lemis.com/grog/stones-road/exterior.php">House photo</a> day today, involving lots
  680. of processing.  And <i>distress</i>, my Microsoft 10 box, decided that it wanted to reboot.
  681. OK, what the hell, though I hate being told what to do.  But after rebooting, things didn't
  682. work normally.  <a href="https://www.dxo.com/dxo-photolab/">DxO PhotoLab</a> isn't a
  683. ball of fire at the best of times, but now it just hung.  And other photo software wasn't
  684. much better.
  685.      </p>
  686.  
  687.      <p>
  688. Bloody Microsoft!  While waiting for that, start processing on <i>dischord</i>, a Microsoft
  689. 7 box.  It was also glacially slow!  What's wrong with these things?  <a href="https://en.wikipedia.org/wiki/Samba_(software)">Samba</a>?  How do you connect these
  690. things?  Wasn't there some program I could use to test connectivity?
  691. <i>smbclient</i>?  Is  <i>eureka</i> even active?  Check from <i>hydra</i>.  Hang:
  692.      </p>
  693.  
  694.      <blockquote class="fullwidth">
  695. <div style="text-align:left">
  696.  <tt>
  697. <code><font color="blue">=== root@hydra (/dev/pts/4)</font> <font color="red">~</font> <font color="blue">20</font> &#45;&gt; <b><tt>ps lt11</tt></b></code>
  698. <br />&nbsp;UID &nbsp; PID &nbsp;PPID &nbsp;C PRI NI &nbsp; VSZ &nbsp;RSS MWCHAN STAT TT &nbsp; &nbsp; TIME COMMAND
  699. <br />1004 70313 18824 25 &nbsp;20 &nbsp;0 13344 2956 <b>nfs</b> &nbsp; &nbsp;D+ &nbsp; 11 &nbsp;0:00.00 ls C
  700. <br />
  701.  </tt>
  702. </div>
  703. </blockquote>
  704.  
  705.      <p>
  706. Oh.  Whatever it is, it's not Microsoft's fault.  But clearly <i>eureka</i> was up, so I
  707. checked there.  Hang:
  708.      </p>
  709.  
  710.      <blockquote class="fullwidth">
  711. <div style="text-align:left">
  712.  <tt>
  713. <code><font color="blue">=== grog@eureka (/dev/pts/16)</font> <font color="red">~</font> <font color="blue">1</font> &#45;&gt; <b><tt>ps lt6</tt></b></code>
  714. <br />&nbsp;UID &nbsp; PID &nbsp;PPID CPU PRI NI &nbsp; VSZ &nbsp;RSS MWCHAN STAT TT &nbsp; &nbsp; TIME COMMAND
  715. <br />1004 &nbsp;5266 43366 &nbsp; 0 &nbsp;20 &nbsp;0 16888 2476 <b>suspfs</b> D+ &nbsp; &nbsp;6 &nbsp;0:00.00 ls &#45;lbL, /Photos/
  716. <br />
  717.  </tt>
  718. </div>
  719. </blockquote>
  720.  
  721.      <p>
  722. Oh.  More and more, it became clear that the disk was not accessible.  No error messages,
  723. just a hang.  Force unmount?  That hung the entire system.  Big red button time, and the
  724. third reboot in <a href="http://www.lemis.com/grog/diary-aug2024.php?subtitle=hydra%20crash&amp;article=D-20240830-021500#D-20240830-021500">3 days</a>      </p>
  725.  
  726.      <p>
  727. And fortunately the disk came up again.  But it's clear that it's time to replace the disk.
  728. I've had it up and running for <a href="http://www.lemis.com/grog/diary-jun2017.php?subtitle=New%20disk%20at%20last&amp;article=D-20170626-000457#D-20170626-000457">over 7 years</a>.  I had wanted to wait until the price of big <a href="https://en.wikipedia.org/wiki/SSD">SSDs</a> dropped, but I don't think I can wait that
  729. long, so it's a new magnetic disk for me.  12 TB?  16 TB?  The prices aren't bad, but
  730. strangely backup disks are more expensive.  I need to think how to handle that.
  731.      </p>
  732.  
  733.      <p>
  734. And apart from that, most things came up well.  Only my weather station software didn't.  It
  735. kept reporting “MySQL server has gone away”, which was no longer the case.  But it seems it
  736. doesn't handle that situation, so I needed to restart it.
  737.      </p>
  738.  
  739.      <p>
  740. And then <i>distress</i> told me that “drive” <b>P:</b> was disconnected.  How do you
  741. reconnect it?  I still don't know: surprisingly, it recovered by itself.
  742.      </p>
  743.      </div>
  744.    ]]>
  745.  </description>
  746.  <dc:creator>Greg Lehey</dc:creator>
  747.  <dc:date>2024-09-01T02:40:29+00:00</dc:date>
  748. </item>
  749.  
  750.            
  751.            
  752. <!-- topic ko not selected
  753.      <p>
  754. <a href="http://www.lemis.com/grog/recipes/beef-with-orange.php">Beef with orange and broccoli</a> for dinner
  755. today.  I had forgotten how much work it is, and in the process a number of improvements
  756. occurred to me.
  757.      </p>
  758.  
  759.      <p>
  760. But the result was disappointing.  Not because of the work, but because of new sources of
  761. ingredients.  <a href="http://www.lemis.com/grog/diary-jan2022.php?subtitle=Beef%20with%20broccoli%20and%20orange&amp;article=D-20220123-012016#D-20220123-012016">Previously</a> I had made it with this orange peel, which I had found surprisingly small:
  762.      </p>
  763.  
  764.      
  765.      <p>
  766. But we had run out of that, and the new stuff looks like this:
  767.      </p>
  768.  
  769.            
  770.      <p>
  771. In addition, I had bought some “sizzle steak” (and not “sizzling steak”, the term that
  772. <a href="https://en.wikipedia.org/wiki/Woolworths_Supermarkets">Woolworths</a> use)
  773. from <a href="https://en.wikipedia.org/wiki/ALDI">ALDI</a>:
  774.      </p>
  775.  
  776.      
  777.      <p>
  778. It looks nice, marbled and natural, unlike the steak from Woolworths, and it's also more
  779. expensive than the Woolworths' offering.  But it's <i>tough</i>!  And the orange peel is
  780. also “tough”: it clearly needs soaking before use.  The result was a somewhat disappointing
  781. meal.
  782.      </p>
  783.      
  784. End deselected topic ko (Dinner gone wrong) -->
  785.  
  786.                  
  787. <item>
  788. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2024.php#D-20240903-015753</guid>
  789. <link>http://www.lemis.com/grog/diary-sep2024.php?topics=c#D-20240903-015753</link>
  790. <category>technology</category>
  791. <category>opinion</category>
  792. <title>Where did all my disk space go?</title>
  793.  <description>
  794.    <![CDATA[
  795.    <div align="justify">
  796.      <p>
  797. My nightly backups have another surprise in store:
  798.      </p>
  799.  
  800.      <blockquote class="fullwidth">
  801. <div style="text-align:left">
  802.  <tt>
  803. Filesystem &nbsp;1M&#45;blocks &nbsp; &nbsp; &nbsp;Used &nbsp; Avail Capacity &nbsp;Mounted on
  804. <br />/dev/da0p1 &nbsp;7,630,093 7,630,043 &#45;76,250 &nbsp; 101% &nbsp; &nbsp;/videobackup
  805. <br />tiwi:/spool 7,567,870 7,423,744 &nbsp;68,447 &nbsp; &nbsp;99% &nbsp; &nbsp;/spool
  806. <br />
  807.  </tt>
  808. </div>
  809. </blockquote>
  810.  
  811.      <p>
  812. <i>videobackup</i> is a copy of <i>tiwi:/spool</i>, made with <a href="https://en.wikipedia.org/wiki/rsync">rsync</a>.  Why the discrepancy?  Off to find
  813. out, and, not surprisingly, discovered a number of files on <i>/videobackup</i> that didn't
  814. get removed when they went away on <i>/spool</i>.  OK, remove them:
  815.      </p>
  816.  
  817.      <blockquote class="fullwidth">
  818. <div style="text-align:left">
  819.  <tt>
  820. <code><font color="blue">=== root@eureka (/dev/pts/0)</font> <font color="red">~</font> <font color="blue">55</font> &#45;&gt; <b><tt>df</tt></b></code>
  821. <br />Filesystem &nbsp;1048576&#45;blocks &nbsp; &nbsp; &nbsp;Used &nbsp; Avail Capacity &nbsp;Mounted on
  822. <br />/dev/da0p1 &nbsp; &nbsp; &nbsp; 7,630,093 7,563,450 &nbsp;&#45;9,658 &nbsp; 100% &nbsp; &nbsp;/videobackup
  823. <br />tiwi:/spool &nbsp; &nbsp; &nbsp;7,567,870 7,420,523 &nbsp;71,668 &nbsp; &nbsp;99% &nbsp; &nbsp;/spool
  824. <br />
  825.  </tt>
  826. </div>
  827. </blockquote>
  828.  
  829.      <p>
  830. How can that happen?  What does <i>du</i> say?
  831.      </p>
  832.  
  833.      <blockquote class="fullwidth">
  834. <div style="text-align:left">
  835.  <tt>
  836. <code><font color="blue">=== root@eureka (/dev/pts/0)</font> <font color="red">~</font> <font color="blue">56</font> &#45;&gt; <b><tt>du &#45;s /videobackup</tt></b></code>
  837. <br />7563451 /videobackup
  838. <br />
  839. <br /><code><font color="blue">=== root@tiwi (/dev/pts/14)</font> <font color="red">~</font> <font color="blue">3</font> &#45;&gt; <b><tt>du &#45;s /spool</tt></b></code>
  840. <br />7573170 /spool
  841. <br />
  842.  </tt>
  843. </div>
  844. </blockquote>
  845.  
  846.      <p>
  847. <i>videobackup</i> usage is as expected, but <i>/spool</i> now has <i>more</i> storage in
  848. use than <i>/videobackup</i>, in fact more than the size of the disk and over 150 GB more
  849. than <i>df</i> shows!  How can that happen?  <i>du</i> doesn't follow <a href="https://en.wikipedia.org/wiki/Symbolic_link">symbolic links</a>.  Is there something
  850. hidden under a mount point?  But nothing is mounted on <i>/spool</i>, and even if it
  851. were, <i>df</i> should have shown the correct values.
  852.      </p>
  853.  
  854.      <p>
  855. What happens if I <i>umount</i> and remount <i>/spool</i>?  Not what I expected: the values
  856. are unchanged, but from all other machines I get:
  857.      </p>
  858.  
  859.      <blockquote class="fullwidth">
  860. <div style="text-align:left">
  861.  <tt>
  862. <code><font color="blue">=== root@lagoon (/dev/pts/7)</font> <font color="red">~</font> <font color="blue">12</font> &#45;&gt; <b><tt>mount tiwi:/spool /spool</tt></b></code>
  863. <br />mount_nfs: nmount: /spool: Stale NFS file handle
  864. <br />
  865.  </tt>
  866. </div>
  867. </blockquote>
  868.  
  869.      <p>
  870. At first I thought it was an issue of processes having the old handle open,
  871. but <i>tiwi:/spool</i> wasn't mounted on <i>lagoon</i> when I remounted it on <i>tiwi</i>.
  872. I wasn't able to solve the problem, and I ended up rebooting <i>tiwi</i>—4 machines rebooted
  873. in 4 days!  How that grates.  And for reasons that I don't understand, <i>tiwi</i> started
  874. <a href="https://www.x.org/">X</a>, but came up without a window manager.  That's
  875. low priority, though: <i>tiwi</i> should go away in the near future, and I don't use the
  876. display.  More to the point, though, the backup disk was <i>still</i> full.  Let's see what
  877. happens with the next backup.
  878.      </p>
  879.      </div>
  880.    ]]>
  881.  </description>
  882.  <dc:creator>Greg Lehey</dc:creator>
  883.  <dc:date>2024-09-03T01:57:53+00:00</dc:date>
  884. </item>
  885.  
  886.            
  887. <item>
  888. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2024.php#D-20240903-024741</guid>
  889. <link>http://www.lemis.com/grog/diary-sep2024.php?topics=c#D-20240903-024741</link>
  890. <category>technology</category>
  891. <category>opinion</category>
  892. <title>Another disk fail?</title>
  893.  <description>
  894.    <![CDATA[
  895.    <div align="justify">
  896.      <p>
  897. Seen in this morning's logs:
  898.      </p>
  899.  
  900.      <blockquote class="fullwidth">
  901. <div style="text-align:left">
  902.  <tt>
  903. Sep &nbsp;2 01:12:21 eureka kernel: (da1:umass&#45;sim1:1:0:0): READ(16). CDB: 88 00 00 00 00 01 22 76 29 a8 00 00 00 08 00 00
  904. <br />Sep &nbsp;2 01:12:21 eureka kernel: (da1:umass&#45;sim1:1:0:0): CAM status: SCSI Status Error
  905. <br />Sep &nbsp;2 01:12:21 eureka kernel: (da1:umass&#45;sim1:1:0:0): SCSI status: Check Condition
  906. <br />Sep &nbsp;2 01:12:21 eureka kernel: (da1:umass&#45;sim1:1:0:0): SCSI sense: ABORTED COMMAND asc:47,3 (Information unit iuCRC error detected)
  907. <br />Sep &nbsp;2 01:12:21 eureka kernel: (da1:umass&#45;sim1:1:0:0): Retrying command (per sense data)
  908. <br />Sep &nbsp;2 01:12:29 eureka kernel: (da1:umass&#45;sim1:1:0:0): READ(16). CDB: 88 00 00 00 00 01 22 76 29 a8 00 00 00 08 00 00
  909. <br />Sep &nbsp;2 01:12:29 eureka kernel: (da1:umass&#45;sim1:1:0:0): CAM status: SCSI Status Error
  910. <br />Sep &nbsp;2 01:12:29 eureka kernel: (da1:umass&#45;sim1:1:0:0): SCSI status: Check Condition
  911. <br />Sep &nbsp;2 01:12:29 eureka kernel: (da1:umass&#45;sim1:1:0:0): SCSI sense: NOT READY asc:4,1 (Logical unit is in process of becoming ready)
  912. <br />Sep &nbsp;2 01:12:29 eureka kernel: (da1:umass&#45;sim1:1:0:0): Polling device for readiness
  913. <br />
  914.  </tt>
  915. </div>
  916. </blockquote>
  917.  
  918.      <p>
  919. That's my “new” 10 GB backup disk, the one I bought <a href="http://www.lemis.com/grog/diary-jun2023.php?subtitle=New%20backup%20disk&amp;article=D-20230610-031120#D-20230610-031120">only a little over a year ago</a>.  Is it failing already?  Presumably it has a warranty
  920. of at least 36 months.  But is it defective?  What does “Information unit iuCRC error
  921. detected” mean?  And the time is suspicious.  From the inverter:
  922.      </p>
  923.  
  924.      <blockquote class="fullwidth">
  925. <div style="text-align:left">
  926.  <tt>
  927.  
  928. <br />tstamp &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Pac &nbsp; &nbsp; Status &nbsp; &nbsp; &nbsp; &nbsp; SOC &nbsp; &nbsp; VBat &nbsp; &nbsp;PacGrid PacBat &nbsp;PacPV &nbsp; FromPV &nbsp;W1
  929. <br />2024&#45;09&#45;02 01:12:54 &nbsp; &nbsp; 1046 &nbsp; &nbsp;Waiting to connect to On&#45;grid &nbsp; 22 &nbsp; &nbsp; &nbsp;254 &nbsp; &nbsp; NULL &nbsp; &nbsp;1100 &nbsp; &nbsp;0 &nbsp; &nbsp; &nbsp; 0 &nbsp; &nbsp; &nbsp; 0
  930. <br />2024&#45;09&#45;02 01:12:55 &nbsp; &nbsp; 873 &nbsp; &nbsp; Off&#45;grid &nbsp; &nbsp; &nbsp; &nbsp;22 &nbsp; &nbsp; &nbsp;254 &nbsp; &nbsp; NULL &nbsp; &nbsp;910 &nbsp; &nbsp; 0 &nbsp; &nbsp; &nbsp; 0 &nbsp; &nbsp; &nbsp; 0
  931. <br />2024&#45;09&#45;02 01:13:00 &nbsp; &nbsp; 515 &nbsp; &nbsp; Off&#45;grid &nbsp; &nbsp; &nbsp; &nbsp;22 &nbsp; &nbsp; &nbsp;255 &nbsp; &nbsp; NULL &nbsp; &nbsp;540 &nbsp; &nbsp; 0 &nbsp; &nbsp; &nbsp; 0 &nbsp; &nbsp; &nbsp; 0
  932. <br />2024&#45;09&#45;02 01:13:01 &nbsp; &nbsp; 520 &nbsp; &nbsp; Off&#45;grid &nbsp; &nbsp; &nbsp; &nbsp;22 &nbsp; &nbsp; &nbsp;255 &nbsp; &nbsp; NULL &nbsp; &nbsp;544 &nbsp; &nbsp; 0 &nbsp; &nbsp; &nbsp; 0 &nbsp; &nbsp; &nbsp; 0
  933. <br />...
  934. <br />2024&#45;09&#45;02 01:13:21 &nbsp; &nbsp; 512 &nbsp; &nbsp; Off&#45;grid &nbsp; &nbsp; &nbsp; &nbsp;21 &nbsp; &nbsp; &nbsp;255 &nbsp; &nbsp; NULL &nbsp; &nbsp;536 &nbsp; &nbsp; 0 &nbsp; &nbsp; &nbsp; 0 &nbsp; &nbsp; &nbsp; 0
  935. <br />2024&#45;09&#45;02 01:13:22 &nbsp; &nbsp; 570 &nbsp; &nbsp; Waiting to connect to On&#45;grid &nbsp; 21 &nbsp; &nbsp; &nbsp;255 &nbsp; &nbsp; NULL &nbsp; &nbsp;594 &nbsp; &nbsp; 0 &nbsp; &nbsp; &nbsp; 0 &nbsp; &nbsp; &nbsp; 0
  936. <br />
  937.  </tt>
  938. </div>
  939. </blockquote>
  940.  
  941.      <p>
  942. That first line is strange; normally it comes <i>after</i> a grid outage, like the last
  943. line.  Presumably this was a transient.
  944.      </p>
  945.  
  946.      <p>
  947. That's quite possible, but there are two issues: firstly, the disk error message was
  948. reported nearly a minute before the outage, and then it repeated at 2:25, when the inverter
  949. had no issues.  On the other hand, <a href="http://www.lemis.com/yvonne/">Yvonne</a> reported two
  950. failures of her bedside clock, one of them round 2:30.  So for the moment it looks as if the
  951. errors are due to flaky power.
  952.      </p>
  953.      </div>
  954.    ]]>
  955.  </description>
  956.  <dc:creator>Greg Lehey</dc:creator>
  957.  <dc:date>2024-09-03T02:47:41+00:00</dc:date>
  958. </item>
  959.  
  960.            
  961. <!-- topic P not selected
  962.      <p>
  963. <a href="http://www.lemis.com/grog/diary-aug2024.php?subtitle=Trump%20running%20scared&amp;article=D-20240805-021238#D-20240805-021238">When I signed up</a> for <a href="https://en.wikipedia.org/wiki/Truth_Social">“Truth” Social</a>, I had to choose 3 people to “follow”.  <a href="https://en.wikipedia.org/wiki/Donald_Trump">Donald Trump</a> was a clear choice, and
  964. to my surprise <a href="https://en.wikipedia.org/wiki/Kamala_Harris">Kamala Harris</a> is there too, so I “followed” her.
  965.      </p>
  966.  
  967.      <p>
  968. And the third?  I was given a list, and the name <tt>catturd2</tt> stuck out, so I followed
  969. him/her.  So far he/she seems to have been the most amusing.  Today I received <a href="https://truthsocial.com/@catturd2/posts/113064580002579108">this image</a>:
  970.      </p>
  971.  
  972.      
  973.      <p>
  974.      </p>
  975.      
  976. End deselected topic P (Trump's hiding place discovered) -->
  977.  
  978.                  
  979. <!-- topic Jho not selected
  980.      <p>
  981. Under the shower this morning, the water seemed cool.  I was able to adjust it to normal
  982. shower temperature, but why did I need to?
  983.      </p>
  984.  
  985.      <p>
  986. Outside to take a look at the hot water system.  Yes, it displayed an error code, <b>E9</b>,
  987. and power cycling didn't make it go away.  What's that?  I've had issues with this unit
  988. <a href="http://www.lemis.com/grog/diary-dec2022.php?subtitle=No%20hot%20water!&amp;article=D-20221215-020200#D-20221215-020200">before</a>, <b>E11</b>, and on that occasion I found the instructions online.  But this
  989. time I couldn't find it.  After all, the unit (apparently a Bosch Compress 3000 DW FOO, or
  990. maybe HP 270-2E0 FOO; why do these things always have two names?) is <a href="http://www.lemis.com/grog/diary-jul2019.php?subtitle=Repairing%20the%20hot%20water%20system&amp;article=D-20190731-023954#Bosch-hot-water">over 5 years old</a>!  But I had the URL of the document, and based on that I was able to
  991. find it locally.
  992.      </p>
  993.  
  994.      <p>
  995. So: <b>E9</b> means “Incorrect system purging or Water pump blocked (water not
  996. recirculating) or Hydraulic circuit blocked (water not recirculating)".  In each case, call
  997. a manufacturer's representative.  OK, call Bosch (1300 30 70 37).  Andrew answered
  998. immediately: it seems that their phone system was down, and he couldn't find the
  999. representative immediately, but he would call back.
  1000.      </p>
  1001.  
  1002.      <p>
  1003. In the meantime, how about Paul of <a href="http://ballaratplumbingservices.com.au/">Ballarat Plumbing Services</a> (0418 527 576), the bloke who installed it.  Yes, could
  1004.        come this afternoon.  Please <a href="https://en.wikipedia.org/wiki/SMS">SMS</a>        details.
  1005.      </p>
  1006.  
  1007.      <p>
  1008. Did that, and how about that, Paul showed up in the afternoon as promised.  He suspected a
  1009. defective pump, but it seems that fortunately it was only clogged with some black gunge,
  1010. which he says is typical of systems run off tank water (why?).  Here the pump in the second
  1011. photo, still bleeding now-clear water:
  1012.      </p>
  1013.  
  1014.            
  1015.      <p>
  1016. But the thing takes hours to get back to temperature, and we won't know for sure until
  1017. tomorrow morning.
  1018.      </p>
  1019.      
  1020. End deselected topic Jho (No hot water!) -->
  1021.  
  1022.            
  1023. <!-- topic go not selected
  1024.      <p>
  1025. I had noted with some disappointment that the wildflower bush that we planted last year
  1026. flowered briefly and then died.  Here a year ago and today:
  1027.      </p>
  1028.  
  1029.            
  1030.      <p>
  1031. That's the collection of twigs in the middle, not the healthy plants around it.  But things
  1032. are looking up:
  1033.      </p>
  1034.  
  1035.      
  1036.      <p>
  1037. Will it come back?  What happened in the first place?
  1038.      </p>
  1039.      
  1040. End deselected topic go (Wildflower recovery?) -->
  1041.  
  1042.      
  1043.            
  1044. <item>
  1045. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2024.php#D-20240904-021441</guid>
  1046. <link>http://www.lemis.com/grog/diary-sep2024.php?topics=c#D-20240904-021441</link>
  1047. <category>technology</category>
  1048. <category>multimedia</category>
  1049. <category>opinion</category>
  1050. <title>Finding the lost disk space</title>
  1051.  <description>
  1052.    <![CDATA[
  1053.    <div align="justify">
  1054.      <p>
  1055. After my concerns about disk space <a href="http://www.lemis.com/grog/diary-sep2024.php?subtitle=Where%20did%20all%20my%20disk%20space%20go?&amp;article=D-20240903-015753#D-20240903-015753">yesterday</a>, the backup ran normally today, and for some reason there was much more
  1056. space available.  Here yesterday, then today, seen from <i>eureka</i>:
  1057.      </p>
  1058.  
  1059.      <blockquote class="fullwidth">
  1060. <div style="text-align:left">
  1061.  <tt>
  1062. Filesystem &nbsp;1M&#45;blocks &nbsp; &nbsp; &nbsp;Used &nbsp; &nbsp; Avail Capacity &nbsp;Mounted on
  1063. <br />/dev/da0p1 &nbsp;7,630,093 7,630,043 &nbsp; &#45;76,250 &nbsp; 101% &nbsp; &nbsp;/videobackup
  1064. <br />tiwi:/spool 7,567,870 7,423,744 &nbsp; &nbsp;68,447 &nbsp; &nbsp;99% &nbsp; &nbsp;/spool
  1065. <br />...
  1066. <br />/dev/da0p1 &nbsp;7,630,093 7,372,189 &nbsp; 181,603 &nbsp; &nbsp;98% &nbsp; &nbsp;/videobackup
  1067. <br />tiwi:/spool 7,567,870 7,374,421 &nbsp; 117,770 &nbsp; &nbsp;98% &nbsp; &nbsp;/spool
  1068. <br />
  1069.  </tt>
  1070. </div>
  1071. </blockquote>
  1072.  
  1073.      <p>
  1074. Why?  A look around showed me that <i>everything</i> was gone from <i>/spool/Videos</i>, my
  1075. collection of films.  Ah, just a viewpoint.  The directories are on <i>hydra</i>, and
  1076. they're not visible from <i>tiwi</i>.  On <i>teevee</i> I really do have other file systems
  1077. mounted on <i>/spool</i>:
  1078.      </p>
  1079.  
  1080.      <blockquote class="fullwidth">
  1081. <div style="text-align:left">
  1082.  <tt>
  1083. tiwi:/spool &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;7,567,870 7,374,406 &nbsp; 117,785 &nbsp; &nbsp;98% &nbsp; &nbsp;/spool
  1084. <br />hydra:/VB3/spool/Videos &nbsp; &nbsp; &nbsp;3,815,019 1,762,948 2,013,920 &nbsp; &nbsp;47% &nbsp; &nbsp;/spool/Videos
  1085. <br />hydra:/VB3/spool/Images &nbsp; &nbsp; &nbsp;3,815,019 1,762,948 2,013,920 &nbsp; &nbsp;47% &nbsp; &nbsp;/spool/Images
  1086. <br />
  1087.  </tt>
  1088. </div>
  1089. </blockquote>
  1090.  
  1091.      <p>
  1092. Theoretically that would explain why the sum of the file sizes on <i>/spool</i> would exceed
  1093. the size of the disk.  But that doesn't affect the views from <i>tiwi</i> or <i>eureka</i>,
  1094. as shown above.  I should examine the backup logs more carefully.
  1095.      </p>
  1096.      </div>
  1097.    ]]>
  1098.  </description>
  1099.  <dc:creator>Greg Lehey</dc:creator>
  1100.  <dc:date>2024-09-04T02:14:41+00:00</dc:date>
  1101. </item>
  1102.  
  1103.                  
  1104. <!-- topic ko not selected
  1105.      <p>
  1106. I'm out of deep-frozen cooked rice, time for a new batch.
  1107.      </p>
  1108.  
  1109.      <p>
  1110. I've been cooking rice for well over 50 years, and until recently I had no issues.  Put the
  1111. rice in the saucepan (I've found rice cookers <a href="http://www.lemis.com/grog/diary-jan2009.php?subtitle=Rice%20cookers:%20why%20bother?&amp;article=D30-14#D30-14">not worth the trouble</a>) and cover with water by <i>that much</i>.  How much?  About 2
  1112. cm.
  1113.      </p>
  1114.  
  1115.      <p>
  1116. Problem: that's not very repeatable.  Use the same amount of rice in a larger-diameter
  1117. saucepan and the water ratio will increase.  So I started measuring and found that the water
  1118. was about 1.5 times the amount of rice.  But then I heard of people using as much as twice
  1119. the amount of water, and recently I have increased it to up to 1.8 times.  It seems to work.
  1120. What about 1.9 times?  That's what I tried today. <i>Definitely</i> too much, at least for
  1121. this rice (<a href="https://en.wikipedia.org/wiki/ALDI">ALDI's</a> best long grain).
  1122.      </p>
  1123.  
  1124.      <p>
  1125. Now I should check less water again, and maybe give rice cookers another chance.
  1126.      </p>
  1127.      
  1128. End deselected topic ko (Cooking rice, yet again) -->
  1129.  
  1130.            
  1131. <item>
  1132. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2024.php#D-20240905-004907</guid>
  1133. <link>http://www.lemis.com/grog/diary-sep2024.php?topics=c#D-20240905-004907</link>
  1134. <category>technology</category>
  1135. <category>opinion</category>
  1136. <title>New disk</title>
  1137.  <description>
  1138.    <![CDATA[
  1139.    <div align="justify">
  1140.      <p>
  1141. My new 16 TB Seagate Exos disk has arrived already.  How do I install it?  One issue with
  1142. having <i>hydra</i> built commercially is that I don't understand it as well as the machines
  1143. I built myself.  Took off the covers and compared with the motherboard documentation (at
  1144. <a href="https://download.msi.com/archive/mnu_exe/mb/MAGX670ETOMAHAWKWIFI.pdf">https://download.msi.com/archive/mnu_exe/mb/MAGX670ETOMAHAWKWIFI.pdf</a>), and that's straightforward enough.  But where do I mount the disk?  <a href="http://www.lemis.com/grog/diary-oct2023.php?topics=c&amp;subtitle=Looking%20at%20hydra&amp;article=D-20231018-231622#D-20231018-231622">When I picked up the machine</a>, Seth pointed out disk mounting positions, but they're
  1145. for <a href="https://en.wikipedia.org/wiki/SSD">SSDs</a>.  There seems to be no
  1146. provision for 3½&quot; magnetic disks.  Should I put it on the base?  Or remove the
  1147. <a href="https://en.wikipedia.org/wiki/DVD">DVD</a>, find an adapter frame and put
  1148. it in there?  Or just put it in <i>eureka</i>?  That would clearly be the simplest solution.
  1149.      </p>
  1150.      </div>
  1151.    ]]>
  1152.  </description>
  1153.  <dc:creator>Greg Lehey</dc:creator>
  1154.  <dc:date>2024-09-05T00:49:07+00:00</dc:date>
  1155. </item>
  1156.  
  1157.            
  1158. <!-- topic Jh not selected
  1159.      <p>
  1160. Andrew from Bosch called back after only a little more than 24 hours.  All done and dusted,
  1161. of course, but he was able to give me another number to call:
  1162.      </p>
  1163.  
  1164.      <blockquote class="fullwidth">
  1165. <div style="text-align:left">
  1166.  <tt>
  1167. If you need further service work for the heat pump then consider contacting Craig smith. 0434460771
  1168. <br />
  1169.  </tt>
  1170. </div>
  1171. </blockquote>
  1172.      
  1173. End deselected topic Jh (Bosch service) -->
  1174.  
  1175.            
  1176. <!-- topic Jho not selected
  1177.      <p>
  1178. <a href="http://www.lemis.com/yvonne/">Yvonne</a> has been having fun getting a quotation for replacing
  1179. our defective gate with a sliding one like we had in <a href="http://www.lemis.com/wantadilla/">Wantadilla</a>.  Things don't look good: we had one quote round $10,000.  The current
  1180. one, from BOE Constructions, was $6,050—<i>without</i> installation.  Today Chris of
  1181. Complete Fencing Solutions Ballarat came along to look at the installation.  He later sent a
  1182. quote—<i>another</i> $5,445!  That's a total of $11,495!  I can't recall what we paid at
  1183. Wantadilla, but I think it was under $3,000.  We can resist that.
  1184.      </p>
  1185.  
  1186.      <p>
  1187. In fact, it seems that he has quoted for things that were already in the other quote, the
  1188. motor, controller and solar power kit, a total of $4,235.  And that corresponds pretty
  1189. directly to the $403.43 (including postage) that we paid for the current actuator!
  1190.      </p>
  1191.      
  1192. End deselected topic Jho (Installing a sliding gate) -->
  1193.  
  1194.            
  1195. <!-- topic ko not selected
  1196.      <p>
  1197. I have fond memories of pepper-based foods from my time in <a href="https://en.wikipedia.org/wiki/Sarawak">Sarawak</a>, so a while back I bought this
  1198. spice mix:
  1199.      </p>
  1200.  
  1201.            
  1202.      <p>
  1203. I've been meaning to use it for ever, but I was concerned that <a href="http://www.lemis.com/yvonne/">Yvonne</a> might find it too overpoweringly <i>pedas</i>.  It expired a few months ago,
  1204. and today we had some other Chinese leftovers, so I got round to cooking it.
  1205.      </p>
  1206.  
  1207.      <p>
  1208. I had my doubts, and I should have looked at the recommended recipe more carefully: 450 g
  1209. (isn't that a familiar number?) chicken, 150 g broccoli and 25 g carrot.  And both
  1210. vegetables should be cooked for only 2 minutes!
  1211.      </p>
  1212.  
  1213.      <p>
  1214. Despite all that, it didn't turn out too badly:
  1215.      </p>
  1216.  
  1217.            
  1218.      <p>
  1219. But clearly I should read the instructions more carefully before buying these things.
  1220.      </p>
  1221.      
  1222. End deselected topic ko (Sarawak pepper chicken) -->
  1223.  
  1224.            
  1225. <item>
  1226. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2024.php#D-20240905-022430</guid>
  1227. <link>http://www.lemis.com/grog/diary-sep2024.php?topics=c#D-20240905-022430</link>
  1228. <category>technology</category>
  1229. <category>opinion</category>
  1230. <title>More NFS pain</title>
  1231.  <description>
  1232.    <![CDATA[
  1233.    <div align="justify">
  1234.      <p>
  1235. Watching TV in the evening, I wanted to watch a film.  They're on <i>/spool/Videos/</i>,
  1236. <a href="https://en.wikipedia.org/wiki/Network_File_System">NFS</a> mounted on an
  1237. external drive from <i>hydra</i>.  And I had an access error.
  1238.      </p>
  1239.  
  1240.      <p>
  1241. Oh.  Yes, <i>hydra</i> agreed.  Disk not accessible.  I must have accidentally disconnected
  1242. it while looking at the machine this afternoon, and <i>/var/log/messages</i> agreed:
  1243.      </p>
  1244.  
  1245.      <blockquote class="fullwidth">
  1246. <div style="text-align:left">
  1247.  <tt>
  1248. Sep &nbsp;4 14:25:03 hydra kernel: ugen3.2: &lt;Western Digital My Passport 2627&gt; at usbus3 (disconnected)
  1249. <br />Sep &nbsp;4 14:25:03 hydra kernel: umass0: at uhub2, port 4, addr 1 (disconnected)
  1250. <br />Sep &nbsp;4 14:25:03 hydra kernel: da0 at umass&#45;sim0 bus 0 scbus8 target 0 lun 0
  1251. <br />Sep &nbsp;4 14:25:03 hydra kernel: da0: &lt;WD My Passport 2627 4008&gt; &nbsp;s/n 575856324537304557343143 detached
  1252. <br />Sep &nbsp;4 14:25:03 hydra kernel: ses0 at umass&#45;sim0 bus 0 scbus8 target 0 lun 1
  1253. <br />Sep &nbsp;4 14:25:03 hydra kernel: ses0: &lt;WD SES Device 4008&gt; &nbsp;s/n 575856324537304557343143 detached
  1254. <br />Sep &nbsp;4 14:25:03 hydra kernel: (ses0:umass&#45;sim0:0:0:1): Periph destroyed
  1255. <br />Sep &nbsp;4 14:25:03 hydra kernel: (da0:umass&#45;sim0:0:0:0): Periph destroyed
  1256. <br />Sep &nbsp;4 14:25:03 hydra kernel: umass0: detached
  1257. <br />Sep &nbsp;4 14:25:06 hydra kernel: usb_msc_auto_quirk: UQ_MSC_NO_PREVENT_ALLOW set for USB mass storage device Western Digital My Passport 2627 (0x1058:0x2627)
  1258. <br />Sep &nbsp;4 14:25:06 hydra kernel: ugen3.2: &lt;Western Digital My Passport 2627&gt; at usbus3
  1259. <br />Sep &nbsp;4 14:25:06 hydra kernel: umass0 on uhub2
  1260. <br />Sep &nbsp;4 14:25:06 hydra kernel: umass0: &lt;Western Digital My Passport 2627, class 0/0, rev 2.10/40.08, addr 1&gt; on usbus3
  1261. <br />Sep &nbsp;4 14:25:06 hydra kernel: umass0: &nbsp;SCSI over Bulk&#45;Only; quirks = 0x8000
  1262. <br />Sep &nbsp;4 14:25:06 hydra kernel: umass0:8:0: Attached to scbus8
  1263. <br />Sep &nbsp;4 14:25:06 hydra kernel: da0 at umass&#45;sim0 bus 0 scbus8 target 0 lun 0
  1264. <br />Sep &nbsp;4 14:25:06 hydra kernel: da0: &lt;WD My Passport 2627 4008&gt; Fixed Direct Access SPC&#45;4 SCSI device
  1265. <br />Sep &nbsp;4 14:25:06 hydra kernel: da0: Serial Number 575856324537304557343143
  1266. <br />Sep &nbsp;4 14:25:06 hydra kernel: da0: 40.000MB/s transfers
  1267. <br />Sep &nbsp;4 14:25:06 hydra kernel: da0: 3815415MB (7813969920 512 byte sectors)
  1268. <br />Sep &nbsp;4 14:25:06 hydra kernel: da0: quirks=0x2&lt;NO_6_BYTE&gt;
  1269. <br />Sep &nbsp;4 14:25:06 hydra kernel: ses0 at umass&#45;sim0 bus 0 scbus8 target 0 lun 1
  1270. <br />Sep &nbsp;4 14:25:06 hydra kernel: ses0: &lt;WD SES Device 4008&gt; Fixed Enclosure Services SPC&#45;4 SCSI device
  1271. <br />Sep &nbsp;4 14:25:06 hydra kernel: ses0: Serial Number 575856324537304557343143
  1272. <br />Sep &nbsp;4 14:25:06 hydra kernel: ses0: 40.000MB/s transfers
  1273. <br />Sep &nbsp;4 14:25:06 hydra kernel: ses0: SES Device
  1274. <br />
  1275.  </tt>
  1276. </div>
  1277. </blockquote>
  1278.  
  1279.      <p>
  1280. OK, force <i>umount</i>, <i>fsck</i>, <i>mount</i>.  All OK.  Mount from <i>teevee</i>:
  1281.      </p>
  1282.  
  1283.      <blockquote class="fullwidth">
  1284. <div style="text-align:left">
  1285.  <tt>
  1286. mount_nfs: nmount: /VB3: Stale NFS file handle
  1287. <br />
  1288.  </tt>
  1289. </div>
  1290. </blockquote>
  1291.  
  1292.      <p>
  1293. I've <a href="http://www.lemis.com/grog/diary-sep2024.php?topics=c&amp;subtitle=Where%20did%20all%20my%20disk%20space%20go?&amp;article=D-20240903-015753#D-20240903-015753">seen that before</a>, but the first time was only a couple of days ago.  Why is this
  1294. happening now?  And I didn't find a solution this evening; we watched series episodes
  1295. instead: they're on a different disk, on <i>tiwi</i>.
  1296.      </p>
  1297.      </div>
  1298.    ]]>
  1299.  </description>
  1300.  <dc:creator>Greg Lehey</dc:creator>
  1301.  <dc:date>2024-09-05T02:24:30+00:00</dc:date>
  1302. </item>
  1303.  
  1304.                  
  1305. <!-- topic hH not selected
  1306.      <p>
  1307. When I got up this morning I discovered a message on <i>albo</i>, my mobile phone:
  1308. <a href="https://en.wikipedia.org/wiki/Powercor_Australia">Powercor</a> had become
  1309. aware of a <a href="http://www.lemis.com/grog/powercor/power-failures.php#bottom">grid power failure</a> at 5:52, along with another message telling me that power had been restored 41 minutes
  1310. later.  The air conditioner was running, but fortunately we didn't run out of power.
  1311.      </p>
  1312.  
  1313.      <p>
  1314. Than another at 11:27, while we were having breakfast, this time only 22 minutes.  The
  1315. inverter didn't handle it well, causing various screams from the electronics, but the only
  1316. thing really affected was the radio.
  1317.      </p>
  1318.  
  1319.      <p>
  1320. Clearly this was another <a href="http://www.lemis.com/grog/diary-sep2019.php?subtitle=Another%20power%20failure&amp;article=D-20190905-234500#D-20190905-234500">fifth anniversary gift</a>.  But to be fair to Powercor, things have looked up a lot
  1321. since we moved to <a href="https://en.wikipedia.org/wiki/Dereel">Dereel</a>.  Let's
  1322. hope they stay that way.
  1323.      </p>
  1324.      
  1325. End deselected topic hH (Anniversary power fail) -->
  1326.  
  1327.            
  1328. <item>
  1329. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2024.php#D-20240906-021724</guid>
  1330. <link>http://www.lemis.com/grog/diary-sep2024.php?topics=c#D-20240906-021724</link>
  1331. <category>technology</category>
  1332. <category>multimedia</category>
  1333. <category>opinion</category>
  1334. <title>NFS recovery</title>
  1335.  <description>
  1336.    <![CDATA[
  1337.    <div align="justify">
  1338.      <p>
  1339. So why am I getting these stale <a href="https://en.wikipedia.org/wiki/Network_File_System">NFS</a> handles?  Discovered a
  1340. number of these messages in <i>/var/log/messages</i>:
  1341.      </p>
  1342.  
  1343.      <blockquote class="fullwidth">
  1344. <div style="text-align:left">
  1345.  <tt>
  1346. Sep &nbsp;4 18:40:48 teevee kernel: newnfs: server 'hydra' error: fileid changed. fsid 0:0: expected fileid 0x31700, got 0x2. (BROKEN NFS SERVER OR MIDDLEWARE)
  1347. <br />
  1348.  </tt>
  1349. </div>
  1350. </blockquote>
  1351.  
  1352.      <p>
  1353. What does that mean?  The result of trying to remount a new mount on <i>hydra</i>?  What
  1354. does <i>hydra</i> say?
  1355.      </p>
  1356.  
  1357.      <blockquote class="fullwidth">
  1358. <div style="text-align:left">
  1359.  <tt>
  1360. Sep &nbsp;4 18:44:50 hydra kernel: UFS: forcibly unmounting /dev/da0p1 from /VB3
  1361.  </tt>
  1362. </div>
  1363. </blockquote>
  1364.  
  1365.      <p>
  1366. But that was a few minutes later.  Nothing obvious.  A web search brought up various stuff,
  1367. suggesting that it's new, but nothing that helps much.  What I did establish is that the
  1368. issue is with <i>hydra</i>, not with <i>teevee</i>, and that it's not related to existing
  1369. mounts: the same thing happens on <i>lagoon</i>, which didn't have the file system mounted.
  1370.      </p>
  1371.  
  1372.      <p>
  1373. So: what happens if I mount the same device on a different mount point on <i>hydra</i>, and
  1374. then export that and mount it from <i>teevee</i>?  That's a thing that I wanted to do
  1375. anyway, so tried that.  Instead of mounting and exporting <i>/VB3</i>, use the mount point
  1376. name <i>/Videos</i>.  Success!
  1377.      </p>
  1378.  
  1379.      <p>
  1380. So somewhere it seems that there's an issue in the NFS stack.  I suppose I should follow up.
  1381.      </p>
  1382.  
  1383.      <p>
  1384. To confuse the issue, looked at the file systems mounted on <i>teevee</i> after that and
  1385. found, inter alia
  1386.      </p>
  1387.  
  1388.      <blockquote class="fullwidth">
  1389. <div style="text-align:left">
  1390.  <tt>
  1391. Filesystem &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;1048576&#45;blocks &nbsp; &nbsp; &nbsp;Used &nbsp; &nbsp; Avail Capacity &nbsp;Mounted on
  1392. <br />tiwi:/VB2 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;5,722,572 5,182,906 &nbsp; 482,440 &nbsp; &nbsp;91% &nbsp; &nbsp;/VB2
  1393. <br />tiwi:/spool &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;7,567,870 7,374,516 &nbsp; 117,675 &nbsp; &nbsp;98% &nbsp; &nbsp;/spool
  1394. <br />hydra:/VB3/spool/Images &nbsp; &nbsp; &nbsp; &nbsp;3,815,019 1,762,948 2,013,920 &nbsp; &nbsp;47% &nbsp; &nbsp;/spool/Images
  1395. <br />tiwi:/VB2 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 39,664 &nbsp; &nbsp;23,880 &nbsp; &nbsp;12,610 &nbsp; &nbsp;65% &nbsp; &nbsp;/VB2
  1396. <br />hydra:/Video &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3,815,019 1,762,948 2,013,920 &nbsp; &nbsp;47% &nbsp; &nbsp;/Video
  1397. <br />hydra:/Video/spool/Videos &nbsp; &nbsp; &nbsp;3,815,019 1,762,948 2,013,920 &nbsp; &nbsp;47% &nbsp; &nbsp;/spool/Videos
  1398. <br />
  1399.  </tt>
  1400. </div>
  1401. </blockquote>
  1402.  
  1403.      <p>
  1404. There are a number of issues here:
  1405.      </p>
  1406.  
  1407.      <ul>
  1408.        <li class="fullwidth">
  1409.          <div class="listitemwidth">
  1410.    I have mounted a NFS file system from <i>hydra</i> (<i>hydra:/VB3/spool/Images</i> on
  1411.    top of <i>/spool</i>, an NFS file system mounted from <i>tiwi</i>.
  1412.          </div>
  1413.        </li>
  1414.  
  1415.        <li class="fullwidth">
  1416.          <div class="listitemwidth">
  1417.            Possibly the problem is related to the fact that I still
  1418.            had <i>hydra:/VB3/spool/Images</i> mounted.  I seem to have mised that.
  1419.          </div>
  1420.        </li>
  1421.  
  1422.        <li class="fullwidth">
  1423.          <div class="listitemwidth">
  1424.            <i>/VB3</i> isn't mounted on <i>hydra</i>, but it's still visible on <i>teevee</i>, and
  1425.            the contents are correct, and I can create and remove files.  Where is it getting this
  1426.            information from?
  1427.          </div>
  1428.        </li>
  1429.  
  1430.        <li class="fullwidth">
  1431.          <div class="listitemwidth">
  1432.            <i>tiwi:/VB2</i> is mounted twice, accessing two different file systems (the second
  1433.            appears to be <i>tiwi:/</i>).
  1434.          </div>
  1435.        </li>
  1436.      </ul>
  1437.  
  1438.      <p>
  1439. I've run into the “double mount” problem before.  It doesn't appear to be limited to NFS.
  1440.        Why should it ever be useful to mount a file system twice, especially if two different file
  1441.        systems get mounted on the same mount point?  I've already established that a <i>umount</i>
  1442.        will umount the last instance, but I still needed to force <i>umount</i> it
  1443.      </p>
  1444.  
  1445.      <blockquote class="fullwidth">
  1446. <div style="text-align:left">
  1447.  <tt>
  1448. <code><font color="blue">=== root@teevee (/dev/pts/12)</font> <font color="red">/spool</font> <font color="blue">55</font> &#45;&gt; <b><tt>umount /VB2</tt></b></code>
  1449. <br />umount: unmount of /VB2 failed: Device busy
  1450. <br /><code><font color="blue">=== root@teevee (/dev/pts/12)</font> <font color="red">/spool</font> <font color="blue">56</font> &#45;&gt; <b><tt>umount &#45;f /VB2</tt></b></code>
  1451. <br /><code><font color="blue">=== root@teevee (/dev/pts/12)</font> <font color="red">/spool</font> <font color="blue">57</font> &#45;&gt; <b><tt>df</tt></b></code>
  1452. <br />...
  1453. <br />tiwi:/VB2 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;5,722,572 5,182,906 &nbsp; 482,440 &nbsp; &nbsp;91% &nbsp; &nbsp;/VB2
  1454. <br /><code><font color="blue">=== root@teevee (/dev/pts/12)</font> <font color="red">/spool</font> <font color="blue">58</font> &#45;&gt; <b><tt>l /VB2</tt></b></code>
  1455. <br />total 19428
  1456. <br />drwxrwxr&#45;x &nbsp; 2 grog home &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 512 12 Feb &nbsp;2018 .snap
  1457. <br />&#45;r&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45; &nbsp; 1 root wheel &nbsp; &nbsp; 33,554,432 &nbsp;1 May &nbsp;2019 .sujournal
  1458. <br />drwxr&#45;xr&#45;x &nbsp; 8 grog home &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 512 25 Jun 11:43 spool
  1459. <br />drwxr&#45;xr&#45;x &nbsp;23 grog wheel &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;512 29 Apr &nbsp;2023 spool&#45;old
  1460.  </tt>
  1461. </div>
  1462. </blockquote>
  1463.  
  1464.      <p>
  1465. This last <i>ls</i> shows what I expect, so I have the correct file system mounted.
  1466.      </p>
  1467.      </div>
  1468.    ]]>
  1469.  </description>
  1470.  <dc:creator>Greg Lehey</dc:creator>
  1471.  <dc:date>2024-09-06T02:17:24+00:00</dc:date>
  1472. </item>
  1473.  
  1474.            
  1475. <item>
  1476. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2024.php#D-20240906-024555</guid>
  1477. <link>http://www.lemis.com/grog/diary-sep2024.php?topics=c#D-20240906-024555</link>
  1478. <category>technology</category>
  1479. <category>opinion</category>
  1480. <title>Installing the new disk</title>
  1481.  <description>
  1482.    <![CDATA[
  1483.    <div align="justify">
  1484.      <p>
  1485. So what do I do with my new 16 TB Seagate Exos disk?  On the whole it seems to be a better
  1486. idea to put it in <i>eureka</i>, where the old disk is.  That would save issues with
  1487. <a href="https://en.wikipedia.org/wiki/Network_File_System">NFS</a> and <a href="https://en.wikipedia.org/wiki/Server_Message_Block">SMB</a>, and there's plenty of
  1488. space for it.  So reluctantly shut <i>eureka</i> down for the second time in a few days, put
  1489. the disk in, cabled it up, rebooted into the BIOS setup menu.  No new disk.
  1490.      </p>
  1491.  
  1492.      <p>
  1493. What happened there?  I know I've had cable problems in <i>eureka</i>—after all,
  1494. it <i>is</i> <a href="http://www.lemis.com/grog/diary-jan2014.php?subtitle=New%20computer,%20finally&amp;article=D-20140201-022258#D-20140201-022258">over 10 years old</a>—but I thought that this would work.
  1495.      </p>
  1496.  
  1497.      <p>
  1498. What are the alternatives?  <i>hydra</i> after all?  It seems a messy way to go, since the
  1499. web server files are on <i>/Photos</i>, and the web server runs on <i>eureka</i>.  I already
  1500. have an issue with <a href="http://www.lemis.com/yvonne/">Yvonne's</a> photos on <i>lagoon:/Photos</i>,
  1501. for which I need to copy the photos to <i>eureka</i> (yes, potentially <a href="https://en.wikipedia.org/wiki/Symbolic_link">symlinks</a> would do the job, but so far
  1502. I haven't looked at it; one way or another it's an issue).  So: how about putting it in a
  1503. test machine, copying the data and then moving the disk to the physical position
  1504. of <i>/Photos</i> in <i>eureka</i>?  But which machine?  In principle I have three spare
  1505. <a href="https://en.wikipedia.org/wiki/ThinkCentre">ThinkCentres</a>, but two are
  1506. probably defective, and the third is still running as <i>tiwi</i> until I get my weather
  1507. station software sorted out.
  1508.      </p>
  1509.  
  1510.      <p>
  1511. But there are still the two machines from Bruce Evans.  I've decided that I don't like the
  1512. <a href="https://support.hp.com/au-en/document/c01709726">HP Z800</a>, which seems
  1513. particularly hard to work with, but what about the other one, the one he
  1514. called <i>zetaplex</i>?  I haven't really looked at it very carefully, but it seems normal
  1515. enough, if you ignore the silly lights:
  1516.      </p>
  1517.  
  1518.        <a id="Photo-2" name="Photo-2"
  1519.          href="diary-sep2024.php?dirdate=20240906&amp;imagesizes=112&amp;topics=c#Photo-2">
  1520.          <img alt="This should be quartet-7.jpeg.  Is it missing?" border="0" id="Photo_2"
  1521.               title="Photo quartet-7.jpeg.  Click to redisplay larger version of image."
  1522.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20240906/small/quartet-7.jpeg"
  1523.               width="300" height="225"
  1524.           /></a>
  1525.  
  1526.      <p>
  1527. I'm sure that wasn't Bruce's choice.  It's comparable to but about 11% faster
  1528. than <i>eureka</i> (<a href="https://www.cpubenchmark.net/compare/2027vs2275/Intel-i7-4771-vs-Intel-i7-4790K">Intel
  1529. i7 4790K instead of Intel i7 4771</a>).  It has enough space for all the disks
  1530. on <i>eureka</i>, but only 16 GB of memory instead of 32 GB.  Still, a good backup to have
  1531. in case <i>eureka</i> dies.
  1532.      </p>
  1533.  
  1534.      <p>
  1535. The disk is in a tray with cables too short to remove it, possibly an issue with the
  1536. assembly.  I'll look at that later.  But to my surprise I found 2 <a href="https://en.wikipedia.org/wiki/SSD">SSDs</a> almost completely hidden in other trays,
  1537. both too polite to mention their capacity; I'll look at that when the copying is done.  Put
  1538. in my <i>quartet</i> SSD, the one I set up <a href="http://www.lemis.com/grog/diary-jun2024.php?subtitle=More%20VirtualBox%20fun&amp;article=D-20240629-005229#D-20240629-005229">a couple of months ago</a>, and of course the new disk.  Power up, into <a href="https://en.wikipedia.org/wiki/BIOS">BIOS</a> setup.  Not seen!  Of course, modern
  1539. BIOS/<a href="https://en.wikipedia.org/wiki/UEFI">UEFI</a> screens are really hard
  1540. to understand.  Booted into <a href="https://www.freebsd.org/">FreeBSD</a> anyway.
  1541. It saw the disk.  Reboot, into the BIOS screen.  It saw the disk.
  1542.      </p>
  1543.  
  1544.      <p>
  1545. Is there something about the disk that wants somebody to throw the first stone?  Would it
  1546. have worked in <i>eureka</i>?  I couldn't be bothered to recable all over again, so I'll
  1547. never know.
  1548.      </p>
  1549.  
  1550.      <p>
  1551. So, time to integrate into the LAN.  But I couldn't access the net!  After some examination,
  1552. I found that the box has three Ethernet interfaces, like the Z800 (why?).  But there seem to
  1553. be only two connections.  My startup script had assigned the same IP address to
  1554. both <i>em0</i> and <i>re0</i>, while <i>em1</i> remained unconfigured.  Connect the cable
  1555. to <i>em0</i> (on the motherboard) and all was well.
  1556.      </p>
  1557.  
  1558.      <p>
  1559. Then a custom <i>newfs</i> for a disk with large files, something like I decided upon
  1560. <a href="http://www.lemis.com/grog/diary-jun2016.php?subtitle=Backup%20disk%20hell&amp;article=D-20160628-002411#D-20160628-002411">years ago</a>:
  1561.      </p>
  1562.  
  1563.      <blockquote class="fullwidth">
  1564. <div style="text-align:left">
  1565.  <tt>
  1566. <code><font color="blue">=== root@quartet (/dev/pts/10)</font> <font color="red">~</font> <font color="blue">44</font> &#45;&gt; <b><tt>newfs &#45;L Photos &#45;O 2 &#45;U &#45;a 64 &#45;b 16384 &#45;d 16384 &#45;e 2048 &#45;f 2048 &#45;g 3145728 &#45;h 64 &#45;i 2752512 &#45;m 1 &#45;o space /dev/ada1p1</tt></b></code>
  1567.  </tt>
  1568. </div>
  1569. </blockquote>
  1570.  
  1571.      <p>
  1572. After writing what seem to be far too many cylinder groups, it appeared to hang creating the
  1573. journal, about 90 seconds.  But it was apparently accessing the disk the whole time.
  1574.      </p>
  1575.  
  1576.      <p>
  1577. And that gave me the biggest file system I have ever seen:
  1578.      </p>
  1579.  
  1580.      <blockquote class="fullwidth">
  1581. <div style="text-align:left">
  1582.  <tt>
  1583. <code><font color="blue">=== grog@quartet (/dev/pts/2)</font> <font color="red">~</font> <font color="blue">23</font> &#45;&gt; <b><tt>df /Photos /newphotos/</tt></b></code>
  1584. <br />Filesystem &nbsp; &nbsp; 1048576&#45;blocks &nbsp; &nbsp; &nbsp;Used &nbsp; &nbsp; &nbsp;Avail Capacity &nbsp;Mounted on
  1585. <br />eureka:/Photos &nbsp; &nbsp; &nbsp;7,629,565 6,806,391 &nbsp; &nbsp;746,877 &nbsp; &nbsp;90% &nbsp; &nbsp;/Photos
  1586. <br />/dev/ada1p1 &nbsp; &nbsp; &nbsp; &nbsp;15,257,008 &nbsp; &nbsp; &nbsp; &nbsp; 0 15,104,437 &nbsp; &nbsp; 0% &nbsp; &nbsp;/newphotos
  1587. <br />
  1588.  </tt>
  1589. </div>
  1590. </blockquote>
  1591.  
  1592.      <a name="IBM-3330" id="IBM-3330"></a>
  1593.      <p>
  1594. That corresponds to nearly 10,000 <a href="https://en.wikipedia.org/wiki/IBM_3330">IBM
  1595. 3330</a> subsystems, my old yardstick for disk capacity.  If I interpret <a href="https://gemini.google.com/app/12f6ded0cb11427e">this incorrect answer</a> correctly, a
  1596. 3330 cabinet has a footprint of 7.65 m², so we're looking at about 7.6 <a href="https://en.wikipedia.org/wiki/Hactare">ha</a> of cabinets, on top of which you'd need
  1597. probably the same amount to move round the things.
  1598.      </p>
  1599.  
  1600.      <p>
  1601. Then the copy, using <i>tar</i> across <a href="https://en.wikipedia.org/wiki/Network_File_System">NFS</a>, running close to wire
  1602. speed at between 90 and 110 MB/s.  At that speed it should take about a day, filling the
  1603. first IBM 3330 equivalent in about 20 seconds.  But while looking at the results, I
  1604. discovered that a lot of the directories had a modification timestamp 1 January 2009.  The
  1605. system clock had lost its memory, and that must have been the <a href="https://en.wikipedia.org/wiki/Epoch_(computing)">epoch</a> for the BIOS.  OK, run
  1606. an <i>ntpdate</i> and fire up <i>ntpd</i>.
  1607.      </p>
  1608.  
  1609.      <blockquote class="fullwidth">
  1610. <div style="text-align:left">
  1611.  <tt>
  1612. <code><font color="blue">=== grog@quartet (/dev/pts/3)</font> <font color="red">~</font> <font color="blue">19</font> &#45;&gt; <b><tt>date</tt></b></code>
  1613. <br />Thu &nbsp;1 Jan 2009 14:21:09 AEDT
  1614. <br /><code><font color="blue">=== root@quartet (/dev/pts/3)</font> <font color="red">/home/grog</font> <font color="blue">1</font> &#45;&gt; <b><tt>ntpdate eureka</tt></b></code>
  1615. <br />&nbsp;5 Sep 18:25:31 ntpdate[2069]: step time server 192.109.197.137 offset +494744636.627861 sec
  1616. <br />You have mail in /var/mail/grog
  1617. <br /><code><font color="blue">=== root@quartet (/dev/pts/3)</font> <font color="red">/home/grog</font> <font color="blue">2</font> &#45;&gt; <b><tt>date</tt></b></code>
  1618. <br />Thu &nbsp;5 Sep 2024 18:26:46 AEST
  1619. <br /><code><font color="blue">=== root@quartet (/dev/pts/3)</font> <font color="red">/home/grog</font> <font color="blue">3</font> &#45;&gt; <b><tt>ntpd</tt></b></code>
  1620. <br />daemon control: got EOF
  1621. <br />
  1622.  </tt>
  1623. </div>
  1624. </blockquote>
  1625.  
  1626.      <p>
  1627. Huh?  What does that mean?  <i>ntpd</i> wasn't running.  More web surfing brought me to
  1628. <a href="https://www.linuxquestions.org/questions/showthread.php?p=6505352">this
  1629. article</a>, which at least confirmed that it's not a <a href="https://www.freebsd.org/">FreeBSD</a> issue.  Use the <tt>-4</tt> to avoid trying
  1630. <a href="https://en.wikipedia.org/wiki/IPv6">IPv6</a>.  But that didn't help.  On
  1631. the other hand, <i>/var/log/messages</i> showed:
  1632.      </p>
  1633.  
  1634.      <blockquote class="fullwidth">
  1635. <div style="text-align:left">
  1636.  <tt>
  1637. Sep &nbsp;5 18:31:15 quartet ntpd[2088]: ntpd 4.2.8p18&#45;a (1): Starting
  1638. <br />Sep &nbsp;5 18:31:15 quartet ntpd[2088]: Command line: ntpd
  1639. <br />Sep &nbsp;5 18:31:15 quartet ntpd[2089]: bind(23) AF_INET 192.109.197.151:123 flags 0x19 failed: Address already in use
  1640. <br />Sep &nbsp;5 18:31:15 quartet ntpd[2089]: unable to create socket on re0 (3) for 192.109.197.151:123
  1641. <br />Sep &nbsp;5 18:31:15 quartet ntpd[2088]: daemon child died with signal 11
  1642. <br />Sep &nbsp;5 18:31:15 quartet kernel: pid 2089 (ntpd), jid 0, uid 0: exited on signal 11 (core dumped)
  1643. <br />
  1644.  </tt>
  1645. </div>
  1646. </blockquote>
  1647.  
  1648.      <p>
  1649. More web surfing, no insights.  But one thing stood out: “unable to create socket on re0”.
  1650. That's what comes of having multiple interfaces with the same IP address.  Reset <i>re0</i>
  1651. and it found <i>em0</i> and ran.
  1652.      </p>
  1653.      </div>
  1654.    ]]>
  1655.  </description>
  1656.  <dc:creator>Greg Lehey</dc:creator>
  1657.  <dc:date>2024-09-06T02:45:55+00:00</dc:date>
  1658. </item>
  1659.  
  1660.                  
  1661. <item>
  1662. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2024.php#D-20240907-015305</guid>
  1663. <link>http://www.lemis.com/grog/diary-sep2024.php?topics=c#D-20240907-015305</link>
  1664. <category>technology</category>
  1665. <category>opinion</category>
  1666. <title>Disk copy, continued</title>
  1667.  <description>
  1668.    <![CDATA[
  1669.    <div align="justify">
  1670.      <p>
  1671. Into the office this morning to discover that my disk copy had failed after transferring 4
  1672. TB:
  1673.      </p>
  1674.  
  1675.      <blockquote class="fullwidth">
  1676. <div style="text-align:left">
  1677.  <tt>
  1678. ...
  1679. <br />x ./grog/20160115/orig/P1153725.jpg
  1680. <br />x ./grog/20160115/orig/P1153728.jpg
  1681. <br />x ./grog/20160115/orig/P1153729.jpgtar: (null)
  1682. <br />: Truncated tar archive: Unknown error: &#45;1
  1683. <br />tar: Error exit delayed from previous errors.
  1684. <br />
  1685.  </tt>
  1686. </div>
  1687. </blockquote>
  1688.  
  1689.      <p>
  1690. That wasn't completely unexpected.  OK, continue with <a href="https://en.wikipedia.org/wiki/rsync">rsync</a>, something that I'll have to do anyway
  1691. a couple of times.  In the process, discovered that the <tt>--delete-after</tt> option
  1692. changes <i>rsync's</i> behaviour: it first builds a list of files, which takes some time.  I
  1693. wanted immediate results, so I restarted without:
  1694.      </p>
  1695.  
  1696.      <blockquote class="fullwidth">
  1697. <div style="text-align:left">
  1698.  <tt>
  1699. <code><font color="blue">=== root@quartet (/dev/pts/0)</font> <font color="red">/var/tmp</font> <font color="blue">34</font> &#45;&gt; <b><tt>Log rsync &#45;av &#45;&#45;delete&#45;after /Photos/ /newphotos</tt></b></code>
  1700. <br />===== Fri 6 Sep 2024 09:30:09 AEST on quartet.lemis.com: rsync &#45;av &#45;&#45;delete&#45;after /Photos/ /newphotos
  1701. <br />building file list ... ^C
  1702. <br /><code><font color="blue">=== root@quartet (/dev/pts/0)</font> <font color="red">/var/tmp</font> <font color="blue">35</font> &#45;&gt; <b><tt>Log rsync &#45;av /Photos/ /newphotos</tt></b></code>
  1703. <br />===== Fri 6 Sep 2024 09:32:22 AEST on quartet.lemis.com: rsync &#45;av /Photos/ /newphotos
  1704. <br />sending incremental file list
  1705. <br />.sujournal
  1706. <br />rsync: [receiver] rename "/newphotos/.sujournal.8MXurP" &#45;> ".sujournal": Operation not permitted (1)
  1707. <br />grog/19640828/orig/hide/
  1708. <br />grog/19640828/orig/hide/img466.tif
  1709. <br />
  1710.  </tt>
  1711. </div>
  1712. </blockquote>
  1713.  
  1714.      <p>
  1715. And of course it ran all day.  But when it was done, I had:
  1716.      </p>
  1717.  
  1718.      <blockquote class="fullwidth">
  1719. <div style="text-align:left">
  1720.  <tt>
  1721. Filesystem &nbsp; &nbsp; 1048576&#45;blocks &nbsp; &nbsp; &nbsp;Used &nbsp; &nbsp; Avail Capacity &nbsp; iused &nbsp; &nbsp; ifree %iused &nbsp;Mounted on
  1722. <br />eureka:/Photos &nbsp; &nbsp; &nbsp;7,629,565 6,806,544 &nbsp; 746,725 &nbsp; &nbsp;90% 1,764,224 1,479,422 &nbsp; 54% &nbsp; /Photos
  1723. <br />/dev/ada1p1 &nbsp; &nbsp; &nbsp; &nbsp;15,257,008 7,237,056 7,867,381 &nbsp; &nbsp;48% 1,877,934 4,608,208 &nbsp; 29% &nbsp; /newphotos
  1724. <br />
  1725.  </tt>
  1726. </div>
  1727. </blockquote>
  1728.  
  1729.      <p>
  1730. Why the discrepancy?  The used space can depend on the <i>newfs</i> parameters, which I
  1731. should compare.  But more obvious is the number of <a href="https://en.wikipedia.org/wiki/inode">inodes</a> used, 115,000 more
  1732. than <i>/Photos</i>.  That looks like link breakage.  Where?  Mañana.
  1733.      </p>
  1734.      </div>
  1735.    ]]>
  1736.  </description>
  1737.  <dc:creator>Greg Lehey</dc:creator>
  1738.  <dc:date>2024-09-07T01:53:05+00:00</dc:date>
  1739. </item>
  1740.  
  1741.            
  1742. <!-- topic po not selected
  1743.      <p>
  1744. How do I take a photo of <i>quartet</i>, previously <i>zetaplex</i>?  A photo of a computer
  1745. is straightforward enough, but in this case I wanted to highlight this silly blue
  1746. illumination, so I didn't want much extraneous light, and the light levels were low.  OK, no
  1747. worries, pull down the blinds to minimize external illumination and take at high <a href="https://en.wikipedia.org/wiki/Film_speed#Digital_camera_ISO_speed_and_exposure_index">ISO</a>:
  1748.      </p>
  1749.  
  1750.      
  1751.      <p>
  1752. Acceptable, but not good.  In particular, the aperture f/1.4 means that the back is out of
  1753. focus, and the noise could be better:
  1754.      </p>
  1755.  
  1756.      
  1757.      <p>
  1758. OK, mount on a tripod and try a longer exposure at 200/24° ISO:
  1759.      </p>
  1760.  
  1761.      
  1762.      <p>
  1763. That's an improvement, but there's not much detail in the computer below <i>quartet</i>
  1764. (<i>distress</i>).
  1765.      </p>
  1766.  
  1767.      
  1768.      <p>
  1769. How about <a href="https://en.wikipedia.org/wiki/High-dynamic-range_imaging">HDR</a>?  Two different ways, one with <a href="http://hugin.sourceforge.net"><i>Hugin</i></a> tools and one with <a href="http://www.hdrsoft.com/"><i>Photomatix</i></a>:
  1770.      </p>
  1771.  
  1772.            
  1773.      <p>
  1774. There's surprisingly little difference from the normal shots.
  1775.      </p>
  1776.  
  1777.      <p>
  1778. OK, mobile phones are supposed to be as good as real cameras.  Try that:
  1779.      </p>
  1780.  
  1781.      
  1782.      <p>
  1783. Oh.  Of course, they have fixed focal lengths.  To be fair, I didn't think to try the
  1784. “telephoto lens”, which I think doubles the focal length.  But never mind, I can crop:
  1785.      </p>
  1786.  
  1787.      
  1788.      <p>
  1789. But that has terrible detail:
  1790.      </p>
  1791.  
  1792.      
  1793.      <p>
  1794. Or I can come closer and accept the perspective distortion:
  1795.      </p>
  1796.  
  1797.      
  1798.      <p>
  1799. That doesn't help much either.  Detail is terrible, and there's clear evidence of camera
  1800. shake:
  1801.      </p>
  1802.  
  1803.            
  1804.      <p>
  1805. So mobile phones are really not worth the trouble.  It looks as if my best choice is the old
  1806. camera on tripod and more aggressive postprocessing.
  1807.      </p>
  1808.  
  1809.      <p>
  1810. In passing, the <a href="https://en.wikipedia.org/wiki/Exif">Exif</a> data for the
  1811. phone claims +5 <a href="https://en.wikipedia.org/wiki/Exposure_value">EV</a> exposure compensation.  That looks like a misunderstanding on the part of the firmware
  1812. programmers.  There was no compensation.
  1813.      </p>
  1814.      
  1815. End deselected topic po (Computer photo challenge) -->
  1816.  
  1817.            
  1818. <!-- topic aho not selected
  1819.      <p>
  1820. Found <a href="http://www.lemis.com/grog/Albums/Animals/Mona.php">Mona</a> looking interestedly at the
  1821. air conditioner return air filter.  And indeed, I had heard some noise in there.  Opened the
  1822. filter holder, and in went Mona.  Within 10 seconds she had caught <i>and killed</i> a
  1823. mouse:
  1824.      </p>
  1825.  
  1826.            
  1827.      <p>
  1828. Has she done that before?  My guess is no.  I think the killing at this point was
  1829. accidental.  Cats play with mice before killing them, and Mona showed interest in playing
  1830. with it. But the mouse wasn't interested:
  1831.      </p>
  1832.  
  1833.      <div align="left">
  1834.      </div>
  1835.  
  1836.      <p>
  1837. After a bit of messing around, Mona walked off, while <a href="http://www.lemis.com/grog/Albums/Animals/Bruno.php">Bruno</a> spent another 10 minutes or so playing with
  1838. it.  It's interesting to note that he didn't interfere with Mona at all.  Ultimately he lost
  1839. interest too, and I gave it to <a href="http://www.lemis.com/grog/Albums/Animals/Larissa.php">Larissa</a>, who carried it off and presumably ate it.
  1840.      </p>
  1841.  
  1842.      <blockquote class="fullwidth">
  1843.        <div class="listitemwidth">
  1844.          <i>So, was it a mouse?  I had looked at the tail and thought a young rat.  And <a href="http://www.lemis.com/grog/diary-sep2024.php?subtitle=Dinner%20with%20Pene%20Kirk&amp;article=D-20240908-020503#D-20240908-020503">on the following day</a> Pene Kirk agreed with me.</i>
  1845.        </div>
  1846.      </blockquote>
  1847.      
  1848. End deselected topic aho (A mouse?  Rats!) -->
  1849.  
  1850.                  
  1851. <!-- topic ko not selected
  1852.      <p>
  1853. We have a lot of carrots that have to be eaten quickly.  What do I do with them?  A fantasy
  1854. stir-fry, in the process trying this spice mix that is also approaching its use-by date:
  1855.      </p>
  1856.  
  1857.      
  1858.      <p>
  1859. The result:
  1860.      </p>
  1861.  
  1862.            
  1863.      <p>
  1864. Edible, not much more.  The paste is sticky, and the 80 g I used were barely enough.  Next
  1865. time I'll use a whole sachet (120 g).
  1866.      </p>
  1867.      
  1868. End deselected topic ko (Another ALDI spice mix) -->
  1869.  
  1870.            
  1871. <!-- topic go not selected
  1872.      <p>
  1873. Gradually the weather is getting warmer, and more flowers are appearing:
  1874.      </p>
  1875.  
  1876.      <div align="left">
  1877.      </div>
  1878.  
  1879.      <p>
  1880. Jesse Walsh came along to tidy out the “trough” round the terrace, and <a href="http://www.lemis.com/yvonne/">Yvonne</a> was able to find at short notice somebody known only as “Eugene”
  1881. to come and collect the leftovers:
  1882.      </p>
  1883.  
  1884.            
  1885.      <p>
  1886. Eugene tells me that he had a friend in <a href="https://en.wikipedia.org/wiki/Geelong">Geelong</a> called Phil Lehey.  That would be interesting, but I suspect that he had
  1887. misunderstood the spelling of the surname.
  1888.      </p>
  1889.      
  1890. End deselected topic go (Spring on its way) -->
  1891.  
  1892.            
  1893. <item>
  1894. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2024.php#D-20240908-020443</guid>
  1895. <link>http://www.lemis.com/grog/diary-sep2024.php?topics=c#D-20240908-020443</link>
  1896. <category>technology</category>
  1897. <category>opinion</category>
  1898. <title>Understanding the disk copy issues</title>
  1899.  <description>
  1900.    <![CDATA[
  1901.    <div align="justify">
  1902.      <p>
  1903. So why is the copy of my <i>/Photos</i> disk so much bigger?
  1904.      </p>
  1905.  
  1906.      <blockquote class="fullwidth">
  1907. <div style="text-align:left">
  1908.  <tt>
  1909. <code><font color="blue">=== grog@quartet (/dev/pts/2)</font> <font color="red">~</font> <font color="blue">31</font> &#45;&gt; <b><tt>df &#45;i /Photos /newphotos/</tt></b></code>
  1910. <br />Filesystem &nbsp; &nbsp; 1048576&#45;blocks &nbsp; &nbsp; &nbsp;Used &nbsp; &nbsp; Avail Capacity &nbsp; iused &nbsp; &nbsp; ifree %iused &nbsp;Mounted on
  1911. <br />eureka:/Photos &nbsp; &nbsp; &nbsp;7,629,565 6,806,976 &nbsp; 746,292 &nbsp; &nbsp;90% 1,764,291 1,479,355 &nbsp; 54% &nbsp; /Photos
  1912. <br />/dev/ada1p1 &nbsp; &nbsp; &nbsp; &nbsp;15,257,008 7,237,056 7,867,381 &nbsp; &nbsp;48% 1,877,931 4,608,211 &nbsp; 29% &nbsp; /newphotos
  1913. <br />
  1914.  </tt>
  1915. </div>
  1916. </blockquote>
  1917.  
  1918.      <p>
  1919. It strongly suggests <a href="https://en.wikipedia.org/wiki/Symbolic_link">symlinks</a> changed to separate files.  Off for a look, and discovered—not surprisingly—the main
  1920. discrepancy in <i>/newphotos/grog</i>:
  1921.      </p>
  1922.  
  1923.      <blockquote class="fullwidth">
  1924. <div style="text-align:left">
  1925.  <tt>
  1926. <code><font color="blue">=== root@eureka (/dev/pts/1)</font> <font color="red">/Photos</font> <font color="blue">83</font> &#45;&gt; <b><tt>du &#45;s /Photos/grog</tt></b></code>
  1927. <br />6603970 /Photos/grog
  1928. <br /><code><font color="blue">=== root@quartet (/dev/pts/0)</font> <font color="red">/newphotos</font> <font color="blue">97</font> &#45;&gt; <b><tt>du &#45;s /newphotos/grog</tt></b></code>
  1929. <br />7011999 /newphotos/grog
  1930. <br />
  1931.  </tt>
  1932. </div>
  1933. </blockquote>
  1934.  
  1935.      <p>
  1936. Those are sizes in megabytes!  408 <b>GB</b> size difference.  OK, go down a level.  The big
  1937. difference was:
  1938.      </p>
  1939.  
  1940.      <blockquote class="fullwidth">
  1941. <div style="text-align:left">
  1942.  <tt>
  1943. eureka: &nbsp;93834 &nbsp; www
  1944. <br />quartet: 383635 &nbsp;www
  1945. <br />
  1946.  </tt>
  1947. </div>
  1948. </blockquote>
  1949.  
  1950.      <p>
  1951. Really?
  1952.      </p>
  1953.  
  1954.      <blockquote class="fullwidth">
  1955. <div style="text-align:left">
  1956.  <tt>
  1957. <code><font color="blue">=== root@eureka (/dev/pts/1)</font> <font color="red">~</font> <font color="blue">85</font> &#45;&gt; <b><tt>du &#45;s /Photos/grog/www</tt></b></code>
  1958. <br />383632 &nbsp;/Photos/grog/www
  1959. <br /><code><font color="blue">=== root@quartet (/dev/pts/0)</font> <font color="red">~</font> <font color="blue">99</font> &#45;&gt; <b><tt>du &#45;s /newphotos/grog/www</tt></b></code>
  1960. <br />383635 &nbsp;/newphotos/grog/www
  1961. <br />
  1962.  </tt>
  1963. </div>
  1964. </blockquote>
  1965.  
  1966.      <p>
  1967. Yes, this must be a link issue.
  1968.      </p>
  1969.  
  1970.      <blockquote class="fullwidth">
  1971. <div style="text-align:left">
  1972.  <tt>
  1973. <code><font color="blue">=== root@eureka (/dev/pts/1)</font> <font color="red">~</font> <font color="blue">86</font> &#45;&gt; <b><tt>find /Photos/grog/www &#45;type l | wc &#45;l</tt></b></code>
  1974. <br />&nbsp;&nbsp; &nbsp;1099
  1975. <br /><code><font color="blue">=== root@quartet (/dev/pts/0)</font> <font color="red">~</font> <font color="blue">100</font> &#45;&gt; <b><tt>find /newphotos/grog/www &#45;type l | wc &#45;l</tt></b></code>
  1976. <br />&nbsp;&nbsp; &nbsp;1099
  1977. <br />
  1978.  </tt>
  1979. </div>
  1980. </blockquote>
  1981.  
  1982.      <p>
  1983. Oh.  Exactly the same number of symlinks.  In fact, both disks have exactly 4005 symlinks.
  1984. Not the issue.
  1985.      </p>
  1986.  
  1987.      <p>
  1988. “Hard” links?  You'd see that from the link count.  But the directories that I looked at all
  1989. had exactly the same content and link counts.  Is it possible that two issues are ganging up
  1990. on me?  The “big” files in the <i>www</i> directories are supposed to be linked to the
  1991. corresponding file in two levels above in the hierarchy.  For example:
  1992.      </p>
  1993.  
  1994.      <blockquote class="fullwidth">
  1995. <div style="text-align:left">
  1996.  <tt>
  1997. <code><font color="blue">=== root@eureka (/dev/pts/1)</font> <font color="red">~</font> <font color="blue">89</font> &#45;&gt; <b><tt>ls &#45;l /Photos/grog/20240903/Hot&#45;water&#45;system&#45;1.jpeg /Photos/grog/www/20240903/big/Hot&#45;water&#45;system&#45;1.jpeg</tt></b></code>
  1998. <br />&#45;rwxr&#45;&#45;r&#45;&#45; &nbsp;1 grog &nbsp;wheel &nbsp;3,270,177 &nbsp;3 Sep 15:37 /Photos/grog/20240903/Hot&#45;water&#45;system&#45;1.jpeg
  1999. <br />&#45;rwxr&#45;&#45;r&#45;&#45; &nbsp;1 grog &nbsp;wheel &nbsp;3,270,177 &nbsp;3 Sep 15:37 /Photos/grog/www/20240903/big/Hot&#45;water&#45;system&#45;1.jpeg
  2000. <br />
  2001.  </tt>
  2002. </div>
  2003. </blockquote>
  2004.  
  2005.      <p>
  2006. But they're not!  I need to see whether I have broken something, and whether older images
  2007. are correctly linked.  In that case there's more to be repaired.
  2008.      </p>
  2009.      </div>
  2010.    ]]>
  2011.  </description>
  2012.  <dc:creator>Greg Lehey</dc:creator>
  2013.  <dc:date>2024-09-08T02:04:43+00:00</dc:date>
  2014. </item>
  2015.  
  2016.            
  2017. <!-- topic hk not selected
  2018.      <p>
  2019. It's been some time since we have had guests for dinner.  Ten years ago Chris Bahlo was a
  2020. regular visitor, but she has now found a life, and we no longer see her very often.  But
  2021. today we were able to host Pene Kirk, and <a href="http://www.lemis.com/yvonne/">Yvonne</a> went to some
  2022. trouble: bisque de fruits de mer, <a href="http://www.lemis.com/grog/recipes/bef-stroganoff.php">bef
  2023. Strogranoff</a> and poires gourmandes:
  2024.      </p>
  2025.  
  2026.      
  2027.      <p>
  2028. Somehow we spent more time talking about animals and health than I expected.  Pene was one
  2029. of the people who recommended <a href="https://en.wikipedia.org/wiki/Cataract">cataract</a> surgery when I was thinking about it, and she confirmed <a href="http://www.lemis.com/grog/diary-mar2024.php?subtitle=Simulating%20cataract%20surgery%20improvement&amp;article=D-20240324-004313#D-20240324-004313">my experience</a> that the cataract diminishes colour recognition and makes everything
  2030. look a bit yellowish.  And looking at yesterday's “mouse”, she agreed that it looked more
  2031. like a juvenile rat.  My assumption was based on the tail, which was hairless, but Pene
  2032. based her assessment on the shape of the head.
  2033.      </p>
  2034.  
  2035.            
  2036. End deselected topic hk (Dinner with Pene Kirk) -->
  2037.  
  2038.                  
  2039. <item>
  2040. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2024.php#D-20240909-015601</guid>
  2041. <link>http://www.lemis.com/grog/diary-sep2024.php?topics=c#D-20240909-015601</link>
  2042. <category>general</category>
  2043. <category>technology</category>
  2044. <category>opinion</category>
  2045. <title>Unwise actions</title>
  2046.  <description>
  2047.    <![CDATA[
  2048.    <div align="justify">
  2049.      <p>
  2050. Received in the mail today:
  2051.      </p>
  2052.  
  2053.        <a id="Photo-3" name="Photo-3"
  2054.          href="diary-sep2024.php?dirdate=20240908&amp;imagesizes=1112&amp;topics=c#Photo-3">
  2055.          <img alt="This should be Unwise-detail.png.  Is it missing?" border="0" id="Photo_3"
  2056.               title="Photo Unwise-detail.png.  Click to redisplay larger version of image."
  2057.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20240908/small/Unwise-detail.png"
  2058.               width="400" height="443.72469635628"
  2059.           /></a>
  2060.  
  2061.      <p>
  2062. Yes, I'm still with <a href="https://www.wise.com/">“Wise”</a>, despite my annoyance
  2063. last month.  My searches show that they're the best of a bad lot.  But now they're asking me
  2064. to migrate my secure desktop environment to my mobile phone.  Or are they?  This is just an
  2065. email, asking me to log in.  Most emails of that nature are scams.  What do they say on
  2066. their web site?
  2067.      </p>
  2068.  
  2069.      <p>
  2070. How do I access the web site?  Once again these <b><i>HORRIBLE</i></b> <a href="https://en.wikipedia.org/wiki/CAPTCHA">CAPTCHAs</a>, asking me to identify fire
  2071. hydrants, whatever they may be.  A quick Google search <a href="https://www.bundabergnow.com/2021/04/06/fire-hydrant-inspection-program-underway/">shows</a>:
  2072.      </p>
  2073.  
  2074.      <a href="https://www.bundabergnow.com/wp-content/uploads/2021/04/hydrant.jpg">
  2075.      <img alt=""
  2076.          title=".  Click to see in original size."
  2077.          src="https://www.bundabergnow.com/wp-content/uploads/2021/04/hydrant.jpg"
  2078.          width="300"
  2079.          /></a>
  2080.      <p>
  2081. But there was nothing like that on the CAPTCHA.  OK, “Wise” are a British company.
  2082. <a href="https://www.rbfrs.co.uk/fire-hydrants/what-is-a-fire-hydrant/">What do
  2083. British fire hydrants look like?</a> Pretty much the same:
  2084.      </p>
  2085.  
  2086.      <a href="http://www.lemis.com/grog/Day/20240908/hydrants1.jpeg">
  2087.      <img alt=""
  2088.          title=".  Click to see in original size."
  2089.          src="http://www.lemis.com/grog/Day/20240908/hydrants1.jpeg"
  2090.          width="300"
  2091.          /></a>
  2092.      <p>
  2093. But it seems that the CAPTCHA wants me to identify <a href="https://en.wikipedia.org/wiki/USA">US</a> fire hydrants!  How can they expect me to
  2094. know what they look like?  That reminds me of other things they want to know, like
  2095. identifying “crosswalks”, whatever they may do.  My guess is that <a href="https://en.wikipedia.org/wiki/AI">AI</a> can do better than I can.
  2096.      </p>
  2097.  
  2098.      <p>
  2099. Finally fought my way in and checked on the app.
  2100. <b><i>NOTHING AT ALL!</i></b>  No warnings, no mention of an app.  What kind of security is
  2101. that?  About the only thing that looks kosher is that the app is available in the <a href="https://play.google.com/store/apps/details?id=com.transferwise.android">Google app store</a>.  Signed in and got mail from Wise
  2102. confirming it, another marginal proof that it's legitimate.  And it allows me to sign in
  2103. with a thumbprint.
  2104.      </p>
  2105.  
  2106.      <p>
  2107. Am I really overly critical?  There are so many warning bells, and even the idea of using a
  2108. mobile phone for anything related to security scares me.  The app description includes:
  2109.      </p>
  2110.  
  2111.      <blockquote class="fullwidth">
  2112.        <div class="listitemwidth">
  2113.          Safety starts with understanding how developers collect and share your data. Data privacy
  2114.          and security practices may vary based on your use, region, and age. The developer provided
  2115.          this information and may update it over time.
  2116.        </div>
  2117.      </blockquote>
  2118.  
  2119.      <p>
  2120. Well, for me safety starts with understanding how malicious people can abuse the system.  On
  2121. the whole I trust the developers.  Since they asked me to review it, I gave it 2 stars with
  2122. the comment:
  2123.      </p>
  2124.  
  2125.      <blockquote class="fullwidth">
  2126.        <div class="listitemwidth">
  2127.          This app scares me.  "Wise" send me email asking me to install it by logging in from the
  2128.          email message.  Their web site doesn't mention it.  This has all the hallmarks of an
  2129.          exploit.  Hopefully I'm wrong.
  2130.        </div>
  2131.      </blockquote>
  2132.      </div>
  2133.    ]]>
  2134.  </description>
  2135.  <dc:creator>Greg Lehey</dc:creator>
  2136.  <dc:date>2024-09-09T01:56:01+00:00</dc:date>
  2137. </item>
  2138.  
  2139.            
  2140. <!-- topic ko not selected
  2141.      <p>
  2142. Jane Ashhurst is a fan of Japanese food, something that I still barely understand.  We had
  2143. planned to make <a href="https://en.wikipedia.org/wiki/Sushi">sushi</a>, something I
  2144. have never made before, but I decided that it might be a good idea to try it first.  I have
  2145. a sushi kit that I bought from <a href="https://en.wikipedia.org/wiki/ALDI">ALDI</a> years ago—so long that it has passed its use-by date—and today I tried making some.
  2146.      </p>
  2147.  
  2148.      <p>
  2149. The instructions for the pack were short but helpful.  300 g of rice.  Cook with (only!) 400
  2150. ml water, add vinegar (which proved to be 40 ml) to the mess and spread on the <a href="https://en.wikipedia.org/wiki/Nori">nori</a>.  Add filling ingredients.
  2151.      </p>
  2152.  
  2153.      <p>
  2154. After preparing the filling, back to look at the <a href="https://youtu.be/nIoOv6lWYnk">video</a> that I located <a href="http://www.lemis.com/grog/diary-jun2024.php?subtitle=Sushi?&amp;article=D-20240623-032843#D-20240623-032843">a couple of months ago</a>:
  2155.      </p>
  2156.  
  2157.      <iframe width="400"
  2158.            height="300"
  2159.            src="http://www.youtube.com/embed/nIoOv6lWYnk"
  2160. allowfullscreen
  2161.            frameborder="0" >
  2162.     </iframe>
  2163.  
  2164.      <p>
  2165. A little late.  I had done a number of things differently, including cutting the ingredients
  2166. finely.  But it was of help, and I followed it as best I could.
  2167.      </p>
  2168.  
  2169.      <p>
  2170. That wasn't very best:
  2171.      </p>
  2172.  
  2173.            
  2174.      <p>
  2175. Oh.  Not quite the way it looked in the video.  Try again:
  2176.      </p>
  2177.  
  2178.            
  2179.      <p>
  2180. At first sight that looked better, but only at first sight.  As soon as I touched it, it
  2181. self-destructed:
  2182.      </p>
  2183.  
  2184.      
  2185.      <p>
  2186. OK, the video shows the cook using half sheets of nori.  How about whole sheets?
  2187.      </p>
  2188.  
  2189.            
  2190.      <p>
  2191. That looks marginally better, but still nothing like good.  After a bit more
  2192. experimentation, ended up with:
  2193.      </p>
  2194.  
  2195.            
  2196.      <p>
  2197. What went wrong?  The biggest issue is wrapping.  How should the ends of the nori overlap?
  2198. Our expert cook didn't have an issue, of course, but I still don't know how to do it right.
  2199. Yes, leave the ends free of rice, but how do I get them to line up?  I need to find a video
  2200. “how to ruin sushi”.
  2201.      </p>
  2202.  
  2203.      <p>
  2204. In passing, it seems that a full width of nori takes about 100 g of rice, much more than I
  2205. expected.  And it was good to have the vinegar measured out in the kit.
  2206.  
  2207. states to use 20%  <i>by volume</i> vinegar to <i>dry</i> rice (which, of course, is already
  2208. cooked).  But the instructions seem to be right: 40 g vinegar to 300 g dry rice, or 13⅓%.
  2209.      </p>
  2210.      
  2211. End deselected topic ko (Sushi?) -->
  2212.  
  2213.            
  2214. <!-- topic ko not selected
  2215.      <p>
  2216. What goes with <a href="https://en.wikipedia.org/wiki/Sushi">sushi</a>?  <a href="https://en.wikipedia.org/wiki/Miso_soup">Miso soup</a>, it seems.  And I have plenty
  2217. of shiro <a href="https://en.wikipedia.org/wiki/Miso">miso</a>.  Just find a recipe.
  2218. It seems that a typical recipe is with <a href="https://en.wikipedia.org/wiki/Tofu">doufu</a> and spring onions.  But I need <a href="https://en.wikipedia.org/wiki/Dashi">dashi</a>.  I can make that in various ways.  One
  2219. is with seaweed.
  2220.      </p>
  2221.  
  2222.      <p>
  2223. <a href="http://www.lemis.com/grog/diary-aug2024.php?subtitle=Jane%20Ashhurst%20visits&amp;article=D-20240814-023243#D-20240814-023243">Last month</a> Jane Ashhurst brought some ingredients with her, including this:
  2224.      </p>
  2225.  
  2226.      
  2227.      <p>
  2228. What is it?  There was nothing written on the bag she put it in.  My guess is that it's some
  2229. kind of <a href="https://en.wikipedia.org/wiki/Kelp">kelp</a>, but what?  I'll have
  2230. to ask.
  2231.      </p>
  2232.  
  2233.      <p>
  2234. But then there was this:
  2235.      </p>
  2236.  
  2237.            
  2238.      <p>
  2239. Jane can't have bought that.  About the only thing that I could read, apart from the pretty
  2240. useless “Nutrition Facts”, was that it expired nearly 10 years ago.  And I have a number of
  2241. bags of it.  What is it?  With some searching I found the word <a href="https://en.wikipedia.org/wiki/Wakame">wakame</a> hidden on the side.  And the rest?
  2242. <a href="https://en.wikipedia.org/wiki/Google_Translate">Google Translate</a> to the
  2243. rescue:
  2244.      </p>
  2245.  
  2246.      
  2247.      <p>
  2248.  
  2249. Use in miso soup!  1 g for who knows how much soup?  That seemed a little, so I put in 2 g:
  2250.      </p>
  2251.  
  2252.      
  2253.      <p>
  2254. I don't think I've ever seen anything swell up that much.  In the end I threw half of it out
  2255. again.
  2256.      </p>
  2257.  
  2258.      <p>
  2259. Next, how much miso?  One recipe called for 2 tablespoons in 4 cups, whatever that may mean.
  2260. It seems that there are 16 US tablespoons to a US cup, so that's 1/32 of the volume.  While
  2261. searching, came up with another ratio of miso to water, ¼ teaspoon to 1 cup.  If I have that
  2262. right, it's a ratio of 1:192, almost nothing.  To be generous, I took a 1:20 ratio: 500 g
  2263. water, 25 g miso, 30 g spring onion and 65 g (the size of the block) of doufu.
  2264.      </p>
  2265.  
  2266.      <p>
  2267. The result?  Boring.  Certainly not too much miso.  After some investigation, it seems that
  2268. the wakame is not a substitute for dashi, as this photo from the <a href="https://en.wikipedia.org/wiki/Miso_soup">Wikipedia page</a> shows
  2269.      </p>
  2270.  
  2271.      <a href="https://upload.wikimedia.org/wikipedia/commons/thumb/e/e8/Miso_Soup_001.jpg/2560px-Miso_Soup_001.jpg">
  2272.      <img alt=""
  2273.          title=".  Click to see in original size."
  2274.          src="https://upload.wikimedia.org/wikipedia/commons/thumb/e/e8/Miso_Soup_001.jpg/2560px-Miso_Soup_001.jpg"
  2275.          width="300"
  2276.          /></a>
  2277.      <p>
  2278. So for next time we need to find some good dashi.
  2279.      </p>
  2280.      
  2281. End deselected topic ko (Miso soup) -->
  2282.  
  2283.                  
  2284. <item>
  2285. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2024.php#D-20240910-021044</guid>
  2286. <link>http://www.lemis.com/grog/diary-sep2024.php?topics=c#D-20240910-021044</link>
  2287. <category>technology</category>
  2288. <category>opinion</category>
  2289. <title>NBN advice for morons</title>
  2290.  <description>
  2291.    <![CDATA[
  2292.    <div align="justify">
  2293.      <p>
  2294. The <a href="https://www.nbnco.com.au/">National Broadband Network</a> sends
  2295. information emails from time to time, maybe monthly.  I've only just found out about them
  2296. and signed up.  I don't know why I bothered.
  2297.      </p>
  2298.  
  2299.      <p>
  2300. Today I got a newsletter offering <a href="https://www.nbnco.com.au/corporate-information/about-nbn-co/newsroom/articles/customer/avoid-the-wi-fi-gap-get-the-internet-you-need">Avoid the ‘Wi-Fi gap’ and get the internet you need</a> (capitalization original).  It
  2301. also offers a <a href="https://www.nbnco.com.au/corporate-information/about-nbn-co/newsroom/articles/customer/avoid-the-wi-fi-gap-get-the-internet-you-need#too-long-didnt-read">TL:DR</a> (punctuation also original), which can be summarized: buy new equipment and a
  2302. faster Internet link.  No mention of troubleshooting of any kind.  Thank you, NBN, for
  2303. reinforcing my negative impressions.
  2304.      </p>
  2305.  
  2306.      <p>
  2307. To be fair, though, there was more information about the upcoming outages: <a href="https://www.nbnco.com.au/support/network-status/nbn-fixed-wireless-outages">this page</a> explains that they're upgrading the system to new “5G mm Wave technology” (yet again
  2308. original typography).  What's that?  I hadn't heard of it, and there's <a href="https://www.celona.io/5g-lan/5g-mmwave">little to be found on the web</a> so far.
  2309. It's spelt “mmWave” and refers to frequencies of, well, millimetre wavelengths, specifically
  2310. above 24 GHz.  OK, well and good.  The bandwidths are more interesting.
  2311.      </p>
  2312.  
  2313.      <p>
  2314. And there's more about that <a href="https://www.nbnco.com.au/residential/upgrades/more-fixed-wireless#accordion-17dd10920d-item-9a853f7e1a">here</a>:
  2315.      </p>
  2316.  
  2317.      <blockquote class="fullwidth">
  2318. <p class="listitemwidth">
  2319.  nbn Fixed Wireless Home Fast offers peak wholesale download speeds between 200-250 and
  2320.  upload speeds between 8-20 Mbps.
  2321. </p>
  2322.  
  2323. <p class="listitemwidth">
  2324.  nbn Fixed Wireless Superfast offers peak wholesale download speeds of 400Mbps and upload
  2325.  speeds between 10-40 Mbps.
  2326. </p>
  2327.  
  2328. <p class="listitemwidth">
  2329.  Plus, we’ve boosted speeds on our most popular plan; Fixed Wireless Plus. Wholesale speed
  2330.  capability has now been lifted from up to 75/10Mbps to up to 100/20Mbps.
  2331. </p>
  2332.      </blockquote>
  2333.  
  2334.      <p>
  2335. That does sound interesting.  What does <a href="https://aussiebroadband.com.au/">Aussie Broadband</a> have to say about that?  Oh, another of these stupid <a href="https://en.wikipedia.org/wiki/2FA">2FA</a> things, and after accepting it, the page
  2336. hangs.  Aussie, can you do anything right any more?
  2337.      </p>
  2338.  
  2339.      <p>
  2340. And the outages?  <a href="https://www.nbnco.com.au/support/network-status/nbn-fixed-wireless-outages">The first
  2341. page</a> contains information about the upcoming outages, which <a href="http://www.lemis.com/grog/diary-aug2024.php?subtitle=Bloody%20NBN%20again!&amp;article=D-20240823-003119#D-20240823-003119">I calculated</a> as being 37 hours
  2342.      </p>
  2343.  
  2344.      <blockquote class="fullwidth">
  2345. <p class="listitemwidth">
  2346.  During these upgrade works, you may experience reductions in service and periodic outages
  2347.  as we roll out the upgrades in your area over several weeks.  In most cases, the outages
  2348.  may range from 3-4 minutes.  However, for others, some periodic outages may occur
  2349.  throughout the day and last for up to 12 hours. While the upgrade works are being
  2350.  completed in your area, you may experience more than one outage. We’ll notify your
  2351.  provider of any outages ahead of time, so they can keep you informed. We understand how
  2352.  frustrating outages can be, which is why we’re working hard to keep these to a minimum and
  2353.  reduce the occurrence of outages wherever we can.
  2354. </p>
  2355.  
  2356. <p class="listitemwidth">
  2357.  How we’re minimising the impact of potential outages:
  2358. </p>
  2359.  
  2360. <ul>
  2361.          <li class="fullwidth">
  2362.            <div class="list2width">
  2363.              We’re using temporary antennas to help maintain service for many customers.
  2364.            </div>
  2365.          </li>
  2366.  
  2367.          <li class="fullwidth">
  2368.            <div class="list2width">
  2369.              We’re migrating services to other local towers, where viable.
  2370.            </div>
  2371.          </li>
  2372.  
  2373.          <li class="fullwidth">
  2374.            <div class="list2width">
  2375.              We’re preparing equipment before arriving on site to minimise downtime.
  2376.            </div>
  2377.          </li>
  2378. </ul>
  2379.      </blockquote>
  2380.  
  2381.      <p>
  2382. “In most cases, the outages may range from 3-4 minutes.”  Admittedly, it can be longer.  And
  2383. I particularly appreciate the fact that they're preparing in advance.
  2384.      </p>
  2385.  
  2386.      <p>
  2387. And of course there's the other shoe: if I get connected to 5G mmWave, they'll have to
  2388. change the <del>antenna</del> ODU.  More downtime.
  2389.      </p>
  2390.      </div>
  2391.    ]]>
  2392.  </description>
  2393.  <dc:creator>Greg Lehey</dc:creator>
  2394.  <dc:date>2024-09-10T02:10:44+00:00</dc:date>
  2395. </item>
  2396.  
  2397.            
  2398. <item>
  2399. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2024.php#D-20240910-030520</guid>
  2400. <link>http://www.lemis.com/grog/diary-sep2024.php?topics=c#D-20240910-030520</link>
  2401. <category>technology</category>
  2402. <category>general</category>
  2403. <category>opinion</category>
  2404. <title>Academia surpasses itself</title>
  2405.  <description>
  2406.    <![CDATA[
  2407.    <div align="justify">
  2408.      <p>
  2409. For years I've been getting email from <a href="https://en.wikipedia.org/wiki/Academia">Academia</a> with questions like “Greg Lehey ✏️ Did you write "Treasurer"?”.  To answer I
  2410. first need to pay them money!  I can do without that.
  2411.      </p>
  2412.  
  2413.      <p>
  2414. But today I got the ultimate question:
  2415.      </p>
  2416.  
  2417.      <blockquote class="fullwidth">
  2418. <div style="text-align:left">
  2419.  <tt>
  2420. 131 ND &nbsp;08&#45;09&#45;2024 To academia@lem ( 903) Mentioned by Greg Le &nbsp; $1, 30 day trial. “G. Lehey” mentioned by “Greg Lehey”
  2421.  </tt>
  2422. </div>
  2423. </blockquote>
  2424.      </div>
  2425.    ]]>
  2426.  </description>
  2427.  <dc:creator>Greg Lehey</dc:creator>
  2428.  <dc:date>2024-09-10T03:05:20+00:00</dc:date>
  2429. </item>
  2430.  
  2431.                  
  2432. <!-- topic ko not selected
  2433.      <p>
  2434. <a href="http://www.lemis.com/grog/diary-apr2024.php?subtitle=Finally%20a%20chili%20sauce?&amp;article=D-20240429-002628#D-20240429-002628">A few months back</a> I found a <a href="http://www.lemis.com/grog/recipes/chili-sauce.php">chili sauce
  2435. mix</a> that I liked, at least for <a href="http://www.lemis.com/grog/recipes/huevos-rancheros.php"><i>huevos
  2436. rancheros</i></a>.  But I've finished the batch, time for a new batch.
  2437.      </p>
  2438.  
  2439.      <p>
  2440. Why so much sesame oil?  Why sesame oil at all?  Despite the origins, this isn't intended
  2441. for Korean food.  So I left it out, and while I was at it, I added even more garlic.
  2442.      </p>
  2443.  
  2444.      <p>
  2445. And the result?  Tasted at least as good, but it was so watery.  Why?  My guess is that the
  2446. <a href="https://en.wikipedia.org/wiki/Gochujang">gochujang</a> that I used last
  2447. time wasn't the freshest, and it had dried out.
  2448.      </p>
  2449.      
  2450. End deselected topic ko (Chili sauce revisited) -->
  2451.  
  2452.            
  2453. <item>
  2454. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2024.php#D-20240911-021507</guid>
  2455. <link>http://www.lemis.com/grog/diary-sep2024.php?topics=c#D-20240911-021507</link>
  2456. <category>technology</category>
  2457. <category>opinion</category>
  2458. <title>Understanding the photo size discrepancy</title>
  2459.  <description>
  2460.    <![CDATA[
  2461.    <div align="justify">
  2462.      <p>
  2463. It's been <a href="http://www.lemis.com/grog/diary-sep2024.php?topics=c&amp;subtitle=Understanding%20the%20disk%20copy%20issues&amp;article=D-20240908-020443#D-20240908-020443">a few days</a> since I investigated the cause of my excess data usage on the
  2464. new <i>/Photos</i> disk.  I had suspected issues with links between my photos processing
  2465. directory and the “big” versions in the web hierarchy.  Both images are the same, so they
  2466. should be links, not copies.  But preliminary investigations showed that they were copies on
  2467. the original as well.
  2468.      </p>
  2469.  
  2470.      <p>
  2471. That was for photos taken on <a href="http://www.lemis.com/grog/diary-sep2024.php?topics=c#3">3 September 2024</a>.  Was it always that way?
  2472. Off looking.  No!
  2473.      </p>
  2474.  
  2475.      <blockquote class="fullwidth">
  2476. <div style="text-align:left">
  2477.  <tt>
  2478. <code><font color="blue">=== root@quartet (/dev/pts/0)</font> <font color="red">/Photos/grog</font> <font color="blue">119</font> &#45;&gt; <b><tt>l &#45;i $DATE/*jpeg www/$DATE/big</tt></b></code>
  2479. <br />1480997 &#45;rwxr&#45;&#45;r&#45;&#45; &nbsp;2 grog lemis 3,544,601 &nbsp;1 Jan &nbsp;2015 20150101/Ceiling.jpeg
  2480. <br />
  2481. <br />www/20150101/big:
  2482. <br />1480997 &#45;rwxr&#45;&#45;r&#45;&#45; &nbsp;2 grog lemis 3,544,601 &nbsp;1 Jan &nbsp;2015 Ceiling.jpeg
  2483. <br />
  2484.  </tt>
  2485. </div>
  2486. </blockquote>
  2487.  
  2488.      <p>
  2489. That's the same file, as intended.  Why did it stop?  It seems that things changed in
  2490. mid-April this year.  But why?  My scripts haven't changed in a couple of years.
  2491.      </p>
  2492.  
  2493.      <p>
  2494. More investigation shows, in <i>/Photos/Tools/docopy</i>:
  2495.      </p>
  2496.  
  2497.      <blockquote class="fullwidth">
  2498. <div style="text-align:left">
  2499.  <tt>
  2500. if [ `hostname &#45;s` = "eureka" ]; then
  2501. <br />&nbsp;&nbsp;CP=ln
  2502. <br />else
  2503. <br />&nbsp;&nbsp;CP="cp &#45;p"
  2504. <br />fi
  2505. <br />
  2506.  </tt>
  2507. </div>
  2508. </blockquote>
  2509.  
  2510.      <p>
  2511. That makes sense, up to a point.  At the the time, <a href="http://www.lemis.com/grog/diary-sep2020.php?subtitle=Integrating%20disks,%20day%203&amp;article=D-20200906-034855#D-20200906-034855">4 years ago</a>, I moved <a href="http://www.lemis.com/yvonne/">Yvonne's</a> photos to a disk on her
  2512. machine, <i>lagoon</i>.  But the web files still needed to be on <i>eureka</i>.
  2513.      </p>
  2514.  
  2515.      <p>
  2516. Now, however, I'm doing my processing on <i>hydra</i>, but accessing <i>eureka:/Photos</i>
  2517. via <a href="https://en.wikipedia.org/wiki/Network_File_System">NFS</a>.  And I'm
  2518. still copying!  Yes, I could check for <i>hydra</i> too, but it makes more sense to check
  2519. whether the source and destination are on the same file system.
  2520.      </p>
  2521.  
  2522.      <p>
  2523. How do you do that?  It seems that there should be a simple way, but I didn't find it.
  2524. Instead I used the output of <i>df(1)</i>:
  2525.      </p>
  2526.  
  2527.      <blockquote class="fullwidth">
  2528. <div style="text-align:left">
  2529.  <tt>
  2530. SRCDISK=`df .`
  2531. <br />DSTDISK=`df ${WEBDIR}`
  2532. <br />if [ "$SRCDISK" = "$DSTDISK" ]; then
  2533. <br />&nbsp;&nbsp;# Yes: link
  2534. <br />&nbsp;&nbsp;CP=ln
  2535. <br />else
  2536. <br />&nbsp;&nbsp;# No: copy
  2537. <br />&nbsp;&nbsp;CP="cp &#45;p"
  2538. <br />fi
  2539. <br />
  2540.  </tt>
  2541. </div>
  2542. </blockquote>
  2543.  
  2544.      <p>
  2545. And that works.  A simple <tt>make&nbsp;web</tt> should do the trick:
  2546.      </p>
  2547.  
  2548.      <blockquote class="fullwidth">
  2549. <div style="text-align:left">
  2550.  <tt>
  2551. <code><font color="blue">=== grog@hydra (/dev/pts/23)</font> <font color="red">/Photos/grog/20240831</font> <font color="blue">189</font> &#45;&gt; <b><tt>du &#45;sc . ../www/20240831/</tt></b></code>
  2552. <br />21203 &nbsp; .
  2553. <br />149 &nbsp; &nbsp; ../www/20240831/
  2554. <br />21352 &nbsp; total
  2555. <br /><code><font color="blue">=== grog@hydra (/dev/pts/23)</font> <font color="red">/Photos/grog/20240831</font> <font color="blue">190</font> &#45;&gt; <b><tt>df &#45;i .</tt></b></code>
  2556. <br />Filesystem &nbsp; &nbsp; 1048576&#45;blocks &nbsp; &nbsp; &nbsp;Used &nbsp; Avail Capacity &nbsp; iused &nbsp; &nbsp; ifree %iused &nbsp;Mounted on
  2557. <br />eureka:/Photos &nbsp; &nbsp; &nbsp;7,629,565 6,828,390 724,879 &nbsp; &nbsp;90% 1,765,566 1,478,080 &nbsp; 54% &nbsp; /Photos
  2558. <br /><code><font color="blue">=== grog@hydra (/dev/pts/23)</font> <font color="red">/Photos/grog/20240831</font> <font color="blue">191</font> &#45;&gt; <b><tt>make web/</tt></b></code>
  2559. <br />...
  2560. <br /><code><font color="blue">=== grog@hydra (/dev/pts/23)</font> <font color="red">/Photos/grog/20240831</font> <font color="blue">192</font> &#45;&gt; <b><tt>df &#45;i .</tt></b></code>
  2561. <br />Filesystem &nbsp; &nbsp; 1048576&#45;blocks &nbsp; &nbsp; &nbsp;Used &nbsp; Avail Capacity &nbsp; iused &nbsp; &nbsp; ifree %iused &nbsp;Mounted on
  2562. <br />eureka:/Photos &nbsp; &nbsp; &nbsp;7,629,565 6,828,244 725,024 &nbsp; &nbsp;90% 1,765,588 1,478,058 &nbsp; 54% &nbsp; /Photos
  2563. <br /><code><font color="blue">=== grog@hydra (/dev/pts/23)</font> <font color="red">/Photos/grog/20240831</font> <font color="blue">193</font> &#45;&gt; <b><tt>du &#45;sc . ../www/20240831/</tt></b></code>
  2564. <br />21203 &nbsp; .
  2565. <br />3 &nbsp; &nbsp; &nbsp; ../www/20240831/
  2566. <br />21206 &nbsp; total
  2567. <br />
  2568.  </tt>
  2569. </div>
  2570. </blockquote>
  2571.  
  2572.      <p>
  2573. The 3 MB left in the <i>www</i> directory were the small and tiny images.
  2574.      </p>
  2575.  
  2576.      <p>
  2577. Now to fix up <i>/Photos</i>:
  2578.      </p>
  2579.  
  2580.      <blockquote class="fullwidth">
  2581. <div style="text-align:left">
  2582.  <tt>
  2583. <code><font color="blue">=== grog@hydra (/dev/pts/18)</font> <font color="red">/Photos/grog/www</font> <font color="blue">4</font> &#45;&gt; <b><tt>for i in 20240[4&#45;9]*; do (cd ../$i &amp;&amp; make web); done</tt></b></code>
  2584.  </tt>
  2585. </div>
  2586. </blockquote>
  2587.  
  2588.      <p>
  2589. The result, before and after:
  2590.      </p>
  2591.  
  2592.      <blockquote class="fullwidth">
  2593. <div style="text-align:left">
  2594.  <tt>
  2595. <code><font color="blue">=== grog@hydra (/dev/pts/24)</font> <font color="red">~</font> <font color="blue">8</font> &#45;&gt; <b><tt>df &#45;i /Photos/</tt></b></code>
  2596. <br />Filesystem &nbsp; &nbsp; 1048576&#45;blocks &nbsp; &nbsp; &nbsp;Used &nbsp; Avail Capacity &nbsp; iused &nbsp; &nbsp; ifree %iused &nbsp;Mounted on
  2597. <br />eureka:/Photos &nbsp; &nbsp; &nbsp;7,629,565 6,828,244 725,024 &nbsp; &nbsp;90% 1,765,554 1,478,092 &nbsp; 54% &nbsp; /Photos
  2598. <br />...
  2599. <br /><code><font color="blue">=== grog@hydra (/dev/pts/24)</font> <font color="red">~</font> <font color="blue">12</font> &#45;&gt; <b><tt>df &#45;i /Photos/</tt></b></code>
  2600. <br />Filesystem &nbsp; &nbsp; 1048576&#45;blocks &nbsp; &nbsp; &nbsp;Used &nbsp; Avail Capacity &nbsp; iused &nbsp; &nbsp; ifree %iused &nbsp;Mounted on
  2601. <br />eureka:/Photos &nbsp; &nbsp; &nbsp;7,629,565 6,820,747 732,522 &nbsp; &nbsp;90% 1,764,078 1,479,568 &nbsp; 54% &nbsp; /Photos
  2602. <br />
  2603.  </tt>
  2604. </div>
  2605. </blockquote>
  2606.  
  2607.      <p>
  2608. It doesn't look like much, but it's still a saving of 7.5 GB.
  2609.      </p>
  2610.  
  2611.      <p>
  2612. So that explains the first issue.  The second is the fact that apparently <i>all</i> the
  2613. directories that I have looked at on <i>hydra</i> don't have linked files.  Is that an issue
  2614. with <a href="https://en.wikipedia.org/wiki/Samba_(software)">Samba</a> (unlikely)
  2615. or because I started with <i>tar</i> and completed with <i>Samba</i>?  The way either works
  2616. would be to copy the date files separately from the <i>www</i> hierarchy.  To be
  2617. investigated.
  2618.      </p>
  2619.      </div>
  2620.    ]]>
  2621.  </description>
  2622.  <dc:creator>Greg Lehey</dc:creator>
  2623.  <dc:date>2024-09-11T02:15:07+00:00</dc:date>
  2624. </item>
  2625.  
  2626.            
  2627. <item>
  2628. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2024.php#D-20240911-030504</guid>
  2629. <link>http://www.lemis.com/grog/diary-sep2024.php?topics=c#D-20240911-030504</link>
  2630. <category>technology</category>
  2631. <category>opinion</category>
  2632. <title>Aussie web site hangs</title>
  2633.  <description>
  2634.    <![CDATA[
  2635.    <div align="justify">
  2636.      <p>
  2637. Why can't I access the tariff information on the <a href="https://aussiebroadband.com.au/">Aussie Broadband</a> web site?  Started writing an
  2638. email and looked on the web site for information.  Pop!  Up came a “chat” window.  OK, ask
  2639. Dominic.  No, site working fine.  Will he report that it isn't for me?  No, not worth the
  2640. trouble.
  2641.      </p>
  2642.  
  2643.      <p>
  2644. With a bit of insistence, along with my possibly visible negative response to the “are you
  2645. happy with this response?” popup, he went off and investigated, something that took a total
  2646. of round an hour, including a restart because of a timeout (7 minutes, he says) on his part.
  2647. I ticked “send me the transcript” box for both chats, but I never saw one.
  2648.      </p>
  2649.  
  2650.      <p>
  2651. The startling answer: it's because of my “plan”, only 25/5 Mb/s.  It's no longer in the
  2652. Aussie offerings, and the web code hangs because of some unexpected issue.  Will they fix
  2653. it?  No.
  2654.      </p>
  2655.  
  2656.      <p>
  2657. One thing that Dominic did give me was the <a href="https://www.aussiebroadband.com.au/internet/nbn-plans/">correct page to find the
  2658. “plans”</a>, starting at $69 per month—they say.  But all it offers is “Fixed wireless
  2659. plus” (100/20) for $89 per month unlimited.  It seems that that's all they currently offer.
  2660. That's $14 more than I'm currently paying, so I'll pass.  Presumably they'll force my hand
  2661. some time.
  2662.      </p>
  2663.      </div>
  2664.    ]]>
  2665.  </description>
  2666.  <dc:creator>Greg Lehey</dc:creator>
  2667.  <dc:date>2024-09-11T03:05:04+00:00</dc:date>
  2668. </item>
  2669.  
  2670.                  
  2671. <!-- topic Hko not selected
  2672.      <p>
  2673. When I was a lad, I used to enjoy eating <a href="http://www.lemis.com/grog/recipes/penang-laksa.php">Penang
  2674. laksa</a> on frequent occasions.
  2675.      </p>
  2676.  
  2677.      <p>
  2678. Or did I?  Looking back at my diary, I find only two mentions, both in (<a href="http://www.lemis.com/grog/diary-aug1966.php#24">August</a> and <a href="http://www.lemis.com/grog/diary-nov1966.php#24">November</a>) 1966.  Then I ate much more in
  2679. <a href="https://en.wikipedia.org/wiki/Sarawak">Sarawak</a> in 1969.  But that was
  2680. probably different, as noted by <a href="diary-people.php#Sonny_Rajah">Sonny Rajah's</a>
  2681. rejection of it on <a href="http://www.lemis.com/grog/diary-aug1969.php?topics=c#26">26 August 1969</a>.  Even then I only ate it 19 times.
  2682.      </p>
  2683.  
  2684.      <p>
  2685. So it seems that my love of Penang Laksa is more a fond memory than anything that I really
  2686. liked at the time.  Still, when I found a way to make it myself <a href="http://www.lemis.com/grog/diary-jan2017.php?subtitle=Laksa%20again&amp;article=D-20170118-004228#D-20170118-004228">nearly 8 years ago</a>.  And since then I've eaten it on a regular basis, though it's no
  2687. longer such a favourite, and I've found other things that I prefer for breakfast.
  2688.      </p>
  2689.      
  2690. End deselected topic Hko (Laksa over the millennia) -->
  2691.  
  2692.            
  2693. <!-- topic ko not selected
  2694.      <p>
  2695. Richmond's <a href="http://www.lemis.com/grog/recipes/penang-laksa.php">Penang laksa</a> isn't really as sour
  2696. as I like, so I add <a href="https://en.wikipedia.org/wiki/Tamarind">tamarind</a> to
  2697. the mixture.  That's easy enough—I have tamarind paste that I just mix in—but what's this?
  2698.      </p>
  2699.  
  2700.            
  2701.      <p>
  2702. I've had it for ever, though it's too polite to say how old it is.  It was a 375 g pack of
  2703. “wet tamarind”, and now it only weighs 322 g and isn't wet at all.  But it doesn't look as
  2704. if it has gone bad, so I cut off some slices and tried to mix them with water:
  2705.      </p>
  2706.  
  2707.      <div align="left">
  2708.      </div>
  2709.  
  2710.      <p>
  2711. My guess is that it should have been strained, but I didn't do that.  Despite everything, it
  2712. tasted OK.
  2713.      </p>
  2714.      
  2715. End deselected topic ko () -->
  2716.  
  2717.            
  2718. <!-- topic Po not selected
  2719.      <p>
  2720. Today was the highlight of the US election campaign, the debate between <a href="https://en.wikipedia.org/wiki/Donald_Trump">Donald Trump</a> and <a href="https://en.wikipedia.org/wiki/Kamala_Harris">Kamala Harris</a>.
  2721.      </p>
  2722.  
  2723.      <iframe width="400"
  2724.            height="300"
  2725.            src="http://www.youtube.com/embed/VgsC_aBquUE"
  2726. allowfullscreen
  2727.            frameborder="0" >
  2728.     </iframe>
  2729.  
  2730.      <p>
  2731. I watched a little of it, but clearly I wasn't the only one.  And once again, the
  2732. commentaries didn't match my own observations.  But I can spend more time than I have
  2733. reading the commentaries.  The bottom line seems to be that Harris ran Trump into the
  2734. ground, but that there's no particular reason that it will change the outcome.
  2735.      </p>
  2736.  
  2737.      <p>
  2738. But the <a href="https://en.wikipedia.org/wiki/New_York_Times">New York Times</a> advertising department found it a good reason to subscribe.
  2739.      </p>
  2740.  
  2741.      <blockquote class="fullwidth">
  2742. <div style="text-align:left">
  2743.  <tt>
  2744. From nytimes@e.newyorktimes.com &nbsp;Wed Sep 11 14:04:16 AEST 2024
  2745. <br />Date: Wed, 11 Sep 2024 04:04:13 +0000
  2746. <br />Subject: Sale: Save now before the U.S. debate: A$0.50 a week.
  2747. <br />
  2748.  </tt>
  2749. </div>
  2750. </blockquote>
  2751.  
  2752.      <p>
  2753. That was clearly sent 1½ hours after the end of the debate.  Is that a good advertisement
  2754. for the timeliness of their reporting?
  2755.      </p>
  2756.      
  2757. End deselected topic Po (Towards president Kamala) -->
  2758.  
  2759.            
  2760. <item>
  2761. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2024.php#D-20240912-044332</guid>
  2762. <link>http://www.lemis.com/grog/diary-sep2024.php?topics=c#D-20240912-044332</link>
  2763. <category>technology</category>
  2764. <category>opinion</category>
  2765. <title>Understanding shell syntax</title>
  2766.  <description>
  2767.    <![CDATA[
  2768.    <div align="justify">
  2769.      <p>
  2770. While investigating my lost space on my new photo disk, entered this:
  2771.      </p>
  2772.  
  2773.      <blockquote class="fullwidth">
  2774. <div style="text-align:left">
  2775.  <tt>
  2776. <code><font color="blue">=== grog@eureka (/dev/pts/6)</font> <font color="red">/Photos/grog</font> <font color="blue">17</font> &#45;&gt; <b><tt>DATE=20101009 ls &#45;li $DATE/*jpeg www/$DATE/big</tt></b></code>
  2777. <br />ls: /*jpeg: No such file or directory
  2778. <br />ls: www//big: No such file or directory
  2779. <br />
  2780.  </tt>
  2781. </div>
  2782. </blockquote>
  2783.  
  2784.      <p>
  2785. Huh?
  2786.      </p>
  2787.  
  2788.      <blockquote class="fullwidth">
  2789. <div style="text-align:left">
  2790.  <tt>
  2791. <code><font color="blue">=== grog@eureka (/dev/pts/6)</font> <font color="red">/Photos/grog</font> <font color="blue">18</font> &#45;&gt; <b><tt>DATE=20101009</tt></b></code>
  2792. <br /><code><font color="blue">=== grog@eureka (/dev/pts/6)</font> <font color="red">/Photos/grog</font> <font color="blue">19</font> &#45;&gt; <b><tt>ls &#45;li $DATE/*jpeg www/$DATE/big</tt></b></code>
  2793. <br /><code><font color="blue">=== grog@hydra (/dev/pts/28)</font> <font color="red">/Photos/grog</font> <font color="blue">14</font> &#45;&gt; <b><tt>ls &#45;li $DATE/*jpeg www/$DATE/big</tt></b></code>
  2794. <br />&nbsp;863295 &#45;rwxrw&#45;r&#45;&#45; &nbsp;2 grog &nbsp;lemis &nbsp;3099465 &nbsp;9 Oct &nbsp;2010 20101009/dam&#45;dup&#45;panorama.jpeg
  2795. <br />...
  2796. <br />www/20101009/big:
  2797. <br />&nbsp;863295 &#45;rwxrw&#45;r&#45;&#45; &nbsp;2 grog &nbsp;lemis &nbsp;3099465 &nbsp;9 Oct &nbsp;2010 dam&#45;dup&#45;panorama.jpeg
  2798. <br />...
  2799. <br />
  2800.  </tt>
  2801. </div>
  2802. </blockquote>
  2803.  
  2804.      <p>
  2805. Why didn't it work the first time round?  I do this sort of thing all the time.  Some
  2806. discussion on IRC, culminating in: yes, you can set environment variables like that, but
  2807. they only get inserted into the environment of processes started by this command.
  2808. They <i>don't</i> apply to the command itself.
  2809.      </p>
  2810.  
  2811.      <p>
  2812. Somehow that seems counterintuitive.
  2813.      </p>
  2814.      </div>
  2815.    ]]>
  2816.  </description>
  2817.  <dc:creator>Greg Lehey</dc:creator>
  2818.  <dc:date>2024-09-12T04:43:32+00:00</dc:date>
  2819. </item>
  2820.  
  2821.                  
  2822. <!-- topic ko not selected
  2823.      <p>
  2824. I had some broccoli left over.  What should I do with it?  Build a breakfast around it:
  2825.      </p>
  2826.  
  2827.      <div align="left">
  2828.      </div>
  2829.  
  2830.      <p>
  2831. Nothing special, but for reference:
  2832.      </p>
  2833.  
  2834.          <table summary="Ingredients">
  2835.        <tr>
  2836.          <td align="right"><b>quantity</b></td>
  2837.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2838.          <td><b>ingredient</b> </td>
  2839.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2840.          <td><b>step</b> </td>
  2841.        </tr>
  2842.  
  2843.       <tr>
  2844.          <td valign="top" align="right">67 g</td>
  2845.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2846.          <td valign="top" align="left">doufu</td>
  2847.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2848.          <td valign="top" align="right">1</td>
  2849.       </tr>
  2850.  
  2851.       <tr>
  2852.          <td valign="top" align="right">50 g</td>
  2853.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2854.          <td valign="top" align="left">beef</td>
  2855.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2856.          <td valign="top" align="right">1</td>
  2857.       </tr>
  2858.       <tr>
  2859.         <td>
  2860.         </td>
  2861.       </tr>
  2862.  
  2863.       <tr>
  2864.          <td valign="top" align="right">15 g</td>
  2865.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2866.          <td valign="top" align="left">spring onions</td>
  2867.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2868.          <td valign="top" align="right">2</td>
  2869.       </tr>
  2870.  
  2871.       <tr>
  2872.          <td valign="top" align="right">2</td>
  2873.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2874.          <td valign="top" align="left">shiitake mushrooms</td>
  2875.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2876.          <td valign="top" align="right">2</td>
  2877.       </tr>
  2878.  
  2879.       <tr>
  2880.          <td valign="top" align="right">38 g</td>
  2881.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2882.          <td valign="top" align="left">broccoli</td>
  2883.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2884.          <td valign="top" align="right">2</td>
  2885.       </tr>
  2886.  
  2887.       <tr>
  2888.          <td valign="top" align="right">17 g</td>
  2889.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2890.          <td valign="top" align="left">red capsicum</td>
  2891.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2892.          <td valign="top" align="right">2</td>
  2893.       </tr>
  2894.       <tr>
  2895.         <td>
  2896.         </td>
  2897.       </tr>
  2898.  
  2899.       <tr>
  2900.          <td valign="top" align="right">30 g</td>
  2901.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2902.          <td valign="top" align="left">light soya sauce</td>
  2903.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2904.          <td valign="top" align="right">3</td>
  2905.       </tr>
  2906.  
  2907.       <tr>
  2908.          <td valign="top" align="right">12.5 g</td>
  2909.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2910.          <td valign="top" align="left">dark soya sauce</td>
  2911.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2912.          <td valign="top" align="right">3</td>
  2913.       </tr>
  2914.  
  2915.       <tr>
  2916.          <td valign="top" align="right">30 g</td>
  2917.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2918.          <td valign="top" align="left">shiro miso</td>
  2919.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2920.          <td valign="top" align="right">3</td>
  2921.       </tr>
  2922.       <tr>
  2923.         <td>
  2924.         </td>
  2925.       </tr>
  2926.  
  2927.       <tr>
  2928.          <td valign="top" align="right">150 g</td>
  2929.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2930.          <td valign="top" align="left">Shandong ramen noodles</td>
  2931.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2932.          <td valign="top" align="right">4</td>
  2933.       </tr>
  2934.       <tr>
  2935.         <td>
  2936.         </td>
  2937.       </tr>
  2938.      </table>
  2939.  
  2940.      <p>
  2941. About the only thing of interest is how to fry the doufu.  It sticks to the pan:
  2942.      </p>
  2943.  
  2944.      
  2945.      <p>
  2946. There must be a way of preventing that.  Heat in a microwave oven first?
  2947.      </p>
  2948.      
  2949. End deselected topic ko (More breakfast experiments) -->
  2950.  
  2951.            
  2952. <item>
  2953. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2024.php#D-20240913-023625</guid>
  2954. <link>http://www.lemis.com/grog/diary-sep2024.php?topics=c#D-20240913-023625</link>
  2955. <category>technology</category>
  2956. <category>opinion</category>
  2957. <title>Disk copy pain</title>
  2958.  <description>
  2959.    <![CDATA[
  2960.    <div align="justify">
  2961.      <p>
  2962. Copying my photo disk to the new 16 TB drive still isn't done!  My first attempt ended up
  2963. with far more <a href="https://en.wikipedia.org/wiki/inode">inode</a> and data use
  2964. than the old disk.  Part of that was because I used the wrong invocation: I omitted
  2965. the <b>H</b> option, meaning that <i>rsync</i> created new files for each copy of a link.
  2966. OK, start again with <i>/Photos/grog</i> to see if it works.
  2967.      </p>
  2968.  
  2969.      <p>
  2970. But it put the result in <i>/newphotos/grog/grog</i>, and I couldn't find a way to stop it.
  2971. Next time I'll try something like <i>cd</i> to the source directory and referring to it
  2972. as <b>.</b> (dot), specifying the destination accordingly.  But while I looked at it, it
  2973. occurred to me that my file system parameters were significantly different from the
  2974. old <i>/Photos</i>.  After removing size parameters, I had:
  2975.      </p>
  2976.  
  2977.      <blockquote class="fullwidth">
  2978. <div style="text-align:left">
  2979.  <tt>
  2980. <i>/Photos</i>: &nbsp; &nbsp;newfs &#45;L Photos &#45;O 2 &#45;U &#45;a 4 &#45;b 32768 &#45;d 32768 &#45;e 4096 &#45;f 4096 &#45;g 3145728 &#45;h 64 &#45;i 2469888 &#45;j &#45;k 1152 &#45;m 1 &#45;o space /dev/ada1p1
  2981. <br /><i>/newphotos</i>: newfs &#45;L Photos &#45;O 2 &#45;U &#45;a 64 &#45;b 16384 &#45;d 16384 &#45;e 2048 &#45;f 2048 &#45;g 3145728 &#45;h 64 &#45;i 2752512 &#45;m 1 &#45;o space /dev/ada1p1
  2982. <br />
  2983.  </tt>
  2984. </div>
  2985. </blockquote>
  2986.  
  2987.      <p>
  2988. OK, what the hell, let's start again from
  2989. scratch.  <i>umount</i> <i>/newphotos</i>, <i>newfs</i> it again with the new parameters, and
  2990. start again.
  2991.      </p>
  2992.  
  2993.      <p>
  2994. <i>umount</i> hung!  I couldn't stop it, but it was running and consuming CPU time:
  2995.      </p>
  2996.  
  2997.      <blockquote class="fullwidth">
  2998. <div style="text-align:left">
  2999.  <tt>
  3000. <code><font color="blue">=== grog@quartet (/dev/pts/2)</font> <font color="red">~</font> <font color="blue">121</font> &#45;&gt; <b><tt>date; ps aux | grep umount</tt></b></code>
  3001. <br />Thu 12 Sep 2024 13:33:10 AEST
  3002. <br />root &nbsp; &nbsp; &nbsp; 23962 &nbsp; 2.4 &nbsp;0.0 &nbsp;12728 &nbsp;1820 &nbsp;0 &nbsp;DL+ &nbsp;13:19 &nbsp; &nbsp; &nbsp; 0:15.09 umount /newphotos
  3003. <br />...
  3004. <br /><code><font color="blue">=== grog@quartet (/dev/pts/2)</font> <font color="red">~</font> <font color="blue">122</font> &#45;&gt; <b><tt>date; ps aux | grep umount</tt></b></code>
  3005. <br />Thu 12 Sep 2024 13:38:15 AEST
  3006. <br />root &nbsp; &nbsp; &nbsp; 23962 &nbsp; 2.4 &nbsp;0.0 &nbsp;12728 &nbsp;1820 &nbsp;0 &nbsp;DL+ &nbsp;13:19 &nbsp; &nbsp; &nbsp; 0:25.72 umount /newphotos
  3007. <br />
  3008.  </tt>
  3009. </div>
  3010. </blockquote>
  3011.  
  3012.      <p>
  3013. That's round 2 seconds of CPU time per minute.  It was also performing about 200 I/Os per
  3014. second.  It finally finished at 13:48.  Extrapolating, that's round 45 seconds of CPU time
  3015. and 27,000 I/O transfers, at a guess 250 MB.  What was it doing?
  3016.      </p>
  3017.  
  3018.      <p>
  3019. Finally ran <i>newfs</i> and started the transfer again.  But how?  <i>tar</i> seems to be
  3020. the right way to go, but last time it failed in mid-transfer.  For no reason that still
  3021. seems good I decided to write a <i>tar</i> archive on the new disk.  And that set off
  3022. merrily with a transfer rate of up to 111 MB/s, pretty much exactly the bandwidth of the
  3023. connection, and seldom dropping below 100 MB/s.
  3024.      </p>
  3025.  
  3026.      <p>
  3027. OK, how about a compressed <i>tar</i>?  That way I might miss the bottleneck of the wire.
  3028. But no, the transfer rate dropped to round 35 MB/s: the compression process maxed out a CPU.
  3029. And there's no way I could get a 3-fold compression with my photos.  So plain tar it is.
  3030. 6.8 TB at 100 MB/s would take 19 hours, so no more work today.
  3031.      </p>
  3032.      </div>
  3033.    ]]>
  3034.  </description>
  3035.  <dc:creator>Greg Lehey</dc:creator>
  3036.  <dc:date>2024-09-13T02:36:25+00:00</dc:date>
  3037. </item>
  3038.  
  3039.            
  3040. <item>
  3041. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2024.php#D-20240913-031316</guid>
  3042. <link>http://www.lemis.com/grog/diary-sep2024.php?topics=c#D-20240913-031316</link>
  3043. <category>technology</category>
  3044. <category>opinion</category>
  3045. <title>NBN outages: yes, no, maybe?</title>
  3046.  <description>
  3047.    <![CDATA[
  3048.    <div align="justify">
  3049.      <p>
  3050. Email from <a href="https://aussiebroadband.com.au/">Aussie Broadband</a> today:
  3051.      </p>
  3052.  
  3053.      <blockquote class="fullwidth">
  3054. <div style="text-align:left">
  3055.  <tt>
  3056. Date: Thu, 12 Sep 2024 12:41:14 +1000
  3057. <br />From: Aussie Broadband &lt;no&#45;reply@team.aussiebroadband.com.au&gt;
  3058. <br />Subject: nbn Unscheduled Outage
  3059. <br />
  3060. <br />NBN has let us know that your service/s may currently be affected by an outage.
  3061. <br />
  3062.  </tt>
  3063. </div>
  3064. </blockquote>
  3065.  
  3066.      <p>
  3067. That's one of these “impossible” messages.  How can I receive it if my link is down?
  3068. Checked, and of course it was still up.  But my phone (connected via my <a href="https://www.nbnco.com.au/">NBN</a> link) agreed:
  3069.      </p>
  3070.  
  3071.        <a id="Photo-4" name="Photo-4"
  3072.          href="diary-sep2024.php?dirdate=20240912&amp;imagesizes=11112&amp;topics=c#Photo-4">
  3073.          <img alt="This should be NBN-outage-2-detail.jpeg.  Is it missing?" border="0" id="Photo_4"
  3074.               title="Photo NBN-outage-2-detail.jpeg.  Click to redisplay larger version of image."
  3075.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20240912/small/NBN-outage-2-detail.jpeg"
  3076.               width="229" height="295"
  3077.           /></a>
  3078.  
  3079.      <p>
  3080. Had there been an outage?  Checked my <a href="http://www.lemis.com/grog/nbnstats.php">NBN stats page</a>.  Yes:
  3081.      </p>
  3082.  
  3083.      <blockquote class="fullwidth">
  3084. <div style="text-align:left">
  3085.  <tt>
  3086. Start time End time &nbsp;Duration &nbsp; Badness &nbsp; &nbsp; &nbsp; &nbsp;from &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;to
  3087. <br />&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (seconds)
  3088. <br />
  3089. <br />1726103107 1726103311 &nbsp; &nbsp;204 &nbsp;0.001 # 12 September 2024 11:05:07 12 September 2024 11:08:31
  3090. <br />
  3091.  </tt>
  3092. </div>
  3093. </blockquote>
  3094.  
  3095.      <p>
  3096. But that was over and done with over 1½ hours before they sent the message.
  3097.      </p>
  3098.  
  3099.      <p>
  3100. Oh, sorry about that, try again:
  3101.      </p>
  3102.  
  3103.      <blockquote class="fullwidth">
  3104. <div style="text-align:left">
  3105.  <tt>
  3106. Start time End time &nbsp;Duration &nbsp; Badness &nbsp; &nbsp; &nbsp; &nbsp;from &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;to
  3107. <br />&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (seconds)
  3108. <br />
  3109. <br />1726103107 1726103311 &nbsp; &nbsp;204 &nbsp;0.001 # 12 September 2024 11:05:07 12 September 2024 11:08:31
  3110. <br />1726109505 1726109741 &nbsp; &nbsp;236 &nbsp;0.581 # 12 September 2024 12:51:45 12 September 2024 12:55:41
  3111. <br />
  3112.  </tt>
  3113. </div>
  3114. </blockquote>
  3115.  
  3116.      <p>
  3117. That almost looks as if the second outage happened because of their message.  And at 16:12,
  3118. only 3¼ hours later, they acknowledged that it was over.
  3119.      </p>
  3120.  
  3121.      <p>
  3122. Done?  No, more work needed:
  3123.      </p>
  3124.  
  3125.      <blockquote class="fullwidth">
  3126. <div style="text-align:left">
  3127.  <tt>
  3128. NBN are doing **emergency network maintenance** between **Fri 13th September 2024 00:00 AEST** and **Fri 13th September 2024 06:00 AEST**, for **180 min**.
  3129.  </tt>
  3130. </div>
  3131. </blockquote>
  3132.  
  3133.      <p>
  3134. And yes, that's Aussie's inimitable markup, apparently my fault according to their “support”
  3135. people.  I suppose the emergency maintenance makes sense, and at least it's in the middle of
  3136. the night.
  3137.      </p>
  3138.      </div>
  3139.    ]]>
  3140.  </description>
  3141.  <dc:creator>Greg Lehey</dc:creator>
  3142.  <dc:date>2024-09-13T03:13:16+00:00</dc:date>
  3143. </item>
  3144.  
  3145.            
  3146. <!-- topic aho not selected
  3147.      <p>
  3148. In the evening <a href="http://www.lemis.com/yvonne/">Yvonne</a> feeds the animals:
  3149.      </p>
  3150.  
  3151.      
  3152.      <p>
  3153. Those are pellets for the dogs.  But today things looked different.  What's that thing
  3154. sticking out of the jug?
  3155.      </p>
  3156.  
  3157.      
  3158.      <p>
  3159. Well, in this photo, taken after the event. it's a piece of insulation.  But at the time it
  3160. was a mouse tail!  Where was the mouse?  At the other end, of course, and very much alive.
  3161. It escaped behind the fridge before any animal could catch it, so we'll have the fun of
  3162. catching it later.
  3163.      </p>
  3164.  
  3165.      <p>
  3166. Looking in the food tun, I found two more!  It seems that they had chewed a hole in the lid
  3167. of the tun, fallen in and couldn't get out again.  I'm reminded of the story of the Irishman
  3168. falling into a vat of beer.
  3169.      </p>
  3170.  
  3171.      <p>
  3172. OK, <a href="http://www.lemis.com/grog/Albums/Animals/Mona.php">Mona</a> showed a lot of interest
  3173. <a href="http://www.lemis.com/grog/diary-sep2024.php?topics=a&amp;subtitle=A%20mouse?%20%20Rats!&amp;article=D-20240907-025631#D-20240907-025631">last week</a>.  Brought her to the tun, where the mice were happily running around.  Not
  3174. interested.  <a href="http://www.lemis.com/grog/Albums/Animals/Bruno.php">Bruno</a> was marginally more
  3175. interested, but not enough.  Took the tun outside and let the dogs take a look.  Yes, they
  3176. were interested and chased each of the mice as I let them out.  And as far as I can see,
  3177. they killed them within seconds, but they didn't really know what to do then.  I only found
  3178. one, but I don't think they ate the other one.  We still have an uphill battle.
  3179.      </p>
  3180.      
  3181. End deselected topic aho (Do-it-yourself mousetrap) -->
  3182.  
  3183.                  
  3184. <item>
  3185. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2024.php#D-20240914-020930</guid>
  3186. <link>http://www.lemis.com/grog/diary-sep2024.php?topics=c#D-20240914-020930</link>
  3187. <category>technology</category>
  3188. <category>opinion</category>
  3189. <title>NBN outage?</title>
  3190.  <description>
  3191.    <![CDATA[
  3192.    <div align="justify">
  3193.      <p>
  3194. So how long did the announced overnight <a href="https://www.nbnco.com.au/">NBN</a> outage last?  It didn't.  It seems that it didn't happen, and both <a href="https://aussiebroadband.com.au/">Aussie Broadband</a> and NBN web sites deny all
  3195. knowledge of it.
  3196.      </p>
  3197.      </div>
  3198.    ]]>
  3199.  </description>
  3200.  <dc:creator>Greg Lehey</dc:creator>
  3201.  <dc:date>2024-09-14T02:09:30+00:00</dc:date>
  3202. </item>
  3203.  
  3204.            
  3205. <item>
  3206. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2024.php#D-20240914-020936</guid>
  3207. <link>http://www.lemis.com/grog/diary-sep2024.php?topics=c#D-20240914-020936</link>
  3208. <category>technology</category>
  3209. <category>opinion</category>
  3210. <title>Disk copy, day 9</title>
  3211.  <description>
  3212.    <![CDATA[
  3213.    <div align="justify">
  3214.      <p>
  3215. Into the office this morning thinking that I hadn't been overly clever by copying an archive
  3216. to <i>quartet</i>.  It had completed, after only about 24 hours, but now I had to extract
  3217. it, and that could take as long again.
  3218.      </p>
  3219.  
  3220.      <p>
  3221. But it didn't.  It was over in about 10 seconds: truncated archive.  Now it was no longer
  3222. 6.8 TB in size, only 2048 bytes!  How did that happen?
  3223.      </p>
  3224.  
  3225.      <p>
  3226. Oh.  In another <i>xterm</i> I had accidentally entered:
  3227.      </p>
  3228.  
  3229.      <blockquote class="fullwidth">
  3230. <div style="text-align:left">
  3231.  <tt>
  3232. <code><font color="blue">=== root@quartet (/dev/pts/0)</font> <font color="red">/newphotos</font> <font color="blue">274</font> &#45;&gt; <b><tt>tar cvf Photos.tar /Photosiostat 1</tt></b></code>
  3233. <br />tar: /Photosiostat: Cannot stat: No such file or directory
  3234. <br />tar: 1: Cannot stat: No such file or directory
  3235. <br />tar: Error exit delayed from previous errors.
  3236. <br />
  3237.  </tt>
  3238. </div>
  3239. </blockquote>
  3240.  
  3241.      <p>
  3242. Damn.  Start again.  Another day to go.
  3243.      </p>
  3244.      </div>
  3245.    ]]>
  3246.  </description>
  3247.  <dc:creator>Greg Lehey</dc:creator>
  3248.  <dc:date>2024-09-14T02:09:36+00:00</dc:date>
  3249. </item>
  3250.  
  3251.            
  3252. <item>
  3253. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2024.php#D-20240914-021758</guid>
  3254. <link>http://www.lemis.com/grog/diary-sep2024.php?topics=c#D-20240914-021758</link>
  3255. <category>technology</category>
  3256. <title>Ethernet issues?</title>
  3257.  <description>
  3258.    <![CDATA[
  3259.    <div align="justify">
  3260.      <p>
  3261. Seen in my daily report:
  3262.      </p>
  3263.  
  3264.      <blockquote class="fullwidth">
  3265. <div style="text-align:left">
  3266.  <tt>
  3267. Sep 13 01:32:47 eureka kernel: em0: Watchdog timeout Queue[0]&#45;&#45; resetting
  3268. <br />Sep 13 01:32:47 eureka kernel: Interface is RUNNING and ACTIVE
  3269. <br />Sep 13 01:32:47 eureka kernel: em0: TX Queue 0 &#45;&#45;&#45;&#45;&#45;&#45;
  3270. <br />Sep 13 01:32:47 eureka kernel: em0: hw tdh = 785, hw tdt = 903
  3271. <br />Sep 13 01:32:47 eureka kernel: em0: Tx Queue Status = &#45;2147483648
  3272. <br />Sep 13 01:32:47 eureka kernel: em0: TX descriptors avail = 903
  3273. <br />Sep 13 01:32:47 eureka kernel: em0: Tx Descriptors avail failure = 5
  3274. <br />Sep 13 01:32:47 eureka kernel: em0: RX Queue 0 &#45;&#45;&#45;&#45;&#45;&#45;
  3275. <br />Sep 13 01:32:47 eureka kernel: em0: hw rdh = 330, hw rdt = 329
  3276. <br />Sep 13 01:32:47 eureka kernel: em0: RX discarded packets = 0
  3277. <br />Sep 13 01:32:47 eureka kernel: em0: RX Next to Check = 330
  3278. <br />Sep 13 01:32:47 eureka kernel: em0: RX Next to Refresh = 329
  3279. <br />Sep 13 01:32:47 eureka kernel: em0: link state changed to DOWN
  3280. <br />Sep 13 01:32:51 eureka kernel: em0: link state changed to UP
  3281. <br />
  3282.  </tt>
  3283. </div>
  3284. </blockquote>
  3285.  
  3286.      <p>
  3287. What's that?  Is it serious?  It repeated later in the morning.
  3288.      </p>
  3289.      </div>
  3290.    ]]>
  3291.  </description>
  3292.  <dc:creator>Greg Lehey</dc:creator>
  3293.  <dc:date>2024-09-14T02:17:58+00:00</dc:date>
  3294. </item>
  3295.  
  3296.            
  3297. <!-- topic pHo not selected
  3298.      <p>
  3299. One of the most significant things about the evolution of cameras is the viewfinder.  You
  3300. want to be able to see what you are going to take, and ensure that it is in focus.  Over the
  3301. years, technology improved things.  I've been through this in some detail <a href="http://www.lemis.com/grog/diary-jul2021.php?subtitle=More%20camera%20history&amp;article=D-20210716-023320#D-20210716-023320">a few years ago</a>.  TL;DR:
  3302.      </p>
  3303.  
  3304.      <ul>
  3305.        <li class="fullwidth">
  3306.          <div class="listitemwidth">
  3307.            Very first cameras: simple viewfinder that matches the view of some lens.
  3308.          </div>
  3309.        </li>
  3310.  
  3311.        <li class="fullwidth">
  3312.          <div class="listitemwidth">
  3313.            1932: Camera with integrated rangefinder (<a href="https://en.wikipedia.org/wiki/Leica_II">Leica II</a>).  Requires to be adjusted to
  3314.            the film plane and lens focal length, suffers from parallax at close distances.
  3315.          </div>
  3316.        </li>
  3317.  
  3318.        <li class="fullwidth">
  3319.          <div class="listitemwidth">
  3320.            1934: Single-lens reflex camera (<a href="https://en.wikipedia.org/wiki/Kine_Exakta">Kine Exakta</a>).  No more parallax or
  3321.            focal length issues.  Still requires alignment of viewfinder screen with film plane.
  3322.          </div>
  3323.        </li>
  3324.  
  3325.        <li class="fullwidth">
  3326.          <div class="listitemwidth">
  3327.            1981: First SLR with autofocus (<a href="https://en.wikipedia.org/wiki/Pentax_ME_F">Pentax ME F</a>).  Less danger of focus problems.
  3328.          </div>
  3329.        </li>
  3330.  
  3331.        <li class="fullwidth">
  3332.          <div class="listitemwidth">
  3333.            1995: First digital SLR camera (<a href="https://en.wikipedia.org/wiki/Nikon_E_series">Nikon E</a>).  No viewfinder
  3334.            advantage.
  3335.          </div>
  3336.        </li>
  3337.  
  3338.        <li class="fullwidth">
  3339.          <div class="listitemwidth">
  3340.            2008: First interchangeable lens camera with direct sensor data viewfinder (<a href="https://en.wikipedia.org/wiki/Panasonic_Lumix_DMC-G1">Panasonic Lumix DMC-G1</a>).
  3341.            No more issues with focus alignment.
  3342.          </div>
  3343.        </li>
  3344.      </ul>
  3345.  
  3346.      <p>
  3347. All of these were progress.  What's next?  I think we're done.  More recent mirrorless
  3348. cameras allow magnifying the viewfinder image for more exact focus, but that's about it.
  3349.      </p>
  3350.  
  3351.      <p>
  3352. So what do we do now?  If you're <a href="https://en.wikipedia.org/wiki/Leica">Leica</a>, start all over again.  I've just discovered that they have a range of cameras,
  3353. most recently the <a href="https://www.dpreview.com/news/2945561017/leica-announces-the-screen-less-m11-d">M11</a>, which can be supplied without all mod cons, only the same kind of rangefinder that they
  3354. introduced 92 years ago!  And that not only at Leica's normal eye-watering prices (US
  3355. $9,395, $400 <i>more</i> than the standard model, despite it having fewer components).  To
  3356. quote the article,
  3357.      </p>
  3358.  
  3359.      <blockquote class="fullwidth">
  3360.        <div class="listitemwidth">
  3361.          The company says the lack of a display will help users focus on "the elementary aspects of
  3362.          pictorial design such as composition, aperture, shutter speed and ISO.”
  3363.        </div>
  3364.      </blockquote>
  3365.  
  3366.      <p>
  3367. I'm amazed.  Of course, they should go the whole hog and offer only a specific sensor
  3368. sensitivity (ISO).
  3369.      </p>
  3370.      
  3371. End deselected topic pHo (Leica: back to the past) -->
  3372.  
  3373.            
  3374. <!-- topic go not selected
  3375.      <p>
  3376. While walking the dogs, saw this at the Nyary's place:
  3377.      </p>
  3378.  
  3379.      
  3380.      <p>
  3381. They're removing all the vines!  Why?
  3382.      </p>
  3383.  
  3384.      <p>
  3385. Also saw this mystery flower again, the one that we planted in the south garden and then
  3386. died.  Or at least I think it's the same flower.  Here two different bushes in different
  3387. state of bloom:
  3388.      </p>
  3389.  
  3390.            
  3391.      <p>
  3392. I'll keep an eye on them over the next few days.
  3393.      </p>
  3394.      
  3395. End deselected topic go (No more wine in Dereel?) -->
  3396.  
  3397.            
  3398. <!-- topic Jh not selected
  3399.      <p>
  3400. Fiona Drayton brought us a new front gate a couple of days ago, and this evening Rod DeGroot
  3401. and mate showed up to install it.  Done!
  3402.      </p>
  3403.  
  3404.      <p>
  3405. <a href="http://www.lemis.com/yvonne/">Yvonne</a> is happy, but somehow it doesn't quite seem to fit:
  3406.      </p>
  3407.  
  3408.            
  3409.      <p>
  3410. It also closes too “closed”, in other words further than the post.  But it's minor, and Rod
  3411. put in a bar to limit the travel, so now it closes cleanly.
  3412.      </p>
  3413.  
  3414.            
  3415.      <p>
  3416. Hopefully it'll stay that way.
  3417.      </p>
  3418.      
  3419. End deselected topic Jh (A new gate) -->
  3420.  
  3421.                  
  3422. <!-- topic h not selected
  3423.      <p>
  3424. Another <a href="http://www.lemis.com/grog/powercor/power-failures.php#bottom">grid power failure</a> this morning at 4:04, which for some reason causes <i>something</i> to beep.  Damn!  How
  3425. long is it going to last?  Turned off the air conditioner and tried to get back to sleep.
  3426. Another beep a little later.
  3427.      </p>
  3428.  
  3429.      <p>
  3430. The result?  Only one outage, lasting 90 seconds.
  3431.      </p>
  3432.      
  3433. End deselected topic h (Another power failure) -->
  3434.  
  3435.            
  3436. <item>
  3437. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2024.php#D-20240915-023629</guid>
  3438. <link>http://www.lemis.com/grog/diary-sep2024.php?topics=c#D-20240915-023629</link>
  3439. <category>technology</category>
  3440. <category>general</category>
  3441. <category>opinion</category>
  3442. <title>Disk copy, day 10</title>
  3443.  <description>
  3444.    <![CDATA[
  3445.    <div align="justify">
  3446.      <p>
  3447. Into my office in the morning to find that <i>quartet</i> had rebooted as a result of the
  3448. <a href="http://www.lemis.com/grog/powercor/power-failures.php#bottom">grid power outage</a>.  Had it
  3449. finished the copy?  No.  Mounted <i>/newphotos</i> (not in <i>/etc/fstab</i>) and
  3450. discovered, to my horror:
  3451.      </p>
  3452.  
  3453.      <blockquote class="fullwidth">
  3454. <div style="text-align:left">
  3455.  <tt>
  3456. <code><font color="blue">=== root@quartet (/dev/pts/0)</font> <font color="red">/home/grog</font> <font color="blue">8</font> &#45;&gt; <b><tt>df &#45;i /newphotos</tt></b></code>
  3457. <br />Filesystem &nbsp;1048576&#45;blocks Used &nbsp; &nbsp; &nbsp;Avail Capacity iused &nbsp; &nbsp; ifree %iused &nbsp;Mounted on
  3458. <br />/dev/ada1p1 &nbsp; &nbsp; 15,257,008 &nbsp;903 15,103,534 &nbsp; &nbsp; 0% &nbsp; &nbsp; &nbsp; 3 6,486,139 &nbsp; &nbsp;0% &nbsp; /newphotos
  3459. <br />
  3460.  </tt>
  3461. </div>
  3462. </blockquote>
  3463.  
  3464.      <p>
  3465. Only 3 <a href="https://en.wikipedia.org/wiki/inode">inodes</a> and 903 MB in use.
  3466. What's that?
  3467.      </p>
  3468.  
  3469.      <blockquote class="fullwidth">
  3470. <div style="text-align:left">
  3471.  <tt>
  3472. <code><font color="blue">=== root@quartet (/dev/pts/0)</font> <font color="red">/home/grog</font> <font color="blue">10</font> &#45;&gt; <b><tt>l /newphotos|less</tt></b></code>
  3473. <br />total 1279
  3474. <br />&#45;rwxrwxrwx &nbsp; &nbsp; 1 root &nbsp; wheel &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 82 &nbsp;3 Apr &nbsp;2012 ._.TemporaryItems
  3475. <br />drwxrwx&#45;&#45;&#45; &nbsp; &nbsp; 2 root &nbsp; operator &nbsp; &nbsp; &nbsp; &nbsp; 512 14 Jan &nbsp;2016 .snap
  3476. <br />&#45;r&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45; &nbsp; &nbsp; 1 root &nbsp; wheel &nbsp; &nbsp;947,322,880 12 Sep 13:59 .sujournal
  3477. <br />&#45;rwxr&#45;&#45;r&#45;&#45; &nbsp; &nbsp; 1 root &nbsp; wheel &nbsp; &nbsp; &nbsp; &nbsp;754,482 28 Apr &nbsp;2022 #foo#
  3478. <br />drwxrwxr&#45;x &nbsp; &nbsp; 2 grog &nbsp; wheel &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;512 13 Sep 12:07 0&#45;grog
  3479. <br />drwxr&#45;xr&#45;x &nbsp; &nbsp; 2 grog &nbsp; wheel &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;1,536 13 Sep 12:04 1&#45;Skylum
  3480. <br />drwxrwxrwx &nbsp; &nbsp; 2 grog &nbsp; wheel &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;1,024 13 Sep 12:14 2&#45;grog
  3481. <br />
  3482.  </tt>
  3483. </div>
  3484. </blockquote>
  3485.  
  3486.      <p>
  3487. Well, the 903 MB are clearly the journal.  But what about those other files?  They don't
  3488. match the 3 <a href="https://en.wikipedia.org/wiki/inode">inodes</a>.  Why did the
  3489. system allow me to mount a dirty file system?  OK,
  3490.      </p>
  3491.  
  3492.      <blockquote class="fullwidth">
  3493. <div style="text-align:left">
  3494.  <tt>
  3495. <code><font color="blue">=== root@quartet (/dev/pts/0)</font> <font color="red">/home/grog</font> <font color="blue">11</font> &#45;&gt; <b><tt>fsck &#45;y /dev/ada1p1</tt></b></code>
  3496. <br />** /dev/ada1p1
  3497. <br />** SU+J Recovering /dev/ada1p1
  3498. <br />
  3499. <br />USE JOURNAL? yes
  3500. <br />
  3501. <br />** Reading 947322880 byte journal from inode 4.
  3502. <br />
  3503. <br />RECOVER? yes
  3504. <br />
  3505. <br />** Building recovery table.
  3506. <br />** Resolving unreferenced inode list.
  3507. <br />** Processing journal entries.
  3508. <br />
  3509. <br />***** FILE SYSTEM IS CLEAN *****
  3510. <br /><code><font color="blue">=== root@quartet (/dev/pts/0)</font> <font color="red">/home/grog</font> <font color="blue">12</font> &#45;&gt; <b><tt>mount /dev/ada1p1 /newphotos/</tt></b></code>
  3511. <br /><code><font color="blue">=== root@quartet (/dev/pts/0)</font> <font color="red">/home/grog</font> <font color="blue">13</font> &#45;&gt; <b><tt>df &#45;i /newphotos</tt></b></code>
  3512. <br />Filesystem &nbsp;1048576&#45;blocks &nbsp; &nbsp; &nbsp;Used &nbsp; &nbsp; Avail Capacity iused &nbsp; &nbsp; ifree %iused &nbsp;Mounted on
  3513. <br />/dev/ada1p1 &nbsp; &nbsp; 15,257,008 5,271,466 9,832,971 &nbsp; &nbsp;35% 889,919 5,596,223 &nbsp; 14% &nbsp; /newphotos
  3514.  </tt>
  3515. </div>
  3516. </blockquote>
  3517.  
  3518.      <p>
  3519. That looks better.  Continued the copy, but after a while <i>quartet</i> paniced!  I didn't
  3520. find out until it had rebooted, but <i>/var/crash/core.txt.5</i> shows:
  3521.      </p>
  3522.  
  3523.      <blockquote class="fullwidth">
  3524. <div style="text-align:left">
  3525.  <tt>
  3526. panic: ffs_blkfree_cg: freeing free block
  3527. <br />
  3528.  </tt>
  3529. </div>
  3530. </blockquote>
  3531.  
  3532.      <p>
  3533. That sounds like file system corruption.  Journalling not good enough?  Run a
  3534. full <i>fsck</i>, which found many problems.  After 45 minutes and 28.827 lines, it asked me
  3535. if I really wanted to continue.  Yes, why not.  Finally, after nearly 90 minutes and 70,769
  3536. lines of output (roughly 1,250 pages in print), I got what I didn't want to see:
  3537.      </p>
  3538.  
  3539.      <blockquote class="fullwidth">
  3540. <div style="text-align:left">
  3541.  <tt>
  3542. 884600 files, 1342191538 used, 2563602610 free (613818 frags, 320373599 blocks, 0.0% fragmentation)
  3543. <br />
  3544. <br />***** FILE SYSTEM MARKED DIRTY *****
  3545. <br />***** FILE SYSTEM WAS MODIFIED *****
  3546. <br />***** PLEASE RERUN FSCK *****
  3547. <br />
  3548.  </tt>
  3549. </div>
  3550. </blockquote>
  3551.  
  3552.      <p>
  3553. Clearly there's no recovery for this.  In particular, only 884,600 files remained.  The rest
  3554. must have been “recovered”.  And I want perfection for a backup disk.  So, start all over
  3555. again with another <i>newfs</i>.
  3556.      </p>
  3557.  
  3558.      <p>
  3559. While it was running, it occurred to me that I have seen this before.  I should have
  3560. disabled soft updates.  But by then it was too late.  Let's see what happens by tomorrow.
  3561.      </p>
  3562.      </div>
  3563.    ]]>
  3564.  </description>
  3565.  <dc:creator>Greg Lehey</dc:creator>
  3566.  <dc:date>2024-09-15T02:36:29+00:00</dc:date>
  3567. </item>
  3568.  
  3569.                  
  3570. <item>
  3571. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2024.php#D-20240916-014313</guid>
  3572. <link>http://www.lemis.com/grog/diary-sep2024.php?topics=c#D-20240916-014313</link>
  3573. <category>technology</category>
  3574. <category>opinion</category>
  3575. <title>Disk copy, day 11</title>
  3576.  <description>
  3577.    <![CDATA[
  3578.    <div align="justify">
  3579.      <p>
  3580. Into the office today to find:
  3581.      </p>
  3582.  
  3583.      <blockquote class="fullwidth">
  3584. <div style="text-align:left">
  3585.  <tt>
  3586. x ./grog/20110827/Components/dam&#45;panorama&#45;CPL&#45;6&#45;1EV.jpeg
  3587. <br />x ./grog/20110827/Components/dam&#45;panorama&#45;CPL&#45;6.jpegtar: (null)
  3588. <br />: Truncated tar archive: Unknown error: &#45;1
  3589. <br />tar: Error exit delayed from previous errors.
  3590. <br />
  3591.  </tt>
  3592. </div>
  3593. </blockquote>
  3594.  
  3595.      <p>
  3596. <i>Another</i> <a href="https://en.wikipedia.org/wiki/Network_File_System">NFS</a> issue!  OK, that's enough.  Try the rest with <a href="https://en.wikipedia.org/wiki/rsync">rsync</a>, this time with the <b>H</b> option.
  3597. And how about that, after hardly more than 5 hours:
  3598.      </p>
  3599.  
  3600.      <blockquote class="fullwidth">
  3601. <div style="text-align:left">
  3602.  <tt>
  3603. grog/www/test/
  3604. <br />grog/www/test/big/
  3605. <br />grog/www/Photos/small/white&#45;background.gif =&gt; grog/www/Photos/big/white&#45;background.gif
  3606. <br />
  3607. <br />sent 1,193,207,971,130 bytes &nbsp;received 18,071,175 bytes &nbsp;63,800,349.81 bytes/sec
  3608. <br />total size is 7,886,580,015,513 &nbsp;speedup is 6.61
  3609. <br />rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1359) [sender=3.3.0]
  3610. <br />&nbsp;&nbsp; &nbsp;18702.08 real &nbsp; &nbsp; &nbsp; 433.88 user &nbsp; &nbsp; &nbsp;1307.03 sys
  3611. <br />
  3612.  </tt>
  3613. </div>
  3614. </blockquote>
  3615.  
  3616.      <p>
  3617. What's that error?  OK, try again:
  3618.      </p>
  3619.  
  3620.      <blockquote class="fullwidth">
  3621. <div style="text-align:left">
  3622.  <tt>
  3623. <code><font color="blue">=== root@quartet (/dev/pts/1)</font> <font color="red">/Photos</font> <font color="blue">20</font> &#45;&gt; <b><tt>Log rsync &#45;Hav . /newphotos</tt></b></code>
  3624. <br />===== Sun 15 Sep 2024 15:05:02 AEST on quartet.lemis.com: rsync &#45;Hav . /newphotos
  3625. <br />sending incremental file list
  3626. <br />./
  3627. <br />.sujournal
  3628. <br />Log.log.quartet
  3629. <br />Log.log.quartet.0
  3630. <br />rsync: [receiver] rename "/newphotos/.sujournal.3wUiHl" &#45;> ".sujournal": Operation not permitted (1)
  3631. <br />Log.log.quartet.1
  3632. <br />Log.log.quartet.2
  3633. <br />Log.log.quartet.3
  3634. <br />Log.log.quartet.4
  3635. <br />Log.log.quartet.5
  3636. <br />Log.log.quartet.6
  3637. <br />
  3638. <br />sent 174,640,554 bytes &nbsp;received 88,974 bytes &nbsp;146,893.26 bytes/sec
  3639. <br />total size is 7,886,623,224,434 &nbsp;speedup is 45,136.18
  3640. <br />rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1359) [sender=3.3.0]
  3641. <br />&nbsp;&nbsp; &nbsp; 1188.83 real &nbsp; &nbsp; &nbsp; &nbsp; 4.47 user &nbsp; &nbsp; &nbsp; &nbsp;28.22 sys
  3642. <br />
  3643. <br /><code><font color="blue">=== root@quartet (/dev/pts/0)</font> <font color="red">/newphotos/grog</font> <font color="blue">65</font> &#45;&gt; <b><tt>date; df &#45;i /Photos/ /newphotos/</tt></b></code>
  3644. <br />Sun 15 Sep 2024 15:28:12 AEST
  3645. <br />Filesystem &nbsp; &nbsp; 1048576&#45;blocks &nbsp; &nbsp; &nbsp;Used &nbsp; &nbsp; Avail Capacity &nbsp; iused &nbsp; &nbsp; ifree %iused &nbsp;Mounted on
  3646. <br />eureka:/Photos &nbsp; &nbsp; &nbsp;7,629,565 6,841,077 &nbsp; 712,191 &nbsp; &nbsp;91% 1,764,773 1,478,873 &nbsp; 54% &nbsp; /Photos
  3647. <br />/dev/ada1p1 &nbsp; &nbsp; &nbsp; &nbsp;15,257,008 6,845,610 8,258,827 &nbsp; &nbsp;45% 1,764,814 4,721,328 &nbsp; 27% &nbsp; /newphotos
  3648. <br />
  3649.  </tt>
  3650. </div>
  3651. </blockquote>
  3652.  
  3653.      <p>
  3654. That looks better.  And yes, the error was the attempt to copy <i>.sujournal</i>, the soft
  3655. updates journal file.  But we still have more space in <i>/newphotos</i> than
  3656. in <i>/Photos</i>.  Not surprising, given that I didn't delete files that weren't
  3657. on <i>/Photos</i>.  OK, a third time:
  3658.      </p>
  3659.  
  3660.      <blockquote class="fullwidth">
  3661. <div style="text-align:left">
  3662.  <tt>
  3663. <code><font color="blue">=== root@quartet (/dev/pts/1)</font> <font color="red">/Photos</font> <font color="blue">21</font> &#45;&gt; <b><tt>Log rsync &#45;Hav &nbsp;&#45;&#45;exclude=.sujournal &#45;&#45;delete&#45;after . /newphotos</tt></b></code>
  3664. <br />===== Sun 15 Sep 2024 15:28:46 AEST on quartet.lemis.com: rsync &#45;Hav &#45;&#45;exclude=.sujournal &#45;&#45;delete&#45;after . /newphotos
  3665. <br />building file list ... done
  3666. <br />Log.log.quartet
  3667. <br />deleting 0&#45;grog/Wildflower&#45;2.jpeg
  3668. <br />deleting 0&#45;grog/Wildflower&#45;1.jpeg
  3669. <br />...
  3670. <br />deleting 6&#45;HDR/PhotomatixResults01/e&#45;from&#45;house&#45;0+0EV_+1EV_&#45;1EV.tif
  3671. <br />deleting grog/20240914/multishot~
  3672. <br />deleting grog/20240914/magic&#45;pto&#45;now
  3673. <br />
  3674. <br />sent 36,804,908 bytes &nbsp;received 34 bytes &nbsp;52,540.96 bytes/sec
  3675. <br />total size is 7,886,589,671,198 &nbsp;speedup is 214,280.73
  3676. <br /><code><font color="blue">=== root@quartet (/dev/pts/0)</font> <font color="red">/var/tmp</font> <font color="blue">79</font> &#45;&gt; <b><tt>date; df &#45;i /Photos/ /newphotos/</tt></b></code>
  3677. <br />Sun 15 Sep 2024 15:41:19 AEST
  3678. <br />Filesystem &nbsp; &nbsp; 1048576&#45;blocks &nbsp; &nbsp; &nbsp;Used &nbsp; &nbsp; Avail Capacity &nbsp; iused &nbsp; &nbsp; ifree %iused &nbsp;Mounted on
  3679. <br />eureka:/Photos &nbsp; &nbsp; &nbsp;7,629,565 6,841,077 &nbsp; 712,191 &nbsp; &nbsp;91% 1,764,773 1,478,873 &nbsp; 54% &nbsp; /Photos
  3680. <br />/dev/ada1p1 &nbsp; &nbsp; &nbsp; &nbsp;15,257,008 6,841,899 8,262,538 &nbsp; &nbsp;45% 1,764,815 4,721,327 &nbsp; 27% &nbsp; /newphotos
  3681. <br />
  3682.  </tt>
  3683. </div>
  3684. </blockquote>
  3685.  
  3686.      <p>
  3687. That looks better.  But for some reason the <tt>iused</tt> field hasn't changed.  I suspect
  3688. that there's an issue with soft updates there.  Still, <i>finally</i> I have a valid copy
  3689. and an incantation to perform the sync.  Only 11 days!
  3690.      </p>
  3691.      </div>
  3692.    ]]>
  3693.  </description>
  3694.  <dc:creator>Greg Lehey</dc:creator>
  3695.  <dc:date>2024-09-16T01:43:13+00:00</dc:date>
  3696. </item>
  3697.  
  3698.            
  3699. <!-- topic ko not selected
  3700.      <p>
  3701. Discovered this in a kitchen cabinet today:
  3702.      </p>
  3703.  
  3704.      
  3705.      <p>
  3706. Where did it come from?  I didn't buy it, and <a href="http://www.lemis.com/yvonne/">Yvonne</a> denies
  3707. all knowledge.  What it is is clearer: a splatter guard for a frying pan.  But what's that
  3708. plastic foil?  It's the remains of the packaging, thoughtfully applied before the handle was
  3709. attached.  To remove it, you need a screwdriver to remove the handle:
  3710.      </p>
  3711.  
  3712.      
  3713.      <p>
  3714. And then I saw this:
  3715.      </p>
  3716.  
  3717.      
  3718.      <p>
  3719. If there's one thing that needs a machine wash, it's this kind of device that catches fat in
  3720. the fabric.  What do the instructions on the package say?  “Wash before use”.  Nothing else
  3721. at all.  I'm amazed.  My guess is that the advice is misplaced.  I'll put it in the
  3722. dishwasher, and if it falls apart, I'll throw it out
  3723.      </p>
  3724.      
  3725. End deselected topic ko (Quality kitchen utensils) -->
  3726.  
  3727.            
  3728. <!-- topic Pho not selected
  3729.      <p>
  3730. <a href="https://en.wikipedia.org/wiki/Ayşenur_Ezgi_Eygi">Ayşenur Eygi</a> was
  3731. buried today.  The world is outraged: an innocent civilian was <a href="https://www.washingtonpost.com/world/2024/09/11/american-activist-aysenur-eygi-killed-idf-west-bank/">shot dead by Israeli snipers</a>.
  3732.      </p>
  3733.  
  3734.      <p>
  3735. And so the world should be.  But she was only one person.  What about the 1,139 people,
  3736. mainly Israelis, killed on <a href="https://en.wikipedia.org/wiki/Israel%E2%80%93Hamas_war">3 October 2023</a>?  That's
  3737. several orders of magnitude worse, and the world rightly condemns <a href="https://en.wikipedia.org/wiki/Hamas">Hamas</a> for perpetrating it.  But it almost
  3738. seems that the death of Ayşenur Eygi was worse, a US citizen killed by Israeli snipers.
  3739. Well, half: she was also Turkish.
  3740.      </p>
  3741.  
  3742.      <p>
  3743. But then there are the <a href="https://www.aljazeera.com/news/longform/2023/10/9/israel-hamas-war-in-maps-and-charts-live-tracker">currently 41,821 Palestinians</a> that the Israelis have killed since 7 October 2023.
  3744. The number is rising daily.  If the newspapers reported on each of them to the extent that
  3745. they have reported on Ayşenur Eygi, it would take them centuries to complete.
  3746.      </p>
  3747.  
  3748.      <p>
  3749. Why this discrepancy?  One death is enough.  1,140 are a tragedy.  But 42,000!  How
  3750. can <i>any</i> country support such carnage, let alone one claiming to abide by human
  3751. rights?  And that's before you look at the destruction that was once <a href="https://en.wikipedia.org/wiki/Gaza_Strip">Gaza</a>.  <a href="https://www.aljazeera.com/news/longform/2023/10/9/israel-hamas-war-in-maps-and-charts-live-tracker">This page</a> summarizes the horrors perpetrated by Israel.  Currently it states that in
  3752. Gaza <i>every hour</i> 42 bombs are dropped, 12 buildings are destroyed, 15 people (6 of
  3753. them children) are killed and another 35 people are injured.
  3754.      </p>
  3755.  
  3756.      <p>
  3757. How can a supposedly law-abiding government commit such atrocities?  How can the USA support
  3758. it?  By comparison, the Russian aggression in <a href="https://en.wikipedia.org/wiki/Ukraine">Ukraine</a> is almost civilized.  The US
  3759. government is losing international credibility with the support of this carnage.  If the
  3760. death of Ayşenur Eygi can draw people to look at the atrocities, she won't have died in
  3761. vain.
  3762.      </p>
  3763.      
  3764. End deselected topic Pho (½ US American? 1139 Israelis? 41,821 Palestinians?) -->
  3765.  
  3766.                  
  3767. <item>
  3768. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2024.php#D-20240917-023903</guid>
  3769. <link>http://www.lemis.com/grog/diary-sep2024.php?topics=c#D-20240917-023903</link>
  3770. <category>technology</category>
  3771. <category>opinion</category>
  3772. <title>Back to the old slog</title>
  3773.  <description>
  3774.    <![CDATA[
  3775.    <div align="justify">
  3776.      <p>
  3777. So after only 11 days I have finally copied my disk.  Time to shut down <i>quartet</i> and
  3778. revert to the other system configuration issues I have.
  3779.      </p>
  3780.  
  3781.      <p>
  3782. One relatively minor issue is that the function of the <b>Prev</b> and <b>Next</b> keys
  3783. (marked <b>PageUp</b> and <b>PageDown</b>) on <i>xterm</i> has changed: it should, as the
  3784. inscriptions suggest, page up and down, but now it pages through the shell history.
  3785.      </p>
  3786.  
  3787.      <p>
  3788. Why?  It must have something to do with the <a href="https://www.x.org/">X</a> resources.  I've been playing with them recently, adding additional key bindings.  Initially
  3789. they were:
  3790.      </p>
  3791.  
  3792.      <blockquote class="fullwidth">
  3793. <div style="text-align:left">
  3794.  <tt>
  3795. *VT100.Translations: #override \
  3796. <br />&nbsp;&nbsp; &lt;Key&gt;Next: scroll&#45;forw(1,page) \n\
  3797. <br />&nbsp;&nbsp; &lt;Key&gt;Prior: scroll&#45;back(1,page)
  3798.  </tt>
  3799. </div>
  3800. </blockquote>
  3801.  
  3802.      <p>
  3803. But in the course of my configuration attempts, I changed them to:
  3804.      </p>
  3805.  
  3806.      <blockquote class="fullwidth">
  3807. <div style="text-align:left">
  3808.  <tt>
  3809. xterm*VT100.Translations: #override \
  3810. <br />&nbsp;&nbsp; &lt;Key&gt;Next: scroll&#45;forw(1,page) \n\
  3811. <br />&nbsp;&nbsp; &lt;Key&gt;Prior: scroll&#45;back(1,page) \n\
  3812. <br />&nbsp;&nbsp; Shift &lt;Key&gt;Insert: &nbsp; &nbsp;insert&#45;selection(SELECT) \n\
  3813. <br />&nbsp;&nbsp; Ctrl Shift &lt;Key&gt;V: &nbsp; &nbsp;insert&#45;selection(SELECT) \n\
  3814. <br />&nbsp;&nbsp; Ctrl Shift &lt;Key&gt;C: &nbsp; &nbsp;copy&#45;selection(SELECT)
  3815. <br />
  3816.  </tt>
  3817. </div>
  3818. </blockquote>
  3819.  
  3820.      <p>
  3821. That looks straightforward enough to me.  Adding <tt>xterm</tt> to the resource shouldn't
  3822. make any difference.  Tried reverting.  No difference.
  3823.      </p>
  3824.  
  3825.      <p>
  3826. OK, <a href="https://en.wikipedia.org/wiki/RTFM">RTFM</a> time.  And <i>once
  3827. again</i> I couldn't find anything that helps.  What does <tt>#override</tt> mean?  I
  3828. haven't found any reference to it, though <i>xrdb</i> has an <tt>-override</tt> option:
  3829.      </p>
  3830.  
  3831.      <blockquote class="fullwidth">
  3832. <div style="text-align:left">
  3833.  <tt>
  3834. <b> &#45;override</b>
  3835. <br />&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; This option indicates that the input should be added to,
  3836. <br />&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; instead of replacing, the current contents of the specified
  3837. <br />&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; properties. &nbsp;New entries override previous entries.
  3838. <br />
  3839.  </tt>
  3840. </div>
  3841. </blockquote>
  3842.  
  3843.      <p>
  3844. But that doesn't seem to work here.  Much searching, no results.
  3845.      </p>
  3846.      </div>
  3847.    ]]>
  3848.  </description>
  3849.  <dc:creator>Greg Lehey</dc:creator>
  3850.  <dc:date>2024-09-17T02:39:03+00:00</dc:date>
  3851. </item>
  3852.  
  3853.            
  3854. <!-- topic ah not selected
  3855.      <p>
  3856. It's been quite cool in the few weeks since the beginning of spring, a minimum temperature
  3857. of 1.8°.  And the <a href="https://en.wikipedia.org/wiki/Bureau_of_Meteorology">Bureau
  3858. of Meteorology</a> has been warning of dead lambs.
  3859.      </p>
  3860.  
  3861.      <p>
  3862. And indeed, that seems to be the case:
  3863.      </p>
  3864.  
  3865.      
  3866.      <p>
  3867. Those white spots in the foreground are dead lambs.  There were more a couple of days ago,
  3868. so it seems that they're dying daily.  I wouldn't have expected that, especially since the
  3869. weather wasn't <i>that</i> cold.
  3870.      </p>
  3871.      
  3872. End deselected topic ah (Oh the springtime it brings on the deadlambs) -->
  3873.  
  3874.            
  3875. <item>
  3876. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2024.php#D-20240917-023958</guid>
  3877. <link>http://www.lemis.com/grog/diary-sep2024.php?topics=c#D-20240917-023958</link>
  3878. <category>general</category>
  3879. <category>technology</category>
  3880. <category>opinion</category>
  3881. <title>Banking: the pain</title>
  3882.  <description>
  3883.    <![CDATA[
  3884.    <div align="justify">
  3885.      <p>
  3886. Last Wednesday <a href="http://www.lemis.com/yvonne/">Yvonne</a> had problems with the <a href="https://en.wikipedia.org/wiki/Bank_of_Melbourne_(2011)">Bank of Melbourne</a>: her
  3887. debit card expired in February, and she had to go to the branch in <a href="https://en.wikipedia.org/wiki/Ballarat">Ballarat</a> to get money.  It took her nearly
  3888. an hour, and the person who dealt with it—clearly an immigrant—spoke English so badly that
  3889. she could barely understand him.  And this at the “we speak your language” Bank of
  3890. Melbourne!
  3891.      </p>
  3892.  
  3893.      <p>
  3894. So why did she not get a new card?  After over 30 frustrating minutes on the phone, we
  3895. established:
  3896.      </p>
  3897.  
  3898.      <ul>
  3899.        <li class="fullwidth">
  3900.          <div class="listitemwidth">
  3901.            Yvonne never received a replacement card.
  3902.          </div>
  3903.        </li>
  3904.  
  3905.        <li class="fullwidth">
  3906.          <div class="listitemwidth">
  3907.            The Bank cancelled Yvonne's card (but not mine) because it hadn't been activated.  They
  3908.            didn't inform us of this action.
  3909.          </div>
  3910.        </li>
  3911.  
  3912.        <li class="fullwidth">
  3913.          <div class="listitemwidth">
  3914.            To reinstate the card, they needed information from Yvonne like the number and nature of
  3915.            the accounts that we have with the bank.  No outside help allowed, so I (standing next
  3916.            to her) couldn't help.  But she didn't even know what accounts we had!
  3917.          </div>
  3918.        </li>
  3919.  
  3920.        <li class="fullwidth">
  3921.          <div class="listitemwidth">
  3922.            They wanted her to identify herself with things like bank passwords.  Again, no help
  3923.            from me allowed.  Since she never used online banking, she couldn't know.
  3924.          </div>
  3925.        </li>
  3926.  
  3927.        <li class="fullwidth">
  3928.          <div class="listitemwidth">
  3929.            Finally she “identified” herself with date of birth, driver license number and address,
  3930.            along with the last transaction (at the branch in Ballarat).  With the exception of the
  3931.            last, which even I didn't know, there's nothing difficult to find here.  Any
  3932.            well-prepared criminal could have found them.
  3933.          </div>
  3934.        </li>
  3935.  
  3936.        <li class="fullwidth">
  3937.          <div class="listitemwidth">
  3938.            They can't send us the card.  It has to be picked up at the branch!  At least it seems
  3939.            that there could be a possibility of making an appointment to avoid the long waits.
  3940.          </div>
  3941.        </li>
  3942.      </ul>
  3943.  
  3944.      <p>
  3945. Why is this all so complicated?  Yes, establishing identity is good.  But at the very least
  3946. Yvonne didn't receive her replacement card, and they cancelled it without warning.  There's
  3947. no excuse for that.  By contrast, my <a href="http://www.lemis.com/grog/diary-dec2022.php?subtitle=ANZ%20card:%20done?&amp;article=D-20221221-001234#D-20221221-001234">last similar interaction</a> with <a href="https://en.wikipedia.org/wiki/ANZ_(bank)">ANZ</a> went more smoothly, though I had my issues there too.
  3948.      </p>
  3949.  
  3950.      <p>
  3951. Change bank?  Yes, it sounds like a good idea, but only if I can be sure that the new one is
  3952. better.  After my experience with <a href="https://en.wikipedia.org/wiki/Bankwest">Bankwest</a> <a href="http://www.lemis.com/grog/diary-oct2021.php?subtitle=Reporting%20Centrelink%20security%20breach&amp;article=D-20211013-015651#D-20211013-015651">3 years ago</a>, I'm particularly wary.
  3953.      </p>
  3954.      </div>
  3955.    ]]>
  3956.  </description>
  3957.  <dc:creator>Greg Lehey</dc:creator>
  3958.  <dc:date>2024-09-17T02:39:58+00:00</dc:date>
  3959. </item>
  3960.  
  3961.                  
  3962. <!-- topic ko not selected
  3963.      <p>
  3964. I have a surprising number of different kinds of <a href="http://www.lemis.com/grog/recipes/noodle-cooking-times.php">noodles</a>, mainly of Chinese origin.  Time to get
  3965. rid of some of the older ones.  Today I had <a href="http://www.lemis.com/grog/recipes/mi-udang-tean.php"><i>mi
  3966. udang</i></a> for breakfast, requiring noodles like these:
  3967.      </p>
  3968.  
  3969.            
  3970.      <p>
  3971. What's the difference?  Very little in taste.  They're intended as single servings: boil in
  3972. water for about 2 minutes and they're done.  But the first (<a href="http://www.lemis.com/grog/recipes/noodle-cooking-times.php#Sau-Tao">Sau Tao</a>) only weigh 45 g per portion,
  3973. giving about 100 g of cooked noodles—not enough.  They're also more difficult to separate
  3974. than the other one (<a href="http://www.lemis.com/grog/recipes/noodle-cooking-times.php#Chefs-world">“Chef's
  3975. world”</a>), which give a better 150 g of finished noodle.
  3976.      </p>
  3977.  
  3978.      <p>
  3979. So: I had 5 baskets of Sau Tao, in this case only 207 g.  Cook them for 472 g of finished
  3980. noodles.  That's three portions and the last of the Sau Tao.
  3981.      </p>
  3982.      
  3983. End deselected topic ko (Sau Tao: too much trouble) -->
  3984.  
  3985.            
  3986. <item>
  3987. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2024.php#D-20240918-013547</guid>
  3988. <link>http://www.lemis.com/grog/diary-sep2024.php?topics=c#D-20240918-013547</link>
  3989. <category>technology</category>
  3990. <category>opinion</category>
  3991. <title>X breakthrough</title>
  3992.  <description>
  3993.    <![CDATA[
  3994.    <div align="justify">
  3995.      <p>
  3996. Why don't my changes to <i>.Xdefaults</i> make any difference?  On a whim, started a
  3997. new <i>xterm</i>.  It works!  So the whole issue was that <i>xterm</i> doesn't pay any
  3998. attention to the <i>.Xdefaults</i> after it has been started.  That makes sense, but it took
  3999. me a while to get to it.
  4000.      </p>
  4001.      </div>
  4002.    ]]>
  4003.  </description>
  4004.  <dc:creator>Greg Lehey</dc:creator>
  4005.  <dc:date>2024-09-18T01:35:47+00:00</dc:date>
  4006. </item>
  4007.  
  4008.            
  4009. <!-- topic g not selected
  4010.      <p>
  4011. Paul Donaghy along today to mow the lawn, the first time this season.  For once nothing
  4012. seems to have gone wrong, though he thinks that the drive belt for the lawn mower is
  4013. slipping.
  4014.      </p>
  4015.      
  4016. End deselected topic g (First lawn mowing of spring) -->
  4017.  
  4018.            
  4019. <item>
  4020. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2024.php#D-20240918-014453</guid>
  4021. <link>http://www.lemis.com/grog/diary-sep2024.php?topics=c#D-20240918-014453</link>
  4022. <category>technology</category>
  4023. <category>opinion</category>
  4024. <title>Back to the makefs bug</title>
  4025.  <description>
  4026.    <![CDATA[
  4027.    <div align="justify">
  4028.      <p>
  4029. It's been <a href="http://www.lemis.com/grog/diary-sep2023.php?subtitle=Debugging%20again&amp;article=D-20230921-023558#D-20230921-023558">nearly a year</a> since I started investigating a <a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273725">bug</a> in <i>makefs(8)</i>,
  4030. or at least in the <a href="https://www.freebsd.org/">FreeBSD</a> version.  It comes
  4031. from <a href="https://en.wikipedia.org/wiki/NetBSD">NetBSD</a>, where it works.
  4032.      </p>
  4033.  
  4034.      <p>
  4035. High time to get back to it.  But it seems that <i>kimchi</i>, my NetBSD box, no longer has
  4036. a debug version of <i>makefs</i>, and to build it I need to build a kernel.  And for some
  4037. reason, the build fails.
  4038.      </p>
  4039.  
  4040.      <p>
  4041. Dammit, any old (well, newer) version of NetBSD will do.  But first I have to download
  4042. things.  And that took the rest of the day.
  4043.      </p>
  4044.      </div>
  4045.    ]]>
  4046.  </description>
  4047.  <dc:creator>Greg Lehey</dc:creator>
  4048.  <dc:date>2024-09-18T01:44:53+00:00</dc:date>
  4049. </item>
  4050.  
  4051.            
  4052. <!-- topic g not selected
  4053.      <p>
  4054. Our <a href="https://en.wikipedia.org/wiki/Curry_tree">Curry tree</a>, now 14 years
  4055. old, was not happy about a lapse in watering a few weeks back, combined with the annual
  4056. attack of mites:
  4057.      </p>
  4058.  
  4059.      
  4060.      <p>
  4061. But new growth is coming, and it seems that it might even flower:
  4062.      </p>
  4063.  
  4064.            
  4065.      <p>
  4066. It has only done that <a href="http://www.lemis.com/grog/diary-jan2024.php?subtitle=Some%20garden%20improvement&amp;article=D-20240113-005030#D-20240113-005030">once before</a>, and I had attributed that to the lack of mites:
  4067.      </p>
  4068.  
  4069.      
  4070.      <p>
  4071. But that was only 8 months ago, and maybe it is just mature enough.
  4072.      </p>
  4073.      
  4074. End deselected topic g (Curry tree flowering?) -->
  4075.  
  4076.            
  4077. <!-- topic po not selected
  4078.      <p>
  4079. Taking photos of the <a href="https://en.wikipedia.org/wiki/Curry_tree">curry tree</a> wasn't easy.  Clearly I needed flash, so I chose the mecablitz 15 MS-1, which also needs
  4080.        a trigger flash.  This was on the <a href="https://en.wikipedia.org/wiki/Olympus_OM-D_E-M1_Mark_II">Olympus OM-D E-M1 Mark II</a>, so the obvious choice was the toy FL-LM3 flash that came with the camera.  But I
  4081.        couldn't get it to fire!  It seems that it has died after being used about once a year since
  4082.        I bought it 7 years ago!
  4083.      </p>
  4084.  
  4085.      <p>
  4086. Not surprisingly, the photos were ridiculously underexposed:
  4087.      </p>
  4088.  
  4089.      
  4090.      <p>
  4091. More surprisingly, my photo processing software almost recovered it.  This is the same photo
  4092. after processing:
  4093.      </p>
  4094.  
  4095.      
  4096.      <p>
  4097. But even after replacing it with the <a href="http://www.lemis.com/grog/photography/Mecablitz-58-AF-1.php">mecablitz 58 AF-2</a>,
  4098. the results were ridiculously underexposed.  Once again, as I have been doing for 60 years,
  4099. I wonder what use on-camera flash is.
  4100.      </p>
  4101.  
  4102.      <p>
  4103. So what do I do now?  More and more I appreciate the studio flash units that I have spread
  4104. around the house.  In this case, though, I think focus stacking with natural light will do
  4105. the trick.  Mañana.
  4106.      </p>
  4107.      
  4108. End deselected topic po (Bloody flash!) -->
  4109.  
  4110.                  
  4111. <item>
  4112. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2024.php#D-20240919-025101</guid>
  4113. <link>http://www.lemis.com/grog/diary-sep2024.php?topics=c#D-20240919-025101</link>
  4114. <category>technology</category>
  4115. <title>Exploit?</title>
  4116.  <description>
  4117.    <![CDATA[
  4118.    <div align="justify">
  4119.      <p>
  4120. Into the office this morning to see lots of messages streaming off the log screen.  The
  4121. first that hit me were these:
  4122.      </p>
  4123.  
  4124.      <blockquote class="fullwidth">
  4125. <div style="text-align:left">
  4126.  <tt>
  4127. Sep 18 08:27:20 eureka Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from tiwi: postfix/smtpd[39164]: connect from localhost[127.0.0.1]
  4128. <br />Sep 18 08:27:20 eureka Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from tiwi: postfix/smtpd[39164]: NOQUEUE: reject: MAIL from localhost[127.0.0.1]: 452 4.3.4 Message size exceeds fixed limit; from=&lt;&gt; proto=ESMTP helo=&lt;tiwi.lemis.com&gt;
  4129. <br />Sep 18 07:45:54 eureka Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: postfix/local[11450]: C04D126359D: to=&lt;grog@lemis.com&gt;, relay=local, delay=0.2, delays=0.19/0/0/0.01, dsn=2.0.0, status=sent (delivered to command: &nbsp;exec /usr/local/bin/procmail &#45;t 2&gt;&gt;/home/grog/Mail/procmailerr || exit 75)
  4130. <br />Sep 18 09:05:40 eureka Forwarded from 192.109.197.137: postfix/cleanup[25410]: EB30626359D: message&#45;id=&lt;172661433578.1482.3761641752870526039@worldpartners24.com&gt;
  4131. <br />Sep 18 09:05:40 eureka Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: postfix/smtpd[25400]: disconnect from www.lemis.com[45.32.70.18] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5
  4132. <br />Sep 18 08:55:25 eureka Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: postfix/local[18921]: 9124426359D: to=&lt;grog@lemis.com&gt;, relay=local, delay=1.4, delays=1.4/0/0/0.01, dsn=2.0.0, status=sent (delivered to command: &nbsp;exec /usr/local/bin/procmail &#45;t 2&gt;&gt;/home/grog/Mail/procmailerr || exit 75)
  4133. <br />
  4134.  </tt>
  4135. </div>
  4136. </blockquote>
  4137.  
  4138.      <p>
  4139. “Message size exceeds fixed limit”.  From <i>tiwi</i>?  What's going on there.  Shut
  4140. down <i>eureka</i>'s mail system while I'm investigating.
  4141.      </p>
  4142.  
  4143.      <p>
  4144. But then there were other messages:
  4145.      </p>
  4146.  
  4147.      <blockquote class="fullwidth">
  4148. <div style="text-align:left">
  4149.  <tt>
  4150. Sep 18 09:19:11 192.109.197.137 Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: kernel: Limiting icmp unreach response from 203 to 200 packets/sec
  4151. <br />Sep 18 09:15:06 192.109.197.137 Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: kernel: Limiting icmp unreach response from 215 to 200 packets/sec
  4152. <br />...
  4153. <br />Sep 18 09:12:46 192.109.197.137 Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.137: Forwarded from 192.109.197.1
  4154. <br />
  4155.  </tt>
  4156. </div>
  4157. </blockquote>
  4158.  
  4159.      <p>
  4160. What's this nonsense?  <i>named</i> was locked at 100% CPU, so I stopped that too.  And
  4161. still they kept coming, so I stopped <i>syslogd</i>.  Gradually I was able to investigate
  4162. things, which included messages like:
  4163.      </p>
  4164.  
  4165.      <blockquote class="fullwidth">
  4166. <div style="text-align:left">
  4167.  <tt>
  4168. Sep 18 06:56:32 eureka Forwarded from homephone: HT802 [c0:74:ad:37:66:d8] [1.0.21.4]CallRecord::writeCDRFile, No space! current file size =51158bytes, need extra 91 bytes.
  4169. <br />Sep 18 07:54:58 eureka Forwarded from homephone: HT802 [c0:74:ad:37:66:d8] [1.0.21.4]CallRecord::writeCDRFile, No space! current file size =51158bytes, need extra 92 bytes.
  4170. <br />Sep 18 07:40:08 eureka Forwarded from homephone: HT802 [c0:74:ad:37:66:d8] [1.0.21.4]CallRecord::writeCDRFile, No space! current file size =51158bytes, need extra 91 byte
  4171.  </tt>
  4172. </div>
  4173. </blockquote>
  4174.  
  4175.      <p>
  4176. They're from the <a href="http://www.grandstream.com/products/gateways-and-atas/analog-telephone-adaptors/product/ht802">Grandstream HT802</a> <a href="https://en.wikipedia.org/wiki/VoIP">VoIP</a> <a href="https://en.wikipedia.org/wiki/Analogue_telephone_adapter">ATA</a>.  And I
  4177. had turned off all logging!  Where do they come from?  Why are they out of chronological
  4178. order?  About the only thing that isn't a surprise is the content of the message: that's
  4179. indicative of the terminally buggy firmware of the HT802, as I have <a href="http://www.lemis.com/grog/diary-aug2023.php?subtitle=HT802%20noise&amp;article=D-20230825-024731#D-20230825-024731">already discovered</a>.
  4180.      </p>
  4181.  
  4182.      <p>
  4183. So what is it?  The other messages don't make much sense either.  Just these “Forwarded
  4184. from” prefixes.  <i>syslog</i> loop?  No, it was only ever the same IP
  4185. address, <tt>192.109.197.137</tt>, which is <i>eureka</i>.  I gradually restarted
  4186. everything, and things worked normally.  No idea when it started: the flood of messages had
  4187. overwritten all the older copies of <i>/var/log/messages</i> and <i>/var/log/maillog.</i>
  4188.      </p>
  4189.  
  4190.      <p>
  4191. I'm baffled.  I should investigate the <tt>Forwarded&nbsp;from</tt> prefix.  <i>syslogd</i>
  4192. sources?
  4193.      </p>
  4194.      </div>
  4195.    ]]>
  4196.  </description>
  4197.  <dc:creator>Greg Lehey</dc:creator>
  4198.  <dc:date>2024-09-19T02:51:01+00:00</dc:date>
  4199. </item>
  4200.  
  4201.            
  4202. <!-- topic Po not selected
  4203.      <p>
  4204. <a href="https://www.reuters.com/world/middle-east/dozens-hezbollah-members-wounded-lebanon-when-pagers-exploded-sources-witnesses-2024-09-17/">News of the day</a>: a large number of <a href="https://en.wikipedia.org/wiki/Pager">pagers</a> used by <a href="https://en.wikipedia.org/wiki/Hezbollah">Hezbollah</a>, a <a href="https://en.wikipedia.org/wiki/Lebanon">Lebanese</a> political party,
  4205. exploded at 15:30 local time, killing round 10 people and injuring thousands.
  4206.      </p>
  4207.  
  4208.      <p>
  4209. How did that happen?  People are still trying to put the pieces together, not only of the
  4210. hundreds who lost hands or eyes.  But it seems accepted (not a good word) that <a href="https://en.wikipedia.org/wiki/Israel">Israel</a> is behind it.
  4211.      </p>
  4212.  
  4213.      <p>
  4214. That's terrorism!  From the <a href="https://en.wikipedia.org/wiki/Terrorism">Wikipedia page</a>:
  4215.      </p>
  4216.  
  4217.      <blockquote class="fullwidth">
  4218.        <div class="listitemwidth">
  4219.          The term is used in this regard primarily to refer to intentional violence during
  4220.          peacetime or in the context of war against non-combatants (mostly civilians and neutral
  4221.          military personnel).  Different definitions of terrorism emphasize its randomness, its aim
  4222.          to instill fear, and its broader impact beyond its immediate victims.
  4223.        </div>
  4224.      </blockquote>
  4225.  
  4226.      <p>
  4227. I've been disgusted by Israel's actions for at least a year now.  Somehow there's no room
  4228. left for an increase in disgust.  But when will people do something about the US-backed
  4229. Israeli terrorists?
  4230.      </p>
  4231.      
  4232. End deselected topic Po (US-backed Israeli terrorism?) -->
  4233.  
  4234.            
  4235. <item>
  4236. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2024.php#D-20240919-032427</guid>
  4237. <link>http://www.lemis.com/grog/diary-sep2024.php?topics=c#D-20240919-032427</link>
  4238. <category>technology</category>
  4239. <category>opinion</category>
  4240. <title>More NetBSD pain</title>
  4241.  <description>
  4242.    <![CDATA[
  4243.    <div align="justify">
  4244.      <p>
  4245. My <a href="https://en.wikipedia.org/wiki/NetBSD">NetBSD</a> sources are in place,
  4246. so I followed the <a href="https://www.netbsd.org/docs/guide/en/chap-fetch.html">build
  4247. instructions</a>.  Oh.  For some reason, they're for cross-builds.  And the
  4248. old <tt>make&nbsp;build</tt> seems no longer to be the way to go.  OK, move on to the next
  4249. chapter, <a href="https://www.netbsd.org/docs/guide/en/chap-kernel.html">compiling the
  4250. kernel</a>.  And it failed!  A typical situation is:
  4251.      </p>
  4252.  
  4253.      <blockquote class="fullwidth">
  4254. <div style="text-align:left">
  4255.  <tt>
  4256. kimchi# <b>config GENERIC</b>
  4257. <br />Build directory is ../compile/GENERIC
  4258. <br />Don't forget to run "make depend"
  4259. <br />kimchi# <b>make depend</b>
  4260. <br />make: don't know how to make depend. Stop
  4261. <br />
  4262.  </tt>
  4263. </div>
  4264. </blockquote>
  4265.  
  4266.      <p>
  4267. Clearly it wants that done in a different directory, but which?  <i>/usr/src</i>?
  4268.      </p>
  4269.  
  4270.      <blockquote class="fullwidth">
  4271. <div style="text-align:left">
  4272.  <tt>
  4273. kimchi# <b>make depend</b>
  4274. <br /><i>... much output</i>
  4275. <br /># &nbsp; &nbsp;create &nbsp;lib/pcap&#45;common.d
  4276. <br />CC=/tooldir.NetBSD&#45;10.0&#45;amd64/bin/x86_64&#45;&#45;netbsd&#45;gcc /tooldir.NetBSD&#45;10.0&#45;amd64/bin/nbmkdep &#45;f pcap&#45;common.d.tmp &nbsp;&#45;&#45; &nbsp; &#45;std=gnu99 &#45;Wall &#45;Wstrict&#45;prototypes &#45;Wmissing&#45;prototypes &#45;Wpointer&#45;arith &#45;Wno&#45;sign&#45;compare &#45;Wsystem&#45;headers &#45;Wno&#45;traditional &#45;Wa,&#45;&#45;fatal&#45;warnings &#45;Wreturn&#45;type &#45;Wswitch &#45;Wshadow &#45;Wcast&#45;qual &#45;Wwrite&#45;strings &#45;Wextra &#45;Wno&#45;unused&#45;parameter &#45;Wno&#45;sign&#45;compare &#45;Wsign&#45;compare &#45;Wformat=2 &#45;Wno&#45;format&#45;zero&#45;length &#45;Werror &nbsp;&#45;DLBL_ALIGN &#45;&#45;sysroot=/ &#45;DPCAP_DONT_INCLUDE_PCAP_BPF_H &#45;DHAVE_CONFIG_H &#45;DENABLE_REMOTE &#45;DPCAP_SUPPORT_RPCAP &#45;I/usr/src/external/bsd/libpcap/lib &#45;I/usr/src/external/bsd/libpcap/lib/../include &#45;I/usr/src/external/bsd/libpcap/lib &#45;I/usr/src/external/bsd/libpcap/lib/../dist &#45;DYYBISON &#45;DHAVE_CONFIG_H &#45;DINET6 &nbsp; &nbsp; /usr/src/external/bsd/libpcap/lib/../dist/pcap&#45;common.c &amp;&amp; &nbsp;mv &#45;f pcap&#45;common.d.tmp pcap&#45;common.d
  4277. <br />/usr/src/external/bsd/libpcap/lib/../dist/pcap&#45;common.c:1131:2: error: #error The LINKTYPE_ matching range does not match the DLT_ matching range
  4278. <br />&nbsp;1131 | #error The LINKTYPE_ matching range does not match the DLT_ matching range
  4279. <br />&nbsp;&nbsp; &nbsp; &nbsp;| &nbsp;^~~~~
  4280. <br />nbmkdep: compile failed.
  4281. <br />*** Error code 1
  4282. <br />
  4283.  </tt>
  4284. </div>
  4285. </blockquote>
  4286.  
  4287.      <p>
  4288. Never mind, I didn't want to build a kernel.  How about the next chapter, <a href="https://www.netbsd.org/docs/guide/en/chap-updating.html">Updating an existing system
  4289. from sources</a>?
  4290.      </p>
  4291.  
  4292.      <blockquote class="fullwidth">
  4293. <div style="text-align:left">
  4294.  <tt>
  4295. kimchi# <b>./build.sh &#45;O ../obj &#45;T ../tools &#45;U distribution</b>
  4296. <br /><i>...much output</i>
  4297. <br /># &nbsp; install &nbsp;/usr/src/../tools/include/compat/nbtool_config.h
  4298. <br />/usr/src/../obj/tools/binstall/xinstall &#45;c &nbsp;&#45;r nbtool_config.h /usr/src/../tools/include/compat/nbtool_config.h
  4299. <br />cd: can't cd to include
  4300. <br />
  4301. <br />*** Failed target: &nbsp;includes
  4302. <br />*** Failed command: (cd include &amp;&amp; find . &#45;name '*.h' &#45;print | while read f ; do /usr/src/../obj/tools/binstall/xinstall &#45;c &#45;r $f /usr/src/../tools/include/compat/$f ; done)
  4303. <br />*** Error code 2
  4304. <br />
  4305.  </tt>
  4306. </div>
  4307. </blockquote>
  4308.  
  4309.      <p>
  4310. This is ridiculous.  I've never had problems building NetBSD before.  Yes, I can try to
  4311. debug the thing, but this is a standard install following the instructions.  What has gone
  4312. wrong?
  4313.      </p>
  4314.  
  4315.      <p>
  4316. I have another image, probably the one I used last year.  If that's the case, I already have
  4317. a debug version of <i>makefs</i>, so I don't need to do anything.
  4318.      </p>
  4319.      </div>
  4320.    ]]>
  4321.  </description>
  4322.  <dc:creator>Greg Lehey</dc:creator>
  4323.  <dc:date>2024-09-19T03:24:27+00:00</dc:date>
  4324. </item>
  4325.  
  4326.                  
  4327. <item>
  4328. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2024.php#D-20240920-021318</guid>
  4329. <link>http://www.lemis.com/grog/diary-sep2024.php?topics=c#D-20240920-021318</link>
  4330. <category>technology</category>
  4331. <category>history</category>
  4332. <category>opinion</category>
  4333. <title>IBM 3330 space requirements</title>
  4334.  <description>
  4335.    <![CDATA[
  4336.    <div align="justify">
  4337.      <p>
  4338. For years I've been comparing the capacity and size of my disk drives with those of the
  4339. <a href="https://en.wikipedia.org/wiki/IBM_3330">IBM 3330</a>, <i>the</i> big disk
  4340. drive of the 1970s.  Here an image from the <a href="https://www.cs.auckland.ac.nz/historydisplays/FifthFloor/MagneticDataStorage/MagneticDisks.php">University of Auckland</a>:
  4341.      </p>
  4342.  
  4343.      <a href="https://www.cs.auckland.ac.nz/historydisplays/FifthFloor/MagneticDataStorage/DataStorageImages/DiskPacks/IBM3330.jpg">
  4344.      <img alt=""
  4345.          title=".  Click to see in original size."
  4346.          src="https://www.cs.auckland.ac.nz/historydisplays/FifthFloor/MagneticDataStorage/DataStorageImages/DiskPacks/IBM3330.jpg"
  4347.          width="400"
  4348.          /></a>
  4349.      <p>
  4350. It had 8 or 9 drives, though I've only ever seen 8, as in that photo.  Each drive initially
  4351. held 100 MB, but by the time I came on the scene they had doubled that to 200 MB, so an 8
  4352. drive configuration held 1.6 GB, coincidentally 0.01% of the capacity of my newest drive.
  4353.      </p>
  4354.  
  4355.      <p>
  4356. My most recent disk drive has a capacity of 16&nbsp;TB, roughly 10,000 times the size of the
  4357. 3330.  But how much physical space does it take up?  My current drive is a pretty standard
  4358. 5¼&quot; drive.  And the 3330?  <a href="https://gemini.google.com/app/12f6ded0cb11427e">Google Gemini</a> fails badly and
  4359. gives the information:
  4360.      </p>
  4361.  
  4362.      <table summary="Automatically generated table">
  4363.       <tr>
  4364.          <td valign="top" align="left">Model</td>
  4365.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  4366.          <td valign="top" align="center">Width</td>
  4367.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  4368.          <td valign="top" align="center">Depth</td>
  4369.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  4370.          <td valign="top" align="center">Height</td>
  4371.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  4372.          <td valign="top" align="center">Floor space</td>
  4373.       </tr>
  4374.  
  4375.       <tr>
  4376.          <td valign="top" align="left">3330-1</td>
  4377.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  4378.          <td valign="top" align="center">48 inches (122 cm)</td>
  4379.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  4380.          <td valign="top" align="center">36 inches (91 cm)</td>
  4381.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  4382.          <td valign="top" align="center">72 inches (183 cm)</td>
  4383.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  4384.          <td valign="top" align="center">16.5 square feet (1.53 square meters)</td>
  4385.       </tr>
  4386.  
  4387.       <tr>
  4388.          <td valign="top" align="left"></td>
  4389.       </tr>
  4390.    </table>
  4391.  
  4392.      <p>
  4393. It also includes identical information for the 3330-2, 3330-3 and 3330-4.
  4394.      </p>
  4395.  
  4396.      <p>
  4397. So what are those measurements?  The disk packs were 14&quot; in diameter.  Can each bay
  4398. really be 48&quot; wide?  That seems like a lot, more than 3 times the diameter of the pack.
  4399. But the pack covers on top of the unit are about 15&quot; in diameter, so it seems
  4400. plausible.  Certainly the height appears correct.
  4401.      </p>
  4402.  
  4403.      <p>
  4404. So: let's guess.  Each bay is 1.22 m wide, with the exception of the controller at the
  4405. right.  There seem to have been many controllers with different widths, but for the sake of
  4406. convenience I'll assume the same width as a disk bay.  That makes a total of 6.1 m and an
  4407. area of 7.65 m².  But that's just the footprint.  To change packs, you need to open a drive
  4408. drawer.  Assuming that there are several rows, how much space does each unit need?  I'd
  4409. guess an absolute minimum of 60 cm, making for a total footprint of 6.1 × 1.82 m or 11.1 m²,
  4410. or about 144 MB/m².  It's been a long time since data took up that much area.
  4411.      </p>
  4412.  
  4413.      <p>
  4414. So at that density, you'd need 16,000 ÷ 0.144 or 11.11 ha of area.  That's considerably more
  4415. than <a href="http://www.lemis.com/grog/diary-sep2024.php?topics=c&amp;subtitle=Installing%20the%20new%20disk&amp;article=D-20240906-024555#D-20240906-024555">my last estimate</a>, but still smaller than the size of the <a href="https://en.wikipedia.org/wiki/Vatican_City">Vatican City</a>.  For that you'd need the
  4416. equivalent of nearly 5 16&nbsp;TB disks.
  4417.      </p>
  4418.  
  4419.      <p>
  4420. And transfer speed?  Hard to say.  I haven't measured the speed of my new disk, but let's
  4421. assume round 400 MB/s.  The 3330 arrays would have a total of 80,000 disk packs, all capable
  4422.  
  4423. that would be a transfer rate of round 40 GB/s, more than anything currently available.
  4424.      </p>
  4425.      </div>
  4426.    ]]>
  4427.  </description>
  4428.  <dc:creator>Greg Lehey</dc:creator>
  4429.  <dc:date>2024-09-20T02:13:18+00:00</dc:date>
  4430. </item>
  4431.  
  4432.                  
  4433. <item>
  4434. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2024.php#D-20240921-021403</guid>
  4435. <link>http://www.lemis.com/grog/diary-sep2024.php?topics=c#D-20240921-021403</link>
  4436. <category>technology</category>
  4437. <category>multimedia</category>
  4438. <category>opinion</category>
  4439. <title>Secure confirmation</title>
  4440.  <description>
  4441.    <![CDATA[
  4442.    <div align="justify">
  4443.      <p>
  4444. For some reason I wasn't signed up for the <a href="https://en.wikipedia.org/wiki/ARD_(broadcaster)">ARD</a> mailing list.  OK, fight my
  4445. way through the broken web site and sign up.
  4446.      </p>
  4447.  
  4448.      <p>
  4449. Obligatory confirmation message:
  4450.      </p>
  4451.  
  4452.      <blockquote class="fullwidth">
  4453. <div style="text-align:left">
  4454.  <tt>
  4455. Date: Fri, 20 Sep 2024 03:03:58 +0200
  4456. <br />From: ARD Mediathek Newsletter &lt;newsletter@ard.de&gt;
  4457. <br />Subject: Bitte bestätigen Sie Ihre Anmeldung
  4458. <br />
  4459. <br />Bitte klicken Sie auf den folgenden Link, um Ihre Anmeldung zu bestätigen:
  4460. <br />
  4461. <br />&nbsp;https://seu2.cleverreach.com/f/136025&#45;139443/wss/1220015&#45;cb7511128984
  4462. <br />
  4463.  </tt>
  4464. </div>
  4465. </blockquote>
  4466.  
  4467.      <p>
  4468. “Please click on this link to confirm your registration”.  <a href="https://www.cleverreach.com">https://www.cleverreach.com</a>?  What's that?
  4469.      </p>
  4470.  
  4471.      <p>
  4472. Yes, on some reflection there's little that can go wrong.  But it requires reflection, and
  4473. it encourages sloppiness.  <i>Bad</i> ARD.
  4474.      </p>
  4475.      </div>
  4476.    ]]>
  4477.  </description>
  4478.  <dc:creator>Greg Lehey</dc:creator>
  4479.  <dc:date>2024-09-21T02:14:03+00:00</dc:date>
  4480. </item>
  4481.  
  4482.            
  4483. <item>
  4484. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2024.php#D-20240921-021724</guid>
  4485. <link>http://www.lemis.com/grog/diary-sep2024.php?topics=c#D-20240921-021724</link>
  4486. <category>technology</category>
  4487. <category>opinion</category>
  4488. <title>More makefs debugging?</title>
  4489.  <description>
  4490.    <![CDATA[
  4491.    <div align="justify">
  4492.      <p>
  4493. So why can't I build a <a href="https://en.wikipedia.org/wiki/NetBSD">NetBSD</a> system any more?  Do I really need to?  No, I still have the disk image that I was using
  4494. <a href="http://www.lemis.com/grog/diary-sep2023.php?subtitle=More%20makefs%20insights&amp;article=D-20230923-011158#D-20230923-011158">last time</a>.  OK, replace the “disk” in <i>kimchi</i> with that image and reboot.
  4495.      </p>
  4496.  
  4497.      <p>
  4498. No networking!  I've seen that <a href="http://www.lemis.com/grog/diary-sep2023.php?subtitle=More%20VirtualBox%20fun&amp;article=D-20230923-011058#D-20230923-011058">before</a> too, though I've never been able to work out why.  Create a new VM using that
  4499. disk, and all is well.
  4500.      </p>
  4501.  
  4502.      <p>
  4503. Except that I don't have a debug version of <i>makefs</i> there, only some output:
  4504. <a href="http://www.lemis.com/grog/diary-sep2023.php?subtitle=Looking%20at%20makefs&amp;article=D-20230922-023940#D-20230922-023940">as I discovered later</a>, <i>makefs</i> contains debug options.  OK, time for a new
  4505. <a href="https://www.freebsd.org/">FreeBSD</a> machine.  Install 14.1 and upgrade
  4506. to <tt>-CURRENT</tt>.  And that almost worked: it seems that the <i>/usr/obj</i> has blown
  4507. out to 18 GB!  So it filled up the virtual disk, and I had to put it via <a href="https://en.wikipedia.org/wiki/Symbolic_link">symlink</a> on <i>/hydra</i>.  But then
  4508. things ran without trouble, only not fast enough for me to do anything more today.
  4509.      </p>
  4510.      </div>
  4511.    ]]>
  4512.  </description>
  4513.  <dc:creator>Greg Lehey</dc:creator>
  4514.  <dc:date>2024-09-21T02:17:24+00:00</dc:date>
  4515. </item>
  4516.  
  4517.                  
  4518. <item>
  4519. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2024.php#D-20240922-014640</guid>
  4520. <link>http://www.lemis.com/grog/diary-sep2024.php?topics=c#D-20240922-014640</link>
  4521. <category>general</category>
  4522. <category>technology</category>
  4523. <category>opinion</category>
  4524. <title>Spring rains arrive</title>
  4525.  <description>
  4526.    <![CDATA[
  4527.    <div align="justify">
  4528.      <p>
  4529. Heavy rain overnight, causing me to decide to turn off the heating in case we had a power
  4530. failure.  That didn't happen, but we got round 22 mm of rain, or, as the <a href="https://en.wikipedia.org/wiki/Bureau_of_Meteorology">Bureau of Meteorology</a> put it,
  4531. 2.2 mm:
  4532.      </p>
  4533.  
  4534.        <a id="Photo-5" name="Photo-5"
  4535.          href="diary-sep2024.php?dirdate=20240921&amp;imagesizes=111112&amp;topics=c#Photo-5">
  4536.          <img alt="This should be Weather-report-2.jpeg.  Is it missing?" border="0" id="Photo_5"
  4537.               title="Photo Weather-report-2.jpeg.  Click to redisplay larger version of image."
  4538.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20240921/small/Weather-report-2.jpeg"
  4539.               width="174" height="387"
  4540.           /></a>
  4541.  
  4542.      <p>
  4543. It's easy to understand inaccuracies in weather forecasts, especially for areas far from
  4544. weather stations.  But this app shows quite accurate rainfall maps, so it's hard to
  4545. understand why they should be so completely inaccurate in recording rainfall.
  4546.      </p>
  4547.      </div>
  4548.    ]]>
  4549.  </description>
  4550.  <dc:creator>Greg Lehey</dc:creator>
  4551.  <dc:date>2024-09-22T01:46:40+00:00</dc:date>
  4552. </item>
  4553.  
  4554.            
  4555. <!-- topic go not selected
  4556.      <p>
  4557. Jesse Walsh along today to do some weeding.  Somehow it's not working.  After an hour he had
  4558. removed about 95% of the weeds from an area of about 8 m².  In two weeks it will look the
  4559. same as it did yesterday.
  4560.      </p>
  4561.  
  4562.      <p>
  4563. How do professional gardeners address the issue?
  4564.      </p>
  4565.      
  4566. End deselected topic go (More weeding) -->
  4567.  
  4568.            
  4569. <item>
  4570. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2024.php#D-20240922-020349</guid>
  4571. <link>http://www.lemis.com/grog/diary-sep2024.php?topics=c#D-20240922-020349</link>
  4572. <category>technology</category>
  4573. <category>general</category>
  4574. <category>opinion</category>
  4575. <title>Measure your IQ</title>
  4576.  <description>
  4577.    <![CDATA[
  4578.    <div align="justify">
  4579.      <p>
  4580. Today I saw an advertisement from a company called <a href="https://www.cerebrumiq.com/">Cerebrum</a> offering to tell me my type of intelligence:
  4581.        spatial, musical, mumble.  Over the years I've noticed that different people address
  4582.        problems in different manners, and I've decided for myself that I'm very much spatial.  But
  4583.        I've had very intelligent people at work who couldn't find their way round the building.
  4584.        Clearly not a spatially defined intelligence.
  4585.      </p>
  4586.  
  4587.      <p>
  4588. So this test looked interesting.  Disappointing: it was all a matter of pattern matching,
  4589. and some of the questions were quite difficult.  Finally I finished.  Show me the results?
  4590. No, they wanted to send them to me.  OK, another throwaway email address.  And after a while
  4591. they sent me a message telling me all about IQ, something that I didn't want to know.  No
  4592. mention of kind of intelligence.
  4593.      </p>
  4594.  
  4595.      <p>
  4596. OK, click on <b>Get my IQ Score Now!</b>.  Error 404!
  4597.      </p>
  4598.  
  4599.      <p>
  4600. OK, contact.  They have a bot.  OK, tell it: “Your web link is 404”.
  4601.      </p>
  4602.  
  4603.      <p>
  4604. Hang.  After 20 minutes, I asked “Are you still there”.  Yes, “Hi, I'm the Cerebrum bot.
  4605. What do you need help with?”.  OK, maybe an easier-to-parse response: “You have sent me an
  4606. email with a broken link”.  Yes, this time I got an answer: “Hi, I'm the Cerebrum bot.  What
  4607. do you need help with?”.
  4608.      </p>
  4609.  
  4610.      <p>
  4611. Things continued like that, with alternate hangs, repeats and nonsense.  In the end I gave
  4612. up, but first I noticed the information at the bottom of the page:
  4613.      </p>
  4614.  
  4615.      <blockquote class="fullwidth">
  4616. <div style="text-align:left">
  4617.  <tt>
  4618. © Cerebrium IQ &#45; 2024. All rights reserved
  4619. <br />30 N Gould St Ste R Sheridan, WY 82801 USA
  4620. <br />
  4621.  </tt>
  4622. </div>
  4623. </blockquote>
  4624.  
  4625.      <p>
  4626. They can't even spell their own name!  Somehow they seem completely unintelligent.
  4627.      </p>
  4628.      </div>
  4629.    ]]>
  4630.  </description>
  4631.  <dc:creator>Greg Lehey</dc:creator>
  4632.  <dc:date>2024-09-22T02:03:49+00:00</dc:date>
  4633. </item>
  4634.  
  4635.            
  4636. <item>
  4637. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2024.php#D-20240922-025435</guid>
  4638. <link>http://www.lemis.com/grog/diary-sep2024.php?topics=c#D-20240922-025435</link>
  4639. <category>technology</category>
  4640. <category>opinion</category>
  4641. <title>More on software maintenance</title>
  4642.  <description>
  4643.    <![CDATA[
  4644.    <div align="justify">
  4645.      <p>
  4646. <a href="http://www.lemis.com/grog/diary-feb2024.php?subtitle=Making%20software%20maintenance%20easy&amp;article=D-20240209-013125#D-20240209-013125">Earlier this year</a> I discovered a bug in the man page for <i>make(1)</i>.  <i>make</i>
  4647.      first looks for a file <i>BSDmakefile</i>, but it's not mentioned anywhere in the man page.
  4648.      In fact, it's not mentioned anywhere in the sources.  Where does it come from?  After some
  4649.      discussion on IRC, discovered that <i>make</i> reads a file <i>/usr/share/mk/sys.mk</i>, and
  4650.      that contains:
  4651.      </p>
  4652.  
  4653.      <blockquote class="fullwidth">
  4654. <div style="text-align:left">
  4655.  <tt>
  4656. # Tell bmake the makefile preference
  4657. <br />.MAKE.MAKEFILE_PREFERENCE= BSDmakefile makefile Makefile
  4658. <br />
  4659.  </tt>
  4660. </div>
  4661. </blockquote>
  4662.  
  4663.      <p>
  4664. OK, that's specific to <a href="https://www.freebsd.org/">FreeBSD</a>.  <a href="https://en.wikipedia.org/wiki/NetBSD">NetBSD</a> doesn't know a <i>BSDmakefile</i>.
  4665. How do we handle it?  Started a mail discussion with Simon J. Gerraty, who considered the
  4666. possibility of adding operating system dependent text.  But I wonder if it wouldn't make
  4667. more sense to remove <i>BSDmakefile</i> altogether.
  4668.      </p>
  4669.      </div>
  4670.    ]]>
  4671.  </description>
  4672.  <dc:creator>Greg Lehey</dc:creator>
  4673.  <dc:date>2024-09-22T02:54:35+00:00</dc:date>
  4674. </item>
  4675.  
  4676.            
  4677. <!-- topic ko not selected
  4678.      <p>
  4679. <a href="http://www.lemis.com/grog/recipes/roast-beef.php">Roast beef</a> for dinner today.  That's nothing
  4680. new, but somehow the details evade me.  Cook at 180° fan-forced to 53°, taking about 42
  4681. minutes per kilogram.  That's the easy part.  But this roast had a layer of fat on top.
  4682. That calls for heat from above, also suggesting that the beef should be higher in the oven:
  4683.      </p>
  4684.  
  4685.      
  4686.      <p>
  4687. Started like that.  After 20 minutes, the inside temperature was still showing the initial
  4688. 18°.  Something wrong with the (wireless) thermometer?
  4689.      </p>
  4690.  
  4691.      <p>
  4692. OK, try a second thermometer, inserted not quite as deeply as the first.  And sure enough,
  4693. it rose more quickly.  After the expected 42 minutes the temperature was 53°, just what I
  4694. had expected.  But the first thermometer was only showing round 40°.  After 20 minutes' rest
  4695. they were closer, round 50° and 60°.
  4696.      </p>
  4697.  
  4698.      <p>
  4699. That's understandable, but it brings back to me how difficult it is to specify a meat
  4700. temperature.  I don't know how to address the problem.
  4701.      </p>
  4702.  
  4703.      <p>
  4704. And then <a href="http://www.lemis.com/grog/recipes/yorkshire-pudding.php">Yorkshire pudding</a>.  Not a
  4705. success: it takes much longer to cook than I expected, and after 20 minutes at 210° it was
  4706. still undercooked.  More investigation required.
  4707.      </p>
  4708.      
  4709. End deselected topic ko (Roast beef again) -->
  4710.  
  4711.                  
  4712. <!-- topic hko not selected
  4713.      <p>
  4714. Vanessa Milamber along for breakfast today.  She's travelling Australia (and the world) and
  4715. is currently staying with Chris Bahlo.
  4716.      </p>
  4717.      
  4718. End deselected topic hko (Breakfast with Vanessa) -->
  4719.  
  4720.            
  4721. <!-- topic go not selected
  4722.      <p>
  4723. It's the <a href="https://en.wikipedia.org/wiki/September_equinox">September
  4724. equinox</a>, time for the monthly <a href="http://www.lemis.com/grog/Albums/garden/Flowers-20240922.php">garden flower photos</a>.
  4725.      </p>
  4726.  
  4727.      <p>
  4728. It has been one of the mildest winters since I started keeping records:
  4729.      </p>
  4730.  
  4731.      <blockquote class="fullwidth">
  4732. <div style="text-align:left">
  4733.  <tt>
  4734. mysql> <b>select year(date),
  4735. <br />&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;min(outside_temp),
  4736. <br />&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;avg(outside_temp),
  4737. <br />&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;max(outside_temp)
  4738. <br />&nbsp;&nbsp; &nbsp; &nbsp; from observations
  4739. <br />&nbsp;&nbsp; &nbsp; &nbsp; where month(date) &gt; 5
  4740. <br />&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;and month(date) &lt; 9
  4741. <br />&nbsp;&nbsp; &nbsp; &nbsp; group by year(date);</b>
  4742. <br />+&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;+&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;+&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;+&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;+
  4743. <br />| year(date) | min(outside_temp) | avg(outside_temp) | max(outside_temp) |
  4744. <br />+&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;+&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;+&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;+&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;+
  4745. <br />| &nbsp; &nbsp; &nbsp; 2017 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&#45;2.2 | 8.560618937140722 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;19.7 |
  4746. <br />| &nbsp; &nbsp; &nbsp; 2018 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&#45;3 | 8.791814473911545 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;19.7 |
  4747. <br />| &nbsp; &nbsp; &nbsp; 2019 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&#45;0.9 | 9.059936482458161 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;20.4 |
  4748. <br />| &nbsp; &nbsp; &nbsp; 2020 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&#45;0.8 | 8.716560253881685 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;20.7 |
  4749. <br />| &nbsp; &nbsp; &nbsp; 2021 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&#45;0.6 | 9.301671782613512 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;23 |
  4750. <br />| &nbsp; &nbsp; &nbsp; 2022 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&#45;2.6 | 9.085142510706916 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;20.4 |
  4751. <br />| &nbsp; &nbsp; &nbsp; 2023 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&#45;1.4 | 9.892861121292666 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;23.6 |
  4752. <br />| &nbsp; &nbsp; &nbsp; 2024 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&#45;2.8 | 9.608775174628834 | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;24.4 |
  4753. <br />+&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;+&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;+&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;+&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45;+
  4754. <br />
  4755.  </tt>
  4756. </div>
  4757. </blockquote>
  4758.  
  4759.      <p>
  4760. But somehow the garden looks less developed than in previous years.  There's almost nothing
  4761. worth highlighting.  About the only thing of interest is this <a href="https://en.wikipedia.org/wiki/Abutilon">Abutilon</a> outside my bedroom window, which
  4762. has had its ups and downs:
  4763.      </p>
  4764.  
  4765.      
  4766.      <p>
  4767. The parent tree of our blue-flowering wildflower is flowering nicely:
  4768.      </p>
  4769.  
  4770.            
  4771.      <p>
  4772. But the best we can say about the one that we transplanted is that it's not dead yet:
  4773.      </p>
  4774.  
  4775.      
  4776.      <p>
  4777. It looked much worse a few months back, so there's still (a little) hope.
  4778.      </p>
  4779.  
  4780.      <p>
  4781. The rest aren't dead yet, but they're taking their time coming.  Here they are:
  4782.      </p>
  4783.      
  4784. End deselected topic go (Garden flowers in early spring) -->
  4785.  
  4786.            
  4787. <!-- topic ko not selected
  4788.      <p>
  4789. Grilled chicken legs for dinner tonight, something that we haven't done very much recently.
  4790. In particular, I didn't have much for the “hair dryer” <a href="http://www.lemis.com/grog/recipes/air-fryer.php">“air fryer”</a>.  Tried them for 30 minutes at 200°, but they were ready after 25
  4791. minutes:
  4792.      </p>
  4793.  
  4794.      
  4795.      <p>
  4796. That was a relatively painless experiment.
  4797.      </p>
  4798.      
  4799. End deselected topic ko (“Air fried” chicken legs) -->
  4800.  
  4801.                  
  4802. <item>
  4803. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2024.php#D-20240924-014113</guid>
  4804. <link>http://www.lemis.com/grog/diary-sep2024.php?topics=c#D-20240924-014113</link>
  4805. <category>technology</category>
  4806. <category>opinion</category>
  4807. <title>DVD disaster</title>
  4808.  <description>
  4809.    <![CDATA[
  4810.    <div align="justify">
  4811.      <p>
  4812. When I finalized the specifications for <i>hydra</i> <a href="http://www.lemis.com/grog/diary-sep2023.php?topics=c&amp;subtitle=New%20computer&amp;article=D-20230922-014301#D-20230922-014301">almost exactly a year ago</a>, one of the requirements was a <a href="https://en.wikipedia.org/wiki/DVD">DVD</a> drive.  That seemed like a no-brainer, but
  4813. it later occurred to me that DVDs and <a href="https://en.wikipedia.org/wiki/Compact_disk">CDs</a> are gradually becoming a thing of
  4814. the past, and that for the few occasions that I might need one, I could use a <a href="https://en.wikipedia.org/wiki/USB">USB</a> drive.  As it was, the choice of an inbuilt
  4815. drive limited my choice of case.
  4816.      </p>
  4817.  
  4818.      <p>
  4819. Today I had some data CDs that I had been asked to copy.  OK, put them in the drive.  It's
  4820. behind a door.  How do you open the thing?  While trying to do so, saw a red light go on on
  4821. top of the cabinet.  The machine shut down!
  4822.      </p>
  4823.  
  4824.      <p>
  4825. This <i>stupid</i> idea of putting the controls on the top of the case!
  4826.      </p>
  4827.  
  4828.        <a id="Photo-6" name="Photo-6"
  4829.          href="diary-sep2024.php?dirdate=20231018&amp;imagesizes=1111112&amp;topics=c#Photo-6">
  4830.          <img alt="This should be hydra-18.jpeg.  Is it missing?" border="0" id="Photo_6"
  4831.               title="Photo hydra-18.jpeg.  Click to redisplay larger version of image."
  4832.               src="https://lemis.nyc3.digitaloceanspaces.com/grog/Photos/20231018/small/hydra-18.jpeg"
  4833.               width="369" height="183"
  4834.           /></a>
  4835.  
  4836.      <p>
  4837. The one on the left is the power button, and it's only that far from the front of the case
  4838. (extreme left).  I must have pressed it while trying to open the door, which (I discovered)
  4839. opens in the opposite direction.  Why do people do this?  It must be (relatively) modern,
  4840. since Bruce Evans' <i>zetaplex</i> also has it.  I need to put a plastic guard on top of it.
  4841.      </p>
  4842.  
  4843.      <p>
  4844. The machine came up relatively smoothly, as was to be expected with a clean shutdown.  But:
  4845.      </p>
  4846.  
  4847.      <blockquote class="fullwidth">
  4848. <div style="text-align:left">
  4849.  <tt>
  4850. mount: /dev/da0p1: R/W mount on /Video denied. &nbsp;Filessystem is not clean &#45; run fsck.: Operation not permitted
  4851.  </tt>
  4852. </div>
  4853. </blockquote>
  4854.  
  4855.      <p>
  4856. Huh?  What went wrong there?  OK, mark it <tt>noauto</tt> in <i>/etc/fstab</i> and continue.
  4857. Run <i>fsck</i>, which went for hours.  Didn't I have journalling enabled?  When <i>fsck</i>
  4858. finished, confirmed: no, it wasn't enabled.  OK, enable, then <i>umount</i> and remount 3
  4859. different file systems on <i>teevee</i>.  But:
  4860.      </p>
  4861.  
  4862.      <blockquote class="fullwidth">
  4863. <div style="text-align:left">
  4864.  <tt>
  4865. <code><font color="blue">=== root@teevee (/dev/pts/12)</font> <font color="red">/home/grog</font> <font color="blue">10</font> &#45;&gt; <b><tt>mount /spool/Videos</tt></b></code>
  4866. <br />[tcp] hydra:/Video/spool/Videos: No such file or directory
  4867. <br />
  4868.  </tt>
  4869. </div>
  4870. </blockquote>
  4871.  
  4872.      <p>
  4873. <i>/spool/Videos</i> is mounted on <i>hydra:/Video/spool/Videos</i>.  <i>/Video</i> is
  4874. already mounted.  What's the problem?
  4875.      </p>
  4876.  
  4877.      <blockquote class="fullwidth">
  4878. <div style="text-align:left">
  4879.  <tt>
  4880. <code><font color="blue">=== root@teevee (/dev/pts/12)</font> <font color="red">/home/grog</font> <font color="blue">11</font> &#45;&gt; <b><tt>ls &#45;l /Video</tt></b></code>
  4881. <br />total 2019944
  4882. <br />drwxrwxr&#45;x &nbsp; 2 root operator &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 512 15 May 13:35 .snap
  4883. <br />&#45;r&#45;&#45;&#45;&#45;&#45;&#45;&#45;&#45; &nbsp; 1 root wheel &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;655,589,376 23 Sep 13:59 .sujournal
  4884. <br />drwxr&#45;xr&#45;x &nbsp;11 root wheel &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;512 15 May 13:54 home
  4885. <br />&#45;rw&#45;r&#45;&#45;r&#45;&#45; &nbsp; 1 root wheel &nbsp; &nbsp;2,116,891,893,624 16 May 04:28 homeimage.gz
  4886. <br />
  4887.  </tt>
  4888. </div>
  4889. </blockquote>
  4890.  
  4891.      <p>
  4892. <b><i>OH</i></b>.  What's that?  Where have all my videos gone?  I don't have a backup for
  4893. this file system.
  4894.      </p>
  4895.  
  4896.      <p>
  4897. Took a moment to recover.  Did <i>fsck</i> find an old version of the disk?  Potentially
  4898. that could happen in very small areas, but we're talking about 2 TB of data here.  The old
  4899. random detection of USB drives after boot?  But I only have one drive!
  4900.      </p>
  4901.  
  4902.      <p>
  4903. More searching.  Oh, how about that, there <i>is</i> more than one drive.  But it's not
  4904. connected.
  4905.      </p>
  4906.  
  4907.      <p>
  4908. Still more searching.  Oh, how about that, the drive <i>is</i> is connected, not just where
  4909. I thought.  And sure enough, not only was the drive undamaged, it was also clean.  Panic
  4910. over.  And in the process discovered that the other disk has the same size as <i>/Video</i>,
  4911. so I can use it as a backup disk.
  4912.      </p>
  4913.      </div>
  4914.    ]]>
  4915.  </description>
  4916.  <dc:creator>Greg Lehey</dc:creator>
  4917.  <dc:date>2024-09-24T01:41:13+00:00</dc:date>
  4918. </item>
  4919.  
  4920.            
  4921. <!-- topic ho not selected
  4922.      <p>
  4923. <a href="http://www.lemis.com/grog/diary-sep2024.php?subtitle=Banking:%20the%20pain&amp;article=D-20240917-023958#D-20240917-023958">Last week</a> we had one of many annoyances with the <a href="https://en.wikipedia.org/wiki/Bank_of_Melbourne">Bank of Melbourne</a>.  I didn't note
  4924. it at the time, but I asked them to take a complaint, for which they didn't give a reference
  4925. number.
  4926.      </p>
  4927.  
  4928.      <p>
  4929. Today we received mail from the Bank of Melbourne.  The promised new debit card?
  4930. Information on how to pick it up?  No, no mention of a new card, which had been promised by
  4931. today.
  4932.      </p>
  4933.  
  4934.      <p>
  4935. It addressed the complaint.  At least I now know the reference number, CS95140069.  But I
  4936. don't know what use it is:
  4937.      </p>
  4938.  
  4939.      <blockquote class="fullwidth">
  4940.        <div class="listitemwidth">
  4941.          Thank you for your time sharing your complaint.  We are please we have been able to
  4942.          resolve the matter with you.
  4943.        </div>
  4944.      </blockquote>
  4945.  
  4946.      <p>
  4947. “With you”?  There was no interaction, and if they have resolved the matter, then only to
  4948. their satisfaction.  You'd think they were deliberately trying to insult her.
  4949.      </p>
  4950.  
  4951.      <p>
  4952. If anything, the only effect of this message is to reinforce our intention to change banks.
  4953.      </p>
  4954.      
  4955. End deselected topic ho (Insults from Bank of Melbourne) -->
  4956.  
  4957.                  
  4958. <!-- topic ko not selected
  4959.      <p>
  4960. It's been <a href="http://www.lemis.com/grog/diary-aug2021.php?subtitle=KL%20Hokkien%20Mee&amp;article=D-20210803-013826#D-20210803-013826">over 3 years</a> since I first started to try to cook <a href="http://www.lemis.com/grog/recipes/KL-Hokkien-Mee.php">KL Hokkien Mee</a>.  Gradually it doesn't seem to be as
  4961. complicated any more, but that's at least because of some of the simplifications made: use
  4962. fried pork skin and onion flakes instead of greaves (chu yau cha, 猪油渣), don't brown the
  4963. squid, making it possible to cook without smoking the place out, not like <a href="http://www.lemis.com/grog/diary-mar2022.php?subtitle=Smoke%20in%20the%20kitchen&amp;article=D-20220318-000621#D-20220318-000621">on this occasion</a>:
  4964.      </p>
  4965.  
  4966.            
  4967.      <p>
  4968. I also add chili and much more garlic than the recipes I have found.  The result looks like
  4969. this, before and after the onion flakes:
  4970.      </p>
  4971.  
  4972.            
  4973.      <p>
  4974.      </p>
  4975.      
  4976. End deselected topic ko (KL Hokkien Mee: my version) -->
  4977.  
  4978.            
  4979. <item>
  4980. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2024.php#D-20240925-014345</guid>
  4981. <link>http://www.lemis.com/grog/diary-sep2024.php?topics=c#D-20240925-014345</link>
  4982. <category>technology</category>
  4983. <category>opinion</category>
  4984. <title>New ports</title>
  4985.  <description>
  4986.    <![CDATA[
  4987.    <div align="justify">
  4988.      <p>
  4989. Somebody has broken <a href="http://www.gregroelofs.com/greg_xv.html"><i>xv</i></a>,
  4990. a program that I have been using for ever.  It was one of the programs on my <a href="http://www.lemis.com/grog/Software/Applications-for-UnixWare.php">Applications for UnixWare</a> CD,
  4991. released in 1993.  But the version I have on <i>hydra</i> doesn't recognize <a href="https://en.wikipedia.org/wiki/PNG">PNG</a> images.  I've <a href="http://www.lemis.com/grog/diary-jul2024.php?subtitle=Fixing%20xv&amp;article=D-20240730-225557#D-20240730-225557">established</a> that the problem is with a library, not <i>xv</i> itself, but does that
  4992. help?
  4993.      </p>
  4994.  
  4995.      <p>
  4996. There's a <a href="https://lists.freebsd.org/archives/freebsd-questions/2024-September/005709.html">thread</a> on the <a href="https://lists.freebsd.org/archives/freebsd-questions/">FreeBSD-questions</a> list about mail clients, but there was <a href="https://lists.freebsd.org/archives/freebsd-questions/2024-September/005751.html">one
  4997. reply</a> suggesting <a href="https://feh.finalrewind.org/"><i>graphics/feh</i></a>.  Installed that.  Yes, it works, displays PNG.  But there's nothing that I can do to
  4998. influence the display.  As far as I can see, no rotate, no resize.  Not really a replacement
  4999. for <i>xv</i>, not even in this limited context.
  5000.      </p>
  5001.  
  5002.      <p>
  5003. Alastair Boyanich also recommended another tool for comparing source trees: <a href="https://meld.app/"><i>meld</i></a>.  It's a <a href="https://en.wikipedia.org/wiki/GNOME">GNOME</a> application, but surprisingly installed
  5004. easily and didn't pull in the normal hundreds of GNOME helper ports.  I still don't dare try
  5005. it out.
  5006.      </p>
  5007.      </div>
  5008.    ]]>
  5009.  </description>
  5010.  <dc:creator>Greg Lehey</dc:creator>
  5011.  <dc:date>2024-09-25T01:43:45+00:00</dc:date>
  5012. </item>
  5013.  
  5014.            
  5015. <!-- topic ko not selected
  5016.      <p>
  5017. <a href="http://www.lemis.com/grog/diary-sep2024.php?subtitle=Roast%20beef%20again&amp;article=D-20240922-030313#D-20240922-030313">Saturday's</a> <a href="https://en.wikipedia.org/wiki/Yorkshire_pudding">Yorkshire
  5018. pudding</a> was not a success.  Today we ate more of the roast, and I put the pudding in
  5019. the “bathtub” <del><a href="http://www.lemis.com/grog/recipes/air-fryer.php">air fryer</a></del> convection
  5020. oven for another 20 minutes at 210°.  Still not a real recovery:
  5021.      </p>
  5022.  
  5023.      
  5024.      <p>
  5025. But at least it tasted firmer.  Clearly Yorkshire pudding is not a dish that you can recover
  5026. like this, but it would be interesting to consider whether I could make it in the bathtub.
  5027.      </p>
  5028.      
  5029. End deselected topic ko (Recovering the Yorkshire pudding) -->
  5030.  
  5031.                  
  5032. <!-- topic ah not selected
  5033.      <p>
  5034. The cats have been interested in the garage for quite a while now, and we have suspected
  5035. that they have found rodents.  But I was still surprised when <a href="http://www.lemis.com/grog/Albums/Animals/Bruno.php">Bruno</a> came out of the garage this evening with a
  5036. live mouse in his mouth.
  5037.      </p>
  5038.  
  5039.      <p>
  5040. He went off to the front door with it, where he started playing with it.  I put <a href="http://www.lemis.com/grog/Albums/Animals/Mona.php">Mona</a> there too, and they investigated in some
  5041. detail:
  5042.      </p>
  5043.  
  5044.      
  5045.      <p>
  5046. But they didn't attempt to kill it, confirming my suspicion <a href="http://www.lemis.com/grog/diary-sep2024.php?topics=a&amp;subtitle=A%20mouse?%20%20Rats!&amp;article=D-20240907-025631#D-20240907-025631">a few weeks ago</a> that Mona killed the rat by accident rather than by design.
  5047.      </p>
  5048.  
  5049.      <p>
  5050. So: what do I do with the mouse?  <a href="http://www.lemis.com/yvonne/">Yvonne</a> wanted to put it
  5051. outside, but then it would just have found its way back into the garage.  So: put it in a
  5052. mousetrap:
  5053.      </p>
  5054.  
  5055.            
  5056.      <p>
  5057. It's amazing all the things you can do with chopsticks.  After that I put it outside to wait
  5058. until the morning.
  5059.      </p>
  5060.  
  5061.      <p>
  5062. In passing, it's interesting that when <a href="http://www.lemis.com/grog/Albums/Animals/Larissa.php">Larissa</a> came to join in the fun, Mona let her come really close without getting
  5063. upset.  Clearly there were more interesting things to do.
  5064.      </p>
  5065.      
  5066. End deselected topic ah (Cats and mouse) -->
  5067.  
  5068.      
  5069.                  
  5070. <!-- topic a not selected
  5071.      <p>
  5072. The mouse that we caught <a href="http://www.lemis.com/grog/diary-sep2024.php?subtitle=Cats%20and%20mouse&amp;article=D-20240926-031346#D-20240926-031346">yesterday evening</a> was dead when I came out this morning.  Probably it was on its last
  5073.        legs when <a href="http://www.lemis.com/grog/Albums/Animals/Bruno.php">Bruno</a> caught it.  What should
  5074.        I do with it?  The cats were clearly not interested.  Offered it to <a href="http://www.lemis.com/grog/Albums/Animals/Lena.php">Elena</a>, who sniffed at it and walked off.  Offered
  5075.        it to <a href="http://www.lemis.com/grog/Albums/Animals/Larissa.php">Larissa</a>, who took it off
  5076.        somewhere and presumably disposed of it.
  5077.      </p>
  5078.      
  5079. End deselected topic a (What to do with a dead mouse) -->
  5080.  
  5081.            
  5082. <!-- topic G not selected
  5083.      <p>
  5084. This morning at breakfast, <a href="http://www.lemis.com/yvonne/">Yvonne</a> was looking decidedly
  5085. unwell, and she told me that she was feeling unwell in a manner that suggested that her
  5086. heart medication wasn't sufficient.  She took another <a href="https://en.wikipedia.org/wiki/Flecainide">Flecainide</a> tablet, as instructed for
  5087. such occasions, and gradually things weren't as bad.  But it's happening more often.  Time
  5088. to talk to <a href="https://ballaratcardiology.com.au/staff/dr-rod-reddy">Rodney
  5089. Reddy</a> again.  Called up and—as always—was put on hold waiting for an answer.  But none
  5090. came: after less than 4 minutes, the phone system decided it had had enough, told me to call
  5091. back later, and hung up.  Moral: don't call in the middle of the day.
  5092.      </p>
  5093.  
  5094.      <p>
  5095. Do we even have a referral for Dr. Reddy?  Called up <a href="https://www.healthfirstballarat.com.au/">Health First</a> and asked for one.  More
  5096. hold while the receptionist spoke with Paul Smith, who suggested that she go to the
  5097. Emergency Department—that way madness lies—but reported that she had a permanent referral.
  5098.      </p>
  5099.  
  5100.      <p>
  5101. Called up <a href="https://ballaratcardiology.com.au/">Ballarat Cardiology</a> later
  5102.        and was given the information that Dr. Reddy is on leave until the end of the month, but
  5103.        that she should contact Paul Smith, whom she would inform.  That looks like a waste of time,
  5104.        but we should check.
  5105.      </p>
  5106.  
  5107.      <p>
  5108. Also asked her about mobile phone ECG devices.  <a href="https://en.wikipedia.org/wiki/Apple_Watch">Apple Watch</a>!  I don't see that
  5109. happening; apart from the presumed fact that there are cheaper and better devices, that
  5110. Yvonne wouldn't want to wear something that obstructive, and that she would almost certainly
  5111. need an <a href="https://en.wikipedia.org/wiki/iPhone">iPhone</a> to work with it.
  5112. She didn't have any other suggestions, but at least I didn't get the line “these ECG devices
  5113. are all useless”.  So I'll do some further investigation.
  5114.      </p>
  5115.      
  5116. End deselected topic G (Yvonne unwell) -->
  5117.  
  5118.            
  5119. <!-- topic go not selected
  5120.      <p>
  5121. Nick Macdonald of <a href="https://instagram.com/macgardens">macGARDENS</a> along
  5122. today, rather unexpectedly: he had been due to come yesterday, but didn't inform us, so we
  5123. had written him off.  He was here to take a look at the garden with a view to tidying it up.
  5124. He recognized me instantly: “Wasn't I here a couple of years ago, and we didn't see eye to
  5125. eye?  You were quite antagonistic”.
  5126.      </p>
  5127.  
  5128.      <p>
  5129. Huh?  Was he the bloke who wanted to come only twice a year?  I do recall him, and that our
  5130. intentions didn't match up.  But no, he wasn't that one.  Spent some time talking, and
  5131. though he's <i>really</i> expensive—$1,430 per day—he doesn't have to come that often, and
  5132. we should be able to get by with Jesse doing most of the work for a fraction of the price.
  5133.      </p>
  5134.  
  5135.      <p>
  5136. And was he here before?  Yes, <a href="http://www.lemis.com/grog/diary-sep2021.php?subtitle=A%20new%20gardener?&amp;article=D-20210922-012117#D-20210922-012117">three years ago</a>.  He was the bloke who wanted to come only twice a year—or at least,
  5137. that's what I wrote.  Clearly some kind of misunderstanding.
  5138.      </p>
  5139.      
  5140. End deselected topic go (Another gardener?) -->
  5141.  
  5142.      
  5143.            
  5144. <item>
  5145. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2024.php#D-20240927-030749</guid>
  5146. <link>http://www.lemis.com/grog/diary-sep2024.php?topics=c#D-20240927-030749</link>
  5147. <category>technology</category>
  5148. <category>history</category>
  5149. <category>opinion</category>
  5150. <title>Linux on Intel 4004</title>
  5151.  <description>
  5152.    <![CDATA[
  5153.    <div align="justify">
  5154.      <p>
  5155. Interesting reference in email today: Dmitri Grinberg has run <a href="https://en.wikipedia.org/wiki/Linux">Linux</a> on an <a href="https://en.wikipedia.org/wiki/Intel_4004">Intel 4004</a>:
  5156.      </p>
  5157.  
  5158.      <iframe width="400"
  5159.            height="300"
  5160.            src="http://www.youtube.com/embed/NQZZ21WZZr0"
  5161. allowfullscreen
  5162.            frameborder="0" >
  5163.     </iframe>
  5164.  
  5165.      <p>
  5166. This video is at least partially in fast forward.  It's worth looking at the clock in the
  5167. bottom right corner of the laptop display.
  5168.      </p>
  5169.  
  5170.      <p>
  5171. But how can it work?  The 4004 only had maximum of 4 kB of memory.  It seems that <a href="https://dmitry.gr/?r=05.Projects&amp;proj=35.%20Linux4004#_TOC_6cd03fe22e73587a2147bd353d8c3391">it really just emulates a MIPS instruction set</a>.  Still, an impressive achievement.
  5172.      </p>
  5173.      </div>
  5174.    ]]>
  5175.  </description>
  5176.  <dc:creator>Greg Lehey</dc:creator>
  5177.  <dc:date>2024-09-27T03:07:49+00:00</dc:date>
  5178. </item>
  5179.  
  5180.                        
  5181. <item>
  5182. <guid isPermaLink='true'>http://www.lemis.com/grog/diary-sep2024.php#D-20240928-021431</guid>
  5183. <link>http://www.lemis.com/grog/diary-sep2024.php?topics=c#D-20240928-021431</link>
  5184. <category>technology</category>
  5185. <category>general</category>
  5186. <category>opinion</category>
  5187. <title>Instagram pain</title>
  5188.  <description>
  5189.    <![CDATA[
  5190.    <div align="justify">
  5191.      <p>
  5192. I've had an <a href="https://en.wikipedia.org/wiki/Instagram">Instagram</a> account
  5193. for I don't know how long.  It's not the kind of site that I find useful, but Nick Macdonald
  5194. seems to have <a href="https://instagram.com/macgardens">his only web presence</a> on it.  OK, take a look.
  5195.      </p>
  5196.  
  5197.      <p>
  5198. “Please login to view the remainder of this page”.  OK, Instagram, if you wish.
  5199. “<span style="color:red">Sorry, your password was incorrect.  Please double-check your
  5200. password</span>”.
  5201.      </p>
  5202.  
  5203.      <p>
  5204. Damn you, Instagram.  You have changed my password without telling me.  OK, send me a “Login
  5205. Link”.  But nothing came.  Repeat.  Nothing came.  The mail logs showed that it didn't even
  5206. try.
  5207.      </p>
  5208.  
  5209.      <p>
  5210. OK, new email address, new account.  Select nick?  Sorry, they're all taken or “not
  5211. available”:
  5212.      </p>
  5213.  
  5214.      <table summary="Automatically generated table">
  5215.       <tr>
  5216.          <td valign="top" align="left">stupidinstagrambpas</td>
  5217.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  5218.          <td valign="top" align="left">user already exists</td>
  5219.       </tr>
  5220.  
  5221.       <tr>
  5222.          <td valign="top" align="left">biglier</td>
  5223.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  5224.          <td valign="top" align="left">not available</td>
  5225.       </tr>
  5226.  
  5227.       <tr>
  5228.          <td valign="top" align="left">endlessfrustration</td>
  5229.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  5230.          <td valign="top" align="left">not available</td>
  5231.       </tr>
  5232.  
  5233.       <tr>
  5234.          <td valign="top" align="left"></td>
  5235.       </tr>
  5236.    </table>
  5237.  
  5238.      <p>
  5239. And yes, the first nick was really “stupidinstagrambpas”; I must have accidentally hit some
  5240. extra keys.  But “user already exists”?  Come on, Instagram.  You know that's not true,
  5241. though “endlessfrustration” sounds likely.  How about something in German?  Yes, it accepted
  5242. “verdammteidioten”.  I suppose I should change it if I really want to do something with
  5243. Instagram, but that's becoming ever less likely.
  5244.      </p>
  5245.  
  5246.      <p>
  5247. But my success was short-lived.  A message from Instagram that at least looked amusing in
  5248. the inbox:
  5249.      </p>
  5250.  
  5251.      <blockquote class="fullwidth">
  5252. <div style="text-align:left">
  5253.  <tt>
  5254. &nbsp;&nbsp;10 &nbsp; &nbsp; 26&#45;09&#45;2024 To broken&#45;insta ( 125) Instagram &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Action needed on your account, verdammteidioten
  5255.  </tt>
  5256. </div>
  5257. </blockquote>
  5258.  
  5259.      <p>
  5260. The content, in <a href="https://en.wikipedia.org/wiki/HTML">HTML</a>      </p>
  5261.  
  5262.      <blockquote class="fullwidth">
  5263. <div style="text-align:left">
  5264.  <tt>
  5265. Take action or lose access to verdammteidioten
  5266. <br />Hi verdammteidioten,
  5267. <br />
  5268. <br />Your Instagram account has been suspended. This is because your account, or activity on it, doesn't follow our Community Guidelines on account integrity and authentic identity.
  5269. <br />
  5270. <br />If you think we made a mistake, you have until March 26, 2025 to appeal.
  5271.  </tt>
  5272. </div>
  5273. </blockquote>
  5274.  
  5275.      <p>
  5276. It gave me a login link that didn't work.  Somehow my link name seems appropriate.  My guess
  5277. is that they had a background checker (maybe human) that decided that my nick was not
  5278. appropriate.  But then they should have said so and not immediately disabled my login.
  5279. Should I care?  None of this would have happened if they hadn't broken my original login,
  5280. which remains broken.
  5281.      </p>
  5282.      </div>
  5283.    ]]>
  5284.  </description>
  5285.  <dc:creator>Greg Lehey</dc:creator>
  5286.  <dc:date>2024-09-28T02:14:31+00:00</dc:date>
  5287. </item>
  5288.  
  5289.            
  5290. <!-- topic Go not selected
  5291.      <p>
  5292. So it seems that it's a good idea to buy an <a href="https://en.wikipedia.org/wiki/ECG_monitor">ECG monitor</a> for <a href="http://www.lemis.com/yvonne/">Yvonne</a>.  But which?  Clearly the <a href="https://en.wikipedia.org/wiki/Apple_Watch">Apple Watch</a> is out of the question.
  5293. But they have one at <a href="https://en.wikipedia.org/wiki/Chemist_Warehouse">Chemist
  5294. Warehouse</a> that looks reasonable: the <a href="https://www.biosigdx.com/ecgme">Biosignals ecgme</a>.  I could go into town and get one right now, assuming they're in
  5295. stock.
  5296.      </p>
  5297.  
  5298.      <p>
  5299. But it requires a mobile phone app to operate.  How closely are the data tied to the app?
  5300. Can I back them up?  Off to look for the <a href="https://www.biosigdx.com/_files/ugd/a8ca81_8221aa60a8ca4e0db7fee967751e9c78.pdf">user
  5301. manual</a>, presented as a single strip of 30 pages.  Lots of warnings and things.  How do
  5302. I back up the data?  No mention.  Clearly this is a modern device.
  5303.      </p>
  5304.  
  5305.      <p>
  5306. Much more searching brought me to the <a href="https://store.kardia.com/products/kardiamobile">Alivecor KardiaMobile</a>, and also
  5307. the better <a href="https://store.kardia.com/products/kardiamobile6l">KardiaMobile
  5308. 6L</a>, both of which have <a href="https://kardia.com/ifus/6l-row/19LB75.2.pdf">much better instructions</a>, in particular describing the fact that the ECGs can be
  5309. downloaded in <a href="https://en.wikipedia.org/wiki/PDF">PDF</a> format, which I
  5310. suppose is the best we can hope for at the moment, though the text suggests that something
  5311. gets lost in the translation:
  5312.      </p>
  5313.  
  5314.      <blockquote class="fullwidth">
  5315.        <div class="listitemwidth">
  5316.  Health care professionals (HCPs) may review and analyze the recorded EKG. The Kardia app
  5317.  provides users with the ability to forward the recorded EKG to their HCP in one of two
  5318.  ways, one by using a referral code with HCPs who use Kardia Pro, and the other, by
  5319.  emailing the EKG PDF to the HCP. When connected to Kardia Pro, the user’s EKG recordings
  5320.  are automatically transferred and made available to the HCP. HCPs can review the EKG PDF
  5321.  to perform rhythm assessments as well as measure the QT interval.
  5322.        </div>
  5323.      </blockquote>
  5324.  
  5325.      <p>
  5326. Also found a report that suggested that the KardiaMobile 6L performed much more accurately
  5327. than the Apple Watch.
  5328.      </p>
  5329.  
  5330.      <p>
  5331. In passing, a few recognitions:
  5332.      </p>
  5333.  
  5334.      <ul>
  5335.        <li class="fullwidth">
  5336.          <div class="listitemwidth">
  5337.            The SmartWatch approach has the obvious advantage that it can monitor continuously,
  5338.            while the phone-attached devices require manual intervention.
  5339.          </div>
  5340.        </li>
  5341.  
  5342.        <li class="fullwidth">
  5343.          <div class="listitemwidth">
  5344.            The approach in each case is via electrodes.  Presumably the smart watches only have
  5345.            one, most phone-attached devices have two (one for each hand), and the best have three
  5346.            (the third for the left knee).
  5347.          </div>
  5348.        </li>
  5349.  
  5350.        <li class="fullwidth">
  5351.          <div class="listitemwidth">
  5352.            A dual electrode device such as the KardiaMobile is documented as supplying a single
  5353.            lead ECG.  The triple electrode device such as the KardiaMobile 6L is documented as
  5354.            supplying a 6 lead ECG, thus the name.  Others also repeat this claim, including the
  5355.            better of the two Biosignals ecgme.  By comparison, a clinical ECG monitor has 12 leads.
  5356.            Nobody explains how you can make 1 out of 2 and 6 out of 3.
  5357.          </div>
  5358.        </li>
  5359.      </ul>
  5360.      
  5361. End deselected topic Go (ECG monitor: walk before you can run) -->
  5362.  
  5363.      </channel>
  5364. </rss>
  5365.  

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

  1. Download the "valid RSS" banner.

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

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

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

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

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