| Commit message (Collapse) | Author | Files | Lines |
|
millert@
|
|
|
|
|
|
OK bcook@ jung@
|
|
ok mpi@
|
|
macppc.
|
|
let someone else figure it out.
ok mpi@
|
|
the daemon is actually running (instead of only when using rc_bg).
This *may* trigger the following side effect: if a daemon starts then stops
right away (because of a config parsing issue for e.g.), then it will slow down
the boot process because rc will wait a bit before considering the start action
failed. But at least it will allow us to detect those daemons and fix them or
their rc.d(8) script.
At least as far as I can tell, all base daemons should cope with it just fine.
ok sthen@ robert@ on an earlier diff
|
|
and actually not a "logging" function. No functional change.
|
|
tell you that the daemon succesfully started; prevent this by running a config
check first.
Note that we only do this for those particular daemons, not all that support a
config test mode.
ok benno@ phessler@
|
|
Based on linux commit 5613beb46d54da6ef7f1c4589e9f2e60eeb10721 found
by jsg@.
KMS is now usable on Uninorth machines but X11 output is still
corrupted.
ok kettenis@
|
|
ok kettenis@
|
|
support for G4 machines.
This allows us to enable agp(4) again for G5 machines.
ok kettenis@
|
|
This is needed in order to fully unlock ARP processing with carp(4)
interfaces as found the hardway by sthen@.
ok sthen@, dlg@
|
|
ok sthen@ robert@
|
|
Let -f recognize non-ASCII blank characters
and let -s count characters rather than bytes.
OK zhuk@ bentley@
|
|
|
|
|
|
xen_intr_establish was using a variable that hasn't got its value
updated in the supplementary check for event channel port unmasking.
xen_intr_disestablish didn't save and correctly check the return value
of xen_lookup_intsrc call and was incorrectly indexing into the pending
event channel port bitmap.
|
|
|
|
|
|
ok tb@
|
|
exit>".
|
|
sixteen years.
ok millert@, tb@, sthen@
|
|
introduced in the previous step, and use atomic instructions to make the
tx completion path mpsafe as well.
ok claudio@, mpi@
|
|
regression observed on avahi.
ok benno@
|
|
|
|
Tested by Cedric on macppc/i386, and by myself on macppc.
|
|
introduced in the previous step, and use atomic instructions to make the
tx completion path mpsafe as well.
ok claudio@, mpi@
|
|
|
|
|
|
|
|
ok visa@
|
|
Help with testing and ok kettenis@
|
|
partition-table of a certain type and optionally if it has a partition
of a certain type.
Use disk_has() in the install.md script to replace all the various
"fdisk <disk> | grep <pattern>" commands greatly simplifying things.
positive feedback from sthen@
"time to get it really tested" deraadt@
OK krw@
|
|
wasn't used
|
|
ok mpi@
|
|
|
|
|
|
NetBSD also turn off this piece of code.
ok tb@
|
|
csqrt(conj(z)) == conj(csqrt(z))
Before
csqrt(-4.0 + -0.0i) = 0.0 + 2.0j
but should be
csqrt(-4.0 + -0.0i) = 0.0 - 2.0j
ok tb@, also discussed with daniel@
|
|
Ensure that arc4random_uniform() doesn't loop by redefining
ND6_MAX_DESYNC_FACTOR to be 512, the largest power of two smaller
than the RFC-specified 600 seconds. Suggested by florian@ and deraadt@
ok florian@, sthen@ in this form, arc4random change ok djm@, tedu@
|
|
This is slightly less robust, but RAND_MAX must be one below a power
of two in both variants anyway.
Based on a suggestion by Matthew Martin.
ok tedu@
|
|
prodded by tim@, ok mpi@
|
|
page protection bits.
Go ahead, mlarkin@
|
|
found by + ok jsg@
|
|
fail. This codepath doesn't exist upstream, so it's fine to change.
ok jsg@
|
|
towards other YES|NO options and drop the error warning.
with and ok tim@, ok rpe@ on an earlier diff
|
|
|
|
the CPU that handles most hardware interrupts but we don't account for that
in any way in the scheduler. So processes (and kernel threads) that are
unlucky enough to end up on this CPU will get less CPU cycles than those
running on other CPUs. This is especially true for the softnet taskq.
There network interrupts will prevent the softnet taskq from running. This
means that the more packets we receive, the less packets we can actually
process and/or forward. This is why "unlocking" network drivers actually
decreases the forwarding performance. This diff restores most of the lost
performance by making it less likely that the softnet taskq ends up on the
same CPU that handles network interrupts.
Tested by Hrvoje Popovski
ok mpi@, deraadt@
|