From mint-bounce@lists.fishpool.fi Tue Feb 7 15:33:38 2006 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Subject: Re: [MiNT] change of max. allowed path From: Petr Stehlik To: mikro Cc: mint@fishpool.com In-Reply-To: <20060207133110.GA20415@hysteria.sk> References: <20060207113831.GB1380@hysteria.sk> <20060207124550.GA29899@hysteria.sk> <20060207133110.GA20415@hysteria.sk> Content-Type: text/plain; charset=ISO-8859-2 Date: Tue, 07 Feb 2006 15:27:59 +0100 Message-Id: <1139322479.11383.12.camel@petr.sophics> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: joy@sophics.cz 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: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by wh58-508.st.uni-magdeburg.de id k17EXbvp018533 mikro píše v Út 07. 02. 2006 v 14:31 +0100: > currently. Maybe you remember my post I'm (still) not able to delete path > which is longer than 255 characters... You replied mintlib doesn't use any > static fields for paths but it seems some restrictions are still present. How about giving us a simple program in C that creates deep path (or long filename, or what's the problem) and then tries to delete it. Should be only a few lines. Test it and then make it available both as source and binary so that others can test under the same conditions and perhaps experience the problem you describe. Petr