Path: utzoo!attcan!utgpu!utstat!jarvis.csri.toronto.edu!rutgers!texbell!sugar!ficc!peter From: peter@ficc.uu.net (Peter da Silva) Newsgroups: comp.os.minix Subject: Re: New fs/protect.c that allows mortals to chown() Message-ID: <6961@ficc.uu.net> Date: 14 Nov 89 15:54:14 GMT References: <689.255678C1@mudos.ann-arbor.mi.us> <1989Nov7.185627.24105@world.std.com> <10159@attctc.Dallas.TX.US> <1989Nov13.192902.15473@world.std.com> Reply-To: peter@ficc.uu.net (Peter da Silva) Organization: Xenix Support, FICC Lines: 24 In article <1989Nov13.192902.15473@world.std.com> madd@world.std.com (jim frost) writes: > image (for instance) is owned by "foo" who has no disk quota, or "bar" > who has only a megabyte. There is no way to deal with accountability. I really think that the day when disk quotas become important for MINIX is sufficiently far away that this isn't a real concern. Make it an option. > I honestly think chown should be a root-only; it's much simpler that > way and if a user really needs to chown a file, logging in as the > other user and using "cp" works great. Can't put that in a script. If you're going to start talking about security, how about backups and restorations? You want to have to make system operators root? > This is getting off the minix track, though. For sure. -- `-_-' Peter da Silva . 'U` -------------- +1 713 274 5180. "*Real* wizards don't whine about how they paid their dues" -- Quentin Johnson quent@atanasoff.cs.iastate.edu