Movatterモバイル変換

254 captures

02 Sep 2006 - 10 Jul 2025

Aug	SEP	Nov
	30
2017	2018	2019

success

fail

About this capture

COLLECTED BY

Organization:Alexa Crawls

Starting in 1996,Alexa Internet has been donating their crawl data to the Internet Archive. Flowing in every day, these data are added to theWayback Machine after an embargo period.

Collection:Alexa Crawls

Starting in 1996,Alexa Internet has been donating their crawl data to the Internet Archive. Flowing in every day, these data are added to theWayback Machine after an embargo period.

TIMESTAMPS

Released Nov 1, 2006
Copyright 1997-2006, Theo de Raadt.

4.0 Song:"Humppa Negala"

• See the information onThe FTP page for a list of mirror machines.
• Go to the directory on one of the mirror sites.
• Have a look atThe 4.0 Errata page for a list of bugs and workarounds.
• See adetailed log of changes between the 3.9 and 4.0 releases.

All applicable copyrights and credits are in the src.tar.gz,sys.tar.gz, xenocara.tar.gz, ports.tar.gz files, or in thefiles fetched via ports.tar.gz.

This is a partial list of new features and systems included in OpenBSD 4.0.For a comprehensive list, see thechangelog leadingto 4.0.

• New/extended platforms:
  • OpenBSD/armish.
    Various ARM-based appliances, using the Redboot boot loader, currently only supporting the Thecus N2100 and IOData HDL-G.
  • OpenBSD/sparc64.
    UltraSPARC III based machines are now supported!
  • OpenBSD/zaurus.
    Support for the Zaurus SL-C3200.

• Improved hardware support, including:
  • Newmsk(4) driver for Marvell/SysKonnect Yukon-2 Gigabit Ethernet.
  • Newbnx(4) driver for Broadcom NetXtreme II Gigabit Ethernet.
  • Newxge(4) driver for Neterion Xframe/Xframe II 10Gb Ethernet.
  • Newrum(4) driver for Ralink Technology 2nd gen USB IEEE 802.11a/b/g wireless.
  • Newacx(4) driver for Texas Instruments ACX100/ACX111 IEEE 802.11a/b/g wireless.
  • Newpgt(4) driver for Connexant/Intersil Prism GT Full-MAC IEEE 802.11a/b/g wireless.
  • Newuath(4) driver for Atheros USB IEEE 802.11a/b/g wireless.
  • New binary blob freewpi(4) driver for Intel PRO/Wireless 3945ABG IEEE 802.11a/b/g wireless.
  • Newarc(4) driver for Areca Technology Corporation SATA RAID; including RAID management viabio(4).
  • Newmfi(4) driver for LSI Logic & Dell MegaRAID SAS RAID; including RAID management viabio(4).
  • Newazalia(4) driver for generic High Definition Audio.
  • New SD/MMC/SDIO drivers (sdhc(4),sdmmc(4)), currently supporting SD memory cards as fake SCSIsd(4) drives.
  • Newudcf(4) driver for Gude ADS Expert mouseCLOCK DCF77/HBG time signal station receivers.
  • Newuslcom(4) driver for Silicon Laboratories CP2101/CP2102 based USB serial adapters.
  • Newucycom(4) driver for Cypress microcontroller based USB serial adapters.
  • Newuark(4) driver for Arkmicro Technologies ARK3116 based USB serial adapters.
  • Newumsm(4) driver for Qualcomm MSM EVDO based modems.
  • New Dallas/Maxim 1-Wire bus support, including:
    • Newgpioow(4) driver for 1-Wire bus bit-banging through GPIO pin
    • Newonewire(4) 1-Wire bus driver
    • Newowid(4) 1-Wire ID family driver
    • Newowtemp(4) 1-Wire temperature family driver
  • Newisagpio(4) driver for ISA I/O mapped as GPIO.
  • Newnmea(4)line discipline for NMEA 0183 (GPS) devices. The newnmeaattach(8)utility can be used to receive NMEA 0183 data and provide the timereceived as a timedelta sensor to be used by, for example,ntpd(8).
  • New VAX framebuffer drivers:
    • Newlcg(4) driver for VAXstation 4000/60 and VLC color frame buffers
    • Newlcspx(4) driver for Low-Cost SPX color frame buffers
    • Newgpx(4) driver for GPX color frame buffers
    • smg(4) driver for Small Monochrome Graphics frame buffers heavily updated to be a modernwscons(4) driver
  • Support for VAX-based Digital VXT2000 and VXT2000+ terminals.
  • Thebge(4) driver supporting newer chipsets, such as the Broadcom BCM5754, BCM5755, BCM5786, and BCM5787.
  • Theem(4) driver supporting newer chipsets, such as the Intel ESB2 and ICH8.
  • Thenfe(4) driver supporting newer chipsets, such as the NVIDIA MCP61 and MCP65.
  • There(4) driver supporting newer chipsets, such as the Realtek RT8101E, RT8168, and RT8169SC.
  • Thedc(4) driver supporting newer chipsets, such as the ADMtek ADM9511 and ADM9513.
  • Thepciide(4) driver supporting newer chipsets, such as:
    • ATI IXP300 SATA, IXP600 IDE
    • Intel 6321ESB IDE/SATA, 82801G SATA, and 82801H SATA
    • IT Express IT8211F IDE
    • NVIDIA MCP61 SATA, MCP65 SATA
    • Promise PDC205xx SATA
    • ServerWorks SATA
    • VIA VT8237A SATA
  • Thempt(4) driver has been replaced withmpi(4), a more stable driver that supports more hardware.
  • Thecom(4) driver now supports pcmcia and cardbus cards on macppc.
  • Working interrupt routing on Sun Netra t1 105, Ultra 60 and possibly othersparc64 systems.
  • Work around broken VIA and NVIDIA MPBIOSes, fixes interrupt routing with GENERIC.MP on several systems.
  • Initialbio(4) support for Compaq/HPciss(4) Smart ARRAY 5/6 SAS/SCSI RAID controllers.
  • Improved speed control on some systems:
    • New SpeedStep detection code, also adds support for VIA C7-M, and several newer Pentium M's.
    • Support SpeedStep in rudimentary fashion on most unknown CPU's that advertise the feature.
    • Zaurus can be moved into slower speeds now too.
    • The Pentium 4 Thermal Clock Control driver now supports more CPU's including the Intel Pentium M and Xeon, and provides an estimated performance impact.
    • Numerous improvements to PowerNow K7 and K8 support on i386, and support for K8 was added to amd64.
  • Support for Intel 945G/GM video chipsets (on i386).
  • Support for additional I2C sensors:
    • Theadt(4) driver now supports the National Semiconductor LM9600, SMSC EMC6D10x and SMSC SCH5017 chips.
    • Theadmtemp(4) driver now supports the Analog Devices ADM1023, Genesys Logic GL523SM and Global Mixed-mode Technology G781 chips.

