AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20071031130701.6836c174@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<eric.barrett@onstor.com>,<chris.vandever@onstor.com>,<dl-Customer-Engineering@onstor.com>,<dl-designreview@onstor.com>,<charissa.willard@onstor.com>,<brian.deforest@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#mh/Mailbox/design review	0	BB375AF679D4A34E9CA8DFA650E2B04E0648DE70@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Wed, 31 Oct 2007 13:10:26 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Eric Barrett" <eric.barrett@onstor.com>
Cc: "Chris Vandever" <chris.vandever@onstor.com>, "dl-Customer-Engineering"
 <dl-Customer-Engineering@onstor.com>, "dl-Design Review"
 <dl-designreview@onstor.com>, "Charissa Willard"
 <charissa.willard@onstor.com>, "Brian DeForest" <brian.deforest@onstor.com>
Subject: Re: Hostnames, Filer Names, and Cluster Names... Case Sensitive or
 Not?
Message-ID: <20071031131026.660aad42@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E0648DE70@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E03E9A407@onstor-exch02.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E0648DE70@onstor-exch02.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

I'm deeply saddened by the pervasiveness and perversity of Microsoft
[read: brain-dead] thinking in this area.  Of course we should allow
case sensitive host/filer, vsrv, and other object names (vsrv names
always should have been - that is a bug).  If you go around trying to
dumb everything down, then only dumb users will want to use the product.
Next thing people will be suggesting is that we limit object names to
8.3 format.  Sheesh.

Even Microsoft had to cave in and change their filesystem to support
case sensitive file names.  Otherwise, all you have is a system only a
preschooler wants to use.

What we *should* do, however, is have the GUI, which *does* have the
job of keeping the user from shooting themselves in the foot, warn the
user if they are trying to specify a new volume, vsrv, hostname, etc.
that might be too similar -- say, differs only by case -- to an already
existing object of the same type, and require confirmation that they
really want to do this inadviseable action.  Something like a little
page that says "You already have a volume named vol1, do you really
want another volume named Vol1?  If in doubt, answer 'No'."  Would
suffice.  But we should not take possibly desired functionality out of
the hands of those that want to use it just because the vocal minority
manage to find a way to hurt themselves with it.

Cheers,

a

On Wed, 31 Oct 2007 12:18:05 -0700 "Eric Barrett"
<eric.barrett@onstor.com> wrote:

> Well, I filed at least one of those :)  My $0.02 is the bugs stand as
> is.  Hostnames should not be case-sensitive, especially since virtual
> servers (which one could think of as "sub-hosts") are not.
> 
> I don't know of any customer who currently expects hostnames to be
> case sensitive, but doesn't mean there isn't one.
> 
> 
> > _____________________________________________ 
> > From: 	Chris Vandever  
> > Sent:	Wednesday, October 31, 2007 11:52 AM
> > To:	dl-Customer-Engineering; dl-Design Review
> > Cc:	Charissa Willard; Brian DeForest
> > Subject:	Hostnames, Filer Names, and Cluster Names... Case
> > Sensitive or Not?
> > 
> > We have two ECRs we'd like to get some feedback on:
> > 
> > *	#17831 (Gateway names should be case-insensitive)
> > *	#11325 ("vsvr move -f filername" is case sensitive, "vsvr
> > set vsvrname" is not)
> > 
> > Currently, filer names and cluster names are case sensitive, just
> > like the underlying hostname on which they are based in BSD.  Vsvr
> > names and CIFS share names are case insensitive, and are converted
> > to upper case before they are stored in the cluster database.
> > 
> > Convenience would dictate that filer names and cluster names be case
> > insensitive.  However, that imposes restrictions that do not exist
> > for the underlying hostnames in BSD.  Do we have customers who rely
> > on the names being case sensitive?  What do customers expect?
> > 
> > Thoughts?
> > 
> > ChrisV & Charissa
> > 
