Re: Function conflicts between kernel and libc

["Simon 'corecode' Schubert" <corecode@xxxxxxxxxxxx>]

Matthew Dillon wrote:
> :
> :This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
> :--------------enig27D47D72C34079BE1F6C35CA
> :Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> :Content-Transfer-Encoding: 7bit
> :
> :Matthew Dillon wrote:
> :>     There are a number of function and type conflicts between the kernel
> :>     and libc that I need to deal with.  My current plan is as follows:
> :
> :I keep wondering if there isn't a cleaner way to separate namespaces.
>
>     So do I.  But I want to use as few code tricks as possible.  Renaming
>     is the cleanest solution but even I can't justify renaming simple
>     string functions.

maybe we should not link libc at all?  or at least use a linker script which removes all functions from libc (won't work possibly).

i mean, what do we need from libc?

- write (syscall)
- read (syscall)
- open (syscall)
- mmap (syscall) to get pages/memory
- new VM syscalls
- maybe ioctl (syscall)

apart from that, the kernel is self-hosting anyways.  maybe it will be less effort to not use libc functions that to rename all overlaps.  actually, i'm sure about that.

cheers
 simon

--
Serve - BSD     +++  RENT this banner advert  +++    ASCII Ribbon   /"\
Work - Mac      +++  space for low €€€ NOW!1  +++      Campaign     \ /
Party Enjoy Relax   |   http://dragonflybsd.org      Against  HTML   \
Dude 2c 2 the max   !   http://golden-apple.biz       Mail + News   / \

Attachment: signature.asc
Description: OpenPGP digital signature