|
| Greg's diary |
|
||||||||
|
|
|
||||||||||||||||
| Wednesday, 1 April 2026 | Today's diary | Today's images | top | next | last |
Another of those day pairs where I do lots of things (yesterday) and spend the whole next day writing up about them (today). I didn't even finish before dinner.
Yvonne into town today, and while she was there she had a growth excised. She was given a sheet of paper, a copy of a message sent to Matthew Pilkington, a colleague of Paul Smith who had presumably written the referral. Diagnosis: "LEFT LATERAL NECK SHAVE NODULAR AND SUPERFICIAL BASAL CELL CARCINOMA” (why do they shout?). Then clinical notes: "Left lateral neck evolving flat red macule ? Bowen's disease”. No mention of a prognosis, and following up shows that Bowen's disease is different from basal-cell carcinoma. The general impression I get is that the matter has been dealt with now, but it would be nice to have some kind of confirmation. The Wikipedia pages suggest that there's not much danger, but why go to a doctor when “I read it on the Internet”?
File system full on fra.lemis.com today. Nothing unusual: it's the web server logs. Rotate (I must really automate this) and compress.
But then I saw a file /var/tmp/webfoo or some such, and it was big (gigabytes) and growing. Where did that come from? lsof to my aid. Oh, no lsof. OK,
=== root@fra (/dev/pts/1) /var/tmp 62 -> pkg install lsof
Updating FreeBSD repository catalogue...
pkg: An error occurred while fetching package: No error
pkg: An error occurred while fetching package: No error
repository FreeBSD has no meta file, using default settings
And there it hung. This isn't a very old system (FreeBSD 14.2, not even a year old).
While pondering what to do, compressing the old web log completed. And webfoo went away. Was it a symlink maybe? It had a link count of 1. Strange name to choose, more like something that I might have thought up. But I have no recollection.
No named failures today, but it's only a matter of time. And currently I have no backup, so each failure means an average of 30 minutes with no resolution. Why not do it on fra?
Oh. fra has had a named running since December last year. Copy the latest zone files and try again:
=== root@fra (/dev/pts/1) /usr/local/etc/namedb 115 -> service named restart
named not running? (check /var/run/named/pid).
/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
There's something very strange about named.
| Thursday, 2 April 2026 | Today's diary | Today's images | top | previous | next | last |
So why does named no longer run on fra.lemis.com? Another question for the twins, which indicated that my named.conf is older than the named on fra. OK, fix:
@@ -1,10 +1,12 @@
+include "/usr/local/etc/namedb/rndc.key";
+
controls {
inet * port 52 allow { any; }; // a bad idea
- unix "/var/run/ndc" perm 0600 owner 0 group 0; // the default
+ inet 127.0.0.1 port 953 allow { 127.0.0.1; } keys { "rndc-key"; };
};
And yes, that fixed it. But BIND is now 40 years old. It's still unstable (version 8 at any rate), and you'd think that the new versions could accommodate the old ones.
One of the things that most irritate me about DxO PhotoLab is that by default cropping an image retains the original aspect ratio, and there's no setting to get rid of it: I have to reset to “unconstrained” every time. But today, for the first time in over 10 years, I found a reason to use it.
Well, not quite. The photo was taken with my OM System OM-1 Mark II and thus had a 4:3 aspect ratio. But Yvonne wanted it on the root window of lagune as a background, so it had to be 16:9. And I was able to set that:
Yvonne has been following the weekly petrol prices. This week they're lower. The government has halved the petrol excise tax, worth about 25¢ per litre:
|
||||||||||||||||||||||||
But look at the image quality. Here a cutout:
|
|
||||||||||
That should be perfectly legible. What went wrong? One thing, of course, is that it was taken with a mobile phone, but it still should be much better than that. To be investigated.
| Friday, 3 April 2026 | Today's diary | top | previous | next | last |
What did I do today? Nothing interesting that I could remember the following morning. I suppose this will happen more and more as I get older. It's not as if I didn't do anything, but it was just repetitive stuff not worth talking about.
| Saturday, 4 April 2026 | Today's diary | Today's images | top | previous | next | last |
Sixty-three years ago I started keeping what has become this diary. At the time, I wrote a relatively detailed description of what I did throughout the day. But that's boring: get up, have breakfast, have lunch, ...
But that's about all I did today. Also take the house photos, watch TV... Is it going to continue like that?
From time to time I have used formulations like “The firings will continue until morale improves” in humour. But there's no humour in this amazingly stupid war against Iran. Today I read in the Washington Post, quoting an unnamed “former official”:
“If the Iranian side is not flexible, then they can keep killing them until you find someone who is willing to cut a deal,” he said. “When you put more pressure, that’s what the Iranians seem to be more responsive to.”
Idiocy. They don't understand anything. Where will this end?
Call from Joe at thecatshack today with a quote for the cat enclosure: $5,200! We were expecting roughly 20% of that price.
After catching my breath, told him that that was beyond our means. What do we do now? Make the enclosure smaller? Many people live in less than the 85 m² that we had wanted to enclose. Yvonne came up with an alternative, a prefabicated frame with typical “metric” dimensions 1.8 × 1.8 × 5.4 m, not too small for the cats, for $802 delivered:
|
|||||||||||||||||||||||
Is that the solution? How do the cats get in and out? Our previous plan would be simple enough: open the door and let them in. Here Yvonne was talking about a tunnel and a hole in the wall. To be considered.
| Sunday, 5 April 2026 | Today's diary | Today's images | top | previous | next | last |
So what do we do with the cat enclosure? We're really only a little further than we were a month ago. But maybe the dog run isn't such a bad idea after all. Yes, getting Paul Donaghy to do it will be much cheaper than Joe, but it will still be more expensive than the prefabricated unit that we were looking at yesterday. We'll need 156 m² of netting, about $750, and then the frames to hold it up, and of course Paul's time. What can go wrong?
We've seen these lilies before:
|
|||||||||||||||||||||||
They're clearly self-seeding, and in the past they have flowered mainly in March or earlier. Yvonne once liked them, but now she doesn't.
I've made a number of Semmelknödel over the last few years, but I've always had trouble with the quantities. Today I did it again, and finally it seems to be taking shape (spherical, of course). Conveniently, I now need 150 ml of milk, exactly the content of a small pack of UHT milk. A little less breadcrumbs (I think 140 g instead of 150 g) and we should be done.
| Monday, 6 April 2026 | Today's diary | Today's images | top | previous | next | last |
Strange message in my news feed this morning:
Tuesday will be Power Plant Day, and Bridge Day, all wrapped up in one, in Iran. There will be nothing like it!!! Open the Fuckin’ Strait, you crazy bastards, or you’ll be living in Hell - JUST WATCH! Praise be to Allah.
Not the sort of message I usually see. Clearly somebody from Israel or the USA. Ah, there:
President DONALD J. TRUMPApr 05, 2026, 10:03 PM
The time, supplied by his “Truth” Social, appears to be our local time, in other words 12:03 UTC.
But even for Trump this is a new low. Is he really getting scared? May he die of fright!
It's been nearly 2½ years since I got hydra.lemis.com, my new desktop machine. And I still haven't finished configuring it!
I suppose I should take comfort in the fact that Bruce Evans apparently had the same issues with his “new” machine, which coincidentally I called hydra before it became evident that it was not worth keeping. And probably he had the same issues that I had: the software has changed in ways that I don't like, in many cases outright bugs. I've started collecting them in their own page. So far I have:
So what do I do about it? Keep eureka around, now over 12 years old and running FreeBSD 10.2, installed over 10 years ago. Under the circumstances it doesn't make sense to upgrade it.
Some time ago I bought this sauce for a recipe I found somewhere:
|
|||||||||||||||||||||||
Where? I don't recall. I really should write these things down here. Off to look at YouTube videos, where I came up with Rad Na:
And there they showed a bottle that looked the same, but not quite. Mine is labeled (in English) “Soybean paste”, but theirs was labeled “Fermented Soybean Paste”. What's the difference? Much searching showed that they have at least five different labels, but only the one product. Their product description page shows yet another variety. The important detail is that it's “Soybean” paste A, and that there are no chilis in it (that's a different product).
Apart from the Rad Na, I also found a recipe for Pad Kee Mao.
And the twins came up with further names that I could follow: Khao Man Gai, Pak Boong and Gai Pad King.
Last year I found some camera strap clips that looked almost ideal. But I was cautious at the time, and it looks as if I was right. Today one came apart, sort of. It opened up beyond what should have been possible. Put it back together by moving the tongue sideways, and it looks almost acceptable:
|
|||||||||||||||||||||||
But looking at it from the side, it's no longer stable:
|
|||||||||||||||||||||||
That's almost impossible to recognize. But the clip has to go. When will people come up with a reliable, quick-open strap clip?
| Tuesday, 7 April 2026 | Today's diary | Today's images | top | previous | next | last |
Decided on phat si-io for breakfast today. That's a straightforward enough dish, and I have all the ingredients, including gai lan and kway teow. But why not experiment a bit? The one issue with the dish is that the kway teow needs to be cooked very hot and charred (nothing to do with char kway teow). One of the things that I noted yesterday is that some other Thai dishes char the noodles first, which could be an advantage. But how about other flat noodles that don't disintegrate as easily, like the Shan Dong noodles that I have. And while I'm at it, I had some cabbage left over that I could use instead of the gai lan.
So off. First the noodles:
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
And this time I cut the cabbage with a knife rather than with a mandolin:
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
The result doesn't look as good with cabbage as with gai lan (first image):
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
And the taste? Not as powerful as I recalled. But then I discovered that I had made nearly double the quantity of noodles, and it kept me sated all day, to the point that I only had a light dinner. The recipe calls for 180 g of kway teow, but a “basket” of the Shan Dong noodles weighs 230 g after cooking. Next time I should aim for 150 g of either.
While cooking breakfast this morning, I had a photo taken before the flash units had recharged:
|
|||||||||||||||||||||||
I never cease to be amazed how much can be pulled out with postprocessing. It's still not good, of course, but it's interesting that the smoke is much more in evidence. Here a comparison with a correctly exposed image (run the cursor over an image to compare it with its neighbour):
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Maybe I should disable the flashes (and expose accordingly) for this kind of photo.
Donald Trump is up on his hind legs again. “A whole civilization will die tonight” says the would-be recipient of the Nobel Peace Prize.
Why now? He's been working on destroying US civilization for nearly 10 years.
| Wednesday, 8 April 2026 | Today's diary | top | previous | next | last |
It's been eight months since my last experience with git. It wasn't positive, and I put it into the “too hard” basket.
But I have to commit something to maintain my “commit bit”, now nearly 28 years old. OK, try again with the same file. And how about that, the results were different:
=== grog@hydra (/dev/pts/38) /home/src/FreeBSD/git/main/usr.bin/du 19 -> git push freebsd
fatal: unable to access 'https://git.freebsd.org/src.git/': The requested URL returned error: 403
Oh. What's that? Asking the twins brought only marginal help. But they suggested trying directly with ssh. And how about that:
=== grog@hydra (/dev/pts/38) /home/src/FreeBSD/git/main/usr.bin/du 20 -> ssh git.freebsd.org
grog@git.freebsd.org: Permission denied (publickey).
Disconnected at Wed 8 Apr 2026 12:05:53 AEST
What's going on there? Has somebody already removed my commit bit? My guess is that I somehow ended up messing around with invalid ssh keys. I've already had issues with eureka, whose ssh no longer talks to other systems even on my local network. It's ancient. How old? The man page tells me:
-V Display the version number and exit.
OK,
=== grog@eureka (/dev/pts/0) ~ 11 -> ssh -V
unknown option: '-V'
OpenSSH_6.6.1p1, OpenSSL 1.0.1p-freebsd 9 Jul 2015
Somehow this all fills me with confidence. But I really need to debug those issues, and soon.
I did establish one thing, though:
=== grog@hydra (/dev/pts/38) /home/src/FreeBSD/git/main/usr.bin/du 9 -> git config --list
color.ui=no
color.all=false
color.all=no
color.push=false
color.branch=false
color.diff=false
color.interactive=false
color.status=false
color.log=false
safe.directory=/eureka/home/src/FreeBSD/git/main
safe.directory=/eureka/home/src/FreeBSD/git/stable-13
safe.directory=/eureka/home/src/FreeBSD/git/ports
user.email=groggyhimself@FreeBSD.org
user.name=Greg Lehey
core.repositoryformatversion=0
core.filemode=true
core.bare=false
core.logallrefupdates=true
remote.freebsd.fetch=+refs/notes/*:refs/notes/*
remote.freebsd.url=https://git.freebsd.org/src.git
remote.freebsd.fetch=+refs/heads/*:refs/remotes/freebsd/*
branch.main.remote=freebsd
branch.main.merge=refs/heads/main
Where is it getting that information from? git seems to use relative files some of the time, and this one is in the main hierarchy. I would far rather see the file itself. But it contains a couple of entries of interest: safe.directory. main is there, and also stable-13. Where did stable-14 go? Is it related to where I asked for the config info?
HOW I hate git!
| Thursday, 9 April 2026 | Today's diary | Today's images | top | previous | next | last |
Checking the overnight logs in the office this morning, discovered that lagune was down. There was no other indication of a power issue, so it really looks as if it (probably the power supply) is on the way out. Really not a good purchase.
Warren Toomey runs two mailing lists on TUHS, the Unix Heritage Society, and from time to time I send messages there. I've noticed in the past that I seldom get replies, but I had expected one from my message about Panic! last month. A bit of searching through the archives showed that no message of mine was saved in the archives in as far back as I looked.
Message to Warren, who was just recovering from an international flight, jet lag and flu, and entertaining a house visitor. He tried a couple of things and decided that it was probably because I cryptographically sign my mail messages. Who would have thought that software in the Unix space (here Mailman) would reject cryptographic signatures?
But none of his “fixes” helped. In the end, he responded with effectively “It's your problem. You fix it”. That's not unfriendly. He gave me complete access to minnie.tuhs.org, a high honour. Now to try to understand Mailman.
What should we eat tonight? Nothing special. How about fettuccine with ragù bolognese? We have both, so we just have to warm them up.
Oh. No cooked and frozen fettuccine. But we had these:
|
|||||||||||||||||||||||
I've never eaten this particular variety before. OK, cook them. But they really didn't want to, and they stuck together really badly, and also burnt on the base of the saucepan. Lots of attempts to salvage them, with only partial success. And as if that weren't enough, we didn't have any grattuto and had to make do with some tasteless grated “pizza cheese”. Neither a pleasant nor an easy dish, and my attempts to salvage things mean a second dishwasher load tomorrow.
What went wrong? They weren't even the first flat noodles that I cooked today (flat rice noodles for breakfast). Why did they stick? Not enough water? Bad kind of pasta? One way or the other, that's the last time I buy them from Woolworths.
| Friday, 10 April 2026 | Today's diary | top | previous | next | last |
Spent some time today, not overly long, in looking at tuhs.org's mailman issues. I've never seen it before, but in principle the web interface (intuitively called “Postorius”, which I thought was a German politician) doesn't look too bad. With the marginal help from Google Gemini found a tab “Alter Messages”, which only accepts specific MIME types. But it included the types specified in my messages, text/plain and application/pgp-signature, presumably after Warren added them. So what could it be? Is there something hidden in my messages?
Yes! Looking at the message as stored on /var/mail/groggyhimself, the whole thing is enclosed in a multipart/signed which is invisible to the user. It did accept multipart, so it wasn't clear whether adding multipart/signed would help. But it did. And promptly G. Branden Robinson piped up: he, too, had had the same problem, and possibly others who hadn't noticed it. As I wrote in my test message,
I'm not overly secure, but cryptographic signatures have so far been only refused by systems in the Microsoft space.
And there was general agreement.
After one success, how about another try to commit the file that failed so dramatically on Wedensday. I had written to Philip Paeps to ask him to check my access.
Fool! I had tried to commitpush to a read-only repository! I should push
to gitrepo.freebsd.org, not git.freebsd.org. Read the git primer.
Well, yes, that's what I had read. It states:
Then you should have the official mirrors as your remote:% git remote -v
freebsd https://git.freebsd.org/${repo}.git (fetch)
freebsd https://git.freebsd.org/${repo}.git (push)
Ah, but ignore that. Some way further down it says:
% git remote set-url --push freebsd git@gitrepo.freebsd.org:\${repo}.git
Now isn't that misleading? But there's more in there, including what to do when—once again—I got the message
=== grog@hydra (/dev/pts/37) /src/FreeBSD/git/main/usr.bin/du 48 -> git push
To gitrepo.freebsd.org:src.git
! [rejected] main -> main (fetch first)
error: failed to push some refs to 'gitrepo.freebsd.org:src.git'
hint: Updates were rejected because the remote contains work that you do not
hint: have locally. This is usually caused by another repository pushing to
hint: the same ref. If you want to integrate the remote changes, use
hint: 'git pull' before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.
So far it seems that the first thing is to ignore the illegible text, but I need to read the whole document first. It seems that it is in great need of updating; apart from the misleading text, some of the information is over 10 years out of date. But at least I can see a way forward.
One thing still doesn't work, and nobody can tell me what to do: HOW can I get rid of this half-coloured output from git, like in the example above?
I eat KL Hokkien Mee relatively frequently. I also have a recipe for Singapore Hokkien Mee, but only pre-prepared sauce or my own experiments. Today I found this recipe, which, like others, stresses the importance of using home-made prawn head broth. It also emphasizes that the noodles should be half Hokkien noodles and half rice vermicelli, something that I think also applies to KL Hokkien Mee, and it mentions two further varieties, both from Penang: Hokkien Char and Penang Hokkien Mee. Time to consolidate.
| Saturday, 11 April 2026 | Today's diary | Today's images | top | previous | next | last |
Warren Toomey was very happy about yesterday's success in persuading mailman to deliver signed email messages. So he added me to the admin list! Now as long as nobody tries to claim that I'm a mailman expert.
That required getting more access to minnie.tuhs.org. Allow it to contact me? In principle I had (somewhat unorthodox) shell access, but it can't harm to add it explicitly:
ipfw add 111 allow ip from minnie.tuhs.org to any
The result? The existing shell connection to minnie was aborted. Why? That doesn't make any sense at all. I had to remove the rule, after which things worked.
My hourly start of named on lax.lemis.com seems to have leveled out. Until recently. Today I had no fewer than 12 restarts—every other hour. Presumably that means that there was no named running for 6 hours! A good thing I have a backup on fra, but this is unacceptable.
Jesse Walsh along today for what proved 5 hours' work in the garden. It certainly makes a difference.
While he was there, he changed the light globe that I had noted last month. Surprise, surprise! It wasn't the remaining one that still worked: it was the other one.
My web site load is rising again, due to many anonymous bots. How can I protect myself?
=== root@lax (/dev/pts/2) /var/log/www 117 -> tail -1000 /var/log/www/www.lemis.com.log | sed 's: .*::' | uniq -c | sort -n
...
18 57.141.2.8
19 52.167.144.171
19 57.141.2.55
26 40.77.167.143
126 57.141.2.45
OK, 57.141.2.45 only accounts for 12.6% of the load, but there are others:
=== root@lax (/dev/pts/2) /var/log/www 117 -> grep 57.141.2 | wc -l
963
And it's too polite to have reverse lookup. Goodbye 57.141.2.45:
=== root@lax (/dev/pts/2) /var/log/www 119 -> ipfw add 113 deny ip from 57.141.2/24 to any
00113 deny ip from 57.141.0.0/24 to any
Huh? I said 57.141.2, not 57.141.0. It seems that I needed to specify the entire address:
=== root@lax (/dev/pts/2) /var/log/www 127 -> ipfw add 113 deny ip from 57.141.2.0/24 to any
00113 deny ip from 57.141.2.0/24 to any
And how about that, the load dropped significantly:
=== root@lax (/dev/pts/2) /var/log/www 133 -> ipfw show | grep ^00113; sleep 10; ipfw show | grep ^00113
00113 1128 65000 deny ip from 57.141.2.0/24 to any=== root@lax (/dev/pts/2) /var/log/www 134 -> ipfw show | grep ^00113; sleep 10; ipfw show | grep ^00113
00113 1168 67400 deny ip from 57.141.2.0/24 to any
But there must be a better way. I had thought of blocking requesters without reverse lookup, but that probably excludes many valid requests. I really should rework my photo display functions to use POST instead of GET.
| Sunday, 12 April 2026 | Today's diary | top | previous | next | last |
To my surprise, joining the TUHS team was not as quiet as I expected. Somehow I spent most of the day chasing up things, most of which are confidential.
The TUHS issue wasn't made any easier by the fact that my nameds kept going away. I had guessed yesterday that 12 hourly restarts meant 6 hours without named, but that's assuming a random distribution. Started a loop instead:
=== root@lax (/dev/pts/2) /var/log/www 155 -> while :; do /usr/local/sbin/named -4 -f -u bind -c /usr/local/etc/namedb/named.conf; date; done
Abort trap
Sun 12 Apr 2026 02:16:16 UTC
Abort trap
Sun 12 Apr 2026 02:19:33 UTC
...
Abort trap
Sun 12 Apr 2026 13:14:41 UTC
All in all I had 91 crashes in 11 hours, an average of one crash every 7¼ minutes. But then it stopped. Wouldn't it be nice to know what was causing it?
My web servers were overloaded again today, which also didn't help my other issues. Where's my mail? On lax.lemis.com, /var/log/maillog told me:
Apr 12 02:52:12 lax sm-mta[2203]: rejecting connections on daemon Daemon0: load average: 42
Apr 12 02:52:27 lax sm-mta[2203]: rejecting connections on daemon Daemon0: load average: 41
Apr 12 02:52:42 lax sm-mta[2203]: rejecting connections on daemon Daemon0: load average: 42
Apr 12 02:52:47 lax postfix/smtpd[2079]: connect from unknown[114.64.255.201]
Apr 12 02:52:48 lax postfix/smtpd[2079]: NOQUEUE: reject: RCPT from unknown[114.64.255.201]: 450 4.7.25 Client host rejected: cannot find your hostname, [114.64.255.201]; from=<shuiwudaikai2@hotmail.com> to=<liuzhong@lemis.com> proto=ESMTP helo=<hotmail.com>
Apr 12 02:52:48 lax postfix/smtpd[2079]: disconnect from unknown[114.64.255.201] ehlo=1 mail=1 rcpt=0/1 rset=1 quit=1 commands=4/5
Apr 12 02:52:57 lax sm-mta[2203]: rejecting connections on daemon Daemon0: load average: 41
Apr 12 02:53:12 lax sm-mta[2203]: rejecting connections on daemon Daemon0: load average: 40
The load averages were roughly correct. But what's sm-mta? What's Daemon0?
Cordon bleu for dinner tonight. Yvonne had bought some Woolworths veal “sizzle steak” for the purpose. Not a good idea, it seems. Their quality leaves much to be desired, they're too thick even after hammering, and they're also too tough. Not to be repeated; either good quality veal or chicken breast, though I personally don't like the latter as much.
| Monday, 13 April 2026 | Today's diary | Today's images | top | previous |
Received in the mail today:
Hi GREGORY
It�s time to reverify your personal details
We�re committed to protecting you and the wider community from identity theft, fraud and other financial crime.
From time to time, we need to check in to ensure your personal details are up to date. This is a legal requirement sometimes known as �Know Your Customer� that helps us keep you and the community safer.
The message claimed to be ANZ, a bank with whom I have an account. Is it genuine? One of their settings is the name by which they should call me, Greg and not GREGORY. And clearly their markup is broken. A quick look at the source shows:
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DUTF=
-8">
...
It=92s time to reverify your personal details
The =3D are because it was Quoted-printable, and it represents ", which is valid. But the text contains the character =92 (0x92), which is not in the UTF-8 character set (it's a Microsoftism), and firefox chooses to represent it as �. All indications that it's some kind of scam, as does the message itself:
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
But the message came from what appears to be ANZ, and it was sent to my private ANZ email address. Could ANZ be that broken? Yes, in my experience. That's one of the several reasons why I'm migrating elsewhere. They wanted me to prove my identity with documentation in a manner that might become clear as I progressed:
|
|
|||||||||
OK, go to my onlie profile. First step: I was presented with a QR code. What can I do with that on my computer? And how do I know what it is? Fired up hirse, my old phone, and took a look:
|
|||||||||||||||||||||||
“https://idv.trustme...”. idv, I don't trust you further than I can throw you. So much is wrong with this message:
|
|||||||||||||||||||||||
Sorry, ANZ, though I suspect that it must be you (no scammer would produce such a broken case), this is the last straw.
For some reason one of the mice on Yvonne's computer, lagune.lemis.com was jittery: the cursor ran back and forth a few pixels several times a second, though it didn't wander. Maybe for that reason the screen never blanked, and Yvonne had to turn off the monitor when not using the machine.
Took a look this morning. Nothing obvious. Stopped and restarted X. No help. Disconnected and reconnected the mice. The jittering stopped, but it still doesn't blank. Why not?
I think that it's really time to replace the hardware.
It's been two years since my cataract operations. No glasses any more? Anything but! I don't have any accomodation any more, so I have:
And of course I'm continually mislaying glasses. Today it was the computer glasses. But this time, despite repeated searching, there was no sign of them. And the window was pretty tight: from just before taking the dogs for a walk until just after the return. I don't take the glasses with me when I walk the dogs, though I did check if they were on the road somewhere. Where can they be?
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 | Greg's home page | Today's diary entry | Greg's photos | Copyright information |
