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

Igor Peshansky pechtcha@cs.nyu.edu
Thu Apr 3 17:23:00 GMT 2008


On Thu, 3 Apr 2008, Corinna Vinschen wrote:

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

I agree that the path to the root dir is not needed -- I never argued with
that.  It's the "override the /bin dir" functionality that I was worried
about.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_	    pechtcha@cs.nyu.edu | igor@watson.ibm.com
ZZZzz /,`.-'`'    -.  ;-;;,_		Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-'		old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"That which is hateful to you, do not do to your neighbor.  That is the whole
Torah; the rest is commentary.  Go and study it." -- Rabbi Hillel



More information about the Cygwin-developers mailing list