> Ingo Krabbe <ikrabbe....@gmail.com> wrote:
> |Hey,
> |
> |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.
>
> 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>.
Yes, cifs is used often to mount windows shares, but in this special case I
just chose cifs, as NFS has no current user space server and I want to share
some filesystems of a virtual host, where I can't add kernel modules.
So actually in my setup I use a Linux CIFS Server (aka. smbd, samba) and the
cifs client from plan9.
The shared filesystem originally is a ext2 (or 3 or 4).
Should I really have managed to step over a system design bug that is imported
from 1978 till now, through all systems and versions.
Actually, mounting the cifs with a linux mount -t cifs command maps the "aux"
filename correctly. So the bug might just have been imported into the plan9
cifs client.
Funny bug.
> [.]
> |Any hints for debugging this might help.
>
> Maybe.
> Ciao
>
> |cheers
> |
> |ingo krabbe
>
> --steffen
--- Begin Message ---
Ingo Krabbe <ikrabbe....@gmail.com> wrote:
|Hey,
|
|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.
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>.
[.]
|Any hints for debugging this might help.
Maybe.
Ciao
|cheers
|
|ingo krabbe
--steffen
--- End Message ---