Desktop Linux Sliding in Under the Radar? 742
Paul Johnson asks: "This article at ComputerWorld describes a sysadmin's discovery that many people in his company are installing Linux on their desktops without consulting IT. The writer is concerned with the security implications, but there is a wider issue. At present the 'official' penetration of Linux into the desktop market is something around 1%. The writer of this article doesn't give figures, but it sounds like he may have stumbled on several times that percentage of desktop Linux installations. If so then this is an important trend. Linux got its foot in the datacentre door in exactly the same way a few years ago, with unofficial installations doing odd server jobs.
If you are a sysadmin, in an organization that runs Windows on the desktop, have you stumbled on many unofficial Linux installations?"
This is unexpected? (Score:1, Interesting)
Undercover LINUX (Score:5, Interesting)
VMWare rules! (Score:1, Interesting)
excellent application that runs in Windows and Linux and fully virtualizes
the hardware. You literally "switch on" a machine in a VMWare window and
you see a BIOS startup and then your favorite operating system starts.
You can do things like run Linux as your main operating and have Windows
as a Window within your window manager. Or you could run Windows as your
main operating system and have Linux in a window. In addition you can have
multiple versions of each OS. I have, for testing purposes, Windows 98,
Windows XP and RedHat Linux as VMWare images, at any time I can boot into
a clean version of them and test software. At the end of the session VMWare
asks me if I want to save the changes that have occurred in that session. If I
say "no" then none of the changes get committed to disk. For Windows that means
even the registry, so I am guaranteed a pristine environment next time.
At my company about 25% of people run Linux as their desktop with Windows in a
VM and the others the other way around. It's very cool...
John.
Unofficial installations (Score:5, Interesting)
desktop installations. While I was pro alternatives to Microsoft, there was the concern about security - e.g. open e-mail relays, unpatched servers. The company ended up with a policy of permitting Linux on the desktop, but not supporting it. If you had an application issue - you were on your own. The only users that ran it had a clue and we didn't run into issues. Being a research environment, Linux ended up replacing SGI systems as the scientific workstation standard.
Nope, not here (Score:4, Interesting)
back in the old days... (Score:2, Interesting)
I don't have any figures for you though.
Don't reinstall - boot linux from another disk (Score:5, Interesting)
I DO, however, frequently boot my machine with knoppix [knopper.net]. Most corporate IT environments prevent users from installing their own software - but Knoppix has pretty much every app I need. I sacrifice local file storage and some embedded data like PIM stuff, but its just more comfortable and doesn't raise the ire of the lesser IT geeks.
Does this count? (Score:5, Interesting)
FreeBSD 4.7, autostart XFree86,
full-screen RDesktop to central Win2k Terminal Servers.
User's still think they have a windows
box(windows splash screen on boot).
Does this count?
Re:Don't reinstall - boot linux from another disk (Score:5, Interesting)
The question is printing.
Article is refreshingly good (Score:2, Interesting)
(and I say this as someone who's worked in IT, and managed IT departments, for _years_.)
Re:VMWare rules! (Score:3, Interesting)
However we didn't blow $400 on VMWare we needed it. Our product runs cross platform on Windows and Linux and wanted a way for the developers to be able to use both cheaply. Dual booting isn't an option because it's very slow to change context and you don't want to have two email clients, etc. to manage (or only be able to check email etc. when in one operating system), two machines was too expensive ($400 is a lot cheaper than a second PC). So VMWare was the answer.
We blew the money on two 19" flat screens per developer.
John.
backbone isp (Score:1, Interesting)
Re:they better not (Score:1, Interesting)
jesus fucking cyberfascist punk (Score:1, Interesting)
Sick of stupid ass admins who think that they are important. Without users, we would NOT have jobs...
Re:they better not (Score:5, Interesting)
Oh, for the miniscule number of Linux viruses?
no agents for our desktop license management
Since *most* software that requires license management is either Windows-only or hard for Joe User to come by, I don't see this as a huge problem either.
and almost certainly wouldn't be keeping up with security updates.
Ah, now this is a real concern. I would hope that your company has firewalls, but I can certainly understand not wanting them to be your *only* line of defense.
the users don't own their machines - the company does. if they want to piss around with _any_ os, let them do it on their own time, on their own network, and on their own equipment.
I can certainly understand this. When you're responsible for eleventy jillion desktops, you can't have people going rogue on you. At least not without knowing that if you have to come fix their PC, it's getting reimaged.
Now, I personally happen to run a stealth RH install, dual-booting to Win2K for when I just have to do something in Windows. My workstation, however, is well-secured, and has updates applied regularly. I have *never* had to bug the IT department, and my workstation is exceedingly well-behaved on the network. If the IT department decide to be real hard-asses about it and reimage me, I'll understand. Doesn't mean I won't be cranky, though.
Re:Does this count? (Score:3, Interesting)
Just curious, I did a big NT 4 terminal server install once and it was one of the more challenging times in my life. Hard, it was, and long. Win2k is supposed to be much better, but is it really worthy (stable, etc.) of a thin client environment?
I'm under the radar (Score:4, Interesting)
I've been here 3 years. Last year and the year previous to that, all of the IT web pages said that the only officially supported OSes were Windows and MacOS, with a stern implication that that was it (and don't you think about using anything else, grrr!). This year, they've acknowledged that Linux exists, and are giving some support for it. The IT folks are at least aware of Linux now, a change for the better.
Why is this happening? Because there are a few researchers (including me) who have installed Linux on their desktop/analysis machines, and are doing their own system administration. But, these users still need to fit into the global IT picture, for example, communicating with the email servers. As we have migrated from one email system to another recently, the IT folk have visited every single user (no, not kidding) to move their email system over. The fact that I was running Linux was not only no big deal, but they even correctly guessed which mail client I was using, given that I was running Linux. We are, slowly, winning.
From a security viewpoint, installing MSFT (Score:3, Interesting)
Re:Nope, not here (Score:1, Interesting)
Uhh, I'd hope a hospital had some technically inclined people in it. I mean, You don't hire a bum off the street to run an MRI machine, or replace a spleen or something.
It probably doesn't count, but (Score:3, Interesting)
As part of my job I set up the office G4 (OS X...which they thought was Linux... probably because of Smb) for training... I am in charge of Apple desktop support for our largest client in the area, an HP 9000 D class for my support of the 9000's in the data center (24/7 on-call), a Windows 2000 AS box for training (Citrix Metaframe XP, etc.) and the box I interface it all with... my Powerbook Pismo. I was told to shutdown and remove these from the network... they have a point about security holes and unauthorized access points...but I kind of chuckle because their infrastructure is very poorly built and my machines are 10 x as secure as theirs (case in point I run only SSHd for the most part and lock down everything)
They decided to send us a switch and give us an external IP... (IP only after bitching that a lab environment is useless without an internet connection) which is fine except we can't use the local printers... so instead I built a NetBSD firewall and put everything us techs use behind it and then configured it to never respond to any outside services nor pings. So yes I have unofficial non-Windows and technically oriented OS's... and I had Gentoo Linux on my last laptop... but I probably don't count because I am an admin just not by job this time around (I've been director of IT before)
Re:IT headaches (Score:5, Interesting)
I work for a company that was heavily Unix (and X-terms) until the LAN somehow became all MS PCs. Now people and projects are insisting on replacing not only MS but Sun and SGI stuff with Linux. We are meeting heavy resistance from IS.
They are claiming that it costs more to administer a Linux box, even though we've been in meetings and showed that it wasn't true, based on recent experience. They refuse to give even knowledgeable users superuser privileges on their own machines, although Windows users can install anything or delete everything on their boxes at will.
To me it appears that some of the people in IS are afraid of being made less powerful, less needed, and less relied upon.
First thing I did (Score:3, Interesting)
Months later, I walked away after initiating an (infrequent) reboot. After making the rounds, I came back to an NT login. WTF I thought - then realized I'd set NT as the default in lilo in case someone needed to use the copmuter.
Inside HP... (Score:2, Interesting)
FreeBSD Under the Radar (Score:3, Interesting)
But IT doesn't know about it. I don't have their permission. But guess what? IT doesn't own this computer, my department does, and I got my boss's permission, his boss's permission, and the permission of the VP above him. I would have told IT, but then they would have a cow and it would become a big pile of political crap. But IT doesn't know, so they're happy, I'm happy and my boss is happy.
I'm certainly not going to tell them about the development lab being switched over the FreeBSD, the Dicom lab running Mandrake, or any of the internal websites running Redhat and SuSE.
Re:Remember... (Score:4, Interesting)
I'm not a sysadmin, but I'm one of the people that has installed Linux (I didn't blow away the corporate windows install, for accounting sakes) on his own at work.
How did I get the corporate mail client (MS only) and other ends to work? I downloaded custom-wrapped wine rpms created (on their spare time) by other coworkers on the other side of the country at another research facility. This was hosted on a un-official internal "Go Linux!" website, for all of the company's employees to see (we're allowed to have personal and "club" websites) and download (they have all of MS Office 2K running smoothly, along with Notes, the corporate e-mail client).
I got a couple of coworkers excited about Linux -- mind you, we're not just another corporate center, this is a hardware R&D filled with geeks (the sort of people that aren't sysadmins, but might play them on slashdot!) so I imagine we're at one end of the scale in the corporate world. But, thanks to Knoppix (try out a recent Linux distribution with zero liability on the company's computer to see if all your stuff is recognized! What a sale!) I've managed to get even some of the "old crusties" excited about Linux.
Anyways, my sneaking suspicion (and my hope! so this probably biases my "suspicion") is that there is a large number of uncounted Linux installs, and growing.
I was concerned about security, but who are we kidding? I know to not rest on laurels and all that (keep this RH73 as up to date as possible), but the alternative for my machine is Win2K, and we've been through the wringer with updates, worms, reboots and virus infected computers on *that* platform
Bull cocky times five (Score:3, Interesting)
Dont install KDE? For a user? are you expecting them to use X? or maybe the CLI? or should i dictate them to simply use my preferred manager? Once again... poster said these would be boxes i didnt set up.... so theyd probably install whatever they wanted. Support contracts are certainly cool... but even still... my job is to fix things quickly ... not to wait on the phone.
if you think supporting linux amongst a bunch of users looking for ease of use and smooth inter-operability with a windows world (especialy in sales and buisness app's) your out of your freaking mind. While i certainly do agree ssh is a powerfull tool for remote support (though i prefer VNC) your totaly missing the point.... resolving issues QUICK. the amount of variables involved with a *nix are much greater than windows.... this is the power of *nix. And also why support can be problematic.
As to your "no" policy... i seriously laugh at you. If your in the buisness of shooting down your users ... your not a very good sysadmin. While you most certainly shouldn't encourage or offer active support for non-approved SW... Users are users, and simply want their shit to work. The more you can facilitate that with ease the better the admin you are. thats "support".
People who hold the above attitude are very BAD admins.... our role in general is to make people happy as best we can without going over-board. I suppose that's why my company has gone through 8 admins until they found me... your job security is BASED upon your user satisfaction. In which case ease of support IS important.
where I work (Score:4, Interesting)
The home office has a special network security "swat team". Last year, they did a security audit of our site, which consisted of trying to hack into our network, from the inside.
They found several rogue Linux boxes, and were able to hack into them through ftpd. Holy hell was raised. All Linux was purged from our network. Oddly enough, here it is, 8 months later, and nearly every developer has a second box on his or her desk, with, you guessed it, Linux. However, it's a distribution and configuration, approved and controlled by IT.
It's all about control with these guys. .
You'd think that black leather keyboards with spikes and clamps would be popular with these freaks.
Re:Ignoring the standard MS shot... (Score:4, Interesting)
i have a local gentoo build server with 2 python scripts, and some cron jobs my systems are updated daily on my home network (14 machines. varying from athlons, to mips, to alpha) (not running gentoo on the mips, that runs irix [octane])
Re:IT headaches (Score:2, Interesting)
Re:Remember... (Score:1, Interesting)
i work for a large bank in network administration. of 350 users at our site i am the only one to install linux. on a laptop. my boss showed me a memo that forbid installing linux because it was a hacker os - i shit you not. this was a couple of years ago, i think it was redhat 6.0
so i installed freebsd
when our shitty ms dhcp server stopped handing out ip addresses for two subnets i built a freebsd dhcp server but was never allowed to implement it
dumbasses
Re:I work for M$ (Score:1, Interesting)
Strange but true.
Underground network (Score:3, Interesting)
Total FUD, par for the Computerworld course. (Score:4, Interesting)
The weaknesses from the rogue installs ...come from the installation of third-party applications and utilities, which can leave a desktop or server vulnerable to attack if set up incorrectly.
Huh? What total Microsoft brain washing! What is a "third party application" in the free software world? This dude has his head shoved so deep into the M$ world that he confuses all the crap and spyware that accumulates on windoze boxes and runs as root with free software. I don't know how he's transfered his complete lack of control over Windoze onto software that works. I don't get it.
He goes on, after mentioning that he might be man enough to run Red Hat. He thinks it could do his company good to replace the hideous pile of Word Docs that is their QA tool because it sucks to have to do a "word search" to find information in the 300 reporst/year they generate. So true, just putting those things on a Samba server so you can use grep and find would be really helpful. Imagine how nice his life would be with a nice little mySQL/PHP webform for entry and search instead of a Word template. Progress, forge on brave man!
But, oh no, he shrinks from the fear of vulnerability:
For example, there always seem to be vulnerabilities associated with programs such as file transfer protocol, sendmail and Apache. And other open-source software is vulnerable, especially when the developer hasn't written the program with security in mind.
Poop. Plain and simple poop. Sendmail handles most email. Apache handles most web sites. Who needs ftp when you've got ssh? Well, anonymous ftp is a nice way to share big piles of files and programs like proftp are plenty secure. This is total shit to scare people who don't know what file tranfer protocal is, but like the ease of windoze file sharing. It's ignorant if not intentionally misleading. This line says volumes:
We can't eliminate Linux
No, but some fools wish they could. Other people everywhere are learning all the good things free software can do for them.
Anyone who's worried about security should use Debian's stable distribution. Not only is it all field tested, upgrades can be applied everyday from http://security.debian.org via shell script. Unlike the windows world, these updates install easily and don't break other "third-party" applications.
You say:
This could make the case for desktop Linux look worse, if people are not securing their dektops and/or keeping up with security updates.
That seems to be the intent of the article. Fortunately, only the very ignorant will pay attention to such nonsense and it can easily be deflated. Microsoft is going to have to try much harder than this to keep people away from superior software. Then again, I'm not sure how they can do that. The thing that makes the best case against the Windows desktop is it's record. That now including the author's laborious treck around his company caused by yet another Windows failure. There is not software anywhere with such bad performance.
Re:Ignoring the standard MS shot... (Score:3, Interesting)
When they connect that second device to their stealth hub or switch, your switch will cut them off (Seeing a second connected MAC address disables the switchport).
Re:This is unexpected? (Score:5, Interesting)
From a personal perspective, my previous employer didn't give a rat's ass what OS I ran, as long as it ran the software we used. The reply I got when I asked if I could was something like "oh sure, but you do it on your own time, and if it breaks, don't come whining to us..."
Re:This is unexpected? (Score:1, Interesting)
hrm... stumbled... not exactly... (Score:2, Interesting)
We used to be a windoze only shop... (Score:3, Interesting)
I hope to have the whole company converted by christmas!
Re:Ignoring the standard MS shot... (Score:2, Interesting)
Re:Not exactly ... (Score:5, Interesting)
WinXxxx Only Option on IT Forms (Score:3, Interesting)
Running FreeBSD as the primary and only OS on three machines at work, I have a really hard time with these forms. What further investigation revealed (as I wanted to give them the CORRECT information despite their problematic form) was that their bonehead Access database required a primary OS from the list, with an optional secondary OS from the secondary list - no other options could be entered. So my three computers were registered as Win 2000 primary OS and Linux for secondary OS. Despite repeated pleas by me, we're paying Microsoft for three unnecessary liceses.
What annoys me most is that when ever I say "FreeBSD," my supervisors always hear "Linux." They aren't against Linux (or FreeBSD for that matter) as it seems many of your bosses are. Linux is a keyword in marketspeak, so it's acceptable. When asked about why they hear "Linux" when I say "FreeBSD," I was told that the "Free" in "FreeBSD" makes it sound cheap (in quality) to administration and potential customers. Using it is OK, but not to the outside world (or department).
Talk about hitting the nail on the head (Score:3, Interesting)
All worked beautifully until IT migrated to Active Directory and EVERYTHING stopped working. Well, actually only the shares and Outlook stopped working, but not having email is enough to end my Linux using days. IT wouldn't help at all on the AD server so my options are running low. SCO actually has software that would help, but I shiver at the thought of using a SCO product.
IT is now going to open up Outlook Web Access... I thought this would solve everything, but they are somehow locking it down so every client that connects to OWA will need to be running some sort of Windows-only Symantec software (we also use a Symantec firewall... maybe this is some sort of PPTP client, but IT wouldn't say). This makes me doubtful of getting it to work under Linux unless I can emulate the Symantec software.
Where I am going with this is that I used Linux on my work desktop for two years and some helpdesk guys even knew about it, but I was out on my own when IT went to AD, so this sort of thing sure isn't going to get any support from many IT departments. Good luck to you in running Linux at work. I wish I had more luck.
Re:Not exactly ... (Score:1, Interesting)
Parent post is overrated nonsense, with some FUD thrown in for good measure. While there are some valid reasons for unifying desk tops (easier maintenance), msot points mentioned were not amongst them. The right option is to say "ok, you run it but we won't support it", not "no you run Windows as its secure".
Re:Not exactly ... (Score:5, Interesting)
I guess my point is that it is not so much what os a person runs as it is the IT policies and how well they're enforced. Keep up with security patches, don't install untrusted software, good password policy, etc. These things aren't unique to any particular desktop OS and any user could potentially violate them. However, any user that depends on their system for everyday tasks isn't going to intentionally munge it up since they lose the use of it while you may be inconvenienced with rebuilding it. There is always the danger of the 'malicious insider' and we risk it every summer with an influx of student help that always includes some idiot that will try 'bad things'. Deal with them swiftly and harshly and make sure everyone knows about it and you can keep it to a minimum, but you can never eliminate the risks completely.
Re:This is unexpected? (Score:1, Interesting)
i worked at a large e-commerce site, and one of the credit-card-fraud cases i worked on occurred because of a corporate key-logger captured someone's information when they placed an order at Amazon, and unfortunatelly the company didn't keep their keylogs secure and the credit card #s of people who used work computers for e-commerce were stolen.
IMHO it's very important for employers to let people know that such logs exist and that any credit-card-numbers typed on such computers may be compromised.
The head of CSFB firewall team did this... (Score:1, Interesting)
Now this is a big bank, with thousands of desktops, and very strict policies on what you can run on your desktop (ie: you can run the heavily modded and locked down corporate build of Windows 2000, or you can work elsewhere), and this guy, global head of one of the two network security bits flaunted the rules - talk about setting an example.
He ran VMWare [vmware.com] on his Red Hat box, and had the corporate build of Windows 2000 running on that.
He took great delight in quietly telling the story that he ran up Red Hat, and ran up the virtual machine with the corporate build on it and asked the 'corporate build' team to check it out and tell him if they found anything up with it. They didn't.
When you consider that around 50% of this particular corporate's network security is in the hands of someone who behaves like this, you start to wonder how secure some of these large corporates can possibly be!
Re:Not exactly ... (Score:1, Interesting)
Supposing IT is not full of Linux specialists, they would need to learn quite a lot about Linux, take courses, hire more people etc. etc. If you are just managing to control your current 1000 - 8000 or what ever number of desktops, you do not want to make the extra effort without pretty good reasons. Given that the current staff probably knows Windows but not Linux, it would be pretty difficult to find these reasons.
It's a bit different thing to have Linux servers (maintained by your trusty Linux knowledgeable part of your staff) on your network than to have (by definition) inexperienced users try and install Linuxes all around your network.
Also, the above does not necessarily apply to your average University etc. With corporate IT, it would be more like this...
Re:Not exactly ... (Score:3, Interesting)
In that situation, you're not in the business of running a computer network, you're in the business of supplying electronic stationery. You could theoretically replace every machine with a green screen terminal linked in to a big ol' mainframe, and productivity would barely dip. (okay, in some graphics-intensive environments, such as engineering drawing, laying out newspapers, etc., maybe you'd have to use X terminals, or similar, but the effect is the same).
There are situations where the computers on desks aren't just document-editing dumb terminals, though. They are genuinely used by the employees who work with them as general purpose bits of hardware that help them solve problems. Research groups, software developers, tech support shops, labs, hell, even creative places like design studios, visual FX teams and so on. In shops like that, you're supplying every user with computer equipment to help them do their job. If they want to replace the OS to do their job better, woe betide any sysadmin standing in their way. If an ad agency's client wants a particular visual effect, and the cheapest way to do it is to install Linux, so you can run some bit of software off sourceforge, then you're not going to make yourself popular if your first reaction is to cut the guy's network access off mid download, and send down the two heaviest helpdesk guys to cart the computer away.
I worked for a long time in a company where I felt the sysadmins had a near impossible job. Half the staff in the company were running multi-boot systems with development Linux kernels, betas of MS operating systems, and running their own web servers, SMTP servers, hell, even setting up their own NT domains. If the sysadmins had stopped people from doing this, then the company's main activities would have come to a grinding halt. That the sysadmins managed to run a network that allowed this kind of anarchy on one level, while ensuring the email always got through and the finance guys could access their SAGE system, was a source of some amazement to me.
Not every company can treat the computers as dumb terminals and dictate how they're used from a helpdesk console in the sky.
How about official Linux desktops, sorta. (Score:2, Interesting)
Some one in IT has realised the beauty of Opensource, it's cheaper than MS. Cheap is good, saving money is good. Where an open source solution exists that can replace a commercial solution, it is on the desktop. Out went eXceed, in came Xfree 86 on Cygwin. Out went Reflections, in came Putty. And so on.
Several servers are already running Linux and I've heard they are trialling a rack of blades using Linux for something or other. I envisage more servers going over to Linux to save money and more of the desktop converting to Linux or at least Cygwin/Opensource for the same reason.
Re:Not exactly ... (Score:1, Interesting)
I want your job...
Windows sucks and it's all they know.
Is General Motors, North American Operations, big enough? Because they are exactly the idiot you describe with only three options for software.
Funny thing is, they run a ton of Sun Servers, most of which break at a fantastic rate, and yet they tell me that Perl is not an approved programming language and I'm not allowed to use it.
I asked them to let me know when they were going to remove Perl from all the servers so I could stay home that day.
They are considering the possibility of allowing some perl installations to exist even though they consider it to be inherently insecure, unstable, non-practical, and not of enterprise grade
Most companies are that stupid and few allow any flexability in the software you choose to use. If you think otherwise, then you haven't been around enough in the entire spectrum of industry in America.
Stealth Linux has its benefits (Score:3, Interesting)
So I'm thinking, and decide to wipe their machines and install a nice RH distro on all of them. Set them up with StarOffice, Mozilla, and Samba and hey presto they're doing 50% more products per day now (I'm not naive--I know they're gonna write emails, but it's not the time sink IM-ing is). Furthermore, their old Pentium machines are faster, and I can SSH into their boxes to fix anything that's wrong.
That last bit is key, because the tech dept. at this company is so bad they don't even know what an IP address is. But, they like to spy. There are cameras everywhere, and believe me, they ain't protecting national secrets at this place. So I figure, if they like to spy on you with cameras, they probably also like to spy on your computer. So with linux, no more spyware.
Yep, stealth linux works for me.
Re:You've got to be kidding (Score:4, Interesting)
You are IT. You are present to help workers get their damn work done, not to push some random personal agenda. If you wipe an entire system and kill that employee's work, you are a serious impediment to getting work done
In most companies, the standard OS is hardly a "personal agenda" - and the worker that installs a new OS on his/her computer without authorization is hardly "getting work done".
Most large companies I know don't allow you to keep your work on your local machine, as it makes all kinds of problems for backups, upgrades, and hardware trouble. Instead employees save all of their work to a central fileserver, which gets backed up on a regular basis. Re-imaging a machine is not a big deal. Even the place I work now (total of 20 employees) does this.
WTF does the OS have to do with this?
If the sysadmins don't know Linux, then they won't be able to fix the breakin.
Re:Linux on the Desktop? Not likely in many orgs (Score:2, Interesting)
I am the network engineer for a manufacturing firm, and I can tell you that (not counting the guys in production lines) our office workers could probably handle cut-and-paste on a good day. So I get to teach them how to add a printer while doing other system and network admin stuff.
1 in 60 is 'countable' (Score:3, Interesting)
This starts to be the question, how is Linux counted? Three broad categories: media sales, net scans, and installation reports.
Media Sales - simple count up the sales reports from major vendors. Using this method alone, one would get an unrealisticly low estimate of Linux users. Though I have installed Linux on over 250 machines, I have only purchased CDs from a vendor twice (OpenBSD 2.7 and Slackware 3.3). I have purchased CDs from other sources: flea markets, computer stores, etc - but these are not 'official' pressings and probably are not counted.
Net Scans - Netcraft does a srvey to see what OS / web server various sites are using. WHile this is handy, a lot of the servers I have installed have not been accessible to the outside world, for security reasons. Ones that are available to the outside world have a limited number of services running, and a firewall (usually the Linux machine itself) for access control. So this still isn't accurate.
Installation Reports - Various OSs request permission to inform a central location of a new Linux installation upon the installs completion. The ease of this process varies quite a bit. I used to never report, out of general paranoia, but I have started to in the past few years. I think we all should. I also think that there needs to be a standard method on installtion counting and reporting: some way to determine if a specific install is actually an upgrade, a switch, or whatever, and a way to protect users' privacy, but give some good statistics about the install. For instance, it would be great to report the platform (including CPU type & speed, memory, HD space, peripheral cards) and even the package selections. I know this is what redhat does with their RH network stuff, and though some people may find it annoying and opt out it does provide useful information to help developers and businesspeople in their decisions about where to concentrate support resources.
Here's an interesting bit of historical trivia: Back years ago, mayb 1996 or so, I was running tcpdump and noticed some very strange DNS queries. Every so often my Slackware machine would query to root servers for what turned out to be the last line of my
Re:Not exactly ... (Score:2, Interesting)
Re:You've got to be kidding (Score:1, Interesting)
honestly... we don't have 100k desktops and those
desktops we have are, yes, w2k... but I am allowed
to run virtualpc. I load up freebsd and put it into full screen mode. 200 days uptime and I get all the stuff I want *and* I'm (local/virtual) root. I'm happy, the w2k standard is still in place, etc.
Yes, some places are more open to alternatives... because they are scientific, research, educational, etc... other places are businesses where w2k cybercops think pushing policy is better than sex.
I don't care if anyone else runs unix/linux -- but I *do* care about MS trying to make open source / unix / linux be illegal (ie: legislation, drm, licensing, etc).
This whole line about having to buy a license if you use linux to access terminal services or citrix is very very very very very wrong.
Linux Under the Radar (Score:1, Interesting)
Now the developers are starting to ask how to create the same setup.
Our company is only about 300 users...but I have worked for Fortune 500s before - and while they tend to be slower in implementation of good technologies, the fact that we are starting to see users outside of the Infrastructure group want to run a *nix as their desktop tells me that it should not be long before the larger companies follow suite.