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 is very interesting. Did you use something like top to see what processes were taking up the most CPU cycles? I can see that a different, perhaps more efficient, kernel could make a difference, but that sounds like a very large change in temperature.
Just for a comparison, the ambient temperature this morning in my computer room is about 23.3C and my computers - the ones that have high computing loads, are running anywhere from low 40sC to high 60sC. I run all 64-bit kernels.
Although I did not explicitly spell it out, I knew that most folks will understand that I advocate leaving computers on 24/7 to extend their lifetime.
And thanks for the information about Multics. I was unaware that they used thermal cycling to intentionally fail the unreliable components. That is a good thing to know, and especially cool coming from one who was there.
Thanks!