Adding a new drive / fstab

[Ben Scott]

On Wed, Jul 9, 2008 at 11:50 AM, Labitt, Bruce
<labittb1 at tycoelectronics.com> wrote:
> ... I would like the drive to be the "home" for my linux image for
> my blade server.

  Use what works for you.

  Me, I use /mnt for "temporary" mount points.  Things like floppies
and CDs, flash drives, network filesystems I'm temporarily mounting
for whatever reason, that sort of thing.

  In organizations (companies), I try to build an org-wide directory
structure under a top-level name.  For example, if I work for Acme
Products, I'd have </acme> off the root, and structure things under
there.  If I was in the materials lab at Acme, and I was building a
blade server called "darkstar", I might use </acme/matlab/darkstar/>.
If I was hosting multiple system images, or thought I might do so, I
might use </acme/matlab/hosts/darkstar/> or something like that.

  This has the advantage in that the corporate IT resource server can
be mounted under </acme/it/pub/>, centralized home directories under
</acma/home/>, the software lab's source code under
</acma/softlab/svn/>, or whatever.  You get a consistent structure
everywhere.

  That may be total gigantic overkill for what you're doing.  Maybe
you just want </darkstar/>, or </hosts/darkstar/>.

  The FHS that V. Alex Brennen references actually states that </mnt/>
is for temporary mounts; the location for stuff you're serving out
would be under </srv/>.  So maybe </srv/darkstar/> or whatever.

  I would recommend against just </blade/>, because then when you get
your second blade server, confusion occurs.  Use unique names.

    But use what works for you.

-- Ben