Re: Bah and Double Bah (BDB)!
A CDR for every CAR. . . .
90 publicly visible posts • joined 28 Jan 2019
A now-defunct company for which I once worked hired movers who didn't know computers. Management had decided that the new server room would be the one with a huge transformer in the middle of it, and the movers set one of the file servers on that, thus scrambling the hard drive contents.
Just to satisfy curiosity, I didn't boot any of my test VMs, Windows 10, Windows 11, Devuan Linux (pegged to the unstable branch) for a month, to see which one would update fastest. Devuan unstable is pretty much Debian unstable, lots and lots of packages over the course of a month.
From clicking power on, to forcing the update, to rebooting and then shutting down, with all three on the same SSD, and updated serially:
Devuan: 13 minutes (included installing a new kernel and linking in the Nvidia and ZFS packages)
Windows 11: 31 minutes
Windows 10: 34 minutes
I finally got a second SSD for my laptop that came with Windows 11, and put Linux Mint Debian Edition on it.
Wake from sleep is more reliable now - Windows would frequently switch off the backlight right at the point it wanted my password, and I'd have to type Ctrl-Shift-Win-B several times to get it to come back.
All my games work fine with either Lutris or Steam.
The video card in my DVR is a GT 610, an Nvidia Fermi-chipset model, and the 390 driver is the last in the Devuan package archive to support it. Someone in the maintenance pipeline has been nursing it along; version 390.157-8 compiles and links with the 6.10 kernel series.
This card's stock fan is loud, so I rewired it to run on 5V. I don't drive the GPU hard enough to need the fan to run faster than it does on 5V.
Every time there's an update to this driver package, I make sure to download all the associated .deb files, in case they disappear from the repos.
Back in the day, my favorite word processor was Wordstar something-dot-something (maybe 2.x) on my TRS-80 Model I. Clearly a port of the CP/M version, it was the only word processor I used on an 8-bit computer that could handle files bigger than memory (48KB, in my case). I ran it on both floppy disks and HDD - my first was 5MB.
If you rely solely on Apple, that's sort of true.
The people who maintain the OpenCore Legacy Patcher are great.
My mid-2012 non-Retina MacBook Pro is still running a current macOS release (Monterey), thanks to them. On an SSD, it's still usable. Forget using an old Mac with an HDD unless it's in a server role, where snappy interactive performance may not be needed/desired.
I have another one running Windows 10, via Bootcamp drivers, which is, sadly, better-performing than any macOS release. It's even still usable as a light gaming rig.
Once Windows 10 support goes away, I'll either let the old MBPs go or switch them to some Linux distro. Hopefully one of them gets the trackpad support right. So far I haven't found such a beast.
. . . as a pathway for the emergency of artificial general intelligence?
If DNA replication errors lead to mutations, some of which lead to successful offspring, then why couldn't a long-running piece of software, if big and complex enough, possibly lead to a moment of self-direction?
It may take a long time, but. . . .
A while back I bought Pimlical through the Google Play store. Pimlical is the current offering from the author of the long-ago popular Palm Pilot app Datebk3 and then Datebk4, which I also used back in the day.
I changed phones, and didn't use it for a while, then decided I wanted to try it again. Gone from the Play store, because the author didn't want to play Google's games any more.
No recourse but to buy it again, directly from the author.
No, thanks.
"On the other hand, by supporting systemd, we reduce the friction and problems that KDE and GNOME developers face currently, they build their UIs to work with systemd and so we can run them as they intended to. The APIs provided by systemd are actually needed to run a modern smartphone UI on Linux: there isn't really an alternative out there."
systemd is friction incarnate, keeping me from controlling the hardware I own.
I doubt it will work with Veracrypt, either, which is how my old Macbook Pro's Windows installation is encrypted.
I did the manual resizing steps in my Win10 VM, and they worked, but I haven't yet decided to try it on the MBP, because I'd have to unencrypt first.
Edit: I did have to move the EFI partition after resizing the C: partition, as this VM was converted to EFI after initial build. I used Knoppix+Gparted for that. . . .
After that, there was enough room to make a new, bigger, WinRE partition.