Every now and again with my other favourite platform someone will come along and ask "Why bother?" (usually followed by a snide remark or two). If the comment seems to be of genuine interest, I'll answer. I do the same when dealing with prejudice with the Linux platform. What I don't do is give my time to the defense of something I like, enjoy and prefer to use. I don't mind spending time when it comes to helping to inform someone about what we can do with our systems (Commodore or Linux), but I don't see any point in having a long drawn out argument with someone closed minded. I have better things to do with my time, and I've found that these remarks are often made to see how much of a rise they can get.
It's one thing to have a preference for what we like, it's quite another when we start arguing with others over which is better. This is something that seems deeply ingrained in our psyche--people argue over Republicans vs Democrats, vi vs Emacs, KDE vs Gnome, Linux vs Windows. Having a choice is important; forcing your choice onto others isn't.
Respect is earned. It isn't something you can receive by way of apology or by preaching that your OS is better than any other. Your goal should be to let others know that you use Linux, not to convince them to install Linux at their first opportunity. The reason? People who are only casually interested will be turned off with a hard sell approach. Instead, plant a seed of interest and wait to see what develops.
My opportunities to introduce others to Linux generally come in one of two different ways. Sometimes a client will be in the workshop, notice the desktop on my monitor doesn't look anything like they've ever seen, and comment "What kind of computer is that?". The other common scenario is when I am out somewhere and the conversation turns to computers.
How far I go in taking "advantage" of introducing Linux depends on what happens after the initial few moments. In the first scenario, if the person tells me they're computer illiterate and don't know a thing about them, I generally go back to work and don't worry about it. If they show an interest and mention some aspect of computing they enjoy, I'll try to show them what software I use to accomplish the same, or simply give them a brief demonstration of some of my Linux favourites. Much depends on the attitude expressed and the amount of free time I have. In the second type of scenario, I generally comment that I use Linux and wait for the response, "Oh, I've heard about that, is it any good?", and carry on from there. If the casual comment hits a nerve and the other person doesn't want to know, I don't waste any further time on the subject. On at least one occasion, this has worked very well, as a few months later the person who told me Linux wasn't a real operating system rang me up and asked about Linux software. If I had argued with them in the first instance, chances are they would have looked elsewhere for support.
Consider it against the rules to say anything against "the competition". The competition speaks for itself each time your friend has to reboot their computer or when they get the dreaded "blue screen of death". Talking down the other person's choice of operating system isn't going to endear you to them.
It's by far easier to demonstrate some of the cooler things about using Linux by actually showing your guest what can be done. If possible, try to show something that you have plenty of experience using. I tend to make use of a few of my favourite GIMP script-fu scripts, or the ability to have multiple virtual windows in Enlightenment. If it's appropriate, be sure to show how long your computer has been up without a reboot. Go with the interest of your guest--show them things they have an interest in.
If you've never used a particular type of software, now isn't the time to take a crash course. Murphy's Law can strike at any time, and it's my experience that this law is magnified ten-fold when there's someone watching what you're doing.
If asked about some aspect of Linux that you can't answer, don't try to bluff. And if there's something you really don't like, say so--first of all, it gives you credibility. I don't tell people installing Linux is easy--it may be easier with current distributions, but my first experience was a long six week learning period. I enjoy learning, so it wasn't a terrible experience, but I wouldn't call it easy either. Was it worth it? Oh my, yes.
Practical Task Scheduling Deployment
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.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- Stunnel Security for Oracle
- The Firebird Project's Firebird Relational Database
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Google's SwiftShader Released
- Doing for User Space What We Did for Kernel Space
- 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