[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Path length in GEM file selector

To: mint-request@terminator.rs.itd.umich.edu (Nicholas S Castellano)
Subject: Re: Path length in GEM file selector
From: Julian Reschke <reschke@GOEDEL.UNI-MUENSTER.DE>
Date: Fri, 21 Jan 94 1:04:38 MET DST
Cc: mint@terminator.rs.itd.umich.edu (MiNT-Liste)
In-reply-to: <199401202251.RAA15499@terminator.rs.itd.umich.edu>; from "Nicholas S Castellano" at Jan 20, 94 5:51 pm
Organization: Westfaelische Wilhelms-Universitaet, Muenster, Germany Department of Mathematics

> 
> >From: moacs11!walra@relay.NL.net (Waldi Ravens)
> >In <9401201204.AA13974@urix6.uni-muenster.de>, Marcus Haebler wrote:
> >> there is a little problem with the path length in GEM programs if
> >> you use the normal length of 128 Bytes, this is quite small for
> >> Minix FSs etc. Should we set path length to 1024 like BSD does?
> >Since P1003.1 does not define a maximum length for a path, no application
> >should assume that there is one. You'll have to use something more
> >flexible than a compile time constant.
> 
> Unfortunately P1003.1 *does* specify a minimum acceptable value of 255
> for the path length.  MiNT obviously doesn't meet this requirement.
> 
> Can this value be changed in MiNT without patching GEMDOS?
> 
> -entropy

GEMDOS itself doesn't have any lenght limits at all (the only critical
call is Dgetpath(), and this is using the user's buffer).

-- 
---------------------------------------------------
Julian F. Reschke, Hensenstr. 142, D-48161 Muenster
 eMail: reschke@math.uni-muenster.de jr@ms.maus.de
___________________________________________________

References:
- Path length in GEM file selector
  - From: "Nicholas S Castellano" <entropy@terminator.rs.itd.umich.edu>

Prev by Date: Path length in GEM file selector
Next by Date: Re: Cookie Cache
Previous by thread: Path length in GEM file selector
Next by thread: Re: Path length in GEM file selector
Index(es):
- Date
- Thread