Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Date: Fri, 16 Jun 2000 12:01:42 -0400
From: Christopher Faylor <cygwin AT sourceware DOT cygnus DOT com>
To: cygwin AT sourceware DOT cygnus DOT com
Subject: Re: Problems with new ci.exe and co.exe
Message-ID: <20000616120142.H1165@cygnus.com>
Reply-To: cygwin AT sourceware DOT cygnus DOT com
Mail-Followup-To: cygwin AT sourceware DOT cygnus DOT com
References: <F614BF868E0DD411A5A700508B957E0038D037 AT MSGBOS679NTS DOT fmr DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <F614BF868E0DD411A5A700508B957E0038D037@MSGBOS679NTS.fmr.com>; from Steve.Tolkin@fmr.com on Fri, Jun 16, 2000 at 10:27:21AM -0400

On Fri, Jun 16, 2000 at 10:27:21AM -0400, Tolkin, Steve wrote:
>Dear group, especially Rod W., Chris F., and Uwe S. (who will get this as
>direct email as well as via the list)

There is no reason to send me email directly.  I obviously read the
cygwin mailing list.  I don't need to have duplicates in my mailbox.

>Uwe avoided that bug becase he mounted everything as binmode.
>But I had to mount c: as textmode to work around a "Permission denied"
>problem I got when running gcc (which invoked cpp), rcsdiff (which invoked
>co and diff), and sort.

As I have previously indicated, I have never heard of anyone solving a
"permission denied" error by changing to text mode.

>I generally try to minimize the disturbances to me system.  But here I can
>change up to four independent variables.  I would like your collective
>advice about this.
>Here are the possibilities:
>1. Change from release 1.1.1 to 1.1.2.  I plan to do this, but first I would
>like to see the detailed description of the line endings bug above.

Read ChangeLog entries for newlib for a detailed description or go
through a few weeks worth of cygwin mailing list where people were
complaining about the problem.

As the announcement said, it fixes problems with not translating CRLF
line endings correctly.  If you are having problems with CRLF line
endings showing up in your files then I have a hard time understanding
why you would go to the effort of composing a long email message rather
than updating your DLL.  Backup your directories if you think that
updating will have a catastrophic effect.

>2. Change from textmode to binmode for C:/  I may try this, to see if I am
>still getting "Permission denied".  But even if that problem is gone it
>seems strange to mount this binmode when many of the files on that drive are
>text.  Someone also mentionned that it seemed very odd that I had e.g.
>/usr/bin mounted in binmode but that / was textcode

There is nothing wrong with mounting / as text mode assuming that you
understand what you're doing.

>3. Change the root of the cygwin installation from C:/ to C:/cygwin   
>I originally chose to install cygwin into the root directory i.e.  c:/
>Later I read somewhere that this is not recommended, and it recommended
>installing into e.g.  c:/cygwin.  But it did not give the reasons, or
>the pros and cons of each.  I will change this if someone can explain
>to me why I should.

Again, the mailing list archives are your friend.

If you don't want to install in c:\cygwin there is no reason why you should
have to.  Basically, it just encapsulates all of the cygwin stuff in one
directory.

>4. Change from the original ci.exe and co.exe I have been running to the new
>versions provided by Uwe. (Later maybe can also try to compile them  myself,
>and then apply the patches and compile again).
>
>An important extra question:  Currently my $HOME is /usr/home and I have a
>lot of files there.  I am concerned that a new install might somehow damage
>(i.e. remove) things below /usr.  Should I for safety's sake do something
>like
>mv /usr/home /_myhome
>HOME=/_myhome

For safety's sake, if you are concerned about losing things, you should backup
your files and not rely on supposition from people in a mailing list.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com