I used to work at Kettering University. We supported all the major OS, but the Linux and BSD users take so much less time on average. I would expect, the smaller schools to have a higher ratio of Unix support people in the server room, since MS doesn't make functional versions of some core networking stuff like dns, that any public domain needs. Besides, if there are any programming classes, those would typically be on Unix too, let alone any of the engineering type stuff (nix) or graphics arts (often mac). -- sent from my phone <div class="gmail_quote">On Jun 10, 2011 11:00 AM, "Clay Dowling" <<a href="mailto:clay@lazarusid.com">clay@lazarusid.com</a>> wrote: > On 6/10/11 9:41 AM, Frank Dolinar wrote: >> FYI: Posted this morning on Slashdot. >> >> >> Ask Slashdot: Linux Support In Universities? >> <<a href="http://ask.slashdot.org/story/11/06/10/136234/Ask-Slashdot-Linux-Support-In-Universities">http://ask.slashdot.org/story/11/06/10/136234/Ask-Slashdot-Linux-Support-In-Universities</a>> >> >> >> > For a smaller university adding support staff capable of handling Mac > and Linux issues would be a challenge. Although I would add that if > you're running Linux you probably should have some technical savvy of > your own, or know somebody who does. If you're running BSD without > significant technical savvy you'd be completely hosed anyway. > > With a modern installation of any OS though the amount of techno-magic > you need to make it work with network services is pretty minimal. My > office is a mixed environment of Mac, Linux, and a few freaky people who > run windows (as they point out, it's getting the job done). Tech > support is pretty mac-centric, but nobody seems to have any problems. > > Clay > _______________________________________________ > linux-user mailing list > <a href="mailto:linux-user@egr.msu.edu">linux-user@egr.msu.edu</a> > <a href="http://mailman.egr.msu.edu/mailman/listinfo/linux-user">http://mailman.egr.msu.edu/mailman/listinfo/linux-user</a> </div>