<feed xmlns='http://www.w3.org/2005/Atom'>
<title>wireguard-openbsd/distrib/notes/macppc/install, branch jd/simplify-queueing</title>
<subtitle>WireGuard implementation for the OpenBSD kernel</subtitle>
<id>https://git.zx2c4.com/wireguard-openbsd/atom/distrib/notes/macppc/install?h=jd%2Fsimplify-queueing</id>
<link rel='self' href='https://git.zx2c4.com/wireguard-openbsd/atom/distrib/notes/macppc/install?h=jd%2Fsimplify-queueing'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/'/>
<updated>2014-10-10T13:25:08Z</updated>
<entry>
<title>r1.45 of macppc install.md eliminated the verbiage exhorting users</title>
<updated>2014-10-10T13:25:08Z</updated>
<author>
<name>krw</name>
<email>krw@openbsd.org</email>
</author>
<published>2014-10-10T13:25:08Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=8d2ba1a8814ab684c9f8b2180c4f39e544d6ec4f'/>
<id>urn:sha1:8d2ba1a8814ab684c9f8b2180c4f39e544d6ec4f</id>
<content type='text'>
to create an HFS partition with type AND name 'OpenBSD'. Worse, it
added checks to make sure the partition type and name were correct.

Sevan Janiyan pointed out that the example in INSTALL.macppc did
not show the 'n' command required to set the name of the OpenBSD
partition to 'OpenBSD'. Thus leaving HFS users possibly puzzled
over partitioning prerequisites.

Add required command to example.
</content>
</entry>
<entry>
<title>you are still welcome to install from tape, but as befits an elite master</title>
<updated>2014-03-19T01:59:48Z</updated>
<author>
<name>tedu</name>
<email>tedu@openbsd.org</email>
</author>
<published>2014-03-19T01:59:48Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=a3192fd5e2b88c6e4a2ffc0484d69629cd7433cb'/>
<id>urn:sha1:a3192fd5e2b88c6e4a2ffc0484d69629cd7433cb</id>
<content type='text'>
of unix arcana, we will not condescend to tell you how. why spoil the fun?
</content>
</entry>
<entry>
<title>committing uwe's autoinstall notes, as requested by deraadt;</title>
<updated>2013-12-04T23:20:19Z</updated>
<author>
<name>jmc</name>
<email>jmc@openbsd.org</email>
</author>
<published>2013-12-04T23:20:19Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=2f2506daca014585b8dd547c1edac3249cc4226a'/>
<id>urn:sha1:2f2506daca014585b8dd547c1edac3249cc4226a</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Jumbo commit for 4.7 installation instructions:</title>
<updated>2010-03-16T17:23:05Z</updated>
<author>
<name>miod</name>
<email>miod@openbsd.org</email>
</author>
<published>2010-03-16T17:23:05Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=670b07cf0da4750e213677cafc465b6054245a0c'/>
<id>urn:sha1:670b07cf0da4750e213677cafc465b6054245a0c</id>
<content type='text'>
- do not mention tape as an installation media on systems where it is very
  unlikely that a tape drive can be connected to (i.e. anything with only
  USB as expansion capabilities)
- do not mention that fetching the installation sets from a partition is
  ``for upgrades only''. You may do this for installation, but of course
  you can not use a partition which will be newfs'ed for that purpose.
- mention ext2fs partitions as possible installation sets source only on
  platforms where the installation media actually can mount an ext2fs
  filesystem.
- stress the fact that the sparc miniroot image is a GENERIC kernel with
  a little on-disk filesystem, and not a RAMDISK kernel with a little
  in-memory filesystem, and thus must not be overwritten during installation
  (i.e. be careful if you repartition the disk the miniroot has been put on).
- more conv=sync -&gt; conv=osync for tape setup instructions.
- model-specific layout changes on armish, loongson and socppc instructions.
- fix various typos and grammar mistaeks.

