delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2006/10/12/08:10:22

X-Spam-Check-By: sourceware.org
Date: Thu, 12 Oct 2006 08:09:57 -0400
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: [ANNOUNCEMENT] Updated: vim-7.0.122-1
Message-ID: <20061012120957.GA30160@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <452D2696 DOT 3060602 AT users DOT sourceforge DOT net> <014c01c6ed5b$d6a1e9a0$a501a8c0 AT CAM DOT ARTIMI DOT COM> <egjc38$teg$1 AT sea DOT gmane DOT org> <20061012065523 DOT GP13105 AT calimero DOT vinschen DOT de> <20061012111836 DOT GA29649 AT trixie DOT casa DOT cgf DOT cx> <20061012115416 DOT GB8323 AT calimero DOT vinschen DOT de>
Mime-Version: 1.0
In-Reply-To: <20061012115416.GB8323@calimero.vinschen.de>
User-Agent: Mutt/1.5.11
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Thu, Oct 12, 2006 at 01:54:16PM +0200, Corinna Vinschen wrote:
>I think it is needed.  At least the base-files-mketc.sh postinstall
>script creates paths which point outside the Cygwin root, so it either
>needs to reference cygdrive paths, or use DOS paths.  Using cygdrives
>paths is preferable, IMHO.  Since the cygdrive path is not fixed, and
>can even differ between different users on the same machine, there must
>be a fixed method to reference these paths.

If we're pointing outside of the Cygwin root then we can either 1) use a
mount or (in the current scenario) 2) establish a standard way to access
the windows directory.  My mild objection is that we're talking about
modifying the Cygwin DLL to accommodate the Cygwin distribution.  A
standalone Cygwin program doesn't necessarily need to use /etc/hosts but,
if we are modifying cygwin1.dll to hard-wire a path, it will nonetheless
have to suffer the consequences of that decision.

>Personally I'd rather not further clutter the root directory, which is
>why /proc seems to me to be a better place to point to the cygdrive
>paths in a constant fashion.  But that is only a mild opposition.  I'd
>also go along with /cygdrive.

We're already cluttering the root one less than linux since modern linuxes
use /dev, /proc, and /sys.

Hmm.  /sys/drive/c  has a nice feel to it, although this is YA a case where
the existence of a filesystem under this directory is not linux-like.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019