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 -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
