From mint-bounce@lists.fishpool.fi  Sun Feb 19 23:04:36 2006
X-Original-To: fnaumann@mail.boerde.de
Delivered-To: fnaumann@mail.boerde.de
From: "Roger Burrows" <anodyne@cyberus.ca>
Organization: Anodyne Software
To: MiNT List <mint@fishpool.com>
Date: Sun, 19 Feb 2006 16:57:15 -0500
MIME-Version: 1.0
Subject: [MiNT] PATH_MAX in mintlib
Message-ID: <43F8A36B.12086.C2A303@localhost>
Priority: normal
X-mailer: Pegasus Mail for Windows (v4.02a)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body
X-ecartis-version: Ecartis v1.0.0
Sender: mint-bounce@lists.fishpool.fi
Errors-To: mint-bounce@lists.fishpool.fi
X-original-sender: anodyne@cyberus.ca
Precedence: bulk
List-help: <mailto:ecartis@lists.fishpool.fi?Subject=help>
List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
List-Id: <mint.lists.fishpool.fi>
X-List-ID: <mint.lists.fishpool.fi>
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=3.0 tagged_above=-50.5 required=7.0 tests=AWL,
 BAYES_00, RCVD_IN_SORBS
X-Spam-Level: **

Hi!
While browsing the mintlib sources (0.57.6), I noticed that PATH_MAX was 128.  
This mostly seems to be used in conjunction with _unx2dos()/_dos2unx(), so I 
suppose that for a TOS FAT16 filesystem, this may not be a real problem.

However symbolic link support (symlink/readlink) also uses PATH_MAX as the 
maximum symlink size:

1. symlink.c: if we try to create a symbolic link > 128 bytes, a truncated 
value will be stored in the link.

2. readlink.c: fails if a symbolic link is more than 128 bytes long.

Roger Burrows