projects / unix-history / blame
| Commit | Line | Data |
|---|---|---|
| b88624ba GCI |
1 | |
| 2 | ||
| 3 | ||
| 4 | 1.0 Installation | |
| 5 | ---------------- | |
| 6 | ||
| 7 | 1.0.1: I just installed my system and rebooted. Now I can't find the | |
| 8 | extract or configure programs, where did they go? | |
| 9 | ||
| 10 | ||
| 11 | These two commands are just shell builtins. To get these back, either | |
| 12 | create a account [adding a user] with /.profile as its profile or | |
| 13 | boot FreeBSD with a '-s' at the boot prompt. | |
| 14 | ||
| 15 | ||
| 16 | 1.0.2: I want to install FreeBSD unto a SCSI disk that has more than | |
| 17 | 1024 cylinders. How do I do it? | |
| 18 | ||
| 19 | This depends. If you don't have DOS (or another operating system) on the | |
| 20 | system, you can just keep the drive in native mode and simply make sure that | |
| 21 | your root partition is below 1024 so the bios can boot the kernel from it. | |
| 22 | It you also have DOS/some other OS on the drive then your best bet is to find | |
| 23 | out what parameters that it thinks you have before installing FreeBSD. When | |
| 24 | FreeBSD's installation procedure prompts you for these values, you should then | |
| 25 | enter them rather than simply going with the defaults. | |
| 26 | ||
| 27 | There is a freely available utility distributed with FreeBSD called `pfdisk' | |
| 28 | (located in the tools/ subdirectory) which can be used for this purpose. | |
| 29 | ||
| 30 | ||
| 31 | 1.0.3: When I boot FreeBSD it says "Missing Operating System". | |
| 32 | ||
| 33 | See above (1.0.2). This is classicaly a case of FreeBSD and DOS or some other | |
| 34 | OS conflicting over their ideas of disk geometry. You will have to reinstall | |
| 35 | FreeBSD, but obeying the instructions given above will almost always get you | |
| 36 | going. | |
| 37 | ||
| 38 | ||
| 39 | 1.0.4: I have an IDE drive with lots of bad blocks on it and FreeBSD doesn't | |
| 40 | seem to install properly. | |
| 41 | ||
| 42 | FreeBSD's bad block (bad144) handling is still not 100% (to put it charitably) | |
| 43 | and it must unfortunately be said that if you've got an IDE or ESDI drive | |
| 44 | with lots of bad blocks, then FreeBSD is probably not for you! That said, it | |
| 45 | does work on thousands of IDE based systems, so you'd do well to try it first | |
| 46 | before simply iving up. | |
| 47 | ||
| 48 | ||
| 49 | 1.0.5: I have 32MB of memory, should I expect any special problems? | |
| 50 | ||
| 51 | If you have an IDE controller, no. Likewise, if you have a full EISA system | |
| 52 | with EISA disk controller or a working local bus controller (read further) | |
| 53 | you'll have no problems. If you have an ISA system, or an EISA system with an | |
| 54 | ISA disk controller then you will most certainly have problems with the upper | |
| 55 | 16MB of memory due to the ISA 24 bit DMA limitation (which ISA cards in EISA | |
| 56 | systems will also exhibit). If you have a local bus disk controller, and it's | |
| 57 | NOT a Buslogic Bt445S with a revision less than `D' (BIOS 3.36 or earlier), | |
| 58 | then you should be OK. Never fear, however, as all is not lost. | |
| 59 | FreeBSD-current (and the upcoming FreeBSD 1.2) have bounce-buffer support that | |
| 60 | make all of the above scenarios work with a full 32MB of memory or more. You | |
| 61 | are therefore advised to simply pull 16MB of memory out, install, and then see | |
| 62 | about upgrading to FreeBSD-current or FreeBSD 1.2 (when it comes out) so that | |
| 63 | you can put it back. | |
| 64 | ||
| 65 |