Re: sysconf - exposing constants to userspace

[Jeff Sipek]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 19 February 2004 19:20, Jamie Lokier wrote:
> Jeff Sipek wrote:
> > I think that making something in /sys would make the most sense,
> > with one constant per file. We could dump the consts files to for
> > example /sys/consts, or make a logical directory structure to make
> > navigation easier.
>
> Isn't that very similar to the /proc/sys/kernel we have now?

If I understand the original post correctly, the numbers that we don't make 
available to userspace are compile time constants. For example, since I can't 
think of anything better, NR_CPUS. It is set during the config process, but 
one cannot read the number from userspace while running that kernel. I know 
that there are better examples, but I just can't think of any at the moment.

If I missed the point of the original post, please ignore me.

Jeff.

- -- 
Trust me, you don't want me doing _anything_ first thing in the morning.
		- Linus Torvalds
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFANVUBwFP0+seVj/4RArdbAJ4tsq5cyDJ+058h1D6JDli1nsmP9ACeJnoN
pxE9BuRBNND271SGp81SMHM=
=rmLE
-----END PGP SIGNATURE-----

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/