X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
Date: Thu, 27 Dec 2001 11:55:34 +0200 (WET)
From: Andris Pavenis <pavenis AT lanet DOT lv>
X-Sender: pavenis AT ieva06
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Cc: djgpp-workers AT delorie DOT com
Subject: Re: lfn from scratch...
In-Reply-To: <5832-Wed26Dec2001215442+0200-eliz@is.elta.co.il>
Message-ID: <Pine.A41.4.05.10112271151560.29944-100000@ieva06>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk



On Wed, 26 Dec 2001, Eli Zaretskii wrote:

> > Date: Wed, 26 Dec 2001 13:17:28 -0500
> > From: DJ Delorie <dj AT delorie DOT com>
> > 
> > The first drive checked is *always* the non-lfn one, because I can't
> > change to that drive before starting bash (or other djgpp programs).
> > So I can't even say "well, start with the lfn one and just never use
> > the others, and we'll get by."
> 
> Why do you have to change to a drive at all?  You are mapping a
> Unix-style filesystem into DOS drive letters, right?  So all you
> should need is some data structure that maps the root of each drive to
> a Unix directory, and something that says what is the current drive.
> How does changing drives enter this picture?

DOSEMU can access disk either using Linux filesystem support or by direct
access to partition (never tried the latest). In the first one LFN support
could be possible, in other one it could be much more difficult to proved
it by DOSEMU. 

> 
> > So it seems that for the non-lfn drives, I need to emulate the lfn
> > api, at least in a dumb way (by calling the non-lfn api in its place).
> 
> That would be the best strategy, I think.  NTLFN does that, and it
> works well.
> 

Perhaps so

Andris