| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
| |
last cleanup. Since the oid_arg2 field of struct sysctl_oid is not wide
enough to hold a long, the SYSCTL_LONG() macro has been modified to only
support exporting long variables by pointer instead of by value.
Reviewed by: bde
|
|
|
|
|
|
| |
You can now use the `want_fd' command in the vmstat display.
Suggested by: grog
|
|
|
|
|
| |
non-problems for elf -- `ld -elf -O foo.tmp -x -r foo' apparently puts
the result in a.out so it has essentially no effect.
|
| |
|
|
|
|
| |
harmful if it were used.
|
|
|
|
| |
Pre 3.0 branch cleanup casualty #4: pcvt
|
|
|
|
|
| |
i386's with 64-bit longs -- the padding between mmap()'s 5th and 6th
is an int, not a long. The other mismatches were benign.
|
|
|
|
| |
Fixed `make cleandepend'. The default is null because SRCS is null.
|
| |
|
|
|
|
| |
Superceded by the snd driver...
|
|
|
|
| |
Superceded by acd driver...
|
|
|
|
| |
Superceded by acd driver...
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
No CAM drivers available. If somebody CAMifies one of these, they
will be welcome back in the tree
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Submitted by: Peter Philipp <pjp@bsd-daemon.net>
|
|
|
|
| |
PR: 8937
|
|
|
|
| |
(can get old behavior with -DWANT_FD)
|
|
|
|
|
| |
It might cause some problem and something like USB has its
own driver.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Describe subdisk attachment in more detail
- Describe new 'makedev' command
- Correct use of 'partition' and 'slice'
- Describe 'setupstate' keyword
- Include performance guidelines for striped plexes
- Correct numerical values in examples
- Add examples for disklabel(8)
- Clarify problems creating Vinum drives on inappropriate partitions
Prodded by: NAGANUMA Yasuhiro <y_naga@carat.rim.or.jp> (slices and
partitions)
|
|
|
|
|
|
|
|
|
|
| |
- Get the (tm) signal correct in nroff versions
- Correct highlighting (docs/9196)
Sigh. This is still a long way from being correct. In particular,
the states are both incorrect, and they don't format properly in
troff. But it will have to wait until I stop changing the meanings of
the states.
|
| |
|
| |
|
| |
|
|
|
|
| |
make sure flags and stuff are set sensibly.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
hacker -> intruder (couldn't desired between this and 'cracker')
config -> configuration
sorted crossreferences
spell checked
Overall very good content, but we need one of our wordsmiths to change the
tone to match the CSRG manpages.
|
|
|
|
|
| |
which prevents sysinstall from building. We'll just have to live with
the warning on the x86. :(
|
|
|
|
|
|
| |
slightly garbled but older servers seemed to understand it).
Reviewed by: David O'Brien <obrien@nuxi.ucdavis.edu>
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
"uptime" the right way. Sheesh.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
"I've been having a problem running the patches [committed to current]
installed with the COMPAT_LINUX_THREADS option along
with the VM_STACK patches I did. I'm not sure what
the problem is, since it seemed to work before.
In any event, the attached patch fixes the problem for
me. While I've had no report of problems from anyone
else, possibly it would be wise to commit the patch
until the problem is found.
Also, there was some left-over junk in the linux_misc.c
file from some earlier work I did. The attached patch
cleans that up too."
Submitted by: "Richard Seaman, Jr." <dick@tar.com>
|
| |
|
|
|
|
| |
not EtherEZ.
|
|
|
|
| |
CRC in received frames, which we need to trim manually.
|
|
|
|
| |
Suggested by: bde
|
|
|
|
|
|
|
| |
bring in stddef.h so we can use NULL instead of 0 for pointer comparisons.
Hinted at by: Bruce Evans
Reviewed by: John Polstra
|
|
|
|
|
| |
ethernet CRC in received frames and has no option to turn this behavior
off. Trim the CRC off manually in vr_rxeof().
|
|
|
|
|
| |
an existing chain, don't forget to move xl_tx_tail to point to the new
tail end.
|
|
|
|
|
|
|
|
|
|
|
| |
in cyopen() were done in a different order than in sioopen(), partly
to (ab)use a side effect of comparam() and partly because I didn't
understand what the reset was doing (it flushes the fifos). This
turned out to be more than a cosmetic problem. Flushing the fifos
quite late is good for discarding input that arrived while the line
state was being initialized, and in the cy driver it also seems to
reduce a problem with input that arrived long ago during the previous
close (the UART loses sync too easily and for too long).
|