| Age | Commit message (Collapse) | Author |
|---|
|
|
|
"The BeagleV-Starlight prototype will not be going into mass production"
https://forum.beagleboard.org/t/the-future-of-beaglev-community/30463
|
|
|
|
|
|
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
|
|
|
|
|
|
|
|
resolvd(8), slaacd(8) and dhcpleased(8) are different from other daemons
in that there must only be a single instance.
resolvd already does this, adjust slaacd and dhcpleased accordingly while
moving the lockfile paths under /dev/ such that they work early on boot and
don't run into races should /var be (un)mounted between daemon starts.
Locking is especially required in the installer where all three daemons are
started every time the "(I)nstall, (U)pgrade, (A)utoinstall or (S)hell? "
prompt is entered, i.e. restarting installation or dropping into a shell
and back into the prompt again would start multiple instances.
To avoid expected lockfile error messages in between installer prompts,
discard standard error when starting the autoconf daemons; none of them
has other potential failure cases in installer mode before daemon(3)izing.
Input sthen deraadt
OK deraadt
|
|
ok krw@, deraadt@
|
|
|
|
dhcpleased(8)'s lease files are much simpler than dhclient.leases(5):
- exactly one lease per file (not many)
- only option lines (not statement, declaration, etc.)
- every option/value is separated by a single ": " (no optional leading
"option ")
- values are not quoted or escaped (like dhclient does)
lease_value() is hard to read, mostly because it strips optional double
quotes around option values as was required with dhclient.
dhclient VIS_ALL's values if they contain backticks, backslashes and
other characters, otherwise it VIS_SAFE's (and optionally quotes them).
dhcpleased VIS_SAFE's all value strings equally.
All install.sub users of lease_value() quote its output so they should
be safe without any special unescaping as previously done.
OK florian
|
|
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
|
|
|
|
More cleanup is needed from a real ksh hacker, but looks already
pretty good to kn.
OK deraadt
|
|
resolv.conf.shadow and start dhcpleased/resolvd.
OK deraadt
|
|
OK deraadt who also helped making some space.
|
|
OK deraadt
|
|
|
|
away)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
while here
|
|
Empty statements accepted by ksh(1) pointed out by millert@, use of this
non-standard grammar in the installer pointed out by halex@.
ok halex@ millert@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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@
|
|
initial sizes were from arm64
|
|
initial sizes were from arm64
|
|
remove -DSEEALSO, as suggested by millert
ok millert
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
ok jsg@(with suggested improvements) mlarkin@
|
|
|
|
|
