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

Re: Reading system framework information through Stabs file ?
by Jean-Daniel Dupas 18 Aug '09

18 Aug '09

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com _______________________________________________ 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: Reading system framework information through Stabs file ?
by Arnab Ganguly 18 Aug '09

18 Aug '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:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=6Q8qUNCYxMUQ2bgGse9ynAA2xffruLQuprQ9dEUQ6sg=; b=wIzKERvBleCvjo1BnD5ZZAresPrgQZpLd+t17FHjC9cugIllGsmWGkM7a3XppMxR0z a7dDIguIuQ3vu5g2AUQC8aK45ucdAHgjiWCL70zDczK2qseDX1HwhCOtDVTeNW8q9t4t BWwwHty4SxSgVHx4UgbGRdTETT74lbIBPRZz4= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=prD/xN1JfZtXOMG1FnxVixN9U26+Pa1niLSvVitJ174t+zJ+o/yaQpkynJmj6jPxHN WEj7kyMQ5YKylx8vzB+15WUScN7/TALK4OcKRFDC/J8fplK39Bhd8qW9BpVS7DIcLgQv PQ1p12fXvDF7IjQF/KdLxg6YVEf1853Xqi+Gs= _______________________________________________ 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

Reading system framework information through Stabs file ?
by Arnab Ganguly 18 Aug '09

18 Aug '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=vXmcWoQof9eue77qQF6h9+H5gmdWxTWxTgmxPUceeXA=; b=Z+TTsQY6AXGd/NB3UXbWuEXcgHKZJgCgNIkJHVBE34fLppOBnwQ2irKp9UGBCQ8qIL FyS2Mb9eQFN4trXSimGYzUEwDErKJL7rRFizYsSNw5qe/qhgMcqgSXpgIiF553pZy2pt QDDEiZbEzDjWNxTft8HJIzzvoEdtOQCqRRFqc= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=xwLo/XZIaavikWzzPpTeuyKeJxM1tY/IGFkSOvRUV1h43Z341mxnttxZWoQpyMEuwa 2psPoBrDfzSYPmYeE/hsZrunWMLphGM70gni1JR/eUoek0fePelsSz9rkMWd2WRpaIvi O1oBlcdSM+n5HHvZxY7WQ9efJpLz0ZhYyxtK4= _______________________________________________ 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

looking for System APIs for load monitoring
by Marc Lohse 18 Aug '09

18 Aug '09

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com Thread-index: Acof1c/nC81uz0JR2EmfTCT4HHe//A== Thread-topic: looking for System APIs for load monitoring I am developing an application that needs to monitor the system's CPU and IO load while it's running to be able to identify a low system load and only do it's resource-hungry work while the system is not busy doing other things. I've been searching for the low-level system API that would give me access to this kind of information but i have not yet found exactly what i need - functions like host_processor_info supply the overall CPU usage which is nice, but i need to know the CPU usage of each individual process. The kind of information i need is essentially what's supplied by the ps -axv command. But i don't want to solve my problem by calling ps as an external task - i am sure there is a more elegant way to get the info directly. Could anybody help me by pointing me to some source of documentation (maybe i am stupid or looking in the wrong place but i did not find the info in the documentation supplied with Xcode) and/or maybe some code examples. thanks a lot _______________________________________________ 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: Trials and Tribulations building DirectoryService
by Stephen J. Butler 17 Aug '09

