Re: cvs commit: src/sys/conf files options src/sys/kern init_sysent.c syscalls.c syscalls.master uipc_socket.c uipc_syscalls.c src/sys/net rtsock.c src/sys/netinet in.h in_proto.c src/sys/sys mbuf.h protosw.h socket.h syscall-args syscall-hide.h syscall.h ...

[Joerg Sonnenberger <joerg@xxxxxxxxxxxxxxxxx>]

On Fri, Jul 15, 2005 at 10:54:48AM -0700, Eirik Nygaard wrote:
> eirikn      2005/07/15 10:54:48 PDT
> 
> DragonFly src repository
> 
>   Modified files:
>     sys/conf             files options 
>     sys/kern             init_sysent.c syscalls.c syscalls.master 
>                          uipc_socket.c uipc_syscalls.c 
>     sys/net              rtsock.c 
>     sys/netinet          in.h in_proto.c 
>     sys/sys              mbuf.h protosw.h socket.h syscall-args 
>                          syscall-hide.h syscall.h syscall.mk 
>                          sysproto.h sysunion.h 
>   Log:
>   Tie SCTP into the kernel, this includes adding a new syscall (sctp_peeloff).

Is that really necessary? I find it kind of dump to have a syscall
specific for a single network protocol.

Joerg