=================================================================== RCS file: /cvsrepo/anoncvs/cvs/www/53.html,v retrieving revision 1.90 retrieving revision 1.91 diff -c -r1.90 -r1.91 *** www/53.html 2019/04/24 15:54:53 1.90 --- www/53.html 2019/05/27 22:55:18 1.91 *************** *** 1,29 **** ! ! !
!
Released May 1, 2013
Copyright 1997-2013, Theo de Raadt.
! ISBN 978-0-9881561-1-1
5.3 Song: "Blade Swimmer"
--- 1,41 ----
!
!
!
!
! ! |
Released May 1, 2013 Copyright 1997-2013, Theo de Raadt. ! ISBN 978-0-9881561-1-1 5.3 Song: "Blade Swimmer" *************** *** 31,37 ****
|
This is a partial list of new features and systems included in OpenBSD 5.3. For a comprehensive list, see the changelog leading to 5.3. *************** *** 58,134 ****
!
hwfeatures
displays the maximum MTU supported by the driver (indicating support for jumbo/baby-jumbo frames).
!
!
!
--- 216,222 ----
*************** *** 214,220 ****
diff-buffer-with-file
, make-directory
and revert-buffer
.
Column numbers have been made configurable and locale is respected for ctype purposes, like displaying ISO Latin 1 characters.
! AuthenticationMethods
option. This option lists one
or more comma-separated lists of authentication method names.
Successful completion of all the methods in any list is required for
authentication to complete. This allows, for example, requiring a
user having to authenticate via public key or GSSAPI before they are
offered password authentication.
! RevokedKeys
! sshd_config(5)
option.
! IdentitiesOnly
now applies to keys obtained from a
PKCS11Provider. This allows control of which keys are offered from
! tokens using IdentityFile
.
! local
" and "remote
"
! in addition to its previous "yes
"/"no
" keywords to
allow the server to specify whether just local or remote TCP
forwarding is enabled.
! AuthorizedKeysCommand
to support fetching
authorized_keys from a command in addition to (or instead of) from
the filesystem. The command is run under an account specified by an
! AuthorizedKeysCommandUser
! sshd_config(5)
option.
! -d
option to allow the starting directory to
be something other than the user's home directory.
! ~v
and ~V
escape sequences to raise and lower
the logging level respectively.
! ~?
) context sensitive so that
only commands that will work in the current session are shown.
! ~.
escape sequence is used. This means that ~.
should now work in mux clients even if the server is no longer
responding.
! -k
option to
allow deleting of the key only.
! -N
, ensure that it shuts down
gracefully when a client sends it "-O stop" rather than hanging
around. (bz#1985)
!
!
|
|
|
|
-
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 --- 465,479 ----
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 *************** *** 504,517 ****
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 *************** *** 534,559 **** To make a boot floppy under MS-DOS, use the "rawrite" utility located at CD1:5.3/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. -
-
# 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. +
The 5.3 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. *************** *** 569,579 ****
If you are planning to dual boot OpenBSD with another OS, you will need to read INSTALL.amd64. -
-
If you are planning to dual boot OpenBSD with another OS, you will need to read INSTALL.amd64. +
Burn the image from the FTP site to a CDROM, and poweron your machine while holding down the C key until the display turns on and shows OpenBSD/macppc boot. *************** *** 581,591 ****
Alternatively, at the Open Firmware prompt, enter boot cd:,ofwboot /5.3/macppc/bsd.rd -
-
--- 588,597 ----
Alternatively, at the Open Firmware prompt, enter boot cd:,ofwboot /5.3/macppc/bsd.rd +
Put CD3 in your CDROM drive and type boot cdrom.
*************** *** 604,615 ****
If nothing works, you can boot over the network as described in INSTALL.sparc64. -
!
Write FTP:5.3/alpha/floppy53.fs or FTP:5.3/alpha/floppyB53.fs (depending on your machine) to a diskette and enter boot dva0. Refer to INSTALL.alpha for more details. --- 610,620 ----
If nothing works, you can boot over the network as described in INSTALL.sparc64. +
! Write FTP:5.3/alpha/floppy53.fs or FTP:5.3/alpha/floppyB53.fs (depending on your machine) to a diskette and enter boot dva0. Refer to INSTALL.alpha for more details. *************** *** 617,628 **** Make sure you use a properly formatted floppy with NO BAD BLOCKS or your install will most likely fail. !
-
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. --- 622,630 ---- Make sure you use a properly formatted floppy with NO BAD BLOCKS or your install will most likely fail. !
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. *************** *** 630,703 **** 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. -
-
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. -
-
Write miniroot53.fs to the start of the CF or disk, and boot normally. -
-
Write miniroot53.fs to a USB stick and boot bsd.rd from it or boot bsd.rd via tftp. Refer to the instructions in INSTALL.loongson for more details. -
-
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. -
-
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.
-
-
To install on an O2, burn cd53.iso on a CD-R, put it in the CD drive of your machine and select Install System Software from the System Maintenance menu. --- 632,688 ---- 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. +
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. +
Write miniroot53.fs to the start of the CF or disk, and boot normally. +
Write miniroot53.fs to a USB stick and boot bsd.rd from it or boot bsd.rd via tftp. Refer to the instructions in INSTALL.loongson for more details. +
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. +
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.
+
To install on an O2, burn cd53.iso on a CD-R, put it in the CD drive of your machine and select Install System Software from the System Maintenance menu. *************** *** 707,733 **** setup a DHCP/tftp network server, and boot using "bootp()/bsd.rd.IP##" using the kernel matching your system type. Refer to the instructions in INSTALL.sgi for more details. -
-
After connecting a serial port, boot over the network via DHCP/tftp. Refer to the instructions in INSTALL.socppc for more details. -
-
! ok boot cdrom 5.3/sparc/bsd.rd or ! > b sd(0,6,0)5.3/sparc/bsd.rd !
If your SPARC system does not have a CD drive, you can alternatively boot from floppy. --- 692,715 ---- setup a DHCP/tftp network server, and boot using "bootp()/bsd.rd.IP##" using the kernel matching your system type. Refer to the instructions in INSTALL.sgi for more details. +
After connecting a serial port, boot over the network via DHCP/tftp. Refer to the instructions in INSTALL.socppc for more details. +
Boot from one of the provided install ISO images, using one of the two commands listed below, depending on the version of your ROM. !
! ok boot cdrom 5.3/sparc/bsd.rd or ! > b sd(0,6,0)5.3/sparc/bsd.rd !
If your SPARC system does not have a CD drive, you can alternatively boot from floppy. *************** *** 736,746 **** 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 --- 718,728 ---- 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 *************** *** 750,794 **** 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. -
-
-
Using the Linux built-in graphical ipkg installer, install the openbsd53_arm.ipk package. Reboot, then run it. Read INSTALL.zaurus for a few important 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 --- 732,777 ---- 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. +
Boot over the network via mopbooting as described in INSTALL.vax. +
Using the Linux built-in graphical ipkg installer, install the openbsd53_arm.ipk package. Reboot, then run it. Read INSTALL.zaurus for a few important 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 *************** *** 796,824 **** 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 5.2 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 !
The ports/ subdirectory is a checkout of the OpenBSD ports tree. Go read the ports page --- 779,809 ---- 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 5.2 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 !
The ports/ subdirectory is a checkout of the OpenBSD ports tree. Go read the ports page *************** *** 828,834 **** 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 --- 813,819 ---- 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 *************** *** 837,846 **** available on a read-write medium and update the tree with a command like:
!
# cd /usr/ports # cvs -d anoncvs@server.openbsd.org:/cvs update -Pd -rOPENBSD_5_3 !
[Of course, you must replace the server name here with a nearby anoncvs server.] --- 822,831 ---- available on a read-write medium and update the tree with a command like:
!
# cd /usr/ports # cvs -d anoncvs@server.openbsd.org:/cvs update -Pd -rOPENBSD_5_3 !
[Of course, you must replace the server name here with a nearby anoncvs server.] *************** *** 851,857 **** 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. !
! ! ! --- 836,839 ---- 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. !