Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com Date: Wed, 3 May 2000 13:43:30 -0400 Message-Id: <200005031743.NAA26680@envy.delorie.com> From: DJ Delorie To: earnie_boyd AT yahoo DOT com CC: cygwin-developers AT sourceware DOT cygnus DOT com In-reply-to: <20000503171211.3492.qmail@web117.yahoomail.com> (message from Earnie Boyd on Wed, 3 May 2000 10:12:11 -0700 (PDT)) Subject: Re: /cygdrive/windows ? References: <20000503171211 DOT 3492 DOT qmail AT web117 DOT yahoomail DOT com> > I get it now, sorry. Hmm... How about an internal mapping of /boot for the > SystemDrive, /boot/windir for the windows path? Since the System and System32 > directories always fall as subdirectories of /boot/windir this wouldn't have to > be mapped. So, for example, if you have your WINNT system on the C: drive then > /boot would be mapped to C:/ and /boot/windir would map to C:/WINNT. If Windows is installed to a shared network drive, windir is local and sysdir is shared. I think. Otherwise, I can't think of why Win32 has separate calls for those two directories.