IMHO, you should bump param.h when you commit the kernel code that implements the new syscall. You should also have syscall/stubs in userland committed very quickly thereafter, and that would not need a version bump. (You might need to bump the libc library version.)
Later on, you can have as many userland programs access the new syscall without worrying about version. On Wed, 14 Oct 2015, Robert Swindells wrote:
If I add a new syscall at what point do I bump the version number in param.h ? Do I just do it when I have committed the kernel side or when I have done the userland bit too ? The syscall is sctp_peeloff(). Robert Swindells
+------------------+--------------------------+-------------------------+ | Paul Goyette | PGP Key fingerprint: | E-mail addresses: | | (Retired) | FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com | | Kernel Developer | 0786 F758 55DE 53BA 7731 | pgoyette at netbsd.org | +------------------+--------------------------+-------------------------+
