Date: Thu, 12 Oct 2006 13:54:16 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: [ANNOUNCEMENT] Updated: vim-7.0.122-1
Message-ID: <20061012115416.GB8323@calimero.vinschen.de>
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>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20061012111836.GA29649@trixie.casa.cgf.cx>
User-Agent: Mutt/1.4.2i
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Oct 12 07:18, Christopher Faylor wrote:
> On Thu, Oct 12, 2006 at 08:55:23AM +0200, Corinna Vinschen wrote:
> >On Oct 11 13:10, mwoehlke wrote:
> >> Dave Korn wrote:
> >> >... although I can see problems arising when someone uses mount to rename 
> >> >the
> >> >cygdrive mount.  Maybe it would be worth providing a notation that means
> >> >'cygdrive, no matter how it may have been renamed.
> >
> >This sounds like a good idea to me.  Scripts in the distro relying on
> >the cygdrive path could use it.  There's also the problem that different
> >users could use different cygdrive prefixes.
> >
> >> Hmm, how about /dev/fs/<driveletter>? ;-)
> >
> >What about /proc/cygdrive/<driveletter>?
> 
> A filesystem under /dev or /proc is not very linux-like.
> 
> If this is really needed (which I'm not convinced is really true) why
> don't we just hardwire /cygdrive?  The mount option could still allow
> referencing drives via some other path but /cygdrive could still be
> available.

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.

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.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
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/