On 02.12.2017 22:23, David Holland wrote: > On Sat, Dec 02, 2017 at 10:04:26PM +0100, Maxime Villard wrote: > > > Revert this. Compat on amd64 must be available all the way back to > > > 0.9, same as i386. > > > > > > Also, please stop unilaterally breaking the world. > > > > You are kidding, right? Everything below COMPAT_15 has *never* been > > enabled. This change does not break anything, since nothing was > > enabled in the first. > > No, I am not kidding. It is there in GENERIC so it can be enabled for > people who want to run very old i386 binaries. > > > "Compat on amd64 must be available" > > > > What authority do you have to say that? It has never been this way. > > Providing compat has been policy for 25+ years. > > Since you bring up the notion of authority... what authority do you > think you have to make declarations about what will and won't be > removed? > For the record, we were fixing 0.9 compat in HEAD at least in May 2017, after the breakage from vm.user_va0_disable. (I recall commits fixing syscalls that were introduced later). http://gnats.netbsd.org/52246 It used to work on a NetBSD-7.99.71/amd64 kernel with NetBSD-0.9/i386 a.out executables. I still want to use this software as reference, but I will ask core@ what to do.
Attachment:
signature.asc
Description: OpenPGP digital signature