| Age | Commit message (Collapse) | Author |
|
Thanks for Simon Burge for plic(4).
|
|
On ARM ports, the EFI boot loader handles a boot.cfg file if it
exists, but one is not installed by default. In contrast, both the
i386 and amd64 ports do install boot.cfg by default. Bring these
ports into agreement by installing boot.cfg on ARM ports with EFI boot
loaders.
|
|
read from disk is trusted. Revert to use drvctl again.
|
|
Fetch geometry from disklabel to be consistent.
Use disktab format instead of the normal human-readable output for parsing
the disklabel.
Avoid overflows in size computation.
|
|
|
|
|
|
|
|
another copyright claim line. again. (i did this in 2008 and then
did not update all of my personal templates.)
|
|
|
|
This set is only installed on amd64,i386,evbarm.
This set is installed on minimal installs and on install media, in
case someone needs it for basic driver functionality.
Comments:
Switched to a single MK tunable for it - that is probably unneeded.
An upcoming DRM update will include even fatter firmware, and we'd
like to minimize the impact of it.
|
|
This makes no difference in the randomness of the pool, but it improves
on the estimation (if any) of how many random bits were obtained.
Also make the ftp -q time out a bit longer since I got some time outs.
|
|
I found that in the cloud I tried, by the time this script runs, there
is no default route in effect yet. That takes some 5 to 10 seconds
longer. So I added a retry loop, and to make that easier, changed the
order of queries. To make sure it doesn't wait ~forever for a
non-existent service I added the -q 1 option to ftp invocations.
I also added OpenStack-specific metadata which contains a different
random_seed of 512 bytes every time it is requested. See
https://github.com/openstack/nova/blob/master/nova/api/metadata/base.py#L355
It may not be trusted data but only in the strictest sense of the word.
The data can only be observed by people with access to the cloud's
overlay network for the particular VM.
|
|
|
|
and install the ssh key in that user's home directory instead.
|
|
Add -w to dhcpcd_flags when running on EC2, since we need to wait for the
network to come up before contacting the metadata service.
|
|
|
|
For mkimage:
- Update "size" if auto-calculated.
- Use "dd bs=1" instead of non-portable "head -c".
- Some style nits.
For MD make_label() functions:
- Stop using "newsize" as image size in MB, use "size" instead.
|
|
Otherwise, there may not be enough space after the ffs partition for a
gpt, leading to very confusing results.
|
|
|
|
|
|
|
|
require the bootloader to be installed on SD cards at LBA1 which makes
them incompatible with GPT images.
|
|
|
|
Amlogic S805 based boards) needs to be installed to sector 1, which
conflicts with the GPT header.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
part of a separate set, "dtb.tgz", and only built when MKDTB=yes. This
defaults to yes for earmv[67]* and aarch64, and no everywhere else.
|
|
an alternate cmdline txt file (cmdline-pi4.txt) on these boards.
|
|
|
|
|
|
|
|
commit 0c01dbefba45a08c47f8538d5a071a0fba6b7e83
Author: popcornmix <popcornmix@gmail.com>
Date: Wed Dec 11 15:30:08 2019 +0000
and include firmware for RPI4
Firmware has bee updated to support mainline linux kernels as described in
https://github.com/raspberrypi/linux/issues/3237
|
|
|
|
|
|
|
|
|
|
when crating a msdos file system.
|
|
Mkimage (eroneously) creates a FAT16 partition (despite the configuration
asking for FAT32), and that has a root directory size limit.
Idea from Jared.
|
|
|
|
|
|
|
|
This is meant to make updates safer: if something goes wrong with updating
base, we still have the old, standalone /rescue to recover from.
|
|
Note that we do not currently build EFI bootloader for earmv7hf-eb,
as it requires little-endian version of toolchain.
|
|
|
|
- clean up variable usage
- be explicit that $ssh_userkeys is global
- don't assig id output to a variable not used
|