Age | Commit message (Collapse) | Author |
|
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@
|
|
folks from shooting themselves in the foot. Make sure (W) can't be used
if an "APFS ISC" is found on the disk. This is the most essential
partition that is required for Apple M1 machines to boot.
ok krw@, deraadt@
|
|
ok krw@
|
|
Also recognize Apple "platforms" and change the default from "whole" to
"edit" when installing on disk with a GPT on those. This should prevent
users from accidentally overwriting essential partitions that are needed
to boot those machines.
ok deraadt@
|
|
amd64. This makes the installer recognize an OpenBSD partition such that
the installation will proceed if such a partition is found.
ok krw@, deraadt@
|
|
U-Boot binaries that work on Raspberry Pi 3 and 4 (and possibly others)
and firmware for Raspberry Pi 4. This allows the same installation
method as used on Raspberry Pi 3 without separate UEFI firmware
(although UEFI can still be used). Help from kettenis@ jsg@ deraadt@
|
|
|
|
requested by kettenis, first testing by kn
|
|
arm64 ramdisk has customization in mr.fs target, in order to create
usr/mdec/pine64 and usr/mdec/rpi directories (files will be copied
inside them by runlist.sh).
uses MKDIR directive to create these directories instead of.
it put back mr.fs target identical to others archs.
ok deraadt@
|
|
filesystems or ramdisks to use explicit -O 1; installer already does that.
ok sthen@
|
|
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
|
|
console uart instead of the 'mini uart' a quirky 8250 alike which
lacks flow control and break detection. By default the pl011 is used
for bluetooth. The pins the console is on do not change.
When com(4) takes over the console with the mini uart on rpi3 I see
noise before output resumes and can't interact with the console after it
has booted. With pluart(4) as console everything is fine.
|
|
multiple of bs use conv=sync to zero pad the final record. Avoids
"vnd0: sloppy write from proc" messages when building arm releases.
tested by deraadt@
|
|
U-Boot has been built with CONFIG_OF_BOARD for a year now
ok patrick@
|
|
more empty space before the MS-DOS and OpenBSD partitions.
Also make sure we don't overwrite the firmware with the Pine64 on anything
but the Pine64 and Pine64+.
With help from jsg@
ok deraadt@, jsg@, patrick@
|
|
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..
|
|
moving progress bar during auto upgrade/install and a clean log
afterwards. ok deraadt@
|
|
chunks in a specified order, using a few variables, performing bsd.rd
to bsd.gz conversion as similar as possible)
|
|
|
|
|
|
Eliminate many more differences. When it makes sense, build bsd.rd
and miniroot/ramdisk.fs and cd.iso in the same directory. More steps
coming after this..
|
|
|
|
the sme.
|
|
|
|
|
|
having two mysterious names, let's settle on one.
|
|
|