On Wed, Jul 9, 2008 at 12:28 PM, Drew Van Zandt <[EMAIL PROTECTED]> wrote:
> On 7/9/08, Labitt, Bruce <[EMAIL PROTECTED]> wrote: >> > Anyone got any >> > suggestions? Pitfalls on how I am thinking about things? >> > > > It seems to me that using any of the "traditional" mount points in this > situation is somewhat inappropriate; the new drive is intended primarily as > a resource for another machine. Given that, Thomas' suggestion of > /bladeimages is a pretty sensible one. I tend to mount shared net drives on > mountpoints like "/share", or mount a RAID on /raid, make a directory called > "share" on it, and share that directory. It makes it obvious what physical > resource is associated with the mountpoint, and you can use symlinks to > organize things in a logical sense. > > I dislike the /mnt suggestion because to me, /mnt is for a foreign > filesystem, e.g. something that might be removed. On the blade server, > however, I'd probably mount the shared net filesystem under /mnt, for > reasons mentioned in VAB's reply. > Just to throw a few more wrenches... Solaris uses /export for file systems that will be exported on NFS. /export/home is for home directories. /opt is for 3rd part packages. /mnt and /home are used by automount to mount NFS file systems from servers I'm using /misc on my Linux boxes where Solaris has /mnt /media on Fedora linux is for CDs, USB drives. I think Ubuntu uses it too. Solaris uses /cdrom, /floppy and probably /usb.
_______________________________________________ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
