Fix one such THING in code to match comment.
Sort IO_GSC* into numeric order and update comments about the gaps.
Sort common SCSI addresses into alphabetical order.
Remove bogus comments about com ports having i/o size 4.
Uniformize whitespace.
Uniformize case in hex digits.
This file is very incomplete. In particular, it doesn't mention any
network cards. This doesn't matter much for the base addresses, but
it means that the comments about which addresses are free are mostly
bogus. The i/o sizes are unreliable because of split address ranges
for many devices (VGA, wd). The i/o sizes are incomplete. In
particular, there are no sizes for SCSI controllers. The bt driver
still returns a truth value instead of a size.
is an ambiguity in the NFS version 2 protocol.
VREG should be taken literally as a regular file. If a
server intents to return some type information differently
in the upper bits of the mode field (e.g. for sockets, or
FIFOs), NFSv2 mandates fa_type to be VNON. Anyway, we
leave the examination of the mode bits even in the VREG
case to avoid breakage for bogus servers, but we make sure
that there are actually type bits set in the upper part of
fa_mode (and failing that, trust the va_type field).
NFSv3 cleared the issue, and requires fa_mode to not
contain any type information (while also introduing sockets
and FIFOs for fa_type).
The fix has been tested against a variety of NFS servers.
It fixes problems with the ``Tropic'' NFS server for Windows,
while apparently not breaking anything.
Pointed-out by: scott@zorch.sf-bay.org (Scott Hazen Mueller)
documented and is incompatible with gnu cp. It has very few good effects
(it recovers some disk space) and many bad ones:
- special files are unlinked after certain errors.
- the data may not be recoverable if the source is a special file or fifo.
- unlinking destroys the target attributes as well as the target data.
- unlinking doesn't actually remove the target data if the target is multiply
linked.
mrouted-3.5n. This is being splatted onto the head rather than properly
imported thanks to the ``delete trailing whitespace'' screw. This code is
now actively working in an operational environment (the DARTNET) so I
have some confidence that the basic functionality actually works.
Obtained from: Bill Fenner, PARC, and ISI
editor" here and in the docs. People have come to understand "FDISK"
as a more generic term and have been complaining that they didn't
equate the "master" partition editor with the old fdisk stage and were
confused.
on me:
1. Mark Murray's eBones patches.
2. Joerg's German docs + fixes.
3. Various sysinstall bug fixes from me + Mark's eBones menu changes.
4. Steven G. Kargl's doc fixes.
Submitted by: markm, joerg, jkh, kargl@troutmask.apl.washington.edu
".../packages/All". The "all" category that was automatically added
for every package is gone.
Note that bsd.port.mk requires category names to start with lowercase
names, otherwise it may get confused.
Reviewed by: jkh
By the way, here is a small script to convert your local package
hierarchy. Run it in bash, as /bin/sh not only will bark at the
$(.) command substitution but will also botch the [a-z]*/*.tgz
expansion (long-standing and annoying bug, reported before).
cd /usr/ports/packages
mv .packages All
for i in [a-z]*/*.tgz; do
j=$(basename $i)
/bin/rm $i
ln -s ../All/$j $i
done
speak english. In this doc I say that "2.0.5 fills a much needed
gap between 2.0R and 2.1." No wonder the translators were confused!
I'm trying to say that we _wanted_ a gap between 2.0.5 and 2.1? That
such gaps are much needed? Wurgh! Not what I was trying to say at
all! It should have (and now does) read: "2.0.5 fills a critical
gap between 2.0R and 2.1." Critical gap, not much needed. :-)
Translators: You may wish to adjust your own translations as
well if you tried to translate my original botch! Send me diffs
as soon as you can. Thanks!
Submitted by: me
changes over another! Bad form, and I thought they
were both coming from the same author or I wouldn't have done
it. Revert to original author's version until the two Spanish
translators figure out who's doing what.. :-)
