[haiku-development] Re: [RFC] fat initialization function -- fat driver
- From: Marcus Overhagen <marcusoverhagen@xxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Wed, 21 May 2008 00:01:15 +0200
Marco Minutoli schrieb:
Hello
I am on the way of writing a fat addon for the disk system and I
noticed that the FAT driver miss an initialization function ATM.
We have the mkdos bin tool which does this job.
First of all does it make any sense to write the initialization
function for the actual FAT driver? I saw it has a different licence
and a it's not designed in an OO way like BFS so I was
wondering if you want to rewrite it sooner or later.
You could/should reuse/call mkdos. Rewriting FAT fs and mkdos tool
isn't really an easy job.
[1] suggests how to initialize a FAT volume on a device with 512Mb
sectors and explain Windows policies during the initialization
process. In Windows by default for device size under 512MB a FAT16
volume is built while for disk size larger than 512MB a FAT32 volume is
initialized. FAT12 is only used for floppy. Should we maintain this
policies?
Sure.
As you can readn in [2] Win2k and WinXP are able to read FAT
volume of any size but the format utility isn't able to initialize
volume larger than 32GB. Is this an acceptable limitation for us?
No.
Marcus
- Follow-Ups:
- [haiku-development] Re: [RFC] fat initialization function -- fat driver
- From: Ingo Weinhold
- References:
- [haiku-development] [RFC] fat initialization function -- fat driver
- From: Marco Minutoli
Other related posts:
- » [haiku-development] [RFC] fat initialization function -- fat driver
- » [haiku-development] Re: [RFC] fat initialization function -- fat driver
- » [haiku-development] Re: [RFC] fat initialization function -- fat driver
- » [haiku-development] Re: [RFC] fat initialization function -- fat driver
- » [haiku-development] Re: [RFC] fat initialization function -- fat driver
- » [haiku-development] Re: [RFC] fat initialization function -- fat driver
Hello I am on the way of writing a fat addon for the disk system and I noticed that the FAT driver miss an initialization function ATM.
First of all does it make any sense to write the initialization function for the actual FAT driver? I saw it has a different licence and a it's not designed in an OO way like BFS so I was wondering if you want to rewrite it sooner or later.
[1] suggests how to initialize a FAT volume on a device with 512Mb sectors and explain Windows policies during the initialization process. In Windows by default for device size under 512MB a FAT16 volume is built while for disk size larger than 512MB a FAT32 volume is initialized. FAT12 is only used for floppy. Should we maintain this policies?
As you can readn in [2] Win2k and WinXP are able to read FAT volume of any size but the format utility isn't able to initialize volume larger than 32GB. Is this an acceptable limitation for us?
- [haiku-development] Re: [RFC] fat initialization function -- fat driver
- From: Ingo Weinhold
- [haiku-development] [RFC] fat initialization function -- fat driver
- From: Marco Minutoli