Documented tackiness, that's a new one... :)
Nix, Robert P. wrote:
Did that. It shows $ALLOC$(0,0) as an overlap, and MAINT and SYSDUMP1(0,10016)
as an overlap, and .DRCT.(1,20) as an overlap. The rest of the disks are not
flagged. However, where I defined the other disks on the first-level system,
they show a gap the size of the disk. 510RES should show a gap following the
last defined minidisk, but does not.
Found the problem while I was typing this. In the :EXCLUDES. Section, the doc
says that an address can be one to four digits. But later, it says that address
represents the LEFT-MOST digits of an address. A trailing asterisk, OR
SPECIFICATION OF LESS THAN FOUR DIGITS implies that all addresses starting with
the specified are considered excluded.
Everywhere else in the system, an address can be specified by its significant
digits. One take on this is that I should have read further. (which is true...)
But another take could be that common usage should have been followed,
especially when the asterisk is allowed in the syntax anyway, so a three digit
address wouldn't be ambiguous.
Changing the excluded address from 123 to 0123 solved the problem. Personally,
I think that's fairly tacky, but then the tackiness is documented, so I guess I
don't really have a valid complaint....
Sorry to bother everyone. Back to work...
--
Robert P. Nix Mayo Foundation
RO-CE-8-857 200 First Street SW
507-284-0844 Rochester, MN 55905
-----
"In theory, theory and practice are the same, but
in practice, theory and practice are different."
--
Rich Smrcina
VM Assist, Inc.
Main: (262)392-2026
Cell: (414)491-6001
Ans Service: (360)715-2467
rich.smrcina at vmassist.com
Catch the WAVV! http://www.wavv.org
WAVV 2006 - Chattanooga, TN - April 7-11, 2006
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
