From mint-bounce@lists.fishpool.fi Sun Oct 23 16:54:51 2005 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Message-ID: <435BA35D.4060001@hysteria.sk> Date: Sun, 23 Oct 2005 16:51:09 +0200 From: Miro Kropacek User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051011) X-Accept-Language: sk, en-us, en MIME-Version: 1.0 Cc: Mint List Subject: Re: [MiNT] problem with long filename References: <435A5043.5030200@hysteria.sk> In-Reply-To: <435A5043.5030200@hysteria.sk> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: mikro@hysteria.sk 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=-1.0 tagged_above=-50.5 required=7.0 tests=BAYES_00 X-Spam-Level: >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... -- ---------------------------------------------------------------------------- MiKRO Atari XE/XL/Mega STE/Falcon060 http://mikro.atari.org ----------------------------------------------------------------------------