Re: Is shared memory now only for use by the kernel in 2.3.x????

From: Tigran Aivazian (tigran@veritas.com)
Date: Sat Apr 29 2000 - 13:02:15 EST


On Sat, 29 Apr 2000, Ricky Beam wrote:

> On Thu, 27 Apr 2000, Tigran Aivazian wrote:
> >SHMMAX is a default value of kernel variable called shm_ctlmax which
> >happens to be a sysctl tunable and therefore is available by reading from
> >/proc/sys/kernel/shmmax. What's wrong with reading that file (apart from
> >being incompatible with other OSes)?
>
> 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.)

what is "figlet"? I know "fillet", "piglet" and even "aiglet" but not
"figlet".

> First, it requires one's kernel to have procfs enabled.

which is enabled in 100%-epsilon of the cases (i.e. except some
specialized/embedded systems where people try to save a few K by disabling
such an important part of the kernel as /proc)

> Second, it requires the program (user) to have read access to /proc.

No, that particular file is readable by all 0644.

> 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.

human-readable interfaces in /proc are the right thing to have. No point
in arguing against or about it. (if it was wrong, Linus wouldn't put it
there - trust him).

>
> The relatively undocumented shmctl() commands IPC_INFO and SHM_INFO can
> retrieve this information properly.
 
ok, that is fine - I am glad you found an alternative solution.

> (Gez, are we going to start programming everything in prolog now?)

PROLOG is quite irrelevant for this discussion.

Regards,
Tigran.

-
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/



This archive was generated by hypermail 2b29 : Sun Apr 30 2000 - 21:00:17 EST