9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] Why do we need syspipe() ?
Date: Mon,  5 Jan 2009 09:28:56 +0200	[thread overview]
Message-ID: <d7dc25e31d78f6889aaed46f7bdeeeef@proxima.alt.za> (raw)
In-Reply-To: <dd6fe68a0901042220y278aa283g87f42d2eb458e617@mail.gmail.com>

> The # device syntax is very useful to mean the kernel device
> and none other in these situations.  There's definitely
> something unsatisfactory about it, but it works.

Smacks of overloading; at the very least it seems to suggest that
there ought to be official sanction as well as documented situations
exactly as you described.  To pepper the libraries with direct calls
to the kernel drivers is likely to cause consternation at the very
minimum.  I appreciate that a solution isn't yet obvious and I hope
that further thought will eventually lead to the necessary elegance.

++L




  reply	other threads:[~2009-01-05  7:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-04  5:04 Roman V. Shaposhnik
2009-01-04  6:56 ` Russ Cox
2009-01-05  4:39   ` Roman V. Shaposhnik
2009-01-05  6:20     ` Russ Cox
2009-01-05  7:28       ` lucio [this message]
2009-01-05 11:00         ` roger peppe
2009-01-08 23:36           ` Roman V. Shaposhnik
2009-01-06 17:40       ` Nathaniel W Filardo
2009-01-06 20:37         ` Charles Forsyth
2009-01-06 23:13           ` Roman V. Shaposhnik
2009-01-06 23:15             ` erik quanstrom
2009-01-08 23:45               ` Roman V. Shaposhnik
2009-01-08 23:48                 ` erik quanstrom
2009-01-09  2:05                   ` Roman V. Shaposhnik
2009-01-09 12:54                     ` roger peppe
2009-01-07  3:48             ` lucio
2009-01-07  7:00       ` Roman Shaposhnik
2009-01-07  9:31         ` Charles Forsyth

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d7dc25e31d78f6889aaed46f7bdeeeef@proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).