Re: Pthread assumption + starting real port

[Farid Hajji]

gernot> We've been through that too. We looked at porting glibc and decided
gernot> that there's too much Unix in there. We tried OSkit, which looked
gernot> promising at first, but turned out a nightmare on non-Intel
gernot> (particularly 64-bit) systems. That was a painful and expensive
gernot> experience, we ended up dumping a lot of work.
That's really good to know! Thanks for the hint.

gernot> We're now working on our own libc. SawMill is doing something similar,
gernot> and we hope to merge/share code. Doing a complete libc which is as
gernot> independent from the underlying OS as possible (obviously parts are
gernot> inherently tied to the OS) would be beneficial for lots of people.
Indeed, that's absolutely true. It would be wonderful to use a truly
portable libc in this case. This is yet another reason to avoid as much
glibc specialities in the new Hurd as possible. Let us restrict ourselves
to what POSIX specifies (without the Unix dependencies?) in the Hurd,
and we'll get a system that (hopefully) compiles everywhere.

How do you plan to add support for underlying kernels (be they Unix or
ukernels)? Through hooks?

Thanks,

-Farid.

-- 
Farid Hajji -- Unix Systems and Network Admin | Phone: +49-2131-67-555
Broicherdorfstr. 83, D-41564 Kaarst, Germany  | address@hidden
- - - - - - - - - - - - - - - - - - - - - - - + - - - - - - - - - - - -
Murphy's Law fails only when you try to demonstrate it, and thus succeeds.