David Both

7227 points
David Both
Raleigh

David Both is an Open Source Software and GNU/Linux advocate, trainer, writer, and speaker. He has been working with Linux and Open Source Software since 1996 and with computers since 1969. He is a strong proponent of and evangelist for the "Linux Philosophy for System Administrators."

He has written articles for magazines including, Linux Magazine, Linux Journal, and OS/2 Magazine back when there was such a thing. He currently writes prolifically for OpenSource.com. He particularly enjoys learning new things while researching his books and articles, building his own computers, and helping his grandchildren build their computers. He has found some interesting
and unusual ways of problem solving, including sitting on one computer on which he was working.

David has published five books with Apress. Four solo works, “The Linux Philosophy for SysAdmins,” August 2018, and a three volume self-study training course, “Using and Administering Linux — From Zero to SysAdmin,” released in December, 2019. He has also written one book with co-author Cyndi Bulka, "Linux for Small Business Owners" that was released in 2022.

David currently lives in Raleigh, NC, with his amazing and supportive wife, Alice.

He can be reached via email at LinuxGeek46@both.org or on Mastodon at @LinuxGeek46@linuxrocks.online.

Authored Content

An introduction to Linux filesystems

This article is intended to be a very high-level discussion of Linux filesystem concepts. It is not intended to be a low-level description of how a particular filesystem type…

Authored Comments

I first heard that anecdote at IBM training school in 1974. It is a good story and accurately reflects the state of many places I have worked.

Thanks for these tips. I appreciate them. One thing about writing for Opensource.com is that many folks like you are willing to share your own expertise. I will definitely try out hint #1.

As for item 2, I specifically want my create_motd scripts - and any others - available from the command line and placing them in /usr/local/etc does that because it is always in the PATH and /etc/cron.daily is not. So adding the link in cron.daily is the best way to make the script run daily - in my opinion.

I had forgotten about rpmlint and I thank you for letting everyone who reads this know about it.