Thanks for the info. I do read the commit logs, and I was aware
of this commit; however, it's not entirely clear to me if this
commit resolves the issue I'm talking about.
The problem, as I recall, had to do with the bpf pseudo-device
attaching to devices _only_ at boot time, so it would not see
I see that support has been added for demand-loading network
if drivers. I seem to recall that the last time I tried using
network drivers as klds, nothing that required bpf to work
was functional anymore, because bpf required that the device
existed at the time it was initialized. Is this still
Thanks for the info. I do read the commit logs, and I was aware
of this commit; however, it's not entirely clear to me if this
commit resolves the issue I'm talking about.
The problem, as I recall, had to do with the bpf pseudo-device
attaching to devices _only_ at boot time, so it would not see
Donald J . Maddox scribbled this message on Sep 26:
> I see that support has been added for demand-loading network
> if drivers. I seem to recall that the last time I tried using
> network drivers as klds, nothing that required bpf to work
> was functional anymore, because bpf required that the d
I see that support has been added for demand-loading network
if drivers. I seem to recall that the last time I tried using
network drivers as klds, nothing that required bpf to work
was functional anymore, because bpf required that the device
existed at the time it was initialized. Is this still
