(tightly scoped) reason for recording the node address by recording
the assigned number. Dink pci/if_bge.c to match, since ic/ath.c was
used as the archetype.
external buffer for the PC card connected to the channel. This hack
makes pcmcia cards "being used" at the boot time (by WinCE or NetBSD)
correctly detected. A machine running with root on NFS can now be
properly rebooted.
reversed order.
When you boot with two CF cards inserted, this options makes the one
in the "memory only" slot (channel 1), which is almost always the card
with the NetBSD install, attached as wd0.
Unlike using fixed unit numbers in the kernel config, if you boot with
only a single CF card, that single card will still be wd0 regardless
of which slot it is inserted in.
http://mail-index.netbsd.org/port-hpcsh/2003/10/23/0000.html provides
a more verbose description of why this option is convenient for most
usage patterns.
numbers passed in instead of using a BEGIN construct. nawk didn't like
the hex escapes used there.
Fixes a problem reported by Shin'ichiro TAYA on port-powerpc.
Use "int(NUMBER)%256" instead of just "NUMBER" in the printf "%c"
statements in the awk script. nawk was appearing to refuse outputing
a 0 byte of the low eight bits of the number were 0 but any higher
bits were set.
walnut-mkimg.sh tested using gawk, nawk and mawk.
yesterday's sys/dev/ic/ath.c) to match today's ath.c driver.
Commit now in the hope that Andrew Brown will pick up this file for
any more pending changes.
other semantics from an earlier incarnation.
Call kcont_init() from init_main before device autoconfiguration,
so kcont is availble to device drivers if required.
Also ensure the kthread process runs any pending continuations once
the kthread is finally up and running. For now, use a non-null timeout
to poll the queue periodically. Draining any pending requests just
before the kthread enters its ltsleep()/kc_run loop is cleaner, but
this is the version I tested with an early-in-boot kcont request.)
configuration to enable inbound mail reception.
This is in line with general security policy, so that postfix is
"safe" until other required configuration steps have been taken.
This way, systems enabling this mailer for local mail delivery only
won't be vulnerable to surprise exploits, being used as relays,
/var/mail filling up with spam, etc.
