As the first machines I booted with PaX MPROTECT active were completely diskless, I didn't see any other fallout than the C/C++ compilers.
Once I booted a machine which uses local disk, it turns out that 'fsck_ffs' fails due to expecting to write to the text segment. As such, # paxctl +m /sbin/fsck_ffs is needed. It still prints: fsck_ffs: text relocations but otherwise works now. -- |/"\ John D. Baker, KN5UKS NetBSD Darwin/MacOS X |\ / jdbaker[snail]mylinuxisp[flyspeck]com OpenBSD FreeBSD | X No HTML/proprietary data in email. BSD just sits there and works! |/ \ GPGkeyID: D703 4A7E 479F 63F8 D3F4 BD99 9572 8F23 E4AD 1645
