Remembering Bruce Steinberg
I've known Bruce Steinberg since we met online, so long ago I don't remember. I'm guessing it might have been back when SCO was still a leading Unix company and Bruce was its VP of Marketing Communications. Or it might have been through Usenet, or some other pre-Web online service.
We always had so much to talk about. We were both tech geeks from New York who grew up in the fifties and shared interests in radio, photography, music and technology — to name four topics at which Bruce was far more knowledgeable and accomplished than I . That's not idle flattery, either. Bruce was a ham radio operator for so long that he had a four-letter callsign: N6LZ. He was a musician and photographer with a long list of credits at both.
And, of course, he was a techie of the first water. In addition to his radio work and his decade or more at SCO (their best years, from '83 to '93), Bruce was a PCM Telemetry Field Engineer for the Apollo Program at the Kennedy Space Center and a Quality Assurance Engineer for the Mariner Mars Program at Berkeley's Space Sciences Lab. That was back in the '60s. Before that he got his BEE at Cornell, where he also rowed on the varsity crew team. And after that he was a performer and photographer working in the music industry.
Bruce was my best reader. I can't think of anybody who would contribute more interesting, useful or frequent responses to my writing here in Linux Journal (or in my Suitwatch newsletters, or in my blog). Every few weeks or months I could count on a beautifully written email from Bruce that would be thick with facts, lore, wisdom and experience. I often encouraged Bruce to write for public consumption, because he was a terrific writer, and it would have done the world good to share the wealth of Great Stuff that he lavished on his correspondents. But that wasn't his style, and it was cool.
We always talked about getting together, but never did, and now I regret it terribly. Because I got an email this morning in which Bruce Steinberg was the subject rather than the source. It carried news that Bruce is gone. He died early yesterday after a brief illness at age 64.
I've been looking around the Web for some of Bruce's footprints. There are lots of hints and fragments... a posting about Tower of Power to rec.music.bluenote, a thread on Steely Dan in the same group, a thread on calendars and old gear at rec.ham-radio, a posting on vanila extract at rec.food.cooking...
I'm sure many readers also knew Bruce. I hope some of you will fill us in on some links and recollections of one of the most enjoyable and excellent human beings we've known.
Doc Searls is Senior Editor of Linux Journal
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- Google's SwiftShader Released
- SUSE LLC's SUSE Manager
- Interview with Patrick Volkerding
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Tech Tip: Really Simple HTTP Server with Python
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide