=================================================================== RCS file: /cvsrepo/anoncvs/cvs/www/36.html,v retrieving revision 1.59 retrieving revision 1.60 diff -c -r1.59 -r1.60 *** www/36.html 2019/04/24 15:54:53 1.59 --- www/36.html 2019/05/27 22:55:18 1.60 *************** *** 1,30 **** ! ! !
Released November 1, 2004
Copyright 1997-2004, Theo de Raadt.
! ISBN 0-9731791-4-7
3.6 Song: "Pond-erosa Puff (live)"
--- 1,42 ----
!
!
!
!
! ! |
Released November 1, 2004 Copyright 1997-2004, Theo de Raadt. ! ISBN 0-9731791-4-7 3.6 Song: "Pond-erosa Puff (live)" *************** *** 32,38 ****
|
This is a partial list of new features and systems included in OpenBSD 3.6. For a comprehensive list, see the changelog leading to 3.6. *************** *** 72,106 ****
!
!
--- 195,208 ----
*************** *** 206,212 ****
-
Following this are the instructions which you would have on a piece of paper if you had purchased a CDROM set instead of doing an alternate form of install. The instructions for doing an ftp (or other style --- 259,272 ----
Following this are the instructions which you would have on a piece of paper if you had purchased a CDROM set instead of doing an alternate form of install. The instructions for doing an ftp (or other style *************** *** 285,298 ****
Quick installer information for people familiar with OpenBSD, and the use of the "disklabel -E" command. If you are at all confused when installing OpenBSD, read the relevant INSTALL.* file as listed above! -
!
Quick installer information for people familiar with OpenBSD, and the use of the "disklabel -E" command. If you are at all confused when installing OpenBSD, read the relevant INSTALL.* file as listed above! !
Play with your BIOS options to enable booting from a CD. The OpenBSD/i386 release is on CD1. If your BIOS does not support booting from CD, you will need to create a boot floppy to install from. To create a boot floppy write *************** *** 314,345 ****
To make a boot floppy under MS-DOS, use the "rawrite" utility located at CD1:3.6/tools/rawrite.exe. To make the boot floppy under a Unix OS, ! use the dd(1) utility. The following is an example usage of ! dd(1) , where the device could be "floppy", "rfd0c", or "rfd0a". !
! # dd if=<file> of=/dev/<device> bs=32k !
Make sure you use properly formatted perfect floppies with NO BAD BLOCKS or your install will most likely fail. For more information on creating a boot floppy and installing OpenBSD/i386 please refer to this page. -
-
-
To make a boot floppy under MS-DOS, use the "rawrite" utility located at CD1:3.6/tools/rawrite.exe. To make the boot floppy under a Unix OS, ! use the dd(1) ! utility. The following is an example usage of ! dd(1) , where the device could be "floppy", "rfd0c", or "rfd0a". !
! # dd if=<file> of=/dev/<device> bs=32k !
Make sure you use properly formatted perfect floppies with NO BAD BLOCKS or your install will most likely fail. For more information on creating a boot floppy and installing OpenBSD/i386 please refer to this page. +
Boot over the network via mopbooting as described in INSTALL.vax. +
The 3.6 release of OpenBSD/amd64 is located on CD2. Boot from the CD to begin the install - you may need to adjust your BIOS options first. *************** *** 355,385 ****
If you are planning to dual boot OpenBSD with another OS, you will need to read INSTALL.amd64. -
-
Alternatively, at the Open Firmware prompt, enter boot cd:,ofwboot /3.6/macppc/bsd.rd -
-
! ok boot cdrom 3.6/sparc/bsd.rd or ! > b sd(0,6,0)3.6/sparc/bsd.rd !
If your SPARC system does not have a CD drive, you can alternatively boot from floppy. --- 370,398 ----
If you are planning to dual boot OpenBSD with another OS, you will need to read INSTALL.amd64. +
Put the CD2 in your CDROM drive and poweron your machine while holding down the C key until the display turns on and shows OpenBSD/macppc boot.
Alternatively, at the Open Firmware prompt, enter boot cd:,ofwboot /3.6/macppc/bsd.rd +
The 3.6 release of OpenBSD/sparc is located on CD3. To boot off of this CD you can use one of the two commands listed below, depending on the version of your ROM. !
! ok boot cdrom 3.6/sparc/bsd.rd or ! > b sd(0,6,0)3.6/sparc/bsd.rd !
If your SPARC system does not have a CD drive, you can alternatively boot from floppy. *************** *** 388,398 **** the floppy use one of the two commands listed below, depending on the version of your ROM. !
! ok boot floppy or ! > boot fd() !
Make sure you use a properly formatted floppy with NO BAD BLOCKS or your install --- 401,411 ---- the floppy use one of the two commands listed below, depending on the version of your ROM. !
! ok boot floppy or ! > boot fd() !
Make sure you use a properly formatted floppy with NO BAD BLOCKS or your install *************** *** 402,412 **** If your SPARC system doesn't have a floppy drive nor a CD drive, you can either setup a bootable tape, or install via network, as told in the INSTALL.sparc file. -
-
--- 415,424 ---- If your SPARC system doesn't have a floppy drive nor a CD drive, you can either setup a bootable tape, or install via network, as told in the INSTALL.sparc file. +
Put the CD3 in your CDROM drive and type boot cdrom.
*************** *** 422,433 ****
If nothing works, you can boot over the network as described in INSTALL.sparc64 -
!
Write FTP:3.6/alpha/floppy36.fs or FTP:3.6/alpha/floppyB36.fs (depending on your machine) to a diskette and enter boot dva0. Refer to INSTALL.alpha for more details. --- 434,444 ----
If nothing works, you can boot over the network as described in INSTALL.sparc64 +
! Write FTP:3.6/alpha/floppy36.fs or FTP:3.6/alpha/floppyB36.fs (depending on your machine) to a diskette and enter boot dva0. Refer to INSTALL.alpha for more details. *************** *** 435,479 **** Make sure you use a properly formatted floppy with NO BAD BLOCKS or your install will most likely fail. !
-
After updating the firmware to at least ABLE 1.95 if necessary, boot FTP:3.6/cats/bsd.rd from an ABLE-supported device (such as a CD-ROM or an existing FFS or EXT2FS partition). -
-
Boot over the network by following the instructions in INSTALL.hp300. -
-
Boot over the network by following the instructions in INSTALL.hppa or the hppa platform page. -
-
Copy bsd.rd to a Mach or UniOS partition, and boot it from the PROM. Alternatively, you can create a bootable tape and boot from it. Refer to the instructions in INSTALL.luna88k for more details. -
-
Boot MacOS as normal and partition your disk with the appropriate A/UX configurations. Then, extract the Macside utilities from FTP:3.6/mac68k/utils onto your hard disk. Run Mkfs to create your --- 446,479 ---- Make sure you use a properly formatted floppy with NO BAD BLOCKS or your install will most likely fail. !
After updating the firmware to at least ABLE 1.95 if necessary, boot FTP:3.6/cats/bsd.rd from an ABLE-supported device (such as a CD-ROM or an existing FFS or EXT2FS partition). +
Boot over the network by following the instructions in INSTALL.hp300. +
Boot over the network by following the instructions in INSTALL.hppa or the hppa platform page. +
Copy bsd.rd to a Mach or UniOS partition, and boot it from the PROM. Alternatively, you can create a bootable tape and boot from it. Refer to the instructions in INSTALL.luna88k for more details. +
Boot MacOS as normal and partition your disk with the appropriate A/UX configurations. Then, extract the Macside utilities from FTP:3.6/mac68k/utils onto your hard disk. Run Mkfs to create your *************** *** 481,561 **** "BSD/Mac68k Installer" to copy all the sets in FTP:3.6/mac68k/ onto your partitions. Finally, you will be ready to configure the "BSD/Mac68k Booter" with the location of your kernel and boot the system. -
-
You can create a bootable installation tape or boot over the network.
The network boot requires a MVME68K BUG version that supports the NIOT
and NBO debugger commands. Follow the instructions in INSTALL.mvme68k
for more details.
-
-
You can create a bootable installation tape or boot over the network.
The network boot requires a MVME88K BUG version that supports the NIOT
and NBO debugger commands. Follow the instructions in INSTALL.mvme88k
for more details.
-
-
-
- # mkdir -p /usr/src - # cd /usr/src - # tar xvfz /tmp/src.tar.gz --
sys.tar.gz contains a source archive starting at /usr/src/sys. This file contains all the kernel sources you need to rebuild kernels. To extract:
-
- # mkdir -p /usr/src/sys - # cd /usr/src - # tar xvfz /tmp/sys.tar.gz --
Both of these trees are a regular CVS checkout. Using these trees it is possible to get a head-start on using the anoncvs servers as described here. Using these files results in a much faster initial CVS update than you could expect from a fresh checkout of the full OpenBSD source tree. -
-
If you already have an OpenBSD 3.5 system, and do not want to reinstall, upgrade instructions and advice can be found in the Upgrade Guide. -
-
A ports tree archive is also provided. To extract:
!
! # cd /usr ! # tar xvfz /tmp/ports.tar.gz ! # cd ports !
The ports/ subdirectory is a checkout of the OpenBSD ports tree. Go read the ports page --- 481,563 ---- "BSD/Mac68k Installer" to copy all the sets in FTP:3.6/mac68k/ onto your partitions. Finally, you will be ready to configure the "BSD/Mac68k Booter" with the location of your kernel and boot the system. +
You can create a bootable installation tape or boot over the network.
The network boot requires a MVME68K BUG version that supports the NIOT
and NBO debugger commands. Follow the instructions in INSTALL.mvme68k
for more details.
+
You can create a bootable installation tape or boot over the network.
The network boot requires a MVME88K BUG version that supports the NIOT
and NBO debugger commands. Follow the instructions in INSTALL.mvme88k
for more details.
+
src.tar.gz contains a source archive starting at /usr/src. This file contains everything you need except for the kernel sources, which are in a separate archive. To extract: + +
++ # mkdir -p /usr/src + # cd /usr/src + # tar xvfz /tmp/src.tar.gz +
sys.tar.gz contains a source archive starting at /usr/src/sys. This file contains all the kernel sources you need to rebuild kernels. To extract: + +
++ # mkdir -p /usr/src/sys + # cd /usr/src + # tar xvfz /tmp/sys.tar.gz +
Both of these trees are a regular CVS checkout. Using these trees it is possible to get a head-start on using the anoncvs servers as described here. Using these files results in a much faster initial CVS update than you could expect from a fresh checkout of the full OpenBSD source tree. !
If you already have an OpenBSD 3.5 system, and do not want to reinstall, upgrade instructions and advice can be found in the Upgrade Guide. +
A ports tree archive is also provided. To extract:
!
! # cd /usr ! # tar xvfz /tmp/ports.tar.gz ! # cd ports !
The ports/ subdirectory is a checkout of the OpenBSD ports tree. Go read the ports page *************** *** 565,571 **** OpenBSD ports system.
The ports/ directory represents a CVS (see the manpage for ! cvs(1) if you aren't familiar with CVS) checkout of our ports. As with our complete source tree, our ports tree is available via anoncvs. So, in --- 567,573 ---- OpenBSD ports system.
The ports/ directory represents a CVS (see the manpage for ! cvs(1) if you aren't familiar with CVS) checkout of our ports. As with our complete source tree, our ports tree is available via anoncvs. So, in *************** *** 573,581 **** available on a read-write medium and update the tree with a command like:
!
! # cd [portsdir]/; cvs -d anoncvs@server.openbsd.org:/cvs update -Pd -rOPENBSD_3_6 !
[Of course, you must replace the local directory and server name here with the location of your ports collection and a nearby anoncvs --- 575,583 ---- available on a read-write medium and update the tree with a command like:
!
! # cd [portsdir]/; cvs -d anoncvs@server.openbsd.org:/cvs update -Pd -rOPENBSD_3_6 !
[Of course, you must replace the local directory and server name here with the location of your ports collection and a nearby anoncvs *************** *** 587,593 **** If you're interested in seeing a port added, would like to help out, or just would like to know more, the mailing list ports@openbsd.org is a good place to know. !
! ! ! --- 589,592 ---- If you're interested in seeing a port added, would like to help out, or just would like to know more, the mailing list ports@openbsd.org is a good place to know. !