[src/trunk]: src/distrib/notes/common * Mention the different floppy images a...

[fvdl <fvdl%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/61651b51417c
branches:  trunk
changeset: 499171:61651b51417c
user:      fvdl <fvdl%NetBSD.org@localhost>
date:      Mon Nov 13 22:05:52 2000 +0000

description:
* Mention the different floppy images and the machine types for which
  they are suitable (for i386).
* Mention xf86config(1) for ports that use XFree86.
* Since i386 INSTALL kernels do not have symbols, point users at
  the symbol files should they need them (hopefully not).

diffstat:

 distrib/notes/common/postinstall |   7 ++++-
 distrib/notes/common/sysinst     |  37 +++++++++++++++++++++++++-----
 distrib/notes/common/xfer        |  47 +++++++++++++++++++++++----------------
 3 files changed, 63 insertions(+), 28 deletions(-)

diffs (172 lines):

diff -r 2f6ea18228db -r 61651b51417c distrib/notes/common/postinstall
--- a/distrib/notes/common/postinstall  Mon Nov 13 21:48:33 2000 +0000
+++ b/distrib/notes/common/postinstall  Mon Nov 13 22:05:52 2000 +0000
@@ -1,4 +1,4 @@
-.\"    $NetBSD: postinstall,v 1.19 2000/11/13 01:22:40 hubertf Exp $
+.\"    $NetBSD: postinstall,v 1.20 2000/11/13 22:05:52 fvdl Exp $
 .\"
 .\" Copyright (c) 1999, 2000 The NetBSD Foundation, Inc.
 .\" All rights reserved.
@@ -219,7 +219,10 @@
 .Pp
 You will need to set up a configuration file, see
 .Pa /usr/X11R6/lib/X11/XF86Config.eg
-for an example.  See
+for an example. The
+.Xr xf86config 1
+utility can interactively create a first version of such a configuration
+file for you. See
 .Lk http://www.xfree86.org/
 and the XFree86 manual page for more information.
 .\}
diff -r 2f6ea18228db -r 61651b51417c distrib/notes/common/sysinst
--- a/distrib/notes/common/sysinst      Mon Nov 13 21:48:33 2000 +0000
+++ b/distrib/notes/common/sysinst      Mon Nov 13 22:05:52 2000 +0000
@@ -1,4 +1,4 @@
-.\"    $NetBSD: sysinst,v 1.16 2000/11/13 01:22:40 hubertf Exp $
+.\"    $NetBSD: sysinst,v 1.17 2000/11/13 22:05:52 fvdl Exp $
 .\"
 .\" Copyright (c) 1999, 2000 The NetBSD Foundation, Inc.
 .\" All rights reserved.
@@ -61,20 +61,29 @@
 .It
 .Em Possible Tn PCMCIA Em issues
 .Pp
-There is a serious problem that may make installation of
-.Nx
-on
+Machines with
 .Tn PCMCIA
-machines difficult. This problem does not make
-.Em using
+slots may have problems during installation. With the improvements of
+the
 .Tn PCMCIA
-difficult once a machine is installed. If you do not have
+code in this release, this will not happen very frequently.
+If you do not have
 .Tn PCMCIA
 on your machine
 .Tn ( PCMCIA
 is only really used on laptop machines),
 you can skip this section, and ignore the
 .Dq Bq Tn PCMCIA
+notes. If you do have
+.Tn PCMCIA
+in your machine, you can safely ignore this section and the
+.Dq Bq Tn PCMCIA
+the first time, as you are likely to not have problems. Should troubles
+occur during floppy boot, they may be
+.Tn PCMCIA
+specific. You should then re-read this section and try again,
+following the instructions in the
+.Dq Bq Tn PCMCIA
 notes.
 .Pp
 This section explains how to work around the installation problem.
@@ -192,6 +201,20 @@
 .Dl pcic_isa_alloc_iosize              0xbff = 0xbf
 .Dl db> Ic "continue"
 .Pp
+Note that, since some floppy images may not have symbol information in
+the kernel, you may have to consult the matching
+.Pa .symbols
+file in the
+.Pa binary/kernel
+directory in the installation tree. Find the pcic_ symbols used above,
+look at the hexadecimal value in the first column, and write, for
+example (if
+.Va pcic_isa_intr_alloc_mask
+is equal to c0513e3c):
+.Pp
+.Dl db> Ic "write 0xc0513e3c 0x0a00"
+.Pp
+
 After installation, this value can be permanently written to the kernel image
 directly with:
 .Pp
diff -r 2f6ea18228db -r 61651b51417c distrib/notes/common/xfer
--- a/distrib/notes/common/xfer Mon Nov 13 21:48:33 2000 +0000
+++ b/distrib/notes/common/xfer Mon Nov 13 22:05:52 2000 +0000
@@ -1,4 +1,4 @@
-.\"    $NetBSD: xfer,v 1.11 2000/11/13 02:38:36 lukem Exp $
+.\"    $NetBSD: xfer,v 1.12 2000/11/13 22:05:52 fvdl Exp $
 .\"
 .\" Copyright (c) 1999, 2000 The NetBSD Foundation, Inc.
 .\" All rights reserved.
@@ -46,24 +46,33 @@
 If you are not booting off a CD-ROM, you will need to have some floppy
 disks to boot off;
 either two 1.44 MB floppies or one 1.2 MB floppy.
-You must write the boot floppy images
-.Pa ( boot1.fs
+.Pp
+For laptops that have cardbus slots, you should use the
+.Pa bootlap1.fs
+and
+.Pa bootlap2.fs
+floppy images.
+.Pp
+For older machines with little RAM, use
+.Pa boot-tiny.fs .
+This image is tailored towards old, small-memory systems, and thus does
+not contain any PCI or SCSI support. It should work on systems with
+4M of RAM. Note that this means 4M available to NetBSD; systems that
+are said to have 4M may have 640k of base memory and 3072k of extended
+memory, which currently will not work, as this is a total of 3712k.
+.Pp
+For old machines that may have EISA, SCSI and more RAM, but only
+have an 1.2M floppy drive, use
+.Pa boot-small.fs .
+For all other systems, use
+.Pa boot1.fs
 and
 .Pa boot2.fs
-for 1.44 MB floppies,
-.Pa boot-tiny.fs
-for 1.2 MB floppies) onto these disks, which contain
-software to install or upgrade your
-.Nx
-system.
+.
 .Pp
-Note that the
-.Pa boot-tiny.fs
-image is tailored for
-.Dq small
-machines. this install image does not have drivers for PCI, PCMCIA,
-EISA or SCSI (i.e. ISA-only), but can be used on machines with only
-4 MB of RAM.
+For the 2-floppy sets (and the CD boot image), utilities to repair
+a badly crashed systems are included. The -small and -tiny images
+have seperate rescue floppy images because of lack of space.
 .Pp
 If you are using a
 .Ul
@@ -92,7 +101,7 @@
 A
 .Ic rawrite32
 is also available that runs under
-.Tn Windows .
+.Tn MS Windows .
 .Pp
 .\} \" r_i386
 .
@@ -140,7 +149,7 @@
 A
 .Ic rawrite32
 is also available that runs under
-.Tn Windows .
+.Tn MS Windows .
 .Pp
 Though
 .Nx*M
@@ -519,7 +528,7 @@
 If you have a
 .Tn MS-DOS
 or
-.Tn Windows
+.Tn MS Windows
 machine with an M-O drive connected, use it.
 If you don't, and if you have a program to handle
 .Tn IBM