[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: RFC: block size identification
From: |
Patrick Leslie Polzer |
Subject: |
Re: RFC: block size identification |
Date: |
Sun, 22 Jan 2006 10:23:01 +0100 |
On Sun, 22 Jan 2006 00:37:31 +0100
Sven Luther <Sven Luther <address@hidden>> wrote:
| Well, the block size information for the filesystem is in the
| partition table block. I currently reread the partition table code in
| the filesystem code, because there is no way to pass that information
| from the partition table code to the filesystem code.
Yes, that's what I understood from your explanations.
| > But to remedy your problem you could employ some heuristics:
|
| [...]
|
| Nope, this is unrelated. The information is found in the partition
| block but the filesystem layer cannot get it from the partition
| table. But I'm talking about the root block of the file system here.
| If we check every possible end of the first block, we can find out
| indirectly without using the PT what the block size of this file
| system is.
| > * why do Amiga file systems register fs{0..7}, e.g.
| > affs0..7 in Parted? Is this really necessary?
| > Can't this be avoided?
|
| Because there are different kind of affs and co versions, and there
| was no other mean to achieve that. if we had the ability to have a
| root filesystem, and then various variants, then things would be
| different.
What about introducing a field of possible versions?
struct PedFileystemVersion
{
int id;
char* description;
};
Leslie
--
gpg --keyserver pgp.mit.edu --recv-keys 0x52D70289
pgp_N02TyBiWM.pgp
Description: PGP signature
Re: RFC: block size identification, Otavio Salvador, 2006/01/21