From: Peter <peterg@fishinternet.com.au>
To: Ray Olszewski <ray@comarre.com>
Cc: linux-newbie@vger.kernel.org
Subject: Re: Setting quota on user's home folders?
Date: Fri, 18 Mar 2005 06:21:25 +1100 [thread overview]
Message-ID: <1111087285.25539.9.camel@localhost.localdomain> (raw)
In-Reply-To: <5.1.0.14.1.20050316155238.01f4fb98@celine>
On Wed, 2005-03-16 at 16:31 -0800, Ray Olszewski wrote:
>
> For quotas to work, they have to be enabled in your kernel. Stock
> kernels
> usually do not include quota capability, so this means a local
> compile.
I noticed, on running ` locate quota` , that these lines appear in my
output
/lib/modules/2.6.8.1-4-386/kernel/fs/quota_v1.ko
/lib/modules/2.6.8.1-4-386/kernel/fs/quota_v2.ko
I'm thinking this means quotas are supported by modules in this kernel,
and thus a `modprobe quota* ` or similar would suffice, rather than a
kernel recompile.
Is this correct?
Just thinking this could save Eve and others a *lot* of time...
In Debian, I assume after using the modprobe command the module name
could simply be put in /etc/modules to make loading persistent across
reboots. ( Other distros like the Redhat variants would do this
differently, I suppose)
apt-get install quota
would then install what's necessary for the quota command...
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2005-03-17 19:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-16 2:13 SOLVED: Some users locked out of ssh and sftp? Donald Duckie
2005-03-16 23:43 ` Setting quota on user's home folders? Eve Atley
2005-03-17 0:02 ` J.
2005-03-17 0:31 ` Ray Olszewski
2005-03-17 19:21 ` Peter [this message]
2005-03-17 20:00 ` Eve Atley
-- strict thread matches above, loose matches on Subject: below --
2005-03-23 20:28 Jessica_Schieffer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1111087285.25539.9.camel@localhost.localdomain \
--to=peterg@fishinternet.com.au \
--cc=linux-newbie@vger.kernel.org \
--cc=ray@comarre.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox