Currently, setup-1.7 installs a version of xhost (1.0.2-1) that is not
compiled properly for IPv6 protocol support.
When querying against an IPv6 X server IPv6 addresses are not recognized.
The fix for this is to simply rebuild the xhost package.
However, to get it to work at all with the
Ok, just verified that the xserver running on the desktop crashes with
the following scenario:
Xserver on a dual display desktop (windows xp, cygwin), running wmaker
as the window manager.
I connect remotely to the desktop from a laptop(xp, cisco vpn) mstsc.exe
to the desktop.
I can see the
CVSROOT:/cvs/uberbaum
Module name:winsup
Changes by: c...@sourceware.org 2009-08-04 22:35:35
Modified files:
cygwin : ChangeLog fhandler_socket.cc net.cc path.cc
path.h
Log message:
* fhandler_socket.cc
CVSROOT:/cvs/uberbaum
Module name:winsup
Changes by: c...@sourceware.org 2009-08-05 03:18:48
Modified files:
cygwin : ChangeLog path.h
Log message:
* path.cc (patch_conv::check): Zero path before setting it.
Patches:
CVSROOT:/cvs/uberbaum
Module name:winsup
Changes by: c...@sourceware.org 2009-08-05 04:44:29
Modified files:
cygwin : ChangeLog cygheap.h debug.cc dtable.cc
Log message:
* cygheap.h (cygheap_debug::endh): Delete.
* debug.cc
I just noticed one of those annoying black boxes when running X on
Windows 7. I don't think I ever tried to run X there before.
The first release of Cygwin which was supposed to fix this problem
was 1.7.0-51 but I can't even run X with that version.
Have the console windows always been showing
On 04/08/2009 01:04, Christopher Faylor wrote:
I just noticed one of those annoying black boxes when running X on
Windows 7. I don't think I ever tried to run X there before.
The first release of Cygwin which was supposed to fix this problem
was 1.7.0-51 but I can't even run X with that
2009/8/4 Christopher Faylor:
I just noticed one of those annoying black boxes when running X on
Windows 7. I don't think I ever tried to run X there before.
The first release of Cygwin which was supposed to fix this problem
was 1.7.0-51 but I can't even run X with that version.
Have the
I just noticed that for several cygwin1.dll versions git svn is not
working. Here's the repo I can reproduce it with and cygcheck -s -r:
http://kitsu.ru/cygwin17-psyco2-git.tar.bz2
http://kitsu.ru/cygwin17-psyco2-cygcheck.log.gz
aborzen...@ng-ws0212
Jay K wrote:
Friend also found freesshd works and will use that.
So 3 out of 4 sshd work, Cygwin sshd is the only one that doesn't.
Wrong. That is uninformed speculation and guesswork. Stop spreading
misinformation.
Cygwin SSHD has had the support for fully logging in as any user since
X11 forwarding has to be enabled on the server. If it's not, then any
request by the client to forward X connections (due to -X or -Y
options or ForwardX11 in ~/.ssh/config or /etc/ssh_config or wherever)
will be ignored.
Check the sshd_config on the final host (the work computer).
--
Problem
On Tue, Aug 04, 2009 at 09:30:22AM +0100, Andy Koppe wrote:
2009/8/4 Christopher Faylor:
I just noticed one of those annoying black boxes when running X on
Windows 7. ??I don't think I ever tried to run X there before.
The first release of Cygwin which was supposed to fix this problem was
On Tue, Aug 04, 2009 at 12:49:03AM -0400, Christopher Faylor wrote:
On Mon, Aug 03, 2009 at 11:42:40PM -0400, Christopher Faylor wrote:
On Mon, Aug 03, 2009 at 09:21:35PM -0600, Jim Reisert AD1C wrote:
I removed the *56* release file from my Cygwin install directory and
tried a re-install. Now in
2009/8/4 Christopher Faylor:
On Mon, Aug 03, 2009 at 11:35:25PM -0500, Yaakov (Cygwin/X) wrote:
On 01/08/2009 15:10, Christopher Faylor wrote:
I have uploaded a new Cygwin 1.7 test release, 1.7.0-56.
This fixes the bug introduced in -53 and -54 which resulted in various
problems execing
On Tue, Aug 04, 2009 at 04:26:40PM +0200, Reini Urban wrote:
2009/8/4 Christopher Faylor:
On Mon, Aug 03, 2009 at 11:35:25PM -0500, Yaakov (Cygwin/X) wrote:
On 01/08/2009 15:10, Christopher Faylor wrote:
I have uploaded a new Cygwin 1.7 test release, 1.7.0-56.
This fixes the bug introduced in -53
/
fatal: write error (Socket operation on non-socket)
$ uname -a
CYGWIN_NT-5.1 eblake 1.7.0s(0.212/5/3) 20090804 00:31:58 i686 Cygwin
Running the above through strace generates more than half a
megabyte, but the point where 'errno 108' occurs in the trace
is shortly after a call to dup2(3,4), so
The ls can't show file problem and vim go back forground problem seems fixed.
2009/8/4 Christopher Faylor cgf-use-the-mailinglist-ple...@cygwin.com
On Tue, Aug 04, 2009 at 12:49:03AM -0400, Christopher Faylor wrote:
On Mon, Aug 03, 2009 at 11:42:40PM -0400, Christopher Faylor wrote:
On Mon,
On 04/08/2009 05:27, Andrew DeFaria wrote:
mcoughlin wrote:
Well it is good to know that it is doable.
My computer is running Windows Vista, the middle computer runs Red Hat
3, and the work computer runs Red Hat 4.
ssh -X computer #2
Warning: untrusted X11 forwarding setup failed: xauth key
with the 20090804 snapshot.
--
Eric Blake
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
p7zip is the Unix port of 7-Zip, a file archiver that archives
with very high compression ratios.
p7zip provides /usr/bin/7zr, a standalone minimal version of the
7-zip tool that only handles 7z archives. It also provides
/usr/bin/7za, a statically-linked application that supports packing
and
p7zip is the Unix port of 7-Zip, a file archiver that archives
with very high compression ratios.
p7zip provides /usr/bin/7zr, a standalone minimal version of the
7-zip tool that only handles 7z archives. It also provides
/usr/bin/7za, a statically-linked application that supports packing
and
behavior of
git, I haven't seen anything else misbehave with the 20090804 snapshot.
Does that mean you don't see the problem with the 20090704 snapshot or
that you haven't tested that far back?
I'll try this command out as soon as I can.
cgf
--
Problem reports: http://cygwin.com/problems.html
On Tue, Aug 04, 2009 at 11:10:07PM +0800, Huang Bambo wrote:
2009/8/4 Christopher Faylor wrote:
Did anyone test this? ?This snapshot fixes some memory corruption
introduced by the recent change to reduce the size of some in-memory
filename structures.
The ls can't show file problem and vim go
Rather than stripping our exe's and dll's I suggest to strip the debug
info into
seperate /usr/lib/debug/path/file.dbg and package them seperately in -debuginfo
packages such as with fedora.
On any error which requires user-side debugging these symbols can be used
by gdb (--symbols=SYMFILE)
2009/8/4 Christopher Faylor:
On Tue, Aug 04, 2009 at 04:26:40PM +0200, Reini Urban wrote:
2009/8/4 Christopher Faylor:
On Mon, Aug 03, 2009 at 11:35:25PM -0500, Yaakov (Cygwin/X) wrote:
On 01/08/2009 15:10, Christopher Faylor wrote:
I have uploaded a new Cygwin 1.7 test release, 1.7.0-56.
This
On Tue, Aug 04, 2009 at 09:06:00PM +0200, Reini Urban wrote:
2009/8/4 Christopher Faylor:
On Tue, Aug 04, 2009 at 04:26:40PM +0200, Reini Urban wrote:
2009/8/4 Christopher Faylor:
On Mon, Aug 03, 2009 at 11:35:25PM -0500, Yaakov (Cygwin/X) wrote:
On 01/08/2009 15:10, Christopher Faylor wrote:
I
Just want to point out a slightly difference in behavior of ksh
@(#)PD KSH v5.2.14 99/07/13.2
between Cygwin 1.5 1.7 First, the above is a older version of pdksh
that I had to tweek the cygwin sources a l-o-n-g time ago. Under 1.5,
the following does work properly:
$ cd
On Tue, Aug 4, 2009 at 4:08 PM, Paul McFerrin wrote:
Just want to point out a slightly difference in behavior of ksh
@(#)PD KSH v5.2.14 99/07/13.2
OK, please don't assume that (1) what you're seeing is happening for
everyone, or (2) it was intentional (you are forcing me *A LOT* of
extra
Paul McFerrin wrote:
Just want to point out a slightly difference in behavior of ksh
@(#)PD KSH v5.2.14 99/07/13.2
between Cygwin 1.5 1.7 First, the above is a older version of pdksh
that I had to tweek the cygwin sources a l-o-n-g time ago. Under 1.5,
the following does work properly:
Paul McFerrin wrote:
Just want to point out a slightly difference in behavior of ksh
@(#)PD KSH v5.2.14 99/07/13.2
between Cygwin 1.5 1.7 First, the above is a older version of pdksh
that I had to tweek the cygwin sources a l-o-n-g time ago. Under 1.5,
the following does work properly:
_setlocale_r isn't really reentrant, is it? It invokes loadlocale(),
which writes to the global function pointers __mbtowc and __wctomb,
i.e. there's a single global locale setting.
Its man page needs to be corrected:
`_localeconv_r' and `_setlocale_r' are reentrant versions of
Dave: Let's put this prob on hold for a while. At least til I
investigate it some more. Something is acting weird. This prob has
disappeared! I tried unloading everything just in case some name cache
had it already expanded. I did get correct results from using latest
pdksh. Weird.
Hello all,
I am unable to build the source package cygwin-1.5.25-15-src.tar.bz2.
Making earlier versions was ok before, but now I am unable to build
any version at all. I've tried -15, -14, and -12. They all produce
the same error when linking cygcheck.exe.
These two patches are applied if
a new
failure in the latest snapshot. Other than this weird behavior of
git, I haven't seen anything else misbehave with the 20090804 snapshot.
Does that mean you don't see the problem with the 20090704 snapshot or
that you haven't tested that far back?
I'll try this command out as soon as I can
Zip is an open-source, command-line alternative to other zip-format
archives such as WinZip, etc. zip-3.0 is the latest release from
Info-Zip, http://www.info-zip.org/pub/infozip/Zip.html.
This is a packaging bugfix and feature release. It supports large
files ( 2GiB) and unicode file names.
UnZip is an open-source, command-line alternative to other zip-format
archives such as WinZip, etc. unzip-6.0 is the latest release from
Info-Zip, http://www.info-zip.org/pub/infozip/UnZip.html.
This is a major feature release. It supports large files ( 2GiB)
and unicode file names.
This
This problem has already been reported on 7/22/2009 9:37 PM, but I think to
have found the reason for it.
Unfortunately I am not able to put together a patch; -- never done one.
What follows is the message I get when running updatedb:
assertion ent-fts_info == FTS_NSOK || state.type != 0
I believe this is a non-problem. The cause: human error. Doing a
cd /c/Doc*/pa*/App*is not the same as
cd /c/Doc*/Pa*/App*
Wildcard lookups are always case sensitive. I must not have been
consistant when switching between Windows.
Paul McFerrin wrote:
Dave: Let's put this prob
I downloaded the 4 Aug cygwin1.dll from the test area:
http://cygwin.com/snapshots/
8/04/2009 20:34 2,464,724 cygwin1.dll
This one is even worse than -56, I can't even get uname to work:
d:\cygwin\binuname -a
1 [main] uname 1800 _cygtls::handle_exceptions: Exception:
I tried to bunzip the snapshot and get the following:
~
$ bunzip2.exe cygwin1-20090804.dll.bz2
bunzip2: Data integrity error when decompressing.
Input file = cygwin1-20090804.dll.bz2, output file =
cygwin1-20090804.dll
It is possible that the compressed file(s) have become corrupted
On 03/08/2009 23:53, Christopher Faylor wrote:
Well, at least this time there was cygcheck output. However, other than
showing that you're running Windows 7, I don't see anything too useful.
So, it looks likely that who reports a bug is going to be SOL unless
you can show me how to duplicate
On 08/04/2009 07:43 PM, Jerry DeLisle wrote:
I tried to bunzip the snapshot and get the following:
~
$ bunzip2.exe cygwin1-20090804.dll.bz2
bunzip2: Data integrity error when decompressing.
Input file = cygwin1-20090804.dll.bz2, output file =
cygwin1-20090804.dll
It is possible
I screwed up the previous cygwin-20090804 snapshot but there is a new
one up now which shouldn't produce a STATUS_EXCEPTION_VIOLATION.
Sorry for the inconvenience with the previous one.
cgf
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq
On 08/04/2009 08:27 PM, Christopher Faylor wrote:
I screwed up the previous cygwin-20090804 snapshot but there is a new
one up now which shouldn't produce a STATUS_EXCEPTION_VIOLATION.
Sorry for the inconvenience with the previous one.
This one installs and runs fine now on NT 4.
Jerry
p7zip is the Unix port of 7-Zip, a file archiver that archives
with very high compression ratios.
p7zip provides /usr/bin/7zr, a standalone minimal version of the
7-zip tool that only handles 7z archives. It also provides
/usr/bin/7za, a statically-linked application that supports packing
and
p7zip is the Unix port of 7-Zip, a file archiver that archives
with very high compression ratios.
p7zip provides /usr/bin/7zr, a standalone minimal version of the
7-zip tool that only handles 7z archives. It also provides
/usr/bin/7za, a statically-linked application that supports packing
and
UnZip is an open-source, command-line alternative to other zip-format
archives such as WinZip, etc. unzip-6.0 is the latest release from
Info-Zip, http://www.info-zip.org/pub/infozip/UnZip.html.
This is a major feature release. It supports large files ( 2GiB)
and unicode file names.
This
47 matches
Mail list logo
