[openbeos] Re: Kernel status (POSIX)

> 
> For a lot of stuff you need kernel support (or at least support
> from some module living in kernel space). A pure POSIX
> implementation in userland is next to undoable... tell me,
> for instance, how do you plan to implement fork() in userland.
> 

void *pitch_fork( /* some parameters */)
{
/*
use some standard beos functions like....
*/
create_area();
clone_area();
delete_area();

/*
to share data
*/

/*
and standard beos functions like....
*/
load_image();

/*
to create new teams; essentially the same as forking
if the process your spawning is identical to the current process 
*/

etc....();

return /* a void pointer that the fork function can use */ ;;
/*
 posix is gonna get scewered....bet on it...
*/
}


> 
> > I drew *a-lot* of flak for that. Especially from linux/eunucs people.
> 
> The "eunucs" part is totally uncalled for.

Sensitive? he he....
It's and OS not a religon. I've been using UNIX
since 1982. I think it's safe to say I understand
some of its failings. Enough to be allowed to 
make fun of it anyway.

> 
> That's a pathetically passive attitude... why don't you peek
> at the perforce server instead?
> 

Hey, I offered to code other stuff and people gave me POSIX.
I'm not in charge here. I'm doing what I was told to do and will
continue to do so.
I'm just curious about the status.
Wasn't Mike Phipps organizing these things? 
I know he *doesn't* want to be in charge, but he knows
what's up.

Peter

Other related posts: