From: Anton Petrusevich <casus@att-ltd.biz>
To: linux-kernel@vger.kernel.org
Subject: ftruncate64
Date: Thu, 26 Feb 2004 05:27:30 +0600 [thread overview]
Message-ID: <200402260527.30306.casus@att-ltd.biz> (raw)
Hi guys,
Sorry guys, forgot about bs, 2Tb is large enough :)
--
Anton Petrusevich
next reply other threads:[~2004-02-25 23:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-25 23:27 Anton Petrusevich [this message]
[not found] <1tgNg-8o9-5@gated-at.bofh.it>
[not found] ` <1vBDZ-48V-7@gated-at.bofh.it>
2004-03-03 21:42 ` ftruncate64 Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2004-02-25 23:23 ftruncate64 Anton Petrusevich
2004-03-03 10:08 ` ftruncate64 Chris Wedgwood
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=200402260527.30306.casus@att-ltd.biz \
--to=casus@att-ltd.biz \
--cc=linux-kernel@vger.kernel.org \
/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®