Re: [9fans] using opendisk on a sd partition

["Michael Teichgräber" <mt@wmipf.in-berlin.de>]

It seems that disk/format is using the c/h/s values under
a certain condition. If type is `hard' and you provide the -f
option (which I did following some examples), disk->c/h/s will
have an influence on the size of the created fat system:

	if(t->sectors == 0 && strcmp(type, "hard") == 0) {
		t->sectors = disk->s;
		t->heads = disk->h;
		t->tracks = disk->c;
	}

	...

	if(fflag){
		disk->size = t->bytes*t->sectors*t->heads*t->tracks;
		disk->secsize = t->bytes;
		disk->secs = disk->size / disk->secsize;
	}

I'm wondering whether `fflag' somehow is used with different
meanings in format.c. The first is explained for `-f' in the
man-page: don't low-level format a floppy, for other devices
it's a no-op. Moreover, in the context above it seems to
be used as `is-a-file' flag: The code makes sure that the
size-related members of `disk' are set to proper values, in case it
is perhaps a file that is too small to contain an image of the
selected fd type. Some lines later the file would be expanded
to meet disk->size. Perhaps the condition above should read

	if(disk->type == Tfile){

then -f resp. fflag would really be a no-op for non-floppy
devices (and disk->c would be ignored, while h and s still
are stored into the fat parameter block).

Michael