All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: kernel patch support large fat partitions
Date: 5 Jan 2002 12:40:51 -0800	[thread overview]
Message-ID: <a17ocj$qr5$1@cesium.transmeta.com> (raw)
In-Reply-To: <5.1.0.14.0.20020103152205.039f2008@mage.qualcomm.com> <5.1.0.14.0.20020104104826.03a15978@mage.qualcomm.com>

Followup to:  <5.1.0.14.0.20020104104826.03a15978@mage.qualcomm.com>
By author:    Vijay Kumar <jkumar@qualcomm.com>
In newsgroup: linux.dev.kernel
> 
> Using 28bit cluster numbers and 65536 cluster size I could go upto 16TB 
> which is lot more than what I wanted. So right now I have no problem with 
> the on-disk format of a fat partition. Nevertheless with hard drives prices 
> going down dramatically it may not be too long before we hit the limit.
> 
> Regards,
> - Vijay
> 

That's Microsoft's problem -- that's a fundamental limit of the format
they defined.  The fact that they defined it in the first place is
part of the problem (the only way you can make a FAT filesystem work
*well* is by loading the entire FAT into memory ahead of time, and
"FAT32" breaks that), instead of creating a more sensible
replacement.

(FWIW, the reason they used to justify FAT32 was "it would be too much
work to make DOS handle NTFS", as if those were the only options...)

	-hpa

-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt	<amsp@zytor.com>

  reply	other threads:[~2002-01-05 20:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-03 23:42 kernel patch support large fat partitions Vijay Kumar
2002-01-04  0:24 ` Andreas Dilger
2002-01-04  0:34 ` Vijay Kumar
2002-01-04  2:48 ` CJ
2002-01-04 18:52 ` Vijay Kumar
2002-01-05 20:40   ` H. Peter Anvin [this message]
2002-01-05  0:12 ` Vijay Kumar
  -- strict thread matches above, loose matches on Subject: below --
2002-01-04 10:40 Randal, Phil

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='a17ocj$qr5$1@cesium.transmeta.com' \
    --to=hpa@zytor.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.