17 Aug '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:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=F1xvc0BtzVFnyqadVQ726xU0CjGA1d/bfJnJKnq7CcE=; b=PZTcaADnZH7LuMafX9EFR5jrsbL3RJ0J0PoMUN6JsCI9iYS44d4bfn9r8SfORfMxud rKE1GaIP6JtzZ167I4SW9smv6VTkCARmlPpUA6Df6ZuvULTX60IiNEJ+jENaL/R0h7Gx mIxZjO/IWZrWhzFXUcnykiERDofq/GpT0nQwg= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=YhmqmOawEar9FzUNaCUdeGsqbLYsEY+E5tsBTL3yL6dikYBTuOSBfKMs2pWfbNoix9 WZC4T8dVN1ymOsocNtlhcrqGfauS9fP7i7w3tTe9R56ajFSPbPu9MMRkXSH1rn3MtCkv O4RITdkCZzmVYotQDc8tt2AHmbN06LImxVbTk= On Mon, Aug 17, 2009 at 3:05 PM, William Siegrist<wsiegrist(a)apple.com> wrote: > On Aug 17, 2009, at 12:22 PM, Stephen J. Butler wrote: >> What is /XCD/SY/Library/PrivateFrameworks, and why isn't it looking in >> /System/Library/PrivateFrameworks? > > It is where darwinbuild puts Xcode inside the chroot. The fact that builds > have their include paths rewritten to /XCD is a bug in darwinbuild. I don't > have a workaround for this problem other than to use "-nochroot" which will > skip the chroot and installation of Xcode. I think I managed to tweak around this. I opened up the Xcode project and added /System/Library/Frameworks and /System/Library/PrivateFrameworks to the frameworks list. I've kind of succeeded in building this beast, but I had to do some things I'm not proud of: - move aside the darwinbuild CoreFoundation.framework - copy CoreFoundation.framework from my system. - copy the PrivateHeaders from darwinbuild's CoreFoundation.framework into the one I copied from my system - Define HAVE_CORE_SERVER=0 in the Xcode project - Remove libXSEventPort.a from the libraries list. Speaking of which... does anyone know what XSEventPort.h/libXSEventPort are? I can't find any reference to them on the internet. All this to change three lines in the LDAP plugin. _______________________________________________ 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: Trials and Tribulations building DirectoryService
by William Siegrist 17 Aug '09

17 Aug '09

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com On Aug 17, 2009, at 12:22 PM, Stephen J. Butler wrote: What is /XCD/SY/Library/PrivateFrameworks, and why isn't it looking in /System/Library/PrivateFrameworks? -Bill _______________________________________________ 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… It is where darwinbuild puts Xcode inside the chroot. The fact that builds have their include paths rewritten to /XCD is a bug in darwinbuild. I don't have a workaround for this problem other than to use "-nochroot" which will skip the chroot and installation of Xcode. This email sent to site_archiver(a)lists.apple.com

1 0

Trials and Tribulations building DirectoryService
by Stephen J. Butler 17 Aug '09

17 Aug '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:content-transfer-encoding; bh=wChT1rEGPI1alCAM0kWEbClUn8WIN7f/Bpp7T4SH6y8=; b=WvgVi3wsYWseiee/TkNdNKWAiOAVw/lsXBAWVm0BwZ0dnrvJ/5zxuehDDqxGF7YrUV UUXDB1f4c6dwyHHl3m3pMo8ZRHVM7exueQFe0zEu2e3bwBNPYMXiux7EGmJjeEsZSIfM CmgYC4e0Kzg0X86YcK7Uluqv4FwFI0mqqD/vE= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=DyBYWdgRCLdAlSA/FGtxqaYneapW7XR+o3OFaXMT7zJC1hrvNrF+ycUxyFh6kxn8gW 5+O/itXQH8ML0Ug2sxa1Wexo24hfg9MqdgrHhdEI30YUoGM8wCJuJg3KbhGWHNc6j9mJ o2D3rwdmFnKsLUMcOHpbTY6DSjCq3S3OIm/wU= I've spent way too many hours this weekend trying to build the Server target of DirectoryService for 10.5.8. My latest problem, which I don't quite know how to work around, is this: In file included from /SourceCache/DirectoryService/DirectoryService-514.25/PlugIns/Common/BaseDirectoryPlugin.h:41, from /SourceCache/DirectoryService/DirectoryService-514.25/PlugIns/Local/CDSLocalPlugin.h:38, from /SourceCache/DirectoryService/DirectoryService-514.25/Server/CServerPlugin.cpp:37: /SourceCache/DirectoryService/DirectoryService-514.25/PlugIns/Common/CDSAuthParams.h:28:37: error: PasswordServer/AuthFile.h: No such file or directory /SourceCache/DirectoryService/DirectoryService-514.25/PlugIns/Common/CDSAuthParams.h:92: error: 'PWGlobalAccessFeatures' does not name a type /SourceCache/DirectoryService/DirectoryService-514.25/PlugIns/Common/CDSAuthParams.h:93: error: 'PWGlobalMoreAccessFeatures' does not name a type ** BUILD FAILED ** Doing darwinxref findFile AuthFile.h nicely returns: DSPasswordServerFramework: /System/Library/PrivateFrameworks/PasswordServer.framework/Versions/A/Headers/AuthFile.h But looking at the Compiler line, the problem becomes apparent: /XCD/loper/usr/bin/gcc-4.0 -x c++ -arch ppc -fmessage-length=0 -pipe -Wno-trigraphs -fpascal-strings \ -fasm-blocks -Os -mdynamic-no-pic -DDSSERVERTCP -DSERVERINTERNAL -D__MigTypeCheck=1 \ -DHAVE_CORE_SERVER=1 -mtune=G4 -fvisibility-inlines-hidden -mmacosx-version-min=10.5 \ -gdwarf-2 \ -I/private/var/tmp/DirectoryService/DirectoryService-514.25.obj/DirectoryService.build/Server.build/DirectoryService.hmap \ -Wmost -Wno-four-char-constants -Wno-unknown-pragmas \ -F/private/var/tmp/DirectoryService/DirectoryService-514.25.sym/BuiltProducts \ -F/XCD/SY/Library/PrivateFrameworks \ -F/SourceCache/DirectoryService/DirectoryService-514.25/build/Development \ -I/private/var/tmp/DirectoryService/DirectoryService-514.25.obj \ -I/private/var/tmp/DirectoryService/DirectoryService-514.25.sym/BuiltProducts/include \ -I/XCD/SY/Library/PrivateFrameworks/CoreServer.framework/Versions/A/Headers \ -I/XCD/SY/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/Headers \ -I/AppleInternal/XCD/loper/Headers/sasl \ -I/private/var/tmp/DirectoryService/DirectoryService-514.25.obj/DirectoryService.build/Server.build/DerivedSources/ppc \ -I/private/var/tmp/DirectoryService/DirectoryService-514.25.obj/DirectoryService.build/Server.build/DerivedSources \ -fconstant-cfstrings -DHAVE_CORE_SERVER=1 \ -c /SourceCache/DirectoryService/DirectoryService-514.25/Server/CServerPlugin.cpp \ -o /private/var/tmp/DirectoryService/DirectoryService-514.25.obj/DirectoryService.build/Server.build/Objects-normal/ppc/CServerPlugin.o What is /XCD/SY/Library/PrivateFrameworks, and why isn't it looking in /System/Library/PrivateFrameworks? _______________________________________________ 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: Sending SCSI commands in Mac OS X
by rohan a 17 Aug '09

