From: Jan Kara <jack@suse.cz>
To: Mike Glover <mpg4@duluoz.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: block size for quotas?
Date: Fri, 9 Feb 2001 11:21:03 +0100 [thread overview]
Message-ID: <20010209112103.I24444@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <20010119100231Z129818-469+195@vger.kernel.org>
In-Reply-To: <20010119100231Z129818-469+195@vger.kernel.org>; from mpg4@duluoz.net on Fri, Jan 19, 2001 at 02:02:43AM -0800
Hello.
> I maintain quotatool, a command-line quota utility.
> Right now, I'm using BLOCK_SIZE -- defined in
> <linux/fs.h> -- to convert between blocks and bytes.
> I'd like to not use the linux header files at all for
> this, but how else can I find the info?
In current kernel there's no constant specifying quota
blocksize and BLOCK_SIZE is hardcoded into the quota code
so it's fairly reasonable to use that constant for utils...
(In my patches for new quota format this issue is also
addressed and constant QUOTABLOCK_SIZE is defined).
I don't know if you know that there's been created
SourceForge project for linux quota utils (project has description
'Linux DiskQuota' and has name 'linuxquota'). If you're
interested you might include your utility to standard
quota utils package (there's setquota utility which should be
command line tool in the package so we might drop setquota
if your util is better :)) BTW: What does your util better
than setquota?)
Bye
Honza
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-02-09 10:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-19 10:02 Mike Glover
2001-02-09 10:21 ` Jan Kara [this message]
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=20010209112103.I24444@atrey.karlin.mff.cuni.cz \
--to=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mpg4@duluoz.net \
/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
all inboxes | Powered by JetHome®