From owner-freebsd-questions Sun Mar 1 20:46:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA08481 for freebsd-questions-outgoing; Sun, 1 Mar 1998 20:46:52 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from lariat.lariat.org (ppp1000.lariat.org@lariat.lariat.org [129.72.251.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA08475 for ; Sun, 1 Mar 1998 20:46:47 -0800 (PST) (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.lariat.org (8.8.8/8.8.8) id VAA07787; Sun, 1 Mar 1998 21:46:27 -0700 (MST) Message-Id: <3.0.5.32.19980301214604.00b55100@mail.lariat.org> X-Sender: brett@mail.lariat.org X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Sun, 01 Mar 1998 21:46:04 -0700 To: "Jesse T Kipp" From: Brett Glass Subject: Re: MS-DOS file system: Can it handle FAT32? Long file names? Cc: questions@FreeBSD.ORG In-Reply-To: References: <3.0.5.32.19980301145433.00a2e3b0@mail.lariat.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:02 PM 3/1/98 -0600, zaphod wrote: >As for at I know, FreeBSD doesn't support FAT32 systems. It can read FAT16 >file systems with long name support (AKA VFAT) but if a file was like >THEFILENAME it will appear as THEFIL~1 because window 95 keeps an internal >record of the long file names. Not so. The record is on the disk in special directory entries; the file system simply needs to know how to read them! It's not hard to do, and the details of the scheme are not secret. >Don't alter THEFIL~1 while in FreeBSD, >because windows isn't good about handling such errors (it assumes that >nothing else will access the file system, I guess...). Actually, all that will happen is that the long version of the name may be invalidated, in which case Windows 95 will see the file as having its short name only. This *can* be a problem, though, if a program is relying upon seeing the long file name. Again, it's not hard to keep the short and long names in sync! The name-mangling scheme is documented, as is the scheme for storing long names. I'd be glad to help whoever is hacking this code to implement the relevant extensions. >(p.s. it would be nice if you could get a mail client that puts line >breaks every 60 columns so mail doesn't appear as one long line for some >of us... ;)...) More and more, applications are shifting from the "line-oriented" paradigm (in which lines are explicitly terminated by line breaks) to the "paragraph-oriented" paradigm (in which text flows to the end of the paragraph unless hard line breaks are included). The latter paradigm is part of HTML as well as most GUI wordprocessors, and is incorporated into most e-mail programs. Any e-mail client should be able to wrap long "lines" if necessary. What are you using to read your mail? If it doesn't know how to handle the paragraph-oriented paradigm, it'd probably be a good idea to fix it! Netscape, Eudora, AOL, and the many Web-based e-mail services aren't going to go back to line-oriented text, so we should write tools that recognize and handle the equally valid paragraph-oriented model. --Brett Glass P.S. -- I've *tried* to force Eudora to insert hard returns into this message, but don't know if it'll work. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message