March 2002 - Darwin-kernel - lists.apple.com

IPSec Question
by Guy Gardner 05 Mar '02

05 Mar '02

All, I noticed on NetBSD.org that IPsec support is built in since 1999 but you must rebuild the kernel to use it. I poked around under the kernel framework of Mac OS X and found a header file related directly to IPSec along with several other header files that are related to the way IPSec is implemented on NetBSD. Darwin is based on NetBSD so this makes sense. I know that there are plenty of people out there looking for a IPSec support for Mac OS X. At least I know I am chopping at the bit for it! I am not a Unix guru but am learning (slowly) SO I was wondering if anyone out there, that really has a good grasp of BSD networking, has rebuilt Darwin/Mac OS X with IPSec turned on in the kernel and been able to get IPSec tunneling to work? Also: I am very surprised that Apple hasn't in the last few Mac OS X refreshes turned this on and provided it to the user community? I could have used it months ago and others in the company I work for are also waiting on it too and there must be many other companies that have remote users that need this for VPN access... And: Does anyone have an idea if Apple is considering the next Mac OS X and Darwin refreshes with IPSec options built into the Kernel and providing a nice UI/Command line way to set this all up to work? Thanks, Guy Gardner Sent using the Entourage X Test Drive. _______________________________________________ darwin-kernel mailing list | darwin-kernel(a)lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/darwin-kernel Do not post admin requests to the list. They will be ignored.

1 0

updating HFS+ inode info. on open() call
by Ian Brown 05 Mar '02

05 Mar '02

I am looking for a way to update inode information whenever an open() call is made to an HFS+ file. Specifically I would like to keep a counter in the inode that counts the number of open() calls made to that file. Does anyone have any ideas on how to go about this? Regards, Ian _______________________________________________ darwin-kernel mailing list | darwin-kernel(a)lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/darwin-kernel Do not post admin requests to the list. They will be ignored.

1 0

Re: pthread issues
by Jason Evans 01 Mar '02

01 Mar '02

On Friday, March 1, 2002, at 01:11 , Mark Asbach wrote: please excuse if I send this question to the wrong list - I'm absolutely new to the Darwin project. This particular question crosses the kernel/userland boundary, so this list should be fine. darwin-userlevel might have been slightly better though. Currently I'm trying to port a realtime CORBA ORB to Mac OS X. While it compiles and runs fine on Solaris machines, I've got certain troubles with X's pthread implementation. As I was told on the student developer's list, the Darwin kernel currently doesn't support per-thread signals. So I'd tried to replace the unimplemented calls to pthread_kill() with pthread_cancel() or pthread_detach(). Both result in 'zombie' threads that are stuck in a "semaphore_wait_trap" within pthread_exit() as the gdb call chain tells me. pthread_kill() doesn't merely kill the target thread; it sends a signal. Signals in some cases are used for legacy or portability reasons to communicate among threads, so unless you understand the application you are porting well enough to be sure what it is using pthread_kill() for (and you understand the program flow to know that pthread_cancel() won't change things in a damaging way), pthread_cancel() probably won't do the job for you. pthread_detach() surely won't help by itself, since all it does is make a thread's exit state immediately reapable by the threads implementation, (as opposed to keeping it around until pthread_join() is called for the thread). Since someone also stated, that this is a known issue and already corrected in "the current builds of 10.2 (expected July or so)", I wonder, if I can replace this specific part of Mac OS X's kernel with a current build of Darwin (that hopefully got rid of this issue already) - and how to do that in detail. You could potentially get a Darwin system working with an updated xnu and Libsystem, but this isn't for the faint of heart. Unless you're already familiar with how Apple projects are built, you're in for several days of learning. As for replacing those components on an OS X 10.1 box, I wouldn' t even try it, since it is bound to break many other things. Jason _______________________________________________ darwin-kernel mailing list | darwin-kernel(a)lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/darwin-kernel Do not post admin requests to the list. They will be ignored.

1 0

pthread issues
by Mark Asbach 01 Mar '02

01 Mar '02

Hi there, please excuse if I send this question to the wrong list - I'm absolutely new to the Darwin project. Currently I'm trying to port a realtime CORBA ORB to Mac OS X. While it compiles and runs fine on Solaris machines, I've got certain troubles with X's pthread implementation. As I was told on the student developer's list, the Darwin kernel currently doesn't support per-thread signals. So I'd tried to replace the unimplemented calls to pthread_kill() with pthread_cancel() or pthread_detach(). Both result in 'zombie' threads that are stuck in a "semaphore_wait_trap" within pthread_exit() as the gdb call chain tells me. Since someone also stated, that this is a known issue and already corrected in "the current builds of 10.2 (expected July or so)", I wonder, if I can replace this specific part of Mac OS X's kernel with a current build of Darwin (that hopefully got rid of this issue already) - and how to do that in detail. Feel free to redirect my question to a more appropriate list or newsgroup. Mark _______________________________________________ darwin-kernel mailing list | darwin-kernel(a)lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/darwin-kernel Do not post admin requests to the list. They will be ignored.

1 0