Remove dead CRYPTOCHUNK usageinstall.sub r1.1245 "Ask for disk crypto after root disk question" got ridof global CRYPTO* variables; no functional change.
Retire -E's "expert" mode. Introduced 23 years ago to avoidconfusing users with FFS attributes that only experts shouldfiddle with. Actual use has withered away with functionalityrendered moot or
Retire -E's "expert" mode. Introduced 23 years ago to avoidconfusing users with FFS attributes that only experts shouldfiddle with. Actual use has withered away with functionalityrendered moot or moved elsewhere.'-e' remains for the truly obscure corner cases.Simply excise the code for now to see if hidden users/uses areexposed. Further simplifications are possible if no suchusers/uses surface.ok with sthen@ millert@ kn@ otto@
show more ...
Add support for RTL8188FTV chip to urtwn(4).Tested with Comfast CF-WU710N v4."go ahead" deraadt@OK stsp@
Treat crypto disk like the root disk, both are boot disksChosing [W]hole on a GPT disk means it needs non-default `-b' fdisk(8)to boot and preserve any existing BIOS boot partition.With 'Encrypt
Treat crypto disk like the root disk, both are boot disksChosing [W]hole on a GPT disk means it needs non-default `-b' fdisk(8)to boot and preserve any existing BIOS boot partition.With 'Encrypt the root disk?' answered postively, the crypto disk instead ofthe root disk becomes the boot disk.Extend the sanity check to both crypto and root disk, really asking"is this a boot disk?".This preserves existing boot partitions when using guided disk encryption.
Change variables 'MRFSDISKTYPE' to 'MRDISKTYPE' like every other arch.No functional change.Noticed by & ok kn@
Initial support for guided disk encryptionOne new question to cover the most common use case, such that manual setupin (S)hell or '!' prior to install is no longer required: Encrypt the root
Initial support for guided disk encryptionOne new question to cover the most common use case, such that manual setupin (S)hell or '!' prior to install is no longer required: Encrypt the root disk? (disk, 'no' or '?' for details) [no] ? Create a passphrase protected CRYPTO softraid volume to be used as root disk. Available disks are: sd0. Encrypt the root disk? (disk, 'no' or '?' for details) [no]Use of keydisk or different disciplines are not covered.Only asked in interactive installations; no autoinstall(8) or upgrades.Only reachable on i386, amd64, sparc64 and riscv64 for now (arm64 WIP).Tested by cheloha naddy and a few usersFeedback from cheloha deraadt claudioOK cheloha"get it in now" deraadt
Use "echo '/ *' | disklabel -wAT-" to put all free space into theroot partition.Identical behaviour as but more readable than the "echo 'aa\n\n\n\nw\nq\n'| disklabel -E" it replaces.It also eli
Use "echo '/ *' | disklabel -wAT-" to put all free space into theroot partition.Identical behaviour as but more readable than the "echo 'aa\n\n\n\nw\nq\n'| disklabel -E" it replaces.It also eliminates the extraneous output of -E that required">/dev/null".ok kn@
Add space after comma in MD "No * partition in *,try again." repliessplit across `echo -n' and `echo'. Those in single `echo' have it.
Allow installation on a disk with a GPT.OK krw@
Use the '-b' to create boot partitions instead of '-e' scripts.Media creation & subsequent installation tests by visa@ok visa@
Use installboot(8) in install.md of riscv64.OK kettenis@ deraadt@
Add firmwares for rsu(4), rtwn(4), and urtwn(4) drivers.ok deraadt@
new installboot will sometimes reuse the existing msdos boot partition insteadof running newfs_msdos, so fsck_msdos gets run behind the scenes. A fewarchitectures were missing this binary on their
new installboot will sometimes reuse the existing msdos boot partition insteadof running newfs_msdos, so fsck_msdos gets run behind the scenes. A fewarchitectures were missing this binary on their install mediajsg notices two more arch need it also, due to crazy Makefile games in installboot
MP support seems to work fine nowok deraadt@
Pass make flags to kernel and lib buildsRunning `make -j4' in /usr/src/distrib/amd64/ramdisk_cd/ et al. executesmake(1) to both build the RAMDISK kernel and build libraries.Doing so does not pro
Pass make flags to kernel and lib buildsRunning `make -j4' in /usr/src/distrib/amd64/ramdisk_cd/ et al. executesmake(1) to both build the RAMDISK kernel and build libraries.Doing so does not propagate the flags specified to the ramdisk_cdinvocation, which in turn means `-j4' for example is ignored and both kerneland libraries will not be built in parallel.Pass make(1)'s MFLAGS along to retain relevant flags; make is clever enoughto separate flags, variable assignments and targets from each other and onlypass along things to `MFLAGS' that'd make sense, i.e. `make -C. -j4 foo=bar'does *not* pass `-C.' to change directories.(can be easily tested with `make -p ... | grep MFLAGS'.)This makes hacking on ramdisks/the installer much faster, espescially sincethe `bsd' target does `make clean' and therefore builds a new kernel everytime.OK deraadt
Remove hackery around /tmp/i/resolv.conf*. In particular "lookup file bind"is required because of TLS servername for contacting ftp.openbsd.org, andthere is no point doing that in resolv.conf.tail
Remove hackery around /tmp/i/resolv.conf*. In particular "lookup file bind"is required because of TLS servername for contacting ftp.openbsd.org, andthere is no point doing that in resolv.conf.tail because it is no longer used.ok florian kn
Replace dhclient with dhcpleased/resolvd on the ramdisk.OK deraadt who also helped making some space.
do not guess at MP support yet.
Correct the library path for native build of ramdisks.
Adjust ramdisk generation for self hosting, remove cross bits.
Riscv64 distrib pieces to buld ramdiskCopied from arm64 with minimal changes.ok deraadt@