This is the mail archive of the
mailing list for the Cygwin project.
Re: [ANNOUNCEMENT] Updated: vim-7.0.122-1
On Oct 12 08:09, 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.
> establish a standard way to access the windows directory
Yes, that's something which annoys me rather often. I'm usually creating
a symlink to /mnt/c/WINDOWS directory in / (which nicely contradicts
my statement about cluttering the root dir...), but that requires the
cygdrive directory to stay /mnt. It would be a rather good idea, IMHO,
to have a constant POSIX path pointing to the system directory and,
maybe, even to the "Ducuments and Setting" directory.
> >Personally I'd rather not further clutter the root directory, which is
Yes, yes, I said that.
> 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.
There's a precedent for valid paths in /proc, though. Think of the
virtual symlinks in /proc/<pid> like "cmd", "exe", "root". Why not
use another part of /proc for a similar purpose. There's also
/proc/registry which comes to mind as a vaguely similar approach.
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html