Theodore Tso wrote:
> The question then is what to do when the user specifies something
> non-sensical, where they put the filesystem type last.
Well, I'd say do what they asked, treat the [filesystem type] stanza
just like any other, and anything in it which may override previous
stanzas, does.
> One approach
> would be to use a two-pass algorithm, where you first scan the list
> for any filesystem type or size types, and if so, you suppress
> prefixing the list with the fs_type and size_type. I think that's
> what you are suggesting.
Not exactly...
> Then there was my approach, which was admittedly partially influenced
> by what was quicker and easier to code, which only checked the
> expected position.
Well, I think that what I'm suggesting (but it's late, and I'm tired, so
it's hard for me to tell for sure... ;) is that there is no special
anything. You simply take the specified -T arguments in order, and use
that as the search/override order for any setting found in the stanzas
specified. This would probably be simplest to code, actually, as well
as simplest to document, and even most powerful/flexible for the user.
But, I suppose I can live with
-T [fs_type,][size_type,]user_type[,additional_type...]
which is reasonably clear, though... we just need to document that there
are 7 special stanza names in 2 categories, which the code will put
there *for* you if you don't put it them the right place, yourself.
It's just, IMHO, a more complicated and restricted specification for the
option.
-Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
