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 Comments
That would be one part of a more comprehensive approach because it only ensures that journal entries stored in memory don't get lost when the host is powered off. I am glad you mentioned it, though, because I will be sure to include that option in my article. I am working on it now so good timing.
It is possible to send journal entries to STDOUT as well as to the journal itself. I have not tried it but I would imagine that could be redirected to an email. If you try that, please let us know how that turned out.
Thanks!