17 Aug '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:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=pjwwlIBE6oyvu2/jQOWP7T4neJRPxP2HSdksci9M1Mc=; b=huBWJBsqMEgBs+R+1lij3/XbaINZRkdwG1ViATQrJKBU49prTxw4GXvBGD09KvUWBP bB6Vspy85ZftwyzAbFW1Loz7+A1Kn1TpQKsfXToIkw7p7z8K0JMWQ7P0JZUqzhMIBNec Mj++LSZvszzHvj2KlqtwDVNOuVoqAkycMLFW8= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=gEYklj8LNA0NjDfpe/EEl1Y8rRXEFg/QZIFzq3Vh5wyV4GjgM49GXnJzHmYMqpkW5r AkE+bW7oySJYWyw90MgkAXf3GB/pPk++LesLwQZ/2W5T9e3BNSFtzvi1hr80UgE3o3OC EETa3rSK3RoVftuhXSmFWWT5j295hJc6ZeST0= Hi, Thanks a lot for the help. I am now able to send SCSI commands to the drive (vendor specific too). However, for sending a SCSI command I need to pass the interface address. Something like, SCSITaskDeviceInterface ** interface = NULL; Inquiry ( interface ); EnableEncryption ( interface ); Here the interface is just a pointer and will change frequently. If I scan the devices every time and then send commands to each device it would work fine. But what if I need to send commands to a particular device only and this too without having to re-scan all devices ? I cant just store and use "interface" as it would have changed in the meantime and might be pointing to some other device. What should I be doing here ? On Fri, Jul 31, 2009 at 5:23 PM, rohan a<info1686(a)gmail.com> wrote: > Hi, > WorkingwithSAM.pdf also states that: > > $00 for block storage devices that comply with the SCSI block commands > specification > $05 for multimedia devices that comply with the SCSI multimedia > commands specification > $07 for magneto-optical devices that comply with the SCSI block > commands specification > $0E for reduced block command devices that comply with the SCSI > reduced block commands specification > > Now how do I check if a device falls in a particular category. Is > there anyway I know that a device is $00,05,07 or 0E ? > > Also, > I see that SCSI commands require SCSITaskDeviceInterface **interface > ex: void Inquiry(SCSITaskDeviceInterface **interface) > > On looking further I see this: > interface = ( *mmcInterface )->GetSCSITaskDeviceInterface ( mmcInterface ); > But this is only for MMCDevice Interface. > What about SCSI devices? > > Thanks > > > > > > On 7/24/09, mlists(a)ugsoft.de <mlists(a)ugsoft.de> wrote: >> >> Am 24.07.2009 um 05:55 schrieb Terry Lambert: >> >> > Since no one else posted... >> > >> > Apparently the last machine I used had your tools installed on, which >> generated BSD device stubs for my QIC tape drive when I plugged it it. 8-). >> > >> >> Ok. What we are doing with our tools is to create pseudo device files in >> /etc/UGSdev, e.g. /etc/UGSdev/nst0, which can be passed as remote devices >> (e.g. 127.0.0.1:/etc/UGSdev/nst0) to command line tools such as tar, xtar, >> dump/restore, mt, etc., so that our rmt will communicate with the SCSI, >> FireWire, USB and FibreChannel tape/changer devices. Please take a look at >> http://www.ugsoft.de/intl/faq.html#xtarntape for more >> information on that. >> >> For those who are interested: >> The tools esbdump, esbrestore, esbmt, rmt and the smtc tape device "driver" >> are free to use and are included in ES-Backup >> http://www.ugsoft.de/intl/esbackup . No registration nor >> activation keys required to use the shell commands. See included License >> document. Since no source code is included one won't be able to learn how to >> do the SCSI programming on OS X, though. In addition to the functionality of >> the corresponding Unix tools such as the standard dump tape format, our >> tools offer support for Mac OS X file attributes, resource forks, etc., as >> well as direct tape positioning during restore which make them usefull for >> today's large amounts of backup data. Also, these tools are used in our >> commercial product ES-Backup on Mac OS X Intel and PPC, Solaris SPARC and >> x86, Linux x86 - but this is off-topic. >> >> >> > >> > The officially supported interface is SCSITaskDeviceInterface, from a user >> client. Sorry for the confusion. >> > >> >> I thought I've missed something ;-) >> >> Uwe >> >> >> > >> > Rohan: This means "no, you can not use an ioctl". >> > >> > -- Terry >> > >> > On Jul 23, 2009, at 7:04 AM, mlists(a)ugsoft.de wrote: >> > >> > > Am 23.07.2009 um 13:26 schrieb Terry Lambert: >> > > >> > > > Did you go to <http://developer.apple.com> and read the document "SCSI >> Architecture Model Device Interface Guide"? >> > > > >> > > > It states: >> > > > >> > > > "By design, Mac OS X does not allow applications to send SCSI or ATA >> commands to storage devices unless the application developer also provides >> an in-kernel device driver that supports the commands." >> > > > >> > > > One of the intents if this is to allow the driver to model state for >> such coomands such that the state if the device is known to the driver at >> all times. >> > > > >> > > > For standard tape devices, you should not need to write your own >> driver; if you plug the device in, it will show up in /dev, >> > > > >> > > >> > > Never seen a tape drive, neither SCSI, FireWire, USB nor FibreChannel >> connected to Mac OS X 10.2 up to 10.5 which shows up in /dev. What device >> filename should I look for? >> > > >> > > >> > > > and you can at least issue reads, writes, and standard commands, such >> as causing a rewind, via the device file. For non-standard commands, such as >> you would use to control loading and unloading tapes in a tape robot, etc., >> you will need to write an in-kernel driver that knows how to talk to the >> hardware and subclasses the more generic device (i.e. the IOKit model lets >> you write only the missing pieces implementing the missing control commands; >> you don't write a whole driver that implements read/write/etc.). >> > > > >> > > >> > > Instead we use SCSITaskDeviceInterface functions from userland as >> described in Apple's SCSI Architecture Model Device Interface Guide >> "WorkingWithSAM.pdf" in order to implement a "SCSI pass-thru" functionality. >> No additional driver required. >> > > >> > > >> > > Uwe >> > > >> > > >> > > >> > >> > >> >> > > > On 7/24/09, mlists(a)ugsoft.de <mlists(a)ugsoft.de> wrote: >> >> Am 24.07.2009 um 05:55 schrieb Terry Lambert: >> >> > Since no one else posted... >> > >> > Apparently the last machine I used had your tools installed on, which >> generated BSD device stubs for my QIC tape drive when I plugged it it. 8-). >> > >> >> Ok. What we are doing with our tools is to create pseudo device files in >> /etc/UGSdev, e.g. /etc/UGSdev/nst0, which can be passed as remote devices >> (e.g. 127.0.0.1:/etc/UGSdev/nst0) to command line tools such as tar, xtar, >> dump/restore, mt, etc., so that our rmt will communicate with the SCSI, >> FireWire, USB and FibreChannel tape/changer devices. Please take a look at >> http://www.ugsoft.de/intl/faq.html#xtarntape for more >> information on that. >> >> For those who are interested: >> The tools esbdump, esbrestore, esbmt, rmt and the smtc tape device "driver" >> are free to use and are included in ES-Backup >> http://www.ugsoft.de/intl/esbackup . No registration nor >> activation keys required to use the shell commands. See included License >> document. Since no source code is included one won't be able to learn how to >> do the SCSI programming on OS X, though. In addition to the functionality of >> the corresponding Unix tools such as the standard dump tape format, our >> tools offer support for Mac OS X file attributes, resource forks, etc., as >> well as direct tape positioning during restore which make them usefull for >> today's large amounts of backup data. Also, these tools are used in our >> commercial product ES-Backup on Mac OS X Intel and PPC, Solaris SPARC and >> x86, Linux x86 - but this is off-topic. >> >> >> > >> > The officially supported interface is SCSITaskDeviceInterface, from a user >> client. Sorry for the confusion. >> > >> >> I thought I've missed something ;-) >> >> Uwe >> >> >> > >> > Rohan: This means "no, you can not use an ioctl". >> > >> > -- Terry >> > >> > On Jul 23, 2009, at 7:04 AM, mlists(a)ugsoft.de wrote: >> > >> > > Am 23.07.2009 um 13:26 schrieb Terry Lambert: >> > > >> > > > Did you go to <http://developer.apple.com> and read the document "SCSI >> Architecture Model Device Interface Guide"? >> > > > >> > > > It states: >> > > > >> > > > "By design, Mac OS X does not allow applications to send SCSI or ATA >> commands to storage devices unless the application developer also provides >> an in-kernel device driver that supports the commands." >> > > > >> > > > One of the intents if this is to allow the driver to model state for >> such coomands such that the state if the device is known to the driver at >> all times. >> > > > >> > > > For standard tape devices, you should not need to write your own >> driver; if you plug the device in, it will show up in /dev, >> > > > >> > > >> > > Never seen a tape drive, neither SCSI, FireWire, USB nor FibreChannel >> connected to Mac OS X 10.2 up to 10.5 which shows up in /dev. What device >> filename should I look for? >> > > >> > > >> > > > and you can at least issue reads, writes, and standard commands, such >> as causing a rewind, via the device file. For non-standard commands, such as >> you would use to control loading and unloading tapes in a tape robot, etc., >> you will need to write an in-kernel driver that knows how to talk to the >> hardware and subclasses the more generic device (i.e. the IOKit model lets >> you write only the missing pieces implementing the missing control commands; >> you don't write a whole driver that implements read/write/etc.). >> > > > >> > > >> > > Instead we use SCSITaskDeviceInterface functions from userland as >> described in Apple's SCSI Architecture Model Device Interface Guide >> "WorkingWithSAM.pdf" in order to implement a "SCSI pass-thru" functionality. >> No additional driver required. >> > > >> > > >> > > Uwe >> > > >> > > >> > > >> > >> > >> >> > _______________________________________________ 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: dns_lookup returns NULL?
by Mike Patnode 13 Aug '09