• New tools:
  • GNU RCS has been replaced withOpenRCS.

• New functionality:
  • IPsec has been greatly improved:
    • ipsecctl(8) has been greatly extended and completely supersedes ipsecadm(8):
      • Lots of documentation improvements (manipsec.conf)
      • IPv6 support
      • AH support
      • Transport mode support
      • Dynamic IKE support for roaming users
      • USER_FQDN id support
    • sasyncd(8) works much better:
      • communicates withisakmpd(8), telling it to run active or passive depending on the master/slave state of thecarp(4) interfaces. This makesIPsec failover setups much more robust.
      • looks at thecarp(4) interface group by default to suppress preemption ofIPsec traffic during system boot.
    • isakmpd(8) can now be safely configured byipsecctl(8) on startup.
  • ftp(1) now supports HTTPS.
  • cdio(1) can now perform track-at-once burning and rewritable blanking.
  • spppcontrol(8) and wicontrol(8) functionality has been merged intoifconfig(8).
  • gcc(1) provides a new warning, -Wstack-larger-than-N, to report functionswhich are too greedy in stack variables, seegcc-local(1) for details.
  • An in-kernelgetcwd(3) implementation.
  • A new system calladjfreq(2)to allowntpd(8)to adjust the tick rate of the system clock automatically.
  • Support for X11 on VAX has been added
  • Virtual Allocation Table (VAT) support forUDF.
  • C99 functionsround(3),roundf(3),trunc(3), andtruncf(3)have been added to libm, the math library.
  • pf(4) now supports Unicast Reverse Path Forwarding (uRPF) checks for simplified ingress filtering.
  • bpf(4) can now ignore packets based on their direction (inbound/outbound) using the BIOCSDIRFILT ioctl.
  • pdisk(8) can now set up slices on HFS(DPME) partitioned disks on mac68k.
  • New dissectors have been added totcpdump(8):
    • Cisco's VQP (VLAN Query Protocol)
    • IEEE 802.1AB LLDP (Link Layer Discovery Protocol)
  • trunk(4) now supports the new loadbalance mode to balance outgoing traffic based on hashed protocol header information.
  • bioctl(8) has been extended to provide runtime information on rebuilds, scrubs and initialization.
  • New sysctls to check the system vendor, product, version, serial number, and UUID.
  • Equal cost multipath routing support. Needs to be enabled by a sysctl.
  • Prebind, a secure implementation of prelinking, has been added toldconfig(8),it speeds up launching of shared binaries. Prebind is compatible withaddress space randomization, unlike prelink.
  • vnconfig(8) can now use PKCS #5 PBKDF2 to create a more secure key when using encryption.

