Skip to content

Both.org

News, Opinion, Tutorials, and Community for Linux Users and SysAdmins

Primary Menu
  • About Us
  • Computers 101
    • Hardware 101
    • Operating Systems 101
  • Linux
    • Why I use Linux
    • The real reason we use Linux
  • My Linux Books
    • systemd for Linux SysAdmins
    • Using and Administering Linux – Zero to SysAdmin: 2nd Edition
    • The Linux Philosophy for SysAdmins
    • Linux for Small Business Owners
    • Errata
      • Errata for The Linux Philosophy for SysAdmins
      • Errata for Using and Administering Linux — 1st Edition
      • Errata for Using and Administering Linux — 2nd Edition
  • Open Source Resources
    • What is Open Source?
    • What is Linux?
    • What is Open Source Software?
    • The Open Source Way
  • Write for us
    • Submission and Style guide
    • Advertising statement
  • Downloads
  • Home
  • Using my own books
  • Books
  • Linux

Using my own books

David Both January 23, 2021 4 minutes read
BlankMillenniumHeader

Last Updated on February 3, 2026 by David Both

One of the things I state in the Introductions about my books is that I use them myself as references and this week was no exception.

I perform many tasks on Linux computers for which I am responsible and a good deal of the time, that means remotely. And I don’t mean just from one room to the next. In many cases I need to do things over a distance of miles. I do a lot of things quite frequently and so I need no reminders of how to perform those tasks. But this week was different.

I had two problems on one computer for which I am responsible at a remote location and I did not have the time to drive there. Well – I didn’t want to drive there in any event. So, to fix both problems, I logged in to the problem computer from home using SSH.

And I used my own books as a reference resource for the tasks I performed.

Kernel problems

The first problem was with VirtualBox, the free open source software I use for running virtual machines. I knew I could fix this easily because I have done it several times; it is a problem in which VirtualBox cannot compile the kernel modules for the new kernel and I need to revert to the previous kernel. So I configured grub to boot to the previous kernel by changing the line GRUB_DEFAULT=saved to GRUB_DEFAULT=1 in /etc/default/grub. Normally the “saved” option specified in that line says that every time that Linux boots, grub saves the identity of the kernel that was booted and that becomes the default kernel for the next boot.

This resolves the problem until a kernel fix can be provided. I did not need much help with this but I did check Chapter 16 of Volume 1 of my self-study series “Using and Administering Linux: Zero to SysAdmin” to verify that I remembered the right option and the right file in which to make that change. I also needed a little help with the syntax of the command required to rebuild the grub configuration file using the revised grub default file.

[root@studentvm1 grub2]# grub2-mkconfig > /boot/grub2/grub.cfg

I don’t cover this specific situation in that series so I have added this information to my technical website at http://www.linux-databook.info/?page_id=6044.

Printer configuration

The second problem is that one of the printers available to the host was not available in the print menu when the office manager tried to print. The network printer was visible but the USB attached local printer was not. So I needed to create the print queue for that USB printer. Unfortunately, this is one of those tasks I only perform once every 3 or 4 years so I don’t really remember how to do it.

Using an SSH login session, I followed the step-by-step directions in Volume 2, Chapter 7, of my self-study series “Using and Administering Linux: Zero to SysAdmin,” Experiment 7-2, to add this print queue and test the result – successfully.

About my books

My books were written to be used as references and all of them started as memory aids for me. I would perform many tasks infrequently and it seemed a waste of time to keep doing the same research many times over. So after discovering new tools, fixes, and solutions, I started recording them so I could find them easily. Eventually I used that material as the basis to create a series of three, 4-day instructor-led courses that I taught for several years.

And then I decided to convert those courses into the books that I have written over the past several years. Because they are written in a way that can be used both for training and reference, I find them to be useful all the time. I think you will, too.

So, yes, I would really like you to purchase my books. You can find all of them listed here and specifically my self-study series “Using and Administering Linux: Zero to SysAdmin.”

Post navigation

Previous: Setting the number of desktop workspaces for Xfce4
Next: My Laptop Has No Numlock LED

Related Stories

f44-01-night
  • Fedora
  • Linux
  • Opinion

Fedora 44 Impressions

David Both May 22, 2026
programming_code_keyboard_orange_hands
  • Linux
  • Programming

Converting tabs to spaces

Jim Hall May 20, 2026
Photo by Scott Rodgerson on Unsplash
  • Cloud
  • Digital sovereignty
  • Linux
  • Open Source
  • Security

Digital sovereignty

Seth Kenlon May 15, 2026

Random Quote

Fuzzy project objectives are used to avoid the embarrassment of estimating the corresponding costs.

— Laws of computerdom according to Golub

Why I’ve Never Used Windows

On February 12 I gave a presentation at the Triangle Linux Users Group (TriLUG) about why I use Linux and why I’ve never used Windows.

Here’s the link to the video: https://www.youtube.com/live/uCK_haOXPFM 

Why there’s no such thing as AI

Last October at All Things Open (ATO) I was interviewed by Jason Hibbits of We Love Open Source. It’s posted in the article “Why today’s AI isn’t intelligent (yet)“.

Technically We Write — Our Partner Site

Our partner site, Technically We Write, has published a number of articles from several contributors to Both.org. Check them out.

Technically We Write is a community of technical writers, technical editors, copyeditors, web content writers, and all other roles in technical communication.

Subscribe to Both.org

To comment on articles, you must have an account.

Send your desired user ID, first and last name, and an email address for login (this must be the same email address used to register) to subscribe@both.org with “Subscribe” as the subject line.

You’ll receive a confirmation of your subscription with your initial password as soon as we are able to process it.

Administration

  • Log in
  • Entries feed
  • Comments feed
  • WordPress.org

License and AI Statements

Both.org aims to publish everything under a Creative Commons Attribution ShareAlike license. Some items may be published under a different license. You are responsible to verify permissions before reusing content from this website.

The opinions expressed are those of the individual authors, not Both.org.

You may not use this content to train AI.

 

Advertising Statement

Both.org does not sell advertising on this website.


Advertising may keep most websites running—but at Both.org, we’re committed to keeping our corner of the web ad-free. Both.org does not sell advertising on the website. Nor do we offer sponsored articles at this time. We’ll update this page if our position on sponsorships changes.

We want to be open about how the website is funded. Both.org is supported entirely by David Both and a few other dedicated individuals.

 

 

Copyright © All rights reserved. | MoreNews by AF themes.