2.0.2

To systems that support it, this release adds persistence to the soften_mmap flag across fork() and execve() calls. This solves a long standing issue of legitimate mmap calls failing on certain applications. While the soften_mmap flag addresses this, this feature removes the need to add it to a lot of files, and makes it less of a whack-a-mole situation. Also, it's safe in that it'll only activate on certain process call chains, ie; set soften_mmap on maven, and the javac 4 processes down the line will still work, but only when called through maven, the proper way to do it.