Copyright (C) 2000-2012 |
GNU Info (am-utils.info)Architecture SharingArchitecture Sharing ==================== Often a filesystem will be shared by machines of different architectures. Separate trees can be maintained for the executable images for each architecture, but it may be more convenient to have a shared tree, with distinct subdirectories. A shared tree might have the following structure on the fileserver (called `fserver' in the example): local/tex local/tex/fonts local/tex/lib local/tex/bin local/tex/bin/sun3 local/tex/bin/sun4 local/tex/bin/hp9000 ... In this example, the subdirectories of `local/tex/bin' should be hidden when accessed via the automount point (conventionally `/vol'). A mount-map for `/vol' to achieve this would look like: /defaults sublink:=${/key};rhost:=fserver;type:=link tex type:=auto;fs:=${map};pref:=${key}/ tex/fonts host!=fserver;type:=nfs;rfs:=/vol/tex \ host==fserver;fs:=/usr/local/tex tex/lib host!=fserver;type:=nfs;rfs:=/vol/tex \ host==fserver;fs:=/usr/local/tex tex/bin -sublink:=${/key}/${arch} \ host!=fserver;type:=nfs;rfs:=/vol/tex \ host:=fserver;fs:=/usr/local/tex When `/vol/tex/bin' is referenced, the current machine architecture is automatically appended to the path by the `${sublink}' variable. This means that users can have `/vol/tex/bin' in their `PATH' without concern for architecture dependencies. |