Well, this is all a lot of fun. :)
I bought a PC with a 486DX2/66, 12MB RAM, 350MB HD, and started to install
FreeBSD from a 2.1 CD-ROM I'd picked up somewhere - the intention being to
use this sytem to download a more current BSD once it was all working.
I used FIPS to cut the existing DOS partition in two, ending up with some-
ting like 11MB Swap, 32MB each / and /var, and 64MB /usr. Played around a
bit, got iijppp to dial out on one of my modems (but not the other :?),
all fine: but at a certain point I felt the need to rebuild my kernel,
and of course I had nowhere near enough space. So it's off down to the
shop to buy a lovely new 2.5GB IDE disk.
After enquiring after my system, the shop assistant handed me a floppy
which she thought I would probably need :), containing a driver for older
BIOSes. After much fiddling, I had the new disk installed as a slave,
duly partitioned (I put a DOS partition of 64MB at the beginning and
dedicated the rest to BSD).
My plan was to put / and Swap on the old drive, and /usr on the new. But
for some reason I cannot get this to work: the installer tells me it is
mounting / as read-only (although I've changed it since the last successful
install), and then fails when trying to mount wd0a. I *think* I need to
persuade it to treat my old disk as though it had never held a freebsd
filesystem, but I don't know how to do so.
It also seems that the installation program is writing to the MBR even
when I tell it not to: I keep on having to re-run Seagate's DM program
to re-install its boot sector.
Are these known bugs in the 2.1 installer? Can I use a later one?
Does what I am trying to do make sense? Should I maybe make the new
disk master and the old one slave??
Just how do my BIOS, Seagate's special boot sector, and FreeBSD work
together to make a usable file system?
Any other ideas?
Sometimes I find myself wishing I'd bought that Atari TT instead ...