Chris Devers wrote:
What??
That's hardly why this constraint exists.
If anyone can make changes to any other account's files, then there's no
point in having ownership constraints at all.
Of course. I was being facetious.
The "new" version of chown prevents what?
New is a relative term. I have worked with systems where the /dev was
writable by anyone and the raw devices readable! When I pointed this out
to the sysadmin I was told it can't be changed since some of the system
utilities require this; they didn't run in superuser mode. Needless to
say (but I'm going to anyhow) I only kept what was absolutely necessary
on that system. Modern systems haven't had this problem for decades and
security is given much more consideration than back then.
And yes, back then chown worked exactly as I described; you could use it
to "borrow" some else's quotas. Given the small size of the disks, this
was not an uncommon practice.
BTW, (and this is really going to date me) I do have a copy of the B
Language Manual.
--
Just my 0.00000002 million dollars worth,
--- Shawn
"Probability is now one. Any problems that are left are your own."
SS Heart of Gold, _The Hitchhiker's Guide to the Galaxy_
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
<http://learn.perl.org/> <http://learn.perl.org/first-response>
