On Tue, Jan 02, 2001 at 10:57:29AM +1100, Robert Collins wrote: >Ah, so you see the future? > >Seriously, there are programs that CANNOT change where their files go >and still operate - and when they collide with cygwin, goodbye cygwin | >goodbye those programs. > >Are you saying the FAQ entry is wrong or misleading or hard to >understand? > >I think it is accurate and the suggestion should be made as it is. I >do not think it is misleading. Perhaps it could be clearer as to the >reasons for the recommendation - do you have some suggested text to put >there? (As I wasn't confused by it I am stumped with respect to >understanding the confusion). Big ditto. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple
- why not use root as root? Gerrit P. Haase
- Re: why not use root as root? Anthony & Yinkwan
- Re: why not use root as root? Gerrit P. Haase
- Re: why not use root as root? Robert Collins
- Re: why not use root as root? Christopher Faylor
- Re: why not use root as root? Gerrit P. Haase
- Re: why not use root as root? Robert Collins
- Re: why not use root as ro... Christopher Faylor
- Re: why not use root as ro... Larry Hall (RFK Partners, Inc)
- Re: why not use root ... Earnie Boyd
- Re: why not use root as ro... Gerrit P. Haase
- RE: why not use root as root? Robert Collins
- Re: why not use root as root? Christopher Faylor
- Re: why not use root as root? Earnie Boyd
- Re: why not use root as root? Tim Prince
- Re: why not use root as ro... Gerrit P. Haase
- Re: why not use root as ro... Earnie Boyd
- Re: why not use root as root? Tim Prince