diff options
Diffstat (limited to 'hurd/glibc')
| -rw-r--r-- | hurd/glibc/hurd-specific_api.mdwn | 19 | ||||
| -rw-r--r-- | hurd/glibc/internals.mdwn | 35 |
2 files changed, 13 insertions, 41 deletions
diff --git a/hurd/glibc/hurd-specific_api.mdwn b/hurd/glibc/hurd-specific_api.mdwn index aeb63d91..7ead63cd 100644 --- a/hurd/glibc/hurd-specific_api.mdwn +++ b/hurd/glibc/hurd-specific_api.mdwn @@ -1,17 +1,18 @@ -[[!meta copyright="Copyright © 2002, 2007, 2008 Free Software Foundation, Inc."]] +[[!meta copyright="Copyright © 2002, 2007, 2008, 2010 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]]."]]"""]] +is included in the section entitled [[GNU Free Documentation +License|/fdl]]."]]"""]] [[!meta title="Hurd-specific glibc API"]] These functions have meaning only under Hurd. They are needed to get port -names that are used in native Hurd API (the RPC calls to servers). The `.defs` +names that are used in native Hurd API (the [[RPC]]s to servers). The `.defs` and `.h` files can be found in `/include/hurd` when all development files are installed (Debian package `hurd-dev`.) Note that `.defs` are not included in C programs -- they are used to produce `.h` files. @@ -81,7 +82,13 @@ programs -- they are used to produce `.h` files. <dt><tt><b>openport</b> (io_t port, int flags);</tt></dt> <p> </p> - <dd>Open a file descriptor on a port. FLAGS are as for <tt>open</tt>; flags affected by <tt>io_set_openmodes</tt> are not changed by this. If successful, this consumes a user reference for PORT (which will be deallocated on close.) See <tt>&lt;hurd/io.defs&gt;</tt> and <tt>&lt;hurd/io.h&gt;</tt>.</dd> + <dd>Open a [[unix/file_descriptor]] on a [[microkernel/mach/port]]. FLAGS + are as for <tt>open</tt>; flags affected by <tt>io_set_openmodes</tt> are + not changed by this. If successful, this consumes a user reference for + PORT (which will be deallocated on close.) See + <tt>&lt;hurd/io.defs&gt;</tt> and + <tt>&lt;hurd/io.h&gt;</tt>. + </dd> <p> </p> <dt><tt>task_t</tt></dt> @@ -157,7 +164,7 @@ programs -- they are used to produce `.h` files. </p> <dt><tt>thread_t</tt></dt> <dt><tt><b>hurd_thread_self</b> (void);</tt></dt> - <dd>Return the current thread's thread port. This is a cheap operation (no system call), but it relies on Hurd signal state being set up.</dd> + <dd>Return the current thread's thread port. This is a cheap operation (no [[system call]]), but it relies on Hurd signal state being set up.</dd> <p> </p> <dt><tt>error_t</tt></dt> diff --git a/hurd/glibc/internals.mdwn b/hurd/glibc/internals.mdwn deleted file mode 100644 index 897da92e..00000000 --- a/hurd/glibc/internals.mdwn +++ /dev/null @@ -1,35 +0,0 @@ -[[!meta copyright="Copyright © 2009 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]]."]]"""]] - -Some bits about this, some bits about that. - -# Controlling TTY - -Hurd controlling tty behavior is generally consistent with BSD's, including -`TIOCSCTTY`. Linux also has `TIOCSCTTY` and it is harmless to use it there. -But BSD and Hurd never do an implicit `TIOCSCTTY` (hence our `O_NOCTTY` is -zero). - -C.f. <http://lists.gnu.org/archive/html/bug-hurd/2009-10/msg00030.html> and the -following messages. - -# Sinals - -[[Unix]] signals are implemented in glibc. - -In every process, signals are handled in a separate signal thread. - - [Why does kill hang sometimes?] - <youpi> kill send the signal to the process - <youpi> if the process is hung, killing waits - <youpi> signals should be just asynchronous, but apparently for some reason - Roland & co wanted some syunchronization - -[[!taglink open_issue_glibc]] |