> Date: Wed, 02 Aug 2017 18:19:27 +1000 > from: matthew green <[email protected]> > > > compat_linux > > compat_linux32 > > compat_netbsd32 > > all of these are used regularly by many netbsd users. please don't > include them in your list of targets. saying "modload is OK" is > not how we treat the GENERIC kernel -- if it's OK, then it's OK for > GENERIC is how we treat that. > > the latter is also essential for our mips64 platforms.
Evidently my original message was very confusing, for which I apologize -- you're about the fourth person to have read it this way. Let me try to be a little clearer here. I propose to disable the following modules by default, but leave the code so you can still modload them or include them in your custom kernel config if you want: compat_freebsd compat_ibcs2 compat_linux compat_linux32 compat_ndis compat_osf1 compat_sunos compat_sunos32 compat_svr4 compat_svr4_32 compat_ultrix exec_coff exec_ecoff I *DO NOT* propose *ANY* changes to the following modules, and I make no representation about their notoriety or non-notoriety for bugginess, and I'm not asking about users of them, even though they appear at first glance to match or be relevant to the `compat_xyz' pattern mentioned in the subject or the other modules listed here: compat (i.e., old-NetBSD binary compat) compat_aoutm68k compat_netbsd32 exec_aout exec_elf32 exec_elf64 exec_script
