> Hmm, you need to bump the kernel version for this change.

and why is that?  I did bump the libc version number when I removed it from
libc 2 months ago.  And since a libc bump is all I did when adding it
originally, I don't see why a kernel version bump would be needed now.

> IMHO even if the syscall was unused for a few weeks.

that's irrelevant, I only mentioned this since it tells people that they
need to have a libc/libpthread from after 2004/01/02 and that any binaries
linked statically against libpthread won't work anymore.  It was decided
back then that we'd only keep sa_unblockyield around as long as it doesn't
need maintenance and that we'd definitely dump it before 2.0 so we never
have a release with it.

    christian

> On Sun, Mar 14, 2004 at 12:47:26AM +0000, Christian Limpach wrote:
> >
> > Module Name: src
> > Committed By: cl
> > Date: Sun Mar 14 00:47:26 UTC 2004
> >
> > Modified Files:
> > src/sys/kern: init_sysent.c syscalls.c
> > src/sys/sys: syscall.h syscallargs.h
> >
> > Log Message:
> > regen after:
> > g/c sys_sa_unblockyield which has been unused since 2004/01/02
> >
> >
> > To generate a diff of this commit:
> > cvs rdiff -r1.153 -r1.154 src/sys/kern/init_sysent.c
> > cvs rdiff -r1.148 -r1.149 src/sys/kern/syscalls.c
> > cvs rdiff -r1.146 -r1.147 src/sys/sys/syscall.h
> > cvs rdiff -r1.128 -r1.129 src/sys/sys/syscallargs.h
> >
> > Please note that diffs are not public domain; they are subject to the
> > copyright notices on the relevant files.
> >
>
>
>