=================================================================== RCS file: /cvsrepo/anoncvs/cvs/www/36.html,v retrieving revision 1.1 retrieving revision 1.2 diff -c -r1.1 -r1.2 *** www/36.html 2004/08/26 02:32:24 1.1 --- www/36.html 2004/08/26 09:39:56 1.2 *************** *** 28,66 **** ISBN 0-9731791-4-7

!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!

www@openbsd.org
! $OpenBSD: 36.html,v 1.1 2004/08/26 02:32:24 deraadt Exp $ --- 28,524 ---- ISBN 0-9731791-4-7

! What's New
! How to install
! How to use the ports tree
! Ordering a CD set
+

+ To get the files for this release: +
+
Order a CDROM from our ordering system. +
See the information on The FTP page for + a list of mirror machines. +
Go to the pub/OpenBSD/3.6/ directory on + one of the mirror sites. +
Briefly read the rest of this document. + +
See a detailed log of changes between the + 3.5 and 3.6 releases. +
+

+
+ + Note: All applicable copyrights and credits can be found + in the applicable file sources found in the files src.tar.gz, sys.tar.gz, + XF4.tar.gz, or in the files fetched via ports.tar.gz. The distribution + files used to build packages from the ports.tar.gz file are not included on + the CDROM because of lack of space. +

+ +

What's New

+ 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. +

+ +

New platform: +
- OpenBSD/luna88k
  + Expanding the mvme88k porting effort by supporting Omron's line of + 88100-based workstations. +
+
+ +
SMP support on OpenBSD/i386 and OpenBSD/amd64 platforms. +
+ +
New functionality: +
- A new dhcp + server + and + client + implementation, featuring privilege separation and safe defaults. +
- A clean + ntp + daemon which ought to fit the needs of most ntp users. +
- pfctl + now provides a rules optimizer, to help improving filtering speed. +
+
+ +
Improved hardware support, including: +
- Sangoma T1 and E1 cards + (san) +
- Jumbo frames are now working reliably on + em, + sk + and + ti + adapters. +
- USB 2.0 + (ehci) + controllers. +
- AIC79xx-based Ultra320 SCSI adapters, such as the Adaptec 29320 and + 39320 + (ahd) +
+
+ +
Improved NFS performance and reliability. + +
Shared libraries on the OpenBSD/hppa port. + +
Over 2700 ports, 2500 pre-built packages. +
+ +
Many improvements for security and reliability (look for the red + print in the complete changelog). +
+ +
As ususal, many improvements in manual pages and other documentation. +
+ +
Gcc 3.3.2, including local additions like ProPolice support, for the + OpenBSD/amd64, + OpenBSD/cats, + OpenBSD/hppa and + OpenBSD/sparc64 + platforms. + Other architectures still use gcc 2.95.3 with the same local additions. +
+
OpenSSH 3.9: +
- sshd now re-executes itself on accepting a new connection. This security + measure ensures that all execute-time randomisations are reapplied for each + connection rather than once, for the master process' lifetime. This includes + mmap and malloc mappings, shared library addressing, shared library mapping + order, ProPolice and StackGhost cookies on architectures that support + such things. +
- Selected environment variables can now be passed between the + client and the server. +
- Session multiplexing: a single ssh connection can now carry + multiple login/command/file transfer sessions. +
+
+ +
The system includes the following major components from outside suppliers: +
- XFree86 4.4.0 unencumbered (+ patches, and i386 contains 3.3.X servers also, thus + providing support for all chipsets) +
- Gcc 2.95.3 + (+ patches) + and 3.3.2 + (+ patches) +
- Perl 5.8.5 (+ patches) +
- Apache 1.3.29, mod_ssl 2.8.16, DSO support (+ patches) +
- OpenSSL 0.9.7d (+ patches) +
- Groff 1.15 +
- Sendmail 8.13.0, with libmilter +
- Bind 9.2.3 (+ patches) +
- Lynx 2.8.5rel.2 with HTTPS and IPv6 support (+ patches) +
- Sudo 1.6.7p5 +
- Ncurses 5.2 +
- Latest KAME IPv6 +
- Heimdal 0.6rc1 (+ patches) +
- Arla 0.35.7 +
- Gdb 6.1 +
+
+ +

+ + +

How to install

+ 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 + of) install are very similar; the CDROM instructions are left intact + so that you can see how much easier it would have been if you had + purchased a CDROM instead. +

+ +

+ Please refer to the following files on the three CDROMs or ftp mirror for + extensive details on how to install OpenBSD 3.6 on your machine: +

