Re: checking in >= 256k file fatally corrupts rcs file

2013-10-08 Thread Warren Young
On 10/8/2013 20:08, Gary Johnson wrote: There was a discussion around March 27, 2012, about another change in the behavior of RCS between 5.7 and 5.8. It appears that someone decided to make some sweeping "improvements" to RCS and broke a few things along the way. GNU rcs 5.7 was released in

Re: checking in >= 256k file fatally corrupts rcs file

2013-10-08 Thread Gary Johnson
On 2013-10-08, Warren Young wrote: > On 10/8/2013 18:30, Don Hatch wrote: > >On Tue, Oct 08, 2013 at 05:48:53PM -0600, Warren Young wrote: > >>On 10/8/2013 04:22, Don Hatch wrote: > >>> > >>>Checking in a text file of size >= 256k > >>>corrupts the rcs file, irretrievably losing most of the content

Re: checking in >= 256k file fatally corrupts rcs file

2013-10-08 Thread Warren Young
On 10/8/2013 18:30, Don Hatch wrote: On Tue, Oct 08, 2013 at 05:48:53PM -0600, Warren Young wrote: On 10/8/2013 04:22, Don Hatch wrote: Checking in a text file of size >= 256k corrupts the rcs file, irretrievably losing most of the contents It's documented in the rcs NEWS file: That quote

Re: checking in >= 256k file fatally corrupts rcs file

2013-10-08 Thread Don Hatch
On Tue, Oct 08, 2013 at 05:48:53PM -0600, Warren Young wrote: > On 10/8/2013 04:22, Don Hatch wrote: > > > >Checking in a text file of size >= 256k > >corrupts the rcs file, irretrievably losing most of the contents > > It's documented in the rcs NEWS file: > > - Env var RCS_MEM_LIMIT control

Re: checking in >= 256k file fatally corrupts rcs file

2013-10-08 Thread Warren Young
On 10/8/2013 04:22, Don Hatch wrote: Checking in a text file of size >= 256k corrupts the rcs file, irretrievably losing most of the contents It's documented in the rcs NEWS file: - Env var RCS_MEM_LIMIT controls stdio threshold. For speed, RCS uses memory-based routines for files

Re: transfering cygwin configuration from win XP to win 7

2013-10-08 Thread Chris Olin
I recently did this at work by backing up the C:\cygwin directory, my Windows user profile directory and manually creating the directory path C:\cygwin\etc\setup, then copying C:\cygwin\etc\setup\installed.db to the new computer, running the installer, and changing the install method from "Default"

Re: fixing BLODA-caused fork failures

2013-10-08 Thread Ryan Johnson
On 08/10/2013 3:34 PM, Larry Hall (Cygwin) wrote: On 10/8/2013 3:25 PM, David Boyce wrote: But as a point of practicality, 64-bit Cygwin can help with some cases of DLL address space collisions. So if you haven't experimented with 64-bit Cygwin in your environment, it may be worth your time.

Re: baffling cygwin setup.exe behavior

2013-10-08 Thread Ryan Johnson
On 08/10/2013 2:52 PM, Don Hatch wrote: I've always been baffled by cygwin setup's behavior. I wish I understood it and could control it. Here is a typical example where I want to do something very simple and I have no idea how to get the setup program to do it. Help! My goal: upgrade rcs to t

Re: fixing BLODA-caused fork failures

2013-10-08 Thread Larry Hall (Cygwin)
On 10/8/2013 3:25 PM, David Boyce wrote: But as a point of practicality, 64-bit Cygwin can help with some cases of DLL address space collisions. So if you haven't experimented with 64-bit Cygwin in your environment, it may be worth your time. This sounds very reasonable but I'm curious: is it

Re: fixing BLODA-caused fork failures

2013-10-08 Thread David Boyce
> But as a point of practicality, 64-bit Cygwin can help with some cases of > DLL address space collisions. So if you haven't experimented with > 64-bit Cygwin in your environment, it may be worth your time. This sounds very reasonable but I'm curious: is it to date just a theory that makes sense

Re: baffling cygwin setup.exe behavior

2013-10-08 Thread Larry Hall (Cygwin)
On 10/8/2013 2:52 PM, Don Hatch wrote: So, as far as I can see, the only way to get rcs 5.8.2-1 is to globally select "Curr" and *don't click on rcs at all*. So, to upgrade rcs and nothing else, I'd have to globally select "Curr" and manually change every package *except* rcs to "Keep", leavin

Re: RANCID on Cygwin

2013-10-08 Thread David Stacey
On 08/10/2013 14:53, Jakub Horbacewicz wrote: I have to use Windows server for making backups of network devices. To accomplish that I have to run Rancid, so I need to install Cygwin. Can you help me with compiling Rancid through Cygwin? I cannot find any tutorial or tips in google. If you down

baffling cygwin setup.exe behavior

2013-10-08 Thread Don Hatch
I've always been baffled by cygwin setup's behavior. I wish I understood it and could control it. Here is a typical example where I want to do something very simple and I have no idea how to get the setup program to do it. Help! My goal: upgrade rcs to the "currently considered most stable" vers

Re: /etc/screenrc issue on cygwin64

2013-10-08 Thread Andrew Schulman
> > > Hi cygwin, > > I have found that two lines in /etc/screenrc cause the nano editor to get one > line off in its text buffer display when running gnu screen in a mintty > terminal on cygwin64. The two lines are as follows (the ones beginning with > "termcap" and "terminfo"): > > ># Do no

Re: RANCID on Cygwin

2013-10-08 Thread Ryan Johnson
On 08/10/2013 9:53 AM, Jakub Horbacewicz wrote: Hello, I have to use Windows server for making backups of network devices. To accomplish that I have to run Rancid, so I need to install Cygwin. Can you help me with compiling Rancid through Cygwin? I cannot find any tutorial or tips in google. Hop

RANCID on Cygwin

2013-10-08 Thread Jakub Horbacewicz
Hello, I have to use Windows server for making backups of network devices. To accomplish that I have to run Rancid, so I need to install Cygwin. Can you help me with compiling Rancid through Cygwin? I cannot find any tutorial or tips in google. Regards. -- Problem reports: http://cygwin.co