Why Was: US Military Dead during Iraq War 1825

a signature at the bottom of a post.

I made them up. Think of a family tree. Then a "node" (in the context I'm using the term) would be when two members of a family marry.

In this case, these groupings have more to do with the local system's directory configurations rather than access to their contents. Systems are no longer isolated; in this day and age, isolated systems are now the exception to the rule. It used to be the other way around and that is what the underlying OS philosophies were.

And this is the crucial bug in the architecture. It is the user, and only the user, who is going to make the "which group am I going to join today" decision. Not the government, not the corporations, not the sysadmin, but the USER. It is the user who is going to make the decisions about who should have access to his-her stuff. It is the user who goes shopping for the group s-he wants to join. We, in the computing biz, had better be prepared for this because the fit is going to hit shan no matter how prep'ed we are.

This is a serious bug.

It was already a problem in TOPS-10 in 1978. That's why JMF wrote the monitor code for the File Daemon and gave an example of using it. Just think what you could do if a single disk access of a particular set of bits stored on that disk invoked code before granting the access.

Just think what you as a user could do if people on your list X accessed one of your files; then think what you could do if some of your code could be run before granting that access.

Can you, as the user owning those files, define another group and make it "system-wise" from your point of view?

And corporate question. Think about 1-800 numbers and all the levels you have to go through in order to get an exceptional piece of transaction done.

Good. Think some more :-).

And what about scenarios of If groupA.and.groupB, then groupC.

As an exercise, create all combinations of the IF with ANDs, ORs, and perhaps, XORs. I'm not sure about IORs.

BAH