Date: Sat, 18 Sep 1999 14:57:26 -0700 From: Doug <Doug@gorean.org> To: John-Mark Gurney <gurney_j@resnet.uoregon.edu> Cc: Sheldon Hearn <sheldonh@FreeBSD.ORG>, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/etc pccard_ether rc rc.atm rc.devfs rc.diskless1 rc.diskless2 rc.firewall rc.isdn rc.network rc.pccard rc.resume rc.shutdown rc.suspend security src/etc/etc.alpha MAKEDEV rc.alpha src/etc/etc.i386 MAKEDEV rc.i386 src/etc/isdn answer i Message-ID: <37E40AC6.B2D21A06@gorean.org> References: <199909131544.IAA26697@freefall.freebsd.org> <19990917235139.61698@hydrogen.fircrest.net>
next in thread | previous in thread | raw e-mail | index | archive | help
John-Mark Gurney wrote: > > Sheldon Hearn scribbled this message on Sep 13: > > builtin and (as a side-effect) allows case-insensitivity. > > I thought it was agreed that this is UNIX and case-insensitivity is a > BAD thing... that it shoul stay case sensitive... This was discussed at length on -hackers. Unfortunately, I learned after the project already had approval that some people would prefer to have these issues discussed on -committers. Aside from the virtue of using case, which is a builtin vs. using test/[ which is not; using case allows us to make the tests case insensitive. This is an aid in reducing the learning curve for new users, which is especially important in those areas where a simple, honest mistake can cause serious problems for the user. > why don't we make our file systems case-insensitive next? No one is suggesting such a radical change. My feeling, and the feelings of others is that we should do what we can in areas that are not crucial to make things easier for new users, while at the same time we bring them along slowly to the unix way of doing things. Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?37E40AC6.B2D21A06>