"sure" deraadt@ (without eyeballing)
</content>
</entry>
<entry>
<title>Better disk partitioning details, especially for MBR + disklabel or</title>
<updated>2009-05-13T18:38:27Z</updated>
<author>
<name>miod</name>
<email>miod@openbsd.org</email>
</author>
<published>2009-05-13T18:38:27Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=6f27322a2df174cf23d0c59d9c0ac5e242fc3a4b'/>
<id>urn:sha1:6f27322a2df174cf23d0c59d9c0ac5e242fc3a4b</id>
<content type='text'>
HFS + disklabel setups.
</content>
</entry>
<entry>
<title>Try to catch up with installer changes in the installation notes.</title>
<updated>2009-05-12T21:06:48Z</updated>
<author>
<name>miod</name>
<email>miod@openbsd.org</email>
</author>
<published>2009-05-12T21:06:48Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=d24adbaf4b1ee34fd6533ed2d82b5cbfdd4a1e24'/>
<id>urn:sha1:d24adbaf4b1ee34fd6533ed2d82b5cbfdd4a1e24</id>
<content type='text'>
Also, the per-platform features are moved to a common place, which makes
the MD layout easier to work on. m4.common is still a tangled mess of subtly
placed dnl, though...
</content>
</entry>
<entry>
<title>Clarify and modernize some language about disk layout and the interactive</title>
<updated>2008-10-16T00:05:09Z</updated>
<author>
<name>krw</name>
<email>krw@openbsd.org</email>
</author>
<published>2008-10-16T00:05:09Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=0a5b96cce1db152e92416d56fc7d67f427b1e43d'/>
<id>urn:sha1:0a5b96cce1db152e92416d56fc7d67f427b1e43d</id>
<content type='text'>
label editor. Prompted by comments from Rad Ricka.

Suggestions from jmc@, deraadt@ and Rad.

ok deraadt@
</content>
</entry>
<entry>
<title>Foreign partition on MBR partition tables are put in default disklabels</title>
<updated>2008-08-06T18:20:53Z</updated>
<author>
<name>miod</name>
<email>miod@openbsd.org</email>
</author>
<published>2008-08-06T18:20:53Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=3170999827e69a7c36e114af4ecf2edf72d524fb'/>
<id>urn:sha1:3170999827e69a7c36e114af4ecf2edf72d524fb</id>
<content type='text'>
from partition `i' onwards, not `h' onwards.
</content>
</entry>
<entry>
<title>Better description of the installation steps:</title>
<updated>2008-08-05T22:57:59Z</updated>
<author>
<name>miod</name>
<email>miod@openbsd.org</email>
</author>
<published>2008-08-05T22:57:59Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=e0ac281b6d8425c62b3760c2db367a6916583b1d'/>
<id>urn:sha1:e0ac281b6d8425c62b3760c2db367a6916583b1d</id>
<content type='text'>
- document questions in proper order: hostname before network configuration,
  DNS only if network is configured, sshd and ntpd, aperture only on
  machines which need it, serial console only on machines which need it.
  This is done by splitting the end of OpenBSDCommonURL in various
  macros, OpenBSDInstallWrapup, OpenBSDInstallAperture, OpenBSDInstallConsole
  and OpenBSDInstallWrapupPart2.
- use the above macros when appropriate, OpenBSDInstallWrapup* being
  mandatory on all arches.
- remove serial console configuration blurb on sparc and sparc64, it is
  handled by OpenBSDInstallConsole now.
</content>
</entry>
<entry>
<title>Suggest vt220 as a TERM value for serial-console-in-an-xterm setup everywhere</title>
<updated>2008-03-10T21:38:27Z</updated>
<author>
<name>miod</name>
<email>miod@openbsd.org</email>
</author>
<published>2008-03-10T21:38:27Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=bde736628b17fd4e41747397141d23b1b662d2a9'/>
<id>urn:sha1:bde736628b17fd4e41747397141d23b1b662d2a9</id>
<content type='text'>
instead of a mix of vt100 and vt220.
</content>
</entry>
</feed>
