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
also note, you can still access these magic filenames in windows
thru a unc path.
like \\somemachine\someshare\path\to\magic\file\aux
or when mapped as a dos drive:
\\?\X:\path\to\magic\file\aux
--
cinap
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.
Any
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
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
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
Quoting erik quanstrom quans...@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
the claim that the devices are in the directories and thus the file system is
still false. even if explorer has some unnecessary code. and plan 9 is not
immune from unnecessary weird bits e.g. the export protocol.
- erik
Kurt H Maier k...@sciops.net wrote:
Quoting erik quanstrom
On Wednesday 28 of August 2013 10:26:01 Erik Quanstrom wrote:
the claim that the devices are in the directories and thus the file system
is still false. even if explorer has some unnecessary code. and plan 9 is
not immune from unnecessary weird bits e.g. the export protocol.
a somewhat
Quoting dexen deVries dexen.devr...@gmail.com:
On Wednesday 28 of August 2013 10:26:01 Erik Quanstrom wrote:
the claim that the devices are in the directories and thus the file system
is still false. even if explorer has some unnecessary code. and plan 9 is
not immune from unnecessary weird
To: Fans of the OS Plan 9 from Bell Labs 9fans@9fans.net
Cc:
Date: Wed, 28 Aug 2013 11:39:33 +0200
Subject: Re: [9fans] cifs fails on nodes named aux
Ingo Krabbe ikrabbe@gmail.com wrote:
|Hey,
|
|I found a quite strange effect with cifs (plan9 bell labs edition). \
|I use cifs
not sure why FAT32 would be relevant here, since he's using a linux
cifs server from an ext fs. samba mangles reserved names much as it
mangles long filenames -- check mangle_hash2.c for examples. when
samba is deciding if a filename needs to be mangled, it checks for
reserved
erik quanstrom quans...@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
dexen deVries dexen.devr...@gmail.com wrote:
|On Wednesday 28 of August 2013 10:26:01 Erik Quanstrom wrote:
| the claim that the devices are in the directories and thus the file system
| is still false. even if explorer has some unnecessary code. and plan 9 is
| not immune from unnecessary
14 matches
Mail list logo
