All of lore.kernel.org
 help / color / mirror / Atom feed
From: simo <idra@samba.org>
To: Steve French <smfrench@gmail.com>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	linux-cifs-client@lists.samba.org
Subject: Re: Named pipe support for support of RPC
Date: Thu, 07 Aug 2008 15:50:57 -0400	[thread overview]
Message-ID: <1218138657.25521.84.camel@localhost.localdomain> (raw)
In-Reply-To: <524f69650808071244v550dbeebmc97cecb77164d9d@mail.gmail.com>

On Thu, 2008-08-07 at 14:44 -0500, Steve French wrote:
> The WINE team and others have requested that we add named pipe support
> (at least as a client, since Samba server has some pipe support
> already) - which is important to be able to get to management calls in
> Samba and Windows, but also needed for certain apps.   This would be
> fairly easy to do in cifs.ko (open/read/write/close are not much
> different for pipes than files, although lookup would require "lookup
> intents" to work and they would not show up in readdir), but I was not
> sure if there was a precedent for how named pipes would show up (if at
> all) in the namespace.   In Windows and a few other OS, the client
> side passes the UNC name through the syscall (open) - e.g.
> \\server\pipe\pipename and the VFS dispatches that to the registered
> named pipe handlers - but in Linux it probably makes sense to do this
> through a pseudo-filesystem which Wine can look for and open files
> (pipes) in.   Is there a precedent for something similar or a pipe
> pseudo file system?

If at all possible it would probably make sense to use the same naming
convention and not a pseudo filesystem. This would make it much easier
to port applications and I guess also allow user apps to share data
through pipes created in the normal name space with windows servers.

Simo.

-- 
Simo Sorce
Samba Team GPL Compliance Officer <simo@samba.org>
Senior Software Engineer at Red Hat Inc. <ssorce@redhat.com>

      reply	other threads:[~2008-08-07 19:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-07 19:44 Named pipe support for support of RPC Steve French
2008-08-07 19:50 ` simo [this message]

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=1218138657.25521.84.camel@localhost.localdomain \
    --to=idra@samba.org \
    --cc=linux-cifs-client@lists.samba.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=smfrench@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.