|
| Greg's diary |
| April 2025 |
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Tuesday, 1 April 2025 | Dereel → Ballarat → Dereel | Images for 1 April 2025 |
| Top of page | ||
| next day | ||
| last day |
|
Bloody thumb!
|
Topic: health | Link here |
First thing this morning was to change the bandage on my thumb, which had been there since Sunday evening. Blood everywhere! For whatever reason, it hadn't healed adequately. Quite possibly I pulled off the developing scab along with the bandage, but clearly I still need medical attention.
Off to Ballarat to the UFS Urgent Care Clinic at Level 1, 1010 Sturt Street, where I discovered that they only ever have one doctor in attendance. Fortunately the place was almost empty, so I was in and out within half an hour. First Julie, the nurse, took off my bandage and cleaned the wound, which had gradually stopped bleeding:
|
||||||||||||||||||||||||
Then Ben, the doctor, came in and took a look. Yes, too late to stitch or stick, but it would probably not have been necessary anyway. Bandage and it should heal. I forgot to ask how long it would take. So Julie came back and bandaged it, and gave the advice to maintain pressure on the surface if it started to bleed again.
Only after I left did it gradually dawn on me that I have been there before and even confirmed it at the time with the address. That was nearly 14 years ago, and at the time it was a Tristar clinic, since bankrupted and reborn as Family Doctor, one of the places I considered calling yesterday. Why didn't I recognize it earlier?
|
Mobile phone cameras: the limitations
|
Topic: photography, opinion | Link here |
I had intended to take photos of my thumb while at the clinic. Bring a macro lens for my Olympus E-PM2? No, my phone should do it.
Well, not quite. I had thought that the phone could come quite close, but not close enough. This was as close as I could come, and then I discovered that it was still out of focus:
|
||||||||||||||||||||||||
|
||||||||||||||||||||||||
So: still no substitute for a Real Camera.
| Wednesday, 2 April 2025 | Dereel | Images for 2 April 2025 |
| Top of page | ||
| previous day | ||
| next day | ||
| last day |
|
Slow day
|
Topic: health, photography | Link here |
My thumb seems to be recovering well, though I'm concerned about changing the bandage after yesterday's problems. Spent most of the day processing old photos (much of 1980 and from July 1994 to April 1997), with marginally better results in some cases.
|
What's that noise?
|
Topic: general | Link here |
While processing photos, heard a strange mechanical noise. Did it come from eureka? A dying disk, maybe? Got up, but it stopped. It started a little later and kept going long enough for me to walk about and find it following me. Outside the office? Dish washer?
No, it was outside the house:
|
|||||||||||||||||||||||
The Spiteris are having their water tank cleaned. Why now, when the tank levels are at the lowest of the year? And why was it so difficult to localize the source of the noise?
| Thursday, 3 April 2025 | Dereel | Images for 3 April 2025 |
| Top of page | ||
| previous day | ||
| next day | ||
| last day |
|
Stupid finches!
|
Topic: animals | Link here |
Into Yvonne's bedroom this morning with intent to let Bruno out into the dog run. But it was overrun with red-browed finches, which even congregated directly on his hiding place. They didn't leave until I got my camera.
Currently the run looks like this:
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
So neither reflective strips nor bells have worried them. How has the species survived?
|
Where have my photos gone?
|
Topic: photography, technology, history, opinion | Link here |
More processing old photos today, including considerable improvements on some of the photos I took during the 1967 Asia Trip. Stupidly, I had taken the photos on Ektachrome and developed them myself in substitute chemicals. Given the once-in-a-lifetime nature of the trip, I should have taken them on Kodachrome.
To make matters worse, on at least one film I messed up the clearing bath stage, resulting in a pink tinge on the photos, like here:
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
To my surprise, a simple white balance change fixed it (run the cursor over an image to compare it with the previous version):
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
I had expected it to be some kind of second order cast.
I also had the exposure notes, so I was able to set the Exif data accordingly. This one was labeled “Donkey”:
|
|||||||||||||||||||||||
Where's the donkey? Not the (out of focus) person in the foreground. He just walked into the photo at the last minute, and until today I never realized that I had missed the donkey.
And then I found a number of missing directories that weren't missing at all. They were just missing from the directory list file. One was relatively recently. Off to check. The file is called /home/grog/public_html/photos/dirlist, and it consists of a pair title, description, like this:
20001122 Mike Smith Memorial Room, Greg's office
20001130 Yana in gum tree
I keep it under RCS, so it was relatively easy to see what happened; I just needed to compare each revision with the previous one:
=== grog@hydra (/dev/pts/32) ~/Photos/20250126 4392 -> for i in `jot 100 9830`; do j=`expr $i + 1`; echo rcsdiff -wur1.$i -r1.$j dirlist; rcsdiff -wur1.$i -r1.$j dirlist; done | less
And how about that:
--- dirlist 2025/02/13 02:06:59 1.9838
+++ dirlist 2025/02/13 02:23:19 1.9839
@@ -3,7 +3,6 @@
19561226 Kota Bharu
-19571101 Grattan Street, Carlton
19620912 Bev and Greg before leaving for England
@@ -13,14 +12,11 @@
19640421 Netherton House
-19640601 Sir Alec Douglas-Home at Kings College, Taunton
19640608 Shahram Akhavan
-19640611 Bath festival, Kings College kitchens
-19640816 Swimming Sports at Lake Club
19640822 Kemaman, ferry
@@ -30,11 +26,6 @@
19640913 Greg on TV
-19640924 England, Exeter Cathedral, King's College
-19640927 England, Exeter Cathedral, King's College
-19641009 Ricky Cookson
-19641029 Half term holiday, music, King's College
-19641105 Kings College, Taunton
...
-20250213 Cockatoos and corellas, strange papaya
+C
In fact, the damage is much more extensive:
=== grog@hydra (/dev/pts/32) ~/public_html/photos 4378 -> rlog -r1.9839 dirlist
...
revision 1.9839
date: 2025/02/13 02:23:19; author: grog; state: Exp; lines: +1 -881
Automatic checkin
881 removed lines! How many are left?
=== grog@hydra (/dev/pts/32) ~/Photos/20250126 4394 -> wc -l /home/grog/public_html/photos/dirlist
5615 /home/grog/public_html/photos/dirlist
A sixth of all entries! What do these have to do with anything? Clearly it's not random damage, since it's the loss of specific entries, but why? Looking at them, it seems that many of them have been changed relatively recently. But that would have been a change, not a new entry. So far I can't work out what went wrong. About the only clue I have is that the entry for the day has gone away and been replaced by a line with just the letter C. Could it be that I aborted the process somehow? I still don't seen how that could have caused that damage.
And how can I recover? The obvious thing to do would be to repeat the way I created them:
dirlist:
if [ -f Makejpeg ]; then \
DIRLIST=~/public_html/photos/dirlist; \
BASEDIR=`basename \`pwd\``; \
co -l $$DIRLIST; \
grep -v $$BASEDIR $$DIRLIST > dirlist.tmp; \
echo -n "$$BASEDIR " >> dirlist.tmp; \
head -1 ~/Photos/$$BASEDIR/Makejpeg >> dirlist.tmp; \
sort dirlist.tmp > $$DIRLIST; \
rm dirlist.tmp; \
ci -u -m"Automatic checkin" $$DIRLIST; \
fi
That works, up to a point, but I introduced Makejpeg only about 13 years ago. What about the other ones? And how did this happen in the first place?
|
Thumb on the mend
|
Topic: health | Link here |
Gradually the bandage on my thumb has reached its use-by date. Time to remove it and hope that there won't be lots of blood again.
No:
|
|||||||||||||||||||||||
So that problem seems to have gone away.
| Saturday, 5 April 2025 | Dereel | Images for 5 April 2025 |
| Top of page | ||
| previous day | ||
| next day | ||
| last day |
|
Dog eats cat
|
Topic: animals | Link here |
Seen at the entrance to the dog run outside Yvonne's bedroom:
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Larissa killing Bruno? No, they're just playing:
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
|
Recovering dirlist
|
Topic: photography, technology, opinion | Link here |
How do I recover my seriously broken ~/pubic_html/photos/dirlist? It should have round 6,500 entries, one for each directory in ~/pubic_html/Photos/. But at least 880 entries are missing. I can't automatically rebuild the entries with my current method, because the infrastructure is missing for the older entries.
OK, manual it is. Find the log messages where more than 2 entries had been deleted, and create diffs from the previous
=== grog@hydra (/dev/pts/32) ~/public_html/photos 4449 -> rlog -r1.7655 dirlist
revision 1.7655
date: 2020/10/08 03:47:35; author: grog; state: Exp; lines: +1 -38
Automatic checkin=== grog@hydra (/dev/pts/32) ~/public_html/photos 4450 -> rcsdiff -wur1.7654 -r1.7655 dirlist
===================================================================
RCS file: RCS/dirlist,v
retrieving revision 1.7654
retrieving revision 1.7655
diff -wu -r1.7654 -r1.7655
--- dirlist 2020/10/07 01:08:41 1.7654
+++ dirlist 2020/10/08 03:47:35 1.7655
@@ -326,7 +326,6 @@
20010322 LUGS in Singapore
20010323 Eating satay with LUGS and rms
20010324 Harish and Groggy, Bukit Timah Saddle Club
-20010325 Shierlaw Street house sold
20010403 Fluffy as baby
20010405 Thursday, 5 April 2001
20010411 Yana
@@ -368,7 +367,6 @@
20020104 Mick and Diane Lehey
20020117 Grashopper, new Mitsubishi Magna
20020131 Bushfire at Diane Saunders', Wantadilla house
-20020202 Household computers
20020207 Convert to BSD
20020210 Big steak, Mobilestar breakage
20020215 BSDCon dinner in San Francisco
...
Then collect all the deleted entries, marked by a dash (-) in column 1:
=== grog@hydra (/dev/pts/32) ~/public_html/photos 4449 -> for i in 7655 4501 4404 3985 3301 2825 1440 1297; do j=`expr $i - 1`; rcsdiff -wur1.$j 1.$i ~/public_html/photos/dirlist; done|grep ^- > dirlist-add
The result gave a number of duplicates, of course, most of which I was able to remove with sort(1):
=== grog@hydra (/dev/pts/32) ~/public_html/photos 4409 -> sort -u dirlist-add > dirlist2=== grog@hydra (/dev/pts/32) ~/public_html/photos 4410 -> l dirlist-add > dirlist2=== grog@hydra (/dev/pts/32) ~/public_html/photos 4411 -> sort -u dirlist-add > dirlist2=== grog@hydra (/dev/pts/32) ~/public_html/photos 4412 -> l dirlist-add dirlist2
-rw-r--r-- 1 grog lemis 204.647 4 Apr. 16:15 dirlist-add
-rw-r--r-- 1 grog lemis 54.808 4 Apr. 16:15 dirlist2=== grog@hydra (/dev/pts/32) ~/public_html/photos 4413 -> wc -l dirlist-add dirlist2
4473 dirlist-add
1113 dirlist2
5586 total
But they only removed identical entries, and I had to go through the list and tidying up things like this:
19810924 Oktoberfest in München
19810924 Oktoberfest in München
19810924 Oktoberfest in M\374nchen
That wasn't helped by the fact that Emacs didn't want to believe that the document was UTF-8 because of the breakage. I started with 6,700 entries, and after some hours I made my way through 7% of the file, reducing it to 6,523 entries. That was round mid-2006, and I hope that it represented most of the breakage. But it's a surprisingly slow business.
In passing, the entry for 20010325 is interesting:
|
|||||||||||||||||||||||
That's the mystery photo that I had been puzzling about only last week. It's the house that my aunt Audrey and family had lived in since about 1950, 13 Shierlaw St, Richmond SA. The photo is almost unrecognizable, and looking at Google Maps “street view”, it seems to have been torn down and replaced with something modern.
| Saturday, 5 April 2025 | Dereel | Images for 5 April 2025 |
| Top of page | ||
| previous day | ||
| next day | ||
| last day |
|
Whither Bruno?
|
Topic: animals, general | Link here |
We've had Bruno for two years now. At the time we got him, he was ideal: a male chocolate Burmese, 3 months old—just my specifications. And he was just round the corner, the only one West of Melbourne.
But somehow he didn't develop the way I had hoped. He's still so hyperactive, and we can't be sure that he won't catch another bird. On the other hand, he's not the only cat we've had who caught birds. Sixteen years ago Lilac caught and ate a crimson rosella, and I didn't even bother to mention it in the diary:
|
|||||||||||||||||||||||
I still don't want Bruno to catch birds, but maybe we're becoming more sensitive.
|
Fixing dirlist
|
Topic: photography, technology, general | Link here |
Spent a little time this morning continuing with my dirlist reconstruction, but I didn't have much time. And then it occurred to me: each directory has a file description with the content of the header, though I no longer seem to use it. But that's exactly what I need for my Makefile target:
dirlist:
rm -f dirlist.new
for i in [12]*; do \
if [ -e $i/description ]; then \
(echo -n "$$i "; cat $$i/description) >> dirlist.new; \
fi; \
done
But I didn't have time for that today. The good news is that I could just check in the flaky dirlist that I have, and that it worked, sort of, at least better than before.
|
Rebuilding lagoon
|
Topic: multimedia, technology, general, opinion | Link here |
Today Yvonne made the mistake of taking a video from horseback using her mobile phone. And she held it in portrait orientation!
Once I got it onto a sane machine, I discovered that avidemux, at least as installed on lagoon, has no provision for rotating video clips. It saw it as landscape, and there was nothing I could do to fix it.
I've hated avidemux since I first installed it over 13 years ago. To add to that, my Google Gemini query failed, producing just random junk on the screen. lagoon's system is over 4 years old, and it is clearly in need of upgrading.
So how do I do it this time? Every time I do an upgrade I find things that fail without good reason, and I still haven't finished the install on hydra that I started 1½ years ago. But something has to be done. I had already started an install on an SSD a couple of months ago. Bring it up to date, and then I can install it beside the old lagoon, so that Yvonne can fall back to it if something unexpected shows up. Today I got as far as bringing the system up to date.
| Sunday, 6 April 2025 | Dereel | Images for 6 April 2025 |
| Top of page | ||
| previous day |
|
A new video editor?
|
Topic: technology, multimedia, opinion | Link here |
I've decided that avidemux's days are over. A quick Google Gemini search gave me a list of others to try: kdenlive, openshot and blender. As feared, they dragged in a whole slew of dependencies:
===== Sun 6 Apr 2025 13:58:57 AEST on dereel.lemis.com: pkg install kdenlive openshot blender
The following 183 package(s) will be affected (of 0 checked):
New packages to be INSTALLED:
ImageMagick7: 7.1.1.26_6
...
Number of packages to be installed: 183
The good news is that they installed cleanly. Now to run them. But for that I need X.
|
A maze of twisty little symlinks
|
Topic: technology, opinion | Link here |
So dereel in its incarnation as a copy of lagoon is up and running. Start X? Fails: it had the xorg.conf file for the real lagoon, and the hardware is different here. OK, remove it and see what happens. Starts, bla[cn]k screen.
Oh. Window manager not running. This is due to the transition from fvwm2 to fvwm3 that I started over a year ago. OK, install fvwm3 and continue.
Multiple issues with the configuration files. For years the configuration on lagoon has Just Worked, as the .Xdefaults files show:
=== root@lagoon (/dev/pts/8) ~ 123 -> l ~yvonne/.Xdefaults-*
-rw-r--r-- 1 yvonne home 3,664 6 Jul 2002 /home/yvonne/.Xdefaults-battunga
-r--r--r-- 1 yvonne home 732 1 Nov 2007 /home/yvonne/.Xdefaults-lagoon
Those config files are 23 and 17 years old! One of the reasons for my global changes: I want a central set of configuration files so that any changes I make will apply to all systems. So I have put them in the /home/local/X hierarchy. /home/local is NFS mounted across all systems.
Except on lagoon. For reasons I have forgotten, some of the programs in /home/local/bin are different for lagoon, so it has its own local /home/local. I needed to add a symlink from (local) /home/local to (remote) /home/local/X.
Looking back, it seems clear that I need a further layer in my PATH, something like
That's a surprising number, and the last three have two subdirectories, bin for normal programs and sbin for administrative programs. But any such change is for another day.
Finally got the files where I wanted them:
Finally got all that put together and tried—once again.
X.Org X Server 1.21.1.14
X Protocol Version 11, Revision 0
Current Operating System: FreeBSD dereel.lemis.com 14.2-STABLE FreeBSD 14.2-STABLE #2: Sun Apr 6 10:59:34 AEST 2025 grog@dereel.lemis.com:/home/obj/hydra/home/src/FreeBSD/git/stable/14/amd64.amd64/sys/GENERIC amd64
/home/local/X/.Xdefaults-dereel:1:3: error: invalid preprocessing directive
1 | # $Id: diary-apr2025.php,v 1.6 2025/04/07 02:23:59 grog Exp $
| ^
/home/local/X/.Xdefaults-dereel:24:12: warning: empty character constant [-Winvalid-pp-token]
24 | ! Why doesn''t this work?
| ^
/home/local/X/.Xdefaults-dereel:25:14: warning: empty character constant [-Winvalid-pp-token]
25 | ! Why - doesn''t this work?
| ^
2 warnings and 1 error generated.
xrdb: "*VT100.translations" on line 23 overrides entry on line 5
What's that? It seems that X has become pickier in the course of time. # was never a valid delimiter, but it's not clear why it now objects to text in comments. It appears to go through cpp, and that has changed. But that's easy enough to fix.
Next,
Error: Can't open display: unix:0
Couldn't open /home/yvonne/.fvwm/fvwm_mfl_:0.0.pid because: Permission denied
Why can't it open the display? Hard to say. It's not even clear what produced that first line. But the second was more of a problem. I didn't know that fvwm3 wanted to create files in its configuration directory, and arguably that's wrong. But I wasn't able to set my symlinks so that user yvonne could write to it:
=== root@dereel (/dev/pts/0) ~ 2 -> ls -l ~yvonne/.fvwm
lrwxr-xr-x 1 root home 19 6 Apr 16:18 /home/yvonne/.fvwm -> /home/local/X/.fvwm=== root@dereel (/dev/pts/0) ~ 3 -> chmod 777 ~yvonne/.fvwm=== root@dereel (/dev/pts/0) ~ 4 -> ls -l ~yvonne/.fvwm
lrwxr-xr-x 1 root home 19 6 Apr 16:18 /home/yvonne/.fvwm -> /home/local/X/.fvwm
It took me some time to realize that you need a -h option to change the mode of the symlink itself:
=== root@dereel (/dev/pts/0) ~ 5 -> chmod -h 777 ~yvonne/.fvwm=== root@dereel (/dev/pts/0) ~ 6 -> ls -l ~yvonne/.fvwm
lrwxrwxrwx 1 root home 19 6 Apr 16:18 /home/yvonne/.fvwm -> /home/local/X/.fvwm=== root@dereel (/dev/pts/0) ~ 7 ->
But by then I had had other things to do.
|
Rebuilding dirlist, try 3
|
Topic: technology, photography, opinion | Link here |
Also ran my script to rebuild dirlist as planned yesterday. Things weren't quite as good as I expected: not all the description files contained what they should, and some were missing. Clearly a file whose time has passed. But now I have two different partial dirlists, both wrong. Maybe there's a little less work now, but I'll have to see. The diffs are remarkably large. Here the version I created yesterday (dirlist) and the one I did today (dirlist.new):
=== grog@hydra (/dev/pts/32) ~/public_html 4509 -> diff -wu photos/dirlist Photos/dirlist.new | wc -l
5661=== grog@hydra (/dev/pts/32) ~/public_html 4510 -> wc -l photos/dirlist Photos/dirlist.new
6526 photos/dirlist
6437 Photos/dirlist.new
The diffs are nearly as big as the files, and some of the damage is surprisingly recent:
=== grog@hydra (/dev/pts/32) ~/public_html 4508 -> diff -wu photos/dirlist Photos/dirlist.new
...
20250209 Steak and kidney
+20250210 Corymbia ficifolia
20250211 Yvonne's new rug
|
ALDI enchiladas
|
Topic: food and drink | Link here |
Yvonne bought some pre-prepared enchiladas at ALDI last week. They're wrapped in something vaguely resembling tortillas, but clearly made from wheat, and they're enormous!
|
|||||||||||||||||||||||
They didn't taste too bad, but I have a feeling we could do better ourselves. The big issue is the size of the tortilla—it's possible that ALDI is on the right track with these ones.
Do you have a comment about something I have written? This is a diary, not a “blog”, and there is deliberately no provision for directly adding comments. It's also not a vehicle for third-party content. But I welcome feedback and try to reply to all messages I receive. See the diary overview for more details. If you do send me a message relating to something I have written, please indicate whether you'd prefer me not to mention your name. Otherwise I'll assume that it's OK to do so.
| Top of page | Previous month | Greg's home page | Today's diary entry | Greg's photos | Copyright information |
