| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
effect on operation of fsck on filesystems without snapshots.
If you get compilation errors, be sure that you have copies of
/usr/include/sys/mount.h (1.94), /usr/include/sys/stat.h (1.21),
and /usr/include/ufs/ffs/fs.h (1.16) as of July 4, 2000 or later.
|
| |
|
| |
|
|
|
|
|
|
| |
savings of 68 bytes in boot2.
- Also add a comment warning that you can't remove the empty exit()
function.
|
| |
|
|
|
|
| |
Obtained from: KAME
|
|
|
|
| |
Obtained from: KAME
|
| |
|
| |
|
|
|
|
|
| |
zeros, it is actually the disklabel itself. boot2.ldr is simply a
placeholder in the boot2 binary.
|
| |
|
|
|
|
| |
Obtained from: KAME
|
|
|
|
| |
Obtained from: KAME
|
| |
|
|
|
|
| |
Submitted by: Ri?ardas ?epas <rch@richard.eu.org>
|
|
|
|
|
|
| |
This is required for forthcoming IPv6 ready installer.
Obtained from: KAME
|
| |
|
|
|
|
|
|
|
|
| |
produced human-readable output. I like this, but it's certainly not
something to change willy-nilly without discussion. Revert to -k.
Anyway, the new variable allows folks to pick any units flag that
fits their fancy.
|
|
|
|
|
|
| |
password was empty.
Reviewed by: Warner Losh <imp@freebsd.org>
|
| |
|
| |
|
|
|
|
| |
in ${local_startup} with the `stop' option on shutdown.
|
| |
|
|
|
|
| |
Obtained from: KAME
|
|
|
|
| |
Obtained from: KAME
|
|
|
|
|
|
|
|
|
|
| |
the command-line arguments to be used for the call to df(1) when
daily_status_disks_enable is set to YES.
The name of the new variable was chosen by the maintainer of our
periodic hierarchy, Brian Somers.
PR: 19631
|
|
|
|
|
|
|
| |
and not a file name.
PR: 19698
Reported by: Jeff Blaine <jblaine@mitre.org>
|
|
|
|
|
|
| |
XXX what is the goal of af_switch()? it seems to me it is not necessary
any more with getaddrinfo(3) fix for correct name-resolution ordering.
comments? >shin
|
|
|
|
| |
Obtained from: KAME
|
|
|
|
|
| |
PR: 19689
Submitted by: SUGIMURA Takashi <sugimura@jp.FreeBSD.org>
|
|
|
|
| |
Obtained from: KAME
|
|
|
|
| |
Obtained from: KAME
|
|
|
|
| |
Obtained from: KAME
|
|
|
|
|
| |
supports "delete" subcommand.
corrects PR 19663.
|
|
|
|
|
| |
- correct scoped notation separator (s/@/%/)
- include example and more references
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
SYSCTL_LONG macro to be consistent with other integer sysctl variables
and require an initial value instead of assuming 0. Update several
sysctl variables to use the unsigned types.
PR: 15251
Submitted by: Kelly Yancey <kbyanc@posi.net>
|
|
|
|
| |
to like better (it's commented and easier to read).
|
|
|
|
|
|
| |
sure that it really is by issuing a ISPCTL_ABORT_CMD just on the
off chance the f/w will start it up again and, ha ha, start using
the DMA resources we gave it but are now taking away.
|
|
|
|
|
| |
or even if it fails with INVALID_PARM (which just means that the handle
doesn't refer to an active commane).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
insertion of a CF card, for random values of N > 1. With these fixes,
I've been able to do 100 insert/remove of the cards w/o a crash with
lots of system activity going on that in the past would help trigger
the crash.
The problem:
FreeBSD creates dev_t's on the fly as they are needed and never
destroys them. These dev_t's point to a struct disk that is used for
housekeeping on the disk. When a device goes away, the struct disk
pointer becomes a dangling pointer. Sometimes when the device comes
back, the pointer will point to the new struct disk (in which case the
insertion will work). Other times it won't (especially if any length
of time has passed, since it is dependent on memory returned from
malloc).
The Fix:
There is one of these dev_t's that is always correct. The
device for the WHOLE_DISK_SLICE is always right. It gets set at
create_disk() time. So, the fix is to spend a little CPU time and
lookup the WHOLE_DISK_SLICE dev_t and use the si_disk from that in
preference to the one that's in the device asking to do the I/O. In
addition, we change the test of si_disk == NULL meaning that the dev
needed to inherit properties from the pdev to dev->si_disk !=
pdev->si_disk. This test is a little stronger than the previous test,
but can sometimes be fooled into not inheriting. However, the results
of this fooling are that the old values will be used, which will
generally always be the same as before. si_drv[12] are the only
values that are copied that might pose a problem. They tend to change
as the si_disk field would change, so it is a hole, but it is a small
hole.
One could correctly argue that one should replace much of this code
with something much much better. I would be on the pro side of that
argument.
Reviewed by: phk (who also ported the original patch to current)
Sponsored by: Timing Solutions
|
|
|
|
|
|
|
|
| |
- permit numeric scopeid, be more careful about buffer size
TODO: 2nd arg type should be socklen_t for RFC2553 conformance,
but due to include file dependency it is not a easy thing to do
(netdb.h does not have socklen_t)
|
|
|
|
|
| |
- better return code. from enami@netbsd
- do not use "class" as variable name. C++ guy had trouble with it.
|
|
|
|
|
|
| |
capability-related syscall wrappers.
Obtained from: TrustedBSD Project
|
|
|
|
|
|
|
| |
soon to be committed syscall stubs. These calls will be used to get
and set capability state associated with executables.
Obtained from: TrustedBSD Project
|
|
|
|
|
|
|
| |
error was introduced during the merge; fixing it corrects a (correct)
warning about types.
Obtained from: TrustedBSD Project
|
|
|
|
|
|
| |
committed
Obtained from: TrustedBSD Project
|
| |
|
|
|
|
|
|
| |
interface addresses in a portable manner, without headache of SIOCGIFCONF
or sysctl. it is in bsdi/openbsd/netbsd already.
from kame tree (actually, mandatory for latest kame tree).
|