From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Steve French" Subject: Named pipe support for support of RPC Date: Thu, 7 Aug 2008 14:44:28 -0500 Message-ID: <524f69650808071244v550dbeebmc97cecb77164d9d@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit To: linux-fsdevel , linux-cifs-client@lists.samba.org Return-path: Received: from wf-out-1314.google.com ([209.85.200.169]:50799 "EHLO wf-out-1314.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752322AbYHGTo3 (ORCPT ); Thu, 7 Aug 2008 15:44:29 -0400 Received: by wf-out-1314.google.com with SMTP id 27so982076wfd.4 for ; Thu, 07 Aug 2008 12:44:28 -0700 (PDT) Content-Disposition: inline Sender: linux-fsdevel-owner@vger.kernel.org List-ID: 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? -- Thanks, Steve