I spent the weekend of June 16-19 at Carleton College. The occasion was my 50 year class reunion, for which I was a member of the gift committee, which in turn was a part of the overall planning committee. Mia (my wife) and I had a room on the third floor of Watson Hall, “3rd Watson” was how we would have referred to it back in the day. I don’t know if the current students refer to campus locations like that. I lived on “6th Watson” my senior year.
What I wrote in Slackware Diary – 3 about keeping Slackware up to date is not correct:
slackpkg update gpg slackpkg update
# slackpkg install-new # slackpkg upgrade-all # slackpkg clean-system
By default, Windows assumes that the local system clock is set to local time, and updates it accordingly. Ubuntu Linux assumes that the clock is running UTC (essentially Greenwich Mean Time) and will update it on that assumption. Since it knows your location (you specified it at installation, and hopefully updated it when you moved) it will display the correct local time just like windows.
The problem comes when you have a dual boot (Linux and Windows) system. When you reboot from one OS into the other the new OS will assume the system clock is behaving according its own rules, even though the other OS was following its rules. To fix this:
As I mentioned in Slackware Diary, I installed Free42 As I wrote in 2006 I fell in love with HP calculators and their RPN notation back in the 1970s, and still find the conventional algebraic notation rather awkward. I no longer carry a physical calulator, but I have Free42 installed on my phone and my tablet, and on my Windows systems. Now I also have it on Slackware. So I circled back to see if I could install in on Ubuntu.
Continuing from Slackware Diary – 1
Fixed the prompt by copying .bashrc and .profile (renamed as .bash_profile) from my primary Ubuntu system. This works and I have nice color prompts in Slackware. Need to see if I have scripts from my previous Slackware days to add environment variables, aliases, etc. Life in Slackware means a lot of time on the command line.
The next task on my list was to install Flatpak so I could use apps from Flathub
Back in February I looked at the Slackware Linux web site. After years of working with Ubuntu, and occasionally its parent Debian, I decided to see if I could install Slackware and get it to work. I used it a lot in the first years of the current century. Could I still manage it now, or had the comforts of the Ubuntu installation process dulled my edge? From Slackware 15 – The old brigade:
Slackware is deployed using an ncurses interface, with a set of menus where you must make intelligent choices, including partitioning and package selection. And then, there’s LILO the bootloader. Not GRUB, mind! Feels a bit daunting, but then, if you’re careful and methodical, there should be no issues. That said, the approach automatically precludes Slackware from being a typical desktop choice, as most people would have no idea what to do with the installer.
As I wrote in September, my HP EliteDesk 705 G2 SFF desktop with an AMD PRO A4-8350B R5 processor was giving me messages about limited computer resources when using Zoom under Windows 10, though not under Linux. These sitll occur, even though I have added memory, taking it from 8GB to 24GB. This last time, I finally remembered to bring up Task Manager. It showed me that there was no memory problem, but that Zoom was using a lot of CPU. Why this occurs with Windows but not Linux is puzzling. For now I will have to have all of my Zoom sessions on that system under Linux rather than Windows.