X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Matthew Woehlke Subject: Re: [ANNOUNCEMENT] Updated: vim-7.0.122-1 Date: Thu, 12 Oct 2006 12:49:25 -0500 Lines: 35 Message-ID: References: <452D2696 DOT 3060602 AT users DOT sourceforge DOT net> <014c01c6ed5b$d6a1e9a0$a501a8c0 AT CAM DOT ARTIMI DOT COM> <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> <20061012120957 DOT GA30160 AT trixie DOT casa DOT cgf DOT cx> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.7) Gecko/20060909 Thunderbird/1.5.0.7 Mnenhy/0.7.4.0 In-Reply-To: <20061012120957.GA30160@trixie.casa.cgf.cx> X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Christopher Faylor wrote: > 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. I still like /dev/fs :-), or maybe /sys/fs. Perhaps /sys/fs/os should point to %SYSTEMDIR%? (Or /sys/fs/windows, or - except it sounds redundant - /sys/fs/sys.) -- Matthew "I don't question your existence -- God" (seen on a church billboard) -- 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/