From mint-bounce@lists.fishpool.fi Sun Oct 23 22:38:36 2005 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Date: Sun, 23 Oct 2005 22:35:16 +0200 (CEST) From: Frank Naumann X-X-Sender: fnaumann@wh58-508.st.uni-magdeburg.de To: Mint List Subject: Re: [MiNT] problem with long filename In-Reply-To: <435BA35D.4060001@hysteria.sk> Message-ID: References: <435A5043.5030200@hysteria.sk> <435BA35D.4060001@hysteria.sk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scan-Signature: 8f557e09c6f25d1c731b1614156185f1 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: fnaumann@boerde.de Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: X-Virus-Scanned: by amavisd-new at relay.boerde.de X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on relay.boerde.de X-Spam-Status: No, hits=-0.9 tagged_above=-50.5 required=7.0 tests=AWL, BAYES_00 X-Spam-Level: Hello! >> Any ideas what to do? I can't believe FreeMiNT allowed me to create such >> long name and then can handle shorter ones only. >> > no one? I've tried Dpathconf() to see what's the current filename limit - it > returned 255 for both ext2 and fat32! (the filesystems where I created that > undeletable files). I've got such feeling somewhere in mint(lib) sources is > defined maximum value of 128 for some buffer(s) and then really bad things > happen if the file if >= 128 characters long - some check will say "yeah, no > problem, let's create it" and some other function will use only 128 bytes > long buffer... but this is just a guess... maybe someone more experienced > could explain this... MiNTLib had such limitations some time ago. I think I removed all of this. Against which mintlib is your bash linked? Regards, Frank -- ATARI FALCON 060 // MILAN 060 ----------------------------------------- http://www.cs.uni-magdeburg.de/~fnaumann/ e-Mail: fnaumann@freemint.de