| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
generic part, ykbec(4) provides the device specific parts. Other
battery/power status drivers can easily hook to adb(4). With help
from miod@; ok matthieu@ miod@ jasper@
|
|
anyway, it's not worth fixing. Bump version number.
ok deraadt@
|
|
It misled users to think they could use it, and it didn't really
provide any useful information.
Instead, note that some sysctl variables depend on options(4).
OK jmc@
|
|
|
|
|
|
when computing multicast hash.
From Brad via FreeBSD
|
|
Pointed out by obsd at happyjack.org, fix based on a diff from kili@.
ok deraadt
|
|
Reported by and fix tested by peters at schwertfische dot de.
|
|
what to tell the user. Silences cdio and cdrecord while probing
media.
ok dlg@ marco@ deraadt@
|
|
a good idea
|
|
|
|
buffer cache first, so that all sorts of gibble doesn't end up on the disk.
ok kettenis (for the sparc/sparc64 ones, at least)
|
|
|
|
|
|
|
|
discussed with and ok jakemsr@ jmc@
|
|
just not there.
ok jakemsr@ drahn@
|
|
|
|
OpenSSH certificate key types are not X.509 certificates, but a much
simpler format that encodes a public key, identity information and
some validity constraints and signs it with a CA key. CA keys are
regular SSH keys. This certificate style avoids the attack surface
of X.509 certificates and is very easy to deploy.
Certified host keys allow automatic acceptance of new host keys
when a CA certificate is marked as trusted in ~/.ssh/known_hosts.
see VERIFYING HOST KEYS in ssh(1) for details.
Certified user keys allow authentication of users when the signing
CA key is marked as trusted in authorized_keys. See "AUTHORIZED_KEYS
FILE FORMAT" in sshd(8) for details.
Certificates are minted using ssh-keygen(1), documentation is in
the "CERTIFICATES" section of that manpage.
Documentation on the format of certificates is in the file
PROTOCOL.certkeys
feedback and ok markus@
|
|
Why this code, which must be executed, is not failing on disk is an utter
mystery. More investigation needed.
|
|
|
|
|
|
right flags when protecting the IPv6 loopback addr (instead of reassigning
the IPv4 ones) and install the IPv4 loopback blocker as 127/8 and not as
127.0.0.1/8. First two found by Hiroki Sato hrs (at) allbsd org and I found
the 127/8 issue all by myself.
|
|
was reported by nicm@ which spent a couple hours with me trying to
understand what was causing the bug, and helping me write and test fix.
|
|
allowed to match on old gdium artwork, as newer artwork have nothing
connected to the usb pins, and this causes the empty bus probe to stall the
boot a few seconds.
|
|
for consistency with other manual pages.
ok jakemsr@
|
|
case letters for both `environmental monitoring subsystem' and
`analog to digital converter', as these are generic terms and not
trade marks; s/analogue/analog/ on `analogue to digital converter'.
tweak on iic(4) reminded by jmc@
ok jmc@
|
|
This commit corresponds to what jmc@ did in share/tmac/mdoc/doc-common
and share/man/man7/mdoc.samples.7 on January 24.
|
|
used as a label, not "the first line following", so allow (some kinds of)
intervening macros - some people actually put macros in between.
On the other hand, when there is no text line before the next block macro,
that is, when the .TP block ends without any text line, then something *is*
broken, so still error out in that case.
|
|
The trick is to not switch from the .It header to the body at EOL, but,
in case an explicit block macro follows, at the end of the block.
|
|
|
|
ok deraadt@
|
|
ls_id. This is needed since sometimes the ls_id is not known and we need
to walk part of the tree.
|
|
ok jmc deraadt
|
|
|
|
ok claudio@
|
|
capitilization for names.
from brad, thanks!
|
|
from Alexandr Shadchin <alexandr.shadchin at gmail.com>, thanks!
|
|
from Alexandr Shadchin <alexandr.shadchin at gmail.com>, thanks!
|
|
|
|
with the prefix.
ok claudio@
|
|
changed from 16 bytes to 2 bytes.
no binary change
|
|
|
|
from Windows driver via http://www.wikidrivers.com/wiki/Ralink_RT2870
|
