I had a really good/funny story about Tom's new job here. He started a new job, still at the University but now working for the group that supports the whole campus. He was hired to be their Solaris expert. The CIO of the campus used to be Tom's boss in his old job so he knew what Tom could do. I am thankful he took the job because I think if he had not they would have eliminated Solaris completely. The problem with where he works is they don't know Solaris and so they do not know how to do things correctly. The result is they have made a lot of mistakes which make the systems difficult to admin and makes them run less than optimal.  
 
He made me take the funny story down but that is ok because it was the lesson the story teaches that made me post it. Not knowing they are doing things wrong, they are left just thinking Solaris is not as good as Linux. So, instead you get our conversation about why I posted it:  
 
Kristin: you make great stories, http://blogs.sun.com/kamundse
Tom: don't do that
Kristin: no one from (your work) reads my blog
Kristin: ok ok, i think it is funny, and useful
Tom: it is, but I have to work here
Kristin: i dont just put it on because it is funny, it is important
Kristin: these guys could ditch Solaris because they think it sucks
Kristin: because they can't use it right
Kristin: so why is that? why are they doing it all wrong?
Tom: they are used to Linux, they want to force solaris to work like linux and they don't want to learn the advanced solaris tricks
Kristin: yes
Tom: hence the /etc/hosts file that solaris doesn't deal with correctly
Tom: not using the solaris patch process, but rather making it look as much like linux as they can
Tom: add to that disabling auto_home
Kristin: i think Sun people need to know how the system are being used
Kristin: they need to know how people expect things to work and then we either need to provide linux-like interfaces or really get the message out about how to do things right
Kristin: ok... can i put this on my blog?
Tom: ok