Take a position with a small company which uses computers extensively; but has no formal in house IT support. There are thousands of small companies like this. Then, start small: patch your box and configure it with Open Source software and show your stuff. The guy next to you will notice how much better your system runs; and ask you to fix his system. Repeat as necessary.
Find a section of the computing infrastructure which is badly in need of maintenance, buy a book, and present a plan of action to your manager (which is usually the company owner). This plan should not focus on "fixing all the broken crap"; but, on how this will improve business -- usually meaning the owner will spend less money on contract IT support and less of his time working with a broken system. If you suceed, you have now started on a career in IT.
And, initially, you will have to do all this IT support over and above your normal 40+ hour work assignments. And don't forget to continue to read and discuss technical issues on various discussion boards {Slashdot for example}. I owe a great debt of gratitude to many individuals on the Compuserve hardware forums from over 15 years ago.
The fact that you can still make a "garcia joke" means you did not substantially and effectively participate in "the garcia experience". I feel sorry for you.
The Texas higher education institutions already make heavy use of OSS. Our budgets don't allow us to afford anything else....except, of course, for UT Austin who can walk across the street to wine, dine, and whine the Texas Legislature.
In my opinion the way to discourage this divide in your company it to have the IT department take each of the other departments out for lunch, say once a month
Only if definitive ground rules are set stating no specific problems will be dicussed; and, anyone who violates that rule will pay the tab. I have graciously accepted invites to lunch out with various departments only to be the focus of a barrage of user questions. Deft application of humor and deflection of the subject provided no relief; and, department management made no effort to end the inquisition either. And my users like me (really).
No, no lunches out without implications of pain and suffering for the insufferable idiots.
I think we get jaded and snotty because really, you can only listen to the whines and insults of the users for so long before it affects you -- and make no mistake, users are every bit as insulting as they think we are.
This statement definitively states why IT is under-represented in politics. "lusers" are cute puppies compared to constituents.
Having said that, let me also add that Solaris10 is documented. Heavily. Coherently. Completely. HPUX and AIX are close, Linux isn't even an also-ran in the documentation realm.
...On this, I still have to continually reject. In some measure, maybe, and maybe every building block is documented in man pages, but practically speaking I can get information much more readily about any linux facility and how to use it in most common contexts. Trying to do the same in Solaris didn't get me far.
On documentation, I will have to agree. Solaris has inherited the worst trait of 1970's IBM documentation -- if you already know the answer you can find the answer. If not, the documention is a twisty maze of passages which all look alike.
I would like to see Solaris use some of that surplus processing power on a documentation front end which uses some rudimentary intelligence with synonym lookups on a database to provide useful information from the mess of data which is Solaris documentation.
This depends on your purchasing cycles. I recommend different PCs depending on the the projected life of the system. Two or three year purchasing cycle -- no x64; four years or longer with expansion room for RAM and mirrored HDDs -- yes.
killed by a falling rock ,
killed by a bolt of cold ,
killed by a newt ,
killed by a white unicorn ,
killed by a quasit ,
killed by a giant spider ,
killed by a coyote ,
killed by a rabid rat ,
killed by a soldier ant ,
killed by Mr. Rewuorb the shopkeeper ,
killed by a rabid rat ,
killed by a leocrotta ,
killed by a homunculus ,
killed by a giant ant ,
killed by a fox ,
killed by a giant mimic ,
killed by a sewer rat ,
killed by a mumak ,
killed by a fire ant ,
killed by a wand ,
killed by the invisible Wizard of Yendor ,
killed by a gnome ,
killed by a soldier ant while helpless ,
killed by a giant spider ,
killed by a Woodland-elf ,
killed by a jaguar ,
killed by a goblin ,
killed by a clay golem ,
killed by a giant mummy while helpless ,
killed by a dwarf while helpless ,
killed by a hallucinogen-distorted blue jelly ,
petrified by a cockatrice corpse ,
killed by a soldier ant ,
killed by a killer bee while helpless ,
killed by a leocrotta ,
petrified by a cockatrice corpse ,
petrified by a cockatrice corpse ,
petrified by a cockatrice corpse ,
killed by a snake ,
killed by an iron piercer ,
killed by a soldier ant ,
killed by a boulder ,
killed by a killer bee ,
killed by a little dog ,
killed by a giant rat ,
killed by a mumak ,
killed by an ettin mummy ,
killed by an owlbear ,
killed by a rabid rat ,
choked on a gnome corpse ,
killed by a killer bee ,
killed by an arrow ,
killed by a magic missile ,
killed by a panther while helpless ,
killed by a hill orc ,
killed by a soldier ant while helpless ,
killed by a newt while helpless ,
killed by a winter wolf ,
killed by a plains centaur ,
killed by a bolt of fire ,
killed by a hill orc while helpless ,
killed by a killer bee while helpless ,
killed by a giant spider ,
killed by a hobbit ,
killed by a soldier ant ,
killed by a giant spider ,
killed by a giant spider ,
killed by a large kobold while helpless ,
killed by a fox ,
killed by a bolt of fire ,
killed by an orc mummy while helpless ,
killed by a leocrotta ,
killed by an ape ,
killed by a wand ,
killed by a wand ,
killed by an owlbear ,
killed by a mumak ,
killed by a gnome lord ,
killed by a kitten ,
killed by a dwarf king ,
killed by a bat ,
killed by a werejackal ,
killed by a fox ,
killed by a fox ,
killed by a gnome ,
killed by a leather golem while helpless ,
killed by a rope golem ,
killed by a rothe ,
killed by a fox ,
killed by a boulder ,
killed by a gnome lord ,
killed by an exploding wand ,
killed by a cave spider ,
killed by a coyote ,
killed by a plains centaur ,
killed by a fox ,
killed by an invisible stalker ,
killed by a scorpion ,
killed by a killer bee while helpless ,
killed by a killer bee ,
killed by a mumak ,
killed by a gnome mummy ,
drowned in a pool of water by an electric eel ,
killed by a pyrolisk ,
killed by a plains centaur ,
killed by a blast of frost ,
killed by a rothe ,
killed by a killer bee ,
killed by a spotted jelly...
BSODs only crash the virtual environment, not the host machine.
Which is why I always connect my USB peripherals only to a VM on Workstation. Webcams, Palm TX, USB memory keys, etc have all BSOD my VM. 75 second reboot later, plug in the USB peripheral again and use the peripheral only in a VM.
Now if only the Exchange server was that responsive to a crash sigh
...as long as it says ThinkPad on it, it'll be the same quality we expect from a ThinkPad...
Unfortunately not. Although minor, all twelve of the the Thinkpads by Lenovo I have purchased have all had quality problems -- unlike the t40s previous. The most telling was the keyboard I could not replace because the phillips screw heads were stripped when the keyboard was installed.
The design and engineering are still sound; but, manufacturing is slipping.
Obviously, you have never tried to simualate or graph propagation of an organic virus with a 4 million node set using Matlab x64 on a desktop system.
We would be pleased to take your enthusiast money and 128 of your gaming buddies' money and build a Linux computational cluster to solve a problem that will likely save your life or the life of someone you know.
The doctor explained that this is because sitting puts the more pressure on your disc than laying or standing. In fact, standing seems to be the most neutral position for your back and relieves more pressure on the disc than other positions
Standing transfers the pressure from your lower back to your feet. I suggest you follow proper ergonomics for standing if you choose a standing office. Having worked in warehouses with concrete floors for over 20 years, good shoes are imperative. Else you will just transfer the damage from your lower back to your knees, ankles, and hips.
I can spend 10 very productive hours in a top of the line La Z Boy recliner working on a laptop. The lumbar support is excellent, the ability to lay back, then sit up, rock or sit sideways in the large chair is unparalleled. This chair will set you back $1000; but, I never feel tired nor have any joint issues after long periods of work in this chair. I have previously tried ergonomic chairs, straight backed wood chairs, and Lane recliners.
If only the chair had internal cable management, the power and network cable keep getting pinched by the recliner mechanism.
You did not completely grasp the content of his problem
...the clients just weren't up to the task of running AutoCAD, Architectural Desktop and Mechanical Desktop...
In exploring deployment of thin clients in a University Engineering department, I find the same issues. Regardless of the specifications of the server or infrastructure, if the Engineering Application was specifically designed to function on a single workstation, no amount of configuring, third party packagers, or hacking will make the application function adequately on a thin client. One of the experiments failed miserably because the vendor license daemon for lmgrd would not accept multiple license requests from the same IP address.
Now, if you want to just provide students with access to volume licensed MS apps, Eclipse or other Java IDEs, or email then obviously just throwing hardware at the problem will be effective.
Slashdot Mirror
Mod this +1 Wise -- I now feel enlightened.
Find a section of the computing infrastructure which is badly in need of maintenance, buy a book, and present a plan of action to your manager (which is usually the company owner). This plan should not focus on "fixing all the broken crap"; but, on how this will improve business -- usually meaning the owner will spend less money on contract IT support and less of his time working with a broken system. If you suceed, you have now started on a career in IT.
And, initially, you will have to do all this IT support over and above your normal 40+ hour work assignments. And don't forget to continue to read and discuss technical issues on various discussion boards {Slashdot for example}. I owe a great debt of gratitude to many individuals on the Compuserve hardware forums from over 15 years ago.
The fact that you can still make a "garcia joke" means you did not substantially and effectively participate in "the garcia experience". I feel sorry for you.
1] 30 minutes, my time, for Server2003 R2
2] 5 minutes install VMware Workstation
3] 30 minutes to install and configure the tape autochanger
4] Start previous installation restore from tape backup to Win XP VM. Go to sleep
5] 30 minutes: Let Windows install new hardware on VM and install VMware drivers.
Future hardware changes will only require restoring VMs from tape; or as a network file transfer.
Put down the rational thought. Step away from the rational thought and no one in the government will get hurt.
Then how does Superman make that WHOOSHING sound as he moves thru space? D00d, you don't know nuthin'
'government')
$MORALE is optional. Follow the policy.
As I said...walk across the street to wine, dine and whine the Texas Legislature is easier in Austin.
The Texas higher education institutions already make heavy use of OSS. Our budgets don't allow us to afford anything else....except, of course, for UT Austin who can walk across the street to wine, dine, and whine the Texas Legislature.
I just laughed my beer out my nose. You made me commit a beer sin.
No, no lunches out without implications of pain and suffering for the insufferable idiots.
PEBKAC implicated in UBI!
On documentation, I will have to agree. Solaris has inherited the worst trait of 1970's IBM documentation -- if you already know the answer you can find the answer. If not, the documention is a twisty maze of passages which all look alike.
I would like to see Solaris use some of that surplus processing power on a documentation front end which uses some rudimentary intelligence with synonym lookups on a database to provide useful information from the mess of data which is Solaris documentation.
+1 scary You are giving GM ideas we don't necessarily want them to have!
This depends on your purchasing cycles. I recommend different PCs depending on the the projected life of the system. Two or three year purchasing cycle -- no x64; four years or longer with expansion room for RAM and mirrored HDDs -- yes.
Now your employer can justify spitting on the employees as a workforce motivation tool.
Now roll your tongue back up in your mouth and get back to work code monkey! You can teach them to code but you can't take them out in public....
killed by a falling rock , killed by a bolt of cold , killed by a newt , killed by a white unicorn , killed by a quasit , killed by a giant spider , killed by a coyote , killed by a rabid rat , killed by a soldier ant , killed by Mr. Rewuorb the shopkeeper , killed by a rabid rat , killed by a leocrotta , killed by a homunculus , killed by a giant ant , killed by a fox , killed by a giant mimic , killed by a sewer rat , killed by a mumak , killed by a fire ant , killed by a wand , killed by the invisible Wizard of Yendor , killed by a gnome , killed by a soldier ant while helpless , killed by a giant spider , killed by a Woodland-elf , killed by a jaguar , killed by a goblin , killed by a clay golem , killed by a giant mummy while helpless , killed by a dwarf while helpless , killed by a hallucinogen-distorted blue jelly , petrified by a cockatrice corpse , killed by a soldier ant , killed by a killer bee while helpless , killed by a leocrotta , petrified by a cockatrice corpse , petrified by a cockatrice corpse , petrified by a cockatrice corpse , killed by a snake , killed by an iron piercer , killed by a soldier ant , killed by a boulder , killed by a killer bee , killed by a little dog , killed by a giant rat , killed by a mumak , killed by an ettin mummy , killed by an owlbear , killed by a rabid rat , choked on a gnome corpse , killed by a killer bee , killed by an arrow , killed by a magic missile , killed by a panther while helpless , killed by a hill orc , killed by a soldier ant while helpless , killed by a newt while helpless , killed by a winter wolf , killed by a plains centaur , killed by a bolt of fire , killed by a hill orc while helpless , killed by a killer bee while helpless , killed by a giant spider , killed by a hobbit , killed by a soldier ant , killed by a giant spider , killed by a giant spider , killed by a large kobold while helpless , killed by a fox , killed by a bolt of fire , killed by an orc mummy while helpless , killed by a leocrotta , killed by an ape , killed by a wand , killed by a wand , killed by an owlbear , killed by a mumak , killed by a gnome lord , killed by a kitten , killed by a dwarf king , killed by a bat , killed by a werejackal , killed by a fox , killed by a fox , killed by a gnome , killed by a leather golem while helpless , killed by a rope golem , killed by a rothe , killed by a fox , killed by a boulder , killed by a gnome lord , killed by an exploding wand , killed by a cave spider , killed by a coyote , killed by a plains centaur , killed by a fox , killed by an invisible stalker , killed by a scorpion , killed by a killer bee while helpless , killed by a killer bee , killed by a mumak , killed by a gnome mummy , drowned in a pool of water by an electric eel , killed by a pyrolisk , killed by a plains centaur , killed by a blast of frost , killed by a rothe , killed by a killer bee , killed by a spotted jelly...
Which is why I always connect my USB peripherals only to a VM on Workstation. Webcams, Palm TX, USB memory keys, etc have all BSOD my VM. 75 second reboot later, plug in the USB peripheral again and use the peripheral only in a VM.
Now if only the Exchange server was that responsive to a crash sigh
Unfortunately not. Although minor, all twelve of the the Thinkpads by Lenovo I have purchased have all had quality problems -- unlike the t40s previous. The most telling was the keyboard I could not replace because the phillips screw heads were stripped when the keyboard was installed.
The design and engineering are still sound; but, manufacturing is slipping.
Obviously, you have never tried to simualate or graph propagation of an organic virus with a 4 million node set using Matlab x64 on a desktop system.
We would be pleased to take your enthusiast money and 128 of your gaming buddies' money and build a Linux computational cluster to solve a problem that will likely save your life or the life of someone you know.
If only the chair had internal cable management, the power and network cable keep getting pinched by the recliner mechanism.
In exploring deployment of thin clients in a University Engineering department, I find the same issues. Regardless of the specifications of the server or infrastructure, if the Engineering Application was specifically designed to function on a single workstation, no amount of configuring, third party packagers, or hacking will make the application function adequately on a thin client. One of the experiments failed miserably because the vendor license daemon for lmgrd would not accept multiple license requests from the same IP address.
Now, if you want to just provide students with access to volume licensed MS apps, Eclipse or other Java IDEs, or email then obviously just throwing hardware at the problem will be effective.