diff options
40 files changed, 628 insertions, 559 deletions
diff --git a/distrib/notes/amiga/contents b/distrib/notes/amiga/contents index 07852d8566f..14e091b43e2 100644 --- a/distrib/notes/amiga/contents +++ b/distrib/notes/amiga/contents @@ -49,4 +49,3 @@ OpenBSDxshare(1.5M,8.5M) OpenBSDxfont(6.0M,7.3M) OpenBSDxserv(2.6M,6.3M) - diff --git a/distrib/notes/amiga/hardware b/distrib/notes/amiga/hardware index 2aefdb20d17..f378c14fa0d 100644 --- a/distrib/notes/amiga/hardware +++ b/distrib/notes/amiga/hardware @@ -82,5 +82,6 @@ Supported devices {:-include-:}: The CrossLink. Amiga floppy drives. Amiga mouse. + Amiga joystick. If its not on this list, there is no support for it in this release. diff --git a/distrib/notes/amiga/install b/distrib/notes/amiga/install index e1ecf2ab720..98e4a80278c 100644 --- a/distrib/notes/amiga/install +++ b/distrib/notes/amiga/install @@ -29,17 +29,13 @@ OpenBSDInstallPart2 the dblNTSC mode, you may also {:-include-:} the "-A" option to enable the dblNTSC display mode. - You should see the screen clear and some information about - your system as the kernel configures the hardware. Note which - hard disk device(s) are configured (sd0, sd1, etc). You will - be asked for disknames later during the install. If you cannot - read the messages as they scroll by, do not worry -- you can get - at this information later inside the install program. If you - are doing the miniroot install you will be prompted for a root - device. At this time type 'sd0*', where '0' is the device which - holds the miniroot-containing swap partition you created during - the hard disk preparation. If the system should hang after - entering the root device, try again with +OpenBSDBootMsgs + + If you are doing the miniroot install you will be prompted for a + root device. At this time type 'sd0*', where '0' is the device + which holds the miniroot-containing swap partition you created + during the hard disk preparation. If the system should hang + after entering the root device, try again with loadbsd -I ff -b bsd @@ -51,10 +47,9 @@ OpenBSDInstallPart2 loadbsd -I ff bsd.rd While booting, you will probably see several warnings. You - should be warned that no swap space is present, and that - init(8) cannot find /etc/rc. Do not be alarmed, these are - completely normal. When you reach the prompt asking you for a - shell name, just hit return. + should be warned that no swap space is present. Do not be + alarmed, these are completely normal. When you reach the prompt + asking you for a shell name, just hit return. You will be asked which terminal type to use, you should just hit return to select the default (vt220). @@ -88,7 +83,7 @@ OpenBSDInstallPart2 newfs: ioctl (WDINFO): Invalid argument newfs: /dev/rsd0a: can't rewrite disk label - If there are any others, restart from the the beginning of + If there are any others, restart from the beginning of the installation process. This error is ok as the Amiga does not write disklabels currently. You should expect this error whenever using newfs. diff --git a/distrib/notes/amiga/upgrade b/distrib/notes/amiga/upgrade index 201887e01c8..49481850af9 100644 --- a/distrib/notes/amiga/upgrade +++ b/distrib/notes/amiga/upgrade @@ -1,8 +1,3 @@ -The upgrade to OpenBSD OSREV is a binary upgrade; it would be prohibitive -to make users upgrade by compiling and installing the OSREV sources, and -it would be very difficult to even compile a set of instructions that -allowed them to do so. - To do the upgrade, and if you are using the miniroot installation, you must have the OpenBSD kernel on AmigaDOS and you must transfer the root filesystem miniroot{:--:}OSrev.fs onto the swap partition of the OpenBSD hard disk. diff --git a/distrib/notes/amiga/whatis b/distrib/notes/amiga/whatis index 7a16a3809e8..0c7fd788883 100644 --- a/distrib/notes/amiga/whatis +++ b/distrib/notes/amiga/whatis @@ -1,2 +1,3 @@ - -Several graphics, SCSI and network boards are supported. +OpenBSD/MACHINE is a port to the Amiga machines manufactured by +Commodore. The ports supports a wide range of hardware and peripherals, +with all the stability and security you can expect from OpenBSD. diff --git a/distrib/notes/amiga/xfer b/distrib/notes/amiga/xfer index bf25e14b739..434a1b407cd 100644 --- a/distrib/notes/amiga/xfer +++ b/distrib/notes/amiga/xfer @@ -1,7 +1,7 @@ Installation is supported from several media types, including: AmigaDOS Fast file system partitions - Berkeley FFS partitions + FFS partitions Tape Remote NFS partition FTP @@ -76,7 +76,7 @@ To prepare for installing via NFS: /etc/exports file of the NFS server and resetting mountd, acts which will require superuser privileges. Note the numeric IP address of the NFS server and of - the router closest to the the new OpenBSD machine, + the router closest to the new OpenBSD machine, if the NFS server is not on a network which is directly attached to the OpenBSD machine. diff --git a/distrib/notes/hp300/contents b/distrib/notes/hp300/contents index 1ce5e3a793e..bae045c45ee 100644 --- a/distrib/notes/hp300/contents +++ b/distrib/notes/hp300/contents @@ -12,11 +12,8 @@ OpenBSDrd SYS_UBOOT Unified boot file, used for booting from the network. - HP-IB.geometry A file containing geometry for some HP-IB - disk drives. - - uboot.raw Raw boot file, used internally for booting - from the CDROM. + SYS_CDBOOT Raw boot file, used for booting from + CDROM. DistributionDescription diff --git a/distrib/notes/hp300/hardware b/distrib/notes/hp300/hardware index 83c4e74a7c9..86de87677fa 100644 --- a/distrib/notes/hp300/hardware +++ b/distrib/notes/hp300/hardware @@ -1,7 +1,8 @@ -OpenBSD/MACHINE OSREV will run on most HP 9000/300- and 400-series machines. +OpenBSD/MACHINE OSREV will run on most HP 9000/300- and 400-series +machines. The lowest amount of RAM that has ever been tested is 7.5M, though it -may run with less. Certainly, if you wish to run X, more RAM is -recommended. +may run with less. A GENERIC kernel won't run in 4M, while a custom +kernel can fit. However, if you wish to run X, more RAM is recommended. The following HP hardware is supported: diff --git a/distrib/notes/hp300/install b/distrib/notes/hp300/install index e5b7a6f59a6..5dc14ec81bd 100644 --- a/distrib/notes/hp300/install +++ b/distrib/notes/hp300/install @@ -1,47 +1,19 @@ -Installing OpenBSD is a relatively complex process, but if you have -this document in hand and are careful to read and remember the -information which is presented to you by the install program, it -shouldn't be too much trouble. - -Before you begin, you should know the geometry of your hard disk, i.e. -the sector size (note that sector sizes other than 512 bytes are not -currently supported), the number of sectors per track, the number of -tracks per cylinder (also known as the number of heads), and the -number of cylinders on the disk. The OpenBSD kernel will try to -discover these parameters on its own, and if it can it will print them -at boot time. If possible, you should use the parameters it prints. -(You might not be able to if your disk is so old that the -kernel can't figure out its geometry.) +OpenBSDInstallPrelude You should now be ready to install OpenBSD. -The following is a walk-through of the steps you will take while -getting OpenBSD installed on your hard disk. If any question has a -default answer, it will be displayed in brackets ("[]") after the -question. If you wish to stop the installation, you may hit Control-C -at any time, but if you do, you'll have to begin the installation -process again from scratch. +OpenBSDInstallPart2 Boot your machine from the network. When presented with the boot prompt, enter the path of your kernel (`bsd.rd' is a likely choice if you are booting over the network). - You will then be presented with the OpenBSD kernel boot - messages. You will want to read them, to determine your - disk's name and geometry. Its name will be something like - "sd0" or "hd0" and any geometry or size information will be - printed on a line that begins with its name. As mentioned above, - you will need your disk's geometry when creating OpenBSD's - partitions. You will also need to know the name, to tell the - install tools what disk to install on. If you cannot read the - messages as they scroll by, do not worry -- you can get at this - information later inside the install program. +OpenBSDBootMsgs While booting, you will probably see several warnings. You - should be warned that no swap space is present, and that - init(8) cannot find /etc/rc. Do not be alarmed, these are - completely normal. When you reach the prompt asking you for a - shell name, just hit return. + should be warned that no swap space is present. Do not be + alarmed, these are completely normal. When you reach the prompt + asking you for a shell name, just hit return. You will next be asked for your terminal type. There are only a few specific terminal types supported. If you are using a diff --git a/distrib/notes/hp300/prep b/distrib/notes/hp300/prep index 1b1c8f9cda1..9d0639c17c6 100644 --- a/distrib/notes/hp300/prep +++ b/distrib/notes/hp300/prep @@ -33,8 +33,6 @@ In order to complete this process, you will need the following from the bsd.rd The uncompressed RAMDISK kernel image. - bsd.rd.gz The gzipped RAMDISK kernel image. - To boot SYS_UBOOT via the network, you will need a system capable of handling boot requests for an hp300. If you will use this method, see the special note below. @@ -60,7 +58,7 @@ capable of running the rbootd(8) program. Source code may be found under usr.sbin/rbootd in the OpenBSD source tree, but requires the Berkeley Packet Filter (bpf) in order to function. It may be possible to use HP-UX, but is not recommended (or documented here). For more -information on diskless booting under OpenBSD, see the "diskless" +information on diskless booting under OpenBSD, see the diskless(8) manual page. First of all, configure your rbootd to handle boot requests from the @@ -99,6 +97,3 @@ press the space bar. Shortly, you should see a menu of possible boot options appear. Select the option corresponding to SYS_UBOOT. SYS_UBOOT will then load and prompt you for a kernel name. NFS file names should not have a leading '/' prepended to them, simply use `bsd.rd'. - ------------------- End of network boot-specific section ---------------------- - diff --git a/distrib/notes/hp300/upgrade b/distrib/notes/hp300/upgrade index 64a8f222f25..81ae6caa65e 100644 --- a/distrib/notes/hp300/upgrade +++ b/distrib/notes/hp300/upgrade @@ -1,10 +1 @@ -To upgrade to OpenBSD OSREV from a previous version start with the general -instructions in the section "Installing OpenBSD". - -After booting with the miniroot, select the (U)pdate option rather than -the (I)nstall option at the prompt in the install process. - -The upgrade script will use the existing disk partitions to install the -new system in, and also preserves files in `/etc' which you are likely -to have customized since a previous installation. - +OpenBSDUpgrade diff --git a/distrib/notes/hp300/xfer b/distrib/notes/hp300/xfer index 20c21d23a22..0cc603de185 100644 --- a/distrib/notes/hp300/xfer +++ b/distrib/notes/hp300/xfer @@ -5,7 +5,6 @@ Installation is supported from several media types, including: Remote NFS partition FTP HTTP - rsh & restore Obviously, the steps necessary to prepare the distribution sets for installation or upgrade depend on which installation medium you @@ -62,7 +61,7 @@ NFS, you must do the following: (Both of these actions will probably require superuser privileges on the server.) - You need to know the the numeric IP address of the NFS server, + You need to know the numeric IP address of the NFS server, and, if the server is not on a network directly connected to the machine on which you're installing or upgrading OpenBSD, you need to know the numeric IP address of the router closest diff --git a/distrib/notes/i386/contents b/distrib/notes/i386/contents index b9670872df6..4276a0624fe 100644 --- a/distrib/notes/i386/contents +++ b/distrib/notes/i386/contents @@ -4,6 +4,8 @@ OpenBSDfloppy OpenBSDfloppyB +OpenBSDfloppyC + OpenBSDcdrom OpenBSDdistsets @@ -45,4 +47,3 @@ OpenBSDxfont(5.9M,7.1M) OpenBSDxserv(14.8M,35.2M) OpenBSDxlink - diff --git a/distrib/notes/i386/hardware b/distrib/notes/i386/hardware index ee0afb2d206..27488e1c7e9 100644 --- a/distrib/notes/i386/hardware +++ b/distrib/notes/i386/hardware @@ -1,8 +1,15 @@ -OpenBSD/MACHINE OSREV runs on ISA (AT-Bus), EISA, PCI, and VL-bus systems -with 386-family processors, with or without math coprocessors. It -does NOT support MCA systems, such as some IBM PS/2 systems. The -minimal configuration to install the system is 6M or 8M of RAM and -perhaps 50M of disk space. A custom kernel might be able to run +OpenBSD/MACHINE OSREV works across a broad range of standard PC's and +clones, with a wide variety of processors and I/O bus architectures. It +can be expected to install and run with minimal difficulties on most +current products. The cases where problems may be encountered are +typically older proprietary PC's, Laptops or specialized server boxes +that rely on a custom BIOS to paper over implementation differences. + +OpenBSD does not currently support multiple processors (SMP), but will +run using one processor on a multi-processor system board. + +The minimal configuration to install the system is 6M or 8M of RAM and +perhaps 60M of disk space. A custom kernel might be able to run with only 4MB, though we do not know of anyone running with a system quite this minimal today. To install the entire system requires much more disk space, and to run X or compile the system, more RAM @@ -10,56 +17,139 @@ is recommended. (8M of RAM will actually allow you to run X and/or compile but it won't be speedy. Note that until you have around 16M of RAM, getting more RAM is more important than getting a faster CPU.) -Supported devices {:-include-:}: - Floppy controllers. - MFM, ESDI, IDE, and RLL hard disk controllers. - SCSI host adapters: - Adaptec AHA-154xA, -B, -C, and -CF +Supported hardware {:-include-:}: + Processors + All CPU chips compatible with the Intel 80386 (i386) + architecture: + 386/486 (SX/DX/DX2/DX4) + Intel Pentium/Pentium-MMX + Intel Pentium Pro/II/III/Celeron/Xeon + Intel Pentium IV + AMD 6x86 + AMD K5/K6/K6-2/K6-3 + AMD Athlon/Duron + Cyrix MediaGX/M1/M2 + VIA Cyrix III + Rise mP6 + IDT WinChip + NexGen 586 + Transmeta TMS3200, TMS5400, TMS5600 + Everything that is a clone of the 386 or up should work + fine. The only CPU that is known to work poorly (due to + flawed motherboards designs) is the Cyrix 386DLC. + Buses + All standard ISA, EISA, VLB, and PCI bus based machines, + including: + Intel 450GX/KX based machines + Intel 450NX based machines + ServerWorks chipset-based machines + (We just had to mention those last three, since + they are the hardest to support)) + Both 16-bit PCMCIA Cards and newer 32-bit CardBus + support + Universal Serial Bus (USB) + The MCA bus found in various IBM PS/2 machines is not + supported. + Bus Interfaces + Standard PCI-PCI bridges, including PCI expansion + backplanes + YENTA-compatible PCI-CardBus bridges + Entropy Sources + Interrupt latency collection from many devices + INtel 82802 random number generator found on i810, i815, + i820, i840, i850 and i860 based systems. + Disk Controllers + Floppy controllers. + ISA MFM, ESDI, IDE, and RLL hard disk controllers. + PCI IDE Controllers + Acer Labs M5229 + Advanced Micro Devices 756, 766 + CMD Tech PCI0640, PCI0643, PCI0646, PCI0648, and PCI0649 + Contaq Microsytems/Cypress CY82C693 + HighPoint HPT366, HPT370 + Intel PIIX, PIIX3, and PIIX4 + Intel 82801 (ICH/ICH0/ICH2) + OPTi 82C568, 82D568, and 82C621 + Promise PDC20246, PDC20262, PDC20265/7 + Silicon Integrated Systems 5513 (5597/5598) + VIA Technologies VT82C586[A], VT82C596, VT82C686 + (Other PCI IDE-compliant controllers should work, but + those not listed above may not be capable of DMA modes) + SCSI Host Adapters + Adaptec AHA-1540, AHA-154xA, AHA-154xB, AHA-1542C, + AHA-1542CF, AHA-1542CP, AHA-1640 Adaptec AHA-174x - Adaptec AIC-6260 and AIC-6360 based boards, including + Adaptec AIC-6260 and AIC-6360 based boards, including: the Adaptec AHA-152x and the SoundBlaster SCSI host adapter. (Note that you cannot boot from these boards if they do not have a boot ROM; only the AHA-152x and motherboards using this chip are likely to be bootable, consequently.) - Adaptec AHA-294x[W] cards and some onboard PCI designs using - the AIC7870 chip. The 2940AU is known not to perform - very well with this driver. - Adaptec AHA-394x[W] cards; two AIC7870 chips with an on-board - PCI to PCI bridge. - Adaptec AIC-7770-based SCSI host adapters (including the - Adaptec AHA-274x, AHA-284x families). - Adaptec Ultra160 controller family, including 7892, 7899, - 29160, 39160, and other variants - AdvanSys PCI SCSI host adapters (including ABP-940, ASB-3940 - and ASB-3950 families) - WD-7000 SCSI host adapters. - Buslogic 54x (Adaptec AHA-154x clones; driver on kcadp floppy) + Adaptec AIC-7770-based boards, including the Adaptec + AHA-274x and AHA-284x families) + Adaptec AHA-[23]94x[W] cards and some on-board PCI designs + using the AIC7870 and AIC7880 chips. + Adaptec AHA-[23]94xU[2W] cards and some on-board PCI designs + using the AIC789[01], AIC7895, AIC789[67] chips + Adaptec AIC-780[29] chips and products like the + AHA-29160 based upon it which do 160MB/sec SCSI. + AdvanSys 'U', 'UW', 'U2W' and 'U160' PCI SCSI + controllers including the ABP940U[AW], + ASB3940U[AW]-00, ASB3940U2W-00 and ASB3950U160 + AMD Am53c974 PCscsi-PCI SCSI controllers, including: + Tekram DC-390 + Buslogic BT-54x (Adaptec AHA-154x clones) BusLogic 445, 74x, 9xx (But not the new "FlashPoint" series of BusLogic SCSI adapters) - Symbios Logic (NCR) 53C8xx-based PCI SCSI host adapters - Ultrastor 14f, 34f, and (possibly) 24f - Seagate/Future Domain ISA SCSI adapter cards, including + Initio INIC-940 and INIC-950 based PCI SCSI host + adapters, including the Initio INI-9090U and + Initio INI-9100U/UW, and the Iwill 2935UW + QLogic PCI SCSI controllers + Seagate/Future Domain ISA SCSI adapter cards, including: ST01/02 Future Domain TMC-885 Future Domain TMC-950 - Initio INIC-940 and INIC-950 based PCI SCSI cards, including - Initio INI-9090U - Initio INI-9100U/UW - Iwill 2935UW - AMD Am53c974 PCscsi-PCI SCSI controllers - RAID controllers: + Symbios Logic (NCR) 53C8xx, 53C1010, and 53C1510D-based + PCI SCSI host adapters (including generic/no + name cards, old ASUS cards, the DTC-3130 series, + Diamond Fireport series, etc.) + Tekram DC-300B and DC-320E (Adaptec AHA-154x clones) + Ultrastor 14f, 24f, and 34f + WD-7000 SCSI host adapters + RAID and Cache Controllers 3ware Escalade 3W-5x00, 3W-6x00 + Adaptec FSA-based RAID controllers, including: + Adaptec AAC-2622, AAC-364, AAC-3642 + Dell PERC 2/Si, PERC 2/QC, PERC 3/Si, PERC 3/Di, + PERC 3/QC + HP NetRAID-4M American Megatrends Inc. MegaRAID controllers - Compaq Smart ARRAY PCI/EISA adapters - DPT SmartCache III/IV PCI/EISA adapters - ICP-Vortex GDT 6XXXRP series - Adaptec FSA-based + Compaq Smart ARRAY PCI/EISA adapters, including: + Compaq Integrated Array + Compaq IAES + Compaq IDA, IDA-2 + Compaq RAID LC2 + Compaq Smart Array 221, 3100ES, 3200, 4200, + 4250ES, 431 + Compaq SMART, SMART-2/E, SMART-2/P, SMART-2DH, + SMART-2SL + DPT SmartCache and SmartRaid III/IV PCI/EISA adapters + ICP-Vortex GDT 6XXXR[DNPS] series + CD-ROM and DVD-ROM Drives + Mitsumi CD-ROM drives [*] [+] + [Note: The Mitsumi driver device probe is known + to cause trouble with several devices!] + Most SCSI CD-ROM, CD-R, CD-RW, and DVD drives + Most ATAPI CD-ROM, CD-R, CD-RW, and DVD drives + Tape Drives + Most SCSI tape drives + Most SCSI tape changers + QIC-02 and QIC-36 format (Archive- and Wangtek- MDA, CGA, VGA, SVGA, and HGC Display Adapters. (Note that not all of the display adapters OpenBSD/i386 can work with are supported by X. See the XFree86 FAQ for more information.) - Serial ports: + Serial Ports 8250/16450-based ports 16550-based ports ST16660-base ports @@ -68,15 +158,72 @@ Supported devices {:-include-:}: BOCA 8-port serial cards [*] Cyclades Cyclom-{4, 8, 16}Y serial boards [*] IBM PC-RT 4-port serial boards [*] - Parallel ports. - Ethernet adapters: - Alteon Tigon I/II PCI Gigabit Ethernet boards [*] [+]: - 3Com 3c985 and 3c905B - Alteon ACEnic V (fiber and copper) - Netgear GA620 and GA620T - SGI Tigon - Farallon PN9000 - AMD LANCE and PCnet-based ISA Ethernet adapters [*], including: + Parallel Ports + Any standard parallel port + Communication Controllers + Universal Serial Bus host controllers, including: + USB Universal Host Controller + USB Open Host Controller + PCI `universal' communication cards, providing serial + and parallel ports, including: + Dolphin Peripherals 4014 (dual parallel) and + 4035 (dual serial) + SIIG Cyber 2P1S (dual parallel, single serial) + and 2S1P (dual serial, single parallel) + SIIG Cyber 4S (quad serial) + SIIG Cyber I/O (single parallel, single serial) + SIIG Cyber Parallel, Parallel Dual, Serial, + Serial Dual + VScom PCI-800 (8 port serial, probably OEM) + AT&T/Lucent Venus Modem (found on IBM 33L4618 + card, Actiontec 56K, and others) + US Robotics 3CP5609 PCI (modem) + Lava Computers 2SP-PCI (parallel port) + Lava Computers 2SP-PCI and Quattro-PCI (dual + serial) + NEC PK-UG-X008 (serial) + NEC PK-UG-X001 K56flex PCI (modem) + Koutech IOFLEX-2S (dual serial) + Ethernet Adapters + 3Com 3c501 + 3Com 3c503 + 3Com 3c505 [*] + 3Com 3c507 + 3Com 3c509, 3c579, and 3c59x + 3Com 3c515 [*] [+] + 3Com 3c9xx Etherlink XL adapters, including + 3Com 3c900/3c900B PCI adapters + 3Com 3c905/3c905B/3c905C PCI adapters + 3Com 3c980/3c980C server adapters + 3Com 3cSOHO apapter + 3Com 3c900B-FL and 3c900B-FL/FX fiber optic + adapters + 3Com 3c555/3c556/3c556B MiniPCI adapters + Dell on-board 3c920 + Dell Precision on-board 3c905B + Dell OptiPlex GX1 on-board 3c918 + Dell Latitude laptop docking station embedded + 3c905 + Adaptec "Starfire" AIC-6915 based PCI adapters, + including + Adaptec Single32 ANA-69011 + Adaptec Single64 ANA-62011 and ANA-62020 + Adaptec Duo64 ANA-62022 + Adaptec Quartet64 ANA-62044 + ADMtek AL981 ("Comet") and AN983 ("Centaur-P") based PCI + adapters, including: + Accton EN2242 MiniPCI + Linksys LNE100TX v4.x + Mototech ME316 + ADMtek AN986-based USB adapters, including: + Billionton Systems USB100 + Corega FEther USB-TX + D-Link DSB-650TX + LinkSys USB100TX + Melco Inc. LU-ATX + SMC 2202USB + Kingston KNU101TX + AMD LANCE and PCnet-based ISA Ethernet adapters, including: Novell NE1500T Novell NE2100 Kingston 21xx @@ -84,109 +231,245 @@ Supported devices {:-include-:}: BOCALANcard/PCI AT&T StarLAN 10, EN100, and StarLAN Fiber ASIX 88140A/88141 PCI Ethernet adapters, including: - CNet Pro110 + CNet Pro110B Alfa Inc. GFC2204 - 3COM 3c501 - 3COM 3c503 - 3COM 3c505 [*] - 3COM 3c507 - 3COM 3c509, 3c579, 3c589, 3c59x - 3COM 3c515 [*] [+] - 3COM 3c900, 3c900b, 3c905, and 3c905b, 3c905c + CATC USB-EL1210A-based USB adapters, including: + CATC Netmate and Netmate II + Belkin F5U011/F5U111 + Davicom DM9100, DM9102, and DM9102A based PCI adapters, + including: + Jaton XpressNet Digital DC21x4x-based PCI Ethernet adapters, including: - SMC EtherPower 10, 10/100 (PCI only!) - Znyx ZX34X - Cogent EM100 - Digital DE450 - Digital DE500 - BICC Isolan [* and not recently tested] + Older SMC PCI EtherPower 10, 10/100 (models + 8432, 9332, and 9334) + Older LinkSys 10, 10/100 (newer models are + supported by other drivers) + Znyx ZX3xx + Cogent EM100FX and EM440TX + Digital PCI DE435, EISA DE425, DE450, DE500 + Asante Intel EtherExpress 16 - SMC/WD 8003, 8013, and the SMC "Elite16" ISA boards - SMC/WD 8216 (the SMC "Elite16 Ultra" ISA boards) [X SEE BELOW] - SMC EtherPower II (EPIC 10/100) + Intel EtherExpross PRO/10 ISA + Intel i8255x-based (except the i82556) PCI adapters, + including: + Intel EtherExpress PRO/10+ + Intel EtherExpress PRO/100, PRO/100B, and PRO/100+ + Intel EtherExpress PRO/100+ "Management Adapter" + Intel EtherExpress PRO/100 Dual Port + Kawasaki LSI KL5KUSB101B-based USB adapters, including: + 3Com 3c19250 + 3Com 3c460 HomeConnect + ADS Technologies USB-10T + Aox USB101 + ATen UC10T + Corega USB-T + D-Link DSB-650 + Entegra NET-USB-E45 + Kawasaki USB101 + LinkSys USB10T + Netger EA101 + Peracom USB + SMC 2102/2104USB + I/O Data USB-ET/T + Lite-On PNIC/PNIC-II-based adapters, including: + Kingston KNE110TX + LinkSys LNE100TX + Matrox Networks FastNIC 10/100 + Netgear FA310TX + Macronix 98713/713A/715/715A/725/727/732-based adapters, + including: + Accton EN1217 + Addtron AEF-320TX/AEF-330TX + CNet PRO120A/PRO120B + Complex RL-100TX + NDC Communications SOHOware SFA110A + SVEC PN102-TX Fast Ethernet card + National Semiconductor DP83815-based PCI adapters, + including: + Netgear FA311/FA312 Novell NE1000, NE2000 - Digital DEFPA PCI FDDI adapters - Intel EtherExpress 100 Fast Ethernet adapters - Intel Pro/1000 Gigabit Ethernet adapters - Texas Instruments ThunderLAN PCI Ethernet adapters, including: - Compaq Netelligent PCI Adapters - Compaq NetFlex 3/P - Compaq Deskpro integrated adapter - Compaq Prosignia integrated adapter - Olicom OC2135, OC2183, OC2325, OC2326 - Racore 8165 and 8148 - TI ThunderLAN adapters RealTek 8129, RealTek 8139 Ethernet adapters, including: Accton MPX 5030/5038 Allied Telesyn AT2550 + D-Link DFE530+TX, DFE538TX Encore ENL832-TX 10/100 M PCI Genius GF100TXR KTX-9130TX 10/100 Fast Ethernet Longshine LCS-8038TX-R NDC NE100TX-E Netronix EA-1210 Net Ether 10/100 + Nortel BayStack 21 OvisLink LEF-8129TX, LEF-8139TX SMC EZ Card 10/100 PCI 1211-TX - Macronix 98713/98715/98725 Ethernet adapters, including: - NDC Communications SOHOware SFA110 - SVEC PN102-TX fast ethernet card - Lite-On PNIC/PNIC-II Ethernet adapters, including: - Bay Networks Netgear FA310TX rev D1 - LinkSys LNE100TX - Matrox Networks FastNIC 10/100 + SiS 900 and SiS 7016-based PCI adapters, including: + Mototech ME313 + NetSurf NS-KFE30D + SMC/WD 8003, 8013, and the SMC "Elite16" ISA boards + SMC/WD 8216 (the SMC "Elite16 Ultra" ISA boards) [X SEE BELOW] + SMC EtherEZ PNP + SMC EtherPower II (EPIC 10/100) + Sundance ST201-based PCI adapters, including: + D-Link DFE-550TX + Texas Instruments ThunderLAN PCI Ethernet adapters, including: + Compaq Netelligent PCI Adapters + Compaq NetFlex 3/P + Compaq Deskpro integrated adapter + Compaq Prosignia integrated adapter + Olicom OC2135, OC2183, OC2325, OC2326 + Racore 8165 and 8148 + TI ThunderLAN adapters + VIA Rhine/RhineII Ethernet adapters, including: + Addtron AEF-360TX + Hawking PN102TX + D-Link DFE530TX Winbond W89C840F Ethernet adapters, including: Trendware TE100-PCIE Compex RL100-ATX 10/100baseTX Xircom 16-bit PCMCIA adapters, including: Xircom CE3 Xircom Realport - Lucent technologies WaveLAN IEEE 802.11 [*] [+] + Wireless Ethernet Adapters + Aironet 802.11DS PCMCIA and PCI + RayLink Aviator 2.4/Pro 802.11FH PCMCIA + WaveLAN IEEE 802.11DS + Addtron AWP-100 802.11DS PCMCIA + Gigabit Ethernet Adapters + Alteon Tigon I/II PCI Gigabit Ethernet boards + 3Com 3c985 and 3c985B + Alteon ACEnic V (fiber and copper) + Digital EtherWORKS 1000SX + Farallon PN9000SX + Netgear GA620 and GA620T + SGI Tigon + Intel i82452-based adapters, including: + Intel Pro/1000 Gigabit Server adapter SysKonnect SK-9841/9842/9843/9844 Gigabit Ethernet - adapters [*] [+] - Tape drives: - Most SCSI tape drives - QIC-02 and QIC-36 format (Archive- and Wangtek- - compatible) tape drives [*] [+] - CD-ROM drives: - Mitsumi CD-ROM drives [*] [+] - [Note: The Mitsumi driver device probe is known - to cause trouble with several devices!] - Most SCSI CD-ROM drives - Most ATAPI CD-ROM drives - [Note: With single ATAPI device IDE busses, the - ATAPI device should be set to SLAVE.] - Mice: + adapters + ATM Adapters + Efficient Networks EN-155 and Adaptec ANA-590X ATM + interfaces + FDDI Adapters + Digital DEFEA EISA and PCI FDDI adapters + Wan Adapters + Lan Media Corporation SSI (T1)/HSSI/DS1/DS3 WAN + interfaces + Cryptography Accelerators + Broadcom Bluesteelnet uBsec 5501, 5601, 5805 + Hi/Fn 7751-based boards, including: + GTGI PowerCrypt Encryption Accelerator + NetSec 7751 + HiFn reference board + Invertex AEON + PC Cards (PCMCIA and Carbus) + ATA cards, including: + ATA/IDE card drives + ATA/IDE CD-ROM adapters + CF/ATA flash cards and disk drives + Ethernet adapters, including: + 3Com EtherLink and EtherLink XL-based LAN PC + cards, including: + 3Com 3c556, 3c562 + 3Com 3c574TX, 3c[CX]FE574BT + 3Com 3c589, 3c589[BCDE] + 3Com 3c575TX, 3c[CX]FE575[BC]T CardBus + 3Com 3c[CX]FEM656, 3c[CX]656[BC] CardBus + Intel/DEC 21443 "Tulip" clones, including: + ADMtex AN985 Centaur-C CardBus + IBM EtherJet 10/100 CardBus + SMC EZ CardBus 10/100 + Xircom X3201 CardBus adapters, including + RealPort models + Intel i8255x-based, including: + Intel PRO/100 CardBus II + NE2000-based, including: + Accton EN2216 + AmbiCom AMB8002T + D-Link DE-650, DE-660 + Genius ME 3000II SE + Hawking PN650TX + IC-Card + Kingston KNE-PC2 + Linksys PCMPC100, EC2T Combo + NDC Instant-Link + Netgear FA410TX + Network Everywhere NP10T + New Media LiveWire 10/100 + SMC 91Cxx-based, including: + Megahertz XJEM1144, CC10BT + SMC EtherEZ 8020BT + Xircom, including: + Xircom CreditCard CE2 + PCMCIA controllers, including: + Intel i82365 and compatibles + SCSI host adapters, including: + Adaptec SlimSCSI APA-14[56]0 + Serial ports, including: + Most modems, digital cellular modems, and serial + cards should work + Wireless Ethernet adapters: + See above + Universal Serial Bus (USB) Devices + USB Audio + USB Diamond Multimedia Rio MP3 players + USB Ethernet adapters, see above + USB Generic Human Interface Devices (catch-all) + USB Handspring Visor + USB Hubs + USB Keyboards + USB Mass Storage devices, i.e., USB floppy drives and + USB memory stick controllers + USB Mice + USB Modems + USB Printers + USB Scanners + USB-USB cables + USB Y@p phone + Pointing Devices "Logitech"-style bus mice [*] [+] "Microsoft"-style bus mice [*] [+] "PS/2"-style mice [*] [+] Serial mice (uses serial port driver) - Sound Cards: - SoundBlaster [*] [+] + compatible) tape drives [*] [+] + Sound Devices + C-Media CMI8[37]38 [*] [+] + Cirrus Logic CrystalClear CS4280, CS4281 [*] [+] + Ensoniq AudioPCI [*] [+] + ESS Tech ES188[78], ES888 [*] [+] + ESS Solo-1 PCI AudioDrive [*] [+] + ESS Maestro 1, 2 and 2E and clones, NOT Maestro 3 [*] [+] + Forte Media FM801 audio [*] [+] Gravis Ultrasound and Ultrasound Max [*] [+] - [The following drivers are not extensively tested] + Intel i810/i820 and 440MX AC'97 [*] [+] + NeoMagic 256AV/ZX [*] [+] + SoundBlaster ISA cards and 100% compatibles [*] [+] + SoundBlaster PCI128 [*] [+] + VIA VT82C686A SouthBridge integrated AC'97 audio [*] [+] + Yamaha OPL3-SA3 [*] [+] + Yamaha DS-XG [*] [+] + [The following drivers are not extensively tested:] Personal Sound System [*] [+] - Windows Sound System [*] [+] ProAudio Spectrum [*] [+] - ESS PnP audio cards [*] [+] - ESS Solo-1 PCI-based audio cards [*] [+] - AC'97 sound a part of Intel 810/815/440MX chipsets [*] [+] - Cryptography Accelerators - Hi/Fn 7751 based boards, including: - GTGI PowerCrypt Encryption Accelerator - Miscellaneous: - OPTi(82C929) chipset for multi-interface CD-ROM, and - sound ISA cards. - PCI-PCI bridges and cards which {:-include-:} them, such as - the AHA-394x SCSI host adapter and some - DC21x4x-based multi-Ethernet cards. + S3 SonicVibes [*] [+] + Windows Sound System [*] [+] + Miscellaneous Devices + APM power management, Brooktree 8[47][89] based frame grabber and TV tuner cards, - such as: [*] [+] + including: [*] [+] Hauppage Wincast TV STB TV PCI Television Tuner Miro PC TV Intel Smart Video Recorder III - APM v1.1 power management, - PCI BIOS v2.x interrupt and address configuration. + IMS TV Turbo + AVer Media TV/FM + Many kinds of ISA Plug-and-Play cards + Nearly all SB-style audio cards + Nearly all joystick ports + Nearly all Yamaha-style audio cards + Nearly all NE2000-style Ethernet cards + Nearly all SMC-style Ethernet cards + Most serial port or modem cards + 3c509 cards in PnP mode + NE2100 Etherent cards Drivers for hardware marked with "[*]" are NOT included on the distribution floppies. Except as noted above, all other drivers are @@ -202,24 +485,42 @@ although it is not in the kernel on the installation floppy. Hardware the we do NOT currently support, but get many questions about: - NCR 5380-based SCSI host adapters. - QIC-40 and QIC-80 tape drives. (Those are the tape drives - that connect to the floppy disk controller.) - Multiprocessor systems. (Though they should run fine using - one processor only.) + The "Micro Channel" MCA bus used in many IBM PS/2 models + NCR 5380-based and 53400-based SCSI host adapters + QIC-40 and QIC-80 tape drives (these are the tape drives + that connect to the floppy disk controller) + Multiprocessor motherboards (though they will run fine using + one processor only) + Sony and Panasonic proprietary CD-ROM interfaces + Parallel-port ZIP drives (SCSI and ATAPI ZIP drives work fine) + Intel i82556 (EtherExpress PRO/100A) and i82596 (EtherExpress + PRO/10 PCI) Ethernet adapters + Hewlett-Packard PC-LAN+ (HP27xxx) Ethernet adapters + SoundBlaster Live! (EMU10k1) sound devices + Aureal Vortex sound cards + Winmodems + Infrared devices, such as commonly found on laptops + Firewire + 3c990 Hardware Crypto Accelerators (3Com will not make specs + public) + Mylex and Intel RAID controllers + PCMCIA: + Memory cards + Most multifunction cards We are planning future support for many of these devices. -To be detected by the distributed kernels, the devices must -be configured as follows: +To be detected by the distributed kernels, some devices must +be configured with specific settings. Here's their list: Device Name Port IRQ DRQ Misc ------ ---- ---- --- --- ---- Serial ports pccom0 0x3f8 4 [8250/16450/16550/clones] pccom1 0x2f8 3 [8250/16450/16550/clones] pccom2 0x3e8 5 [8250/16450/16550/clones] - pccom3 0x2e8 3 [PCMCIA modem cards] ast0 0x1a0 5 [AST 4-port serial card] + cy0 12 iomem 0xd4000 [Cyclom + serial card] Parallel ports lpt0 0x378 7 [interrupt-driven or polling] lpt1 0x278 [polling only] @@ -236,12 +537,6 @@ AHA-154x, AHA-174x (in compatibility mode), or BT-54x SCSI host adapters aha0 0x330 any any aha1 0x334 any any -AHA-174x SCSI host adapters (in enhanced mode) - ahb0 any any any - -AHA-284x,274x,2940, aic7770 SCSI host adapters - ahc0 any any - BT445, BT74x, or BT9xx SCSI host adapters bt0 0x330 any any bt1 0x334 any any @@ -251,14 +546,11 @@ Ultrastor 14f, 24f (if it works), or 34f SCSI host adapters uha1 0x334 any any AHA-152x, AIC-6260- or AIC-6360-based SCSI host adapters - aic0 0x340 11 6 + aic0 0x340 11 any Seagate ST0[12], Future Domain TMC-8xx based SCSI controllers sea0 5 iomem 0xc8000 -Symbios Logic/NCR 53C8xx based PCI SCSI host adapters - ncr0 any any any - WD7000 and TMC-7000 SCSI host adapters wds0 0x350 15 6 wds1 0x358 11 5 @@ -274,28 +566,14 @@ SCSI tapes st0 first SCSI tape (by SCSI id) SCSI CD-ROMs cd0 first SCSI CD-ROM (by SCSI id) cd1 second SCSI CD-ROM (by SCSI id) -DPT SmartCache III/IV PCI/EISA adapters - dpt0 any any any - -ICP-Vortex GDT 6XXXRP series - gdt0 any any any - -3ware Escalade 3W-5x00, 3W-6x00 - twe0 any any any - -Adaptec FSA-based - aac0 any any any - -Compaq Smart ARRAY PCI/EISA adapters - cac0 any any any - SMC/WD 8003, 8013, Elite16, and Elite16 Ultra Ethernet boards - we0 0x280 9 - we1 0x300 10 + we0 0x280 9 iomem 0xd0000 + we1 0x300 10 iomem 0xcc000 Novell NE1000, or NE2000 Ethernet boards ne0 0x240 9 iomem 0xd8000 ne1 0x300 10 + ne2 0x280 9 3COM 3c501 Ethernet boards el0 0x300 9 @@ -306,49 +584,24 @@ Novell NE1000, or NE2000 Ethernet boards 3COM 3c505/Etherlink+ Ethernet boards eg0 0x310 5 -3COM 3c509, 3c579, 3c595 Ethernet boards - ep0 any any - -3COM 3c515 - ef0 any any - -3COM 3c900, 3c900b, 3c905, 3c905b Ethernet boards - xl0 any any [you must assign an interrupt in your - PCI BIOS, or let it do so for you] - AT&T StarLAN 10, EN100, or StarLAN Fiber, or 3COM 3c507 Ethernet boards ie0 0x360 7 iomem 0xd0000 EtherExpress boards ie1 0x300 10 -PCNet-PCI based Ethernet boards; see above for partial list - le0 any any [you must assign an interrupt in your - PCI BIOS, or let it do so for you] - -DC21x4x based Ethernet boards; see above for partial list - de0 any any [you must assign an interrupt in your - PCI BIOS, or let it do so for you] +IsoLan, NE2100, and DEPCA + le0 0x360 15 6 -Intel EtherExpress 100 Ethernet boards - fxp0 any any [you must assign an interrupt in your - PCI BIOS, or let it do so for you] +Intel EtherExpress PRO/10 + ex0 0x320 5 -SMC EtherPower II (EPIC) 10/100 Ethernet boards - tx0 any any [you must assign an interrupt in your - PCI BIOS, or let it do so for you] +PCI ethernet boards need to have an interrupt, either assigned in your +PCI BIOS, or autoconfigured. -DEC Tulip clones (Macronix, Lite-On, Davicom) - dc0 any any [you must assign an interrupt in your - PCI BIOS, or let it do so for you] +Hardware not listed in the above table doesn't need any specific +configuration. -Alteon Tigon I/II PCI Gigabit Ethernet boards - ti0 any any [you must assign an interrupt in your - PCI BIOS, or let it do so for you] - -SysKonnect 984x Gigabit Ethernet boards - sk0 any any [you must assign an interrupt in your - PCI BIOS, or let it do so for you] SPECIAL CARE FOR SMC ULTRA ELITE -------------------------------- @@ -437,4 +690,3 @@ Try to gather dmesg output from the failing configuration, for example by using serial console (see boot(8)) and send it to mickey@openbsd.org along with descriptions of your hardware setup. Dig in the code and fix problems. - diff --git a/distrib/notes/i386/install b/distrib/notes/i386/install index 50149abbbce..ada99a5e05e 100644 --- a/distrib/notes/i386/install +++ b/distrib/notes/i386/install @@ -34,10 +34,9 @@ OpenBSDInstallPart2 OpenBSDBootMsgs While booting, you will probably see several warnings. You - should be warned that no swap space is present, and that - init(8) cannot find /etc/rc. Do not be alarmed, these are - completely normal. When you reach the prompt asking you for a - shell name, just hit return. + should be warned that no swap space is present. Do not be + alarmed, these are completely normal. When you reach the prompt + asking you for a shell name, just hit return. Now you will be asked whether you wish to do an "install" or an "upgrade". Enter 'i' for a fresh install or 'u' to diff --git a/distrib/notes/i386/prep b/distrib/notes/i386/prep index 5006e0eb500..fea91d62ccf 100644 --- a/distrib/notes/i386/prep +++ b/distrib/notes/i386/prep @@ -55,7 +55,7 @@ OpenBSD. It is included in the i386 tools area of this distribution as a convenience. It is strongly advised that you read its documentation and understand the consequences of your actions before using it. In some cases, defragmenting your disk and running fips may be much faster than -reinstalling your DOS partitition from the backup. +reinstalling your DOS partition from the backup. Your hard disk is now prepared to have OpenBSD installed on it, and you should proceed with the installation instructions. diff --git a/distrib/notes/i386/upgrade b/distrib/notes/i386/upgrade index 7627db73e23..b8ae5b1a840 100644 --- a/distrib/notes/i386/upgrade +++ b/distrib/notes/i386/upgrade @@ -31,10 +31,9 @@ operating system's partition, before beginning the upgrade process. with the boot prompt (the "boot>" prompt), hit return. While booting, you will probably see several warnings. You should - be warned that no swap space is present, and that init(8) cannot - find /etc/rc. Do not be alarmed, these are completely normal. - When you reach the prompt asking you for a shell name, just hit - return. + be warned that no swap space is present. Do not be alarmed, + these are completely normal. When you reach the prompt asking + you for a shell name, just hit return. You will be presented with a welcome message and a prompt. If you are upgrading from a pre-OpenBSD 1.0 release, you should upgrade diff --git a/distrib/notes/i386/xfer b/distrib/notes/i386/xfer index 711b8f79875..42e4cd5f516 100644 --- a/distrib/notes/i386/xfer +++ b/distrib/notes/i386/xfer @@ -7,7 +7,6 @@ Installation is supported from several media types, including: Remote NFS partition FTP HTTP - rsh & restore No matter which installation medium you choose, you'll need to have a floppy disk (1.44Mb required). @@ -87,7 +86,7 @@ NFS, you must do the following: (Both of these actions will probably require superuser privileges on the server.) - You need to know the the numeric IP address of the NFS server, + You need to know the numeric IP address of the NFS server, and, if the server is not on a network directly connected to the machine on which you're installing or upgrading OpenBSD, you need to know the numeric IP address of the router closest diff --git a/distrib/notes/mac68k/contents b/distrib/notes/mac68k/contents index b2a83d97a68..741f0503423 100644 --- a/distrib/notes/mac68k/contents +++ b/distrib/notes/mac68k/contents @@ -9,12 +9,12 @@ OpenBSDdistsets DistributionDescription - bsd-generic.tgz The OpenBSD/MACHINE OSREV kernel binary. + bsd-generic.tgz The OpenBSD/mac68k OSREV kernel binary. You MUST install this file. It is the kernel that you need to boot the system. [ 1.4M uncompressed ] - bsd-genericsbc.tgz The OpenBSD/mac68k kernel binary. This is + bsd-genericsbc.tgz The OpenBSD/mac68k OSREV kernel binary. This is identical in every way to bsd-generic.tgz accept that it enables a different SCSI driver which may allow some otherwise incompatible SCSI disks to function @@ -61,4 +61,3 @@ this directory are as follows: A MacOS program to build BSD filesystems on various partitions you have created (see below). You will need this if you are performing a new installation. - diff --git a/distrib/notes/mac68k/hardware b/distrib/notes/mac68k/hardware index 9bffc91bd18..015e7d70e0a 100644 --- a/distrib/notes/mac68k/hardware +++ b/distrib/notes/mac68k/hardware @@ -46,9 +46,8 @@ Some systems will boot and are usable from an external terminal possibly others What isn't supported, but often asked about: - PowerPC-based Macs. Work will begin on this, sometime soon. - It will be separate from this port, though. The PowerPC - is a much different processor. + PowerPC-based Macs. They are supported by the OpenBSD/powerpc + port. Machines based on Apple's IOP technology including the Mac IIfx. Machines based on the 68LC040 processor. Unfortunately, the chip itself contains a major bug which is presently being worked diff --git a/distrib/notes/mac68k/install b/distrib/notes/mac68k/install index d9265201168..936e9140443 100644 --- a/distrib/notes/mac68k/install +++ b/distrib/notes/mac68k/install @@ -112,4 +112,3 @@ to a long-standing bug, the preferences will not be saved unless you quit. OpenBSDCongratulations - diff --git a/distrib/notes/mac68k/whatis b/distrib/notes/mac68k/whatis index bf04547a5d7..c37f65c4f84 100644 --- a/distrib/notes/mac68k/whatis +++ b/distrib/notes/mac68k/whatis @@ -1,4 +1,4 @@ -OpenBSD OSREV is the sixth release of OpenBSD for Macintosh +OpenBSD OSREV is a port to the old Macintosh (680x0-based) computers. As always, there is much to be done on this architecture, and help is very much appreciated. However, a wide variety of hardware and software is completely diff --git a/distrib/notes/mac68k/xfer b/distrib/notes/mac68k/xfer index d1618f33bd1..3f0891d3858 100644 --- a/distrib/notes/mac68k/xfer +++ b/distrib/notes/mac68k/xfer @@ -16,4 +16,3 @@ installer.hqx, and booter.sea.hqx, respectively. Extract them as you would any other Macintosh applications. The source code for these utilities should be in the same directory with the word "src" somewhere in the filename. - diff --git a/distrib/notes/powerpc/contents b/distrib/notes/powerpc/contents index 47dd8bad775..aa55ee85d5f 100644 --- a/distrib/notes/powerpc/contents +++ b/distrib/notes/powerpc/contents @@ -1,12 +1,14 @@ TopPart - cd{:--:}OSrev.fs The standard MACHINE boot and installation - CD image; see below. - OpenBSDdistsets OpenBSDbsd +OpenBSDrd + + cd{:--:}OSrev.fs The standard MACHINE boot and installation + CD image; see below. + There are several ways to boot a supported PowerPC Macintosh system into the OpenBSD installer. Unfortunately they all currently require some limited knowledge of Open Firmware, the low-level process that controls @@ -117,4 +119,3 @@ OpenBSDxshare(1.7M,8.1M) OpenBSDxfont(11.6M,7.3M) OpenBSDxserv(4.4M,5.4M) - diff --git a/distrib/notes/powerpc/install b/distrib/notes/powerpc/install index 5259936764b..d5f21501345 100644 --- a/distrib/notes/powerpc/install +++ b/distrib/notes/powerpc/install @@ -240,4 +240,3 @@ OpenBSDCommonFS OpenBSDCommonURL OpenBSDCongratulations - diff --git a/distrib/notes/powerpc/upgrade b/distrib/notes/powerpc/upgrade index 5cfada96ce3..68e28d0362c 100644 --- a/distrib/notes/powerpc/upgrade +++ b/distrib/notes/powerpc/upgrade @@ -1 +1,4 @@ -[Upgrades may not be well supported currently for the MACHINE port] +Be warned that upgrades may not be well supported currently for the +MACHINE port. + +OpenBSDUpgrade diff --git a/distrib/notes/powerpc/xfer b/distrib/notes/powerpc/xfer index a7902e50aea..fbdcb6e6374 100644 --- a/distrib/notes/powerpc/xfer +++ b/distrib/notes/powerpc/xfer @@ -14,7 +14,7 @@ the system can be installed from any of the above. While an installation floppy is included in the snapshot it is unlikely that it will be very useful due to lack of floppy drive on the imac -and the reported inabilty to boot from USB floppies on the supported +and the reported inability to boot from USB floppies on the supported version of the hardware. Obviously, the steps necessary to prepare the distribution sets for diff --git a/distrib/notes/sparc/contents b/distrib/notes/sparc/contents index 1909dfe08e2..c6140f5a967 100644 --- a/distrib/notes/sparc/contents +++ b/distrib/notes/sparc/contents @@ -13,7 +13,7 @@ OpenBSDrd bsd.scsi3 A kernel with SCSI target 3 re-mapped as 0 and 0 mapped as 3. - installboot The OpenBSD/sparc boot loader installation` + installboot The OpenBSD/sparc boot loader installation program bootxx The OpenBSD/sparc boot block boot The OpenBSD/sparc secondary boot loader diff --git a/distrib/notes/sparc/install b/distrib/notes/sparc/install index c4122684f61..e741c90a244 100644 --- a/distrib/notes/sparc/install +++ b/distrib/notes/sparc/install @@ -1,10 +1,9 @@ -Installing OpenBSD is a relatively complex process, but if you have -this document in hand it shouldn't be too much trouble. +OpenBSDInstallPrelude There are several ways to install OpenBSD onto a disk. The easiest way in terms of preliminary setup is to use the OpenBSD miniroot that can be booted off your local disk's swap partition. The normal way is to -use the OpenBSD installation floppy. +use the OpenBSD installation floppy, or an installation tape. If your Sparc is hooked up in a network and you can find a server to arrange for a diskless setup, which is a convenient way to install on a @@ -13,24 +12,8 @@ This is difficult to get set up correctly the first time, but easy to use afterwards. (see ``Installing using a diskless setup'' below). It is also possible to install OpenBSD "manually" from a running SunOS -system, using SunOS tools and gnu tar and gunzip (see ``Installing from SunOS'' -below). - - -This section of the install document is really broken into several parts: - - - booting from the installation media - - the floppy or miniroot install script - - after completing an installation - - installing from Sun OS - - net boot or diskless setup information - -The first section gets you up to the point where you've booted the kernel -from whatever media, to where you have to respond to prompts from the -install script(s). The next two sections describe the path through the -install scripts, and the remainder are notes which might be useful, but -outside the bounds of simple "how to" instructions. - +system, using SunOS tools and gnu tar and gunzip (see ``Installing from +SunOS'' below). Booting from the Installation Media: @@ -41,8 +24,8 @@ does not necessarily wipe out all the partitions on the hard disk, errors during the install process can have unforeseen consequences and you will probably render the system unbootable if you start, but do not complete the installation. Having the installation media for the prior installation, -be it a SunOS or OpenBSD CD-ROM or OpenBSD install diskettes is good insurance -if you want to be able to "go back" for some reason. +be it a SunOS or OpenBSD CD-ROM or OpenBSD install diskettes is good +insurance if you want to be able to "go back" for some reason. After taking care of all that, bring your system down gracefully using the shutdown(8) and/or halt(8) commands. This will get you to the monitor @@ -84,10 +67,6 @@ Booting from Floppy Disk installation media: ok boot floppy bsd # for version 2 OpenBOOT ROMs This will cause the kernel contained in the floppy to be booted. -After the kernel loads, it will eject the bootable floppy and prompt -for a filesystem floppy - for the two floppy installation insert -the appropriate filesystem floppy, for the ramdisk installation, -just hit return, the filesystem image is internal to the kernel. After the initial device probe messages you'll asked to start the install or upgrade procedure. Proceed to the section ``Running the @@ -108,8 +87,8 @@ activity, but no messages or complaints about magic numbers, checksums or formats. Not all sparc systems support bootable CDROMS and the current -boot image is only known to work on sun4c architectures. If it -does not work, you'll have to create a boot floppy or bootable +boot image is only known to work on sun4c and sun4m architectures. +If it does not work, you'll have to create a boot floppy or bootable hard disk using the instructions under preparing boot media. After the initial device probe messages you'll asked to start the @@ -117,7 +96,7 @@ install or upgrade procedure. Proceed to the section ``Running the installation scripts'' below. -Booting from SCSI disk (miniroot or floppy image) +Booting from SCSI disk (miniroot or floppy image): Boot the miniroot by typing the appropriate command at the PROM: @@ -146,7 +125,7 @@ install or upgrade procedure. Proceed to the section ``Running the installation scripts'' below. -Booting from SCSI tape +Booting from SCSI tape: Boot the miniroot by typing the appropriate command at the PROM: @@ -174,7 +153,7 @@ install or upgrade procedure. Proceed to the section ``Running the installation scripts'' below. -Installing using a diskless setup. +Installing using a diskless setup: First, you must setup a diskless client configuration on a server. If you are using a OpenBSD system as the boot-server, have a look at the @@ -200,13 +179,7 @@ scripts'' below. Installing using the Floppy, CD-ROM, tape, miniroot or netboot procedure: -The following is a walk-through of the steps you will take while -getting OpenBSD installed on your hard disk. If any question has a -default answer, it will be displayed in brackets ("[]") after the -question. If you wish to stop the installation, you may hit Control-C -at any time, but if you do, you may have to begin the installation -process again from scratch. Using Control-Z to suspend the process -may be a better option. +OpenBSDInstallPart2 Boot your machine from the installation media as described above. @@ -217,14 +190,7 @@ may be a better option. is bad, your diskless setup isn't correct, or you may have a hardware or configuration problem. - You will then be presented with the OpenBSD kernel boot - messages. You will want to read them to determine your - disk's name and geometry. Its name will be something like - "sd0" or "wd0" and the geometry will be printed on a line that - begins with its name. As mentioned above, you will need your - disk's geometry when creating OpenBSD partitions. You will - also need to know the device name to tell the install tools - what disk to install on. +OpenBSDBootMsgs While booting, you will probably see several warnings. You may be warned that the kernel can't figure out what device @@ -241,10 +207,7 @@ may be a better option. installing from a keyboard/monitor console, the default of "sun" if correct. If you are installing from a serial console you should choose the terminal type from amongst those listed. - (If your terminal type is xterm, just use vt100). Next you - will be prompted for a choice of which text editor to use at - several places in the install script. You will probably want - to use "vi" if your terminal supports this. + (If your terminal type is xterm, just use vt100). After entering the terminal type you will be greeted by a welcome message and asked if you really want to continue. @@ -390,10 +353,6 @@ In order to use 'tip' on OpenBSD/sparc, you'll need to edit /etc/ttys and add "local" to the end of the tty configuration line, and run 'ttyflags -a' to put your changes into effect. -On installing X11 for OpenBSD/sparc, you may wish to add a line similar to -'ldconfig /usr/X11R6/lib' to the end of your /etc/rc.local file. This will -add the X libraries to your dynamic linking search path at boot time. - If you are unfamiliar with UN*X-like system administration, it's recommended that you buy a book that discusses it. @@ -404,7 +363,8 @@ Installing from SunOS. You need a SunOS machine to install OpenBSD. You also need at least the following pieces: - the *.tgz files you want to install (as a minimum, base{:--:}OSrev.tgz) + the *.tgz files you want to install (as a minimum, base{:--:}OSrev.tgz and + etc{:--:}OSrev.tgz) gunzip (GNU gzip) SunOS binary gtar (GNU tar) SunOS binary a "/boot" file from a SunOS machine that matches your machine type @@ -419,21 +379,22 @@ OpenBSD/sparc uses SunOS disk labels.) Give yourself adequate partition sizes. Here is an example layout: partition size offset will be.. - sd2a 28140 0 / - sd2b 16170 28140 swap - sd2c 204540 0 `whole disk' - sd2g 160230 44310 /usr - -BTW, These are not recommended sizes. They simply match the first -(tiny) disk that OpenBSD/sparc ran on. + sd0a 80000 0 / + sd0b 256000 80000 swap + sd0c 4165271 0 `whole disk' + sd0d 100000 436000 /var + sd0f 100000 336000 /tmp + sd0g 3229271 936000 /usr + sd0h 400000 536000 /var/tmp Use SunOS to newfs the partitions which will have filesystems on them. (OpenBSD's filesystem format is identical to SunOS). - sunos# newfs /dev/rsd2a - [... lots of output] - sunos# newfs /dev/rsd2g + sunos# newfs /dev/rsd0a [... lots of output] + +Repeat for any other partition (in this example, /dev/rsd0d, /dev/rsd0f, +/dev/rsd0g, /dev/rsd0h). NOTE: If you are able to, there is a performance benefit from newfs'ing using OpenBSD. If you newfs using the OpenBSD newfs command, @@ -447,8 +408,11 @@ Mount those partitions in a tree formation, under /mnt; ie: sunos# df Filesystem kbytes used avail capacity Mounted on [...] - /dev/sd2a 11501 0 11501 0% /mnt - /dev/sd2g 179529 0 179529 0% /mnt/usr + /dev/sd0a 38427 0 38427 0% /mnt + /dev/sd0d 48249 0 48249 0% /mnt/var + /dev/sd0f 48249 0 48249 0% /mnt/tmp + /dev/sd0g 1564024 0 1564024 0% /mnt/usr + /dev/sd0h 193536 0 193536 0% /mnt/var/tmp Place a standard SunOS "boot" program in /mnt (your new root partition), and use the SunOS command "installboot" to make it work. @@ -472,10 +436,11 @@ And finally copy an OpenBSD kernel (either bsd or bsd.scsi3) onto your disk. sunos# cp bsd.scsi3 /mnt/bsd The GNU gunzip and gtar programs are not distributed as part of SunOS, -but may be present in your local/bin. If not, you will need to obtain -them from a GNU archive and install before proceeding. The OpenBSD -tar files are in the "new format" that includes directory information, -and the standard SunOS tar will not extract from them successfully. +but may be present in your /usr/local/bin. If not, you will need to +obtain them from a GNU archive and install before proceeding. The +OpenBSD tar files are in the "new format" that includes directory +information, and the standard SunOS tar will not extract from them +successfully. After the files have been extracted, setup /mnt/etc/fstab to match your actual disk layout. (Minus the "/mnt" component of each path, of diff --git a/distrib/notes/sparc/prep b/distrib/notes/sparc/prep index bf973a767ef..8475815a6fe 100644 --- a/distrib/notes/sparc/prep +++ b/distrib/notes/sparc/prep @@ -80,14 +80,14 @@ both OpenBSD and SunOS environments on the same system. about missing . and .. entries. Do *not* try to "correct" these problems, as attempting to do so will completely trash the filesystem. - You should avoid using the new OpenBSD "-s enable" option to the - "tunefs" command, which enable the soft update feature. + You should avoid using soft updates (option softdep in /etc/fstab) + on your shared filesystems. Although untested, it is likely that SunOS would be confused by a filesystem with soft update flags enabled. The OpenBSD "Sun Compatible" disklabel have been extended to support 16 partitions, which may be compatible with Solaris, but the old SunOS -format(8) utility only sees the first 8 partititions and may "lose" +format(8) utility only sees the first 8 partitions and may "lose" information about the extended partitions. Use SunOS format(8) only with *extreme* caution on drives that contain diff --git a/distrib/notes/sparc/upgrade b/distrib/notes/sparc/upgrade index b9682976f4d..b7ee9ee41a7 100644 --- a/distrib/notes/sparc/upgrade +++ b/distrib/notes/sparc/upgrade @@ -1,11 +1 @@ -To upgrade to OpenBSD OSREV from a previous version start with the general -instructions in the section "Installing OpenBSD". - -If you are upgrading with the miniroot or the new single floppy image, -select the (U)pdate option rather than the (I)nstall option at the prompt -in the install process. - -The upgrade script will use the existing disk partitions to install the -new system in, and also preserves files in `/etc' which you are likely -to have customized since a previous installation. - +OpenBSDUpgrade({:- or the installation floppy-:}) diff --git a/distrib/notes/sparc/xfer b/distrib/notes/sparc/xfer index b5228455ce8..41a53611a28 100644 --- a/distrib/notes/sparc/xfer +++ b/distrib/notes/sparc/xfer @@ -8,17 +8,15 @@ Installation is supported from several media types, including: HTTP Not all methods are supported on all Sparc Systems and some of them -work only with the single-floppy installation or the miniroot -installation. - +work only with the floppy or the miniroot installation. If you have the OpenBSD CD-ROM distribution (and a CD-ROM drive), you may be able boot from it. Not all sparc systems support booting from -CD-ROM and the current boot images is only known to work on Sun4c -architecture workstations such as the IPC, SS1 or SS2. If you can boot -from the CD-ROM, you are home free and can proceed to the installation -steps. If not, you will need to do some setup work to prepare a bootable -image, either a floppy, hard drive, or compatible net boot server. +CD-ROM and the current boot images is only known to work on sun4c and +some sun4m architecture workstations. If you can boot from the CD-ROM, +you are home free and can proceed to the installation steps. If not, +you will need to do some setup work to prepare a bootable image, either +a floppy, hard drive, or compatible net boot server. In addition to the bootable image, you also need to consider how to access the binary distribution sets to actually install the system. If @@ -61,7 +59,7 @@ Creating a bootable floppy disk using DOS/Windows: errors. Note that if you are using NT to write the images to disk, you - will need to use ntrw.exe instead. It is also availible in the + will need to use ntrw.exe instead. It is also available in the "tools" directory. Grab it and run in with the correct arguments like this "ntrw <image> <drive>:" @@ -273,7 +271,7 @@ NFS, you must do the following: (Both of these actions will probably require superuser privileges on the server.) - You need to know the the numeric IP address of the NFS server, + You need to know the numeric IP address of the NFS server, and, if the server is not on a network directly connected to the machine on which you're installing or upgrading OpenBSD, you need to know the numeric IP address of the router closest @@ -302,4 +300,3 @@ following: Once you have done this, you can proceed to the next step in the upgrade process, actually upgrading your system. - diff --git a/distrib/notes/sun3/contents b/distrib/notes/sun3/contents index 951c08ac571..ea13e8f6253 100644 --- a/distrib/notes/sun3/contents +++ b/distrib/notes/sun3/contents @@ -20,15 +20,14 @@ the OpenBSD System onto Useful Media" for instructions on either method. DistributionDescription -OpenBSDbase(19.4,61.9M) +OpenBSDbase(21.1M,63.6M) -OpenBSDcomp(13.1M,40.6M) +OpenBSDcomp(14.2M,42.0M) -OpenBSDetc(988K,3.2M) +OpenBSDetc(1.0M,3.2M) -OpenBSDgame(2.6M,6.4M) +OpenBSDgame(2.8M,6.6M) -OpenBSDman(4.8M,18.4M) - -OpenBSDmisc(1.6M,5.5M) +OpenBSDman(5.4M,19.5M) +OpenBSDmisc(1.7M,5.6M) diff --git a/distrib/notes/sun3/hardware b/distrib/notes/sun3/hardware index db348b60287..71bc0fdd9c4 100644 --- a/distrib/notes/sun3/hardware +++ b/distrib/notes/sun3/hardware @@ -1,16 +1,18 @@ OpenBSD/sun3 OSREV runs on most Sun3 machines, including: - 3/50, 3/60, 3/110 - 3/75, 3/140, 3/150, 3/160, 3/180 - 3/260, 3/280 + 3/50 + 3/60, 3/60LE + 3/75, 3/110, 3/1[4568]0 + 3/2[68]0 -OpenBSD/sun3 OSREV does not run on the Sun3/80 and Sun3/4x0 (sun3x +OpenBSD/sun3 OSREV does not run on the Sun 3/80 and Sun 3/4x0 (sun3x class) because the sun3x MMU and other devices are very different. The minimal configuration requires 4M of RAM and ~80MB of disk space. -To install the entire system requires much more disk space (approx. -100MB additional space is necessary for full sources). To run X -or compile the system, more RAM is recommended. Good performance -requires 8MB of RAM, or 16 MB when running the X Window System. +To install the entire system requires much more disk space (at least +200MB is recommended, without counting the additional space necessary +for sources or packages). To run X or compile the system, more memory +is recommended. Acceptable performance requires 8MB of RAM, or 16 MB +when running the X Window System. The following Sun3 hardware is supported: @@ -28,9 +30,9 @@ The following Sun3 hardware is supported: On-board "si" (SCSI-3) VME "si" (SCSI-3) board - SMD Disks: (the big, heavy ones) + SMD Disks Controlers: Xylogics 450/451 - Xylogics 753/7053 + Xylogics 750/7053 Input devices: Sun keyboard and mouse @@ -38,4 +40,4 @@ The following Sun3 hardware is supported: Miscellaneous: Battery-backed real-time clock. -If it's not on this list, there is no support for it in this release. +Hardware not listed here is likely to be unsupported by this release. diff --git a/distrib/notes/sun3/install b/distrib/notes/sun3/install index 37b2b2375a5..507b1f2d170 100644 --- a/distrib/notes/sun3/install +++ b/distrib/notes/sun3/install @@ -1,5 +1,4 @@ -Installing OpenBSD is a relatively complex process, but if you have -this document in hand it shouldn't be too much trouble. +OpenBSDInstallPrelude There are several ways to install OpenBSD onto a disk. The easiest way in terms of preliminary setup is to use the OpenBSD miniroot that can @@ -16,24 +15,6 @@ system, using SunOS tools and gnu tar and gunzip (see ``Installing from SunOS'' below). -This section of the install document is really broken into several parts: - - - booting from the installation media - - the miniroot install script - - after completing an installation - - installing from Sun OS - - net boot or diskless setup information - -The first section explains how to run tho install scripts. The second -section gets you up to the point where you've booted the kernel from -whatever media or setup described in the previous section, to where you -have to respond to prompts from the install script. The next section -describes the path through the install script, and the remainder are -notes which might be useful, but outside the bounds of simple "how to" -instructions. - - - Booting from the Installation Media: Prior to attempting an installation, you should make sure that everything @@ -67,7 +48,7 @@ install or upgrade procedure. Proceed to the section ``Running the installation scripts'' below. -Installing using a diskless setup +Installing using a diskless setup: First, you must setup a diskless client configuration on a server. If you are using a OpenBSD system as the boot-server, have a look at the @@ -92,68 +73,56 @@ scripts'' below. In order to have a sun3 machine boot diskless by default, you need to do some nvram wizardry: - > q - 18 + > q 18 12 +then, if your machine is a model 3/50 or 3/60, continue with: 6c 65 00 00 00 +or, for other sun3 machines: + 69 + 65 + 00 + 00 + 00 +and return to the prom prompt with: q > -The miniroot install script: +The above set of commands has changed the boot path strategy to the +network interface, thus a diskless boot. +To change the strategy in diagnostic mode (when the "Diag/Norm" switch +is set to "Diag"), enter the same set of data after a "q 22" command +instead of "q 18". +Remember that the prom having a limited number of write cycles, you +shouldn't abuse this feature. -The following is a walk-through of the steps you will take while -getting OpenBSD installed on your hard disk. If any question has a -default answer, it will be displayed in brackets ("[]") after the -question. If you wish to stop the installation, you may hit Control-C -at any time, but if you do, you may have to begin the installation -process again from scratch. Using Control-Z to suspend the process -may be a better option. + +OpenBSDInstallPart2 Boot your machine from the installation media as described above. - It will take a while to load the kernel especially from a floppy - or slow network connection, most likely more than a minute. If + It will take a while to load the kernel especially from a + slow network connection, 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 medias is probably bad, your diskless setup isn't correct or you may have a hardware or configuration problem. - You will then be presented with the OpenBSD kernel boot - messages. You will want to read them to determine your - disk's name and geometry. Its name will be something like - "sd0" or "wd0" and the geometry will be printed on a line that - begins with its name. As mentioned above, you will need your - disk's geometry when creating OpenBSD partitions. You will - also need to know the device name to tell the install tools - what disk to install on. +OpenBSDBootMsgs While booting, you will probably see several warnings. You may be warned that the kernel can't figure out what device it booted from and that no swap space is present. Do not be - alarmed, these are completely normal. The first warning - occurs because while OpenBSD/sun3 can boot from the floppy - drive, the kernel itself lacks a floppy driver for some - architectures. - - When the loading process is complete, the boot floppy will be - ejected and you will be prompted to insert a filesystem floppy, - just hit return since the filesystem is contained in the kernel - image just loaded. Next there will be a prompt asking you for - a shell name, just hit return to start executing the installation - setup script. + alarmed, these are completely normal. You will next be asked for your terminal type. If you are installing from a keyboard/monitor console, the default of "sun" if correct. If you are installing from a serial console you should choose the terminal type from amongst those listed. - (If your terminal type is xterm, just use vt100). Next you - will be prompted for a choice of which text editor to use at - several places in the install script. You will probably want - to use "vi" if your terminal supports this. + (If your terminal type is xterm, just use vt100). After entering the terminal type you will be greeted by a welcome message and asked if you really want to continue. @@ -252,32 +221,16 @@ OpenBSDCommonFS OpenBSDCommonURL -After completing an installation: - -Now try a reboot. (If needed, swap your scsi id's first). Initially -I'd suggest you "boot sd()bsd -bs", then try multiuser after that. -if you boot single-user the OpenBSD incantation to make the root -filesystem writable is - - OpenBSD# mount -u /dev/sd0a / - OpenBSDCongratulations If you will be running your OpenBSD system from a serial console, you may need to edit /etc/ttys and change the terminal type, and getty method from -"sun" and "console" to "vt100" and "std.9600" or something similar. Also -when running from a serial console, you may wish to adjust the eeprom -settings for input-device, output-device, screen-#columns, and screen-#rows -as appropriate. +"sun" and "console" to "vt100" and "std.9600" or something similar. In order to use 'tip' on OpenBSD/sun3, you'll need to edit /etc/ttys and add "local" to the end of the tty configuration line, and run 'ttyflags -a' to put your changes into effect. -On installing X11 for OpenBSD/sun3, you may wish to add a line similar to -'ldconfig /usr/X11R6/lib' to the end of your /etc/rc.local file. This will -add the X libraries to your dynamic linking search path at boot time. - If you are unfamiliar with UN*X-like system administration, it's recommended that you buy a book that discusses it. @@ -288,10 +241,11 @@ Installing from SunOS. You need a SunOS machine to install OpenBSD. You also need at least the following pieces: - the *.tgz files you want to install (as a minimum, base{:--:}OSrev.tgz) + the *.tgz files you want to install (as a minimum, base{:--:}OSrev.tgz and + etc{:--:}OSrev.tgz) gunzip (GNU gzip) SunOS binary gtar (GNU tar) SunOS binary - a "/boot" file from a SunOS machine + a "/boot" file from a SunOS sun3 machine (not sun3x!) a kernel, most likely "/bsd" All these pieces, except "/boot" and the GNU utilities are supplied in @@ -302,22 +256,22 @@ OpenBSD/sun3 uses SunOS disk labels.) Give yourself adequate partition sizes. Here is an example layout: partition size offset will be.. - sd0a 48825 0 / - sd0b 69825 48825 swap - sd0c 639450 0 `whole disk' - sd0d 65625 118650 /var - sd0g 455175 184275 /usr - -FYI, this particular disk setup is used on a model 3/60 connected -to a shoebox with a Micropolis 1558 ESDI drive. + sd0a 80000 0 / + sd0b 256000 80000 swap + sd0c 4165271 0 `whole disk' + sd0d 100000 436000 /var + sd0f 100000 336000 /tmp + sd0g 3229271 936000 /usr + sd0h 400000 536000 /var/tmp Use SunOS to newfs the partitions which will have filesystems on them. (OpenBSD's filesystem format is identical to SunOS). sunos# newfs /dev/rsd0a [... lots of output] - sunos# newfs /dev/rsd0g - [... lots of output] + +Repeat for any other partition (in this example, /dev/rsd0d, /dev/rsd0f, +/dev/rsd0g, /dev/rsd0h). NOTE: If you are able to, there is a performance benefit from newfs'ing using OpenBSD. If you newfs using the OpenBSD newfs command, @@ -331,16 +285,19 @@ Mount those partitions in a tree formation, under /mnt; ie: sunos# df Filesystem kbytes used avail capacity Mounted on [...] - /dev/sd0a 11501 0 11501 0% /mnt - /dev/sd0g 179529 0 179529 0% /mnt/usr + /dev/sd0a 38427 0 38427 0% /mnt + /dev/sd0d 48249 0 48249 0% /mnt/var + /dev/sd0f 48249 0 48249 0% /mnt/tmp + /dev/sd0g 1564024 0 1564024 0% /mnt/usr + /dev/sd0h 193536 0 193536 0% /mnt/var/tmp Place a standard SunOS "boot" program in /mnt (your new root partition), and use the SunOS command "installboot" to make it work. The installboot man page says to do something like this: - sunos# cp /usr/mdec/sdboot /mnt/boot + sunos# cp /usr/mdec/ufsboot /mnt/boot sunos# sync; sync - sunos# /usr/mdec/installboot -vlt /mnt/boot /usr/mdec/bootsd /dev/rsd0a + sunos# /usr/mdec/installboot -vlt /mnt/boot /usr/mdec/bootxx /dev/rsd0a You can now extract the provided "*.tgz files onto your disk. @@ -356,10 +313,11 @@ And finally copy the OpenBSD kernel onto your disk. sunos# cp bsd /mnt/bsd The GNU gunzip and gtar programs are not distributed as part of SunOS, -but may be present in your /usr/local/bin. If not, you will need to obtain -them from a GNU archive and install before proceeding. The OpenBSD -tar files are in the "new format" that includes directory information, -and the standard SunOS tar will not extract from them successfully. +but may be present in your /usr/local/bin. If not, you will need to +obtain them from a GNU archive and install before proceeding. The +OpenBSD tar files are in the "new format" that includes directory +information, and the standard SunOS tar will not extract from them +successfully. After the files have been extracted, setup /mnt/etc/fstab to match your actual disk layout. (Minus the "/mnt" component of each path, of @@ -451,4 +409,3 @@ A few configuration files need to be edited: Now you must populate the the `/dev' directory for your client. For this, you can simply change your working directory to `<root>/dev' and run the MAKEDEV script: `sh MAKEDEV all'. - diff --git a/distrib/notes/sun3/prep b/distrib/notes/sun3/prep index 2b1b66e5edf..5d32d360413 100644 --- a/distrib/notes/sun3/prep +++ b/distrib/notes/sun3/prep @@ -1,11 +1,9 @@ - Sun3 machines usually need little or no preparation before installing OpenBSD, other than the usual, well advised precaution of BACKING UP ALL DATA on any attached storage devices. You will need to know the SCSI target ID of the drive on which you -will install OpenBSD. Note that SunOS/sun3 uses confusing names for -the SCSI devices: target 1 is sd2, target 2 is sd4, etc. +will install OpenBSD. It might be a good time to run the diagnostics on your Sun3. First, attach a terminal to the "ttya" serial port, then set the "Diag/Norm" @@ -13,9 +11,10 @@ switch to the Diagnostic position, and power-on the machine. The Diag. switch setting forces console interaction to occur on ttya. The console location (ttya, ttyb, or keyboard/display) is controlled -by address 0x1F in the EEPROM, which you can examine and change in -the PROM monitor by entering "q1f" followed by a numeric value (or -just a '.' if you don't want to change it). Console values are: +by address 0x1f in the EEPROM, which you can examine and change in +the PROM monitor by entering "q 1f", then a numeric value (or just a +'.' if you don't want to change it, and "q" again to return to the prom). +Console values are: 00: default graphics display 10: tty a (9600-N-8-1) 11: tty b (1200-N-8-1) @@ -23,9 +22,6 @@ just a '.' if you don't want to change it). Console values are: OpenBSD will use the EEPROM setting to determine which device to use as the console, so you should make sure it is correct. -Before you start you might need to consider your disk configuration -to sort out a quirk in SCSI-ID to SD-UNIT mapping that exists on -Sun Sparcstations. Please note that while OpenBSD and SunOS have a reasonable degree of compatibility between disk labels and filesystems there are some problems @@ -44,24 +40,20 @@ both OpenBSD and SunOS environments on the same system. about missing . and .. entries. Do *not* try to "correct" these problems, as attempting to do so will completely trash the filesystem. - You should avoid using the new OpenBSD "-s enable" option to the - "tunefs" command, which enable the soft update feature. + You should avoid using softupdates (option softdep in /etc/fstab) + on your shared filesystems. Although untested, it is likely that SunOS would be confused by a filesystem with soft update flags enabled. The OpenBSD "Sun Compatible" disklabel have been extended to support 16 -partitions, which may be compatible with Solaris, but the old SunOS -format(8) utility only sees the first 8 partititions and may "lose" -information about the extended partitions. +partitions, however the old SunOS format(8) utility only sees the first +8 partitions and may "lose" information about the extended partitions. Use SunOS format(8) only with *extreme* caution on drives that contain OpenBSD partitions. - OpenBSD and Sun BSD bootblocks are similar in concept, though implemented differently. The OpenBSD bootblocks are architecture independent and also understand the extended disklabels with 16 partitions. You can use SunOS bootblocks, but remember that OpenBSD bootblocks must be installed with OpenBSD installboot and SunOS bootblocks with SunOS installboot. - - diff --git a/distrib/notes/sun3/upgrade b/distrib/notes/sun3/upgrade index 64a8f222f25..81ae6caa65e 100644 --- a/distrib/notes/sun3/upgrade +++ b/distrib/notes/sun3/upgrade @@ -1,10 +1 @@ -To upgrade to OpenBSD OSREV from a previous version start with the general -instructions in the section "Installing OpenBSD". - -After booting with the miniroot, select the (U)pdate option rather than -the (I)nstall option at the prompt in the install process. - -The upgrade script will use the existing disk partitions to install the -new system in, and also preserves files in `/etc' which you are likely -to have customized since a previous installation. - +OpenBSDUpgrade diff --git a/distrib/notes/sun3/whatis b/distrib/notes/sun3/whatis index d2880197e56..1e438c90cad 100644 --- a/distrib/notes/sun3/whatis +++ b/distrib/notes/sun3/whatis @@ -1,20 +1,2 @@ - -OpenBSD OSREV is the second release of OpenBSD for the sun3, -including a full set of binaries. This binary distribution is -referred to elsewhere in this document by the name OpenBSD/sun3. - -This release offers the following features: - -* Native boot programs for disk, network, and tape -* Automated installation tools (using a "miniroot") -* SCSI driver supporting DMA, interrupts, and - disconnect/reselect with SCSI-2 devices (optional) -* Frame buffer drivers for bwtwo, cgtwo, cgfour, - all compatible with SunOS and the X Window System -* Support for the Virtually Addressed Cache (VAC) on - Sun3/260 models (and vastly improved performance) -* SMD disk drivers -* SunOS 4.1 compatibility (runs most Sun3 applications) -* Supports most SCSI devices (CD-ROM, etc) -* Diskless boot capability - +OpenBSD/sun3 OSREV is a port to the ``sun3'' series of workstations +manufactured by Sun in the late 1980s. diff --git a/distrib/notes/sun3/xfer b/distrib/notes/sun3/xfer index aaf79f0ebd7..c9fba3bb2a1 100644 --- a/distrib/notes/sun3/xfer +++ b/distrib/notes/sun3/xfer @@ -144,7 +144,7 @@ NFS, you must do the following: (Both of these actions will probably require superuser privileges on the server.) - You need to know the the numeric IP address of the NFS server, + You need to know the numeric IP address of the NFS server, and, if the server is not on a network directly connected to the machine on which you're installing or upgrading OpenBSD, you need to know the numeric IP address of the router closest @@ -173,4 +173,3 @@ following: Once you have done this, you can proceed to the next step in the upgrade process, actually upgrading your system. - diff --git a/distrib/notes/vax/xfer b/distrib/notes/vax/xfer index 097a1f9b36b..6075e277e6d 100644 --- a/distrib/notes/vax/xfer +++ b/distrib/notes/vax/xfer @@ -22,7 +22,7 @@ NFS, you must do the following: (Both of these actions will probably require superuser privileges on the server.) - You need to know the the numeric IP address of the NFS server, + You need to know the numeric IP address of the NFS server, and, if the server is not on a network directly connected to the machine on which you're installing or upgrading OpenBSD, you need to know the numeric IP address of the router closest |