>> ii) stating that Travis opposes to introduction of posix in his kernel >> is a mis-representation: as I perceive it, it would be better >> worded as "building the next posix clone is not his driving force". >> Some stuff will be there, some other will not. >> > >True. The only people who are really worried about posix are >those who are porting apps from eunucs. Close, but not completely true. There are a number of cases where POSIX is your friend. Like doing things with the kernel, where you can't use C++. :-) >My personal opinion was to strap crappy old posix (spelled U*N*I*X) >onto a rocket and launch it into the sun. People seemed to object >though, so rather than have a realy bad port of posix, from something >slow and spagetti like (linux), I thought it would be good to make >an *unbroken* implementation, that uses the features of BeOS >to maximize throughput. And this is exactly why I am so glad that you are on this.