Date: Mon, 17 Mar 2008 21:07:09 +0100 From: Kris Kennaway <kris@FreeBSD.org> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: Jordan Gordeev <jgordeev@dir.bg>, freebsd-hackers@FreeBSD.org Subject: Re: vkernel & GSoC, some questions Message-ID: <47DECF6D.9010806@FreeBSD.org> In-Reply-To: <200803171838.m2HIcCii019146@apollo.backplane.com> References: <47DBC800.8030601@dir.bg> <47DD1FFF.6070004@FreeBSD.org> <200803170043.m2H0h2qO010175@apollo.backplane.com> <47DDCCC3.3020408@FreeBSD.org> <200803171838.m2HIcCii019146@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Matthew Dillon wrote: > :> Well, I don't think I would agree with your assessment but, > :> particularly, the way vkernels are implemented in DragonFly is NOT > :> in the least disruptive to kernel source. > : > :I was referring to the decision you made to rename all of the kernel > :functions that conflicted with libc functions so that vkernels could be > :linked against libc. > : > :Kris > > Huh. Well, that's about the last thing I would have thought would be > considered disruptive to the kernel source. I don't think there's an issue that needs solving, GCC has -nostdlib and -fno-builtin for precisely this reason. Anyway, I agree that this is the least of someone's worries during a hypothetical port of the dragonfly vkernel code. Just so everyone is clear, the scope of such an effort would not be "port the code", it would be "port the code and also finish it". Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47DECF6D.9010806>