| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Note: DOS names still not work and require similar changes
|
|
|
|
|
|
| |
with SIG_ERR to detect the error case.
Suggested by: bde.
|
|
|
|
|
| |
Submitted by: Dmitrij Tejblum <dima@tejblum.dnttm.rssi.ru>
Obtained from: NetBSD
|
|
|
|
| |
filesystem types.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
offset is non-zero:
- Do not match fragmented packets if the rule specifies a port or
TCP flags
- Match fragmented packets if the rule does not specify a port and
TCP flags
Since ipfw cannot examine port numbers or TCP flags for such packets,
it is now illegal to specify the 'frag' option with either ports or
tcpflags. Both kernel and ipfw userland utility will reject rules
containing a combination of these options.
BEWARE: packets that were previously passed may now be rejected, and
vice versa.
Reviewed by: Archie Cobbs <archie@whistle.com>
|
| |
|
| |
|
| |
|
|
|
|
|
| |
was a directory, so the error message for attempting to unmount
an unmounted-on directory was more broken than before.
|
|
|
|
|
| |
necessary. This fixes warnings about missing forward declarations
for structs in kernel-only prototypes.
|
|
|
|
|
| |
PR: 5614
Submitted by: Dag-Erling Coidan Smorgrav <dag-erli@ifi.uio.no>
|
|
|
|
| |
Submitted by: Bruce Evans
|
| |
|
| |
|
|
|
|
| |
the private one.
|
|
|
|
|
| |
PR: 5447
Submitted by: Craig Leres <leres@ee.lbl.gov>
|
|
|
|
| |
comparing < 0.
|
|
|
|
| |
should be ssize_t too.
|
|
|
|
|
| |
already looked up vfsconf struct for nfs instead of MOUNT_NFS.
Removed related FreeBSD ifdefs.
|
|
|
|
| |
the default.
|
|
|
|
|
|
|
|
|
|
|
|
| |
real path here for the mount device (or path). This fixes difficulties
unmounting devices that are actually symlinks to real devices.
Also, print the original path instead of the real path in early error
messages. nfs path handling and later error messages may still be wrong,
probably only in silly cases where the original path is both a symlink
and a remote path.
PR: 5208
|
|
|
|
|
|
|
| |
size was rounded up to a multiple of the fragment size, but this
gave invalid file systems when the fragment size was > SBSIZE (fsck
aborts early on them). Now a fragment size of 32768 seems to work
(too-simple tests with fsck and iozone worked).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
superblock is invalid, fsck looks at the label to help guess where
the next superblock should be. If the partition type is 4.2BSD,
fsck assumed that the block size was valid and divided by it, so
it dumped core if the size was 0.
Initialization of the label was broken almost 3 years ago in rev.1.9
of newfs/newfs.c. Newfs does not change the label at all, so there
is no problem (except the breakage of the automatic search for
backup superblocks) unless something else sets the partition type
to 4.2BSD. However, it is too easy to set partition types to
4.2.BSD by copying an old label or by using a disktab entry to
create the label.
PR: 2537
|
| |
|
| |
|
| |
|
|
|
|
| |
Remove unused #includes.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
rely on undocumented behavior.
The following fixes were obtained from OpenBSD:
o -Wall fixes to tlist array initialization and assignment used
as truth value.
o Use a restricted environment.
o Improved error message when shutdown fails to exec reboot or halt.
|
|
|
|
| |
Obtained from: NetBSD PR2737 (augustss@cs.chalmers.se) via OpenBSD
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
consequence, ipfw's list command now adjusts its output at runtime
based on the largest packet/byte counter values.
NOTE:
o The ipfw struct has changed requiring a recompile of both kernel
and userland ipfw utility.
o This probably should not be brought into 2.2.
PR: 3738
|
| |
|
|
|
|
|
| |
in the 22nd century and beyond even though it's irrelevant with a 32-bit
time_t which expires in the year 2038.
|
|
|
|
| |
Submitted by: bde
|
|
|
|
| |
Obtained from: Bruce.
|
|
|
|
| |
Use error codes from <sysexits.h>.
|
|
|
|
|
|
|
| |
zero/delete operations fail.
PR: 4231
Reviewed by: Archie Cobbs <archie@whistle.com>
|
|
|
|
| |
to make it print: usage: progname ...
|
| |
|
| |
|
|
|
|
|
| |
PR: 5413
Submitted by: NOKUBI Hirotaka <hnokubi@yyy.or.jp>
|
|
|
|
| |
Suggested by: joerg
|
|
|
|
|
|
|
| |
confused when they can't find it), but leave the reference to it
as being a standard filename (which doesn't imply that it exists).
Discussed with: jkh
|
|
|
|
|
| |
Submitted by: Niall Smart rotel@indigo.ie
Obtained from: OpenBSD (rev 1.7 and 1.8)
|
|
|
|
| |
Approved by: Ari Suutari <ari@suutari.iki.fi>
|
|
|
|
| |
Make the other examples prettier.
|
|
|
|
|
| |
device resides and that the -f flag must specify the `whole slice'
if it's a disk.
|
|
|
|
| |
Submitted by: Bruce Evans <bde@zeta.org.au>
|
| |
|