Slashdot Mirror
Pitfalls and Options For Business-Desktop Linux
swhiser writes "Tom Adelstein dispassionately surveys the remaining fixes that will put desktop Linux through in the enterprise. Peer-to-peer networking, functional printing, laptop support, single sign-on to Active Directory and a better Device Manager (with a driver-get mechanism) are among the things companies are asking for. He says, 'The Linux desktop could fail if companies continue to pilot programs and conclude that it's less trouble to buy Microsoft. Everyone loses in that scenario.'" Pre-loaded systems are no longer a pipe dream or an obscurity, though; read on for one reader's mini-survey of Linux systems from large computer vendors.
Acidus writes "I called around today to the big OEMs (Gateway, Dell, HP, IBM) seeing who offered systems with Linux pre-installed, and the results were good. 3 of the 4 offered Linux on workstations. While no one offered Linux preloaded on laptops, Dell has some references nn how to install Linux on their laptops, while IBM has a scattering of docs on their website about installing Linux on systems. The reps at Dell, even though they have a series of Linux workstations, had to ask me what Linux was, and how to spell it. "Is that L-Y-N-I-C-S?""
We use NIS so that workstations are completely interchangable. Had an EE harddrive meltdown, grabbed a spare machine, ran the kickstart, and the user logged back in via NIS within 15 minutes with no data loss! Could have had him backup instantly if he wanted to go to a spare office.
I can't believe how much easier workstation admin is now that we use Linux.
This way to the egress...
If you want to migrate away from windows you need to start divorcing MS. Take a look at how Novell is doing their internal migration for example.
1) Do away with office. Replace office with openoffice the desktops (still windows).
2) Do away with outlook/exchange. Lucky for novell they have groupwise.
3) Set up a CMS system (novell used thei ifolder product) which keeps track of documents the employees create. This trains the employees to go to an abstract location for all their documents rather then "my documents".
4) Set up a desktop distro with open office, groupwise, ifolder and you are done.
It could be done with small gradual steps. Novell has done it, IBM is doing it and neither one of them is a small company.
evil is as evil does
I think Linux printing is ready, but just recently. That means that things don't come preconfigured to use CUPS yet, which means there's significant setup effort.
/sys/bus/usb/drivers/usblp/*/../product, and look up the right info. Then it will look in /sys/class/printer.
The way things go with Linux is that things start out unsupported. Then they get flawed support. After a bunch of development, the right solution is made, but it requires a lot of configuration to set everything up. Then it comes preconfigured and everything just works.
(When I started using Linux, in '96, in order to get X working, you had to write a mode line with the timings you wanted to get things just right. Then X started coming with mode lines for all the nice modes. Now you don't need mode lines at all; the server will come up with the right information itself. Imagine my surprised when my new X server, with nothing in the config file other than my monitor's capabilities (old monitor; new monitors report their own capabilities), instead of coming up in 1280x1024, came up in 2048x1536 because that's what it could do.)
Today you have to tell CUPS what your printer is. But tomorrow, you won't because the software will read
The article is thinking in the microsoft way about getting drivers. Why should you have to click on an unsupported device in order to get a driver for it? Just try to use it and it should fetch (or build, or just load) a driver. If it doesn't know what the device is, it should use a cddb-like system to report the lack of support, and let users who get it working report what they did.