20190924

Tue 24 Sep 2019 08:04:07 AM EDT Slept from ten to six without waking. High of seventy-six and mostly sunny today. Work: - Email meeting URL to Heidi and Julie Done. - Check out CentOS 8 Done, minimally. - Read about VTI and IPsec Done. - Automate backups for NVR's No. - Continue Prop mgnt software questions Done. https://lists.centos.org/pipermail/centos-announce/2019-September/023449.html https://wiki.centos.org/Manuals/ReleaseNotes/CentOS8.1905?action=show&redirect=Manuals%2FReleaseNotes%2FCentOSLinux8 https://www.redhat.com/en/blog/transforming-development-experience-within-centos > CentOS Stream is a developer-forward distribution […] The CentOS Stream project sits between the Fedora Project and RHEL in the RHEL Development process, providing a "rolling preview" of future RHEL kernels and features. […] CentOS Stream is parallel to existing CentOS builds; this means that nothing changes for current users of CentOS Linux and services, even those that begin to explore the newly-released CentOS 8. So, CentOS Stream is sort of like Debian Testing? Twenty-minute walk at lunch. Heard crickets and cicadas. Saw a quartet of seagulls and a dragonfly. https://hackaday.com/2019/04/01/bye-bye-vi-gnu-linux-distros-drop-support/ > If you grew up with Unix systems like we did, you’ll be sorry to hear the news: vi, the noble text editor that has served us so well these 40 years, is going away — from many GNU/Linux systems, anyway. As of this writing, GNU/Linux Mint, Debian, Ubuntu, and OpenSUSE — four of the five most popular GNU/Linux distributions — have all announced that they will no longer ship the ‘vi’ editor as part of their base installs. For those of us who got our start in the punched-card era and still think of files as a collection of lines instead of a stream of bytes, this is a major blow. But, we can all take some comfort in the fact that, at least for now, the stripped-down version of vim synonymous with vi on these systems will continue to be available from package repositories. > The reasons for the move aren’t entirely clear to us, but from what we can see on the GNU/Linux mailing lists, the confusing modal interface and the fact that novice (and many seasoned) users can’t figure out how to save a file and exit the program seem to have influenced the decision. > So, with the two favorites out of the race, what will be the default editor in the new GNU/Linuxes? We spoke with an insider at a major commercial distribution (you know which one) who told us that a version of Microsoft’s Visual Studio Code (renamed GNU/Visual Studio Code) will ship with the base install of all future versions of their GNU/Linux operating system, effectively replacing vi. Sigh, I got fooled by a five-month-old April Fools joke. But the base Debian Buster install, at least the LXC container, really doesn't come with a vi. Then again, the LXC container doesn't have `nano` either, which I suspect may normally ship with base. Home: - Call mom back Done. - Go to bed early Ten-minute walk. Washed dishes, vacuumed, took out trash Watched a couple episodes of Homeland. Refined my IPsec notes. Servings: grains 6/6, fruit 2/4, vegetables 4/4, dairy 5/2, meat 3/3, nuts 0/0.5 Breakfast: two eggs Brunch: banana, cucumber, coffee Lunch: gyro, fries Afternoon snack: celery, grapefruit, coffee Dinner: pizza 126/73

< ^ txt