11. Wow….that seemed fast…..
12. I got a better job at Lockheed…
13. Management says…
14. Sorry, the new equipment didn’t get budgetted.
15. What do you mean that wasn’t a copy?
16. It didn’t do that a minute ago…
17. Where’s the GUI on this thing?
18. Damn, and I just bought that pop…
19. Where’s the DIR command?
20. The drive ate the tape but that’s OK, I brought my screwdriver.
21. I cleaned up the root partition and now there’s lots of free space.
22. What’s this “any” key I’m supposed to press?
23. Do you smell something?
24. What’s that grinding sound?
25. I have never seen it do *that* before…
26. I think it should not be doing that…
27. I remember the last time I saw it do that…
28. You might as well all go home early today …
29. My leave starts tomorrow.
30. Ooops.
31. Hmm, maybe if I do this…
32. “Why is my “rm *.o” taking so long?”
33. Hmmm, curious…
34. Well, my files were backed up.
35. What do you mean you needed that directory?
36. What do you mean /home was on that disk? I umounted it!
37. Do you really need your home directory to do any work?
38. Oracle will be down until 8pm, but you can come back in and finish your work when it comes up tonight.
39. I didn’t think anybody would be doing any work at 2am, so I killed your job.
40. Yes, I chowned all the files to belong to pvcs. Is that a problem to you?
41. We’re standardizing on AIX.
42. Wonder what this command does?
43. What did you say your (l)user name was…?
44. You did what to the floppy???
45. Sorry, we deleted that package last week…
46. NO! Not that button!
47. Uh huh……”nu -k $USER”.. no problem….sure thing…
48. Sorry, we deleted that package last week…
49. [looks at workstation] “Say, what version of DOS is this running?”
50. Oops! (said in a quiet, almost surprised voice)
51. YEEEHA!!! What a CRASH!!!
52. What do you mean that could take down the whole network?
53. What’s this switch for anyways…?
54. Tell me again what that ‘-r’ option to rm does
55. Say, What does “Superblock Error” mean, anyhow?
56. If I knew it wasn’t going to work, I would have tested it sooner.
57. Was that your directory?
58. System coming down in 0 min….
59. The backup procedure works fine, but the restore is tricky!
60. Hey Fred, did you save that posting about restoring filesystems with vi and a toothpick? More importantly, did you print it out?
61. OH, SH*T! (as they scrabble at the keyboard for ^c).
62. The sprinkler system isn’t supposed to leak is it?
63. It is only a minor upgrade, the system should be back up in a few hours. (This is said on a monday afternoon.)
64. I think we can plug just one more thing in to this outlet strip with out triping the breaker.
65. What is all this I here about static charges destroying computers?
66. I found this rabbit program that is supposed to test system performance and I have it running now.
67. Ummm… Didn’t you say you turned it off?
68. The network’s down, but we’re working on it. Come back after diner. (Usually said at 2200 the night before thesis deadline…)
69. Ooops. Save your work, everyone. FAST!
70. Boy, it’s a lot easier when you know what you’re doing.
71. I hate it when that happens.
72. And what does it mean ‘rm: .o: No such file or directory’?
73. Why did it say ‘/bin/rm: not found’?
74. Nobody was using that file /vmunix, were they?
75. You can do this patch with the system up…
76. What happens to a Hard Disk when you drop it?
77. The only copy of Norton Utilities was on THAT disk???
78. Well, I’ve got a backup, but the only copy of the restore program was on THAT disk….
79. What do mean by “fired”?
80. hey, what does mkfs do?
81. where did you say those backup tapes were kept?
82. …and if we just swap these two disc controllers like this…
83. don’t do that, it’ll crash the sys…….. SHIT
84. what’s this hash prompt on my terminal mean?
85. dd if=/dev/null of=/vmunix
86. find /usr2 -name nethack -exec rm -f {};
87. now it’s funny you should ask that, because I don’t know either
88. Any more trouble from you and your account gets moved to the 750
89. Ooohh, lovely, it runs SVR4
90. SMIT makes it all so much easier……
91. Can you get VMS for this Sparc thingy?
92. I don’t care what he says, I’m not having it on my network
93. We don’t support that. We won’t support that.
94. …and after I patched the microcode…
95. You’ve got TECO. What more do you want?
96. We prefer not to change the root password, it’s an nice easy one
97. Just add yourself to the password file and make a directory…
98-100 are being restored off of the back-up drive and will be available shorty. (Trust us, they’re funny.)

To set the root password run this: “mysql -u root mysql” Then run this query: “SET PASSWORD FOR root@localhost=PASSWORD(’password‘);” at the MySql prompt replacing the italics with the password.

Then run this command to connect to the database: “mysql -u root -p mysql” and enter your password.

