it again and again, practically begging the Bad Man to insert his symlink
underneath it and send us down the path to oblivion.
Noticed by: David Lary <dlary@secureworks.net>
- Look for a hardwired interrupt in the routing table for this
bus/device/pin (we already did this).
- Look for another device with the same link byte which has a hardwired
interrupt.
- Look for a PCI device matching an entry with the same link byte
which has already been assigned an interrupt, and use that.
- Look for a routable interrupt listed in the "PCI only" interrupts
field and use that.
- Pick the first interrupt that's marked as routable and use that.
Also introduce a bunch of (missed?) macros and functions.
This man page still needs a lot of work, most likely a re-ordering
of the macros/functions, and a more complete, more accurate, listing of
available routines.
A good and worthy start nonetheless.
Xtal reference instead of the CLADI input.
In unframed E1 mode, tie SIGFRZ low so that the mysycc doesn't
get confused.
Don't mask errors with OOF. Don't ignore OOF errors.
Stop the channel before freeing mbufs in disconnect.
I still have no T1 devices to test with, so the T1 code is non-existent.
argument. These flags include INTR_FAST, INTR_MPSAFE, etc.
- Properly handle INTR_EXCL when it is passed in to allow an interrupt
handler to claim exclusive ownership of an interrupt thread.
- Add support for psuedo-fast interrupts on the alpha. For fast interrupts,
we don't allocate an interrupt thread; instead, during dispatching of an
interrupt, we run the handler directly instead of scheduling the thread
to run. Note that the handler is currently run without Giant and must be
MP safe. The only fast handler currently is for the sio driver.
Requested by: dfr
multicast filter on the Pegasus chip. Since IPv6 depends a lot
on multicasting, this caused several failures for people trying to
use IPv6 with Pegasus USB ethernet devices.
Submitted by: Jun Kuriyama <kuriyama@FreeBSD.org>
a) the configured default printer entry might turn out to become a security hole
Although lpd isn't enabled by default in FreeBSD 4 and later versions
bad things might happen because of a simple copy and paste failure:
- fill up root-fs, if /dev/lpt0 doesn't exist
- fill up the spool dir (either root-fs or var-fs) if machine hadn't been
designed as print server
Therefore best decision: if people want printing, then configure both
1. /etc/rc.conf
2. /etc/printcap
the default entry wouldn't have served well all tastes and needs anyway...
design of most of our config files is, to have commented out suggestions
if a service is not active.
b) [Garance]
fix old and wrong documentation:
input filters are possible even if you print to a remote printer
this makes FreeBSDs implementation of lpd currently the best without
having to switch to port monster LPRng ...
c) fix pointer to wrong handbook section for a longer time .. so I doesn't fix the number
I'm only referring to the printing section, otherwise this would have to be fixed several
times, if the chapters should be reordered again ...
d) typo: chose -> choose
Submitted by: me and some suggestions by Garance
Approved by: Eivind and Garance A Drosihn <drosih@rpi.edu> in private e-mail
* Use a sub-section (Ss) instead of a section (Sh) for
"Sysctl MIB Entries".
* Use a tagged list (Bl, El and It) instead of sub-sections (Ss) for
the actual MIB entries.
* Mark paths up as such (Pa).
* Mark defined values up as such (Dv).
of files auto-installed during an upgrade from a really old system
can get quite long, and it's piped to the PAGER already, print
that first, then print any of the 4 two-line messages that might
apply.
