Linux is about 10 years old now, which means that it's been around for as long as Windows NT and Netware 4.
We are increasingly using Linux in our shop, and we've proceeded as follows.
First, give the Techs a copy of Red Hat, and have them install it for use as their own server. Either for Non Pirated MP3s, or more useful storage, give them run of the box, and allow them to work together on it just as something to play with. The end result of this will be that they have some basis for using Linux itself, and how it works, as well as learning Samba. Once this is working, they will generally feel comfortable goofing around with Linux. Try to give them a bit of time to do that, even if it's just 15-20 Mins a day. Once they are comfortable with that, they will have spent a month or so supporting file and print sharing through Samba (for themselves.)
Then, when a new application comes up for you to install, start from day one with it on Linux. Or, invent a new application for you to use internally. An IT intranet, or something. Make the managers aware of the project, and give them reports regularly (bi-weekly, or whatever). Then build up to more important things. Linux or not, it doesn't make sence to replace a solution that works just because you can...
IBM's support doesn't particularly matter in the short term, because beople aren't going to go out and buy an S/390 or an AS/400 and junk all their current intel boxes just so they can move to a Linux based network. First, there needs to be a comfort factor. Management needs to see Linux as more than a geek toy, and Tech needs to see Linux as something they can work with. It's like dating. You don't get married and then ask about a person's likes and dislikes. You date, build trust, get comfortable, and THEN commit to marriage. Same with Linux. Start Small, and build up. When you need to replace your ERP package, then worr