Re: [HEADSUP] Let's start a Cygwin 1.7 release area

[Corinna Vinschen <corinna-cygwin@cygwin.com>]

On Apr  3 17:38, Corinna Vinschen wrote:
> On Apr  3 11:16, Igor Peshansky wrote:
> > On Thu, 3 Apr 2008, Corinna Vinschen wrote:
> > > [snip]
> > > > >>>   Get own path   ==> C:\\cygwin\\bin\\cygwin1.dll
> > > > >>>   Where's fstab? ==> C:\\cygwin\\etc\\fstab
> > > > >>
> > > > >> So, it implicitly computes where / is?
> > > > >
> > > > >No, it doesn't.  It just snips away the last two path components and
> > > > >tacks the etc/fstab string on.  Plus the .$SID to get the user mounts.
> > > > >
> > > > >After the mount points have been read, root can potentially be
> > > > >somewhere else entirely.
> > 
> > So would it make sense to put the root mount info in the same directory as
> > cygwin1.dll?  I know it doesn't belong in /bin, but playing with relative
> > paths is even more error-prone.
> 
> I don't understand this.  As discussed somewhat later, if the root dir
> follows automatically from where the DLL itself resides.  Which, btw.,
> [...]

Looks like I distracted myself while replying.

What I was trying to say is, if the root dir is taken automatically
from the path of the DLL, there is no reason to have the path to the 
root dir stored anywhere, isn't it?


Corinna

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