Find a location that is well-known in your area and has plenty of parking. Be sure it has plenty of space and sufficient power sources. An added plus is having carts available to help people bring in their machines.
Host a DemoFest at a meeting about a month ahead of time to generate interest and recruit help.
Publicize in the education community (universities and secondary schools) and computer stores, libraries and major corporations (flyers and brochures in the cafeteria or break room). Ask about advertising on local cable access television and community calendars in newspapers.
Study the Linux Hardware Compatibility FAQ and the Linux Hardware Incompatibility FAQ and bring copies for your workers.
Practice installing Linux on a low-end PC to measure the amount of time it will take to complete. Do the same on a notebook computer and over a network (if you plan to offer this option).
Ask companies in the industry for CDs, literature and other items to use as giveaways.
Ask attendees to make a reservation in advance, stating the type of PC they will be bringing. Prepare for some to turn up without reservations.
Have an area at the front door for signing in and giving away promotional material.
Plan on giving all users a Linux CD, so they can distribute Linux to others.
Have random giveaways of books, T-shirts, etc.
Include Linux training seminars presented in a separate room.
Be kind to your workers. Have water and drinks handy. Order in lunch. Make sure they take breaks.
Bring a box of extra parts that people no longer need—you may need them to complete an installation.
Bring a camera.
—Michael Roberts, Cincinnati GNU/Linux Users Group
Melissa—Explore.zip—Back Orifice. If you think there has been a bad rash of viruses and crack attacks lately, you're right. And security experts say it's going to get worse, not better; the frequency of crack attacks is rising exponentially. So are the money losses from the problem. Computer Economics, a research firm in Carlsbad, NM, reports that American businesses lost $7.6 billion US due to software viruses during the first half of 1999—more than in all of 1998.
Curiously, the massive mainstream media coverage of these incidents completely fails to mention the one thing they all have in common: Microsoft Windows. Non-Microsoft operating systems such as Linux are invulnerable to macro attacks, immune to viruses, and can laugh at Back Orifice.
This simple fact explains why your Internet service provider never suffers from viruses; essentially all ISPs run their services off UNIX boxes, and about 40% of them run Linux. Evidently, businesses are finding this an increasingly attractive option; a recent Computer Associates survey reports that 49% of information technology managers describe Linux as “important or essential” in their enterprise plans.
One of the reasons for this trend is definitely security. Anyone running a Microsoft operating system on a machine visible from the Internet is just begging to be cracked. If you're concerned with computer security, you need to understand why—and why Microsoft will not and cannot fix the problem.
Linux and other operating systems like it were designed from the ground up to be used by several people on the same machine, and to protect those people from each other. The user interface of Linux is separated from the kernel, the privileged operating system core. And the kernel is carefully protected from being modified by ordinary programs. This is why Linux doesn't get viruses.
Microsoft Windows, on the other hand, has a one-person-per-machine assumption built deeply into it. There is no internal security, and the Windows kernel is not protected against being modified by user programs. In fact, the user interface of Windows is wired right into the kernel. This is why hostile programs coming in over an Internet connection (such as Back Orifice) can reach right through the user interface, deep into the operating system core, and infect it.
If you value your data and your privacy, you need to understand that Microsoft cannot fix this security hole. Too many applications (including Microsoft Office and the IIS web server) actually depend on the lack of security in the system. Furthermore, the fact that the source code for Windows is closed means it never gets properly audited for security problems.
How does Microsoft deal with this? Not well. Mainly, they tell lies and try to confuse the issue.
On August 3, 1999, Microsoft put a machine running a beta of its new Windows 2000 operating system on the 'net and challenged crackers the world over to break into it. A few hours after the announcement, the machine crashed. Microsoft spokespeople subsequently claimed that it had been brought down by electrical storms.
But the machine's own error logs showed there had been nine crashes due to errors in Microsoft's own software, not the weather. Furthermore, crackers did indeed get in and alter a guest book application during the short time the machine was actually up—a fact Microsoft tried to dismiss as irrelevant.
A few hours after Microsoft's challenge was announced, a Linux company in Wisconsin matched it. During the following three days, their Linux machine withstood 6,755 attacks without crashing once.
Which system would you rather trust your critical data to?
—Eric S. Raymond
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
- Interview with Patrick Volkerding
- Tech Tip: Really Simple HTTP Server with Python
- My +1 Sword of Productivity
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SuperTuxKart 0.9.2 Released
- Non-Linux FOSS: Caffeine!
- Returning Values from Bash Functions
- Managing Linux Using Puppet
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