| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
as we have active CPUs and bind each thread to its own CPU.
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
deleted a while ago.
PR: docs/85142
Submitted by: Jeremy Chadwick <freebsd@jdc.parodius.com>
MFC after: 3 days
|
|
|
|
|
|
| |
when there is only one key set.
MFC after: 3 days
|
|
|
|
|
|
| |
I want to use it so more.
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
/boot.config or on the "boot:" prompt line via a "-S<speed>" flag,
e.g. "-h -S19200". This adds about 50 bytes to the size of boot2
and required a few other small changes to limit the size impact.
This changes only affects boot2; there are further loader changes
to follow.
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
|
|
|
| |
example on how to obtain information on devices on an ata channel.
PR: 84676
Submitted by: Kevin Oberman <oberman@es.net>
Jeremie Le Hen <jeremie@le-hen.org>
MFC after: 3 days
|
|
|
|
|
|
|
|
|
| |
ping ICMP payload of packets being sent is increased with given step.
Sweeping pings are useful for testing problematic channels, MTU
issues or traffic policing functions in networks.
PR: bin/82625
Submitted by: Chris Hellberg <chellberg juniper.net> (with some cleanups)
|
|
|
|
|
|
|
|
|
|
|
|
| |
to take into account the new default of starting the first partition
after the boot blocks instead of at sector 0. If you used automatic
sizing when the first partition did not start at 0, you would get
an error that the automatically sized partition extended beyond the
end of the disk.
Note that there are probably still many more complex cases where
automatic sizing and placement will not work (e.g. non-contiguous
or out of order partitions).
|
|
|
|
|
|
|
|
|
|
| |
ignore "no such file" errors only, which I wanted to do.
Because of this I ignored all other errors on dlopen(3) failure as well,
which isn't good.
Fix this situation by calling access(2) on library file first and ignore
only ENOENT error. This allows to report all the rest of dlopen(3) errors.
MFC after: 3 days
|
|
|
|
|
| |
made it impossible to use newfs (and mdmfs) when /etc/group is
missing and /etc is read-only.
|
|
|
|
|
|
|
|
|
|
| |
metadata is equal to -1. if we then wanted to attach provider (or change
keys) and forget about '-p' flag it failed on assertion (quite ok, without
assertion it could call PKCS#5v2 with 4294967295 iterations).
Instead of failing on assertion, remind about '-p' flag.
MFC after: 3 days
|
|
|
|
|
|
| |
Noticed by: Michal Mertl
Approved by: mlaier (mentor)
MFC after: 3 days
|
|
|
|
|
| |
Submitted by: Michal Mertl (original version)
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Correct handling of IPv6 Extension Headers.
* Add unreach6 code.
* Add logging for IPv6.
Submitted by: sysctl handling derived from patch from ume needed for ip6fw
Obtained from: is_icmp6_query and send_reject6 derived from similar
functions of netinet6,ip6fw
Reviewed by: ume, gnn; silence on ipfw@
Test setup provided by: CK Software GmbH
MFC after: 6 days
|
|
|
|
| |
MFC after: 2 days
|
|
|
|
|
|
| |
Submitted by: Stanislav Sedov <stas@310.ru>
PR: kern/84638
MFC after: 1 week
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Reported by: Alexander Polakov
|
|
|
|
|
|
|
| |
code but not documented (e.g. wme, mac acl) and correct some
information, etc.
Reviewed by: brueffer
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
Based on:
PR: docs/84200
Submitted by: Gary W. Swearingen <garys at opusnet dot com>
MFC after: 1 week
|
| |
|
| |
|
|
|
|
| |
Approved by: re (kensmith)
|
|
|
|
| |
MFC after: 1 day
|
| |
|
|
|
|
|
|
| |
is properly aligned when we move to the next packet.
Obtained from: ISC dhclient via krw at OpenBSD
|
|
|
|
|
|
| |
PR: docs/84198
Submitted by: Gary W. Swearingen
MFC after: 3 days
|
|
|
|
|
|
|
| |
not allowed in domain names. RFC 2132 does not list valid or invalid
characters and the ISC client accepts anything here.
Reported by: ps
|
| |
|
|
|
|
|
|
|
| |
- Don't link libmd, it is not needed.
- Connect manual page to the build.
MFC after: 1 week
|
|
|
|
|
| |
I need to find out first what is the cause of sha2.c compilation problem
on alpha.
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
For features list and usage see manual page: geli(8).
Sponsored by: Wheel Sp. z o.o.
http://www.wheel.pl
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
capture. Zero length captures caused an infinte loop and short captures
probably caused memory corruption and a crash.
Reported by: many
MFC After: 3 days
|
|
|
|
| |
We may now handle route updates better.
|
|
|
|
|
|
| |
o accept rtsthreshold - (or any) as a shorthand for rtsthreshold 2346
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
accept NUL-terminated strings as required by RFC 2132.
This solution is not perfect as it removes the ability to send
NUL-terminated host-name options which may be required by some broken
servers. Given the current lack of an existance proof of such servers
and the fact that servers that send NUL-terminated domain names do
exist, this seems like an acceptable compromise. A discussion of these
issues can be found at:
http://marc.theaimsgroup.com/?l=dhcp-client&m=96837107208382&w=2
PR: bin/83468
Reported by: Sean Winn <sean at gothic dot net dot au>
MFC-after: 3 days
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
|
| |
Previously, interactive commands specifying a non-existent file or
directory used to display an "out of memory error".
MFC after: 2 weeks
|
|
|
|
| |
Reminded by: ru
|
|
|
|
|
| |
Reviewed by: ru
MFC after: 3 days
|
|
|
|
| |
- Attempt gctl verb "write MBR" when updating.
|