9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Steffen "Daode" Nurpmeso <sdaoden@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] cifs fails on nodes named aux
Date: Wed, 28 Aug 2013 23:49:43 +0200	[thread overview]
Message-ID: <20130828224943.6a1QCLFEvCy6LuXqJTNFXNlI@dietcurd.local> (raw)
In-Reply-To: <804de2a450c38c5f71889cd4c0fe51f5@kw.quanstro.net>

[-- Attachment #1: Type: text/plain, Size: 806 bytes --]

erik quanstrom <quanstro@quanstro.net> wrote:
 |> > cifs is Windows, i think.
 |> > If this is the case, then you may run into the issue of implicit
 |> > filenames.  Search «aux tale», or browse
 |> > <heirloom.sourceforge.net/mailx_aux_c.html>.
 |
 |as entertaining as this is, is isn't true for dos.  there
 |are no device files on dos in *any* directory.  they
 |are a fiction of the executive.  now the effect may
 |be the same if you're using command.com, but
 |explorer should be able to deal with that file name.

Oh, sorry, my last Windows was 95B...  I still have this old
Cyrix around, but .. it's been a long time.
Likely you are right -- but i guess Gunnar Ritter is just trying
to make it what he thinks is a "haptic experience" for Windows
users.

 |- erik

--steffen

[-- Attachment #2: Type: message/rfc822, Size: 3735 bytes --]

From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] cifs fails on nodes named aux
Date: Wed, 28 Aug 2013 07:26:16 -0400
Message-ID: <804de2a450c38c5f71889cd4c0fe51f5@kw.quanstro.net>

> > cifs is Windows, i think.
> > If this is the case, then you may run into the issue of implicit
> > filenames.  Search «aux tale», or browse
> > <heirloom.sourceforge.net/mailx_aux_c.html>.

as entertaining as this is, is isn't true for dos.  there
are no device files on dos in *any* directory.  they
are a fiction of the executive.  now the effect may
be the same if you're using command.com, but
explorer should be able to deal with that file name.

- erik


  parent reply	other threads:[~2013-08-28 21:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-28  9:13 Ingo Krabbe
2013-08-28  9:39 ` Steffen Daode Nurpmeso
2013-08-28  9:51   ` Ingo Krabbe
2013-08-28 11:26     ` erik quanstrom
2013-08-28 13:30       ` Kurt H Maier
2013-08-28 21:49       ` Steffen Daode Nurpmeso [this message]
2013-08-28 15:49     ` Skip Tavakkolian
2013-08-30 20:26 ` Steve Simon
2013-08-30 21:17   ` cinap_lenrek
2013-08-28 14:26 Erik Quanstrom
2013-08-28 15:10 ` dexen deVries
2013-08-28 15:39   ` Kurt H Maier
2013-08-28 17:45     ` Ingo Krabbe
2013-08-28 21:54   ` Steffen Daode Nurpmeso

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=20130828224943.6a1QCLFEvCy6LuXqJTNFXNlI@dietcurd.local \
    --to=sdaoden@gmail.com \
    --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).