tech-kern archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]


        Hello.  The thornier issue, I think, is that unless things have
changed since I worked with this stuf last time, and that is highly
probable, the group data is passed in and out of the kernel in fixed sized
arrays.  so, you'll have to modify libc on every nfs client for every
operating system that wants to be a client of your nfs server, potentially.
I remember trying to do this a number of years ago and finding all of these
limitations in places I didn't expect.  This is why access control lists
came into being.


On Oct 9,  3:58pm, Edgar =?iso-8859-1?B?RnXf?= wrote:
} > Of course.  But will it do what you want?
} I don't understand your concerns.
} My intention was to let the NFS client run the modified kernel with a raised 
} group limit. Then, the process in question will be a member of more than 16 
} secondary groups which will enable it to access files readable for these 
} groups, be it on NFS or not. Where is the NFS server involved? Enforcing 
} access limits is the client's business, isn't it?
>-- End of excerpt from Edgar =?iso-8859-1?B?RnXf?=

Home | Main Index | Thread Index | Old Index