As I mentioned before, I installed the beta version of Ubuntu 22.04 LTS on the same system where I had installed Slackware 15.0. The official release of that version of Ubuntu is out and I have according upgrade that system. A few things that I have noticed so far:
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.
Many years ago I used Slackware Linux. I switched to Ubuntu because I was concerned that Slackware seemed to be essentially a one man show, and that seemed like a single point of failure. But Slackware was good to me, and I have not forgotten it. Recently Slackware came out with a new and up to date release and I am looking at it again.
The web site looks much like what I remember from 15-20 years ago. That is OK with me, although I would like to see some more current content. I decided to download the Slackware book in its pdf form. Firefox just hung when I went to that page. However, I noticed that it was an ftp site, not http. 20 years ago I was accustomed to accessing ftp sites using ftp tools, not web browsers. So I guessed that this was what once known as an anonymous ftp site, and that such sites could be accessed with the ftp command line. Feeling like Gandalf recalling a thousand year old spell, I opened a Linux terminal window and proceeded to type:
Networking was built in on the Ubuntu WSL install. WSL Ubuntu under Windows has an IP of 172.17.xxx.xxx, but it can see my local 192.168 network, and the entire internet. WSL Ubuntu says it uses a DNS Server on the 172.17 network. Since WSL uses NAT, I expect that translates to my router on the 192.168 network, which in turn accesses the DNS servers of my ISP. IP addresses in the range 172.16.0.0 to 172.31.255.255 are private, so apparently WSL creates its own network.
Links to Female hurricanes are deadlier than male hurricanes have been circulating around the Web. However, see:
Irish Class, March 4, 2013
Rang Gaeilge, 4ú lá Mí na Márta 2013