On Tue, Sep 15, 2009 at 5:34 PM, Judy Anderson wrote:
> Emacs is not bothering its little head about cygwin, though; I'm launching it
> outside
> the cygwin environment.
Then that's a completely separate emacs installation. You should be
able to run the Cygwin one by just creating a shortcut to
a shortcut that calls
bash to launch emacs. Thanks for the pointer.
-Original Message-
From: Lee [mailto:ler...@gmail.com]
Sent: Monday, September 14, 2009 1:09 PM
To: cygwin@cygwin.com
Subject: Re: Strange tar error with --format=ustar: value 4294967295 out of
gid_t range 0..2097
On 9/14/09, Judy Anderson wrote:
.. snip ..
> Except on my usual development machine, where I get the error:
>
> E:\yduJ> c:\cygwin\bin\tar cf foo.tar --format=ustar foo
> /usr/bin/tar: value 4294967295 out of gid_t range 0..2097151
> /usr/bin/tar: Exiting with failure status due to previous err
I need to send a collection of files to a Z/OS machine from a windows machine.
When we were on Windows 2000, we just used "pax". But apparently Microsoft has
discontinued pax in Win2003. So we searched for a solution. Cygwin tar SAID
it would produce pax format files, but the Z/OS machine do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Mike Dieter on 11/2/2006 3:26 PM:
> tar version: 1.15.91
>
> I am using Cygwin (see attachment for facts) on an IBM XP home edition.
Cygwin now ships with tar 1.16; consider upgrading.
>
> $ tar -ztvf C:/download/Majordomo.tar.gz
> C:
0, windows pid 2353940, Win32 error 5
> 4 tar: child process: Cannot fork
> 5 tar: Error is not recoverable: exiting now
That is not a bug in tar, but cygwin telling you that Windows limitations
made it impossible to fork. Try a recent cygwin snapshot to see if that
helps your situation. If n
147 [main] tar 2344 C:\cygwin\bin\tar.exe: *** fatal error - fork:
> can't reserve memory for stack 0x23EBE0 - 0x24, Win32 error 487
> 3 7 [main] tar 1372 child_copy: stack write copy failed,
> 0x23EBE0..0x24, done 0, windows pid 2353940, Win32 error 5
> 4 tar:
#x27;t
reserve memory for stack 0x23EBE0 - 0x24, Win32 error 487
3 7 [main] tar 1372 child_copy: stack write copy failed,
0x23EBE0..0x24, done 0, windows pid 2353940, Win32 error 5
4 tar: child process: Cannot fork
5 tar: Error is not recoverable: exiting now
The folder /cygdriv
Larry Hall wrote:
> More seriously, did you try the same with a snapshot?
Now I did. I installed the 5/24 snapshot, same result.
Jeremiah Lott
TimeSys Corporation
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Docum
Christopher Faylor wrote:
On Thu, May 25, 2006 at 02:10:44PM -0400, Larry Hall (Cygwin) wrote:
Lott, Jeremiah wrote:
I'm having a problem extracting a tar that contains the device node
/dev/ptmx (character device 5,2). Tar creates the file, then segfaults.
I originally detected this with a rat
On Thu, May 25, 2006 at 02:10:44PM -0400, Larry Hall (Cygwin) wrote:
>Lott, Jeremiah wrote:
>>I'm having a problem extracting a tar that contains the device node
>>/dev/ptmx (character device 5,2). Tar creates the file, then segfaults.
>>I originally detected this with a rather large tar created o
Lott, Jeremiah wrote:
I'm having a problem extracting a tar that contains the device node
/dev/ptmx (character device 5,2). Tar creates the file, then segfaults.
I originally detected this with a rather large tar created on a linux
machine. However, this can be re-produced entirely on cygwin as
I'm having a problem extracting a tar that contains the device node
/dev/ptmx (character device 5,2). Tar creates the file, then segfaults.
I originally detected this with a rather large tar created on a linux
machine. However, this can be re-produced entirely on cygwin as in the
following transc
13 matches
Mail list logo
