> However, seeing as things are maintained separately (for good
> reasons), perhaps copy-to-libkern itself should just be removed
> since it's basically pointless at this point and hasn't been
> used for about a decade.
I think that is the right direction. Then, do a seperate cleanup.
On Wed, Jun 04, 2014 at 08:02:06PM +, Miod Vallat wrote:
> > First, str{cat,cpy} were vehemently expunged from the kernel many years ago,
> > so stop trying to keep them around.
> >
> > Index: lib/libc/Makefile.inc
>
> Hello, this is libc you are butchering in. I'm afraid strcat and strcpy
>
> It seems the correct thing to do here is to put the shared part in libc,
> list the file in KSRCS in lib/libc/Makefile.inc, and make copy-to-libkern.
> This allows for only one copy to need to be maintained, and avoids hard
> build-time dependency tentacles between lib/ and sys/.
> (If this is no
Hello,
This came up when I was looking for the proper place to put code for dealing
with capsicum data structures which need to be handled by both userland and
the kernel.
FreeBSD's libc build system has tentacles that reach over and grab
sys/kern/subr_capability.c. That's not very elegant, I lik
