oldasdirt is specialNo, not "yellow bus" special.
oldasdirt is a i486 with 16MB of RAM, an old 2.1GB disk and a
10GB disk.
I did a CD install of OpenBSD 2.6 to this machine many, many moons ago. Subsequent upgrades pretty much followed my remote upgrade procedure. I believe that later OpenBSD releases require more memory. If you want to install on a tiny machine, get the 2.6 floppy image and use it to install the latest release or snapshot.
Typical uptimes are past 100 days and the system is usually brought down by powerfailures in the area of my castle. I generally feel uptimes are interpreted completely wrong. It does not matter how long a system has been up. What matters is how often a system goes down due to a failure. Systems that have been up for more than 6 months probably have all sorts of known security vulnerabilities in the kernel anyway, and daemons that have been installed or upgraded for whatever reasons may not be correctly invoked in startup scripts.
I had to use a trick or two to get this old a machine to accept a 10GB disk. If you have been around computers for a while, you will recall the limitations in disksize up through the nineties. I remember getting past 540MB of diskstorage on Intel machines was a problem, as when 2GB and 8GB limits were a problem. Now most systems will accept 160GB disks. You have no clue how good you have it.
Filesystem Size Used Avail Capacity Mounted on /dev/wd0a 62M 28M 30M 48% / /dev/wd0d 62M 5.0K 59M 0% /tmp /dev/wd0e 62M 28M 30M 48% /var /dev/wd0g 1.5G 216M 1.2G 15% /usr /dev/wd0h 566M 113M 426M 21% /home /dev/wd1a 774M 1.0K 736M 0% /usr/src /dev/wd1b 193M 1.0K 184M 0% /usr/ports /dev/wd1d 8.2G 7.7G 96M 99% /g
Now that I think about it, I do not know why I set off partitions for
/usr/src and /usr/ports. It is not like the
system is suitable for building much on anyway. The disks are not very fast,
and due to the low amount of RAM, processes that are idle for a few minutes
gets swapped to disk, introducing a 3-4 second delay on reinvocation.
tty wd0 wd1 fd0 cpu
tin tout KB/t t/s MB/s KB/t t/s MB/s KB/t t/s MB/s us ni sy in id
0 7 6.76 0 0.00 8.23 0 0.00 0.00 0 0.00 0 0 1 1 98
It is an OpenBSD 3.0-current system, sshd with key
authentication so I can get to my CVS working directory which is hosted on its
filesystem, tftpd for my router, dhcpd for other
systems on the LAN, tinydns to provide IP resolving for
*.westend.mongers.org, and dnscache to provide fast
name lookups for LAN users.
At some point I will try to get a Subversion repository running on the machine. I would like to serve my router config files via HTTP instead of TFTP as it provides better access control and good write restrictions. My router does not support fetching configs via HTTP. Currently, any user I allow to connect to my LAN can wipe my router config and destroy my connectivity. Fortunately, this requires them to be within (h)arms reach of me; I can punch the offender repeatedly if the need arises.
Active Internet connections (including servers) Proto Recv-Q Send-Q Local Address Foreign Address (state) tcp 0 0 192.168.42.2.53 *.* LISTEN tcp 0 0 192.168.42.2.22 192.168.42.10.35541 ESTABLISHED tcp 0 0 192.168.42.2.22 192.168.42.10.46021 ESTABLISHED tcp 0 0 192.168.42.2.22 *.* LISTEN tcp 0 0 127.0.0.1.111 *.* LISTEN tcp 0 0 *.111 *.* LISTEN udp 0 0 192.168.42.2.53 *.* udp 0 0 *.67 *.* udp 0 0 127.0.0.1.53 *.* udp 0 0 *.69 *.* udp 0 0 127.0.0.1.111 *.* udp 0 0 *.111 *.* udp 0 0 *.514 *.*
Below is output from various commands. If there is anything special you would like to see, let me know.