wireguard-openbsd/distrib/notes/alpha/install, branch jd/queueboostsWireGuard implementation for the OpenBSD kernelhttps://git.zx2c4.com/wireguard-openbsd/atom/distrib/notes/alpha/install?h=jd%2Fqueueboosts2020-04-28T13:02:10ZThere have been no floppy images since the 6.2 release. Remove mention2020-04-28T13:02:10Zbennobenno@openbsd.org2020-04-28T13:02:10Zurn:sha1:dda1a9012ff5b9d7eee1d04bd49034b560134e17
of boot floppies from the INSTALL.alpha notes.
ok deraadt@
text improvements from evan silberman;2019-08-01T19:42:51Zjmcjmc@openbsd.org2019-08-01T19:42:51Zurn:sha1:c529027a472a645706064133decf320ef60b2f82
tweaked along the way by at least myself and tj;
ok tj deraadt
A first shot at MOP boot instructions.2014-12-13T15:45:53Zmiodmiod@openbsd.org2014-12-13T15:45:53Zurn:sha1:7c1144749d61b1224dfebe1b36399bed6ddbd144you are still welcome to install from tape, but as befits an elite master2014-03-19T01:59:48Ztedutedu@openbsd.org2014-03-19T01:59:48Zurn:sha1:a3192fd5e2b88c6e4a2ffc0484d69629cd7433cb
of unix arcana, we will not condescend to tell you how. why spoil the fun?
committing uwe's autoinstall notes, as requested by deraadt;2013-12-04T23:20:19Zjmcjmc@openbsd.org2013-12-04T23:20:19Zurn:sha1:2f2506daca014585b8dd547c1edac3249cc4226aStop using the name `miniroot' when `bsd.rd' is implied. A few platforms2013-02-09T19:48:37Zmiodmiod@openbsd.org2013-02-09T19:48:37Zurn:sha1:5a47d83823196019ab8ef1956d9a87803ef900b9
have a real miniroot to be dd'ed to the disk, and that's fine; but when
we are talking about booting bsd.rd (either from an existing setup, or the
network, or the cd-rom images), then refer to it as `installation kernel'.
Usual release distrib/notes churning. ok deraadt@2011-08-08T20:03:03Zmiodmiod@openbsd.org2011-08-08T20:03:03Zurn:sha1:b4259f1cb10a5c86ffbde4e2a3c86cce987ce593Jumbo commit for 4.7 installation instructions:2010-03-16T17:23:05Zmiodmiod@openbsd.org2010-03-16T17:23:05Zurn:sha1:670b07cf0da4750e213677cafc465b6054245a0c
- 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 -> 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)
Better disk partitioning details, especially for MBR + disklabel or2009-05-13T18:38:27Zmiodmiod@openbsd.org2009-05-13T18:38:27Zurn:sha1:6f27322a2df174cf23d0c59d9c0ac5e242fc3a4b
HFS + disklabel setups.
Try to catch up with installer changes in the installation notes.2009-05-12T21:06:48Zmiodmiod@openbsd.org2009-05-12T21:06:48Zurn:sha1:d24adbaf4b1ee34fd6533ed2d82b5cbfdd4a1e24
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...