Path: utzoo!attcan!darkover!nebulus!contact!ben From: ben@contact.uucp (Ben Eng) Newsgroups: comp.sys.amiga Subject: Re: csa & cba postings Keywords: filename length limitations Message-ID: <1990Jan21.004454.9373@contact.uucp> Date: 21 Jan 90 05:44:54 GMT References: <75826@tut.cis.ohio-state.edu> <870@pccuts.pcc.amdahl.com> Reply-To: ben@contact.UUCP (Ben Eng) Distribution: na Organization: Jet Penguin Lavatories Lines: 28 In article <870@pccuts.pcc.amdahl.com> acs@pccuts.pcc.amdahl.com (Tony Sumrall) writes: >In article <75826@tut.cis.ohio-state.edu> Jeff Martens writes: >>An operating system should be able to handle a descriptive file name. > >Who says you can't be descriptive within a 14-character limit? This site is running under the most recent version of Xenix and it can't handle long filenames either. I am getting the impression that there is a significant number of sites that are plagued by this limitation. While we are on the topic of improvements to comp.sources.amiga, would it not be a good idea to distribute the source code as a shar'ed-uuencoded-zoo archive, rather than as straight source code? It would certainly cut down on net bandwidth (smaller size), preserve full pathnames, preserve long filenames, and ensure data integrity. If a zoo file is not desirable then I would certainly like to see a MANIFEST file to go along with each distribution, so that when the files are unshar'ed, there is some way to check that all the files are properly extracted. By the way, "Thanks!" to Tad for a great job so far. Ben -- Ben Eng | ben@contact.uucp _or_ ben@ziebmef.mef.org 150 Beverley St. Apt #1L | Bix: jetpen ^^^-down for repair? Toronto, Ontario M5T 1Y6 | UofT Engineering Science: engb@ecf.toronto.edu _-_-_-_-_-_-_-_-_-_-_-_-_| Phone: (416)-979-7885, (416)-979-8761