From owner-freebsd-hackers Tue Sep 10 10:48:07 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA00628 for hackers-outgoing; Tue, 10 Sep 1996 10:48:07 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA00622 for ; Tue, 10 Sep 1996 10:48:04 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA03079; Tue, 10 Sep 1996 10:46:28 -0700 From: Terry Lambert Message-Id: <199609101746.KAA03079@phaeton.artisoft.com> Subject: Re: iname() To: e8917523@linf.unb.br Date: Tue, 10 Sep 1996 10:46:28 -0700 (MST) Cc: hackers@freefall.freebsd.org In-Reply-To: <9609100135.AA0141@DANIEL.sobral> from "Daniel C. Sobral" at Sep 10, 96 04:35:53 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > This fails for VFAT/VFAT32/HPFS/NTFS, all of which have "long names" > > > and 8.3 names for each file. For the Mac FS, it fails because of the > > Err... This does not seem to be the case for HPFS. At least, OS/2 > makes names that don't fall into 8.3 convention invisible to DOS > sessions and can't even copy those files to FAT (you have to provide > a new, acceptable, name). Of course, not knowing the internals of > OS/2, it may be just that IBM is too stupid to provide a useful > resource already coded into the system available to its users... :-) It is a limitation of the broswer and the INT 21 supporting code, not an inherent limitation of the HPFS itself. Sorry I didn't make this clear. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.