Re: Curious: regarding quota control in linux, is it mature? can it be done?
On Wed, 15 May 2002, Miquel van Smoorenburg wrote:
> In article <[🔎] Pine.SOL.3.96.1020515145656.20463C-100000@mfcf.math.uwaterloo.ca>,
> Walter Tautz <wtautz@math.uwaterloo.ca> wrote:
> >I am curious to know why there are two quota.h
> >files in libc-dev:
> >
> >/usr/include/linux/quota.h --- this is described
> > at the top as
> > This just represents the non-kernel parts of <linux/quota.h>.
> >
> >/usr/include/sys/quota.h --- this is presumably the kernel interface?
>
> Easy. You're not supposed to use files under /usr/include/linux or
> /usr/include/asm from user level programs, so forget about that.
>
> >what is the difference between these?
>
> The linux/quota.h is an internal glibc/kernel thing you are not
> supposed to use.
>
I basically gathered that one header is to be used by user programs
but what is linux/quota.h used for then? Kernel compilation?
clearly any program that can be executed by a user be it root or
not would presumably use libc and yet there are two header files.
I have no problem never using /linux headers but it does make
me curious about the general design of libc.... Is there a design
rational for libc that explains the general organization of the
header files? Not just the instace I described above. I am genuinely
curious how these things work.
-walter
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: