[src/trunk]: src/doc npf_boot rc script loads npf.boot.conf to address that i...

[sevan <sevan%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/6568210b9713
branches:  trunk
changeset: 840570:6568210b9713
user:      sevan <sevan%NetBSD.org@localhost>
date:      Wed Apr 10 10:47:23 2019 +0000

description:
npf_boot rc script loads npf.boot.conf to address that issue.

diffstat:

 doc/TODO.npf |  2 --
 1 files changed, 0 insertions(+), 2 deletions(-)

diffs (12 lines):

diff -r f80c33b9b14e -r 6568210b9713 doc/TODO.npf
--- a/doc/TODO.npf      Wed Apr 10 10:09:23 2019 +0000
+++ b/doc/TODO.npf      Wed Apr 10 10:47:23 2019 +0000
@@ -19,8 +19,6 @@
    this is what it does. It does not "start" because like an engine with
    no fuel, an npf with no configuration does not do much.
 
--- npf starts up too late (after traffic can go through)
-
 -- although the framework checks the file for consistency, returning EINVAL
    for system failures is probably not good enough. For example if a module
    failed to autoload, it is probably an error and it should be reported