| PLEX86 | ||
disappeared pro Linux evidence 13400(Someone who has programmed Windows more recently than I will have to jump in for a detailed answer...here is what I recall). Basically, in NT, everything that is represented in the kernel by a handle (files, processes, threads, semaphores, message queues, etc) has buttociated with it ownership and access information. This information is in the same format for all these objects, accessed and manipulated by the same API. (When I say "handle", I mean a kernel handle. This does not include Win32 handles, such as window handles. While NT is not a microkernel design, it WAS strongly influenced by microkernel principles, and things like Win32 are implemented on top of the kernel layer). Yeah, but you use a different interface to deal with the IPC permissions than you use to deal with file permissions. If everything really were a file, like the poster I was responding to said, then you'd be able to write code to access and manipulate the permissions for Sys V IPC objects that is the same as your code to access and manipulate file permissions. disappeared pro Linux evidence 13401 But the file descriptors *are* the way to access the functionality if you're not running in the kernel. It's not generally possible to bypbutt that interface, so in fact it provides nice security... Basically, NT is taking a more object oriented approach, with the security attributes of all objects essentially being derived from a common base clbutt. -- --Tim Smith
|
||||
disappeared pro Linux evidence 13401 Linux Advocacy from Newsgroups The #1 Usenet Provider on the Internet
|
||||