Why Was: US Military Dead during Iraq War 1827
Also, remember that most of the stuff in Tops20 has found its way into *n*x since about a decade ago. snip It provides a very...
This limitation was removed as posix and 32-bit variables made its way into the *n*x code base; timeframe 1990-1995.
I have administered some pretty large *n*x installations; and with modern *n*x these limits have not been a problem.
You misunderstand. Groups are sets of extra priviliges that are granted to you. One group may have access to reading a database. Another may have rights to read the temperature on the machine. A third may have rights to start internet services.
These groups are often managed across machines, and mechanisms like kerberos or ldap used to grant them. They must be enforced by every single system's kernel though.
I don't get if you think usenet groups or unix groups. Unix groups are like "extra" ppn rights. They are doled out top-down, from the administrator downwards.
If we are talking about usenet; try a setup with a usenet proxy. I use leafnode+; there are lots of others. It initially shows all the groups as empty; and will give a single blurb when I join a group. It will then fetch the contents of that group for me off-line. It can run on dialup lines at night if it has to.
I read and post to that local server; located between the water heater, home alarm and the fuse box in a closet. Last time I managed news on it was february 24th when I gave in and subscribed to a commercial news provider. It will still flood news to upstream providers.
The only "behind the scenes setting" I have to set is the expire interval, defined with a set of regular expressions.
on Ok. That leaves redundancy. Heh. That's why those bit gods earned their money. But how do you edit the disk...
Feature. Solved with ACLs, present in secure *n*x systems for close to a decade now.
ACLs, as they were defined on Multics a decade before that, is still a better solution.
I don't think you're understanding how the Unix filesystem works. Attempting to close an already closed file handle will just result in an exception...
Very impractical on large clusters.
If the superuser makes a little "add a group" application, available to group "addgroup", then you may get to do that. This feature would use the setuid feature of unix. This feature can give separate rights to a binary program. It is usually combined with protection so a you need a group privilige to access it.
Similarly, a simple application can be made to add-remove users from the groups you have created; and that way have a universe of access rights locally that mirror that of a superuser.
1-800 numbers are usually operated as machinery that cannot be interrupted.
-- mrr
Why Was: US Military Dead during Iraq War 1828
Alt Folklore Computers from Newsgroups