feature in CVSup-14.0. You no longer need a 200-column window to look
at them.
Also did some general cleanups, and corrected some errors.
2.2 candidate. These should be brought directly into 2.2 if at all
possible, since they correspond with the CVSup release whose port is
going to go into 2.2.
refer the reader to the detailed information in section 5,
remove the mount_* man pages for those file system. mount_std(8)
to cover all of the file systems it is currently being used
to mount.
mount_{devfs, fdesc, kernfs, procfs}.8 are now
MLINKS to mount_std.
I don't want it in sysinstall/help, since that'll get it stuck on the
actual floppy, and I didn't fell like creating a doc/ subdirectory for
one file either. Bah.
use of stdio, I can't just go handing fileno(fp) around and expect
that to work. Since this means I need to have sysinstall play pipeline
on single file distributions now, that means I can also finally add a
progress indicator for them.
Change installation instructions to note that there's no dists directory
anymore on CDROMs.
version of strdup() by a macro, killed many calls to strdup(), thus
potentially wasting less malloc'ed space (their args were never be
free()ed desptie despite of being malloc'ed). Probably still a huge
memory leak at all... Also killed two totally useless variables.
I've tested it as i could, but wouldn't be surprised if unexpected
problems showed up. So watch out this space!
conservative part of the tidyup, like fixing potential buffer overflow
conditions. It is believed to be safe to go into 2.2.
Pointed out by: lozenko@cc.acnit.ac.ru (Evgeny A. Lozenko)
EISA slots to probe. This is mainly intended to allow installing the
system on an HP Netserver with an on-board AIC7xxx EISA SCSI
controller, that is sitting on EISA slot # 11.
Documentation updates explaining this hack will follow shortly.
Note that this can go away again as soon as the EISA device probing
is more intelligent about the address space clash with the PCI address
space.
2.2 candidate.
Not objected by: freebsd-core :)
that we do allow mlock to span unallocated regions (of course, not
mlocking them.) We also allow mlocking of RO regions (which the old
code couldn't.) The restriction there is that once a RO region is
wired (mlocked), it cannot be debugged (or EVER written to.)
Under normal usage, the new mlock code will be a significant improvement
over our old stuff.
