Looking into the Future
Here are a few examples:
Decus invites Linus to speak at their conference in New Orleans.
The Australian Unix Users' Group invites Linus to speak at their annual meeting.
Linux Journal has a booth at Unix Expo and gives out 3,000 copies of the magazine.
PC Week names Linux as software Product of the Week.
Rumors are that HP, IBM, and other big names are using Linux internally.
I went into three mainstream computer stores and said I was looking for a laptop to run Linux. One store didn't know what I was talking about. Another suggested a particular system because it had a larger hard disk which would be good for Linux. The other told me that the laptop they sold didn't run Linux (they had tried it), but suggested another brand that did.
Companies such as the Roger Maris Cancer Center and Virginia Power port applications from commercial operating systems to Linux and explain that they did it because they needed something “better”.
Open Systems World, in its sixth year as a Washington, DC, based trade show decides to have a Linux Conference right along with the SCO and Solaris conferences.
Unix Expo contacts Linux Journal about doing a Linux section at their New York show in 1995.
Because these aren't “Linux events”, these are cases of the “real world” showing an interest in Linux. At the beginning of the year, mainstream computing hadn't even heard of Linux. At Uniforum in March, Linux Journal had a booth. Although the booth was very popular, the most common question was “What is Linux?” Today people seem more likely to ask “Why should I run Linux?”, and then actually listen to the answer.
Now comes the assignment. If we want people to take us seriously we need to give good answers. Yes, Linux is a fun “hacker” system. But some of these people want to do real work. We need to listen to their needs and either explain how Linux can meet those needs or, if it can't, tell everyone who is interested in development what these people are looking for.
And this is where Linux Journal can help. Let us know what people are asking for and we'll help get the word out.
To start off this effort, here is an idea I am working on—a Linux-based “freenet” system. For those of you not familiar with a freenet, it is a public-access computer system designed to offer communications within a local community. Access is free, users are generally not computer oriented and much of the information on the system is supplied by local volunteers.
Current freenet software has a lot of shortcomings which include being inefficient, not particularly user-friendly and generally running on expensive hardware. Combining the openness and capabilities of Linux with this movement could offer a much better starting point for these freenet projects. And implementing a freenet on Linux could help us spread the word on how useful Linux can be.
In future issues of Linux Journal I want to explore the current limitations and see what Linux can offer in the way of a good base for the freenet of the future. Again, your input is welcome. If you want to get involved, write me via Linux Journal or e-mail email@example.com.
Phil Hughes is the publisher 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!
- SUSE LLC's SUSE Manager
- 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
- Doing for User Space What We Did for Kernel Space
- Parsing an RSS News Feed with a Bash Script
- Rogue Wave Software's Zend Server
- SuperTuxKart 0.9.2 Released
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