May 2009 - Darwin-dev - lists.apple.com

Re: kernel source code
by Alexander von Below 28 May '09

28 May '09

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com http://opensource.apple.com/release/mac-os-x-1057/ On 28.05.2009, at 08:32, Esteban Barahona wrote: ...i have a project in mind. _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.app… hi, were and what steps do i have to follow to download the source code for the kernel of macintosh? from... someone that bought a computer that "will make a hacker proud" ^_^ _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/below%40mac.com This email sent to below(a)mac.com This email sent to site_archiver(a)lists.apple.com

1 0

Re: kernel source code
by Martin Costabel 28 May '09

28 May '09

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com User-agent: Thunderbird 2.0.0.21 (Macintosh/20090302) >From this month's list archives: <http://lists.apple.com/archives/darwin-dev/2009/May/msg00031.html> The kernel is called "xnu". -- Martin _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.app… Esteban Barahona wrote: hi, were and what steps do i have to follow to download the source code for the kernel of macintosh? This email sent to site_archiver(a)lists.apple.com

1 0

Re: kernel source code
by Philip Aker 28 May '09

28 May '09

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com On 2009-05-27, at 23:32:30, Esteban Barahona wrote: Philip Aker echo astwta@lvpc.dslh@nl | tr a-z@. p-za-o.@ Democracy: Two wolves and a sheep voting on lunch. _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.app… were and what steps do i have to follow to download the source code for the kernel of macintosh? Look over here: <http://www.opensource.apple.com/source/xnu/xnu-1228.12.14/ > to start. This email sent to site_archiver(a)lists.apple.com

1 0

Re: kernel source code
by Kevin Van Vechten 28 May '09

28 May '09

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com On May 27, 2009, at 11:32 PM, Esteban Barahona wrote: ...i have a project in mind. Good luck! Kevin _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.app… hi, were and what steps do i have to follow to download the source code for the kernel of macintosh? from... someone that bought a computer that "will make a hacker proud" ^_^ The sources are available at <http://www.opensource.apple.com/darwinsource/ >. The kernel project is named "xnu". This email sent to site_archiver(a)lists.apple.com

1 0

kernel source code
by Esteban Barahona 28 May '09

28 May '09

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=u5SglT2L/d1eW9BeJgJUTffuPX52Q2bazJZ2NSuu9IA=; b=K9HffiT7xnb4B67ee8MYgL1aWtkylw5WHTODuEYbipekMNFpvFCtn5maVJ8l4IJzyU bmNY+x2UIk8w5/uxasN7NGwfKTok5PrRgEYPWa3VNgG3OUIyudGVUlX00YcPh8ZwE1eH qRE0MerGYx3gTmCXwH+oG+rTnzIAoY1Us1VKE= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=oaqr3BrGZmbOvzHGxy1KNAw6m2GD3RyYcwxlj/tmuTtM5fotoIyK9UYcwgARMKZZod KZwvB4l0CzKET8yI/xVVmOaWatI3dmmP4Fu+7zpaf1Vul5ECmLi3YLKeh4qF86EYOuXk 85tyRNFiNRMwwRl/TruCXOoXSxbT+3gXNgK/o= _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.app… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Darwin-dev Digest, Vol 6, Issue 119
by Greg Parker 27 May '09

27 May '09

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com http://www.opengroup.org/onlinepubs/009695399/functions/pthread_rwlock_rdlo… -- Greg Parker gparker(a)apple.com Runtime Wrangler _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.app… On May 27, 2009, at 1:19 PM, Karan, Cem (Civ, ARL/CISD) wrote: Interesting. My interpretation was that one thread could hold as many DIFFERENT r/w locks at one time as it wanted (which really confused me, locks would be quite useless if you COULDN'T do so, but that is what I got out of "...for each lock obtained") "For each lock obtained" is supposed to mean "for each successful rdlock call". The POSIX description is more explicit: "A thread may hold multiple concurrent read locks on rwlock (that is, successfully call the pthread_rwlock_rdlock() function n times). If so, the thread must perform matching unlocks (that is, it must call the pthread_rwlock_unlock() function n times)." Reading the code makes it much clearer though; thank you! I did one other stupid test; I locked for reading and then tried to lock for writing. I seem to have deadlocked without an error on that one. Unless that is considered normal behavior, once I confirm that it isn't a problem with my test code, I'll file a bug about it. pthread deadlock detection is optional in the standard. Even something as simple as two consecutive pthread_mutex_lock() calls will hang instead of returning EDEADLK. (And given the amount of code in the world that fails to check the return value, that's probably a good thing.) This email sent to site_archiver(a)lists.apple.com

1 0

RE: Darwin-dev Digest, Vol 6, Issue 119
by Karan, Cem (Civ, ARL/CISD) 27 May '09

