Mmm, that thread is full of the same old rhetoric (i.e. it must be a risk as no one can be bothered/has time to check it and users must be prevented from hurting themselves even if they've already jumped through hoops to enable mm.vm_addr=0, which is a known security risk, so that dosemu can function with cpuemu=off). I do fail to see why the default can't have the vm86() syscall compiled in, but disabled by default at run time. It wouldn't affect anyone except those that want to turn it on at run time. (sorry about the rant, it wasn't directed at anyone here, just letting off steam!) Regarding RHEL kernels, I've used CentOS 3, 4, 5 and 6 successfully with Dosemu cpuemu=off, so CONFIG_VM86=y was set on those. On Sun, 4 Oct 2015 20:36:42 +0300 Stas Sergeev <stsp@xxxxxxx> wrote: > 04.10.2015 20:26, Felix Miata пишет: > > Andrew Bird composed on 2015-10-04 11:32 (UTC+0100): > > > >> ajb@polly:~$ grep VM86 /boot/config-`uname -r` > >> CONFIG_VM86=y > > # uname -a > > Linux gx280 4.2.1-300.fc23.i686+PAE #1 SMP Mon Sep 21 22:32:31 UTC 2015 i686 i686 i386 GNU/Linux > > # grep VM86 /boot/config-`uname -r` > > CONFIG_VM86=y > Interesting, why do they enable it? > According to this thread: > https://lists.fedoraproject.org/pipermail/devel/2015-July/212084.html > they don't even know why themselves. :) > -- > To unsubscribe from this list: send the line "unsubscribe linux-msdos" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- Andrew Bird <ajb@xxxxxxxxxxxxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
