| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
o WARNS should be WARNS?= (broke in rev 1.21).
o Includes should be sorted.
o Move "mntopt.h" out of the standard includes section.
o Rewrite usage() to match the manual page and make it < 80 characters.
o Remove extra .El call on line 187. It is unused and causes mdoc(7) warnings.
Discussed with: bde
|
| |
|
| |
|
|
|
|
| |
They were erroneously removed in revision 1.27.
|
|
|
|
|
| |
instead of "rdonly". "rdonly" works for mount(8) and mount_std(8) but
not from /etc/fstab, whereas "ro" works for all mount_*(8) commands.
|
|
|
|
| |
Obtained from: KAME
|
|
|
|
| |
Suggested by: njl
|
|
|
|
| |
user has attempted to write to a read only, tunable value.
|
|
|
|
|
|
|
|
|
|
| |
original intention of the less restrictive permissions was to allow
users to move or delete recovered files that they own. However, it
is better to not create world-writable directories by default; the
administrator can always pre-create lost+found if different permissions
are desired.
Reviewed by: mckusick
|
|
|
|
| |
but a 'c' partition.
|
| |
|
|
|
|
|
|
|
|
| |
- rename variable
- use strlcpy
- const'fy
Obtained from: KAME
|
| |
|
|
|
|
|
|
|
|
| |
- use size_t as return type of schedlen(), as there's no error
check needed.
- clear key schedule buffer before freeing.
Obtained from: KAME
|
|
|
|
|
|
| |
- correct SADB_X_AALG_RIPEMD160HMAC to 8
Obtained from: KAME
|
|
|
|
|
|
| |
- pass size arg to ah->result (avoid assuming result buffer size)
Obtained from: KAME
|
|
|
|
|
| |
PR: 57462
Submitted by: Ryuichiro Imura <imura@ryu16.org>
|
|
|
|
| |
Obtained from: KAME
|
|
|
|
|
|
|
| |
example.
PR: docs/51897
Submitted by: Kevin Oberman <oberman@es.net>
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the stack to the heap to work around a problem on ia64. Now, roughly
16 months and two compiler updates later, it isn't an issue anymore
in the sense that putting a 1M buffer on the stack just works and we
don't actually need to work around anything anymore.
However, since there's no advantage or need to put the buffer on the
stack (again), this change merely removes the XXX comment describing
that there's an explicit reason for the heap allocation. Hence, this
change is a functional no-op.
PR: ia64/38677
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
filesystem that is checked in background. Create the snapshot in this
directory rather than in the root. There are two benefits:
1) For terabyte-sized filesystems, the snapshot may require many
minutes to build. Although the filesystem will not be suspended
during most of the snapshot build, the snapshot file itself is
locked during the entire snapshot build period. Thus, if it is
accessed during the period that it is being built, the process
trying to access it will block holding its containing directory
locked. If the snapshot is in the root, the root will lock and
the system will come to a halt until the snapshot finishes. By
putting the snapshot in a subdirectory, it is out of the likely
path of any process traversing through the root and hence much
less likely to cause a lock race to the root.
2) The dump program is usually run by a non-root user running with
operator group privilege. Such a user is typically not permitted
to create files in the root of a filesystem. By having a directory
in group operator with group write access available, such a user
will be able to create a snapshot there. Having the dump program
create its snapshot in a subdirectory below the root will benefit
from point (1) as well.
Sponsored by: DARPA & NAI Labs.
|
| |
|
|
|
|
| |
Submitted by: mr
|
| |
|
|
|
|
|
|
|
|
|
| |
and the logic for setting them according to the partition size.
Instead, unspecified filesystem values are left at 0 so that newfs
will use its own defaults. It just caused confusion to have the
defaults duplicated in two different places.
Reviewed by: phk
|
|
|
|
|
|
| |
data structures that have an embedded struct route
Sponsored by: FreeBSD Foundation
|
| |
|
|
|
|
|
|
|
|
| |
- CD9660_ICONV, NTFS_ICONV and MSDOSFS_ICONV kernel options
(with corresponding modules).
- kiconv(3) for loadable charset conversion tables support.
Submitted by: Ryuichiro Imura <imura@ryu16.org>
|
|
|
|
| |
Reviewed by: ru
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Skinny is the protocol used by Cisco IP phones to talk to Cisco Call
Managers. With this code, one can use a Cisco IP phone behind a FreeBSD
NAT gateway.
Currently, having the Call Manager behind the NAT gateway is not supported.
More information on enabling Skinny support in libalias, natd, and ppp
can be found in those applications' manpages.
PR: 55843
Reviewed by: ru
Approved by: ru
MFC after: 30 days
|
|
|
|
|
|
|
| |
variable arguments. version 1.26 incorrectly truncated the message if
the buffer was too long.
Requested by: bde
|
| |
|
|
|
|
| |
Reviewed by: peter
|
|
|
|
|
| |
o use IEEE80211_KEYBUF_SIZE instead of magic numbers
o distinguish between 40-, 104-, and 128-bit WEP keys when printing status
|
| |
|
| |
|
| |
|
|
|
|
| |
Reported by: naddy
|
|
|
|
|
|
| |
PR: 56021
Submitted by: Glen Gibb <grg@ridley.unimelb.edu.au>
MFC after: 1 month
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
of do_cmd() broke things, because this function assumes that a socklen_t
is large enough to hold a pointer.
A real solution to this problem would be a rewrite of do_cmd() to
treat the optlen parameter consistently and not use it to carry
a pointer or integer dependent on the context.
|
|
|
|
|
|
|
|
| |
The immediate purpose for this option is to use it in rc.d so that we
can make savecore behavior conditional.
Tremendous assistance with ideas and sanity checking provided by tjr
and b@etek.chalmers.se.
|
|
|
|
|
|
|
|
| |
PR: bin/56298
Submitted by: Kang Liu <liukang@bjpu.edu.cn>
MFC after: 2 weeks
# We need a regression test suit for ipfw(2)/ipfw(8) badly.
|
|
|
|
| |
English lessons provided by: jhb
|
| |
|