summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorjkh <jkh@FreeBSD.org>1995-05-29 13:04:53 +0000
committerjkh <jkh@FreeBSD.org>1995-05-29 13:04:53 +0000
commitc8b0f1c85a14618077b21f1378ffe04c89b67812 (patch)
treef4aa9049fb31697ce45f9147901daca48f9a3db4
parentde59700f8a0065c74d50fdd973d0e6cb3427df58 (diff)
downloadFreeBSD-src-c8b0f1c85a14618077b21f1378ffe04c89b67812.zip
FreeBSD-src-c8b0f1c85a14618077b21f1378ffe04c89b67812.tar.gz
tweak tweak
-rw-r--r--release/sysinstall/help/en_US.ISO8859-1/drives.hlp11
-rw-r--r--release/sysinstall/help/en_US.ISO_8859-1/drives.hlp11
2 files changed, 12 insertions, 10 deletions
diff --git a/release/sysinstall/help/en_US.ISO8859-1/drives.hlp b/release/sysinstall/help/en_US.ISO8859-1/drives.hlp
index b4c59c3..349ba7e 100644
--- a/release/sysinstall/help/en_US.ISO8859-1/drives.hlp
+++ b/release/sysinstall/help/en_US.ISO8859-1/drives.hlp
@@ -1,20 +1,21 @@
-Select the drives you wish FreeBSD to be able to use.
+Select the drive(s) you wish FreeBSD to be able to use.
If you are going to actually install some portion of FreeBSD on a
-drive, then PLEASE BE VERY CERTAIN that the Geometry reported in the
+drive then PLEASE BE VERY CERTAIN that the Geometry reported in the
Partition Editor (see Installation Menu) is the correct one for your
drive and controller combination!
IDE drives often have a certain geometry set during the PC BIOS setup,
or (in the case of larger IDE drives) have their geometry "remapped"
by either the IDE controller or a special boot-sector translation
-utility (such as that by OnTrack Systems). In these cases, knowing
+utility such as that by OnTrack Systems. In these cases, knowing
the correct geometry gets even more complicated as it's not something
you can easily tell by looking at the drive or the PC BIOS setup. The
best way of determining your geometry in such situations is to boot
DOS (from the hard disk, not a floppy!) and run the ``pfdisk'' utility
-provided in the tools/ subdirectory. It will report the geometry that
-DOS sees, which is generally the correct one.
+provided in the tools/ subdirectory of the FreeBSD CDROM or FTP site.
+It will report the geometry that DOS sees, which is generally the
+correct one.
FreeBSD does its best to guess all of this automatically, of course,
but it sometimes fails which is why it's a good idea to check it. The
diff --git a/release/sysinstall/help/en_US.ISO_8859-1/drives.hlp b/release/sysinstall/help/en_US.ISO_8859-1/drives.hlp
index b4c59c3..349ba7e 100644
--- a/release/sysinstall/help/en_US.ISO_8859-1/drives.hlp
+++ b/release/sysinstall/help/en_US.ISO_8859-1/drives.hlp
@@ -1,20 +1,21 @@
-Select the drives you wish FreeBSD to be able to use.
+Select the drive(s) you wish FreeBSD to be able to use.
If you are going to actually install some portion of FreeBSD on a
-drive, then PLEASE BE VERY CERTAIN that the Geometry reported in the
+drive then PLEASE BE VERY CERTAIN that the Geometry reported in the
Partition Editor (see Installation Menu) is the correct one for your
drive and controller combination!
IDE drives often have a certain geometry set during the PC BIOS setup,
or (in the case of larger IDE drives) have their geometry "remapped"
by either the IDE controller or a special boot-sector translation
-utility (such as that by OnTrack Systems). In these cases, knowing
+utility such as that by OnTrack Systems. In these cases, knowing
the correct geometry gets even more complicated as it's not something
you can easily tell by looking at the drive or the PC BIOS setup. The
best way of determining your geometry in such situations is to boot
DOS (from the hard disk, not a floppy!) and run the ``pfdisk'' utility
-provided in the tools/ subdirectory. It will report the geometry that
-DOS sees, which is generally the correct one.
+provided in the tools/ subdirectory of the FreeBSD CDROM or FTP site.
+It will report the geometry that DOS sees, which is generally the
+correct one.
FreeBSD does its best to guess all of this automatically, of course,
but it sometimes fails which is why it's a good idea to check it. The
OpenPOWER on IntegriCloud