If you are going to disable COMPAT_FREEBSD in GENERIC kernels, then you probably also need to disable twe(4) and twa(4) as well. I would not be in favor of this. Several people have written saying they use tw_cli. I've not written, but I too use tw_cli to manage 3ware cards under NetBSD. I think a better fix would be to update the man pages so they document how fragile the FreeBSD compatibility code is.
-thanks -Brian On Feb 13, 12:35pm, Maxime Villard wrote: } Subject: Re: Removal of compat-FreeBSD } Apparently, compat-FreeBSD is needed by tw_cli users. } } Therefore I think I will just disable it by default in the GENERIC kernels, } unless anyone disagrees. } } } } Le 07/02/2015 12:19, Maxime Villard a écrit : } > Hi, } > I intend to remove the compat-FreeBSD support from the system. } > } > It has a limited interest since no major proprietary software is developed on } > FreeBSD; if one were, it would certainly be available on Linux, and we have full } > compatibility support for that. } > } > You will also notice, after reading the code a bit, that our FreeBSD layer is } > really poor: many syscalls are missing, the translation is not efficient, and } > the layer is only available on i386. Recent FreeBSD-10 binaries often crash. } > } > Recently we found two enormous bugs so obvious and harmful that we should } > normally have received a bug report from a user somewhere. We didn't, which } > means that in 6 years nobody tested compat-FreeBSD - "nobody" being the } > developers and the users. } > } > Clearly, we should not waste time and energy on something that simply does not } > work. compat-FreeBSD could give the impression NetBSD has a reliable way to } > execute FreeBSD binaries, which is far from being the case. } > } > This is what motivates my proposal. } > } > Ok? } > } >-- End of excerpt from Maxime Villard
