| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
o add 802.11 alias support
o suppress display of the default "mode autoselect" when showing the "phy mode"
|
|
|
|
|
|
|
| |
Protocol (IP) is 64 [RFC791, RFC1122].
Prodded by: Igor Kucherenko <kivvy@sunbay.com>
Obtained from: http://www.iana.org/assignments/ip-parameters
|
|
|
|
| |
has been unused and unmaintained for a long time).
|
|
|
|
| |
was already correct).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1.2.3.4/24{5,6,7,10-20,60-90}
for set of ip addresses.
Previously you needed to specify every address in the range, which
was unconvenient and lead to very long lines.
Internally the set is still stored in the same way, just the
input and output routines are modified.
Manpage update still missing.
Perhaps a similar preprocessing step would be useful for port ranges.
MFC after: 3 days
|
|
|
|
|
|
| |
PR: docs/53625
Submitted by: Kostyuk Oleg <cub@cub.org.ua>
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
"ipid" options. This feature has been requested by several users.
On passing, fix some minor bugs in the parser. This change is fully
backward compatible so if you have an old /sbin/ipfw and a new
kernel you are not in trouble (but you need to update /sbin/ipfw
if you want to use the new features).
Document the changes in the manpage.
Now you can write things like
ipfw add skipto 1000 iplen 0-500
which some people were asking to give preferential treatment to
short packets.
The 'MFC after' is just set as a reminder, because I still need
to merge the Alpha/Sparc64 fixes for ipfw2 (which unfortunately
change the size of certain kernel structures; not that it matters
a lot since ipfw2 is entirely optional and not the default...)
PR: bin/48015
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
with a new implementation that has a mostly reentrant "addchar"
routine, supports multiple message buffers in the kernel, and hides
the implementation details from callers.
The new code uses a kind of sequence number to represend the current
read and write positions in the buffer. This approach (suggested
mainly by bde) permits the read and write pointers to be maintained
separately, which reduces the number of atomic operations that are
required. The "mostly reentrant" above refers to the way that while
it is now always safe to have any number of concurrent writers,
readers could see the message buffer after a writer has advanced
the pointers but before it has witten the new character.
Discussed on: freebsd-arch
|
| |
|
|
|
|
| |
the build almost a year ago.
|
| |
|
| |
|
|
|
|
|
|
| |
PR: bin/51750
Submitted by: Vasil Dimov <vd@datamax.bg>
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(1) Reject zero-length strings for CTLTYPE_INT, _UINT, _LONG,
_ULONG. Do not silently convert to 0.
(2) When converting CTLTYPE_INT, _UINT, _LONG, and _ULONG, check the
end pointer generated by strtol() and strtoul() rather than
discarding it. Reject the string if either none of the string
was useful for conversion to an integer, or if there was
trailing garbage.
I.e., we will not allow you to set a numeric sysctl to a value unless
we can completely convert the string argument to a numeric value.
I tripped over this when I put the following in /etc/sysctl.conf:
kern.maxfiles="4000"
Ouch.
|
|
|
|
|
|
|
|
| |
and libdevstat, since the new way of doing things is to just list
maintainership in src/MAINTAINERS.
Also, remove duplicate entries in src/MAINTAINERS for those utilities. I
already had entries for them.
|
|
|
|
|
|
|
| |
options are not required.
Suggested by: Vaclav Petricek
MFC after: 2 weeks
|
|
|
|
|
|
| |
recent changes broke it altogether.
Prompted by: phk
|
| |
|
| |
|
|
|
|
|
|
| |
number X, rather than mdX, making it easier to script tests that
use md devices but don't want to make assumptions about any existing
md use (such as in diskless environments).
|
| |
|
|
|
|
|
| |
You need your kernel and ccdconfig(8) to be in sync, particularly if your
source tree is on a ccd device.
|
|
|
|
| |
with any quoting, but that should be OK for re-input, regardless.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
If we don't have a default label location for the compiled architecture,
insist that a -m <architecture> option is specified.
|
| |
|
| |
|
|
|
|
| |
byte sector devices.
|
| |
|
|
|
|
|
|
|
|
| |
sparc64.
PR: alpha/50658
Submitted by: rizzo
Tested on: alpha
|
|
|
|
|
|
|
| |
Change the list interface to simplify things.
Remove old list ioctls which bogusly exported the softc to userland.
Move the softc and associated structures from the public header to
the source file.
|
|
|
|
| |
Link against libgeom.
|
| |
|
| |
|
|
|
|
|
|
| |
when the data for it is not available.
Founded by: ping -s0 localhost; press ^T
|
|
|
|
|
|
|
|
| |
hinge on the "verb" parameter which the class gets to interpret as
it sees fit.
Move the entire request into the kernel and move changed parameters
back when done.
|
|
|
|
| |
Remove ktrace which leaked out of test-setup.
|
| |
|
|
|
|
| |
Approved by: re (blanket)
|
|
|
|
|
|
|
|
| |
disklabel. I just got burnt again by having an old disklabel binary
kicking around.
Discussed with: phk
Approved by: re (safe amd64 stuff)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
with UFS1, the UFS1 superblocks were not deleted. This allowed any
RELENG_4 (or other non-UFS2-aware) fsck to think it knew how to "fix"
the file system, resulting in severe data scrambling.
This patch is a more advanced version than the one originally submitted.
Lukas improved it based on feedback from Kirk, and testing by me. It
blanks all UFS1 superblocks (if any) during a UFS2 newfs, thereby causing
fsck's that are not UFS2 aware to generate the "SEARCH FOR ALTERNATE
SUPER-BLOCK FAILED" message, and exit without damaging the fs.
PR: bin/51619
Submitted by: Lukas Ertl <l.ertl@univie.ac.at>
Reviewed by: kirk
Approved by: re (scottl)
|
| |
|
| |
|
|
|
|
| |
Approved by: re (blanket)
|
|
|
|
| |
Approved by: re (blanket)
|
|
|
|
| |
Approved by: re (blanket)
|