Oh, maybe, because I DON'T WANT TO READ SOME *** DAMNED TEXT FROM /proc
TO GET A FUCKING NUMBER. (pass that through figlet to get the full effect.)
First, it requires one's kernel to have procfs enabled. Second, it requires
the program (user) to have read access to /proc. Third, it requires a metric
buttload of unnecessary shit-code in the source to grok text intended for
a human to glean a simple number from the kernel.
The relatively undocumented shmctl() commands IPC_INFO and SHM_INFO can
retrieve this information properly. However, there are indications that
the binary-ness of this could be moved to "a proc file system interface"
at some time in the future.
(Gez, are we going to start programming everything in prolog now?)
--Ricky
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/