I often spot dates and times which have unusual regularities. I realised earlier this year that the 2nd of February – 2/2/22 – would have some nice ones. These kind of date patterns are almost always contingent on the order in which day, month and year are written in the date format. I associate D/M/Y with the UK and Europe, and M/D/Y with the US, but the picture is more complicated than that – see this Wikipedia article for details: https://en.wikipedia.org/wiki/Date_format_by_country
Here are a few which I find pleasing:
Works for both MDY and DMY date formats.
How about adding a time?
22:22 2/2/22 – very nice
22:22:22 2/2/22 – adding seconds takes it to the next level
2/22/22 MDY (DMY: 22/2/22)
Without leading zeros, this one has variants for DMY and MDY date formats. We can also add a time as before:
I really like the mirror symmetry, though, the symmetry is broken in MDY format. Since 2022 isn’t a palindrome, just adding a time doesn’t work – unless you also specify seconds
22/02/2022 02:20:22 – huge!
Now, if only this could have all happened on a ‘2sday’ instead of a Wednesday!
It’s amazing how much is going on in the natural world. There is a constant life and death tussle. Yesterday, I watched a tiny spider leap on a tiny fly. In the blink of an eye, it leaped onto the fly and off again. Then it wandered away, licking its chops. I’m not sure if the fly was already dead, and the spider didn’t get anything, or if the fly, in a microsecond, ripped a chunk off it and ate it.
This morning I watched a different, bigger, spider (still no more than 3mm long), munching on a fly.
Yesterday I finally installed pop on my ThinkPad X1 Extreme. I was a little nervous because it has been a loooooooong time since I’ve set up dual booting on anything. This ThinkPad is such a beautiful machine – it would be a shame to break it.
The main issue for me when I was looking into this is getting the Pop! OS boot loader to pick up the existing Windows installation. Pop! installs its firmware in a new EFI partition which is created during installation. The Grub bootloader, which many linuxes use, automatically detects any existing Windows installation – even if it is in a different EFI partition -and adds an entry to its boot menu. Pop! uses systemd-boot instead of grub, and systemd-boot doesn’t detect that Windows is installed with a different EFI partition. I read some advice to copy the windows boot files from the Windows EFI partition into the new Pop OS EFI partition, and some other advice saying that may not work well. I re-read what System 76 say about dual booting Pop OS and I finally got it:
To boot your other OS:
– If your device is in EFI mode, use your device’s built-in boot menu. – If your device is in BIOS mode, a menu will automatically appear when powering on.
Choose your previous OS with the arrow keys, then press Enter.
So the deal is that if you let the machine start using the systemd-boot which was installed, then you will get a boot menu which basically offers Pop. To boot Windows you need to activate the Windows boot loader either by hitting F12 (on my machine) and selecting it from the system UEFI , or, possibly by selecting the Windows boot loader option from the systemd-boot menu.
I have spent a fair amount of time over the past few days reading about bootloaders in preparation for installing linux dual boot on my laptop. I made a Windows recovery drive and took a peek at its contents: