Slashdot Mirror
What Would You Put Into A Software Survival Kit?
LosManos asks: "A call for help to the Everyday Heroes that are out there: I have just returned from a 4 months scientific expedition to some of the more remote parts of the South Pacific. As soon as people we met found out that I was a computer guy they asked me to help them and all to often I had to reply that I didn't have the tools.This got me thinking; what should a software toolbox consist of? OS, patches, digital books, compilers, sniffers, servers, harddisk restore apps...? Please remember that the computers I met where often old and slow. The answers to this could be interesting also when you are not several days away from nearest inhabited island. I mean, what is it that most often break? How is it usually fixed? Are more fancy solutions more error prone?" If you were to create a "first aid kit" consisting of CDs, disks, books and other technical utilities you have used to resurrect dead systems, what would you put in it?
"So far I have found:
- A utility for reading and repairing hard disks
- 'regmon' and 'filemon' from Sysinternals
- Video drivers (but I don't know which)
- A diskette for booting MSDOS with CD support
- Digital books (but I don't know which)
- Remote controlling tools, such as VNC
- CDs with OS (but there are hundreds of those)"
And maybe Norton Utilities. Those are great for when things go wrong.
Bring a copy of Knoppix and a copy of FIRE(Forensic Incident Response Environment.
Nothing I've found that those two can't handle.
Single-floppy linux boot with a tremendous array of rear-end saving utilities.
The first thing I try to keep is a list of how to clear the BIOS settings for every computer I manage. You would be amazed at how dumb you feel if you have all these nifty CDROM/floppy based utilities and are unable to make the damn PC boot from anything other than the screwed up hard drive.
The second thing I keep is a NT password recovery disk. About 90% of my problems are based on not knowing the admin password for a machine that has been in some users closet for 3 years. The user suddenly needs the PC on his network, and there I am trying to figure out the admin password. The best disk I have found is here.
The third thing I keep is a Norton Utilities CDROM. You can boot off the CDROM and scan for a virus or diagnose a flaky hard drive.
I also keep a Gentoo live CD. I have thought about going over to Toms Boot Disk, but the Gentoo disk usually does what I need.
Although I don't carry it with me, I also keep a spare hard drive and a Win2k disk with all the latest patches and utilities that my company uses for the standard install. If worse comes to worse, I just move the users hard drive over to the secondary IDE and then install on a fresh hard drive. Then I can copy the users data onto the new hard drive. After that, the users old hard drive becomes my spare for the next user.
I also have a folder with a hard copy of every config for every switch, router, and other configurable device on my network. This folder also has IP address schemes, network maps, building diagrams, and user names and phone numbers. The folder also has a floppy with soft copies of the above, PuTTY, and a TFTP server for uploading into a router quickly.
I try to locate at least one geek for every office. I try to show this geek some of the details about his office. I let him have localadmin for the computers in his office. If the (l)users in his office need a printer reinstalled or otherwise need localadmin access, I direct them to their local geek. This also serves to deflect all the "my home PC is acting dumb and can you fix it" type users.
Finally, I try to write a "Why Stuff Breaks" document for all the major problems on my network. "User in office 12a keeps unplugging the switch so he can make coffee" type comments for common problems can help my minions diagnose a problem quickly.
I'd rather you do it wrong, than for me to have to do it at all.