From cfccdc1bdbee7fb25ef0aa9639a3ffec926bf690 Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Mon, 13 Dec 2010 19:56:25 +0100 Subject: Shuffle / create / enhance some UNIX / glibc pages. --- hurd/glibc/internals.mdwn | 35 ----------------------------------- 1 file changed, 35 deletions(-) delete mode 100644 hurd/glibc/internals.mdwn (limited to 'hurd/glibc') 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. 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?] - kill send the signal to the process - if the process is hung, killing waits - signals should be just asynchronous, but apparently for some reason - Roland & co wanted some syunchronization - -[[!taglink open_issue_glibc]] -- cgit v1.2.3