diff options
Diffstat (limited to 'distrib/notes/amd64/install')
| -rw-r--r-- | distrib/notes/amd64/install | 89 |
1 files changed, 89 insertions, 0 deletions
diff --git a/distrib/notes/amd64/install b/distrib/notes/amd64/install new file mode 100644 index 00000000000..6a2df1a1113 --- /dev/null +++ b/distrib/notes/amd64/install @@ -0,0 +1,89 @@ +dnl $OpenBSD: install,v 1.1 2004/02/07 21:29:10 deraadt Exp $ +OpenBSDInstallPrelude + +If OpenBSD will be sharing the disk with DOS or another operating +system, you should have already completed the section of these notes +that instructed you on how to prepare your hard disk. You should know +the size of the OpenBSD area of the disk and its offset from the +beginning of the disk. You will need this information when setting up +your OpenBSD partitions. If your BIOS uses translated geometry, you +should use this geometry for the remainder of the install. This is +only necessary if you are sharing the disk with other operating systems +that use the translated geometry. + +There are several ways to install OpenBSD onto a disk. The easiest way, +should your computer support it, is to boot off the OpenBSD CD-ROM, or +off the bootable CD-ROM mini image. Otherwise, you can boot from a 3.5" +1.44MB floppy disk if your machine has a floppy drive. + +OpenBSDInstallPart2 + + With either the CD-ROM or the floppy in the drive, reboot your + computer. You might have to play with your BIOS options to let the + computer boot from the installation media, rather than the hard + disk. + + It will take a while to load the kernel from a floppy or slow + speed CD-ROM drive, most likely more than a minute. If some + action doesn't eventually happen, or the spinning cursor has + stopped and nothing further has happened, either your boot floppy + is bad or you are having hardware problems. If trying another + floppy disk doesn't help, try booting after disabling your CPU's + internal and external caches (if any). If it still doesn't work, + OpenBSD probably can't be run on your hardware. This can probably + be considered a bug, so you might want to report it. + If you do, please {:-include-:} as many details about your system + configuration as you can. + + +OpenBSDBootMsgs + + You will next be asked for your terminal type. You should just + hit return to select the default (vt220). + +OpenBSDInstallPart3({:- or "wd0" for IDE/RLL/ESDI/ST506 drives-:}) + + Next you will have to edit or create a disk label for the disk + OpenBSD is being installed on. If there are any existing + partitions defined (for any operating system), and a disk label + is not found, you will first be given an opportunity to run + fdisk and create an OpenBSD partition. + + If fdisk is being invoked on your behalf, it will start by + displaying the current partitions defined and then allow you + to modify this information, add new partitions and change + which partition to boot from by default. If you make a mistake, + you will be allowed to repeat this procedure as necessary to + correct this. Note that you should make OpenBSD be the active + partition at least until the install has been completed. + +OpenBSDInstallPart4({:- If you have DOS or Linux partitions + defined on the disk, these will usually show up as partition + 'h', 'i' and so on.-:}) + + Note that all OpenBSD partitions in the disk label must have an + offset that makes it start within the OpenBSD part of the disk, + and a size that keeps it inside of that portion of the disk. This + is within the bounds of the 'c' partition if the disk is not being + shared with other operating systems, and within the OpenBSD fdisk + partition if the disk is being shared. + +OpenBSDInstallPart5(wd0) + +OpenBSDInstallNet({:-CD-ROM, -:},nofloppy) + +OpenBSDFTPInstall + +OpenBSDHTTPInstall + +OpenBSDTAPEInstall + +OpenBSDCDROMInstall + +OpenBSDDISKInstall({:-"wdN" or -:},,{:- or MS-DOS-:}) + +OpenBSDCommonFS + +OpenBSDCommonURL + +OpenBSDCongratulations |