From owner-freebsd-hackers Thu Sep 18 08:43:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA13566 for hackers-outgoing; Thu, 18 Sep 1997 08:43:02 -0700 (PDT) Received: from usr03.primenet.com (tlambert@usr03.primenet.com [206.165.6.203]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA13558 for ; Thu, 18 Sep 1997 08:42:58 -0700 (PDT) Received: (from tlambert@localhost) by usr03.primenet.com (8.8.5/8.8.5) id IAA13488; Thu, 18 Sep 1997 08:42:07 -0700 (MST) From: Terry Lambert Message-Id: <199709181542.IAA13488@usr03.primenet.com> Subject: Re: CDROM image To: md6tommy@mdstud.chalmers.se (Tommy Hallgren) Date: Thu, 18 Sep 1997 15:42:06 +0000 (GMT) Cc: tlambert@primenet.com, jkh@time.cdrom.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Tommy Hallgren" at Sep 18, 97 10:03:58 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > In Windows95 everything looked fine. But in Linux(which I used back then) > > > every filename was in lower case. :-( > > > > In Windows95, long file names are case sensitive on storage, case > > insensitive on lookup. I believe lowercasing them was an acessability > > hack in the CDROM driver on Linux. > > They are lower case using FreeBSD too. :-( FreeBSD doesn't, so far as I know, support Joliet, which is what would be require to put out Windows 95 long file names. I think it's only putting out standard ISO9660 or "High Sierra" long names, which are monocased. Linux, on the other hand, is actually monocasing it. So they are doing the right thing to get the names, but the wrong thing once they have them. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.