Recently, VA Research bought the linux.com domain and hired Trae McCombs to be the site manager. I talked to Trae on April 1 to find out his plans.
Margie: Tell us how you came to work on the linux.com site.
Trae: I am constantly amazed I have a job at VA Research. I never graduated from college and I spent four years in the military. At one time, I even had a climbing guide service and taught climbing. In March of 1995, I bought my first computer. I ran Windows for about a year and discovered very quickly that I wanted something else. Then I saw a screen shot of Linux—an old version of Enlightenment called FVWM-XPM—and thought, “I wanna run that!” I actually started running Linux because it was pretty!
Margie: Now that's a Linux story I haven't heard before.
Trae: I know! That was September of 1996, and getting started was pretty hard for me. I think I was the first non-geek, non-technical person to use Linux. Other users told me about RPM and configure->make->make install. I have no programming skills—I couldn't code to save my life!
Margie: So what are you doing working for VA Research?
Trae: That's an interesting question! They hired me for this position because of what I did for the themes.org site. I talked to all the major window manager authors about setting up an official theme site for their window manager. After getting their approval, I started building this huge themes repository for the Linux community. I couldn't have done it alone—I built a staff of about 18 volunteers who I managed. I think Larry Augustin was impressed with how I managed that site, and that's why he hired me.
For linux.com, I'm using that same model. To develop the web site, I have 13 volunteer staff people, and I'll probably scale up to 20 or 25. It's so easy to get people. This type of community involvement is what drives Linux and the Linux kernel. Linus said, “Hey, I can't do everything on my own. Let's bring in other people to do it.” I am using this same model to build linux.com.
Margie: Tell me about the site.
Trae: linux.com is going to have a broad scope. It is going to be the quintessential Linux portal. When people hear about Linux, they will first go to linux.com to look for information. The press will also be able to get various tidbits of information they need. Phil Hughes is on our advisory board—we can't go wrong!
On the home site, there is going to be a huge “What is Linux” button. All around the button will be editorials, interviews, various other content and links to different things. A button bar at the left side will be totally configurable. People will be able to add links to their favorite places to the button bar. No one is doing that—others are just including everyone else's news. To me, this takes away from the experience of actually visiting other people's web sites.
The main feature is the “What is Linux” section that includes three areas: corporate, new to Linux and new to computers. When a visitor clicks on one of these areas, he will be walked through a “power point-esque”-type presentation, as opposed to a text FAQ. It's not going to be a full multimedia experience, but it will be very clear and concise, and at any time, a jump can be made to another path or presentation. The layout the staff is working on is very graphically pleasing, and more is yet to come.
Margie: Other sites do this same sort of thing. What exactly will make linux.com unique?
Trae: We will have a chat section off the main page where people will be able to get tech support from the community. No one does that now. Everyone else offers e-mail or other types of support. We'll have a “Talk with Linux Users” button where it will be easy to find. With just a click, they will be talking to other Linux users and finding answers to their questions. The only reason I am running Linux right now is because the Linux community is so open-armed and willing to help. They spend hours on IRC—countless hours—helping people like me. That's an invaluable resource.
Margie: Yes, it is. I'm always amazed how many people seem to have the time to do that. So, the chat space is why people will come to this site?
Trae: People will come because we are linux.com!
Margie: Oh, because of your name!
Trae: Yes, the name has power, lure—it is the main reason all those other people wanted this domain.
Margie: When do you expect linux.com to be up?
Trae: May 18—the start date for Red Hat's Linux Expo in North Carolina. I wanted to launch it at a trade show, and Linux Expo seemed the right time.
Margie: I'll be at the Expo this year, so I'll see you for the announcement. Any comments about linux.org?
Trae: My hope is that when we bring out this truly awesome site, linux.org will say “Okay, that's great! Let's one-up them.” Then we'll say “Oh, wait a minute—let's one-up what they've done!” Guess who wins this game of “one-up-manship”? The users!
Margie: That is certainly a great attitude. Any closing thoughts?
Trae: As long as the Linux community wins, there will be no fracturing. We will never have hard feelings towards any site. I want to see Linux win. I'd also like to thank the staff and the rest of the Linux community who helped get us here.
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!
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
- Doing for User Space What We Did for Kernel Space
- Google's SwiftShader Released
- Parsing an RSS News Feed with a Bash Script
- Rogue Wave Software's Zend Server
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