Also to completely wipe everything associated with the database run “rm -rf /var/lib/mysql/*” and restart MySql server (/etc/init.d/mysqld start). This can be helpful to reset a forgotten root password, although there are less destructive ways.

My goal is to build a fully functioning webserver(http, ftp, smtp), with Apache, PHP, MySql on a 486 box. Along the way, I want to learn about configuring these components as well as become proficient with the Linux command line. Eventually when it is configured to my satisfaction, I am going to try to do some performance testing, to see how good a server a 486 is.

The first step was to get a working 486 computer. This proved to be harder than I originally thought it would be. I had an old Dell 486, and I had a bunch of old ram and hard drives laying around. I haven’t had this particular machine turned on for about 3 years, and it turned out that it no longer works. It turns on fine, but I am getting a floppy drive failure error, and it stops working. I tried several different floppy drives, and cables but it never worked. I concluded it must be a motherboard problem. After a week of looking on eBay, I found a great deal for a 486 computer, with 2 extra motherboards. This 486 works great. It has a 486 DX/2 50mhz CPU, 16mb Ram, and I added a 2 gb hard drive and a cdrom. The only problem with the computer is that the clock battery is dead, but who cares about correct time.

Next, I had to determine which distro to install. I wanted to try out FreeBSD since I have read that it works well with older hardware. Unfortunatly I could not get it to work. After booting all the floppy disks, it gets to a setup screen. When I hit any button to start setup, it just hangs. It does this with both the 5.4 and 6.0 disks. So I turned to Slackware Linux. I downloaded the 9.1 version. I considered the latest 10.2, but decided that I better not push it. I was hoping to do an ftp installation, but Slackware 9.1 doesn’t support this. So I downloaded both cd isos, but with the packages I selected, only needed the first cd. Here are the steps I followed to get a basic installation on my 486.

1. Booting
If your computer does not support booting from cd, as mine didn’t, then you need to create three floppies. Use RawWrite to create the floppies. Start with the bare disk, and enter the other disks as you are prompted. When the login prompt comes up enter root as the user, with a blank password.

2. Prepare the disk partitions
Enter cfdisk at the command line to enter the partition program. It is similar to the old dos fdisk. I created 2 partitions, an 80mb swap partition which I placed at the end of the drive, and a 2gb root (/) partition. You probably don’t have to, but I rebooted the computer here to make sure it would write the partition table.

3. Run the setup program
After the partitions are written, enter setup by typing setup. Select the menu item to prepare swap partition. After the swap partition is formated, the setup will setup the root partition. I selected the ext2 filesystem. I don’t know if the others have better performance or not, but I figured with such an old computer, it was best to go with the oldest type. The next thing it will ask you for is the source of the packages. I selected cdrom here.

4. Package selection
I selected A – Base system, AP – Applications, D – Development, and N – Networking. Everything else can be unselected, unless you want the X window system (not the best idea for a 486). I know that having development tools on a webserver is not a good security idea, but I figured if I had to compile anything special it might be useful. Next it asks you for the install type. I selected expert, because it lets you select individual packages in these general groups. I unselected anything that I didn’t think I would need. This included multimedia applications, publishing and printing tools, and anything else I knew was unneccessary. I also selected several additional packages in the Network group, like php support, and some monitoring stuff. Also I selected the MySql Package in the AP group.

5. Install system
After this the program installs your package selections.

6. Additional configuration
When the packages are finished installing, the program will setup your root password, timezone, lilo, and network. For network setup, it should autodetect you NIC (mine was a 3com 3c905), then you enter a hostname, domain, ip address (I would recommend giving it a static IP if you are going to make it a server), and default gateway. It will also bring up a list of the servers that you have installed, and ask you which ones you want running. Make sure ssh, inetd, and apache are running. Leave any other that are checked as well.

7. Reboot system
When setup is finished it will exit back to the command prompt. Enter shutdown -r to reboot the system. When it reboots, it should use Lilo to boot into your linux installation. Mine didn’t. Instead Lilo outputed a bunch of 40s on the screen and it froze. So I am using the bare.i floppy to boot. At the prompt that comes up, I enter mount root=/dev/hda1 to boot off my hard drive. (At some point I am going to try to fix this. Maybe I will try Grub. I will post more info on this later.)

You should now have a functioning Linux system!

My 486 is working fine. It is pretty quick. Of course it isn’t running much, but the command line is as fast as a command line can be. Doing the install took about 1 1/2 hours. Of course I spent several other hours getting the correct floppies and getting the install figured out.

Like I said earlier I don’t have much experience with Linux command line administration, or configuring any of the servers I want to run on my box. In fact I would classify myself as a newbie at Linux administration. Google is my best friend for this. I plan to document all the command I learn, and I will follow this installation article with several more about the configuration and commands I learn.

Picture of the 486 Linux server

You can see the CPU has no heat sink. This is before the days of CPU overheating. Also, the cdrom is just sitting there. Next time I reboot the machine, I will probably remove it, since I don’t need it now. The Nic is a 10mb connected to my router. I do have a cover for the box, but it is a little broken right now. Eventually I will get around to fixing it. The computer is actually very quiet. The only fan in it is in the power supply. The hard drive makes very little noise. In fact I think the combination of my laptop and usb hard drive is noisier. But that is not loud at all. The 486 box is quite different from the fast powerful computers that I work with everyday in my job. Much simpler. Kinda like old cars are much simpler than new ones. Oh the good old days.