| Age | Commit message (Collapse) | Author |
|---|
|
|
|
sysupgrade changes
|
|
Firmware is fetched after bootstraps are installed, i.e. on fresh installs
apple-boot is not there yet when installboot ought to place it onto the EFI
System Partition.
Rerun --only on Apple silicon-- to replace Asahi u-boot and boot straight
into ours, nicely visible my different logo.
Input sthen deraadt
|
|
Somehow I did not amend those right away when adding local _disk in r1.43
|
|
|
|
ok deraadt@ kn@
|
|
|
|
|
|
|
|
|
|
install.sub r1.1245 "Ask for disk crypto after root disk question" got rid
of global CRYPTO* variables; no functional change.
|
|
confusing users with FFS attributes that only experts should
fiddle with. Actual use has withered away with functionality
rendered moot or moved elsewhere.
'-e' remains for the truly obscure corner cases.
Simply excise the code for now to see if hidden users/uses are
exposed. Further simplifications are possible if no such
users/uses surface.
ok with sthen@ millert@ kn@ otto@
|
|
Tested with Comfast CF-WU710N v4.
"go ahead" deraadt@
OK stsp@
|
|
Make sure we don't newfs the EFI Sys partition on systems that have an
"apfsisc" partition in the case we're installing with softraid crypto.
Debugged with help from and came up with a fix with kn@
"go ahead" kettenis@
"no objections" krw@
OK kn@
|
|
Chosing [W]hole on a GPT disk means it needs non-default `-b' fdisk(8)
to account for existing EFI Sys partitions, whether it modifies an existing
GPT (Apple APFS ISC) or writing a new one.
With 'Encrypt the root disk?' answered postively, the crypto disk instead of
the root disk becomes the boot disk.
Extend the logic to both crypto and root disk, really asking
"is this a boot disk?".
with caspar
|
|
No functional change.
Noticed by & ok kn@
|
|
'install' disktab entries.
No functional change.
|
|
on apple silicon so that we don't fill up the ramdisk by extracting the
whole tarball
while here, change the code so that the machdep.compatible sysctl gets
read once and then that value is used in the script instead of calling
sysctl several times
from input and ok kn@, kettenis@
|
|
All board specific quirks inside the installer (and other bugs) relating to
root on softraid are fixed, so that install media with the new question
just works for plain as well as encrypted installs.
Tested on Pinebook Pro, Raspberry Pi 4b, SolidRun CEX7.
|
|
Various files are put onto a pi's ESP, assuming root disk means boot disk,
which is not true for root on softraid(4).
Wrap the code in a loop over chunks (if any) or the single disk as before,
just like installboot(8) does.
OK mbuhl
|
|
pine64 happens to be the first board "we ran on", as kettenis explains, and
this code tries to handle the situation of installing to the same disk the
installer booted from.
Similar boards like the Pinebook Pro don't get special treatment and work;
INSTALL.arm64 already explains how to flash required firmware onto disks or
install media -- Allwinner SoCs like the pine64 included.
Spotted through md_installboot() dd'ing blobs onto the root disk,
which does not fly with root on softraid and is in the way of arm64 getting
support for guided disk encryption.
Suggested by kettenis patrick
Feedback jsg patrick
OK patrick
|
|
There since introduction, lucked out since it is the last case.
No functional change.
|
|
All other dd invocations in installer code, INSTALL.* instructions and
dd(1) EXAMPLES use the disk's "raw device".
|
|
`_disk' (and related variables) hold disk names as "sd0" so that all else
can be constructed from it.
Fix the only two offenders across distrib/ which put start the variable
with "/dev/"; no functional change.
|
|
Less duplicate code, easier to add new firmware.
OK afresh1
|
|
We must not discard all errors, just disable informational messages.
OK tb
|
|
root partition.
Identical behaviour as but more readable than the "echo 'a
a\n\n\n\nw\nq\n'| disklabel -E" it replaces.
It also eliminates the extraneous output of -E that required
">/dev/null".
ok kn@
|
|
split across `echo -n' and `echo'. Those in single `echo' have it.
|
|
they are using a glass console and kezboard.
tested with a Thinkpad X13s with a DE kezboard.
OK deraadt@ miod@ kn@
|
|
model there might be no firmware and we want to avoid confusing users
with WARNING messages about patterns that were not matched.
ok deraadt@
|
|
Missed in previous
OK kettenis
|
|
ok kn@, deraadt@
|
|
games in there, in particular during BIOS upgrade sequences.
ok krw kettenis dv
|
|
because of the the tar+mv combination. Purge both path variations
better, so that an interrupted install can be restarted.
ok miod abieber kettenis
|
|
running Xorg in a way that isn't fully understood. So change the arm64
install.md to munge /etc/ttys to enable the ttyC0 entry if we detect that
wsdisplay0 is the console and make sure the code in install.sub that
does the actual munging disables the console entry before enabling another
entry to prevent running two getty(8) processes on (effectively) the same
device.
ok deraadt@
|
|
This mostly adds some checks to make sure that if for some reason the firmware
files aren't present on the EFI System Partition the users doesn't see
several error messages.
ok deraadt@
|
|
formatting the partition such that its contents actually survive.
ok krw@
|
|
Improved chicken scratches from tb@
|
|
devices and copy it into the right directory on the ramdisk such that it
can be used in the installer. And copy it in place at the end of the
install procedure such that it is available for use in the newly installed
system.
ok deraadt@
|
|
Build, boot and install tested by bluhm@
ok bluhm@
|
|
scripting doing the same thing from here.
ok deraadt@, visa@
|
|
ok sthen@, jsg@, deraadt@
|
|
ok deraadt@
|
|
No functional change.
|
|
of running newfs_msdos, so fsck_msdos gets run behind the scenes. A few
architectures were missing this binary on their install media
jsg notices two more arch need it also, due to crazy Makefile games in installboot
|
|
Running `make -j4' in /usr/src/distrib/amd64/ramdisk_cd/ et al. executes
make(1) to both build the RAMDISK kernel and build libraries.
Doing so does not propagate the flags specified to the ramdisk_cd
invocation, which in turn means `-j4' for example is ignored and both kernel
and libraries will not be built in parallel.
Pass make(1)'s MFLAGS along to retain relevant flags; make is clever enough
to separate flags, variable assignments and targets from each other and only
pass 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 since
the `bsd' target does `make clean' and therefore builds a new kernel every
time.
OK deraadt
|
|
ok krw@, deraadt@
|
|
is required because of TLS servername for contacting ftp.openbsd.org, and
there is no point doing that in resolv.conf.tail because it is no longer used.
ok florian kn
|
|
OK deraadt who also helped making some space.
|
|
partition is detected. Otherwise the normal big hammer fdisk -ig.
Only create EFI SYS boot partition on GPT disks that are the ROOTDISK.
ok kettenis@ deraadt@
|