13 Aug '09

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com Thread-index: AcoazllPocDftQ4OTxOzTzP6XW+EdwBat/0w Thread-topic: dns_lookup returns NULL? Thanks for all the responses. It turns out the problem was pilot error with resolv.conf having a non-symmetrical DNS server listed. mDNSResponder had switched to the second DNS server in the list, which was a valid DNS server, it just couldn't answer the questions we were asking it. This is such a common misunderstanding among sysadmins, that we even ship a test utility that insures all the servers listed in resolv.conf are replicas. Of course, the person running the utility has to believe the warning... :) mp -----Original Message----- From: darwin-dev-bounces+mike.patnode=centrify.com(a)lists.apple.com [mailto:darwin-dev-bounces+mike.patnode=centrify.com@lists.apple.com] On Behalf Of Josh Graessley Sent: Tuesday, August 11, 2009 2:55 PM To: Paul Kwan Cc: darwin-dev(a)lists.apple.com; appledev Subject: Re: dns_lookup returns NULL? There are a few more steps you can take to try and narrow down the cause of the problem. dns-sd talks directly to mDNSResponder so you can check to see if that is working: dns-sd -G v4 www.google.com If that's failing, there may be clues in mDNSResponders state. You can dump that state using: sudo killall -INFO mDNSResponder That will dump the state to the system log. Potentially useful is: scutil --dns That will dump the global DNS settings. mDNSResponder should be using those DNS settings. -josh On Aug 11, 2009, at 2:46 PM, Paul Kwan wrote: > In our test environment where it happens, there are no configd core > dumps in > /cores folder or crash reports in /Library/Logs/CrashReporter and > /Library/Logs/DiagnosticReports folders. > > PSK > > > On 8/11/09 2:37 PM, "Josh Graessley" <jgraessley(a)apple.com> wrote: > >> >> I believe the most common cause of this failure is a configd crash >> (usually in one of the plug-ins). If configd crashes, other parts of >> the system are unaware that they will no longer receive notification >> of network changes. mDNSResponder loses DNS settings. >> >> -josh >> >> On Aug 11, 2009, at 2:32 PM, Marc Majka wrote: >> >>> On 10.6, DNS queries are sent to mDNSResponder rather than to >>> DirectoryService as they were on 10.5. If you can reproduce the >>> problem, you may be able to collect some useful debugging output >>> from mDNSResponder. See the mDNSResponder man page for info on >>> getting debug log info. If you can get some data, please file a bug >>> report. >>> >>> You are correct: dig, nslookup, and host all use bare-bones network >>> routines from BIND. The follow a very different code path than >>> mDNSResponder. >>> >>> -- Marc >>> >>> On 11 Aug, 2009, at 14:17, Mike Patnode wrote: >>> >>>> I'll buy that. Any idea why on 10.6 it would suddenly start >>>> returning >>>> NULL for all lookups and continue to do so until a reboot? Tried >>>> restarting DS as well to no avail but a reboot seems to solve the >>>> problem once the system gets in that state. Where should I start >>>> looking for debug info? >>>> >>>> Note that dig and nslookup work fine, but I suspect they don't use >>>> this >>>> API. >>>> >>>> mp >>>> >>>> >>>> Date: Mon, 10 Aug 2009 15:25:55 -0700 >>>> From: Marc Majka <majka(a)apple.com> >>>> Subject: Re: dns_lookup returns NULL? >>>> To: appledev <appledev(a)centrify.com> >>>> Cc: darwin-dev(a)lists.apple.com >>>> Message-ID: <EB755AEA-2B4B-4D95-B453-4E538C1E6EC2(a)apple.com> >>>> Content-Type: text/plain; charset="us-ascii" >>>> >>>> The "status" field of the dns_reply_t structure is currently unused >>>> (it's always zero). There's really not a lot of useful error >>>> information that could be returned by this level of API. >>>> dns_lookup >>>> () >>>> may do multiple queries to multiple DNS clients (see the resolver >>>> (5) man >>>> page). If none of the resolvers returned useful data for the >>>> query, >>>> dns_lookup() returns NULL. A failure like NXDomain from a >>>> particular >>>> nameserver really doesn't mean much if dns_lookup() is searching >>>> multiple sources. >>>> >>>> The situation is similar to an API like, say, getpwnam(). The >>>> DirectoryService daemon might search many different information >>>> sources >>>> to answer a getpwnam() query. If it finds data, it returns it. It >>>> really doesn't mean a lot if, as part of it's search, it got an >>>> error >>>> from an LDAP or NIS server, or if it checked /etc/passwd and failed >>>> to >>>> find a particular user. A reply is really a composite of all of >>>> the >>>> sub-searchs performed to answer a query. A NULL reply means they >>>> all >>>> "failed" in some way, but the API abstracts away the return codes >>>> for >>>> the various sub-systems. >>>> >>>> -- >>>> Marc Majka >>>> >>>> >>>> On 10 Aug, 2009, at 14:37, Mike Patnode wrote: >>>> >>>>> Is there anyway to get error information when dns_lookup() returns >>>>> NULL? It looks like the error code is supposed to be returned in >>>>> the dns_reply_t structure. What does it mean when the return >>>>> value >>>>> is NULL? >>>>> >>>>> thx >>>>> mp >>>>> _______________________________________________ >>>>> 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/majka >>>>> %40apple.com >>>>> >>>>> This email sent to majka(a)apple.com >>>> >>>> _______________________________________________ >>>> 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/majka%40apple.com >>>> >>>> This email sent to majka(a)apple.com >>> >>> _______________________________________________ >>> 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/jgraessley%40apple.com >>> >>> This email sent to jgraessley(a)apple.com >> > _______________________________________________ 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/mike.patnode%40centrif y.com This email sent to mike.patnode(a)centrify.com _______________________________________________ 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: ucontext.h changes between 10.4 and 10.5?
by Rick Mann 13 Aug '09

13 Aug '09

site_archiver(a)lists.apple.com Delivered-To: darwin-dev(a)lists.apple.com Thanks! On Aug 12, 2009, at 17:49:17, Terry Lambert wrote: ... HAL_SavedRegisters regs; regs.edi = SIGCONTEXT_MEMBER( context, edi ); regs.esi = SIGCONTEXT_MEMBER( context, esi ); ...etc... } #include <stdio.h> #include <ucontext.h> /* A small program that proves we actually accessed them */ int main(int ac, char *av[]) { #if __LP64 unsigned long long save_rdi = fee->__ss.__rdi; #else unsigned long save_edi = fee->__ss.__edi; #endif printf("I compiled with the definition in scope\n"); return 0; } /////////////////////////////////// _______________________________________________ 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… Thanks for the info, Terry. It's very helpful. I finally found the right engineer here to talk to, and it looks like we only use that information for crash logging, so a) it's okay if the info changes in a new release, and b) we're going to use OS X's crash reporting anyway, so we'll be yanking all this. Sorry to make you go to the effort of explaining it, but it's very educational, anyway, and I'll keep it around for future reference. On Aug 12, 2009, at 3:25 PM, Rick Mann wrote: I'm guessing I'm going to need to change this code. It uses ucontext to get the sigcontext, and then uses that to save off some registers and optionally deal with some error state. Is there a way to do that without relying on a fragile API? Can you get chip vendors to stop making new chips with new features that might need information saved on a context switch? POSIX pretty much nails us to a non-opaque cross for all time for the ucontext_t and mcontext_t because it mandates that we expose the ucontext_t elements directly off a cast pointer, and it mandates that getcontext() take a ucontext_t that might have been statically declared, instead of treating it opaquely, and there's no corresponding destroycontext() (a pointer to a pointer would have been ideal for the ucontext_t type, with accessor and mutator functions which could be vendor defined, the way it's possible to implement posix_spawn()). I can (probably) post some of our code if it helps. But we basically do this: #if defined( HAVE_BSD_STYLE_SIGNALS ) #define SIGCONTEXT_MEMBER(x, y) ( static_cast< unsigned long >( x- >sc_##y ) ) #endif void Global_sigaction_handler( int signum, siginfo_t *sinfo, void *arg ) { struct ucontext * uc = reinterpret_cast<struct ucontext *>( arg ); struct sigcontext * context = (struct sigcontext *)&uc- >uc_mcontext; Is there an alternative way to implement this? Realize the code will not necessarily be portable between versions of the OS (POSIX is what added the __'s to endure against namespace pollution), and the binaries will not necessarily be portable between software updates, since we reserve the right to plop down pretty much any modified version of a context structure on the user stack we need to in order to support a hardware platform, and then pass a pointer to that as the new ucontext_t/mcontext_t type. Also realize that mcontext_t is implementation defined, and we've defined it as a pointer that points someplace on the stack after the ucontext_t, without definition anything about packing or anything else it'd be convenient to nail down, if you didn't want to have to rev your product on software updates, just like we potentially have to rev gdb, Java, and our other tools that know about the internals of these things on software updates. This cruft is NOT API. If you break on an SU because we change it, you fix it. -- Terry /////////////////////////////////// #define _XOPEN_SOURCE 600L /* This is pretty clearly documented in <ucontexh.h> */ /* * some fake data so I don't really have to write a signal handler and make it fire * to demonstrate successfully accessing structure members of the mcontext... */ ucontext_t foo; char *buf[1024]; mcontext_t fee = (void *)buf;; This email sent to site_archiver(a)lists.apple.com

1 0