9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Skip Tavakkolian <skip.tavakkolian@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 08:49:24 -0700	[thread overview]
Message-ID: <CAJSxfmK81r1n5LGJi0gX=_juHavY0jFD8Mk0fmAZnBuCAAmAZQ@mail.gmail.com> (raw)
In-Reply-To: <a6d7d04c1a06102fa32198696fb2668c@krabbe.dyndns.org>

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

If you want to solve your problem -- rather than trying to figure out why
linux cifs might want to completely emulate windows to a plan9 client  --
i'd suggest importing things from linux with sftpfs or running something
like u9fs on linux side, etc.



On Wed, Aug 28, 2013 at 2:51 AM, Ingo Krabbe <ikrabbe.ask@gmail.com> wrote:

> > Ingo Krabbe <ikrabbe.ask@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
>
>
> ---------- Forwarded message ----------
> From: Steffen Daode Nurpmeso <sdaoden@gmail.com>
> 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.ask@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
>

[-- Attachment #2: Type: text/html, Size: 3739 bytes --]

  parent reply	other threads:[~2013-08-28 15: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
2013-08-28 15:49     ` Skip Tavakkolian [this message]
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='CAJSxfmK81r1n5LGJi0gX=_juHavY0jFD8Mk0fmAZnBuCAAmAZQ@mail.gmail.com' \
    --to=skip.tavakkolian@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).