On Tue, 11 Feb 2003, Max Bowsher wrote: > Brian Ford wrote: > > Here is an example: > > > > ls -l /bin/make.exe > > -rwx------+ 1 ford None 156160 May 11 2002 make.exe > > > > getfacl -a /bin/make.exe > > # file: make.exe > > # owner: ford > > # group: None > > user::rwx > > group::--- > > group:SYSTEM:rwx > > group:Administrators:rwx > > group:Users:r-x > > mask:rwx > > other:--- > > > > So, you can see that the unix permissions do not show read or execute > > status for anyone but me. However, the ACL's show Users do have these > > permissions. > > Yep. It's impossible to fully represent an ACL in traditional Unix > permissions. > That's fine.
> > Trying to execute make in bash via PATH for other users results in > > make not found. But, trying to execute /usr/bin/make works fine for > > them. > > > > Can someone please help? Thanks. > > Options: > - Disable ntsec > - chown/chmod everything > > Future versions of setup will set the group to either Administrators or > Users, which should allow more of the ACL to show in the mode bits. > I strongly vote for Users. Please yell loudly when this future version appears. Why are shells and such confused by this, though? -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
