I could tell you they blocked Legit p2p traffic 24/7 because I was trying to download vmware player iso's just to see what they were talking about. I wanted to see if they were a good solution what I did. I guess preventing someone from working isn't that important.

Given my current Oracle "Support" ticket (for their database) will go a weeks without them touching it, looking at it, or working it, I see no reason why I should buy Oracle hardware. We buy Dells for Windows servers. We might as well buy Dell for Linux servers. Closing out Solaris, is just another reason-- in a long line of reasons --to switch.

Too bad they didn't think of doing this pre-1861

Don't you remember the 80's and 90's when there was the big push to get your children's registered -- just in case they were abducted. What do you think happened to THOSE databases.

Or even Solaris proper. Solaris 10 changed the game from the ground up, much to the point where it's Unix on roids. Run levels have been replaced with milestones, init.d has been replaced with SMF and the contract file system. Dtrace makes life worth living. Look, vmstat is great; but with Dtrace you can recreate vmstat/iostat/mpstat from the ground up! Get the picture of what this tool can do for you?!?! Containers/Zones for virtual hosts. OpenCluster for building and working with an HA cluster. Crossbow, for building whole networks inside your machine.

I think my only complaint about OpenSolaris is packages. After 8 years of Debian apt calls I find *Solaris to be a little too retro-RedHat (before YUM) for dependencies and new software.

I can't wait for the job postings once this mother is turned up to full!

If you think this is bad, then you better freaking skip working in the IT field; where everything is scanned, deep packet inspections, and if you ever place a personal laptop on the network they install a secret application to monitor you.

Then the MS workers can finally work from their own home country! And it would free up a large number of H1B visas for the rest of U.S..

... and thus could not be moved. So IT powered everything where they wanted to make a squatters claim to data center floor space. My favorite example was an SGI Challenge, we hadn't used SGI in 3 years, let alone the Challenge. The only thing plugged into this thing was power, no other cables of any type.

So an individual who vastly outperforms all other workers, and who is solely responsible for making that company money, is kicked out the door because of what? Because others can't read code? Not for work performance, which is what he was hired for, but for smelling bad and having a bad attitude? If that was such a problem why wasn't it in the dress code? I thought we were supposed to tolerate diversity in the workplace? This is another example of the left wing liberal commutarians destroying the individual's ability to function!

It depends on what group policies you have and what you want to do? First, don't use Ubuntu, or if you do, make sure to take the user out of the mix for sudo. Remove sudo and root access. Place everyone in LDAP and restrict / grant user access via ldap groups. Make all shells restricted shells. run ssh / vnc and an automated daemon for pushing out policy changes.

I don't have a BS degree but I was able to get into the field and work my way up. It was durning the 90's tech boom. But I was originally hired into Operations by a guy who liked to hire non-tech people and train them in the field. I worked into Unix Administration over the years. You will find that 80% of the job is just being able to adapt, remember, learn, and get along with the other people. You will also find that no matter what you do, what qualifications you have, a Sysadmin job is not a Sysadmin job. Each company will approach things differently so your main trick will not to "learn the OS" but to "learn the environment". What they have in place and how each part relates to the other part. Working in a cubby whole will get you nowhere. I've also known people, who don't even have a Highschool degree, get hired into the field. They just had to work at really crap jobs and really work their way up. Start looking for jobs. Start looking for anything that will hire you that's close to where you want to go; study; build systems at home and on your spare time (without google) and be ready to change jobs multiple times. Oh, and don't burn bridges. I don't know where you are but I've found that even in large urban centers the sysadmin community is a small one. You may not know the new guy they just hired in, but odds are good that the both of you know someone in common.

That really makes me want to become an EVIL Unix Admin instead of just a normal Unix Admin. I feel the sudden urge for world domination. Um Bork Bork Bork.