• Assorted improvements and code cleanup:
  • Much better time keeping for multiprocessorOpenBSD/i386systems.
  • Much improved implementation oftelldir(3)and friends.
  • Replacement of manymalloc(3) calls that follow a pattern prone to integer overflow with safer constructs.
  • Improved failover handling incarp(4):
    • Extend the carp protocol with the demotion counter to act smarter on multiple failures.
    • Group failovers now work without carp running preempt mode.
    • Demotion can now be controlled via interface groups.
  • chio(1)is now a useful tool for controlling tape changers.
  • Much improvedst(4)device setup, tape handling and error processing.
  • Manydhclient(8)fixes, including 'alias' handling and improved interface initialization.
  • scsi(4)devices detect the correct SCSI version.
  • Moreumass(4)devices properly detected.
  • Improved detection of fibre channel devices and devices in SCSI enclosures.
  • The new RSSI header has been added to theieee80211_radiotap(9) framework as a replacement for ANTSIGNAL headers.
  • Many integer type safety cleanups withlint(1).

• Install/Upgrade process changes
  • Host specific site files add easy customization for individual hosts
  • X Window aperture support, where available, now defaults to off

• New functionality forhostapd(8), the Host Access Point Daemon:
  • IP based roaming to build wireless networks without the requirement of a single broadcast domain.
  • New event rules to match optional elements of radiotap headers: signal percentage, transmit rate and channel frequency.
  • Various bug fixes and improvements.

• OpenSSH 4.4:
  • Conditional configuration insshd_config(5) using theMatch directive. This allows some configuration options to be selectively overridden if specific criteria (based on user, group, hostname and/or address) are met.
  • Add support for Diffie-Hellman group exchange key agreement with a final hash of SHA256.
  • Added aForceCommand directive tosshd_config(5), similar to the command="..." option in ~/.ssh/authorized_keys.
  • Added aPermitOpen directive tosshd_config(5), similar to the permitopen="..." option in authorized_keys, to allow control over the port-forwardings that a user is allowed to establish.
  • Added anExitOnForwardFailure option to cause ssh(1) to exit (with a non-zero exit code) when requested port forwardings could not be established.
  • Added optional logging of transactions tosftp-server(8).
  • ssh(1) will now record port numbers for hosts stored in ~/.ssh/authorized_keys when a non-standard port has been requested.
  • Extended thesshd_config(5) "SubSystem" directive to allow the specification of commandline arguments.
  • Many manpage fixes and improvements

• OpenBGPD 4.0:
  • new nexthop selection logic ignoring bgpd routes, helps in complex setups with ospfd
  • add a "detailed" show rib view to bgpctl, including communities
  • allow requesting a route refresh from a peer that supports it
  • have bgpd always report back the result of an operation to bgpctl, so the operator can spot errors quicker
  • allow bgpd to manipulate carp demotion counters based on session states, gives even greater failover support
  • support restarting sessions that reached max-prefix after a given time
  • bgpctl can now show all routes received from a neighbor before filters were applied, and routes sent to neighbors
  • assorted fixes and improvements, as usual

• OpenOSPFD 4.0:
  • Track uptime of the daemon itself.
  • Track uptime of all ospf enabled interfaces.
  • Adjust logging behaviour to prevent unwanted logging.
  • Delay LSA updates when removing and adding - prevent flapping.
  • Fix plaintext authentication.
  • Improve the output of 'ospfctl show interfaces'.
  • Support rtlabels when redistributing routes.

• OpenNTPD 4.0:
  • support timedelta sensors, such as DCF77 receivers supported byudcf(4) and GPS receivers supported bynmea(4).
  • Adjust the kernel tick frequency, usingadjfreq(2), improving accuracy on many machines.
  • allow for weight to be added to sensors or servers, so that one can weight timedelta sensors higher than ntp peers

