More: [1.7] packaging problem? Both /usr/bin/ and /usr/lib/ are non-empty

Corinna Vinschen
Wed May 13 16:43:00 GMT 2009

On May 13 18:36, Corinna Vinschen wrote:
> On May 13 12:15, Christopher Faylor wrote:
> > On Wed, May 13, 2009 at 10:56:58AM +0200, Corinna Vinschen wrote:
> > >Yes.  The nouser option doesn't make sense for the mount command because
> > >you can't override a nouser mount point with the mount command anyway.
> > >Every mount point created by mount is a user mount point.
> > 
> > That is exactly what I changed.  Since linux doesn't have the concept of
> > a "user" mount, it seems counterintuitive not to be able for a
> > sufficiently privileged user to be able to update a "system" mount
> > without needing to change /etc/fstab and restarting every Cygwin process.
> But that still doesn't make sense.  The idea is that system (or nouser)
> mount points are unchangeable within a session.  The mount points you
> create with mount are valid inside of a session only anyway, and the
> user typically should not override what the system admin has set as
> unchangable by the user.

Oh, btw, Linux *has* a "user" mount option, which are mount points
every user can use.  That's fairly close (of course not 100%) to how
Cygwin is handling user mounts.


Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

More information about the Cygwin-developers mailing list