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

Christopher Faylor
Wed May 13 17:10:00 GMT 2009

On Wed, May 13, 2009 at 06:36:05PM +0200, Corinna Vinschen wrote:
>On May 13 12:15, Christopher Faylor wrote:
>>On Wed, May 13, 2009 at 10:56:58AM +0200, Corinna Vinschen wrote:
>>>On May 12 23:02, Christopher Faylor wrote:
>>>>I've called what we do with '/' "immutable".  An immutable mount
>>>>setting needs to be overridden with an "override" option.
>>>>I've also marked all of the automatic mounts with a ",auto" to make it
>>>>clear that Cygwin is creating them automatically.  I also added this to
>>>>cygdrive mounts.
>>>fillout_mntent shouldn't do that.  "auto" and "immutable" are internal
>>>flags, not valid mount options.  If fillout_mntent adds them to
>>>mnt_opts they will be printed by mount(1), which is not a good idea if
>>>you use the `mount -m' command to generate an /etc/fstab output.
>>I thought it was nice to be able to see which files came into being
>>because of a Cygwin decision and which were called for specifically.
>>Linux adds "stuff" in that field which wasn't specified on the command
>>But, regarding, "mount -m": It looks like more mount work is required
>>there since we don't want mount -m to generate mount commands that will
>>fail (as in the case of root) or to force a mount of /usr/lib when it
>>isn't necessary.  The ",auto" would be a nice clue about that.  We
>>could just have mount ignore that option like linux's mount does with
>>some options that show up in its mount output.
>Ok, sure.  Are you going to do that?

Yes.  Trivial change.

I added "immutable" and "auto" as no-op options for the mount command
too but would you rather not see immutable at all?  Or, mount could
actually implement it and allow it on any old random mount.


More information about the Cygwin-developers mailing list