Re: [ITP] mingw-w64 Second try
On 8/25/2010 8:14 PM, JonY wrote: On 8/25/2010 12:19, JonY wrote: since cygport and gcc has been updated, I can do the packaging without any local hacks. Ping. Less than a single day is a bit quick to ping. I'll take a look at this tonight or tomorrow; thanks for your hard work. -- Chuck
Re: [ITP] mingw-w64 Second try
On 8/26/2010 22:21, Charles Wilson wrote: On 8/25/2010 8:14 PM, JonY wrote: On 8/25/2010 12:19, JonY wrote: since cygport and gcc has been updated, I can do the packaging without any local hacks. Ping. Less than a single day is a bit quick to ping. I'll take a look at this tonight or tomorrow; thanks for your hard work. Sorry, no rush intended. I'm having a bit of a long day here and might have gotten confused about when the itp was sent.
Re: Postinstall script error
On 25/08/2010 03:46, noggin wrote: Here is a slice from setup.log 2010/08/23 23:47:07 running: C:\cygwin\bin\bash.exe --norc --noprofile /etc/postinstall/fltk.sh 2010/08/23 23:48:01 running: C:\cygwin\bin\bash.exe --norc --noprofile /etc/postinstall/libglade2.0.sh 2010/08/23 23:48:03 abnormal exit: exit code=2 2010/08/23 23:48:03 running: C:\cygwin\bin\bash.exe --norc --noprofile /etc/postinstall/obconf.sh A workaround for this problem is reported at [1] mkdir -p /etc/xml edit /etc/postinstall/libglade2.0.sh to add --create /etc/postinstall/libglade2.0.sh [1] http://sourceware.org/ml/cygwin-xfree/2010-08/msg00074.html -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Unable to start XWin with --nolock
I am having trouble starting XWin on my system. It complains about being unable to read lock the file -- okay, so it resides on a FAT32 drive, no big. Just add --nolock to my command line and move on. But it doesn't work. But it does. But doesn't. I AM able to run XWin from inside cygwin's bash prompt: $ xinit -- -nolock -multiwindow $ startxwin -- -nolock But I can NOT run Xwin from a Windows command prompt or a Start Menu shortcut: /cygwin/bin/run.exe /usr/bin/bash.exe -l -c /usr/bin/xinit -- -nolock -multiwindow /cygwin/bin/run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin -- -nolock In these cases I am given the read-lock error, and: XWin was started with the following command line: X :0 In other words, I am unable to pass my command-line options to XWin, so I cannot work around the error. Did I overlook something? What do I do next? -- Stratadrake strata_ran...@hotmail.com Numbers may not lie, but neither do they tell the whole truth. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Unable to start XWin with --nolock
On 26/08/2010 18:18, Richard Gitschlag wrote: I am having trouble starting XWin on my system. It complains about being unable to read lock the file -- okay, so it resides on a FAT32 drive, no big. Just add --nolock to my command line and move on. But it doesn't work. But it does. But doesn't. I AM able to run XWin from inside cygwin's bash prompt: $ xinit -- -nolock -multiwindow $ startxwin -- -nolock But I can NOT run Xwin from a Windows command prompt or a Start Menu shortcut: /cygwin/bin/run.exe /usr/bin/bash.exe -l -c /usr/bin/xinit -- -nolock -multiwindow /cygwin/bin/run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin -- -nolock In these cases I am given the read-lock error, and: XWin was started with the following command line: X :0 In other words, I am unable to pass my command-line options to XWin, so I cannot work around the error. Did I overlook something? What do I do next? You need to quote the command after -c to prevent bash assuming those options are meant for itself. This has been answered a few times before, e.g. at [1] I'm not sure if you arrived at using -nolock from reading FAQ 3.4 [2], perhaps I need to improve that FAQ to give more guidance. [1] http://sourceware.org/ml/cygwin-xfree/2010-04/msg00026.html [2] http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-cant-read-lock-file -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: CygwinX Users Guide
On 20/08/2010 01:21, noggin wrote: Tried to print the PDF version of the guide, August 19 1700h. All screenshots are displaced off the right-hand side. Change magnification and they are still displaced. Thanks for reporting this issue. This document seems to have been this way forever. I've tweaked the docbook source so these images should be scaled to fit in the PDF output, and rebuilt and uploaded the documentation. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: CygwinX Users Guide
Jon, not on my time scale ! Its equivalent in 2003 was OK... I'll have to check 2005 and 2006 when I get back into the lab !! I have our graduate students build CygwinX in order to access the Cambridge Structural Database on a Fedora-Linux box. Needless to say, from Micros**t Windows... Nick On 10.08.26, Jon TURNEY jon.tur...@dronecode.org.uk wrote: On 20/08/2010 01:21, noggin wrote: Tried to print the PDF version of the guide, August 19 1700h. All screenshots are displaced off the right-hand side. Change magnification and they are still displaced. Thanks for reporting this issue. This document seems to have been this way forever. I've tweaked the docbook source so these images should be scaled to fit in the PDF output, and rebuilt and uploaded the documentation. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
src/winsup/cygwin ChangeLog fhandler_proc.cc
CVSROOT:/cvs/src Module name:src Changes by: cori...@sourceware.org 2010-08-26 10:59:13 Modified files: winsup/cygwin : ChangeLog fhandler_proc.cc Log message: * fhandler_proc.cc (format_proc_partitions): Simplify code and enable partition layout printing for non-privileged users. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/ChangeLog.diff?cvsroot=srcr1=1.5009r2=1.5010 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/fhandler_proc.cc.diff?cvsroot=srcr1=1.90r2=1.91
src/winsup/utils ChangeLog cygpath.cc
CVSROOT:/cvs/src Module name:src Changes by: cori...@sourceware.org 2010-08-26 12:06:29 Modified files: winsup/utils : ChangeLog cygpath.cc Log message: * cygpath.cc (get_device_name): Prefer the \\.\X: DOS device for harddisks, if available. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/utils/ChangeLog.diff?cvsroot=srcr1=1.538r2=1.539 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/utils/cygpath.cc.diff?cvsroot=srcr1=1.61r2=1.62
Re: res_send() doesn't work with osquery enabled
- Original Message -
From: Corinna Vinschen
To: cygwin-patches
Sent: Thursday, August 26, 2010 12:38
| Pierre, would you mind to take a look?
|
| On Aug 26 19:07, pse...@egg6.net wrote:
| Currently res_init() checks for availability of the native windows
| function DnsQuery_A. If the function is found, it's preferred over the
| cygwin implementation and res_query is set up to use it.
| As DnsQuery_A finds the configured name servers itself, the current code
| assumes we can avoid loading the dns server list with GetNetworkParams().
|
| However, the assumption that everybody would use res_query is wrong. Some
| programs may use res_mkquery() and res_send() or may only read the list of
| servers from _res.nsaddr_list and send/receive the queries/replies
| themselves. res_send() also relies on nsaddr_list.
It's true that the behavior described above is legitimate, even if nobody had
ever
requested it. If people want to access nsaddr_list after calling res_ninit,
loading
iphlpapi.dll every time (as the patch does) is unavoidable.
The other change has res_nsend return an error if no server can be found.
Alternatively the error could be reported by res_ninit, by removing the second
condition in
if (statp-nscount == 0 !statp-os_query) {
errno = ENONET;
statp-res_h_errno = NETDB_INTERNAL;
Hypothetically this could affect some installations where iphlpapi doesn't
report any
servers although the Windows resolver can find a server (but I don't see how
this
could happen), so it's safer to proceed as in the patch.
However the patch should send errno to ENONET and set res_h_errno to
NETDB_INTERNAL
Except for the previous comment, I am fine with the patch.
Pierre
Re: res_send() doesn't work with osquery enabled
On Aug 26 13:16, Pierre A. Humblet wrote:
- Original Message -
From: Corinna Vinschen
To: cygwin-patches
Sent: Thursday, August 26, 2010 12:38
| Pierre, would you mind to take a look?
|
| On Aug 26 19:07, pse...@egg6.net wrote:
| Currently res_init() checks for availability of the native windows
| function DnsQuery_A. If the function is found, it's preferred over the
| cygwin implementation and res_query is set up to use it.
| As DnsQuery_A finds the configured name servers itself, the current code
| assumes we can avoid loading the dns server list with GetNetworkParams().
|
| However, the assumption that everybody would use res_query is wrong. Some
| programs may use res_mkquery() and res_send() or may only read the list of
| servers from _res.nsaddr_list and send/receive the queries/replies
| themselves. res_send() also relies on nsaddr_list.
It's true that the behavior described above is legitimate, even if nobody had
ever
requested it. If people want to access nsaddr_list after calling res_ninit,
loading
iphlpapi.dll every time (as the patch does) is unavoidable.
The other change has res_nsend return an error if no server can be found.
Alternatively the error could be reported by res_ninit, by removing the second
condition in
if (statp-nscount == 0 !statp-os_query) {
errno = ENONET;
statp-res_h_errno = NETDB_INTERNAL;
Hypothetically this could affect some installations where iphlpapi doesn't
report any
servers although the Windows resolver can find a server (but I don't see how
this
could happen), so it's safer to proceed as in the patch.
However the patch should send errno to ENONET and set res_h_errno to
NETDB_INTERNAL
Except for the previous comment, I am fine with the patch.
IIRC you have checkin rights, Pierre. Please apply whatever you
think is right.
Thanks,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
Re: linux-cygwin cross build environment
On Thu, Aug 26, 2010 at 10:53 AM, Charles Wilson cyg...@cwilson.fastmail.fm wrote: Last weekend I attempted to setup a linux-cygwin cross compiler (and basic sysroot). However, it didn't work: while a simple C 'Hello World' app could be compiled, copied over to a win32 system and executed, a C++ 'Hello World' did not: I attached the scripts I used in December, 2009, trying to build a Cygwin cross toolchain. This is much like the MinGW cross toolchain build scripts. The scripts seem not to be able complete the build procdure of gcc. The Chinese characters in the scripts is encoded as gb2312. -- Chiheng Xu Wuhan,China gcc_cygwin.tar.bz2 Description: BZip2 compressed data -- 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
Re: linux-cygwin cross build environment
On Thu, Aug 26, 2010 at 2:24 PM, Chiheng Xu chiheng...@gmail.com wrote: I attached the scripts I used in December, 2009, trying to build a Cygwin cross toolchain. Also attcach the MinGW scripts. -- Chiheng Xu Wuhan,China gcc_mingw.tar.bz2 Description: BZip2 compressed data -- 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
Re: Build S-Lang Fail
On Wed, Aug 25, 2010 at 6:32 PM, Larry Hall (Cygwin) wrote: On 8/25/2010 8:58 AM, Csaba Raduly wrote: You could either run ldd on the DLLs (cyggcc_s-1.dll, cyggmp-3.dll and cygmpfr-1.dll) or use depends.exe (http://www.dependencywalker.com/) to try to identify the missing DLL. 'cygcheck' is also an option as well. Or maybe all this is a false alarm: http://www.cygwin.com/ml/cygwin/2010-08/msg00707.html -- Life is complex, with real and imaginary parts. Ok, it boots. Which means it must be bug-free and perfect. -- Linus Torvalds People disagree with me. I just ignore them. -- Linus Torvalds -- 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
Re: [ANNOUNCEMENT] NEW: {libtirpc/libtirpc1/libtirpc-devel}-0.2.1-1
On Aug 25 23:36, Charles Wilson wrote: On 8/21/2010 4:54 AM, Corinna Vinschen wrote: The question is, why does libtirpc declare the functions at all? Does it come with its own implementation? Yes, it does. And, that implementation is used by the upstream source for linux, in preference to the glibc-provided version. Any idea, why? I assume it really needs bindresvport_sa to support the bindresvport functionality for IPv6, which is not supported by glibc. But it is supported on Cygwin, BSD, and others. So, is that a configurable option? In other words, does libtirpc configury check for these functions on the target system? I followed that pattern in libtirpc, as well: the libtirpc version is used in preference to cygwin's. Not because I think there is a problem with cygwin's, but simply because I followed the linux pattern. Given that, I think something similar to the krb5 solution could be used here, as well. Unfortunately, the current cygtirpc-1.dll exports its version of bindresvport and bindresvport_sa. That is a *problem* because anything built against it will expect to use ITS version from now on. Not much of a problem, I guess. Given that the application is linked against cygtirpc-1.dll anyway, it doesn't matter if it uses the libtirpc or the cygwin implementation, same as on Linux. At least not as long as the cygtirpc-1.dll functions work correct. Unless I rebuild with renamed versions, and bump the API number. Or, don't bump the API number and break stuff. Since it is a new package, and so far only Erick's private libvirt seems to use it, I'm actually leaning that way. Eric, any thoughts? Whether or not, I think the problem are the libtirpc headers in the first place. OK. Given the above, I think that the libtirpc headers just shouldn't declare these functions on systems providing them via netdb.h. But note that this only occurs with -Wredundant-decls, which is not one of the default warnings. right, but this problem did lead to the discovery of a real issue in cygtirpc-1.dll... I wonder if there are more issues lurking here: The following are exported by both cygtirpc-1.dll and cygwin1.dll: bindresvport bindresvport_sa getpeereid (*) (*) implemented using error = getsockopt(s, SOL_SOCKET, SO_PEERCRED, uc, uclen); and then picking uc.uid and uc.gid (after error checking, etc). Cygwin implements both APIs of getting the peer credentials, so the libtirpc implementation of getpeereid is redundant, but should work. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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
Re: associating device names with cygdrive directories
On Aug 25 16:32, Buchbinder, Barry (NIH/NIAID) [E] wrote:
On Wed, Aug 25, 2010 at 02:47:21PM -0500, Charles D. Russell wrote:
On Linux, the mount command reveals the association between filesystem
names and /dev/ names, but Cygwin mount doesn't tell.
Is this what you want? (The multiple spaces are really tabs.)
$ for F in /dev/s* ; do echo $F$(cygpath -w $F) ; done
I have another one:
$ for F in /dev/s* ; do echo $F$(cygpath -w $F) ; done
/dev/sda\\.\PhysicalDrive0
/dev/sda1
\\.\STORAGE#Volume#{781f8bd6-7d0d-11de-8012-806e6f6e6963}#0010#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
/dev/sda2\\.\Volume{781f8bda-7d0d-11de-8012-806e6f6e6963}
/dev/sda3\\.\D:
but there are two problems.
Up to the current Cygwin 1.7.6 the info from /proc/partitions is
incomplete for non-privileged users. I just checked in a patch to
Cygwin which allows the full partition info also for non-priv'ed users.
Apart from that, the output of cygpath -w for devices isn't overly
helpful yet. I look into improving that a bit.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
--
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
compiling binutils misses sys/user.h
Hello, I try to compile binutils. It complaints a missing sys/user.h. On linux it would find it in /usr/include/sys/user.h. What is the way to go on Cygwin? Do I need to install some additional sources? Al -- 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
Re: associating device names with cygdrive directories
On 2010-08-26 07:26, Corinna Vinschen wrote:
I have another one:
$ for F in /dev/s* ; do echo $F$(cygpath -w $F) ; done
/dev/sda\\.\PhysicalDrive0
/dev/sda1
\\.\STORAGE#Volume#{781f8bd6-7d0d-11de-8012-806e6f6e6963}#0010#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
/dev/sda2\\.\Volume{781f8bda-7d0d-11de-8012-806e6f6e6963}
/dev/sda3\\.\D:
but there are two problems.
Up to the current Cygwin 1.7.6 the info from /proc/partitions is
incomplete for non-privileged users. I just checked in a patch to
Cygwin which allows the full partition info also for non-priv'ed users.
Apart from that, the output of cygpath -w for devices isn't overly
helpful yet. I look into improving that a bit.
Corinna
When I run echo /dev/s*, I only get /dev/shm /dev/stderr /dev/stdin
/dev/stdout, how/why is yours showing the drive devices?
--
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
Re: associating device names with cygdrive directories
On Aug 26 13:26, Corinna Vinschen wrote:
On Aug 25 16:32, Buchbinder, Barry (NIH/NIAID) [E] wrote:
On Wed, Aug 25, 2010 at 02:47:21PM -0500, Charles D. Russell wrote:
On Linux, the mount command reveals the association between filesystem
names and /dev/ names, but Cygwin mount doesn't tell.
Is this what you want? (The multiple spaces are really tabs.)
$ for F in /dev/s* ; do echo $F$(cygpath -w $F) ; done
I have another one:
$ for F in /dev/s* ; do echo $F$(cygpath -w $F) ; done
/dev/sda\\.\PhysicalDrive0
/dev/sda1
\\.\STORAGE#Volume#{781f8bd6-7d0d-11de-8012-806e6f6e6963}#0010#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
/dev/sda2\\.\Volume{781f8bda-7d0d-11de-8012-806e6f6e6963}
/dev/sda3\\.\D:
but there are two problems.
Up to the current Cygwin 1.7.6 the info from /proc/partitions is
incomplete for non-privileged users. I just checked in a patch to
Cygwin which allows the full partition info also for non-priv'ed users.
Apart from that, the output of cygpath -w for devices isn't overly
helpful yet. I look into improving that a bit.
I applied a patch to cygpath which now prefers the \\.\X: DOS device
name over any other device name for harddisks. In my case, the output
is now:
$ for F in $(gawk '{if (FNR 2) print /dev/ $4;}' /proc/partitions) ; do
echo $F$(./cygpath -w $F) ; done
/dev/sda\\.\PhysicalDrive0
/dev/sda1 \\.\Volume{781f8bd9-7d0d-11de-8012-806e6f6e6963}
/dev/sda2 \\.\C:
/dev/sda3 \\.\D:
/dev/sda1 is not available under a drive letter, so that's fine.
HTH,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
--
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
Re: associating device names with cygdrive directories
On Aug 26 08:11, Rolf Campbell wrote:
On 2010-08-26 07:26, Corinna Vinschen wrote:
I have another one:
$ for F in /dev/s* ; do echo $F$(cygpath -w $F) ; done
/dev/sda\\.\PhysicalDrive0
/dev/sda1
\\.\STORAGE#Volume#{781f8bd6-7d0d-11de-8012-806e6f6e6963}#0010#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
/dev/sda2\\.\Volume{781f8bda-7d0d-11de-8012-806e6f6e6963}
/dev/sda3\\.\D:
but there are two problems.
Up to the current Cygwin 1.7.6 the info from /proc/partitions is
incomplete for non-privileged users. I just checked in a patch to
Cygwin which allows the full partition info also for non-priv'ed users.
Apart from that, the output of cygpath -w for devices isn't overly
helpful yet. I look into improving that a bit.
Corinna
When I run echo /dev/s*, I only get /dev/shm /dev/stderr
/dev/stdin /dev/stdout, how/why is yours showing the drive devices?
I got tangled up in copy/paste. Actually the statement should have been:
for F in $(gawk '{if (FNR 2) print /dev/ $4;}' /proc/partitions);
do
echo $F$(./cygpath -w $F);
done
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
--
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
RE: Possible tar version 1.23-1 --remove-files bug.
I have additionally verified now that rolling back to version : tar (GNU tar) 1.22.90 does not exhibit this problem. -Original Message- From: Jeremy Warren [mailto:jer...@gmail.com] Sent: Thursday, August 26, 2010 12:49 AM To: cygwin@cygwin.com Subject: Possible tar version 1.23-1 --remove-files bug. I have duplicated the following behavior on 2 different machines CYGWIN_NT-5.2 1.7.6(0.230/5/3) 2010-08-16 16:06 i686 (Windows 2003 R2 Server) CYGWIN_NT-5.1 1.7.5(0.225/5/3) 2010-04-12 19:07 i686 (Windows XP Desktop) Both are running tar version 1.23-1 and the problem is 100% reproducible in my environment. *Some editing has been made to the output to protect the innocent. Any discrepancies in the output are unlikely related to the problem itself and more likely caused by my sausage shaped fingers. Scenario: Given a directory with sample contents: $ ls file1.asc file2.asc file3.asc file4.asc the following command: $ tar --remove-files -cvf test.tar *.asc file1.asc file2.asc file3.asc file4.asc Produces the expected result of a single test.tar, with the 4 asc files removed. $ ls test.tar And the tarball correctly contains all 4 files. $ tar -tvf test.tar -rw-r--r-- XX/None 22 2010-08-26 00:07 file1.asc -rw-r--r-- XX/None 22 2010-08-26 00:07 file2.asc -rw-r--r-- XX/None 22 2010-08-26 00:07 file3.asc -rw-r--r-- XX/None 22 2010-08-26 00:07 file4.asc *** PROBLEM STARTS HERE *** The following command, using the -r (append -vs- create) switch, correctly produces a test.tar file with all 4 files but fails to delete the files. $ tar --remove-files -rvf test.tar *.asc file1.asc file2.asc file3.asc file4.asc $ ls file1.asc file2.asc file3.asc file4.asc test.tar $ tar -tvf test.tar -rw-r--r-- XX/None 22 2010-08-26 00:11 file1.asc -rw-r--r-- XX/None 22 2010-08-26 00:11 file2.asc -rw-r--r-- XX/None 22 2010-08-26 00:11 file3.asc -rw-r--r-- XX/None 22 2010-08-26 00:11 file4.asc A return code of zero is produced in either instance, and the tarballs created are both fully usable. There is a second scenario where all asc files are deleted except the last one (so test.tar and file4 would be left in the directory at completion) but as of yet I cannot reproduce that scenario at will, so I'm uncertain as to the exact startup conditions that cause it. In my situation using -c is not a solution since this command is embedded within a large loop. Each file is being processed and appended to the archive one at a time. The processing script worked without issue prior to upgrading to the 1.23-1 version tar within the last week or so. *** Other possibly relevant pieces of information: *** I verified using a Linux box (2.6.18-164.9.1.el5.centos.plus) running tar (GNU tar) 1.15.1 to verify that my expectations of the command were correct. $ ls file1.asc file2.asc file3.asc file4.asc $ tar --remove-files -rvf test.tar *.asc file1.asc file2.asc file3.asc file4.asc $ ls test.tar $ tar -tvf test.tar -rw-r--r-- XX/XX 22 2010-08-26 00:15:28 file1.asc -rw-r--r-- XX/XX 22 2010-08-26 00:15:28 file2.asc -rw-r--r-- XX/XX 22 2010-08-26 00:15:28 file3.asc -rw-r--r-- XX/XX 22 2010-08-26 00:15:28 file4.asc Cygwin was installed from different mirrors at different times on each machine. It appears from the release notes that some changes were made in 1.23-1 related to the --remove-files argument ** The --remove-files option removes files only if they were succesfully stored in the archive. I was unable to find any related issues in the archive but was having trouble making the archive search match the '--remove-files' switch in the query. Apologies in advance if I duped. Thanks, Jeremy -- 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
Re: [ANNOUNCEMENT] NEW: {libtirpc/libtirpc1/libtirpc-devel}-0.2.1-1
On 8/26/2010 4:26 AM, Corinna Vinschen wrote: On Aug 25 23:36, Charles Wilson wrote: On 8/21/2010 4:54 AM, Corinna Vinschen wrote: The question is, why does libtirpc declare the functions at all? Does it come with its own implementation? Yes, it does. And, that implementation is used by the upstream source for linux, in preference to the glibc-provided version. Any idea, why? I assume it really needs bindresvport_sa to support the bindresvport functionality for IPv6, which is not supported by glibc. But it is supported on Cygwin, BSD, and others. So, is that a configurable option? In other words, does libtirpc configury check for these functions on the target system? No, it doesn't. Unfortunately, the current cygtirpc-1.dll exports its version of bindresvport and bindresvport_sa. That is a *problem* because anything built against it will expect to use ITS version from now on. Not much of a problem, I guess. Given that the application is linked against cygtirpc-1.dll anyway, it doesn't matter if it uses the libtirpc or the cygwin implementation, same as on Linux. At least not as long as the cygtirpc-1.dll functions work correct. Well, it's a problem if I want to remove or rename the duplicate functions now provided by cygtirpc-1.dll. Given the above, I think that the libtirpc headers just shouldn't declare these functions on systems providing them via netdb.h. But that's quite difficult to implement, in practice. You can't do this: #ifndef HAVE_BINDRESVPORT declare bindresvport #endif in an installed header, because then you'd ALSO have to install and #include your version of config.h, which is a big no-no. Not to mention the namespace conflicts inherent in the autoconf-generated HAVE_* macros. So, you have to make this header an AC_OUTPUT() file, and arrange to somehow munge rpc/rpc.h.in to DTRT depending on the value of HAVE_BINDRESVPORT... It is *doable* -- but not simple. The following are exported by both cygtirpc-1.dll and cygwin1.dll: bindresvport bindresvport_sa getpeereid (*) Cygwin implements both APIs of getting the peer credentials, so the libtirpc implementation of getpeereid is redundant, but should work. Yes, but I don't really like hiding the official implementation for no good reason. OTOH, that's what libtirpc does on linux -- my original justification for doing it this way. I'm of two minds on this. On the one hand: Notwithstanding the rpc/rpc.h re-declaration problem, I'd rather either (a) rename these functions -- which breaks ABI back-compat, or (b) remove them entirely from the build, which does that too -- but also forces libtirpc itself to use cygwin's implementation. Assuming it works, I'd rather go with (b). And not bump the DLL version number, since libtirpc is so young. But breaking the ABI without bumping the DLL number is bad form, and this is all a lot more work than just: On the other hand, Just do it the way it is done on linux, and simply fix the header redeclaration problem. That's less work :-) Regardless of how I deal with the duplicate symbols, fixing the rpc/rpc.h re-declaration problem implies substantial changes to the cygport and patches, so it'll take some time to get it right...especially given other urgent demands on my time right now (updated cygutils, run, run2; deadline approaching for official libtool-2.2.next, ...) -- Chuck -- 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
problem with dblatex
Hello, I have a fresh install of cygwin and I am trying to use dblatex (I should also say that I am a new user of cygwin). I have installed dblatex and tetex, but: - first, with dblatex: BEGIN dhajage $ dblatex essai.xml /usr/lib/python2.6/site-packages/dbtexmf/dblatex/grubber/util.py:8: DeprecationW arning: the md5 module is deprecated; use hashlib instead import md5 Build the book set list... Build the listings... XSLT stylesheets DocBook - LaTeX 2e (0.3) === Build essai.pdf cygwin warning: MS-DOS style path detected: \TeXLive2007\texmf-var\web2c Preferred POSIX equivalent is: /cygdrive/c/TeXLive2007/texmf-var/ web2c CYGWIN environment variable option nodosfilewarning turns off this warning. Consult the user's guide for more details about POSIX paths: http://cygwin.com/cygwin-ug-net/using.html#using-pathnames This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) kpathsea: Running mktexfmt pdflatex.fmt /bin/mktexfmt: line 333: /texconfig/tcfmgr: No such file or directory fmtutil: config file `fmtutil.cnf' not found. I can't find the format file `pdflatex.fmt'! pdflatex failed Could not run pdflatex. Unexpected error occured END - with pdflatex BEGIN dhajage $ pdflatex essai.tex This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) kpathsea: Running mktexfmt pdflatex.fmt /bin/mktexfmt: line 333: /texconfig/tcfmgr: No such file or directory fmtutil: config file `fmtutil.cnf' not found. I can't find the format file `pdflatex.fmt'! END What could be the problem of my installation? Is there any special configuration for pdflatex? Thank you very much for any help. david -- 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
Re: Possible tar version 1.23-1 --remove-files bug.
I have now compiled and verified the problem exists in Linux as well in the Gnu Tar 1.23-1 release, and is not a cygwin specific bug. I have submitted to bug-tar. Sorry for the false alarm. On Thu, Aug 26, 2010 at 8:57 AM, Jeremy Warren jer...@gmail.com wrote: I have additionally verified now that rolling back to version : tar (GNU tar) 1.22.90 does not exhibit this problem. -Original Message- From: Jeremy Warren [mailto:jer...@gmail.com] Sent: Thursday, August 26, 2010 12:49 AM To: cygwin@cygwin.com Subject: Possible tar version 1.23-1 --remove-files bug. I have duplicated the following behavior on 2 different machines CYGWIN_NT-5.2 1.7.6(0.230/5/3) 2010-08-16 16:06 i686 (Windows 2003 R2 Server) CYGWIN_NT-5.1 1.7.5(0.225/5/3) 2010-04-12 19:07 i686 (Windows XP Desktop) Both are running tar version 1.23-1 and the problem is 100% reproducible in my environment. *Some editing has been made to the output to protect the innocent. Any discrepancies in the output are unlikely related to the problem itself and more likely caused by my sausage shaped fingers. Scenario: Given a directory with sample contents: $ ls file1.asc file2.asc file3.asc file4.asc the following command: $ tar --remove-files -cvf test.tar *.asc file1.asc file2.asc file3.asc file4.asc Produces the expected result of a single test.tar, with the 4 asc files removed. $ ls test.tar And the tarball correctly contains all 4 files. $ tar -tvf test.tar -rw-r--r-- XX/None 22 2010-08-26 00:07 file1.asc -rw-r--r-- XX/None 22 2010-08-26 00:07 file2.asc -rw-r--r-- XX/None 22 2010-08-26 00:07 file3.asc -rw-r--r-- XX/None 22 2010-08-26 00:07 file4.asc *** PROBLEM STARTS HERE *** The following command, using the -r (append -vs- create) switch, correctly produces a test.tar file with all 4 files but fails to delete the files. $ tar --remove-files -rvf test.tar *.asc file1.asc file2.asc file3.asc file4.asc $ ls file1.asc file2.asc file3.asc file4.asc test.tar $ tar -tvf test.tar -rw-r--r-- XX/None 22 2010-08-26 00:11 file1.asc -rw-r--r-- XX/None 22 2010-08-26 00:11 file2.asc -rw-r--r-- XX/None 22 2010-08-26 00:11 file3.asc -rw-r--r-- XX/None 22 2010-08-26 00:11 file4.asc A return code of zero is produced in either instance, and the tarballs created are both fully usable. There is a second scenario where all asc files are deleted except the last one (so test.tar and file4 would be left in the directory at completion) but as of yet I cannot reproduce that scenario at will, so I'm uncertain as to the exact startup conditions that cause it. In my situation using -c is not a solution since this command is embedded within a large loop. Each file is being processed and appended to the archive one at a time. The processing script worked without issue prior to upgrading to the 1.23-1 version tar within the last week or so. *** Other possibly relevant pieces of information: *** I verified using a Linux box (2.6.18-164.9.1.el5.centos.plus) running tar (GNU tar) 1.15.1 to verify that my expectations of the command were correct. $ ls file1.asc file2.asc file3.asc file4.asc $ tar --remove-files -rvf test.tar *.asc file1.asc file2.asc file3.asc file4.asc $ ls test.tar $ tar -tvf test.tar -rw-r--r-- XX/XX 22 2010-08-26 00:15:28 file1.asc -rw-r--r-- XX/XX 22 2010-08-26 00:15:28 file2.asc -rw-r--r-- XX/XX 22 2010-08-26 00:15:28 file3.asc -rw-r--r-- XX/XX 22 2010-08-26 00:15:28 file4.asc Cygwin was installed from different mirrors at different times on each machine. It appears from the release notes that some changes were made in 1.23-1 related to the --remove-files argument ** The --remove-files option removes files only if they were succesfully stored in the archive. I was unable to find any related issues in the archive but was having trouble making the archive search match the '--remove-files' switch in the query. Apologies in advance if I duped. Thanks, Jeremy -- 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
Re: Possible tar version 1.23-1 --remove-files bug.
On 08/25/2010 10:49 PM, Jeremy Warren wrote: I have duplicated the following behavior on 2 different machines CYGWIN_NT-5.2 1.7.6(0.230/5/3) 2010-08-16 16:06 i686 (Windows 2003 R2 Server) CYGWIN_NT-5.1 1.7.5(0.225/5/3) 2010-04-12 19:07 i686 (Windows XP Desktop) Both are running tar version 1.23-1 and the problem is 100% reproducible in my environment. Have you also tested this on Linux? I've done very little in the way of cygwin patches (mainly binary mode handling issues), so this is likely an upstream regression that affects all platforms. Note: I haven't had time to test it myself, yet. It appears from the release notes that some changes were made in 1.23-1 related to the --remove-files argument ** The --remove-files option removes files only if they were succesfully stored in the archive. -- Eric Blake ebl...@redhat.com+1-801-349-2682 Libvirt virtualization library http://libvirt.org -- 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
R: problem with dblatex
--- Gio 26/8/10, David Hajage ha scritto: Hello, I have a fresh install of cygwin and I am trying to use dblatex (I should also say that I am a new user of cygwin). I have installed dblatex and tetex, but: - first, with dblatex: BEGIN dhajage $ dblatex essai.xml /usr/lib/python2.6/site-packages/dbtexmf/dblatex/grubber/util.py:8: DeprecationW arning: the md5 module is deprecated; use hashlib instead import md5 Build the book set list... Build the listings... XSLT stylesheets DocBook - LaTeX 2e (0.3) === Build essai.pdf cygwin warning: MS-DOS style path detected: \TeXLive2007\texmf-var\web2c Preferred POSIX equivalent is: /cygdrive/c/TeXLive2007/texmf-var/ web2c Have you a Windows TeXLive2007 in the path before the cygwin tetex ? CYGWIN environment variable option nodosfilewarning turns off this warning. Consult the user's guide for more details about POSIX paths: http://cygwin.com/cygwin-ug-net/using.html#using-pathnames This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) kpathsea: Running mktexfmt pdflatex.fmt /bin/mktexfmt: line 333: /texconfig/tcfmgr: No such file or directory fmtutil: config file `fmtutil.cnf' not found. I can't find the format file `pdflatex.fmt'! pdflatex failed Could not run pdflatex. Unexpected error occured END - with pdflatex BEGIN dhajage $ pdflatex essai.tex This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) kpathsea: Running mktexfmt pdflatex.fmt /bin/mktexfmt: line 333: /texconfig/tcfmgr: No such file or directory fmtutil: config file `fmtutil.cnf' not found. I can't find the format file `pdflatex.fmt'! END What could be the problem of my installation? Is there any special configuration for pdflatex? Thank you very much for any help. david -- 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
Re: [ANNOUNCEMENT] NEW: {libtirpc/libtirpc1/libtirpc-devel}-0.2.1-1
On 08/25/2010 09:36 PM, Charles Wilson wrote: Unless I rebuild with renamed versions, and bump the API number. Or, don't bump the API number and break stuff. Since it is a new package, and so far only Erick's private libvirt seems to use it, I'm actually leaning that way. Eric, any thoughts? libtirpc is new enough, and I haven't distributed my built libvirt anywhere, that I would be just fine with a -2 without a new API number, if that makes life easier for you. Ultimately, I do plan on doing an ITP for libvirt. Right now, we don't really have any native VMs like qemu working under cygwin, and kvm is out of the question without access to the kernel; but a cygwin-built libvirt _is_ capable of doing remote control of VMs hosted on another machine. But the ITP can wait until we are happy with the libtirpc situation. -- Eric Blake ebl...@redhat.com+1-801-349-2682 Libvirt virtualization library http://libvirt.org -- 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
Possible Regression in cygpath
Prior to the latest release of cygwin (which translates to cygpath version 1.6.1), the following command worked fine: cygpath -d . With the latest release of cygwin (which translates to cygpath version 1.8 I believe; the build was ~ August 10th), the same command complains: cygpath: cannot create short name of . However, if I execute: cygpath -d --absolute . it works as expected. It appears that in the latest release, cygpath either requires that --absolute flag, or requires the path that is passed in to be absolute. Was this an intentional change? -- 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
symlinks in 1.5 not readable in 1.7
I've been working for months on this problem since 1.7 went official.. I'm runningWin XP Pro sp3 on an all NTFS filesystems. I was a beta tester for several months before 1.7 went official. In all of my testing as beta, my 1.5 symlinks worked in both 1.5 and 1.7. After (or during) the 1.7 becoming official, my many 1.5 symlinks were no longer working. I have spent considerable time attempting to find and fix these 1.5 created symlinks (300+ total) I was quite taken back that such a major change would be thrown in at the last minute. Mabe it was just an oversight. I am quoting from web page titled: What's new and what changed in Cygwin 1.7 Chapter 1. Cygwin Overview In one of the bullet items on the first page, it states : Cygwin 1.7 can read all old style symlinks, but the new style is not compatible with older Cygwin releases. If this is true, then why am I having these problems now, a few months after 1.7 release? Has anyone else experience these problems or an I just a heavy user of symlinks? Has anyone written a tool that will find and fix these 1.5 symlinks? Note: cygcheck -s is attached. web page titled: -- http://genealogy.mcferrin.org/ # McFerrin Family History, Public View -- 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
1.5 symlinks not readable in 1.7
Sorry for re-submission. Forgot the attachment. I've been working for months on this problem since 1.7 went official.. I'm runningWin XP Pro sp3 on an all NTFS filesystems. I was a beta tester for several months before 1.7 went official. In all of my testing as beta, my 1.5 symlinks worked in both 1.5 and 1.7. After (or during) the 1.7 becoming official, my many 1.5 symlinks were no longer working. I have spent considerable time attempting to find and fix these 1.5 created symlinks (300+ total) I was quite taken back that such a major change would be thrown in at the last minute. Mabe it was just an oversight. I am quoting from web page titled: What's new and what changed in Cygwin 1.7 Chapter 1. Cygwin Overview In one of the bullet items on the first page, it states : Cygwin 1.7 can read all old style symlinks, but the new style is not compatible with older Cygwin releases. If this is true, then why am I having these problems now, a few months after 1.7 release? Has anyone else experience these problems or an I just a heavy user of symlinks? Has anyone written a tool that will find and fix these 1.5 symlinks? Note: cygcheck -s is attached. -- http://genealogy.mcferrin.org/ # McFerrin Family History, Public View Cygwin Configuration Diagnostics Current System Time: Thu Aug 26 09:58:50 2010 Windows XP Professional Ver 5.1 Build 2600 Service Pack 3 Path: C:\cygwin\bin C:\cygwin\lbin C:\cygwin\bin\X11 C:\cygwin\lbin C:\cygwin\bin C:\Program Files\WinOne C:\WINDOWS\system32 C:\WINDOWS C:\WINDOWS\System32\Wbem C:\Program Files\ATI Technologies\ATI.ACE\Core-Static C:\Program Files\Common Files\Acronis\SnapAPI\ C:\Program Files\Acronis\BackupAndRecovery\ .\ SysDir: C:\WINDOWS\system32 WinDir: C:\WINDOWS CYGWIN = 'tty' HOME = '/home/Paul' PWD = '/home/Paul' MAKE_MODE = 'UNIX' Use '-r' to scan registry obcaseinsensitive set to 1 Cygwin installations found in the registry: System: Key: 172d431784c9776c Path: H:\cygwinV (ORPHANED) System: Key: c5e39b7a9d22bafb Path: C:\cygwin System: Key: 8906c960e8a52c64 Path: G:\cygwin_USB System: Key: 6e042ace4f7ac114 Path: C:\cygwin_1.5 a: fd N/AN/A c: hd NTFS 51997Mb 61% CP CS UN PA FC d: cd N/AN/A e: hd NTFS211502Mb 38% CP CS UN PA FC New Volume f: hd NTFS211502Mb 2% CP CS UN PA FC New Volume g: hd NTFS 51199Mb 58% CP CS UN PA FC System h: hd NTFS107520Mb 84% CP CS UN PA FC Volume1 k: hd NTFS107520Mb 66% CP CS UN PA FC Volume2 l: hd NTFS210696Mb 12% CP CS UN PA FC Volume3 r: net NTFS211502Mb 38% CP CS UN PA FC New Volume y: net NTFS 40970Mb 61% CP CS UN PA FC z: net NTFS111576Mb 56% CP CS UN PA FC Local Disk C:\cygwin/ system binary,auto a: /a system binary \bin /bin system binary C: /c system binary D: /d system binary E: /e system binary \etc /etc system binary F: /f system binary G: /g system binary H: /h system binary I: /i system binary J: /j system binary K: /k system binary L: /l system binary \lib /lib system binary M: /m system binary N: /n system binary O: /o system binary P: /p system binary Q: /q system binary R: /r system binary \usr /usr system binary C:\cygwin\bin/usr/bin system binary,auto C:\cygwin\lib/usr/lib system binary,auto cygdrive prefix /cygdrive userbinary,auto Found: C:\cygwin\bin\awk Found: C:\cygwin\bin\awk - C:\cygwin\bin\gawk.exe Found: C:\cygwin\bin\bash.exe Found: C:\cygwin\bin\bash.exe Found: C:\cygwin\bin\cat.exe Found: C:\cygwin\bin\cat.exe Found: C:\cygwin\bin\cp.exe Found: C:\cygwin\bin\cp.exe Found: C:\cygwin\bin\cpp.exe Found: C:\cygwin\bin\cpp.exe - \etc\alternatives\cpp Not Found: cpp (good!) Found: C:\cygwin\bin\crontab.exe Found: C:\cygwin\bin\crontab.exe Found: C:\cygwin\bin\find.exe Found: C:\cygwin\bin\find.exe Found: C:\WINDOWS\system32\find.exe Found: C:\cygwin\bin\gcc.exe Found: C:\cygwin\bin\gcc.exe - \etc\alternatives\gcc Not Found: gcc Not Found: gdb Found: C:\cygwin\bin\grep.exe Found: C:\cygwin\bin\grep.exe Found: C:\cygwin\bin\kill.exe Found: C:\cygwin\bin\kill.exe Found: C:\cygwin\bin\ld.exe Found: C:\cygwin\bin\ld.exe Found: C:\cygwin\bin\ls.exe Found: C:\cygwin\bin\ls.exe Found: C:\cygwin\bin\make.exe Found: C:\cygwin\bin\make.exe Found: C:\cygwin\bin\mv.exe
Re: associating device names with cygdrive directories
On 8/25/2010 4:32 PM, Buchbinder, Barry (NIH/NIAID) [E] wrote:
$ for F in /dev/s* ; do echo $F$(cygpath -w $F) ; done
/dev/scd0 \\.\D:
/dev/scd1 \Device\CdRom1
/dev/scd2 \Device\CdRom2
/dev/sda\\.\PhysicalDrive0
/dev/sda1 \\.\Volume{39f65722-0106-11df-b1c0-806d6172696f}
/dev/sda2 \Device\Harddisk0\Partition2
/dev/sdb\Device\Harddisk1\Partition0
/dev/sdb1 \Device\Harddisk1\Partition1
/dev/sdb2 \Device\Harddisk1\Partition2
/dev/sdc\Device\Harddisk2\Partition0
/dev/sdc1 \Device\Harddisk2\Partition1
/dev/sdc2 \Device\Harddisk2\Partition2
/dev/shmC:\cygwin\dev\shm
/dev/sr0\\.\D:
/dev/sr1\Device\CdRom1
/dev/sr2\Device\CdRom2
/dev/st0\Device\Tape0
/dev/st1\Device\Tape1
/dev/st2\Device\Tape2
/dev/stderr \dev\tty
/dev/stdin \dev\tty
/dev/stdout /proc/2476/fd/pipe:[504]
I'm running Cygwin 1.7.6-1, and when I use your command ('for F in
...'), above, I
don't get all the devices in your list (for those that I have). Instead
I get:
/dev/shmC:\_0\dev\shm
/dev/stderr \devty0
/dev/stdin \devty0
/dev/stdout /proc/4876/fd/pipe:[800]
What's missing? At least:
* ty1
* 2 HD partitions
* 1 1.5 TB USB drive
* 1 TB RAID 0
* 2 CD/DVD drives (one USB, one internal)
* CF drive
* USB 16 GB flash drive
This is not earth shattering since everything (AFAIK) works (with either
Windoze
or Cygwin), but what's the deal, do you think?
Thx,
Lee
--
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
Re: 1.5 symlinks not readable in 1.7
On Aug 26 10:22, Paul McFerrin wrote: Sorry for re-submission. Forgot the attachment. I've been working for months on this problem since 1.7 went official.. I'm runningWin XP Pro sp3 on an all NTFS filesystems. I was a beta tester for several months before 1.7 went official. In all of my testing as beta, my 1.5 symlinks worked in both 1.5 and 1.7. After (or during) the 1.7 becoming official, my many 1.5 symlinks were no longer working. I have spent considerable time attempting to find and fix these 1.5 created symlinks (300+ total) I was quite taken back that such a major change would be thrown in at the last minute. Mabe it was just an oversight. And you actually waited 8 months before reporting it??? I am quoting from web page titled: What's new and what changed in Cygwin 1.7 Chapter 1. Cygwin Overview In one of the bullet items on the first page, it states : Cygwin 1.7 can read all old style symlinks, but the new style is not compatible with older Cygwin releases. If this is true, then why am I having these problems now, a few months after 1.7 release? I have not the faintest idea. The old 1.5 symlinks still work for me, independent of using .lnk-style symlinks (default in 1.5) or plain files with SYSTEM DOS attribute set-style symlinks (CYGWIN=nowinsymlinks, default in 1.7). or an I just a heavy user of symlinks? Has anyone written a tool that will find and fix these 1.5 symlinks? Are all symlinks not working? What *exactly* is wrong or goes wrong? Create an example so that we're on the same line as you are. Problem reports with testcases are infinitely more helpful than without them. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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
Re: associating device names with cygdrive directories
On Aug 26 10:44, Lee D. Rothstein wrote:
On 8/25/2010 4:32 PM, Buchbinder, Barry (NIH/NIAID) [E] wrote:
$ for F in /dev/s* ; do echo $F$(cygpath -w $F) ; done
/dev/scd0 \\.\D:
/dev/scd1 \Device\CdRom1
/dev/scd2 \Device\CdRom2
/dev/sda\\.\PhysicalDrive0
/dev/sda1 \\.\Volume{39f65722-0106-11df-b1c0-806d6172696f}
/dev/sda2 \Device\Harddisk0\Partition2
/dev/sdb\Device\Harddisk1\Partition0
/dev/sdb1 \Device\Harddisk1\Partition1
/dev/sdb2 \Device\Harddisk1\Partition2
/dev/sdc\Device\Harddisk2\Partition0
/dev/sdc1 \Device\Harddisk2\Partition1
/dev/sdc2 \Device\Harddisk2\Partition2
/dev/shmC:\cygwin\dev\shm
/dev/sr0\\.\D:
/dev/sr1\Device\CdRom1
/dev/sr2\Device\CdRom2
/dev/st0\Device\Tape0
/dev/st1\Device\Tape1
/dev/st2\Device\Tape2
/dev/stderr \dev\tty
/dev/stdin \dev\tty
/dev/stdout /proc/2476/fd/pipe:[504]
I'm running Cygwin 1.7.6-1, and when I use your command ('for F in
...'), above,
http://cygwin.com/ml/cygwin/2010-08/msg00837.html
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
--
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
Re: Possible Regression in cygpath
On Aug 26 09:59, Matt Hughes wrote: Prior to the latest release of cygwin (which translates to cygpath version 1.6.1), the following command worked fine: cygpath -d . With the latest release of cygwin (which translates to cygpath version 1.8 I believe; the build was ~ August 10th), the same command complains: cygpath: cannot create short name of . Thanks for the report. This will be fixed in 1.7.7. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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
mintty start menu icon
Hello. I do not want a Cygwin folder in my start menu. When I run the Cygwin setup, I always uncheck Add icon to Start Menu on the last page. Despite of that, every time the mintty package is updated, its icon appears again in the start menu. It would be nice if the mintty package could honor the unchecking of Add icon to Start Menu, just like the legacy Cygwin command prompt. -- Vincent Rivière -- 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
Re: associating device names with cygdrive directories
Is there an easy way to find the association of a given /dev/sd? with
the corresponding /cygdrive/?. Is there a good way to verify the
association before writing to the device with dd?
Larry Hall wrote:
you can certainly use the information from Disk Management to figure out
the mapping.
essentially, Disk 0 = /dev/sda, etc.
Thanks. That is the mapping I was looking for.
Jeremy Bopp wrote:
How would you handle the case where you have more than a single mount
which looks like that? e.g.)
/dev/sda1 on /live/image1 type vfat
(rw,noatime,fmask=0022,dmask=0022,allow_utime=17,codepage=cp437,iocharset=utf8)
/dev/sdb1 on /live/image2 type vfat
(rw,noatime,fmask=0022,dmask=0022,allow_utime=17,codepage=cp437,iocharset=utf8)
***
If I know that /dev/sda1 maps to /live/image1, then I can use df and ls
on /live/image1
to identify the device - easier than using dd |strings on /dev/sda1.
I'm concerned
with distinguishing among USB storage devices.
Corinna Vinschen wrote:
$ for F in $(gawk '{if (FNR 2) print /dev/ $4;}'
/proc/partitions) ; do echo $F$(./cygpath -w $F) ; done
/dev/sda\\.\PhysicalDrive0
/dev/sda1 \\.\Volume{781f8bd9-7d0d-11de-8012-806e6f6e6963}
/dev/sda2 \\.\C:
/dev/sda3 \\.\D:
/dev/sda1 is not available under a drive letter, so that's fine.
*
Nice, but evidently requires your patches, not working on my installation.
__
Andrey Repin wrote:
please, use reply option when replying to list, instead of writing new
message.
**
I would use gmane to enable this, but I'm on dial-up at the end of a
miserable rural telephone line in Maine, where even DNS lookup usually
takes several tries, and servers that are not patient enough for lots of
retries simply won't work.
_
Thanks everyone. I was successful in creating a bootable USB flash
drive using Cygwin to dd from debian-live.img.
It was so slow, though, that I will forget about using Cygwin to clone a
hard drive.
--
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
Re: mintty start menu icon
2010/8/26 Vincent Rivière vincent.rivi...@freesbee.fr: Hello. I do not want a Cygwin folder in my start menu. When I run the Cygwin setup, I always uncheck Add icon to Start Menu on the last page. Despite of that, every time the mintty package is updated, its icon appears again in the start menu. It would be nice if the mintty package could honor the unchecking of Add icon to Start Menu, just like the legacy Cygwin command prompt. -- Vincent Rivière Wouldn't it better if the mintty installer asked on its own if this shortcut were needed on new installs? I find that I like mintty much better than the stock window and I end up liking the mintty shortcut and unchecking the add icons in the installer. Rance -- 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
Re: Possible tar version 1.23-1 --remove-files bug.
Yes, sorry, I tried to send an email waving everyone off. I did not have available a linux machine with the same version until this morning, when I downloaded and compiled the 1.23 and found it existed as well there. I have re-posted to tar-bug list and await their response. Thanks On Thu, Aug 26, 2010 at 9:50 AM, Eric Blake ebl...@redhat.com wrote: On 08/25/2010 10:49 PM, Jeremy Warren wrote: I have duplicated the following behavior on 2 different machines CYGWIN_NT-5.2 1.7.6(0.230/5/3) 2010-08-16 16:06 i686 (Windows 2003 R2 Server) CYGWIN_NT-5.1 1.7.5(0.225/5/3) 2010-04-12 19:07 i686 (Windows XP Desktop) Both are running tar version 1.23-1 and the problem is 100% reproducible in my environment. Have you also tested this on Linux? I've done very little in the way of cygwin patches (mainly binary mode handling issues), so this is likely an upstream regression that affects all platforms. Note: I haven't had time to test it myself, yet. It appears from the release notes that some changes were made in 1.23-1 related to the --remove-files argument ** The --remove-files option removes files only if they were succesfully stored in the archive. -- Eric Blake ebl...@redhat.com +1-801-349-2682 Libvirt virtualization library http://libvirt.org -- 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 -- 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
How do I kill ssmtp?
Hello, I'm getting an inordinate amount of mail in the deadletter files, some 400 meg since this server started. I've grepped for the PID to kill the process, I've looked in the Services table in Windows and I've looked in the Programs, uninstall and can't find any reference to ssmtp to kill! First, is 400 meg a normal amount of dead letter mail for a system that's been up for only two weeks? Second, how do I kill this process? Third, how do I clear the DL file? For now, I've moved the old dead.letter to a different filed and touched a new, empty dead.letter. Fourth, would any of these events cause the system to completely lock up and have to be rebooted? Thanks for your time assistance! Blaine -- 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
Re: Will cron runnnnig as a service cause the server to lock up?
On 8/26/2010 12:59 PM, Blaine Miller wrote: I'm running cron as a service. Twice this week this server has died and needed cold rebooting to get the system back. Questions - First, will cron as a service on a Windows 2003 R2, standard system cause this sort of behavior? No, that's an O/S issue (kernel or drivers). -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- 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
Re: mintty start menu icon
2010/8/26 Vincent Rivière: I do not want a Cygwin folder in my start menu. When I run the Cygwin setup, I always uncheck Add icon to Start Menu on the last page. Despite of that, every time the mintty package is updated, its icon appears again in the start menu. It would be nice if the mintty package could honor the unchecking of Add icon to Start Menu Yes, that would be nice, but unfortunately setup.exe's design doesn't allow for this. The start menu icon is created by the mintty postinstall script, which is run before the user even gets to the Add icon to Start Menu option. Same issue for other packages that create start menu entries. Andy -- 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
Re: mintty start menu icon
On 08/26/2010 11:07 AM, Andy Koppe wrote: 2010/8/26 Vincent Rivière: It would be nice if the mintty package could honor the unchecking of Add icon to Start Menu Yes, that would be nice, but unfortunately setup.exe's design doesn't allow for this. The start menu icon is created by the mintty postinstall script, which is run before the user even gets to the Add icon to Start Menu option. Same issue for other packages that create start menu entries. Well, it sort of does - if you create two packages, mintty (no shortcut menu created) and mintty-shortcut (depends on mintty, and additionally creates the shortcut), then the user can choose whether the shortcut will exist by which package they choose to install. But that's not saying it's the best solution. Another thought - now that we are patching setup.exe to set env-vars that inform the postinstall scripts about aspects of the installation (such as for all users or just me), setup.exe could also be patched to tell postinstall scripts whether start menu modifications are desired. However, this would require some major surgery, since the current implementation runs postinstall scripts prior to the screen where it asks if a start menu icon should exist. -- Eric Blake ebl...@redhat.com+1-801-349-2682 Libvirt virtualization library http://libvirt.org -- 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
Re: mintty start menu icon
On 8/26/2010 1:07 PM, Andy Koppe wrote: 2010/8/26 Vincent Rivière: It would be nice if the mintty package could honor the unchecking of Add icon to Start Menu Yes, that would be nice, but unfortunately setup.exe's design doesn't allow for this. The start menu icon is created by the mintty postinstall script, which is run before the user even gets to the Add icon to Start Menu option. Same issue for other packages that create start menu entries. Would it be reasonable to move that dialog (sans the Finished wording, of course) earlier in the process -- and then export the value of those checkboxes via env vars like your other patch? -- Chuck -- 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
Re: mintty start menu icon
On 26 August 2010 17:02, Rance Hall wrote: Wouldn't it better if the mintty installer asked on its own if this shortcut were needed on new installs? I guess it would be possible for postinstall scripts to somehow throw up a message box before creating shortcuts, but I suspect that would cause much more annoyance than yet another entry start menu entry that's easily deleted or ignored. Also, that approach just wouldn't scale to multiple packages. Andy -- 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
Re: mintty start menu icon
On 26 August 2010 18:13, Charles Wilson wrote: On 8/26/2010 1:07 PM, Andy Koppe wrote: 2010/8/26 Vincent Rivière: It would be nice if the mintty package could honor the unchecking of Add icon to Start Menu Yes, that would be nice, but unfortunately setup.exe's design doesn't allow for this. The start menu icon is created by the mintty postinstall script, which is run before the user even gets to the Add icon to Start Menu option. Same issue for other packages that create start menu entries. Would it be reasonable to move that dialog (sans the Finished wording, of course) earlier in the process -- and then export the value of those checkboxes via env vars like your other patch? Yes, I think that would make sense, but I'm sure setup.exe would have some interesting complications up its sleeve. We'd also need a new final page. Perhaps the postinstall results page could be adapted to serve in that role. Quite a lot of work though for what's not exactly a critical issue. Andy -- 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
Re: Will cron runnnnig as a service cause the server to lock up?
- Original Message - From: Blaine Miller To: cygwin Sent: Thursday, August 26, 2010 12:59 | I'm running cron as a service. Twice this week this server has died and | needed cold rebooting to get the system back. | | Questions - First, will cron as a service on a Windows 2003 R2, standard | system cause this sort of behavior? This has never been reported, as far as I know. You run cron as yourself, if I remember correctly. This avoids various setuid issues. Except for that, cron is a plain vanilla program. | Second, if it does, how do I run cron to keep it from | doing this? | | A snippet of the errors I'm getting are: | | cron: unknown option -- D | usage: /usr/sbin/cron [-n] [-x [ext,sch,proc,pars,load,misc,test,bit]] | Where does the -D come from? That used to be an option in cron 3. It is now replaced by -n Without -n, cron will not remain under the control of cygrunsrv. | My crontable is: | | $ crontab -l | # DO NOT EDIT THIS FILE - edit the master and reinstall. | # (/tmp/crontab.yRr11boUdm installed on Thu Aug 19 14:17:23 2010) | # (Cron version V5.0 -- $Id: crontab.c,v 1.12 2004/01/23 18:56:42 vixie | Exp $) | 00 05 * * * /cygdrive/c/scripts/xfer_vvm_mysql.sh | 00 05 * * * /cygdrive/c/scripts/xfer_vvm_ora.sh | 00 05 * * * /cygdrive/c/scripts/xfer_nab_vnnab.sh | 00 10 * * * /cygdrive/c/scripts/xfer_nab_csnab.sh | 00 06 * * * /cygdrive/c/scripts/xfer_dellsrv20.sh | 00 06 * * * /cygdrive/c/scripts/xfer_directory.sh | 00 06 * * * /cygdrive/c/scripts/xfer_perforce.sh | 00 06 * * 2 /cygdrive/c/scripts/xfer_fileserv.sh | | | As you can see, I'm not passing any paramets to the cron daemon... Remember that PATH may not be the same under cron as under interactive bash. So find and other tools may use a Windows version. But that doesn't explain a crash. Pierre -- 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
Re: mintty start menu icon
Andy Koppe wrote: Quite a lot of work though for what's not exactly a critical issue. I agree. But I wonder why what works for the standard console icon does not work for the mintty icon. Probably a special case. -- Vincent Rivière -- 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
Re: Will cron runnnnig as a service cause the server to lock up?
Hello, Larry, I'm getting this message in the Event Log for cron kicking off... The description for Event ID ( 0 ) in Source ( /usr/sbin/cron ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: /usr/sbin/cron: PID 2160: (Administrator) CMD (/cygdrive/c/scripts/xfer_nab_csnab.sh). Does it mean anything? Thanks for your time and assistance... Blaine Larry Hall (Cygwin) wrote: On 8/26/2010 12:59 PM, Blaine Miller wrote: I'm running cron as a service. Twice this week this server has died and needed cold rebooting to get the system back. Questions - First, will cron as a service on a Windows 2003 R2, standard system cause this sort of behavior? No, that's an O/S issue (kernel or drivers). -- 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
Re: How do I kill ssmtp?
On 2010/08/26 9:51 AM, Blaine Miller wrote: I'm getting an inordinate amount of mail in the deadletter files, some 400 meg since this server started. I've grepped for the PID to kill the process, I've looked in the Services table in Windows and I've looked in the Programs, uninstall and can't find any reference to ssmtp to kill! ssmtp is not a daemon/service, so that is to be expected. First, is 400 meg a normal amount of dead letter mail for a system that's been up for only two weeks? That depends on your definition of normal. But unless your server is handling an extremely large volume of email traffic, I think it's safe to say that 400M in two weeks is not normal. Second, how do I kill this process? You will want to find the process (or processes) that are attempting (and failing) to send email via ssmtp. In your other message to the list today, you mention that you're using cron, so I strongly suspect cron to be the source of most/all your dead emails. It is possible that your cron jobs are generating a lot of output that hasn't been redirected to proper log files or /dev/null. Third, how do I clear the DL file? For now, I've moved the old dead.letter to a different filed and touched a new, empty dead.letter. That sounds okay to me. You should probably examine the file contents to try to discover where the messages are coming from. Fourth, would any of these events cause the system to completely lock up and have to be rebooted? I don't think your dead.letter file could have caused that, unless, perhaps, it filled up the system drive. Thanks for your time assistance! HTH, -SM -- -- 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
Re: Will cron runnnnig as a service cause the server to lock up?
Larry, I'm also getting the following message from the crontab in the Event Log The description for Event ID ( 0 ) in Source ( crontab ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: crontab: PID 1596: (Administrator) LIST (Administrator). This doesn't make sense to me either... Blaine Larry Hall (Cygwin) wrote: On 8/26/2010 12:59 PM, Blaine Miller wrote: I'm running cron as a service. Twice this week this server has died and needed cold rebooting to get the system back. Questions - First, will cron as a service on a Windows 2003 R2, standard system cause this sort of behavior? No, that's an O/S issue (kernel or drivers). -- 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
Re: mintty start menu icon
On 8/26/2010 1:35 PM, Vincent Rivière wrote: Andy Koppe wrote: Quite a lot of work though for what's not exactly a critical issue. I agree. But I wonder why what works for the standard console icon does not work for the mintty icon. Probably a special case. Um, http://cygwin.com/ml/cygwin/2010-08/msg00859.html. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- 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
Re: Will cron runnnnig as a service cause the server to lock up?
On 8/26/2010 1:37 PM, Blaine Miller wrote: Hello, Larry, I'm getting this message in the Event Log for cron kicking off... The description for Event ID ( 0 ) in Source ( /usr/sbin/cron ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: /usr/sbin/cron: PID 2160: (Administrator) CMD (/cygdrive/c/scripts/xfer_nab_csnab.sh). Does it mean anything? That's an informational message only. _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- 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
Re: Will cron runnnnig as a service cause the server to lock up?
Larry, Thanks, that's what I figured. Thanks for your continued assistance... Blaine Larry Hall (Cygwin) wrote: On 8/26/2010 1:37 PM, Blaine Miller wrote: Hello, Larry, I'm getting this message in the Event Log for cron kicking off... The description for Event ID ( 0 ) in Source ( /usr/sbin/cron ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: /usr/sbin/cron: PID 2160: (Administrator) CMD (/cygdrive/c/scripts/xfer_nab_csnab.sh). Does it mean anything? That's an informational message only. _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- 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 -- 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
How/Where do I get an older version of Cygwin?
I'm having cron and ssmtp issues with the new(er) version of Cygwin, 1.7.x.y. Barring getting these items straightened out, how do I revert to an older version? I've been installing from a network setup.exe. I don't believe this leaves a copy on a local system. My co-workers tell me there has to be a way to retrograde to an older version. Can anyone point me in the right direction? An older version of setup.exe perhaps? Thanks for your time and assistance... Blaine -- 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
How/Where do I get an older version of Cygwin?
I'm having cron and ssmtp issues with the new(er) version of Cygwin, 1.7.x.y. Barring getting these items straightened out, how do I revert to an older version? I've been installing from a network setup.exe. I don't believe this leaves a copy on a local system. My co-workers tell me there has to be a way to retrograde to an older version. Can anyone point me in the right direction? An older version of setup.exe perhaps? Thanks for your time and assistance... Blaine PS... I read in the archives the following quote... Rerun 'setup.exe' and pick Prev. There is no such option that I can find... -- 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
Re: How/Where do I get an older version of Cygwin?
On 8/26/2010 2:41 PM, Blaine Miller wrote: I'm having cron and ssmtp issues with the new(er) version of Cygwin, 1.7.x.y. Barring getting these items straightened out, how do I revert to an older version? I've been installing from a network setup.exe. I don't believe this leaves a copy on a local system. My co-workers tell me there has to be a way to retrograde to an older version. Can anyone point me in the right direction? An older version of setup.exe perhaps? I'm not sure why you believe your problems are based in recent Cygwin versions but if you wanted to backtrack to 1.5.x, see this link: http://cygwin.com/#win-9x This an unsupported version of 1.5.x so if you go there, you're on your own. If your problems truly are the result of some recent change to Cygwin, your best bet is to investigate them, report the problems, and work to get them resolved, especially if something has regressed. Otherwise, you'll be stuck in the past forever without an upgrade path. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- 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
Re: How/Where do I get an older version of Cygwin?
On 8/26/2010 3:03 PM, Blaine Miller wrote: snip PS... I read in the archives the following quote... Rerun 'setup.exe' and pick Prev. There is no such option that I can find... Look at the page where you select packages, just above the list of packages and to the right, next to the Category button. Cur is the default selected radio button. Prev is one of the other options. There is also honest to goodness actual documentation: http://cygwin.com/cygwin-ug-net/setup-net.html#setup-packages -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- 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
Re: How/Where do I get an older version of Cygwin?
Larry, I agree with you 100%. I'm getting heat from the folks above me to get Cygwin up and operational. We're using it to scp and rsync files from several linux boxes to a Cygwin-ed Windows 2003 box. Then we run Symantec Backup Exec for Windows to do tape backups of the resulting transferred files. Nothing I've said seem capable of convincing them that the problem is other than Cygwin. I keep pointing out we've replaced everything excpet the server hardware. Aside from downgrading and proving that the older version will have the same problems, I have no alternative at this time. Again, I believe that the new(er) version is the way to go. But I need to kill the cron issue and the ssmtp issue before I can demonstrate that the new version is not the problem and the hardware may be the real issue. Thanks for your continued support and assistance... Blaine Larry Hall (Cygwin) wrote: On 8/26/2010 2:41 PM, Blaine Miller wrote: I'm having cron and ssmtp issues with the new(er) version of Cygwin, 1.7.x.y. Barring getting these items straightened out, how do I revert to an older version? I've been installing from a network setup.exe. I don't believe this leaves a copy on a local system. My co-workers tell me there has to be a way to retrograde to an older version. Can anyone point me in the right direction? An older version of setup.exe perhaps? I'm not sure why you believe your problems are based in recent Cygwin versions but if you wanted to backtrack to 1.5.x, see this link: http://cygwin.com/#win-9x This an unsupported version of 1.5.x so if you go there, you're on your own. If your problems truly are the result of some recent change to Cygwin, your best bet is to investigate them, report the problems, and work to get them resolved, especially if something has regressed. Otherwise, you'll be stuck in the past forever without an upgrade path. -- 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
Re: How/Where do I get an older version of Cygwin?
Thanks! I read the Doc, but must have missed the Cur and Prev mentions... I'll read more carefully next time... Thanks again... Blaine Larry Hall (Cygwin) wrote: On 8/26/2010 3:03 PM, Blaine Miller wrote: snip PS... I read in the archives the following quote... Rerun 'setup.exe' and pick Prev. There is no such option that I can find... Look at the page where you select packages, just above the list of packages and to the right, next to the Category button. Cur is the default selected radio button. Prev is one of the other options. There is also honest to goodness actual documentation: http://cygwin.com/cygwin-ug-net/setup-net.html#setup-packages -- 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
Re: Emacs and DBUS
On 8/26/2010 12:16 AM, Michael Albinus wrote: Ken Brown writes: The blocking you observed when dbus.el is loaded doesn't occur with a build from the Emacs trunk (r101187). Correction: It occurs if and only if the system messagebus service is running. I'm confused: do you mean, the problem is happening when the system bus is running, or when it is *not* running? I suspect the latter case. I really meant it the way I said it: The problem occurs if the system bus *is* running. I've done some further testing, and here are the results, all with a build of emacs from the trunk, starting in the emacs src directory. 1. With the system bus not running, I start Emacs via 'dbus-launch ./emacs.exe -Q' and load dbus.el. In the *scratch* buffer I evaluate some of the expressions that you suggested in your earlier email: (dbus-get-unique-name :session) :1.0 (defun my-dbus-signal-handler (rest args) (message Signal from bus %s received: %s (dbus-event-bus-name last-input-event) args)) my-dbus-signal-handler (dbus-register-signal :session dbus-service-dbus dbus-path-dbus dbus-interface-dbus NameOwnerChanged 'my-dbus-signal-handler) ((:session org.freedesktop.DBus NameOwnerChanged) (org.freedesktop.DBus /org/freedesktop/DBus my-dbus-signal-handler)) Now I try 'dbus-monitor --session' in the xterm window from which I started emacs. This produces output in the xterm window, but I don't see anything in Emacs. Back to *scratch*: (dbus-get-unique-name :system) This throws me into the lisp debugger with the error (dbus-error Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused). I guess this is to be expected, since the system bus is not running. I now start the system bus via 'net start messagebus' in a shell, and I try again: (dbus-get-unique-name :system) :1.0 Is this to be expected, that I get the same name for :system that I got for :session? 2. With the system bus running, I start Emacs as above and load dbus.el. The cursor stops blinking, and Emacs becomes unresponsive. I can type C-g and hear a bell, and I can type C-x C-c to exit, but I can't get a response to any other key presses. I'm willing to try anything else you suggest. Otherwise, I hope you're able to debug this when you return from your travels. The unstripped emacs-X11.exe binary (Emacs 23.2) is at http://www.math.cornell.edu/~kbrown/emacs-X11.exe.bz2 and the binary for my build from the trunk is at http://www.math.cornell.edu/~kbrown/emacs.exe.bz2 Ken -- 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
Re: How/Where do I get an older version of Cygwin?
Larry, Again, I agree. I'm between a rock and a hard place here. I have to prove it's not the current version of Cygwin (also read *free*) and new hardware (read *costs them some money*). I have related to you and others at Cygwin user list both of my issues of cron possibly causing a system fault and can't kill the ssmtp dead.letter running over. I will pass along that I'm on my own with the regression to the older version. Perhaps that'll wake them up... I dunno. I'm just in the middle. Thanks again for your support and assistance. Blaine Blaine Miller wrote: Larry, I agree with you 100%. I'm getting heat from the folks above me to get Cygwin up and operational. We're using it to scp and rsync files from several linux boxes to a Cygwin-ed Windows 2003 box. Then we run Symantec Backup Exec for Windows to do tape backups of the resulting transferred files. Nothing I've said seem capable of convincing them that the problem is other than Cygwin. I keep pointing out we've replaced everything excpet the server hardware. Aside from downgrading and proving that the older version will have the same problems, I have no alternative at this time. Again, I believe that the new(er) version is the way to go. But I need to kill the cron issue and the ssmtp issue before I can demonstrate that the new version is not the problem and the hardware may be the real issue. Thanks for your continued support and assistance... Blaine Larry Hall (Cygwin) wrote: On 8/26/2010 2:41 PM, Blaine Miller wrote: I'm having cron and ssmtp issues with the new(er) version of Cygwin, 1.7.x.y. Barring getting these items straightened out, how do I revert to an older version? I've been installing from a network setup.exe. I don't believe this leaves a copy on a local system. My co-workers tell me there has to be a way to retrograde to an older version. Can anyone point me in the right direction? An older version of setup.exe perhaps? I'm not sure why you believe your problems are based in recent Cygwin versions but if you wanted to backtrack to 1.5.x, see this link: http://cygwin.com/#win-9x This an unsupported version of 1.5.x so if you go there, you're on your own. If your problems truly are the result of some recent change to Cygwin, your best bet is to investigate them, report the problems, and work to get them resolved, especially if something has regressed. Otherwise, you'll be stuck in the past forever without an upgrade path. -- 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 -- 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
Re: Emacs and DBUS
Ken Brown kbr...@cornell.edu writes: I'm confused: do you mean, the problem is happening when the system bus is running, or when it is *not* running? I suspect the latter case. I really meant it the way I said it: The problem occurs if the system bus *is* running. I've done some further testing, and here are the results, all with a build of emacs from the trunk, starting in the emacs src directory. Oops. 1. With the system bus not running, I start Emacs via 'dbus-launch ./emacs.exe -Q' and load dbus.el. In the *scratch* buffer I evaluate some of the expressions that you suggested in your earlier email: (dbus-get-unique-name :session) :1.0 (defun my-dbus-signal-handler (rest args) (message Signal from bus %s received: %s (dbus-event-bus-name last-input-event) args)) my-dbus-signal-handler (dbus-register-signal :session dbus-service-dbus dbus-path-dbus dbus-interface-dbus NameOwnerChanged 'my-dbus-signal-handler) ((:session org.freedesktop.DBus NameOwnerChanged) (org.freedesktop.DBus /org/freedesktop/DBus my-dbus-signal-handler)) Now I try 'dbus-monitor --session' in the xterm window from which I started emacs. This produces output in the xterm window, but I don't see anything in Emacs. No surprise. You have started an own session bus for Emacs, which is not known to dbus-monitor. You shall do # eval `dbus-launch --auto-syntax` dbus-launch returns some environment variables to be set, which is done by the eval command. The most interesting one is $DBUS_SESSION_BUS_ADDRESS # emacs Emacs will find the session bus via $DBUS_SESSION_BUS_ADDRESS. Load dbus.el, and eval the expressions as suggested. # dbus-monitor --session This is also a D-Bus client, which connects to the *same* session bus as Emacs did due to $DBUS_SESSION_BUS_ADDRESS. Now you should see the signal sent by dbus-monitor in Emacs. Back to *scratch*: (dbus-get-unique-name :system) This throws me into the lisp debugger with the error (dbus-error Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused). I guess this is to be expected, since the system bus is not running. I now start the system bus via 'net start messagebus' in a shell, and I try again: (dbus-get-unique-name :system) :1.0 Is this to be expected, that I get the same name for :system that I got for :session? It is not the same name, it simply looks like :-) Any D-bus daemon counts the registered clients. In both cases, Emacs has been the first one, so you've got the same identity name. The good message is that dbusbind.c is able to speak to both buses under Cygwin! 2. With the system bus running, I start Emacs as above and load dbus.el. The cursor stops blinking, and Emacs becomes unresponsive. I can type C-g and hear a bell, and I can type C-x C-c to exit, but I can't get a response to any other key presses. That I need to debug. Hmm, no system available next days. Maybe you can compile dbusbind.c with the compiler flag DBUS_DEBUG, something like this in the Emacs source tree: # MYCPPFLAGS='-DDBUS_DEBUG' make This enables test traces sent to Emacs' stdout (the shell where you have started it). I've introduced this flag while testing dbusbind.c, when it has blocked Emacs, and I didn't want to start gdb ... Maybe I can see something suspicious in the traces. I'm willing to try anything else you suggest. Otherwise, I hope you're able to debug this when you return from your travels. The unstripped emacs-X11.exe binary (Emacs 23.2) is at http://www.math.cornell.edu/~kbrown/emacs-X11.exe.bz2 and the binary for my build from the trunk is at http://www.math.cornell.edu/~kbrown/emacs.exe.bz2 Ken Thanks, and best regards, Michael. -- 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
RE: How/Where do I get an older version of Cygwin?
Larry Hall (Cygwin) sent the following at Thursday, August 26, 2010 3:24 PM Look at the page where you select packages, just above the list of packages and to the right, next to the Category button. Cur is the default selected radio button. Prev is one of the other options. There is also honest to goodness actual documentation: http://cygwin.com/cygwin-ug-net/setup-net.html#setup-packages Also, Prev gives you the previous version of everything. If you want the previous version of just a few packages, click on the version number in the chooser. There's also a cygwin time machine. Check the archives. - Barry Disclaimer: Statements made herein are not made on behalf of NIAID.
Re: How/Where do I get an older version of Cygwin?
Thanks Barry, Got it! Appreciate your time and assistance very much... Blaine Buchbinder, Barry (NIH/NIAID) [E] wrote: Larry Hall (Cygwin) sent the following at Thursday, August 26, 2010 3:24 PM Look at the page where you select packages, just above the list of packages and to the right, next to the Category button. Cur is the default selected radio button. Prev is one of the other options. There is also honest to goodness actual documentation: http://cygwin.com/cygwin-ug-net/setup-net.html#setup-packages Also, Prev gives you the previous version of everything. If you want the previous version of just a few packages, click on the version number in the chooser. There's also a cygwin time machine. Check the archives. - Barry Disclaimer: Statements made herein are not made on behalf of NIAID. -- 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
Re: compiling binutils misses sys/user.h
I try to compile binutils. It complaints a missing sys/user.h. On linux it would find it in /usr/include/sys/user.h. What is the way to go on Cygwin? A question with an answer pays ten times. So here we go for the archives: The solution is to set the host to the appropriate value. AFAIK it is autodetected by ./configure, as long as you don't set it manually to a wrong value as I did (indirectly). The host for cygwin is i686-pc-cygwin. Once it is set right the configure excludes modules that depend on kernel stuff like user.h. A kernel is simply not part of Cygwin. Al -- 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
SSH - Can't login
I've set up SSH with no problems in the past, yet when I try to log into itself I get the following: # ssh -v ca53...@localhost OpenSSH_5.6p1, OpenSSL 0.9.8o 01 Jun 2010 debug1: Reading configuration data /etc/ssh_config debug1: Connecting to localhost [127.0.0.1] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/544 debug1: identity file /home/ca53918/.ssh/id_rsa type 1 debug1: identity file /home/ca53918/.ssh/id_rsa-cert type -1 debug1: identity file /home/ca53918/.ssh/id_dsa type 2 debug1: identity file /home/ca53918/.ssh/id_dsa-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.6 debug1: match: OpenSSH_5.6 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.6 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server-client aes128-ctr hmac-md5 none debug1: kex: client-server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102410248192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY The authenticity of host 'localhost (127.0.0.1)' can't be established. RSA key fingerprint is Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'localhost' (RSA) to the list of known hosts. debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: Roaming not allowed by server debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,password,keyboard-interactive debug1: Next authentication method: publickey debug1: Offering RSA public key: /home/ca53918/.ssh/id_rsa Connection closed by 127.0.0.1 There's an immediate connection. The sshd service is running, and I've used both the ssh_user_config and ssh_host_config script to set up the environment. All the appropriate files look clean underneath my .ssh directory. Any help will be greatly appreciated. Thanks, and regards, Auteria W. Winzer Jr. -- 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
Windows batch program to open shell at directory specified as argument
hi, I use chere to right-click and open a shell at a given directory, and I was wondering if it is possible to setup a windows batch script that would accomplish the same thing from the Windows command line. In other words something like, c: cygwin_start_dir.bat c:\mystuff\directory which would then open my favourite shell at the c:\mystuff\directory. Thanks in advance. -- 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
Re: Updated [experimental]: {emacs,emacs-X11,emacs-el}-23.2-2
On Wed, Aug 18, 2010 at 5:18 AM, Ken Brown wrote: New releases of the emacs, emacs-X11, and emacs-el packages (23.2-2) are now available as experimental packages. These are rebuilds of the 23.2-1 packages, with D-BUS support. You will need to install libdbus1_3 in order to run the new binaries. Please report any regressions. If nothing serious is reported, the new releases will be promoted to current in a few weeks. I finally got around to installing this. I know it's the new version because it went looking for the D-BUS library that wasn't there. Now that that's fixed, it still says: This is GNU Emacs 23.2.1 of 2010-08-16 I assume that's the new version, why does it still say 23.2.1? - Jim -- Jim Reisert AD1C, jjreis...@alum.mit.edu, http://www.ad1c.us -- 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
Re: Updated [experimental]: {emacs,emacs-X11,emacs-el}-23.2-2
On 8/26/2010 8:51 PM, Jim Reisert AD1C wrote: On Wed, Aug 18, 2010 at 5:18 AM, Ken Brown wrote: New releases of the emacs, emacs-X11, and emacs-el packages (23.2-2) are now available as experimental packages. These are rebuilds of the 23.2-1 packages, with D-BUS support. You will need to install libdbus1_3 in order to run the new binaries. Please report any regressions. If nothing serious is reported, the new releases will be promoted to current in a few weeks. I finally got around to installing this. I know it's the new version because it went looking for the D-BUS library that wasn't there. Now that that's fixed, it still says: This is GNU Emacs 23.2.1 of 2010-08-16 I assume that's the new version, why does it still say 23.2.1? The '.1' at the end is added by Emacs. I don't know why. This has nothing to do with the fact that from Cygwin's point of view, it's release -2 of the emacs-23.2 package. You can see this with cygcheck: $ cygcheck -cd emacs Cygwin Package Information Package Version emacs23.2-2 Ken -- 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
Re: Emacs and DBUS
On 8/26/2010 4:16 PM, Michael Albinus wrote: Ken Brown writes: I'm confused: do you mean, the problem is happening when the system bus is running, or when it is *not* running? I suspect the latter case. I really meant it the way I said it: The problem occurs if the system bus *is* running. I've done some further testing, and here are the results, all with a build of emacs from the trunk, starting in the emacs src directory. Oops. 1. With the system bus not running, I start Emacs via 'dbus-launch ./emacs.exe -Q' and load dbus.el. In the *scratch* buffer I evaluate some of the expressions that you suggested in your earlier email: (dbus-get-unique-name :session) :1.0 (defun my-dbus-signal-handler (rest args) (message Signal from bus %s received: %s (dbus-event-bus-name last-input-event) args)) my-dbus-signal-handler (dbus-register-signal :session dbus-service-dbus dbus-path-dbus dbus-interface-dbus NameOwnerChanged 'my-dbus-signal-handler) ((:session org.freedesktop.DBus NameOwnerChanged) (org.freedesktop.DBus /org/freedesktop/DBus my-dbus-signal-handler)) Now I try 'dbus-monitor --session' in the xterm window from which I started emacs. This produces output in the xterm window, but I don't see anything in Emacs. No surprise. You have started an own session bus for Emacs, which is not known to dbus-monitor. You shall do # eval `dbus-launch --auto-syntax` dbus-launch returns some environment variables to be set, which is done by the eval command. The most interesting one is $DBUS_SESSION_BUS_ADDRESS # emacs Emacs will find the session bus via $DBUS_SESSION_BUS_ADDRESS. Load dbus.el, and eval the expressions as suggested. # dbus-monitor --session This is also a D-Bus client, which connects to the *same* session bus as Emacs did due to $DBUS_SESSION_BUS_ADDRESS. Now you should see the signal sent by dbus-monitor in Emacs. OK, I started the session bus the right way this time, but I still didn't see any signal from dbus-monitor in Emacs. I assume I should have seen something in the echo area? 2. With the system bus running, I start Emacs as above and load dbus.el. The cursor stops blinking, and Emacs becomes unresponsive. I can type C-g and hear a bell, and I can type C-x C-c to exit, but I can't get a response to any other key presses. That I need to debug. Hmm, no system available next days. Maybe you can compile dbusbind.c with the compiler flag DBUS_DEBUG, something like this in the Emacs source tree: # MYCPPFLAGS='-DDBUS_DEBUG' make This enables test traces sent to Emacs' stdout (the shell where you have started it). I've introduced this flag while testing dbusbind.c, when it has blocked Emacs, and I didn't want to start gdb ... Maybe I can see something suspicious in the traces. There's very little there. It prints the two lines xd_add_watch: fd 8 xd_add_watch: fd 9 and no more. Does this tell you anything? Ken -- 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
