On Sat, 24 Jun 2000, David Ford wrote:
> > That means I have to use an extra command. I'm a student, and I'm lazy. If
> > users want to protect their files : chmod 600 does the trick, and with a
> > 600 dir you'r safe.
> > > I'm sorry, but I don't see that as a valid rationale.
> > It doesn't make sense for normal users to have immutable / append only
> > privs.
> Yes it does. Virtual sites where you give admins control over their own
> section. They may want to chattr file(s) immutable or append only just incase
> one of their scripts develops a 'feature'.
You never do that on productions machines.
> Users may also be instructing others in a classroom environment and don't need
> the hassle of students going around screwing up files but don't want to give
> their apprentices root authority.
So ?? Let a user screw up his own files.. He'll remember the next
time. Nice thing about Unix is that you can only screw up you own stuff.
> There are several reasons why it would be nice to have special flags avail to
> normal users.
> rm -rf <dir> removes a dir tree regardless of the modes applied to it if the user
> owns it. there's no protection there. chattr +i|a is an extra safegard that
> many people, myself included, enjoy for both user and root.
Personal opinion.. I don't agree..
That means if some user decides to chattr +i all files he owns, and I (as
root) want to remove them, I'll have to chattr -i all files..
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Jun 26 2000 - 21:00:08 EST