File: [local] / www / 42.html (download) (as text)
Revision 1.96, Wed May 6 13:31:34 2020 UTC (4 years ago) by deraadt
Branch: MAIN
CVS Tags: HEAD
Changes since 1.95: +1 -2 lines
be less different from other similar files
|
<!doctype html>
<html lang=en id=release>
<meta charset=utf-8>
<title>OpenBSD 4.2</title>
<meta name="description" content="OpenBSD 4.2">
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="stylesheet" type="text/css" href="openbsd.css">
<link rel="canonical" href="https://www.openbsd.org/42.html">
<h2 id=OpenBSD>
<a href="index.html">
<i>Open</i><b>BSD</b></a>
4.2
</h2>
<table>
<tr>
<td>
<a href="images/Marathon.jpg">
<img width="227" height="343" src="images/Marathon.jpg" alt="Marathon"></a>
<td>
Released Nov 1, 2007<br>
Copyright 1997-2007, Theo de Raadt.<br>
<cite class=isbn>ISBN 978-0-9784475-0-2</cite>
<br>
4.2 Song: <a href="lyrics.html#42">"100001 1010101"</a>
<br>
<br>
<ul>
<li>See the information on <a href="ftp.html">the FTP page</a> for
a list of mirror machines.
<li>Go to the <code class=reldir>pub/OpenBSD/4.2/</code> directory on
one of the mirror sites.
<li>Have a look at <a href="errata42.html">The 4.2 Errata page</a> for a list
of bugs and workarounds.
<li>See a <a href="plus42.html">detailed log of changes</a> between the
4.1 and 4.2 releases.
</ul>
<p>
All applicable copyrights and credits are in the src.tar.gz,
sys.tar.gz, xenocara.tar.gz, ports.tar.gz files, or in the
files fetched via <code>ports.tar.gz</code>.
</table>
<hr>
<section id=new>
<h3>What's New</h3>
<p>
This is a partial list of new features and systems included in OpenBSD 4.2.
For a comprehensive list, see the <a href="plus42.html">changelog</a> leading
to 4.2.
<p>
<ul>
<li>New/extended platforms:
<ul>
<li><a href="sparc64.html">OpenBSD/sparc64</a>.<br>
The PCIe UltraSPARC IIIi machines like the V215 and V245 are now
supported.
<li><a href="hppa.html">OpenBSD/hppa</a>.<br>
Four-digit B/C/J-class workstations like the B2000, C3750 or J6750
are now supported (in 32-bit mode).
<li><a href="alpha.html">OpenBSD/alpha</a>.<br>
Add support in the alpha platform for a couple of new Alpha
models, AlphaServer 1200 and 4100.
</ul>
<p>
<li>Platforms skipped this release:
<ul>
<li><a href="sgi.html">OpenBSD/sgi</a>.<br>
Due to various issues, this architecture will not be released
this time.
</ul>
<p>
<li>Improved hardware support, including:
<ul>
<li> Native Serial-ATA support:
<ul>
<li><a href="https://man.openbsd.org/ahci.4">ahci(4)</a>
driver for SATA controllers conforming to the Advanced Host Controller
Interface specification.
<li><a href=https://man.openbsd.org/jmb.4>jmb(4)</a> driver for the JMicron JMB36x SATA II and PATA Host Controller.
<li><a href="https://man.openbsd.org/sili.4">sili(4)</a>
driver for SATA controllers using the Silicon Image 3124/3132/3531 SATALink
chipsets.
</ul>
<li>The <a href="https://man.openbsd.org/pciide.4">pciide(4)</a> driver has had support added for newer chipsets, including:
<ul>
<li>Intel ICH8M PATA
<li>JMicron JMB36x PATA
<li>VIA CX700/VX700 PATA
</ul>
<li>The <a href="https://man.openbsd.org/lm.4">lm(4)</a>
driver now supports Winbond W83627DHG and W83627EHF-A Super I/O Hardware Monitors.
<li> The <a
href="https://man.openbsd.org/siop.4">siop(4)</a>
driver now has support for NCR 53C720/770 controllers in big endian mode.
In particular this means that the onboard Fast-Wide SCSI on many hppa
machines is supported now.
<li> New <a href="https://man.openbsd.org/tht.4">tht(4)</a>
driver for Tehuti Networks 10Gb Ethernet controllers.
<li> The <a
href="https://man.openbsd.org/malo.4">malo(4)</a>
driver now supports Marvell 88W8385 802.11g based Compact Flash devices.
<li> New <a
href="https://man.openbsd.org/uts.4">uts(4)</a>
driver for USB touch screens, and the <a
href="https://man.openbsd.org/xtsscale.=1">xtsscale(1)</a>
calibration utility.
<li> The <a
href="https://man.openbsd.org/i810.4">i810(4)</a>
X.Org driver and the PCI AGP driver now support Intel i965GM chips.
<li> New <a
href="https://man.openbsd.org/sparc64/led.4">led(4)</a>
driver for the front panel LEDs on the V215/245.
<li> New <a
href="https://man.openbsd.org/sparc64/bbc.4">bbc(4)</a>
driver providing support for the BootBus Controllers in UltraSparc III systems.
<li> New <a
href="https://man.openbsd.org/sparc64/pmc.4">pmc(4)</a>
driver for the
<a href="https://man.openbsd.org/watchdog.4">
watchdog(4)</a> timer on the National Semiconductor PC87317 SuperIO chip.
<li>New <a href=https://man.openbsd.org/sparc64/pyro.4>pyro(4)</a> driver for the SPARC64 Host/PCIe bridge.
<li>New <a href=https://man.openbsd.org/hppa/astro.4>astro(4)</a> driver for the Astro Memory and I/O controller on hppa.
<li>New <a href=https://man.openbsd.org/hppa/elroy.4>elroy(4)</a> driver for the Elroy PCI hostbridge on hppa.
<li>New <a href=https://man.openbsd.org/hppa/lcd.4>lcd(4)</a> driver for the front panel LCD display on hppa.
<li>New <a href=https://man.openbsd.org/hppa/ssio.4>ssio(4)</a> driver for the National Semiconductor PC87560 Legacy IO on hppa.
<li>New <a href=https://man.openbsd.org/zaurus/pxammc.4>pxammc(4)</a> driver for the MMC/SD/SDIO controller on zaurus.
<li>New <a href=https://man.openbsd.org/macppc/xlights.4>xlights(4)</a> driver for the front panel lights on the Xserve G4.
<li>New <a href=https://man.openbsd.org/macppc/sysbutton.4>sysbutton(4)</a> driver for the system identification button on the Xserve G4.
<li>New <a href=https://man.openbsd.org/i386/piixpcib.4>piixpcib(4)</a> driver for System Management Mode initiated speedstep frequency scaling on certain pairings of the Intel PIIX4 ISA bridges and Intel Pentium 3 processors.
<li>CPU frequency and voltage can now be scaled on all CPUs when running GENERIC.MP on a multiprocessor i386 or AMD64 machine with enhanced speedstep or powernow.
<li>Intel enhanced speedstep is now supported on OpenBSD/amd64.
<li>New support for the on die CPU temperature sensor found on the Intel Core family of processors.
<li>The <a href=https://man.openbsd.org/amd64/nvram.4>nvram(4)</a> driver is now available on OpenBSD/amd64.
</ul>
<p>
<li>New tools:
<ul>
<li> <a
href="https://man.openbsd.org/cwm.1">cwm(1)</a>
has replaced wm2 as a simple-looking low-resource window manager.
<li> <a
href="https://man.openbsd.org/zless.1">zless(1)</a>,
view compressed files with
<a href="https://man.openbsd.org/less.1">less(1)</a>.
<li><a href=https://man.openbsd.org/mount_vnd.8>mount_vnd(8)</a>, a utility to configure vnode disks from <a href=https://man.openbsd.org/fstab.5>fstab(5)</a>.
</ul>
<p>
<li>New functionality:
<ul>
<li>FFS2, the updated version of the fast file system.
<li><a
href="https://man.openbsd.org/ftp.1">ftp(1)</a>
now can send cookies loaded from a netscape-like cookiejar, supports
proxies requiring a password, and has a keep-alive option to avoid
overly aggressive control connection dropping.
<li><a href="https://man.openbsd.org/pkg_add.1">pkg_add(1)</a> has been vastly improved. It is more robust, outputs more
consistent error messages, and can deal with a lot more update scenarios
gracefully. It also has much better look-up capabilities for multiple entries
in <code>PKG_PATH</code>, stopping at the first directory with suitable
candidates.
<li><a
href="https://man.openbsd.org/ftp-proxy.8">ftp-proxy(8)</a>
is now able to automatically tag packets passing through the <a
href="https://man.openbsd.org/pf.4">pf(4)</a> rule with a supplied name.
<li>Kernel work queues,
<a href=https://man.openbsd.org/workq_add_task.9>workq_add_task(9)</a>,
<a href=https://man.openbsd.org/workq_create.9>workq_create(9)</a>,
<a href=https://man.openbsd.org/workq_destroy.9>workq_destroy(9)</a> provides a mechanism to defer tasks to a process context when it is impossible to run such a task in the current context.
<li><a href="https://man.openbsd.org/ifconfig.8">ifconfig(8)</a>
now understands IP address/mask in CIDR notation.
<li>Add IP (v4 and v6) load balancing to <a href="https://man.openbsd.org/carp.4">carp(4)</a>, similar to the ARP balancing.
<li><a href="https://man.openbsd.org/sensorsd.8">sensorsd(8)</a>
now supports a zero-configuration monitoring and has a more intuitive logging
for all sensors that automatically provide sensor state. It also features
advancements in user-specified monitoring, including monitoring of sensors
that are periodically flagged as invalid.
<li><a href="https://man.openbsd.org/sensorsd.conf.5">sensorsd.conf(5)</a>
now supports sensor matching by sensor type, allowing easier configuration.
<li>The i386 bootloader can now load amd64 kernels.
<li>The amd64 bootloader can now load i386 kernels.
</ul>
<p>
<li>Assorted improvements and code cleanup:
<ul>
<li>Huge performance improvements in the network stack, including:
<ul>
<li>In pf, store routing table ID, queue ID etc directly in the packet header mbuf instead of using
mbuf tags (which use malloc'd memory). This yields a 100% improvement in pf performance.
<li>Packet forwarding can skip IPSEC stack if no IPSEC flows are defined. This
yields a further 5% improvement in packet forwarding performance.
<li>Skip TCP/UDP/ICMP/ICMP6 checksumming when not necessary.
This yields a further 10% improvement in pf performance.
<li>A change in the way the kernel random pool is stirred greatly increases
performance with network interface cards that support interrupt mitigation, especially
on architectures where reading the clock is expensive (such as amd64).
<li>Enable interrupt holdoff on <a href="https://man.openbsd.org/sis.4">sis(4)</a>
chips that support it. Significant performance gain for slower CPU devices with sis(4), such as Soekris.
</ul>
<li>Large (>1TB) disk and partition support in the disklabel and buffer cache
code and in the userland utilities that manipulate disk blocks. Note
that some parts of the system are not 64-bit disk block clean yet, so partition
larger than 2TB cannot be used at the moment.
<li>Large (>2^32-1 sectors) SCSI disk sizes now probed.
<li>Thread support for the Objective-C library (libobjc).
<li><a href="https://man.openbsd.org/carp.4">carp</a>
route handling has been fixed, solving some problems the routing daemons were exhibiting.
<li>i386 TLB handling improved to avoid possible corruption on Core2Duo processors.
<li>Rework TLB shootdown code for i386 and amd64, gives fairly large speed
improvements.
<li>i386 and amd64 use the BIOS disk geometry when creating default disklabels.
<li>Default disk geometry changed from 64 heads/32 sectors to 255 heads/63 sectors.
<li>More usb devices with various quirks coaxed to work.
<li>Archive/Wangtek cartridge tape drives (wt*) no longer supported.
<li><a href="https://man.openbsd.org/rcs.1">rcs</a> has improved GNU compatibility.
<li><a href="https://man.openbsd.org/make.1">make(1)</a> has improved stability of -j option.
<li><a href="https://man.openbsd.org/isakmpd.8">isakmpd(8)</a> now allows key exchange with RSA signature authentication to work with Cisco IOS.
<li>Fixed <a href="https://man.openbsd.org/isakmpd.8">isakmpd(8)</a> interop-issues with peers, that start rekeying on port 4500 for NAT-T (e.g. Cisco, Openswan)
<li>The stability of <a href="alpha.html">OpenBSD/alpha</a> has been greatly improved.
<li>The stability of <a href="hppa.html">OpenBSD/hppa</a> has been greatly improved.
</ul>
<p>
<li>Install/Upgrade process changes:
<ul>
<li>Allow the specification of an NTP server during installation.
<li>Allow no fsck'ing of clean non-root partitions during upgrade.
<li>Check for INSTALL.<arch> to confirm sets are for the correct architecture.
<li>Create and format the MSDOS partition for macppc installs in a more flexible and reliable way.
</ul>
<p>
<li>OpenBGPD 4.2:
<ul>
<li>Include support for Four-octet AS Number Space.
<li>Allow matching on communities using 0 in the AS part.
<li>Filtering on IPv6 prefixes is now possible.
<li>Various bugs in the encoding of multiprotocol updates were fixed.
<li>Allow the use of pkill -HUP bgpd to reload the config.
<li>bgpctl can filter prefix output by community now
</ul>
<p>
<li>OpenNTPD 4.2:
<ul>
<li>Improved support for timedelta sensors.
</ul>
<p>
<li>OpenOSPFD 4.2:
<ul>
<li>Added support for RFC 3137: OSPF Stub Router Advertisement
<li>It is possible to specify a carp demote group on interfaces and areas.
<li>Added support for mapping route labels to AS-external route tags and vice versa.
<li>Allow the use of pkill -HUP ospfd to reload the config.
</ul>
<p>
<li>Hoststated 4.2:
<ul>
<li>Added support for Layer 7 load balancing (or relay).
<li>Added support for reloading through hoststatectl or SIGHUP.
</ul>
<p>
<li>OpenSSH 4.7:
<ul>
<li>Prevent
<a href="https://man.openbsd.org/ssh.1">ssh(1)</a>
from using a trusted X11 cookie if creation of an
untrusted cookie fails; found and fixed by Jan Pechanec.
<li><a href="https://man.openbsd.org/sshd.8">sshd(8)</a>
in new installations defaults to SSH Protocol 2 only.
Existing installations are unchanged.
<li>The SSH channel window size has been increased, and both
<a href="https://man.openbsd.org/ssh.1">ssh(1)</a>
and
<a href="https://man.openbsd.org/sshd.8">sshd(8)</a>
now send window updates more aggressively.<br>
These improves performance on high-BDP (Bandwidth Delay Product) networks.
<li><a href="https://man.openbsd.org/ssh.1">ssh(1)</a>
and
<a href="https://man.openbsd.org/sshd.8">sshd(8)</a>
now preserve MAC contexts between packets, which
saves 2 hash calls per packet and results in 12-16% speedup for
arcfour256/hmac-md5.
<li>A new MAC algorithm has been added, UMAC-64 (RFC4418) which is
approximately 20% faster than HMAC-MD5.
<li>A -K flag was added to
<a href="https://man.openbsd.org/ssh.1">ssh(1)</a>
to set GSSAPIAuthentication=Yes.
<li>Failure to establish a
<a href="https://man.openbsd.org/ssh.1">ssh(1)</a>
TunnelForward is now treated as a
fatal error when the ExitOnForwardFailure option is set.
<li><a href="https://man.openbsd.org/ssh.1">ssh(1)</a>
returns a sensible exit status if the control master goes
away without passing the full exit status. (bz #1261)
</ul>
<p>
<li>Over 4,500 ports, minor robustness improvements in package tools.
<li>Many pre-built packages for each architecture:
<ul style="column-count: 3">
<li>i386: 4360
<li>sparc64: 4205
<li>alpha: 3779
<li>sh: 817
<li>amd64: 4283
<li>powerpc: 4230
<li>sparc: 3283
<li>m68k: 1107
<li>arm: 2131
<li>hppa: 3215
<li>vax: 108
</ul>
Some highlights:
<ul>
<!-- XXX double check versions -->
<li>Gnome 2.18.
<li>GNUstep 1.14.
<li>KDE 3.5.7 and koffice 1.6.3.
<li>Xfce 4.4.1.
<li>OpenMotif 2.3.0.
<li>OpenOffice.org 2.2.1.
<li>Mozilla Firefox 2.0.0.6.
<li>PostgreSQL 8.2.4.
<li>GHC 6.6.1 (amd64 and i386 only)
</ul>
<p>
<li>As usual, steady improvements in manual pages and other documentation.
<p>
<li>The system includes the following major components from outside suppliers:
<ul>
<li>Xenocara (based on X.Org 7.2 + patches, freetype 2.2.1, fontconfig
2.4.2, expat 2.0.0, Mesa 6.5.2, xterm 225 and more)
<li>Gcc 2.95.3
(+ <a href="https://man.openbsd.org/gcc-local.1">patches</a>)
and 3.3.5
(+ <a href="https://man.openbsd.org/gcc-local.1">patches</a>)
<li>Perl 5.8.8 (+ patches)
<li>Our improved and secured version of Apache 1.3, with SSL/TLS and DSO support
<li>OpenSSL 0.9.7j (+ patches)
<li>Groff 1.15
<li>Sendmail 8.14.1, with libmilter
<li>Bind 9.3.4 (+ patches)
<li>Lynx 2.8.5rel.4 with HTTPS and IPv6 support (+ patches)
<li>Sudo 1.6.9p4
<li>Ncurses 5.2
<li>Latest KAME IPv6
<li>Heimdal 0.7.2 (+ patches)
<li>Arla 0.35.7
<li>Binutils 2.15 (+ patches)
<li>Gdb 6.3 (+ patches)
<!-- XXX double check versions -->
</ul>
</ul>
</section>
<hr>
<section id=install>
<h3>How to install</h3>
<p>
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.
<p>
<hr>
Please refer to the following files on the three CDROMs or FTP mirror for
extensive details on how to install OpenBSD 4.2 on your machine:
<p>
<ul>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/4.2/i386/INSTALL.i386">
.../OpenBSD/4.2/i386/INSTALL.i386 (on CD1)</a>
<p>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/4.2/amd64/INSTALL.amd64">
.../OpenBSD/4.2/amd64/INSTALL.amd64 (on CD2)</a>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/4.2/macppc/INSTALL.macppc">
.../OpenBSD/4.2/macppc/INSTALL.macppc (on CD2)</a>
<p>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/4.2/sparc64/INSTALL.sparc64">
.../OpenBSD/4.2/sparc64/INSTALL.sparc64 (on CD3)</a>
<p>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/4.2/alpha/INSTALL.alpha">
.../OpenBSD/4.2/alpha/INSTALL.alpha</a>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/4.2/armish/INSTALL.armish">
.../OpenBSD/4.2/armish/INSTALL.armish</a>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/4.2/hp300/INSTALL.hp300">
.../OpenBSD/4.2/hp300/INSTALL.hp300</a>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/4.2/hppa/INSTALL.hppa">
.../OpenBSD/4.2/hppa/INSTALL.hppa</a>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/4.2/landisk/INSTALL.landisk">
.../OpenBSD/4.2/landisk/INSTALL.landisk</a>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/4.2/mac68k/INSTALL.mac68k">
.../OpenBSD/4.2/mac68k/INSTALL.mac68k</a>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/4.2/mvme68k/INSTALL.mvme68k">
.../OpenBSD/4.2/mvme68k/INSTALL.mvme68k</a>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/4.2/mvme88k/INSTALL.mvme88k">
.../OpenBSD/4.2/mvme88k/INSTALL.mvme88k</a>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/4.2/sparc/INSTALL.sparc">
.../OpenBSD/4.2/sparc/INSTALL.sparc</a>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/4.2/vax/INSTALL.vax">
.../OpenBSD/4.2/vax/INSTALL.vax</a>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/4.2/zaurus/INSTALL.zaurus">
.../OpenBSD/4.2/zaurus/INSTALL.zaurus</a>
</ul>
</section>
<hr>
<section id=quickinstall>
<p>
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!
<h3>OpenBSD/i386:</h3>
<p>
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
<i>CD1:4.2/i386/floppy42.fs</i> to a floppy and boot via the floppy drive.
<p>
Use <i>CD1:4.2/i386/floppyB42.fs</i> instead for greater SCSI controller
support, or <i>CD1:4.2/i386/floppyC42.fs</i> for better laptop support.
<p>
NOTE: some older BIOSes appear to have problems booting CD1.
A workaround can be found on the
<a href="errata42.html#003_i386_boot">4.2 errata page</a>.
<p>
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.
<p>
If you are planning on dual booting OpenBSD with another OS, you will need to
read INSTALL.i386.
<p>
To make a boot floppy under MS-DOS, use the "rawrite" utility located
at <i>CD1:4.2/tools/rawrite.exe</i>. To make the boot floppy under a Unix OS,
use the
<a href="https://man.openbsd.org/dd.1">dd(1)</a>
utility. The following is an example usage of
<a href="https://man.openbsd.org/dd.1">dd(1)</a>,
where the device could be "floppy", "rfd0c", or
"rfd0a".
<blockquote><pre>
# <kbd>dd if=<file> of=/dev/<device> bs=32k</kbd>
</pre></blockquote>
<p>
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
<a href="faq/faq4.html#MkFlop">this page</a>.
<h3>OpenBSD/amd64:</h3>
<p>
The 4.2 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.
If you can't boot from the CD, you can create a boot floppy to install from.
To do this, write <i>CD2:4.2/amd64/floppy42.fs</i> to a floppy, then
boot from the floppy drive.
<p>
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.
<p>
If you are planning to dual boot OpenBSD with another OS, you will need to
read INSTALL.amd64.
<h3>OpenBSD/macppc:</h3>
<p>
Put CD2 in your CDROM drive and poweron your machine while holding down the
<i>C</i> key until the display turns on and shows <i>OpenBSD/macppc boot</i>.
<p>
Alternatively, at the Open Firmware prompt, enter <i>boot cd:,ofwboot
/4.2/macppc/bsd.rd</i>
<h3>OpenBSD/sparc64:</h3>
<p>
Put CD3 in your CDROM drive and type <i>boot cdrom</i>.
<p>
If this doesn't work, or if you don't have a CDROM drive, you can write
<i>CD3:4.2/sparc64/floppy42.fs</i> or <i>CD3:4.2/sparc64/floppyB42.fs</i>
(depending on your machine) to a floppy and boot it with <i>boot
floppy</i>. Refer to INSTALL.sparc64 for details.
<p>
Make sure you use a properly formatted floppy with NO BAD BLOCKS or your install
will most likely fail.
<p>
You can also write <i>CD3:4.2/sparc64/miniroot42.fs</i> to the swap partition on
the disk and boot with <i>boot disk:b</i>.
<p>
If nothing works, you can boot over the network as described in INSTALL.sparc64.
<h3>OpenBSD/alpha:</h3>
<p>
Write <i>4.2/alpha/floppy42.fs</i> or
<i>4.2/alpha/floppyB42.fs</i> (depending on your machine) to a diskette and
enter <i>boot dva0</i>. Refer to INSTALL.alpha for more details.
<p>
Make sure you use a properly formatted floppy with NO BAD BLOCKS or your install
will most likely fail.
<h3>OpenBSD/armish:</h3>
<p>
After connecting a serial port, Thecus can boot directly from the network
either tftp or http. Configure the network using fconfig, reset,
then load bsd.rd, see INSTALL.armish for specific details.
IOData HDL-G can only boot from an EXT-2 partition. Boot into linux
and copy 'boot' and bsd.rd into the first partition on wd0 (hda1)
then load and run bsd.rd, preserving the wd0i (hda1) ext2fs partition.
More details are available in INSTALL.armish.
<h3>OpenBSD/hp300:</h3>
<p>
Boot over the network by following the instructions in INSTALL.hp300.
<h3>OpenBSD/hppa:</h3>
<p>
Boot over the network by following the instructions in INSTALL.hppa or the
<a href="hppa.html#install">hppa platform page</a>.
<h3>OpenBSD/landisk:</h3>
<p>
Write <i>miniroot42.fs</i> to the start of the CF
or disk, and boot normally.
<!--
<h3>OpenBSD/luna88k:</h3>
<p>
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.
-->
<h3>OpenBSD/mac68k:</h3>
<p>
Boot MacOS as normal and extract the Macside "BSD/Mac68k Booter" utility from
<i>4.2/mac68k/utils</i> onto your hard disk. Configure the "BSD/Mac68k
Booter" with the location of your bsd.rd kernel and boot into the installer.
Refer to the instructions in INSTALL.mac68k for more details.
<h3>OpenBSD/mvme68k:</h3>
<p>
You can create a bootable installation tape or boot over the network.<br>
The network boot requires a MVME68K BUG version that supports the <i>NIOT</i>
and <i>NBO</i> debugger commands. Follow the instructions in INSTALL.mvme68k
for more details.
<h3>OpenBSD/mvme88k:</h3>
<p>
You can create a bootable installation tape or boot over the network.<br>
The network boot requires a MVME88K BUG version that supports the <i>NIOT</i>
and <i>NBO</i> debugger commands. Follow the instructions in INSTALL.mvme88k
for more details.
<h3>OpenBSD/sparc:</h3>
<p>
Boot from one of the provided install ISO images, using one of the two
commands listed below, depending on the version of your ROM.
<blockquote><pre>
ok <kbd>boot cdrom 4.2/sparc/bsd.rd</kbd>
or
> <kbd>b sd(0,6,0)4.2/sparc/bsd.rd</kbd>
</pre></blockquote>
<p>
If your SPARC system does not have a CD drive, you can alternatively boot from floppy.
To do so you need to write <i>floppy42.fs</i> to a floppy.
For more information see <a href="faq/faq4.html#MkFlop">this page</a>.
To boot from the floppy use one of the two commands listed below,
depending on the version of your ROM.
<blockquote><pre>
ok <kbd>boot floppy</kbd>
or
> <kbd>b fd()</kbd>
</pre></blockquote>
<p>
Make sure you use a properly formatted floppy with NO BAD BLOCKS or your install
will most likely fail.
<p>
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.
<h3>OpenBSD/vax:</h3>
<p>
Boot over the network via mopbooting as described in INSTALL.vax.
<h3>OpenBSD/zaurus:</h3>
<p>
Using the Linux built-in graphical ipkg installer, install the
openbsd42_arm.ipk package. Reboot, then run it. Read INSTALL.zaurus
for a few important details.
</section>
<hr>
<section id=sourcecode>
<h3>Notes about the source code</h3>
<p>
<code>src.tar.gz</code> contains a source archive starting at <code>/usr/src</code>.
This file contains everything you need except for the kernel sources, which are
in a separate archive. To extract:
<blockquote><pre>
# <kbd>mkdir -p /usr/src</kbd>
# <kbd>cd /usr/src</kbd>
# <kbd>tar xvfz /tmp/src.tar.gz</kbd>
</pre></blockquote>
<p>
<code>sys.tar.gz</code> contains a source archive starting at <code>/usr/src/sys</code>.
This file contains all the kernel sources you need to rebuild kernels.
To extract:
<blockquote><pre>
# <kbd>mkdir -p /usr/src/sys</kbd>
# <kbd>cd /usr/src</kbd>
# <kbd>tar xvfz /tmp/sys.tar.gz</kbd>
</pre></blockquote>
<p>
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 <a href="anoncvs.html">here</a>.
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.
</section>
<hr>
<section id=upgrade>
<h3>How to upgrade</h3>
<p>
If you already have an OpenBSD 4.1 system, and do not want to reinstall,
upgrade instructions and advice can be found in the
<a href="faq/upgrade42.html">Upgrade Guide</a>.
</section>
<hr>
<section id=ports>
<h3>Ports Tree</h3>
<p>
A ports tree archive is also provided. To extract:
<blockquote><pre>
# <kbd>cd /usr</kbd>
# <kbd>tar xvfz /tmp/ports.tar.gz</kbd>
</pre></blockquote>
<p>
The <i>ports/</i> subdirectory is a checkout of the OpenBSD ports tree. Go
read the <a href="faq/faq15.html">ports</a> 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.
<p>
The <i>ports/</i> directory represents a CVS (see the manpage for
<a href="https://man.openbsd.org/cvs.1">cvs(1)</a> 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 <i>ports/</i> tree
available on a read-write medium and update the tree with a command
like:
<blockquote><pre>
# <kbd>cd [portsdir]/; cvs -d anoncvs@server.openbsd.org:/cvs update -Pd -rOPENBSD_4_2</kbd>
</pre></blockquote>
<p>
[Of course, you must replace the local directory and server name here
with the location of your ports collection and a nearby anoncvs
server.]
<p>
Note that most ports are available as packages on our mirrors. Updated
packages for the 4.2 release will be made available if problems arise.
<p>
If you're interested in seeing a port added, would like to help out, or just
would like to know more, the mailing list
<a href="mail.html">ports@openbsd.org</a> is a good place to know.
</section>
![[BACK]](/icons/back.gif){kind=icon}
Return to 42.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www