Into town today. Apart from a haircut and a visit to the Fruit Shack, Yvonne wanted to look at a carpet for sale in Mount Clear. We were to meet there.
OK, get the directions from Google
Maps and send them to my phone. See that the notification arrived, head off. Enable
the route. It's gone! For no obvious reason, the notification had disappeared. And the
only way to get the information, including the all-important address, would have been to go
back inside to a Real Computer and send it again.
No time for that. But Yvonne had told me: down to the roundabout, first left, first left.
So I tried that. It wasn't nearly as obvious as it sounded, and I found myself driving
around for a while. But Yvonne was there: find her on the map and go to her. And how about
that, I found her in Cartilage Cartledge Avenue. I recognized that name: the
house is there. But she went straight across the road and back the way I had come from.
OK, follow her. After a while she stopped, leaving me blocking an intersection, and told me
that her phone had claimed she had arrived when she was 500 m from the destination.
Fortunately, round that time, the people we want to visit called and gave us the exact
address.
The carpet itself was a disappointment, but I discovered that there was a much easier way
back to Sebastopol:
just head up west on Cartledge Avenue, turn left onto Tinworth Avenue and we'd hit
Whitehorse Road, the road to Sebastopol. In Tinworth Avenue I asked Google Maps to take me
to Arabella. But instead of giving
me a route, it held a lecture about where it might be. When I finally got it to shut up, it
disagreed with my route. Turn back and go down Cartledge Avenue, 1.1 km further. Ignored
that and headed onwards, where there were no issues beyond traffic on Whitehorse Road.
Done? Not at all. Driving on to the Fruit Shack, it lost its mind, or at least its vision:
Still no map, but it had decided that I should go by foot! How do I change that? It took
me 5 minutes to find that it had hidden the choice of transport down some unlikely menu at
bottom left. Finally I briefly emerged from the darkness:
Backups to my first new disk went well. Today's the day for the weekly swap, so put in the
second disk. First, connect to distress to save the disk contents (one
Microsoft Start_Here_Win.exe and a whole slew of programs
in Start_Here_Mac.app). That was a pain: to be on the safe side, I was running
the CMD.EXE as administrator, with the unexpected result that it didn't see any of my
“network shares”, and it
took me a while to work out what was wrong this time.
Preparing the disk for FreeBSD was easier,
but not as easy as it should have been: I wrote down the steps last week, but I got them wrong (now corrected). Here what I did today:
Get the newfs parameters from /Photos and use them to create the new file
system:
Instead of the normal 10 seconds, it took DxO 25 minutes to process the image! My
guess is that it was performing lots of little transfers, each of which got held up by the
disk load of the backup.
Interestingly, this disk identified itself differently. Last week there was no relationship between the serial number on the package and the
serial number of the disk. Today the package stated a serial number NT17MDRZ,
which the device expanded to 00000000NT17MDRZ, and the name was also different:
Jun 11 11:21:09 eureka kernel: da2 at umass-sim2 bus 2 scbus6 target 0 lun 0
Jun 11 11:21:09 eureka kernel: da2: <Seagate Expansion HDD 1802> Fixed Direct Access SPC-4 SCSI device
Jun 11 11:21:09 eureka kernel: da2: Serial Number 00000000NT17MDRZ
Jun 11 11:21:09 eureka kernel: da2: 400.000MB/s transfers
Jun 11 11:21:09 eureka kernel: da2: 15259647MB (31251759103 512 byte sectors: 255H 63S/T 1945332C)
Jun 11 11:21:09 eureka kernel: da2: quirks=0x2<NO_6_BYTE>
Shopping at the Fruit Shack is always frustrating. They have lots of good things, some of the time. Today I found
even less of the items on my shopping list than normal. To make the point, I found more of
them at the nearby Ballarat Asian Grocery, where I normally don't find much.
As if that wasn't enough, I had had problems with an item I bought last time:
I had noted it at the time because it had no identifying label, though clearly it was dòufu
puffs. And when I got round to using them about 10 days ago, they had gone mouldy! The
use-by date is clear: 11 September. So I asked the cashier for a refund. “But they haven't
expired yet”. Tried to make it clear that they were mouldy, but I'm not sure she
understood. “Why didn't you bring them earlier?”. “Look, you can call this number” (on the
receipt). Neither would have helped if they hadn't been mouldy at the time. Call the
manager, please. Sorry, no manager here. Finally, as a gesture of good will, she accepted
it, not before I got seriously angry. And the query about the cost of some pork balls went
nowhere, since they were out of stock and I couldn't show them what I bought. She just said
“That was a Chinese cashier”, something obvious here where nearly everybody is Chinese.
Only she is Indian or similar. Somehow the cashier name on the receipt seems appropriate:
“Simple”.
What do I do? The Fruit Shack is getting more and more on my nerves, but they're a valuable
resource, and I don't want them to get into trouble.
What is it? Yvonne thought that it was a Star, or starling, and that seems likely. But the
German name „Star“ is somehow appropriate: it's a homonym of „starr“, meaning stiff, and so
it was.
How did it die? Yvonne thought that it might have flown against a windscreen and broken its
neck, but the neck seemed unaffected. About the only thing obvious was that one foot was
held higher than the other.
ffm.lemis.com in its old incarnation is gone. fra.lemis.com has taken over
the net proxy, but it only occurred to me today that ffm was also a name server. OK,
migrate the name servers, in the process changing IP addresses so that ffm is now a
name for fra, 192.248.184.42. Simple: take the configuration
from lax.lemis.com (in its incarnation as ns1.lemis.com), frob slightly and
start on fra:
=== root@fra (/dev/pts/2) /usr/local/etc 17 -> service named start /usr/local/etc/namedb/named.conf:7: unix control '/var/run/ndc': not supported
/usr/local/etc/rc.d/named: ERROR: named-checkconf for /usr/local/etc/namedb/named.conf failed
Huh? What does “not supported” mean? But I've always had trouble with rndc, and I
find it easier to restart named with a kill -1. OK, comment out the reference
to /var/run/ndc, which proves to be a socket. Try again.
Jun 12 05:57:25 fra named[10112]: the limit on open files is already at the maximum allowed value: 116964
Jun 12 05:57:25 fra named[10112]: isc_stdio_open '/var/log/named/named-2.log' failed: file not found
Jun 12 05:57:25 fra named[10112]: configuring logging: file not found
Jun 12 05:57:25 fra named[10112]: loading configuration: file not found
Jun 12 05:57:25 fra named[10112]: exiting (due to fatal error)
Jun 12 05:57:25 fra grog[10116]: /usr/local/etc/rc.d/named: WARNING: failed to start named
What does that mean? Ah, no /var/log/named/? Create that and try again:
Jun 12 05:58:41 fra named[10134]: isc_stdio_open '/var/log/named/named-2.log' failed: permission denied
Jun 12 05:58:41 fra named[10134]: configuring logging: permission denied
Jun 12 05:58:41 fra named[10134]: loading configuration: permission denied
Jun 12 05:58:41 fra named[10134]: exiting (due to fatal error)
Jun 12 05:58:41 fra grog[10138]: /usr/local/etc/rc.d/named: WARNING: failed to start named
Oh. /var/log/named belonged to root, but named runs
as bind. Once again:
=== root@fra (/dev/pts/0) /var/log 69 -> l -d named drwxr-xr-x 2 root wheel 512 12 Jun 05:58 named
=== root@fra (/dev/pts/0) /var/log 70 -> chown bind:bind named
And then it ran. Only one message puzzled me:
Jun 12 06:00:53 fra named[10174]: the limit on open files is already at the maximum allowed value: 116964
Sample photo from Yana taken with her new Leica Summilux 25 mm f/1.4 lens. Not good. I have exactly the same model, so it was
relatively easy to compare (and confirm that photos of text are a good way to test lenses).
Here her photo and mine, both taken at f/1.4:
The brightness isn't important. It's difficult to get good exposure of a display screen,
and normally I would correct it. But the image quality seems much worse than mine. Here
top left, centre and bottom right, first Yana's lens, then mine:
On the one hand, both lenses are acceptable. In the Good Old Days you wouldn't expect
anything like that good a result. But clearly the new lens isn't nearly as good as the old
one? Should I return it? That would be a pity.
This page contains (roughly) yesterday's and today's entries. I have
a horror of reverse chronological documents, so
all my diary entries are chronological. This page normally contains the last two days,
but if I fall behind it may contain more. You can find older entries in
the archive. Note that I often update a diary entry
a day or two after I write it.
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.
