[[!meta copyright="Copyright © 2010, 2014 Free Software Foundation, Inc."]] [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable id="license" text="Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled [[GNU Free Documentation License|/fdl]]."]]"""]] A [[UNIX file descriptor|unix/file_descriptor]] is implemented in [[glibc]] by using operations on objects referred to by [[Mach ports|microkernel/mach/port]]). # IRC, freenode, #hurd, 2013-11-29 [[!tag open_issue_documentation]] Hi, are there any advantages to use the __USEPORT and HURD_DPORT_USE etc macros? some things don't work without htem I wondered that too could you be more specific ? i can try __USEPORT is merely a wrapper to HURD_DPORT_USE HURD_PORT_USE handles concurrent access to ports is that enough ? so not using these makes loading the port name racy ? shared ones, yes mostly, file descriptors ok so yes, that's reason enough ;) so even if file descriptor ports are not accessed, it's use is preferred? I assume the answer is yes:-D gnu_srs: not accessed ? file descriptor ports not used, but e.g. auth ports there is code in hurd and eglibc sometimes using the macros, sometimes not the macro is used when ports are shared or can be shared k!, thanks