Since I’m working on two new books, I have, once again, gotten into my LS-120 backup habit. I have been copying files down to a Super Floppy on that one machine for a while now. The other day, when I had family type obligations, I decided to apply updates since I didn’t really have time to get into writing mode. After the updates were applied I decided to make one more Super Floppy backup for … Just How Poorly are IDE Cables Made?Read more
Ubuntu
Question From a Reader
The following question came in from a reader who happened to catch one of my posts on a programming email list. ==== As usual, I quite enjoy your detailed analysis coupled with historical contexts, since I learned my trade through those days (Sun SPARC workstations, VAX minicomputers running VMS, etc.). They are always entertaining, usually edifying, and sometimes nostalgic for me. :) I’m curious, though, about one particular point you made: Windows isn’t even going … Question From a ReaderRead more
How Far We’ve Come – Pt 11
This post is a bit of housekeeping. Since I started this series my development machines have all moved to KDE Neon so I started reading forward from the original post and when I got to this post I realized we didn’t have a pre-installed method of restoring a Raspbian image. Yes, there are lots of posts giving you the dd command for restore after you run a bunch of other commands to identify the SD … How Far We’ve Come – Pt 11Read more
How to Set Up Mutt to Work With JustHost.com Email
Every now and then you are going to need to send email from the command line. In the world of OpenVMS we did it from batch jobs all of the time. Yes, there were abort routines which would notify all operators currently logged in and who had typed REPLY/ENABLE at their terminal, but, you still sent email just in case. OpenVMS had a robust email system long before we had an Internet, indeed, long before … How to Set Up Mutt to Work With JustHost.com EmailRead more
Ubuntu/Linux List All Exit Status Codes
I see this questions about this posted a lot. I also see numerous responses telling people to read through C header files. While you certainly cannot identify application level exit codes without valid documentation for the package, you can get the Ubuntu/Linux exit codes with one easy command. kill -l