Auto-mounts are mounted only as they are accessed, and are unmounted after a period of inactivity.
Because of this, automounting NFS/Samba shares conserves bandwidth and offers better overall performance compared to static mounts via fstab. Indirect maps, such as those in the auto.master file shown above, create-mount points as subdirectories inside the main mount-point.
Remember, the mount points specified here will be relative to the mount point given in /etc/auto.master.
Following the example directory structure above, if you were to enter ls /nfs into a shell, you might be surprised to see nothing listed.
But remember that you need to access a directory before it is auto-mounted. Once it has been accessed, your share will be listed only until it times out.
I've installed a minimal installation of Red Hat 9 in VMware Workstation 5.5.3 and it worked fine.
As a test, I installed Fedora 7 i386 in a VMware server instance, then modified the CPU architecture of the hosted virtual machine to be 64-bit.If you keep in mind that TKL v12.x is based on Debian perhaps you can find smoething via google?OTTOMH you should be able to test that your fstab entry is valid by running And if that works then I strongly suspect that it's as I mentioned above...By permanently labeling the partitions on the boot disk, the system should be able to continue to boot normally, even if the disk is moved to another controller or transferred to a different system.autofs is a program for automatically mounting directories on an as-needed basis.