Re: chmod, chown and user, group
From: Måns Rullgård (mru_at_inprovide.com)
Date: 11/20/04
- Next message: Lothar Scholz: "Re: linux/gui programming, getting started"
- Previous message: Otto Wyss: "Re: chmod, chown and user, group"
- In reply to: Kasper Dupont: "Re: chmod, chown and user, group"
- Next in thread: Kasper Dupont: "Re: chmod, chown and user, group"
- Reply: Kasper Dupont: "Re: chmod, chown and user, group"
- Reply: Otto Wyss: "Re: chmod, chown and user, group"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sat, 20 Nov 2004 23:21:28 +0100
Kasper Dupont <kasperd@daimi.au.dk> writes:
> If it is just about showing something to the user, I'd
> keep it simple. Some of the special cases like immutable
> files I'd avoid, and just let the user see an error
> message.
>
> I'd suggest you verify only two things. First of all
> that the user have write permissions to the directory.
> And in addition to that if the directory is sticky, you
> verify that the user is owner of either the directory
> or the file.
>
> That should be good enough for displaying in a GUI.
Wrong. AFS ignores the usual permission bits when deciding whether to
allow an operation, and looks only at its own ACLs. It's quite
irritating when a program refuses to let you do something you are
allowed to do, only because the program believes it wouldn't work, and
so won't even let you try. It's much better to just attempt the
operation and fail with an error message if it turns out it wasn't
allowed.
-- Måns Rullgård mru@inprovide.com
- Next message: Lothar Scholz: "Re: linux/gui programming, getting started"
- Previous message: Otto Wyss: "Re: chmod, chown and user, group"
- In reply to: Kasper Dupont: "Re: chmod, chown and user, group"
- Next in thread: Kasper Dupont: "Re: chmod, chown and user, group"
- Reply: Kasper Dupont: "Re: chmod, chown and user, group"
- Reply: Otto Wyss: "Re: chmod, chown and user, group"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|