From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <b6f9092d8d262c3b192323e406bbda16@quintile.net>
From: "Steve Simon" <steve@quintile.net>
Date: Fri, 30 Aug 2013 21:26:37 +0100
To: 9fans@9fans.net
In-Reply-To: <262fe92a8b5be326847bdc278b05f27f@krabbe.dyndns.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] cifs fails on nodes named aux
Topicbox-Message-UUID: 77aa93b4-ead8-11e9-9d60-3106f5b1d025

> I found a quite strange effect with cifs (plan9 bell labs edition).
> I use cifs to mount werc installations from p9p linux servers.
> Cifs is needed here, as the virtual hosted machine does not support nfs.
> Maybe I should switch to another userspace filesystem, but for now its cifs.

> Any node named `aux` is translated into `AHY9U3~9`, of course one-way only,
> such that I cannot use the `AHY9U3~9` node in my plan9 mount.


Hi,

I was on holiday last week so I didn't reply. I wrote cifs
and can only say this must be a feature of samba and not cifs.

Cifs knows nothing about reserved  names and filename frogs
(illegal characters), it passes names directly through to the
remote server and expects it to either accept or reject them.

Windows dislikes AUX, NUL, PRN, COM[0-9], LPT[0-9], CON and CLOCK$
irrespective of case; there may be others. These seem to be ghosts of
MSDOS or or was it CP/M, but then again it might have been RSTS-11...

-Steve