From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <60682619.771899.1413721813507.JavaMail.ngmail@webmail24.arcor-online.net> Date: Sun, 19 Oct 2014 16:36:19 +0100 Message-ID: From: Charles Forsyth To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=001a11c1b31212a4720505c85c2e Subject: Re: [9fans] libc struct Dir field type Topicbox-Message-UUID: 1e75bdea-ead9-11e9-9d60-3106f5b1d025 --001a11c1b31212a4720505c85c2e Content-Type: text/plain; charset=UTF-8 On 19 October 2014 16:32, Charles Forsyth wrote: > Only a few have any sort of global > significance, and even that's probably a mistake. > Ignore that: that statement's wrong since they appear in bind operations in bind(1), bind(2), /lib/namespace and similar contexts. I also forgot to add that ls -l shows you the type character: ls -l /dev shows you where different names are produced. --001a11c1b31212a4720505c85c2e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On 19 October 2014 16:32, Charles Forsyth <charles.forsyth@gmail.c= om> wrote:
Only a few have any sort of global
significance, and even that's probably a mistake.

Ignore that: that statement&#= 39;s wrong since they appear in bind operations in bind(1), bind(2), /lib/n= amespace and similar contexts.

I also forgot to add that ls -l shows you the type= character: ls -l /dev shows you where different names are produced.
<= div class=3D"gmail_extra">
--001a11c1b31212a4720505c85c2e--