| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
| |
contrib/bind/doc/{html,misc} as /usr/share/doc/bind/{html,misc}
Install additional manpages:
. named.conf.5
. nsupdate.8
. named-bootconf.8
|
|
|
|
| |
/usr/share/doc/bind/{html,misc}
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
possible.
|
| |
|
|
|
|
|
| |
the vga driver won't be fooled to believe it has a CGA card when
in fact it is a VGA card.
|
|
|
|
| |
. s/freebsd/FreeBSD
|
|
|
|
| |
- Remove erroneous comments.
|
|
|
|
| |
Submitted by: "Kenneth D. Merry" <ken@kdm.org>
|
|
|
|
|
|
|
|
|
|
| |
- Don't use realpath as stat does the right thing.
- Only check ufs filesystems in getmntpt.
- Dont' bother checking that the ufs-mounted-on
device is a special file. It *must* be a special
file, or ufs wouldn't have mounted it.
Submitted by: Paul Saab <ps@yahoo-inc.com>
|
|
|
|
| |
Submitted by: Paul Saab <ps@yahoo-inc.com>
|
|
|
|
|
|
|
| |
Driver is not functional yet, but does compile. Tests with xe cards
indicates that it doesn't panic the machine when they are present, but
fail to probe. Interface help in the pcic/pccard layers are needed to
complete this driver.
|
|
|
|
|
|
|
| |
This prevents a more mysterious crash later.
XXX The long term solution is defer creation of these things until
XXX proc0 lives
|
|
|
|
| |
Submitted by: green
|
|
|
|
|
|
|
|
|
|
|
| |
o ifdef out pccardchip.h (almost all of it, there are dangling bits
o Add rid/res members to pccard_function
o remove pct/pch from pccard_softc
o map memory properly in scan_cis (almost, see XXX for more work)
o manage ccr.
o remove bogus comment I added about touching the ccr being a layering
violation for pccard. It is properly done at that level.
o More function prototyping
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
script is gone.
PR: 15932
Submitted by: Jos Backus <Jos.Backus@nl.origin-it.com>
Tested by: brian, Manfred Antar <mantar@pacbell.net>
|
|\
| |
| |
| | |
which included commits to RCS files with non-trunk default branches.
|
| |
| |
| |
| | |
infringement reasons.
|
| |
| |
| |
| |
| |
| | |
whilst we are playing or recording. since we should irq ~20 times/sec when
active, this should never trigger. in theory. if it never does trigger,
the check will be removed.
|
| |
| |
| |
| |
| | |
working on this code, or things that I think are layering violations.
Plus a minor whitespace cleanup in one place while I'm at it.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
with kld etc just fine, but tracebacks would have less information and
nm /kernel wouldn't be so good).
- Just strip the kernel on the boot disk. This does not affect kld or
module loading, there are two symbol tables in a kernel. There is the
dynamic linking one (.dynsym+.strtab) with just global symbols and a user
symbol table (.symtab+.strtab) with all symbols. BTW; objdump lies and
hides the second one. There's a good half a meg or so that can be saved
from an average kernel by stripping it.
|
| |
| |
| |
| | |
This was suggested by Doug a while ago.
|
| |
| |
| |
| | |
places), and we don't want people to get in trouble just for having it.
|
| |
| |
| |
| |
| |
| |
| | |
This doesn't need to be applied to stable, because somehow -stable seems
to have gotten it right.
Reviewed by: jasone
|
| |
| |
| |
| |
| |
| |
| |
| | |
to wake up any processes waiting via PIOCWAIT on process exit, and truss
needs to be more aware that a process may actually disappear while it's
waiting.
Reviewed by: Paul Saab <ps@yahoo-inc.com>
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
o Realloc memory leak fixed which won't matter but would trigger purify
o Default to sendmail when no mailer.conf exists.
Fixed bugs in OpenBSD version:
o Add NULL termination in the right place.
Also put back the err. free shouldn't touch errno.
Pointed out by: theo de raadt (except the NULL bug :-)
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
working on -current.
Submitted by: Eric D. Futch <efutch@nyct.net>
Approved by: mdodd
|
| |
| |
| |
| |
| | |
in a little while as soon as I find all the places it is used in the
tree.
|
| | |
|
| |
| |
| |
| | |
spurious parity errors on some controllers.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
a string containign 'J'.
o Properly terminate argv list with a NULL entry.
o Use warn() to report the exec failure because free could change errno and
err would report the wrong reason.
o Don't terminate string to err with ':' since this results in two colons.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
1) Fastpath deletions. When a file is being deleted, check to see if it
was so recently created that its inode has not yet been written to
disk. If so, the delete can proceed to immediately free the inode.
2) Background writes: No file or block allocations can be done while the
bitmap is being written to disk. To avoid these stalls, the bitmap is
copied to another buffer which is written thus leaving the original
available for futher allocations.
3) Link count tracking. Constantly track the difference in i_effnlink and
i_nlink so that inodes that have had no change other than i_effnlink
need not be written.
4) Identify buffers with rollback dependencies so that the buffer flushing
daemon can choose to skip over them.
|
| |
| |
| |
| | |
Benchmarks that create huge trees of empty files overwhelm the buffer cache.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
it only on the buf_daemon process). The problem is that when the
syncer process starts running the worklist, it wants to delete
lots of files. It does this by VFS_VGET'ing the vnodes, clearing
the blocks in them and bdwrite'ing the buffer. It can process close
to a thousand files per second which generates a large number of
dirty buffers. So, giving it special priviledge at the buffer trough
leads to trouble as the buf_daemon does occationally need a free
buffer to proceed and if the syncer has used every last one up,
we are toast.
|
| |
| |
| |
| |
| |
| | |
of dirrem structure rather than the collaterally created freeblks
and freefile structures. Limit the rate of buffer dirtying by the
syncer process during periods of intense file removal.
|
| |
| |
| |
| |
| |
| | |
* bring in NIC comments from GENERIC
* slightly reorder a few things in an feable attempt at making the
organization of LINT more logical.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
check before the inode is unlocked while grabbing its parent directory.
Once it is unlocked, other operations may slip in that could make
the inode-is-flushed check fail. Allowing other writes to the inode
before returning from fsync does not break the semantics of fsync
since we have flushed everything that was dirty at the time of the
fsync call.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
init and fini functions. Now the code is very careful to hold no
locks when calling these functions. Thus the dynamic linker cannot
be re-entered with a lock already held.
Remove the tolerance for recursive locking that I added in revision
1.2 of dllockinit.c. Recursive locking shouldn't happen any more.
Mozilla and JDK users: I'd appreciate confirmation that things still
work right (or at least the same) with these changes.
|