From: Tomas Szepe <szepe@pinerecords.com>
To: esp@pyroshells.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: FAT32 problems with kernel 2.4.19
Date: Fri, 16 May 2003 21:46:28 +0200 [thread overview]
Message-ID: <20030516194628.GS3478@louise.pinerecords.com> (raw)
In-Reply-To: <23493.65.122.196.250.1053063209.squirrel@mail.webhaste.com>
> [esp@pyroshells.com]
>
> When I'm writing to FAT32 partition, there seems to be a 300% incurred
> size penalty over the equivalent files on ext2 (when unpacking a
> source distribution like boost, gcc, etc)
I don't understand what you're trying to say. Can you elaborate?
> however it would be really, really nice if NTFS was supported (ie: if
> linux could write files on NTFS..) I have a sneaky suspicion that
> FAT32 isn't the greatest and only used on these drives because it is
> the lowest common denominator.
http://linux-ntfs.sourceforge.net/info/ntfs.html
--
Tomas Szepe <szepe@pinerecords.com>
next prev parent reply other threads:[~2003-05-16 19:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-16 5:33 FAT32 problems with kernel 2.4.19 esp
2003-05-16 6:17 ` Marc Giger
2003-05-16 19:46 ` Tomas Szepe [this message]
2003-05-16 21:22 ` Carl-Daniel Hailfinger
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=20030516194628.GS3478@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=esp@pyroshells.com \
--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