wireguard-openbsd/distrib/alpha, branch jd/simplify-queueingWireGuard implementation for the OpenBSD kernelhttps://git.zx2c4.com/wireguard-openbsd/atom/distrib/alpha?h=jd%2Fsimplify-queueing2020-05-18T06:20:43ZMake ffs2 the default for newfs; change all calls to create e.g. floppy2020-05-18T06:20:43Zottootto@openbsd.org2020-05-18T06:20:43Zurn:sha1:6bc807e4d833195ee4c71cebd213a6e33dd463fa
filesystems or ramdisks to use explicit -O 1; installer already does that.
ok sthen@
Change install images called *.fs to *.img. These are UFS filesystem images,2020-05-17T17:04:27Zderaadtderaadt@openbsd.org2020-05-17T17:04:27Zurn:sha1:4675fc66a864566d1639c35678d029ce2c447edd
but additionally have a bootblock in the first 8K (since UFS does not use that
space). There are some UEFI direct-from-internet bootloaders that require
the name *.img. So this makes things more convenient for those, while keeping
it consistant in all architectures.
ok kettenis beck kn
typo (result was bootblocks from / always installed into media); from miod2019-11-19T09:46:22Zderaadtderaadt@openbsd.org2019-11-19T09:46:22Zurn:sha1:43a6d64ac48b522166f01c172ad0bbcdce9c64eeeliminate differences between all the list files as much as2019-06-07T14:39:54Zderaadtderaadt@openbsd.org2019-06-07T14:39:54Zurn:sha1:b2c5e89128f704fe66b98fa4377ed2230842ee4d
possible, and remove the failed previous attempts at sharing
in ./miniroot and ./ramdisk. maybe now that differences are
eliminated we can start a new sharing effort? i dunno..
Add tee(1) to the ramdisk filesystem and use it to provide both a2019-05-13T23:18:21Znaddynaddy@openbsd.org2019-05-13T23:18:21Zurn:sha1:9ff7454ddbaded13c953b48a93f25d8625e8a99c
moving progress bar during auto upgrade/install and a clean log
afterwards. ok deraadt@
Further removal of differences (using install instead of cp, sorting2019-05-03T20:03:57Zderaadtderaadt@openbsd.org2019-05-03T20:03:57Zurn:sha1:0e6c59ceb58e026875afdf7d00349440bdaa4789
chunks in a specified order, using a few variables, performing bsd.rd
to bsd.gz conversion as similar as possible)
increase verbose +1 (the required level for spitting out block start/end2019-05-01T20:53:34Zderaadtderaadt@openbsd.org2019-05-01T20:53:34Zurn:sha1:90d980fe6cdbf05801eb0ad5c31a44a62ad6b8b6
for files, which is tee'd out to tell installboot where the bootblocks
should point to..) Yes, someone could fix this, but it won't be me today!
step by step, more removal of differences2019-04-30T23:37:31Zderaadtderaadt@openbsd.org2019-04-30T23:37:31Zurn:sha1:e602012db9edbc2f9a99d026a09dc8eaf112e493repair more trivial differences2019-04-30T23:25:19Zderaadtderaadt@openbsd.org2019-04-30T23:25:19Zurn:sha1:4d23fe49f8a8187b560c78bea9cf4c100fd74ac7rm is in /bin, no need to specify2019-04-30T21:14:58Zderaadtderaadt@openbsd.org2019-04-30T21:14:58Zurn:sha1:03c1d9f766f2874e8fc5727de7a42f8eb45dbaeb