Marcus Brinkmann <[EMAIL PROTECTED]> writes: > For shared libraries, we use MAP_COPY. Maybe we can use this for > executables, too?
That is what we do, but the present issue is different; we're talking only about atomicity: that is, if you write the file, then your exec is either the pre-write version or the post-write version, but never some kind of mix. If the exec does several different reads and maps (all of which are already done with MAP_COPY), then these might get the file at different states; that's the point. _______________________________________________ Bug-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-hurd
