Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com Message-ID: <011301c0ffd6$c1fde4e0$806410ac@local> From: "Robert Collins" To: Subject: mount functionality Date: Thu, 28 Jun 2001 23:32:19 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-OriginalArrivalTime: 28 Jun 2001 13:21:20.0681 (UTC) FILETIME=[3876F190:01C0FFD5] I notice that in cygwin there's no FS type for the mount call. This is a problem :[. As I don't know how the mount fs type is set in linux, I'm not going to suggest how we should do it, but what I need for UMSDOS (unless you want it either globally on or off) is to be able to get the correct fhandler_* from a given file path. There's no generic mount based capability in cygwin today (and that will be needed if we ever want a mountable proc file system :]). (the logic is straight forward: find the mount point a file belongs to and lookup the device number from the mount point). Any objections to mount(win32, posix, flags) becoming mount(win32, posix, type, flags) ? if type is NULL, the device number will be the current default of FH_DISK_FILE. Rob