| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
consumers. Teach STRIPE, CONCAT and NOP classes about this improvement.
|
| |
|
| |
|
|
|
|
| |
possibly unsigned).
|
|
|
|
|
|
| |
that provide control over the respective capabilities
of an interface, reception of extended frames and hardware
VLAN multiplexor.
|
|
|
|
| |
Obtained from: KAME
|
| |
|
|
|
|
|
| |
PR: bin/14697
Submitted by: Matthew <kienow@infinet.com>
|
|
|
|
|
|
|
| |
securelevel = 3.
PR: docs/69417
Submitted by: Janos Mohacsi (mohacsi(at)niif(dot)hu)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
RTF_BLACKHOLE as well.
To quote the submitter:
The uRPF loose-check implementation by the industry vendors, at least on Cisco
and possibly Juniper, will fail the check if the route of the source address
is pointed to Null0 (on Juniper, discard or reject route). What this means is,
even if uRPF Loose-check finds the route, if the route is pointed to blackhole,
uRPF loose-check must fail. This allows people to utilize uRPF loose-check mode
as a pseudo-packet-firewall without using any manual filtering configuration --
one can simply inject a IGP or BGP prefix with next-hop set to a static route
that directs to null/discard facility. This results in uRPF Loose-check failing
on all packets with source addresses that are within the range of the nullroute.
Submitted by: James Jun <james@towardex.com>
|
|
|
|
| |
point to write 'Media' in the table header for the -atm option.
|
|
|
|
| |
not 'atmconfig natm list'.
|
| |
|
|
|
|
| |
each help file must start with a level 0 topic.
|
|
|
|
|
| |
Also remove the current directory from the default help file path
and add an appropriate directory in /usr/local instead.
|
| |
|
|
|
|
|
| |
-o offset - specifies where to start on the original provider
-s size - specifies size of the transparent provider
|
|
|
|
|
|
| |
where boot.config needs to reside. Also change /kernel
to /boot/loader, as that is the apparent default now. This
man page probably requires more updates.
|
|
|
|
| |
Obtained from: DragonFly
|
|
|
|
| |
to dump metadata from given components.
|
|
|
|
|
| |
Obtained from: NetBSD via DragonFly BSD
MFC after: 3 days
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add a MOD_QUIESCE event for modules. This should return error (EBUSY)
of the module is in use.
MOD_UNLOAD should now only fail if it is impossible (as opposed to
inconvenient) to unload the module. Valid reasons are memory references
into the module which cannot be tracked down and eliminated.
When kldunloading, we abandon if MOD_UNLOAD fails, and if -force is
not given, MOD_QUIESCE failing will also prevent the unload.
For backwards compatibility, we treat EOPNOTSUPP from MOD_QUIESCE as
success.
Document that modules should return EOPNOTSUPP for unknown events.
|
|
|
|
| |
Based on: simon's patch
|
|
|
|
| |
Reviewed by: simon
|
|
|
|
| |
Submitted by: simon
|
|
|
|
| |
default.
|
|
|
|
| |
Glanced at by: jhb
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Use braces instead.
|
|
|
|
|
|
| |
less dangerous.
- Update manual pages and extend examples.
- Bump versions.
|
| |
|
|
|
|
| |
This makes it possible to do load-sharing on two xDSL lines etc.
|
| |
|
|
|
|
| |
Submitted by: David Magda <dmagda@ee.ryerson.ca>
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This class is used for detecting volume labels on file systems:
UFS, MSDOSFS (FAT12, FAT16, FAT32) and ISO9660.
It also provide native labelization (there is no need for file system).
g_label_ufs.c is based on geom_vol_ffs from Gordon Tetlow.
g_label_msdos.c and g_label_iso9660.c are probably hacks, I just found
where volume labels are stored and I use those offsets here,
but with this class it should be easy to do it as it should be done by
someone who know how.
Implementing volume labels detection for other file systems also should
be trivial.
New providers are created in those directories:
/dev/ufs/ (UFS1, UFS2)
/dev/msdosfs/ (FAT12, FAT16, FAT32)
/dev/iso9660/ (ISO9660)
/dev/label/ (native labels, configured with glabel(8))
Manual page cleanups and some comments inside were submitted by
Simon L. Nielsen, who was, as always, very helpful. Thanks!
|
| |
|
| |
|
| |
|
|
|
|
| |
in over the socket.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
manpage:
The comparison function must return an integer less than, equal to, or
greater than zero if the first argument is considered to be respectively
less than, equal to, or greater than the second.
Therefore, simply returning "arg1 > arg2" is incorrect. Actually it works
but for the number of items to be sorted less than 7 due to special case
handling in qsort(3);
o add missing '\n' to one of usage() calls.
Approved by: phk
|
|
|
|
|
| |
Noticed by: Joshua Goodall <joshua@roughtrade.net>
Approved by: ru
|
| |
|
|
|
|
|
|
|
| |
normal status messages. Previously a large number of these new
messages could be spewed out towards the end of a dump.
Reviewed by: imp
|
| |
|