| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Submitted by: "Philippe Charnier" <charnier@lirmm.fr>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Filter based on ICMP types.
- Accept interface wildcards (e.g. ppp*).
- Resolve service names with the -N option.
- Accept host names in 'from' and 'to' specifications
- Display chain entry time stamps with the -t option.
- Added URG to tcpflags.
- Print usage if an unknown tcpflag is used.
- Ability to zero individual accounting entries.
- Clarify usage of port ranges.
- Misc code cleanup.
Closes PRs: 1193, 1220, and 1266.
|
| |
|
|
|
|
|
|
|
|
|
| |
This covers the security problem descibed in SA-96:10 and Jeff says that
when we upgrade to Lite2 (which fixes this problem), mount no longer needs
to be setuid, so we'll never be going back.
Submitted by: hsu
Reviewed by: pst
|
|
|
|
|
| |
even work. Until pst wakes up, best action deemed to be the simple disabling
of this command.
|
|
|
|
| |
as argv[0].
|
| |
|
|
|
|
|
|
|
|
|
| |
mount_* programs. While we're at it, collapse the four now-identical
mount programs for devfs, fdesc, kernfs, and procfs into links to
a new mount_std(8) which can mount any really generic filesystem
such as these when called with the appropriate argv[0].
Also, convert the mount programs to use sysexits.h.
|
| |
|
|
|
|
|
|
| |
Reviewed by: phk
Submitted by: "Daniel O'Callaghan" <danny@panda.hilink.com.au>
Submitted by: Archie Cobbs <archie@whistle.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Subject: Fix for annoying fsck bug
Date: Wed, 24 Jan 1996 13:33:29 -0700 (MST)
The following small diff fixes the annoying fsck bug that causes it to
need to be run twice to end up with correct reference counts for inodes
for directories that had subdirectories relocated into the lost+found
directory.
I found the need to rerun *extremely* annoying. This fix causes the
count to be correctly adjusted later in pass 4 by correctly stating
the parent reference count.
Note that the parent reference count is incremented when the directory
entry is made (for ".."), but is not really there in the case of a
directory that does not make an entry in its parent dir.
This can be tested by waiting for the inode sync after cd'ing from a
shell into a test fs. Then you "mkdir xxx yyy zzz", wait a second,
and hit the machine reset button.
Reviewed by: nate (Tested lots of crashes :)
Submitted by: Terry Lambert <terry@lambert.org>
|
| |
|
|
|
|
| |
Ok'd by: peter
|
| |
|
| |
|
|
|
|
|
|
| |
Closes PR #misc/1172: Error in sbin/dset/Makefile
Submitted by: masafumi@tky007.tth.expo96.ad.jp (Masafumi NAKANE)
|
|
|
|
| |
program. Use the .Fx (FreeBSD) macro in the HISTORY section.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
was broken. It forced udp in all cases except the extremely unusual case
argc == 0.
|
|
|
|
| |
can be loaded (e.g. ./mymod.o)
|
|
|
|
|
|
| |
to int32_t. I only fixed the ones that I noticed the warnings for.
Perhaps most of the format strings are correct now because they were
wrong before. Except of course if int32_t isn't compatible with `int'.
|
|
|
|
| |
- should this be documented in the man page?
|
| |
|
| |
|
|
|
|
| |
Add main purpose description (MSDOS timestamps)
|
|
|
|
|
| |
related man pages. Comment out cross references to those man
pages from other man pages.
|
|
|
|
|
|
| |
man pages up to mdoc guidelines and fix some minor formatting glitches.
Also fixed a number of man pages to not abuse the .Xr macro to
display functions and path names and a lot of other junk.
|
| |
|
|
|
|
|
| |
sufficient to transfer all the data from stdin, or to stdout. Working
on pipes causes further fragmentation.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Manage adjkerntz kernel variable even for UTC clocks.
Code cleanup.
|
|
|
|
|
| |
warning about the root directory, then you could corrupt your filesystem
if you write to it. Someone, please, feel free to improve this :-)
|
|
|
|
| |
add new feature for "established"
|
|
|
|
|
| |
Reviewed by: phk
Submitted by: "Frank ten Wolde" <franky@pinewood.nl>
|
|
|
|
|
|
| |
discussionn when they were initially added some time ago.
These programs are not needed before nfs is up and running to possibly
mount /usr so they dont need to be static and on the root fs.
|
|
|
|
|
|
| |
- use rpcgen to generate unmodified code instead of havinf it in the
repository
- use "natural" function names to avoid conflicts with prototypes etc.
|
|
|
|
|
|
|
| |
- Use rpcgen to generate the unmodified boilerplate code rather than
having it in the repository.
- Eliminate the conflicting function names by changing them to their
"natural" rpcgen generated names
|
|
|
|
| |
Obtained from: 4.4BSD-Lite2
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
found when the user specifies "mount -t type". Instead of printing
out one message for each path element (/sbin, /usr/sbin), it prints
out:
mount: exec mount_type not found in /sbin, /usr/sbin: No such file or directory
The code is quite long for such a stupid little piece of aesthesism
but it is very straghtforward so I guess it's ok. Besides, I don't
want to do a "char foo[100];" and have malloc break down when someone
decides to add a few more paths to a variable that's far apart from
this code. :)
By the way, there is no malloc() off-by-one error for the '\0' at the
end of the string although I don't explicitly add 1 to the length.
The code allocates strlen(path element)+2 bytes for each path element,
and doesn't use the last two bytes (for the delimiting ", ").
Reviewed by: the list (I hope)
|
|
|
|
|
| |
No redial command. Empty redial command. Non-empty redial command.
Pointed-by: bde
|
| |
|
|
|
|
|
| |
that nfs mounts work again (I locked up my home machine testing it and can't
see what happened until I get home from work tonight).
|
|
|
|
|
| |
for file system types that actually cause a panic (ufs, msdos, cd9660).
This makes /proc mountable again.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
device file and the mount point. This prevents the "unexpected recursive
lock" panic from happening.
This is a temporary fix. A kernel fix would be much much more ugly than
this, and still wouldn't be the "right" way to fix it. After some
of Terry's file system rework is installed, it will be possible to
properly fix this problem in a clean manner. Until then,
this change should prevent use from getting a problem report
on this every month or so (and I just noticed that someone in
one of the freebsd news groups was complaining about this problem, too).
|