27 May '09

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com Thread-index: Acne/e/vbH8T/KPBT8iNEM7nW/ztawABn+KA Thread-topic: Darwin-dev Digest, Vol 6, Issue 119 On Wed, 27 May 2009 13:57:50 -0400, Gwynne Raskind wrote: <<SNIP>> > > From the pthread_rwlock_rdlock(3) manpage: > > A thread may hold multiple concurrent read locks. If so, > pthread_rwlock_unlock() must be called once for each lock obtained. > > And further: > > [EDEADLK] The current thread already owns rwlock for > writing. > > My interpretation of this is that you can hold as many read > locks as you like, recursively, and that EDEADLK will only > show up when you try to take a write lock when you already > have a read lock. > > The manpage names itself as being BSD, not Darwin, so I would > imagine (but not know!) that this is a characteristic of at > least one of the flavors of BSD that Darwin derives from. > > Finally, having a look at the source code for pthread_rwlock_rdlock() > at: > http://www.opensource.apple.com/source/Libc/Libc-498.1.7/pthre > ads/pthread_rwlock.c > > I see that EDEADLK will only be returned if the lock is held > for writing by the current thread. > > -- Gwynne, Daughter of the Code > "This whole world is an asylum for the incurable." Interesting. My interpretation was that one thread could hold as many DIFFERENT r/w locks at one time as it wanted (which really confused me, locks would be quite useless if you COULDN'T do so, but that is what I got out of "...for each lock obtained") Reading the code makes it much clearer though; thank you! I did one other stupid test; I locked for reading and then tried to lock for writing. I seem to have deadlocked without an error on that one. Unless that is considered normal behavior, once I confirm that it isn't a problem with my test code, I'll file a bug about it. Thanks, Cem Karan _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.app… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Why isn't pthread_rwlock_rdlock() deadlocking???
by Gwynne Raskind 27 May '09

27 May '09

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com pthread_rwlock_t lock; pthread_rwlock_init(&lock, NULL); pthread_rwlock_rdlock(&lock); pthread_rwlock_rdlock(&lock); // No EDEADLK???? // ignoring the destructor code >From the pthread_rwlock_rdlock(3) manpage: And further: -- Gwynne, Daughter of the Code "This whole world is an asylum for the incurable." _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.app… On May 27, 2009, at 1:43 PM, Karan, Cem (Civ, ARL/CISD) wrote: I've been busy writing unit tests for an Objective-C wrapper of mine that wraps pthread read/write locks. One of my unit tests should fail with EDEADLK, but I never have that happen. My test code essentially boils down to the following, all of which is run from one thread only: My understanding of read/write locks is that they are NOT recursive. Am I wrong? Or is this special to Darwin? A thread may hold multiple concurrent read locks. If so, pthread_rwlock_unlock() must be called once for each lock obtained. [EDEADLK] The current thread already owns rwlock for writing. My interpretation of this is that you can hold as many read locks as you like, recursively, and that EDEADLK will only show up when you try to take a write lock when you already have a read lock. The manpage names itself as being BSD, not Darwin, so I would imagine (but not know!) that this is a characteristic of at least one of the flavors of BSD that Darwin derives from. Finally, having a look at the source code for pthread_rwlock_rdlock() at: http://www.opensource.apple.com/source/Libc/Libc-498.1.7/pthreads/pthread_r… I see that EDEADLK will only be returned if the lock is held for writing by the current thread. This email sent to site_archiver(a)lists.apple.com

1 0

Why isn't pthread_rwlock_rdlock() deadlocking???
by Karan, Cem (Civ, ARL/CISD) 27 May '09

27 May '09

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com Thread-index: Acne8qgTfOoVJIH1Ru2tUk4zfhUL5g== Thread-topic: Why isn't pthread_rwlock_rdlock() deadlocking??? I've been busy writing unit tests for an Objective-C wrapper of mine that wraps pthread read/write locks. One of my unit tests should fail with EDEADLK, but I never have that happen. My test code essentially boils down to the following, all of which is run from one thread only: pthread_rwlock_t lock; pthread_rwlock_init(&lock, NULL); pthread_rwlock_rdlock(&lock); pthread_rwlock_rdlock(&lock); // No EDEADLK???? // ignoring the destructor code My understanding of read/write locks is that they are NOT recursive. Am I wrong? Or is this special to Darwin? Thanks, Cem Karan _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.app… This email sent to site_archiver(a)lists.apple.com

1 0

Re: xinetd and launchd in Mac OS X 10.5
by Damien Sorresso 27 May '09

27 May '09

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com Hello, My backup/restore application is supposed to run on Mac OS X 10.4 and 10.5. I need the xinetd startup script. But with 10.4 launchd is been used. However, 10.4 also supports xinetd. Does 10.5 also provide xinetd _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.app… This email sent to site_archiver(a)lists.apple.com On May 27, 2009, at 3:14 AM, rohan a wrote: Which is the default startup script : xinetd or launchd ? launchd. All rc scripts are deprecated and support for them may be removed in future releases. -- Damien Sorresso BSD Engineering Apple Inc. smime.p7s

1 0