ena(4) is not in GENERIC, now default for some/all instances on AWS EC2
Rodney W. Grimes
freebsd-rwg at pdx.rh.CN85.dnsmgr.net
Sat Jan 13 04:35:00 UTC 2018
> On Thu, Jan 11, 2018 at 10:14:55AM -0800, Maxim Sobolev wrote:
> > Well, that might work, but I am curious why do we have all other network 40
> > or so drivers in the GENERIC but not this one. Considering significant
> > portion of FreeBSD systems deployed these days are going to be running on
> > the cloud this makes no sense to me. Is there some policy out there which
> > governs such decisions?
>
> Email current@ and ask if there are any objections before you add it to
> GENERIC?
There is work going on in -current by Warner (imp@) called devmatch that
makes this issue go away and rips out all the other drivers from GENERIC
that can be automatically loaded by devmatch in the future.
--
Rod Grimes rgrimes at freebsd.org
More information about the freebsd-virtualization
mailing list