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: <mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com
Date: Thu, 28 Jun 2001 22:27:06 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-apps AT cygwin DOT com
Subject: Re: mount functionality
Message-ID: <20010628222706.C3893@redhat.com>
Reply-To: cygwin-apps AT cygwin DOT com
Mail-Followup-To: cygwin-apps AT cygwin DOT com
References: <011301c0ffd6$c1fde4e0$806410ac AT local>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.11i
In-Reply-To: <011301c0ffd6$c1fde4e0$806410ac@local>; from robert.collins@itdomain.com.au on Thu, Jun 28, 2001 at 11:32:19PM +1000

On Thu, Jun 28, 2001 at 11:32:19PM +1000, Robert Collins wrote:
>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 we are going to change this, it should emulate linux.

Changing it will break backwards compatibility unless we do something like
keep the existing "mount" call, name this "mount1", and #define mount mount1
in some appropriate header file.

Otherwise, I have no objections.

cgf