CD1:3.6/i386/INSTALL.i386 +
CD1:3.6/vax/INSTALL.vax +
+
CD2:3.6/amd64/INSTALL.amd64 +
CD2:3.6/macppc/INSTALL.macppc +
+
CD3:3.6/sparc/INSTALL.sparc +
CD3:3.6/sparc64/INSTALL.sparc64 +
+
FTP:.../OpenBSD/3.6/alpha/INSTALL.alpha +
FTP:.../OpenBSD/3.6/cats/INSTALL.cats +
FTP:.../OpenBSD/3.6/hp300/INSTALL.hp300 +
FTP:.../OpenBSD/3.6/hppa/INSTALL.hppa +
FTP:.../OpenBSD/3.6/luna88k/INSTALL.luna88k +
FTP:.../OpenBSD/3.6/mac68k/INSTALL.mac68k +
FTP:.../OpenBSD/3.6/mvme68k/INSTALL.mvme68k +
FTP:.../OpenBSD/3.6/mvme88k/INSTALL.mvme88k +

+ +

+ 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! +

+ +

OpenBSD/i386:

CD1:3.6/i386/floppy36.fs

+ Use CD1:3.6/i386/floppyB36.fs instead for greater scsi controller + support, or CD1:3.6/i386/floppyC36.fs for better laptop support. + +

+ If you can't boot from a CD or a floppy disk, + you can install across the network using PXE as described in + the included INSTALL.i386 document. + +

+ If you are planning on dual booting OpenBSD with another OS, you will need to + read INSTALL.i386. + +

+ 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 + FAQ4.1. +

+ +

OpenBSD/vax:

+ Boot over the network via mopbooting as described in INSTALL.vax. + + +

OpenBSD/amd64:

CD2:3.6/amd64/floppy36.fs

+ If you can't boot from a CD or a floppy disk, + you can install across the network using PXE as described in the included + INSTALL.amd64 document. + +

+ If you are planning to dual boot OpenBSD with another OS, you will need to + read INSTALL.amd64. +

+ +

OpenBSD/macppc:

OpenBSD/macppc boot

+ Alternatively, at the Open Firmware prompt, enter boot cd:,ofwboot + /3.6/macppc/bsd.rd +

+ +

OpenBSD/sparc:

+ ok boot cdrom 3.6/sparc/bsd.rd
+ or
+ > b sd(0,6,0)3.6/sparc/bsd.rd
+

+ If your sparc does not have a CD drive, you can alternatively boot from floppy. + To do so you need to write CD3:3.6/sparc/floppy36.fs to a floppy. + For more information see FAQ4.1. To boot from + the floppy use one of the two commands listed below, depending on the version of + your ROM. + +

+ ok boot floppy
+ or
+ > b fd()
+

+ Make sure you use a properly formatted floppy with NO BAD BLOCKS or your install + will most likely fail. + +

+ If your sparc 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. +

+ +

OpenBSD/sparc64:

boot cdrom

+ If this doesn't work, or if you don't have a CDROM drive, you can write + CD3:3.6/sparc64/floppy36.fs to a floppy and boot it with boot + floppy.
+ Make sure you use a properly formatted floppy with NO BAD BLOCKS or your install + will most likely fail. + +

+ You can also write CD3:3.6/sparc64/miniroot36.fs to the swap partition on + the disk and boot with boot disk:b. + +

+ If nothing works, you can boot over the network as described in INSTALL.sparc64 +

+ +

OpenBSD/alpha:

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. + +

+ Make sure you use a properly formatted floppy with NO BAD BLOCKS or your install + will most likely fail. + +

+ +

OpenBSD/cats:

+ 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). +

+ +

OpenBSD/hp300:

+ Boot over the network by following the instructions in INSTALL.hp300. +

+ +

OpenBSD/hppa:

+ Boot over the network by following the instructions in INSTALL.hppa or the + hppa platform page. +

+ +

OpenBSD/luna88k:

+ 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. +

+ +

OpenBSD/mac68k:

+ 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 + filesystems on the A/UX partitions you just made. Then, use the + "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. +

+ +

OpenBSD/mvme68k:

+ 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. +

+ +

OpenBSD/mvme88k:

+ 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. +

+ +

Notes about the source code:

+ # 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. +

+ +

Ports Tree

+ 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 + if you know nothing about ports + at this point. This text is not a manual of how to use ports. + Rather, it is a set of notes meant to kickstart the user on the + 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 + order to keep current with it, you must make the ports/ tree + available on a read-write medium and update the tree with a command + like: +

+ # cd [portsdir]/; cvs -d anoncvsserver.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 + server.] +

+ Note that most ports are available as packages through ftp. Updated + packages for the 3.6 release will be made available if problems arise. +

+ 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. +

+ +

www@openbsd.org
! $OpenBSD: 36.html,v 1.2 2004/08/26 09:39:56 miod Exp $