Re: [patches] small fixes to some messages and man pages, and some questions

["Benno Schulenberg" <bensberg@justemail.net>]

> > Also I do not understand the descriptions of the new options --nested,
> > --chained, and --onesector.  [...]
> 
> The original comment from code: 
> 
> /* [...]
> NESTED: every partition is contained in the surrounding partitions
>    and is disjoint from all others.

I still fail to understand.  If "contained in the surrounding partitions"
means "contained in the containing partitions", it says nothing.  If it
means "contained in the partitions that come before and after", this
seems impossible to me.  The only way I can make sense of the
above comment is to read it as follows:

NESTED: every extended partition is contained within a surrounding
extended partition [except of course the outermost one] and is disjoint
from all other extended partitions at the same nesting level.

(Here I take "disjoint" to mean "does not overlap", but then I still fail
to understand how "mutually disjoint" is different.)

> CHAINED: every data partition is contained in the surrounding partitions
>    and disjoint from all others, but extended partitions may lie outside

Is a data partition the same as a logical partition?


> > However, I find this a bit misleading: the timingfile is only optional when
> > it is specified via the -t option.  Wouldn't it be better to describe the
> > command with two alternative synopses, as follows?
> > 
> >   Usage: scriptreplay timingfile [typescript [divisor]]
> >      or: scriptreplay [options] [timingfile] [typescript] [divisor]
> 
>    scriptreplay [options] [-t] timingfile [typescript [divisor]]

Yes, that would do.  It does not cover the possibilty of the typescript
file being passed with option -s and the divisor as a direct argument,
but it's good enough for my taste.

Regards,

Benno

-- 
http://www.fastmail.fm - Same, same, but different...