Another idea, just in case the "drive-path" wasn't fancy enough for you.
I noticed that I used "DRIVE_Path_#" for the "drive:" path, and "ELF_Path_#" for the "elf:" path. How about some sort of naming scheme like that, that lets you define ANY path name? "FOOBAR_Path_1 = mass:/foo/bar" would define the first path for "foobar:". Maybe it would have to be changed to something like "Path_FOOBAR_1" to make sure it didn't interfere with any other directives, but you get the idea (the closest directive we have to that is "path1_OSDSYS_ITEM_1", etc.). You could then have "Path_FMCB_1", "Path_FMCB_2", etc, pre-defined to give the "fmcb:" that was suggested.
The user would just have to be sure he doesn't define, say "Path_MC0_#", or "Path_MASS_#", etc. Or do something like this:
or this:Code:Path_BOOT_1 = apps: Path_APPS_1 = boot:
Code:Path_BOOT_1 = boot: