<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>OpenBSD 3.7 Release</title>
<link rev=made href="mailto:www@openbsd.org">
<meta name="resource-type" content="document">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="description" content="OpenBSD 3.7">
<meta name="keywords" content="openbsd,main">
<meta name="distribution" content="global">
<meta name="copyright" content="This document copyright 2005 by OpenBSD.">
</head>
<body bgcolor="#ffffff" text="#000000" link="#24248E">
<a href="index.html">
<img alt="[OpenBSD]" height="30" width="141" hspace="24" src="images/smalltitle.gif" border="0"></a>
<hr>
<p>
<a href="images/Wizard.jpg">
<img align="left" width="255" height="343" hspace="24" vspace="30"
src="images/Wizard.jpg" alt="OpenBSD 3.7 logo"></a>
<h2><font color="#0000e0">The OpenBSD 3.7 Release:</font></h2>
<p>
Released May 19, 2005<br>
Copyright 1997-2005, Theo de Raadt.<br>
<font color="#e00000">ISBN 0-9731791-5-5</font>
<p>
<a href="#new">What's New</a><br>
<a href="#install">How to install</a><br>
<a href="#upgrade">How to upgrade</a><br>
<a href="#ports">How to use the ports tree</a><br>
<a href="orders.html">Ordering a CD set</a><br>
<p>
<h3><font color="#0000e0">
To get the files for this release:
<ul>
<li>Order a CDROM from our <a href="orders.html">ordering system</a>.
<li>See the information on <a href="ftp.html">The FTP page</a> for
a list of mirror machines.
<li>Go to the <font color="#e00000">pub/OpenBSD/3.7/</font> directory on
one of the mirror sites.
<li>Briefly read the rest of this document.
<li>Have a look at <a href="errata.html">The 3.7 Errata page</a> for a list
of bugs and workarounds.
<li>See a <a href="plus37.html">detailed log of changes</a> between the
3.6 and 3.7 releases.
</ul>
</font></h3>
<br clear=all>
<strong>Note:</strong> 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.
<p>
<a name="new"></a>
<hr>
<p>
<h3><font color="#0000e0">What's New</font></h3>
<p>
This is a partial list of new features and systems included in OpenBSD 3.7.
For a comprehensive list, see the <a href="plus37.html">changelog</a> leading
to 3.7.
<p>
<ul>
<li>New platforms:
<ul>
<li><a href="zaurus.html">OpenBSD/zaurus</a><br>
Expanding the arm porting effort by supporting the Sharp Zaurus SL-C3000,
bringing a secure ssh-capable machine to your pocket.
<li><a href="sgi.html">OpenBSD/sgi</a><br>
</ul>
<p>
<li>Support for a number of much faster 64-bit machines (in 32-bit mode) in
the <a href="hppa.html">OpenBSD/hppa</a> port.
<p>
<li>Improved hardware support, including:
<ul>
<li>New <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ath&sektion=4&arch=i386">ath(4)</a>
driver for Atheros IEEE 802.11a/b/g wireless network adapters.
<li>New <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=iwi&sektion=4&arch=i386">iwi(4)</a>
driver for Intel PRO/Wireless 2200BG/2225BG/2915ABG IEEE 802.11a/b/g wireless network adapters.
<li>New <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ipw&sektion=4&arch=i386">ipw(4)</a>
driver for Intel PRO/Wireless 2100 IEEE 802.11b wireless network adapters.
<li>New <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=atu&sektion=4&arch=i386">atu(4)</a>
driver for Atmel AT76C50x USB IEEE 802.11b wireless network adapters.
<li>New <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ral&sektion=4&arch=i386">ral(4)</a>
and <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ural&sektion=4&arch=i386">ural(4)</a> [USB]
drivers for Ralink Technology RT25x0 IEEE 802.11a/b/g wireless network adapters.
<li>New <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=rtw&sektion=4&arch=i386">rtw(4)</a>
driver for Realtek 8180 IEEE 802.11b wireless network adapters.
<li>Added support to <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=re&sektion=4&arch=i386">re(4)</a>
driver for Realtek 8169 CardBus Ethernet adapters.
<li>New <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=udav&sektion=4&arch=i386">udav(4)</a>
driver for Davicom DM9601 USB Ethernet adapters.
<li>New <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=vge&sektion=4&arch=i386">vge(4)</a>
driver for VIA Networking Technologies VT6122 PCI Gigabit Ethernet adapters.
</ul>
<p>
<li>Many enhancements in the <a href="mac68k.html">OpenBSD/mac68k</a> port.
<ul>
<li>Switch to a bsd.rd based install.
<li>Create partitions with <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pdisk&sektion=8&arch=mac68k">pdisk(8)</a>
<li>Add <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=mc&sektion=4&arch=mac68k">mc(4)</a>
support and enhance
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=zsc&sektion=4&arch=mac68k">zsc(4)</a>
support.
</ul>
<p>
<li>New tools:
<ul>
<li><a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ospfd">ospfd(8)</a>,
implementing the <a href="http://www.rfc-editor.org/rfc/rfc2328.txt">OSPFv2</a>
routing protocol.
</ul>
<p>
<li>New functionality:
<ul>
<li>Repaired mirroring mode in <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ccd&sektion=4&arch=i386">ccd(4)</a>
<li>Privilege separation for <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ftpd&sektion=8&arch=i386">ftpd(8)</a>.
<li>Bash style prompt expansion and POSIX hex and octal constants in
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ksh&sektion=1&arch=i386">ksh(1)</a>.
<li>Improved tcp send performance.
<li>Reentrant
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=getprotobyname_r&sektion=3&arch=i386">getproto*_r(3)</a>
and
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=getservbyname_r&sektion=3&arch=i386">getserv*_r(3)</a>
functions.
</ul>
<p>
<li>New functionality for <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ntpd&sektion=8&">ntpd(8)</a>,
the Network Time Protocol Daemon:
<ul>
<li>ntpd can now set the time hard on startup itself, eliminating the need to
run rdate -n beforehand
<li>Use median instead of average when collapsing all the peers' offsets
into one, greatly improving resistance against falsetickers
<li>Calculate rootdelay, stratum and precision properly; include these in
replies sent out in server mode
<li>Many logging improvements, ntpd is now almost completely silent in normal
operation (unless in debug mode, of course)
</ul>
<p>
<li>New functionality for <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=bgpd&sektion=8&">bgpd(8)</a>,
the Border Gateway Protocol Daemon:
<ul>
<li>Allow sessions to depend on a CARP interface's master/backup state,
reducing failover times in redundant setups
<li>Lower latency for requests from other peers or bgpctl while under heavy
load, e. g. initial table transfer when a session comes up
<li>Allow for the peer descriptions to be used in bgpctl commands where
previously only their IPs where allowed
<li>Allow bgpd to not prepend its own AS number and to not modify the nexthop
on updates sent out
<li>Show associated interfaces and their state on "show nexthop",
to help pointing out why nexthops are invalid
<li>Allow for relative metrics modification, i. e.
"set localpref +20"
</ul>
<p>
<li>New functionality and improvements for <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=isakmpd&sektion=8&">isakmpd(8)</a>,
the Internet Security Association and Key Management Daemon:
<ul>
<li>Allow the Address, Network, or Netmask values of the "IPsec-ID"
to be specified with an interface name or the keyword "default"
(in which case the address is selected based on the default route)
<li>Improved NAT-T and DPD stability and interoperability
</ul>
<p>
<li>New functionality and many improvements for the <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pkg_add&sektion=1&">package tools</a>:
<ul>
<li>In-place updates of packages
<li>Progress meters, helping a lot when installing big packages
<li>Reliable dependencies on shared libraries, including the base system
</ul>
<p>
<li>Over 3000 ports, 2800 pre-built packages.
<p>
<li>Many improvements for security and reliability.
Cleaner source code for
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ksh&sektion=1&">ksh(1)</a>,
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=httpd&sektion=8&">httpd(8)</a> and many more programs.
<p>
<li>As usual, many improvements in manual pages and other documentation.
<p>
<li>OpenSSH 4.1:
<ul>
</ul>
<p>
<li>The system includes the following major components from outside suppliers:
<ul>
<li>X.Org 6.8.2 (+ patches, and i386 contains XFree86 3.3.6 servers
(+ patches) for legacy chipsets not supported by X.Org)
<li>Gcc 2.95.3
(+ <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=gcc-local&sektion=1">patches</a>)
and 3.3.5
(+ <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=gcc-local&sektion=1">patches</a>)
<li>Perl 5.8.6 (+ patches)
<li>Apache 1.3.29, mod_ssl 2.8.16, DSO support (+ patches)
<li>OpenSSL 0.9.7d (+ patches)
<li>Groff 1.15
<li>Sendmail 8.13.3, with libmilter
<li>Bind 9.3.0 (+ patches)
<li>Lynx 2.8.5rel.2 with HTTPS and IPv6 support (+ patches)
<li>Sudo 1.6.8p6
<li>Ncurses 5.2
<li>Latest KAME IPv6
<li>Heimdal 0.6rc1 (+ patches)
<li>Arla 0.35.7
<li>Binutils 2.15
<li>Gdb 6.3
</ul>
<p>
</ul>
<a name="install"></a>
<hr>
<p>
<h3><font color="#0000e0">How to install</font></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 3.7 on your machine:
<p>
<ul>
<li>CD1:3.7/i386/INSTALL.i386
<li>CD1:3.7/vax/INSTALL.vax
<p>
<li>CD2:3.7/amd64/INSTALL.amd64
<li>CD2:3.7/macppc/INSTALL.macppc
<p>
<li>CD3:3.7/sparc/INSTALL.sparc
<li>CD3:3.7/sparc64/INSTALL.sparc64
<p>
<li>FTP:.../OpenBSD/3.7/alpha/INSTALL.alpha
<li>FTP:.../OpenBSD/3.7/cats/INSTALL.cats
<li>FTP:.../OpenBSD/3.7/hp300/INSTALL.hp300
<li>FTP:.../OpenBSD/3.7/hppa/INSTALL.hppa
<li>FTP:.../OpenBSD/3.7/luna88k/INSTALL.luna88k
<li>FTP:.../OpenBSD/3.7/mac68k/INSTALL.mac68k
<li>FTP:.../OpenBSD/3.7/mvme68k/INSTALL.mvme68k
<li>FTP:.../OpenBSD/3.7/mvme88k/INSTALL.mvme88k
<li>FTP:.../OpenBSD/3.7/sgi/INSTALL.sgi
<li>FTP:.../OpenBSD/3.7/zaurus/INSTALL.zaurus
</ul>
<hr>
<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!
<p>
<h3><font color="#e00000">OpenBSD/i386:</font></h3>
<ul>
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:3.7/i386/floppy37.fs</i> to a floppy and boot via the floppy drive.
<p>
Use <i>CD1:3.7/i386/floppyB37.fs</i> instead for greater scsi controller
support, or <i>CD1:3.7/i386/floppyC37.fs</i> for better laptop support.
<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:3.7/tools/rawrite.exe</i>. To make the boot floppy under a Unix OS,
use the <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=
dd&sektion=1">dd(1)</a> utility. The following is an example usage of
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=dd&sektion=1">dd(1)
</a>, where the device could be "floppy", "rfd0c", or
"rfd0a".
<ul><pre>
# <strong>dd if=<file> of=/dev/<device> bs=32k</strong>
</pre></ul>
<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">FAQ4.1</a>.
</ul>
<p>
<h3><font color="#e00000">OpenBSD/vax:</font></h3>
<ul>
Boot over the network via mopbooting as described in INSTALL.vax.
</ul>
<p>
<h3><font color="#e00000">OpenBSD/amd64:</font></h3>
<ul>
The 3.7 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:3.7/amd64/floppy37.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.
</ul>
<p>
<h3><font color="#e00000">OpenBSD/macppc:</font></h3>
<ul>
Put the 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
/3.7/macppc/bsd.rd</i>
</ul>
<p>
<h3><font color="#e00000">OpenBSD/sparc:</font></h3>
<ul>
The 3.7 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.
<ul><pre>
ok <strong>boot cdrom 3.7/sparc/bsd.rd</strong>
or
> <strong>b sd(0,6,0)3.7/sparc/bsd.rd</strong>
</pre></ul>
<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>CD3:3.7/sparc/floppy37.fs</i> to a floppy.
For more information see <a href="faq/faq4.html#MkFlop">FAQ4.1</a>. To boot from
the floppy use one of the two commands listed below, depending on the version of
your ROM.
<ul><pre>
ok <strong>boot floppy</strong>
or
> <strong>b fd()</strong>
</pre></ul>
<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.
</ul>
<p>
<h3><font color="#e00000">OpenBSD/sparc64:</font></h3>
<ul>
Put the 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:3.7/sparc64/floppy37.fs</i> to a floppy and boot it with <i>boot
floppy</i>.<br>
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:3.7/sparc64/miniroot37.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
</ul>
<p>
<h3><font color="#e00000">OpenBSD/alpha:</font></h3>
<ul>
<p>Write <i>FTP:3.7/alpha/floppy37.fs</i> or
<i>FTP:3.7/alpha/floppyB37.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.
</ul>
<p>
<h3><font color="#e00000">OpenBSD/cats:</font></h3>
<ul>
<p>
After updating the firmware to at least ABLE 1.95 if necessary, boot
<i>FTP:3.7/cats/bsd.rd</i> from an ABLE-supported device (such as a CD-ROM
or an existing FFS or EXT2FS partition).
</ul>
<p>
<h3><font color="#e00000">OpenBSD/zaurus:</font></h3>
<ul>
<p>
Using the Linux built-in graphical ipkg installer, install the
openbsd37_arm.ipk package. Reboot, then run it. Read INSTALL.zaurus
for a few important details.
</ul>
<p>
<h3><font color="#e00000">OpenBSD/hp300:</font></h3>
<ul>
<p>
Boot over the network by following the instructions in INSTALL.hp300.
</ul>
<p>
<h3><font color="#e00000">OpenBSD/hppa:</font></h3>
<ul>
<p>
Boot over the network by following the instructions in INSTALL.hppa or the
<a href="hppa.html#netboot">hppa platform page</a>.
</ul>
<p>
<h3><font color="#e00000">OpenBSD/luna88k:</font></h3>
<ul>
<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.
</ul>
<p>
<h3><font color="#e00000">OpenBSD/mac68k:</font></h3>
<ul>
<p>
Boot MacOS as normal and extract the Macside "BSD/Mac68k Booter" utility from
<i>FTP:3.7/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.
</ul>
<p>
<h3><font color="#e00000">OpenBSD/mvme68k:</font></h3>
<ul>
<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.
</ul>
<p>
<h3><font color="#e00000">OpenBSD/mvme88k:</font></h3>
<ul>
<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.
</ul>
<p>
<h3><font color="#e00000">OpenBSD/sgi:</font></h3>
<ul>
<p>
Setup a DHCP/tftp network server, and boot using "bootp()/bsd.rd".
</ul>
<p>
<h3><font color="#e00000">Notes about the source code:</font></h3>
<ul>
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:
<p>
<ul><pre>
# <strong>mkdir -p /usr/src</strong>
# <strong>cd /usr/src</strong>
# <strong>tar xvfz /tmp/src.tar.gz</strong>
</pre></ul>
<p>
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:
<p>
<ul><pre>
# <strong>mkdir -p /usr/src/sys</strong>
# <strong>cd /usr/src</strong>
# <strong>tar xvfz /tmp/sys.tar.gz</strong>
</pre></ul>
<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.
<p>
</ul>
<a name="upgrade"></a>
<hr>
<p>
<h3><font color="#0000e0">How to upgrade</font></h3>
<p>
If you already have an OpenBSD 3.6 system, and do not want to reinstall,
upgrade instructions and advice can be found in the
<a href="faq/upgrade37.html">Upgrade Guide</a>.
<a name="ports"></a>
<hr>
<p>
<h3><font color="#0000e0">Ports Tree</font></h3>
<p>
A ports tree archive is also provided. To extract:
<p>
<ul><pre>
# <strong>cd /usr</strong>
# <strong>tar xvfz /tmp/ports.tar.gz</strong>
# <strong>cd ports</strong>
</pre></ul>
<p>
The <i>ports/</i> subdirectory is a checkout of the OpenBSD ports tree. Go
read the <a href="ports.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="http://www.openbsd.org/cgi-bin/man.cgi?query=cvs&apropos=0&sektion=1&manpath=OpenBSD+Current&arch=i386&format=html">
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:
<p>
<ul><pre>
# <strong>cd [portsdir]/; cvs -d anoncvsserver.openbsd.org:/cvs update -Pd -rOPENBSD_3_7</strong>
</pre></ul>
<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 through ftp. Updated
packages for the 3.7 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 ports@openbsd.org is a good
place to know.
<p>
<hr>
<a href="index.html"><img height="24" width="24" src="back.gif" border="0"
alt="OpenBSD"></a>
<a href="mailto:www@openbsd.org">www@openbsd.org</a>
<br><small>
$OpenBSD: 37.html,v 1.38 2005/03/24 17:42:02 sturm Exp $
</small>
</body>
</html>
![[BACK]](/icons/back.gif){kind=icon}
Return to 37.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www