| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
already does. This eliminates a logical inconsistency, and a small
window where the system is open after the network comes up.
|
| |
|
|
|
| |
with theirs, so this information doesn't need to be in the live file.
Having it in our CVS history is enough.
|
| |
|
|
|
|
|
| |
makes any sense.
Discussed with: dougb, brooks
MFC after: 3 days
|
| |
|
|
| |
Some suggestions from: rwatson, Ruben de Groot <mail25@bzerk.org>
|
| |
|
|
|
|
|
|
|
| |
in keeping the scripts under rc.d in sync with us. So, remove
NetBSD specific stuff (which made our scripts more complicated
than necessary).
The NetBSD ident string will be left intact, both for history and
also incase we wish to pull in future versions.
|
| |
|
|
|
|
| |
in keeping the scripts under rc.d in sync with us. So, begin removal
of NetBSD specific stuff (which made our scripts more complicated
than necessary), starting with the NetBSD KEYWORD.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
o group them together so they run one right after another
o use the NetBSD supplied ipfs script instead of tacking
it on to the end of ipnat
o Load the ipl module in ipnat and ipfilter, if it's not already
loaded
o In ipmon and ipnat show a warning if neither ipfilter nor
ipnat is enabled or the ipl module is not loaded, and exit
Approved by: markm (mentor) (implicit)
Tested by: leafy <leafy@leafy.idv.tw>
|
| |
|
