Bug#728392: linux: Please update m68k config

[Thorsten Glaser <tg@mirbsd.de>]

Dixi quod…

>Ben Hutchings dixit:
>
>>> One’s to add back CONFIG_BRK which is apparently needed to run a
>>> popular ramdisk image used e.g. when testing the hardware or setting
>>> up a completely new system.
>>
>>You mean CONFIG_COMPAT_BRK.  I don't like this but I doubt anyone cares
>>to write exploits for m68k any more.
>
>Oh sorry, yes I do. I understand why you’d not like it, but the

We could set /proc/sys/kernel/randomize_va_space to 2 in the
Debian initrd (am I correct in assuming I have to file a wishlist
bug against initramfs-tools for that?) to mitigate the effects
of this while still keeping the desired compatibility with old
rootfs/initrd images that require this option?

bye,
//mirabilos
-- 
Solange man keine schmutzigen Tricks macht, und ich meine *wirklich*
schmutzige Tricks, wie bei einer doppelt verketteten Liste beide
Pointer XORen und in nur einem Word speichern, funktioniert Boehm ganz
hervorragend.		-- Andreas Bogk über boehm-gc in d.a.s.r