Slashdot Mirror
Linux in the Workplace
Linux has failed to catch on among ordinary users because PC manufacturers have been prevented from offering dual-boot systems. Not only is partitioning and dual booting a little tricky, the OS CD that comes with a new PC is usually just a system restore, making it difficult to configure a dual-boot environment without messing up factory settings and file systems. Learning Linux has become an all-or-nothing proposition; in many cases the new user has to wipe Windows off his system for good or rely on a second machine just to get started.
The irony is that Linux has never been more user friendly, and the latest KDE desktop on my gentoo box is slicker, faster and easier to use than XP. It is becoming easier to be productive on Linux, and while university students have already discovered this, corporate IT departments who support a large number of Windows-only commercial applications tend to view open source solutions as a time burden (these are the same IT departments whose days are consumed with applying Windows patches or verifying license compliance).
The book Linux in the Workplace shows the ordinary user who has never laid eyes on Linux how to perform everyday office tasks. The book assumes that the user has a machine with Linux already installed and successfully configured. This book (which is more of an introduction to the KDE desktop than Linux itself) is easy and fun to read, and has lots of screenshots. Slashdotters might find this book a bit too basic, but it's the kind of book that a technophobe spouse or child or parent might love (and could very well appear under Christmas trees right beside the new Linux PC).
This book devotes a chapter each to talking about Open Office, Gimp, Konqueror, personal information managers, and various KDE office and email applications. Most of them are part of the KDE window manager or installed by default. This book walks a thin line between being too superficial for daily use and dwelling too much on the technical details. There are better books on The GIMP or OpenOffice, for example, but still it is nice to have introductory chapters in a single book. I found a few useful tidbits on controlling file associations, xscanimage, screen capturing and ark archiver. The book is not without a sense of humor. In a useful section on creating a GPG key, the book says "your passphrase should be rude or embarrassing ... using a naughty passphrase will remind you not to type it where others can see."
This book began with the mission to bring a simplified approach to Linux. By definition, it must exclude certain topics, either by design or because an application was not yet mature when the book was being written. The book scrupulously avoids a discussion of server applications like apache (which makes a certain sense), but it would have been nice to have a section on Evolution or mplayer (yes, a media player is an indispensable application for the bored employee) or ssh, cd burning programs, browser plugins, mozilla, crossover, irc or ftp clients.
Surprisingly, the book contains almost nothing about printing or how to install or upgrade applications. Because the book is intended for a newbie user, not a sys admin, it recommends talking to your network administrator about that. Cop out? Perhaps. But even the unskilled non-root user will have to install apps once in a while; the book would have been much better with a section on rpm managers and compiling programs from scratch.
From a sys admin's point of view, I would have liked to see a case study of an office that had actually made the switch. What problems did it encounter? How did the switch change business processes? What applications required the most time and energy for support? How did a Linux-only office manage domain authentication or interoperability? What system management tools made administration easier in a heterogenous environment?
The book raises an epistemological question about the best way to learn a new technology. Will a user who has never really performed tasks as root be able to leverage the freedom and power offered by open source? Will a user truly be comfortable with an operating system without first having experienced the agony of a bad install or frantically scouring the newsgroups for help ? This book presumes that a learner needs to be able to use normal applications before being ready to handle the admin stuff. The problem with that approach is that it depends on IT staff being near and ready to do some hand-holding. But Linux may emerge in the workplace not as a result of IT's enthusiasm but because of ordinary workers' exasperation with uniform proprietary solutions imposed by these IT departments.
In summary: A useful and friendly KDE-centric introduction to Linux for nongeeks. The lack of system administration material makes it probably too basic for slashdotters.
Also recommended:
RUTE Users' Tutorial and Exposition
A Practical Guide to Red Hat Linux 8 by Mark G. Sobell (not yet published)
Robert Nagle is a technical writer, trainer and Linux aficionado in Houston, Texas. You can purchase Linux in the Workplace from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
As a network admin we deploy Linux servers (Debian, thank-you-very-much) because they simply kick ass. Sendmail, Squid, Apache, FreeSwan, iptables, etc., all blow away similar products put out by Microsoft. I wish more IT people would seriously consider Linux at least for server duties.
Printing can be a huge problem in the unix world. I would certainly call the exclusion of that part a cop-out. Otherwise it sounds like a very interesting book. However, saying that KDE is easier to use and faster than Windows XP very subjective. I usually try a new version of a linux distro or two every 6 months. Sure, everything has gradually gotten nicer, and there was even a time when I thought KDE had an advantage over Windows (when it was alpha and before windows 98 came out). But time and time again, I find myself drawn back to the Windows interface. The ease of use just isn't quite on the same level as Microsoft and Apple.
I've always been surprised and even disappointed at my friends' lack of curiosity about Linux.
Linux on the desktop sucks for one reason: fragmentation.
If there wasn't a bunch of if distribution == x && graphical environment == y in the HOWTOs, we'd be much further along right now.
Even with all that cruft, the one itel holding Linux back is the file system requirements. Every mainstream consumer desktop sold these days has a hard drive installed with a 100% NTFS partition. People don't want to screw with boot managers and people don't want to screw with repartitioning.
If someone created a *free* distribution that could be installed *through* Windows on the local NTFS partition (with appropriate *free* boot manager), then we'd have a much larger installed base. Developers could start coding on Linux and distributing it with their applications.
But then there is the GPL/binary module hassle. it will never work. I'm waiting for Apple to port over to x86. I predict 2004.
Life is the leading cause of death in America.
I stopped buying proprietary ice cream from the big monopoly dairy corporations a couple of years ago and now make my own free frozen dairy product -- I call it "Iced Gnu Cream" -- from open ingredients purchased at the co-op grocery about an hour's drive down the road. Sure, driving there and back takes time, and I've had to modify an old fashioned manual ice cream freezer to make this stuff (boy, cranking that thing is an effort!).
The stuff I make is really cold, as cold as proprietary corporate ice cream, but I haven't figured out how to add flavoring unless I buy closed source vanilla or chocolate, so I've been eating it without flavor so far. But, at least, I'm not beholden to corporate America for my frozen treats. (If anyone else knows how to make open, non-proprietary chocolate, let me know, OK?)
I don't understand why everyone doesn't do the same thing.
-- Slashdot: When Public Access TV Says "No"
Don't be. It sounds to me like you have a normal and well rounded set of friends. Good for you.
If people are professionally trained on a particular tool, the benefit in paying the extra few hundred is that they will be more productive. Could they LEARN to be as productive on something else? Maybe. That'd take time. If a company is willing to invest in workers like that - essentially acting as both employer and training center - and can live with lower productivity for a certain period of time, great. Force people to use unfamiliar tools. If not, then give them what they claim they need. They are professionals, and probably have a better idea of what they *need* than you do.
creation science book
Everyone talks about KDE/Gnome as the reason to switch to linux, linux is the kernel and drivers for the hardware. Users want applications and a nice looking desktop, eyecandy.
Personally, I like XP as my gui, and Linux as my server and extension to my workstation. I use my linux box as resources for my windows box. Mount shares, Run services, shell with command line tools, keep tasks running in the background while I play video games on my windose box. (Keep IRC open in a shell with irssi)
I really dont understand why people dont use the best of each platform. Have the best of both worlds, the power of applications (and GNU utils/commands) on a *nix box(bsd or linux) and the anti-aliased fonts/games/apps of windows. (Sounds like OSX, doesnt it...)
But if you only have 1 Box, XP+Cygwin seems a better option for now. KDE/Gnome/Openbox are still lacking in areas, and windows programs wont run native. Repeat, im not bad mouthing linux, linux is a great OS. The Gui KDE, and Back end Xserver is missing features, 3D features, Anti-aliasing, advanced hardware features. But the command line gnu tools, and opensource applications are great. I'm sure with time, linux will be the better choice for a full time os, but gui and applications support needs to be there.
-Brook
-
Blackbox 4 windows an alternative to litestep.
sed awk grep cron sort ftp smb etc.
I can make a shell script in about 10 minutes that will do, in a matter of seconds, something that a human would take hours to do with their favorite GUI app. I rarely run Linux X apps. I do run X apps exported off unix servers on occasion, but the real power of Linux is what I mentioned above. Plus, I don't need to worry about, or even have, an X display driver. We have New Fangled windows-based systems that simply have no way of doing these rudimentary, STANDARD functions (outside of purchasing $$$ or building $$$ specialized apps).
"Would it kill you to put down the toilet seat?" -- Maya Angelou
It's not there yet.
All of my servers are Linux, and they do great. In fact, I'll turn 1 year uptime on them next week. However, I don't think Linux is ready to be on my desk at work.
Every once in a while, I get this urge to try to dump Windows altogether. I've tried it several times now, but I keep coming back to Windows because of apps like Photoshop and Trillian, and the solid UI. There are X equivalents of most apps, yes, but they just aren't the same, and I'm not as productive with these as I am with the Windows products.
Most Linux desktop apps have not been very stable for me either, and what's worse, they don't FEEL stable. MS Windows has a very solid, polished feel to it. They've dumped tons of money and hours into useability, and they have alot to show for it. I think Linux will get there (its come a LONG way already), but for me, its not there yet.
Last time I ran a Linux desktop, someone asked "why are you running Linux instead of Windows?". I really couldn't come up with a valid answer for him, other than "I just want to!" or "I hate Microsoft!".
The bottomline is, right now I'm the most productive when working from an SSH session on my Windows desktop.