i did not try obstacks yet, will have a look at them. what bothers me at the moment is that mremap() is not a standard and that it operates strangely to me: ENOMEM The region is private writable, and insufficient virtual memory is available to extend it. Also, this error will occur if MREMAP_MAYMOVE is not given and the extension would collide with another mapped region. i thought that mmap'ed space is only virtually aligned. possibly it's better to write buffers oneself? the posix interfaces look strange to me. they seem halfhearted and weirdly incompatible. consider a file that is growing. how to best remap it? regards, dennis heuer - To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html