| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Submitted by: dcs
|
|
|
|
| |
PR: bin/25337
|
|
|
|
| |
Reviewed by: peter
|
|
|
|
|
|
| |
comments/additions/corrections are welcome.
Obtained from: KAME
|
|
|
|
|
|
| |
and quota.group.
PR: docs/25124
|
| |
|
|
|
|
| |
Obtained from: KAME
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
userland tool:
Use the vfs.devfs.generation sysctl to test for devfs presense
(thanks phk!) when devfs is active it will not try to create the
device nodes in /dev and therefore will not complain about the
failure to do so.
Revert the change in the #define for VINUM_DIR in the kernel
header so that vinum can find its device nodes.
Replace perror() with vinum_perror() to print file/line when
DEVBUG is defined (not defined by default).
kernel:
Don't use the #define names for the "superdev" creation since
they will be prepended by "/dev/" (based on VINUM_DIR), instead
use string constants.
Create both debug and non-debug "superdev" nodes in the devfs.
Problem noticed and fix tested by: Martin Blapp <mblapp@fuchur.lan.attic.ch>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
actually in the kernel. This structure is a different size than
what is currently in -CURRENT, but should hopefully be the last time
any application breakage is caused there. As soon as any major
inconveniences are removed, the definition of the in-kernel struct
ucred should be conditionalized upon defined(_KERNEL).
This also changes struct export_args to remove dependency on the
constantly-changing struct ucred, as well as limiting the bounds
of the size fields to the correct size. This means: a) mountd and
friends won't break all the time, b) mountd and friends won't crash
the kernel all the time if they don't know what they're doing wrt
actual struct export_args layout.
Reviewed by: bde
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Use sysctlbyname() instead of sysctl().
Clear up and simplify the version extraction code.
Attempt to detect stretches of zeroes in the dump and avoid writing
them to disk to save space and time.
|
|
|
|
| |
Submitted by: Akio Morita <amorita@meadow.scphys.kyoto-u.ac.jp>
|
|
|
|
|
|
| |
They can't be created via mknod and the kernel crashes if it encounters
such an inode.
Approved by: mckusick
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
address is configured on a interface. This is useful for routers with
dynamic interfaces. It is now possible to say:
0100 allow tcp from any to any established
0200 skipto 1000 tcp from any to any
0300 allow ip from any to any
1000 allow tcp from 1.2.3.4 to me 22
1010 deny tcp from any to me 22
1020 allow tcp from any to any
and not have to worry about the behaviour if dynamic interfaces configure
new IP numbers later on.
The check is semi expensive (traverses the interface address list)
so it should be protected as in the above example if high performance
is a requirement.
|
| |
|
|
|
|
|
|
|
| |
Add .Xr to fsck.
Prompted by: JM Jr's script that shows binaries with no whatis info
Reviewed by: adrian
|
|
|
|
| |
mount would show up as "/dev/", loose that trailing slash.
|
|
|
|
|
|
| |
to be the same as -ragged in the current implementation) to
-ragged. With mdocNG, -filled displays produce the correct
output, formatted and justified to both margins.
|
|
|
|
|
|
| |
Seperate does not exist in the english language.
Submitted to look at by: kris
|
|
|
|
|
| |
PR: 24842
Submitted by: Rich Morin <rdm@cfcl.com>
|
|
|
|
|
| |
PR: docs/24693
Submitted by: Etienne Vidal <hallik@libertysurf.fr>
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
field, so it was possible for a filesystem marked clean by fsck_ffs
to cause kernel crashes later when mounted. This could occur when
fsck_ffs was used to repair a badly corrupted filesystem.
As pointed out by bde, it is not sufficient to restrict di_size to
just the superblock fs_maxfilesize limit. The use of 32-bit logical
block numbers (both in fsck and the kernel) induces another file
size limit which is usually lower than fs_maxfilesize. Also, the
old 4.3BSD filesystem does not have fs_maxfilesize initialised.
Following this change, fsck_ffs will enforce exactly the same
file size limits as are used by the kernel.
PR: kern/15065
Discussed with: bde
Reviewed by: bde, mckusick
|
| |
|
| |
|
|
|
|
| |
Reviewed by: sheldonh
|
|
|
|
| |
Submitted by: "Jason Smethers" <jsmethers@pdq.net>
|
|
|
|
| |
Submitted by: "Jason Smethers" <jsmethers@pdq.net>
|
|
|
|
|
|
|
| |
Commit the right version, but without the -b option which is too evil
for the present.
Remove -b and preload from the manpage as well.
|
|
|
|
|
|
| |
Remember to set mode 1777 on /tmp
Submitted by: mjacob
|
| |
|
|
|
|
| |
ENOENT.
|
|
|
|
|
| |
Due to the old message, I spent way more time debugging a diskless
root problem than it should have taken.
|
|
|
|
| |
This is untested, but believed to work.
|
|
|
|
| |
Obtained from: KAME
|
|
|
|
| |
Submitted by: ru
|
| |
|
|
|
|
| |
PR: kern/24248
|
|
|
|
|
| |
PR: 23984
Submitted by: Jimmy Olgeni <olgeni@uli.it>
|
|
|
|
|
|
|
|
|
|
|
| |
Removed used copies of ../mount/getmntopts.c ../mount/mntopts.h. Use the
versions in ../mount directly like all other mount utilities.
Removed used copy of ../mount/pathnames.h. Use the version in ../mount
for free as a side effect of using the mntopts files there. We should
not use it at all, since the 2/3 of the definitions in it are in <paths.h>
and the other 1/3 should be in ../mountd/pathnames.h and is not used by
mount_ifs anyway.
|
|
|
|
| |
been repo-copied.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Submitted by: Jimmy Olgeni <olgeni@uli.it>
PR: 24233
Fix typos.
Submitted by: "Jeroen C. van Gelderen" <jeroen@vangelderen.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
in-core pointers to summary information. An array in this region
(fs_csp) could overflow on filesystems with a very large number of
cylinder groups (~16000 on i386 with 8k blocks). When this happens,
other fields in the superblock get corrupted, and fsck refuses to
check the filesystem.
Solve this problem by replacing the fs_csp array in 'struct fs'
with a single pointer, and add padding to keep the length of the
128-byte region fixed. Update the kernel and userland utilities
to use just this single pointer.
With this change, the kernel no longer makes use of the superblock
fields 'fs_csshift' and 'fs_csmask'. Add a comment to newfs/mkfs.c
to indicate that these fields must be calculated for compatibility
with older kernels.
Reviewed by: mckusick
|
| |
|