Volume Mount Points

No, but perhaps data migration (HCSS) can help you.
HCSS is a data storage system that extends the storage capacity of a NetWare server by integrating an optical disc library, or jukebox, into the NetWare file system.
This allows you to see ALL files in one directory but some files are stored in the current drive and someothers are residing in a low speed media, like a jukebox.
If this may help you, you can read more about this at:
http://www.novell.com/documentation/lg/nw4/docui/index.html#../superenu/data/hvychdnx.html

edt@bancobgn.com

Use the directory map object in nwadmin.

Create a directory map in your subdirectory, and when asked for it's "true" volume name, you would browse to the other volume.

An alias, created on the original volume, but pointing to the other wouldalso work.

Inherited rights get a little tricky at this point.

I thought that was what I explained. In Nwadmin, or console1d

for example, you have 2 file servers, with 3 volumes each

FS-One_sys
FS-One_Apps
FS-One_Data
FS-Two_sys
FS-Two_Apps
FS-Two_Data

You would have to map 4 drive letters to seeboth sets of Apps and Data Drives correct?

Create an aliased volume in the same OU

FS-One_Directory

Using Directory Mapping, you create 4 subdirectories in FS-one_Directory

FS-One_Directory
........One_Apps
........One_Data
........Two_Apps
........Two_Data

One drive mapping will allow users to see all 4 Directories, and the "real directories" as are physically present on the drive. ( if they have rights to see those directories )

ie, a user is mapped to K: at the workstation, and opens the drive in my computer. He sees 4 folders

One_apps, One_data, Two_apps, Two_data

double clicks on One_apps, and the directories appear, just as they would if you had mapped One_apps directly.

Brother Bradley,

I have pondered your pseudo-DFS solution for a couple of minutes and decided to try it on my 5.00sp5 NDS 8.5 box. I'm afraid this doesn't work, unless I'm suffering from a perception problem...

Directory Maps exist only as ameans to create a "share point" that exists in the directory, not in the file system itself (though they do show up in Network Neighborhood). They can be thought of as a dynamic file system entity to which static drives may be mapped (ie. from a login script) by referencing an object located in or out of the default context. I attempted to create a DM beneath the proposed Aliased volume - I have only one of two choices: I can create a directory or a file, not a DM. Perhaps you could provide us with a screenshot, I'd really like to implement your suggestion, but it just ain't happenin' here!

Thanks,

solis