Because I prefer to keep things under control. And I don't think it will require a huge amount of work to disable working with permissions in setup.exe with command line switch. I started to worry about it because cygwin failed so much with permissions, having both cygwin-specific and inherited ones (copied) at the same time, resulting in complete mess. A non-privileged user could modify cygwin configuration files in /etc and it was not possible to do something about it. That is when I decided to control permissions myself, but cygwin setup overwrites permissions on every install, including files in /etc, messing up everything.
On Thu, Sep 2, 2010 at 12:18 AM, Andy Koppe <andy.ko...@gmail.com> wrote: > On 1 September 2010 15:18, Vasya Pupkin wrote: >>> Do creating any entries in /etc/passwd or /etc/group or /etc/fstab >>> files can overcome this... >> >> Nothing can overcome thins until setup.exe is modified to support >> noacl option in /etc/fstab or get a similar comman line parameter or >> even a checkbox. > > Reading /etc/fstab wouldn't work for the initial install. All these > possibilities require a substantial amount of (voluntary) work, yet so > far the only reason you've given for it was that you "don't like how > cygwin works with NTFS permissions and therefore it is disabled > through /etc/fstab". It shouldn't surprise you that that doesn't put > it high on anyone's list of priorities. > > So why do you care about permissions on files that come with setup.exe > packages? Setup.exe won't touch /home or anything outside the Cygwin > install. > > Andy > > -- > Problem reports: http://cygwin.com/problems.html > FAQ: http://cygwin.com/faq/ > Documentation: http://cygwin.com/docs.html > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > > -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