• Over 3700 ports, 3400 pre-built packages, improved package tools.
• Full support for pkg_add(1) over ssh(1), using one single connection.

• As usual, steady improvements in manual pages and other documentation.

• The system includes the following major components from outside suppliers:
  • X.Org 6.9.0 (+ patches, and i386 contains XFree86 3.3.6 servers(+ patches) for legacy chipsets not supported by X.Org)
  • Gcc 2.95.3(+patches)and 3.3.5(+patches)
  • Perl 5.8.8 (+ patches)
  • Apache 1.3.29, mod_ssl 2.8.16, DSO support (+ patches)
  • OpenSSL 0.9.7j (+ patches)
  • Groff 1.15
  • Sendmail 8.13.8, with libmilter
  • Bind 9.3.2-P1 (+ patches)
  • Lynx 2.8.5rel.4 with HTTPS and IPv6 support (+ patches)
  • Sudo 1.6.8p9
  • Ncurses 5.2
  • Latest KAME IPv6
  • Heimdal 0.7.2 (+ patches)
  • Arla 0.35.7
  • Binutils 2.15 (+ patches)
  • Gdb 6.3 (+ patches)

Following this are the instructions which you would have on a piece ofpaper if you had purchased a CDROM set instead of doing an alternateform of install. The instructions for doing an FTP (or other styleof) install are very similar; the CDROM instructions are left intactso that you can see how much easier it would have been if you hadpurchased a CDROM instead.

• CD1:4.0/i386/INSTALL.i386

• CD2:4.0/amd64/INSTALL.amd64
• CD2:4.0/macppc/INSTALL.macppc

• CD3:4.0/sparc/INSTALL.sparc
• CD3:4.0/sparc64/INSTALL.sparc64

• FTP:.../OpenBSD/4.0/alpha/INSTALL.alpha
• FTP:.../OpenBSD/4.0/armish/INSTALL.armish
• FTP:.../OpenBSD/4.0/cats/INSTALL.cats
• FTP:.../OpenBSD/4.0/hp300/INSTALL.hp300
• FTP:.../OpenBSD/4.0/hppa/INSTALL.hppa
• FTP:.../OpenBSD/4.0/luna88k/INSTALL.luna88k
• FTP:.../OpenBSD/4.0/mac68k/INSTALL.mac68k
• FTP:.../OpenBSD/4.0/mvme68k/INSTALL.mvme68k
• FTP:.../OpenBSD/4.0/mvme88k/INSTALL.mvme88k
• FTP:.../OpenBSD/4.0/sgi/INSTALL.sgi
• FTP:.../OpenBSD/4.0/vax/INSTALL.vax
• FTP:.../OpenBSD/4.0/zaurus/INSTALL.zaurus

Quick installer information for people familiar with OpenBSD, and theuse of the "disklabel -E" command. If you are at all confused wheninstalling OpenBSD, read the relevant INSTALL.* file as listed above!

Play with your BIOS options to enable booting from a CD. The OpenBSD/i386release is on CD1. If your BIOS does not support booting from CD, you will needto create a boot floppy to install from. To create a boot floppy writeCD1:4.0/i386/floppy40.fs to a floppy and boot via the floppy drive.

UseCD1:4.0/i386/floppyB40.fs instead for greater SCSI controllersupport, orCD1:4.0/i386/floppyC40.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 inthe included INSTALL.i386 document.

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

