Date: Tue, 6 Jun 1995 00:36:57 -0700 From: David Greenman <davidg> To: soda@sra.co.jp, davidg, freebsd-bugs Subject: Changed information for PR kern/490 Message-ID: <199506060736.AAA07227@freefall.cdrom.com>
next in thread | raw e-mail | index | archive | help
Synopsis: 2.0.5-ALPHA should change msync(2) syscall number for compatibility State-Changed-From-To: open-closed State-Changed-By: davidg State-Changed-When: Tue Jun 6 00:30:22 PDT 1995 State-Changed-Why: Any application prior to 2.0.5A that used msync would have caued the machine to panic. Thus it can be safely assumed that no application is successfully being used with it. The third argument (flags) is also currently unimplemented and (almost) completely ignored. If an old application tries to use msync with only two arguments, the worst that will happen is that junk on the stack would be used as the third arg, and then the msync might fail because of an illegal combination of flags. Considering that the machine would likely crash if the msync() did succeed, this failure is actually a good thing. :-) The above combinations of factors was the reason for deciding not to allocate a new syscall number to msync(). This was a deliberate decision and not a bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199506060736.AAA07227>