To make a boot floppy under MS-DOS, use the "rawrite" utility locatedatCD1:4.0/tools/rawrite.exe. To make the boot floppy under a Unix OS,use thedd(1)utility. The following is an example usage ofdd(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 oryour install will most likely fail. For more information on creating a bootfloppy and installing OpenBSD/i386 please refer tothis page.

The 4.0 release of OpenBSD/amd64 is located on CD2.Boot from the CD to begin the install - you may need to adjustyour BIOS options first.If you can't boot from the CD, you can create a boot floppy to install from.To do this, writeCD2:4.0/amd64/floppy40.fs to a floppy, thenboot from the floppy drive.

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

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

Put CD2 in your CDROM drive and poweron your machine while holding down theC key until the display turns on and showsOpenBSD/macppc boot.

Alternatively, at the Open Firmware prompt, enterboot cd:,ofwboot/4.0/macppc/bsd.rd

The 4.0 release of OpenBSD/sparc is located on CD3. To boot off of this CD youcan use one of the two commands listed below, depending on the version of yourROM.

okboot cdrom 4.0/sparc/bsd.rdor>b sd(0,6,0)4.0/sparc/bsd.rd

If your SPARC system does not have a CD drive, you can alternatively boot from floppy.To do so you need to writeCD3:4.0/sparc/floppy40.fs to a floppy.For more information seethis page.To boot from the floppy use one of the two commands listed below,depending on the version of your ROM.

okboot floppyor>b fd()

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

If your SPARC system doesn't have a floppy drive nor a CD drive, you can eithersetup a bootable tape, or install via network, as told in theINSTALL.sparc file.

Put CD3 in your CDROM drive and typeboot cdrom.

If this doesn't work, or if you don't have a CDROM drive, you can writeCD3:4.0/sparc64/floppy40.fs orCD3:4.0/sparc64/floppyB40.fs(depending on your machine) to a floppy and boot it withbootfloppy. Refer to INSTALL.sparc64 for details.

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

You can also writeCD3:4.0/sparc64/miniroot40.fs to the swap partition onthe disk and boot withboot disk:b.

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

WriteFTP:4.0/alpha/floppy40.fs orFTP:4.0/alpha/floppyB40.fs (depending on your machine) to a diskette andenterboot dva0. Refer to INSTALL.alpha for more details.

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

After connecting a serial port, Thecus can boot directly from the networkeither 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 linuxand 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.

After updating the firmware to at least ABLE 1.95 if necessary, bootFTP:4.0/cats/bsd.rd from an ABLE-supported device (such as a CD-ROMor 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 thehppa 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 tothe instructions in INSTALL.luna88k for more details.

Boot MacOS as normal and extract the Macside "BSD/Mac68k Booter" utility fromFTP:4.0/mac68k/utils onto your hard disk. Configure the "BSD/Mac68kBooter" with the location of your bsd.rd kernel and boot into the installer.Refer to the instructions in INSTALL.mac68k for more details.

You can create a bootable installation tape or boot over the network.
The network boot requires a MVME68K BUG version that supports theNIOTandNBO debugger commands. Follow the instructions in INSTALL.mvme68kfor more details.

You can create a bootable installation tape or boot over the network.
The network boot requires a MVME88K BUG version that supports theNIOTandNBO debugger commands. Follow the instructions in INSTALL.mvme88kfor more details.

Burn cd40.iso on a CD-R, put it in the CD drive of your machine andselectInstall System Software from the System Maintenance menu.

If your machine doesn't have a CD drive, you cansetup a DHCP/tftp network server, and boot using "bootp()/bsd.rd".Refer to the instructions in INSTALL.sgi for more details.

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

Using the Linux built-in graphical ipkg installer, install theopenbsd40_arm.ipk package. Reboot, then run it. Read INSTALL.zaurusfor a few important details.

src.tar.gz contains a source archive starting at /usr/src. This filecontains everything you need except for the kernel sources, which arein 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 itis possible to get a head-start on using the anoncvs servers asdescribedhere.Using these filesresults in a much faster initial CVS update than you could expect froma fresh checkout of the full OpenBSD source tree.

If you already have an OpenBSD 3.9 system, and do not want to reinstall,upgrade instructions and advice can be found in theUpgrade Guide.

A ports tree archive is also provided. To extract:

#cd /usr#tar xvfz /tmp/ports.tar.gz#cd ports

Theports/ subdirectory is a checkout of the OpenBSD ports tree. Goread theports pageif you know nothing about portsat 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 theOpenBSD ports system.

Theports/ directory represents a CVS (see the manpage forcvs(1) ifyou aren't familiar with CVS) checkout of our ports. As with our completesource tree, our ports tree is available via anoncvs. So, inorder to keep current with it, you must make theports/ treeavailable on a read-write medium and update the tree with a commandlike:

#cd [portsdir]/; cvs -d anoncvs@server.openbsd.org:/cvs update -Pd -rOPENBSD_4_0

[Of course, you must replace the local directory and server name herewith the location of your ports collection and a nearby anoncvsserver.]

Note that most ports are available as packages through FTP. Updatedpackages for the 4.0 release will be made available if problems arise.

If you're interested in seeing a port added, would like to help out, or justwould like to know more, the mailing list ports@openbsd.org is a goodplace to know.