Problem with cygwin-xfree mailimg list ?
Something fishy seems to have happen to the cygwin-xfree mailimg list. It usually receives 5 to 15 messages per day, with very few spam. For the last 5 days (March 01 - March 05), not a _single_ real message and 4 spams have got through. It looks like as if the spam filter had been turned around to allow only spam. .. that or Yaakov and John have taken very deserved vacations after killing the very last of the X server bugs, and every user in the world is using X happily ever since! - André Bleau Cygwin's OpenGL package volunteer maintainer. _ Réunissez-vous avec les gens qui vous sont proches- clavardez face à face grâce à Messenger. http://go.microsoft.com/?linkid=9650743 -- 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: Problem with cygwin-xfree mailimg list ?
André Bleau wrote: Something fishy seems to have happen to the cygwin-xfree mailimg list. It usually receives 5 to 15 messages per day, with very few spam. For the last 5 days (March 01 - March 05), not a _single_ real message and 4 spams have got through. It looks like as if the spam filter had been turned around to allow only spam. .. that or Yaakov and John have taken very deserved vacations after killing the very last of the X server bugs, and every user in the world is using X happily ever since! It's quiet...too quiet... -- 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: Problem with cygwin-xfree mailimg list ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Jon TURNEY wrote: André Bleau wrote: .. that or Yaakov and John have taken very deserved vacations after killing the very last of the X server bugs, and every user in the world is using X happily ever since! It's quiet...too quiet... At least until the upcoming update, which will surely stir things up. :-) Yaakov Cygwin/X -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkmxZh4ACgkQpiWmPGlmQSO/fQCgx/dm5OtVQMYUFh1/PjZgvMV8 nk0AoOyVkbmi3pJTy+8Z226P1wl1yGVV =QvQw -END PGP SIGNATURE- -- 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: Problem with cygwin-xfree mailimg list ?
On Fri, Mar 06, 2009 at 12:06:23PM -0600, Yaakov (Cygwin/X) wrote: Jon TURNEY wrote: Andr? Bleau wrote: .. that or Yaakov and John have taken very deserved vacations after killing the very last of the X server bugs, and every user in the world is using X happily ever since! It's quiet...too quiet... At least until the upcoming update, which will surely stir things up. :-) Heh, heh, heh... cgf -- 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/
Solution to: -clipboard does not work when using XDMCP connection.
This e-mail is for documentation purposes, no further help is needed. With the default Cygwin/X install, the XWin.exe -clipboard option does not seem to work when connecting using the XDMCP protocol to a Linux server running GDM. The unix and Windows clipboards would not synchronized and copy/paste did not work across sessions. In /var/log/XWin.0.log, these messages were displayed: - winInitClipboard () winProcQueryTree - winInitClipboard returned. winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP winClipboardProc - DISPLAY=127.0.0.1:0.0 AUDIT: Fri Mar 6 13:23:07 2009: 4144 XWin: client 4 rejected from IP 127.0.0.1 winProcEstablishConnection - ProcEstablishConnection failed, bailing. winClipboardProc - Could not open display, try: 1, sleeping: 4 AUDIT: Fri Mar 6 13:23:11 2009: 4144 XWin: client 4 rejected from IP 127.0.0.1 winClipboardProc - Could not open display, try: 2, sleeping: 4 AUDIT: Fri Mar 6 13:23:15 2009: 4144 XWin: client 4 rejected from IP 127.0.0.1 winClipboardProc - Could not open display, try: 3, sleeping: 4 - My launch batch file for XWin.exe is fairly simple: @echo off start Title C:\cygwin\bin\XWin.exe -clipboard -query 192.168.0.1 I tried a number of solutions offered by others, but this one solved the problem. Create a text file in your Cygwin installation folder called: /etc/X0.hosts (that's X-zero dot hosts) It should contain one line: localhost Effectively, this permissions file allows the X server to access your Windows machine's local IP address (127.0.0.1). This file should probably be part of the standard Cygwin/X install. It also doesn't seem to be mentioned in the Cygwin/X documentation (maybe its there and I just missed it). Now the log file reports: - winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP winClipboardProc - DISPLAY=127.0.0.1:0.0 winProcEstablishConnection - Clipboard client already launched, returning. winClipboardProc - XOpenDisplay () returned and successfully opened the display. - and the clipboard now works properly. Copy and Paste between windows and X works as expected. For GDM users, you may also need to set an entry in your gdm config file located at: /etc/gdm/gdm.conf In the [daemon] section: [daemon] KillInitClients=false I haven't confirm the GDM requirement but this is how it's set up in my configuration. Hope this helps someone. Chris. -- 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: Problem with cygwin-xfree mailimg list ?
Christopher Faylor wrote... On Fri, Mar 06, 2009 at 12:06:23PM -0600, Yaakov (Cygwin/X) wrote: Jon TURNEY wrote: Andr? Bleau wrote: .. that or Yaakov and John have taken very deserved vacations after killing the very last of the X server bugs, and every user in the world is using X happily ever since! It's quiet...too quiet... At least until the upcoming update, which will surely stir things up. :-) Heh, heh, heh... I hope the clipboard problem gets fixed... josé -- 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: Problem with cygwin-xfree mailimg list ?
On Fri, Mar 06, 2009 at 02:12:12PM -0500, jose isaias cabrera wrote: Christopher Faylor wrote... On Fri, Mar 06, 2009 at 12:06:23PM -0600, Yaakov (Cygwin/X) wrote: Jon TURNEY wrote: Andr? Bleau wrote: .. that or Yaakov and John have taken very deserved vacations after killing the very last of the X server bugs, and every user in the world is using X happily ever since! It's quiet...too quiet... At least until the upcoming update, which will surely stir things up. :-) Heh, heh, heh... I hope the clipboard problem gets fixed... I'm sure they will *claim* that it is fixed but that is just to mess with your heads. cgf -- 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/
[spam] The economy is bad, create your own stimulus package with these email listings
billing etc.. 1,000,000 emails - only $150.00 send email to: mad...@statlists.com to terminate please send a blank message to dele...@statlists.com -- 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 cygwin.din posix.s ...
CVSROOT:/cvs/src Module name:src Changes by: cori...@sourceware.org 2009-03-06 10:09:55 Modified files: winsup/cygwin : ChangeLog cygwin.din posix.sgml winsup/cygwin/include/cygwin: version.h Log message: * cygwin.din: Export wprintf, fwprintf, swprintf, vwprintf, vfwprintf, vswprintf. Sort. * posix.sgml: Move fwprintf, swprintf, vwprintf, vfwprintf, vswprintf to SUSv4 list. Sort SUSv4 list. * include/cygwin/version.h: Bump API minor number. Patches: http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/ChangeLog.diff?cvsroot=srcr1=1.4392r2=1.4393 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/cygwin.din.diff?cvsroot=srcr1=1.202r2=1.203 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/posix.sgml.diff?cvsroot=srcr1=1.26r2=1.27 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/include/cygwin/version.h.diff?cvsroot=srcr1=1.284r2=1.285
src/winsup/cygwin ChangeLog cygwin.din net.cc ...
CVSROOT:/cvs/src Module name:src Changes by: cori...@sourceware.org 2009-03-06 16:31:26 Modified files: winsup/cygwin : ChangeLog cygwin.din net.cc posix.sgml winsup/cygwin/include/cygwin: version.h winsup/cygwin/libc: minires.c Log message: * cygwin.din: Export gethostbyname2. * net.cc: define _CYGWIN_IN_H and include resolv.h. (realloc_ent): New function. (dup_ent): Call realloc_ent. (memcpy4to6): New function. (dn_length1): New function. (gethostby_helper): New function. (gethostbyname2): New function. * posix.sgml: Add gethostbyname2. * include/cygwin/version.h: Bump API minor number. * libc/minires.c (get_options): Look for inet6 and apply bounds to retry and retrans. (res_ninit): Set the default options at the beginning. (dn_expand): Fix off by one. Patches: http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/ChangeLog.diff?cvsroot=srcr1=1.4393r2=1.4394 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/cygwin.din.diff?cvsroot=srcr1=1.203r2=1.204 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/net.cc.diff?cvsroot=srcr1=1.249r2=1.250 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/posix.sgml.diff?cvsroot=srcr1=1.27r2=1.28 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/include/cygwin/version.h.diff?cvsroot=srcr1=1.285r2=1.286 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/libc/minires.c.diff?cvsroot=srcr1=1.5r2=1.6
Re: [Patch] gethostbyname2 again
On Fri, Mar 06, 2009 at 09:41:00AM -0500, Pierre A. Humblet wrote: - Original Message - [snip] I see you've joined the throng of people who duplicate bits from the header in the body of a message. Do you really need to do this? | On Tue, Mar 03, 2009 at 12:50:21PM -0500, Pierre A. Humblet wrote: | | To avoid real-time checks, I could do as what dup_ent does, and have 4 versions | of the realloc_ent function, one main one with dst and sz arguments (that one | would be called by dup_ent without any run-time checks) and 3 (actually only | 1 is needed for now) that invoke the main one with the correct dst based on the | type of the src argument . The src argument would be null but would have the | right type! That seems to meet your wishes. OK? | | Yes. OK, here it the patch for realloc_ent. See also attachement. The third chunk (the change to dup_ent) is not essential. In addition in the patch that Corinna sent on March 3, the line + ret = (hostent *) realloc_ent (sz, unionent::t_hostent); should be changed to ret = realloc_ent (sz, (hostent *) NULL); In the Changelog the line (dup_ent): Remove dst argument and call realloc_ent. should either be deleted or Remove dst argument and c should be replaced by C. This is ok with one very minor formatting nit. Please check in with an appropriate changelog. +static inline hostent * +realloc_ent (int sz, hostent * ) ^ extra space cgf
Re: [Patch] gethostbyname2 again
- Original Message - From: Christopher Faylor cgf-use-the-mailinglist-please | On Fri, Mar 06, 2009 at 09:41:00AM -0500, Pierre A. Humblet wrote: | || | This is ok with one very minor formatting nit. Please check in with an | appropriate changelog. | | +static inline hostent * | +realloc_ent (int sz, hostent * ) |^ | extra space OK. I can't do that before Mon eve. It would be easier if Corinna could merge this patch and the previous one (she has the latest version) and apply the whole thing at once, with one changelog block. Pierre
Re: [Patch] gethostbyname2 again
On Mar 6 10:56, Pierre A. Humblet wrote: From: Christopher Faylor cgf-use-the-mailinglist-please | This is ok with one very minor formatting nit. Please check in with an | appropriate changelog. | | +static inline hostent * | +realloc_ent (int sz, hostent * ) |^ | extra space OK. I can't do that before Mon eve. It would be easier if Corinna could merge this patch and the previous one (she has the latest version) and apply the whole thing at once, with one changelog block. Done. Thanks again for this function. This will give us a few new occasions for the future, as I pointed out in my first reply. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
[ANNOUNCEMENT] [1.7] Updated: cygwin-1.7.0-42
Hi folks, I just uploaded a new Cygwin 1.7 test release, 1.7.0-42. Cygwin 1.7 is a major jump from Cygwin 1.5.x. The list with all changes related to Cygwin 1.5.25 is attached below. Just download http://cygwin.com/setup-1.7.exe and use that setup tool to install Cygwin 1.7. As usual, please report bugs and problems to the mailing list cygwin AT cygwin DOT com. We also have a new User's Guide for 1.7, which is currently located at http://cygwin.com/1.7/cygwin-ug-net/cygwin-ug-net.html We also now have new API documentation http://cygwin.com/1.7/cygwin-api/cygwin-api.html And we have a new FAQ, though very likely not quite complete since we still don't know what exactly *is* a FAQ realted to Cygwin 1.7. http://cygwin.com/1.7/faq/faq.html Bug fixes and extensions to the documentation in the form of patches to the source SGML files are much appreciated. The SGML sources are located in the CVS repository under the winsup/doc directory, for example here: http://cygwin.com/cgi-bin/cvsweb.cgi/src/winsup/doc/?cvsroot=src Same goes for Cygwin patches in general, of course. === THIS IS STILL A TEST RELEASE. DON'T USE IN PRODUCTION ENVIRONMENTS. Nevertheless I'd like to encourage everyone to give 1.7 a shot. Due to internal changes it is possible to install a 1.7 release in parallel to a 1.5 release and even run 1.7 processes in parallel to 1.5 processes. * The processes will not know about each other! Any try to interact * between 1.7-based and 1.5-based processes will lead to, at least, funny * results. To install a 1.7 release in parallel to a 1.5 release, all you have to do is to choose another root directory (for instance: C:\cygwin-1.7) in setup-1.7's Choose Installation Directory dialog. * NOTE: Due to the way setup-1.7 works, you have to change the directory * right the first time you visit this dialog! If you pressed the Next * button and then Back again, it's already too late and setup-1.7 will * create a broken 1.7 install. If you pressed Next by mistake, exit * setup-1.7 and start it again. === What's new in contrast to 1.7.0-41 === - New functions wprintf, fwprintf, swprintf, vwprintf, vfwprintf, vswprintf. - New setlocale implementation allows to specify POSIX locale strings. You can now use, for instance in bash, `export LC_ALL=en_US.UTF-8'. The language and territory will be ignored for now, the charset will be used by multibyte-releated functions. - wctomb/mbtowc can now handle surrogate pairs. - So far there was a hack in the 1.7.0 Cygwin DLL which disabled DEP (Data Execution Prevention) on a per-application base when running on a Windows Server 2008 Terminal Server. This was necessary to avoid spurious crashes of Cygwin applications due to a bug in a Windows DLL. This DLL (tsappcmp.dll) is only called on Terminal Servers for applications which don't have the TS-awareness flag set in the executable's file header. It turned out that we can simply avoid the crashes by switching on the TS-awareness bit in executables. In future this will be done automatically when building new applications. For older applications there will be a new tool called `peflags', curtesy Charles Wilson, which allows to set this flag (among others) on already existing executables. Therefore, and because the hack to switch off DEP in the DLL is a major performance killer, the hack has now been disabled in the DLL. Bugfixes: = - Fix select(2) on FIFOs. - A long standing problem in newlib's setlocale() function disallows to read the locale specific LC_* environment variables. - Fix mbtowc/wctomb so as not to handle invalid 5 and 6 byte UTF-8 sequences. Fix wctomb singlebyte behaviour in case the icoming wide char doesn't fit. - Fix cygdrive output in mount -m command. FAQ: - Q: How do I know that I'm running Cygwin 1.7.0-41? A: The `uname -v' command prints 2009-03-06 11:28 Have fun, Corinna Here's the list of user-visible changes in 1.7.0 related to 1.5.25: === OS releated changes: - Windows 95, 98 and Me are not supported anymore. The new DLL will not run on any of these systems. File Access related changes: - Mount points are no longer stored in the registry. Use /etc/fstab and /etc/fstab.d/$USER instead. Mount points created with mount(1) are only local to the current session and disappear when the last Cygwin process in the session exits. - PATH_MAX is now 4096. Internally, path names can be as long as the underlying OS can handle (32K). - UTF-8 filenames are supported now. So far, this requires to set the environment variable CYGWIN to contain codepage:utf8. but this will likely disappear at one point. The
RE: How can I assign a hotkey to run a cygwin/bash script?
Dave Korn wrote on Thursday, March 05, 2009 10:48 PM: Hongyi Zhao wrote: Hi all, I've written a cygwin/bash script and want to run it by a customized hotkey laterly, it this possible? Sure. Create a windows shortcut to bash.exe, open the properties. In Target, after C:\cygwin\bin\bash.exe, add --login -i -c your command here in bash syntax Although I normally defer to Dave, who is far more knowledgeable in these things than I am, I am surprised that he suggests the -i option that makes bash interactive. If the shortcut does not work the way you want, try dropping it. (The scripts that I run from Windows shortcuts work fine with --login -c without the -i. - Barry Disclaimer: Statements made herein are not made on behalf of NIAID. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
problem under cygwin with sh, bash, ksh
Hi All... I've searched and found nothing this script runs just fine on
AIX, Solaris, and Linux, but under cygwin, the array VALUE prints only
blanks.. has anyone else run into this... I've tried a bunch of different
things around typecast, etc, but it looks like VALUE is local in the table_it
function... any thoughts???
table_it()
{
case $1 in
class) VALUE[0]=$2 ;;
source) VALUE[1]=$2 ;;
server) VALUE[2]=$2 ;;
sub_source) VALUE[3]=$2 ;;
msg_catalog) VALUE[4]=$2 ;;
epage) VALUE[5]=$2 ;;
threshold) VALUE[6]=$2 ;;
*) echo UNKNOWN $1 $2 ;;
esac
}
TEMP1=/tmp/parse_log4j_01
find $1 -type f -print | while read filename rest
do
echo $filename
grep Tec_ $filename | dd conv=lcase 2/dev/null | sed -e 's/param
name=//
' -e 's/\///' -e 's///g' -e 's/value=//' -e 's/tec_slotpair//' -e 's/tec_//' -
e 's/,/\n/g' -e 's/:/ /g' | while read flip flop
do
table_it $flip $flop
done
grep tec_ $filename | dd conv=lcase 2/dev/null | sed -e 's/param
name=//
' -e 's/\///' -e 's///g' -e 's/value=//' -e 's/tec_slotpair//' -e 's/tec_//' -
e 's/,/\n/g' -e 's/:/ /g' | while read flip flop
do
table_it $flip $flop
done
echo 0 ${VALUE[0]}
echo 1 ${VALUE[1]}
echo 2 ${VALUE[2]}
echo 3 ${VALUE[3]}
echo 4 ${VALUE[4]}
echo 5 ${VALUE[5]}
echo 6 ${VALUE[6]}
done
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
Re: How can I assign a hotkey to run a cygwin/bash script?
Buchbinder, Barry (NIH/NIAID) [E] wrote: Dave Korn wrote on Thursday, March 05, 2009 10:48 PM: Hongyi Zhao wrote: Hi all, I've written a cygwin/bash script and want to run it by a customized hotkey laterly, it this possible? Sure. Create a windows shortcut to bash.exe, open the properties. In Target, after C:\cygwin\bin\bash.exe, add --login -i -c your command here in bash syntax Although I normally defer to Dave, who is far more knowledgeable in these things than I am, I am surprised that he suggests the -i option that makes bash interactive. If the shortcut does not work the way you want, try dropping it. (The scripts that I run from Windows shortcuts work fine with --login -c without the -i. Yes, I was being overenthusiastic in making sure the startup scripts run, where --login is sufficient on its own. However you'll still want '-i' if any of the scripts prompt for user input, or you won't get readline. cheers, DaveK -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: How can I assign a hotkey to run a cygwin/bash script?
Dave Korn wrote: Although I normally defer to Dave, who is far more knowledgeable in these things than I am, I am surprised that he suggests the -i option that makes bash interactive. BTW, the fact we're talking about launching scripts from a hot key is what made me think that -i might be appropriate: there's clearly an interactive user at the console in this situation. cheers, DaveK -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Problem with cygwin-xfree mailimg list ?
Something fishy seems to have happen to the cygwin-xfree mailimg list. It usually receives 5 to 15 messages per day, with very few spam. For the last 5 days (March 01 - March 05), not a _single_ real message and 4 spams have got through. It looks like as if the spam filter had been turned around to allow only spam. .. that or Yaakov and John have taken very deserved vacations after killing the very last of the X server bugs, and every user in the world is using X happily ever since! - André Bleau Cygwin's OpenGL package volunteer maintainer. _ Réunissez-vous avec les gens qui vous sont proches- clavardez face à face grâce à Messenger. http://go.microsoft.com/?linkid=9650743 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: 1.5.25-Cygstart not showing visible window
Jay Cross wrote on Friday, March 06, 2009 1:09 AM: I'm having an problem with cygstart. When I run a program with it in a bash shell on my cygwin machine everything is fine. When I'm accessing cygwin through another machine (using SSH through Putty) the program window never appears regardless of how I specify command args. The program I specify is running in my Task Manager (Process Explorer) but it has no visible window associated. I can hear sounds it makes.. but no window appears. Is this a feature or a bug - or something in between? It sounds like sshd is lacking the Interact With Desktop flag. You can either remove and reinstall the service with cygrunsrv (and add the -i flag when you reinstall), or open the Cygwin sshd Windows service Properties and check the Allow service to interact with desktop box in the Log On tab. I've tried changing the ownership of cygrunsrv, bash, and sshd. This behavior also occurs when I run the script below. I'm trying to run programs/files on my TV computer at the command of my laptop computer. It would be useful if they actually displayed on TV computer. I know I could use a VNC solution, but it's not really what I'm looking for. Cygstart seems like it is designed to do something similar to what I want, am I asking to much? Have I missed something? Thanks in advance to anyone that can help. HTH, -- Bryan Thrall FlightSafety International bryan.thr...@flightsafety.com -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
1.5.25: Regtool can not find registry?
Hello, I had a working cygwin installation for several years on this machine. But then I decided to remove and reinstall it. (I reinstalled cygwin only, not the whole machine). Since the reinstall, regtool refuses to work. It always complains that it can not find the specified file. Strange enough, cygcheck _is_ able to read information from the registry. Here are examples of what I get: $ regtool get '/HKLM/SOFTWARE/Cygnus Solutions/Cygwin Error (2): Das System kann die angegebene Datei nicht finden. $ regtool get '/HKLM/SOFTWARE/Cygnus Solutions/Cygwin/mounts v2' Error (2): Das System kann die angegebene Datei nicht finden. Any ideas how to track down this problem? BTW: I've attached cygcheck.out to this mail. SysDir: C:\WINNT\system32 WinDir: C:\WINNT USER = 'jw' PWD = '/cygdrive/d' CYGWIN = 'tty title ntea check_case:adjust' HOME = '/cygdrive/h' MAKE_MODE = 'unix' HKEY_CURRENT_USER\Software\Cygnus Solutions HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2 (default) = '/cygdrive' cygdrive flags = 0x0022 HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2\/ (default) = 'd:\cygwin' flags = 0x0002 HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2\/usr/bin (default) = 'd:\cygwin/bin' flags = 0x0002 HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2\/usr/lib (default) = 'd:\cygwin/lib' flags = 0x0002 HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\Program Options HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\Program Options c: hd NTFS 30725Mb 52% CP CS UN PA FC SYSTEM d: hd NTFS 10001Mb 81% CP CS UN PA FC Volume e: hd NTFS 24999Mb 1% CP CS UN PA FC Volume f: hd NTFS 10589Mb 1% CP CS UN PA FC Volume g: fd FAT32 1024Mb 1% CPUN h: net NTFS310851Mb 41% CP CS UN PA FC Data I n: net NTFS 8323Mb 8% CP CS UN PA FC DSK0PAR3 t: net NTFS 1409993Mb 53% CP CS UN PA FC Data z: cd CDFS 2358Mb 100%CS UN CDROM d:\cygwin / userbinmode d:\cygwin/bin /usr/bin userbinmode d:\cygwin/lib /usr/lib userbinmode . /cygdrive userbinmode,cygdrive Found: d:\cygwin\bin\awk.exe Found: d:\cygwin\bin\bash.exe Found: d:\cygwin\bin\cat.exe Found: d:\cygwin\bin\cp.exe Found: d:\cygwin\bin\cpp.exe Not Found: crontab Found: d:\cygwin\bin\find.exe Found: d:\cygwin\bin\gcc.exe Found: d:\cygwin\bin\gdb.exe Found: d:\cygwin\bin\grep.exe Found: d:\cygwin\bin\kill.exe Found: d:\cygwin\bin\ld.exe Found: d:\cygwin\bin\ls.exe Found: d:\cygwin\bin\make.exe Found: d:\cygwin\bin\mv.exe Found: d:\cygwin\bin\patch.exe Found: d:\cygwin\bin\perl.exe Found: d:\cygwin\bin\rm.exe Found: d:\cygwin\bin\sed.exe Found: d:\cygwin\bin\ssh.exe Found: d:\cygwin\bin\sh.exe Found: d:\cygwin\bin\tar.exe Found: d:\cygwin\bin\test.exe Not Found: vi Found: d:\cygwin\bin\vim.exe 107k 2009/01/18 d:\cygwin\bin\cygapr-1-0.dll 89k 2008/09/01 d:\cygwin\bin\cygaprutil-1-0.dll 72k 2008/10/26 d:\cygwin\bin\cygaudio-2.dll 61k 2008/04/01 d:\cygwin\bin\cygbz2-1.dll 448k 2008/12/16 d:\cygwin\bin\cygcairo-2.dll 16k 2005/10/11 d:\cygwin\bin\cygcompface-0.dll 7k 2003/10/19 d:\cygwin\bin\cygcrypt-0.dll 1074k 2009/01/08 d:\cygwin\bin\cygcrypto-0.9.8.dll 221k 2007/06/30 d:\cygwin\bin\cygcurl-4.dll 703k 2007/12/17 d:\cygwin\bin\cygdb-4.2.dll 943k 2007/12/17 d:\cygwin\bin\cygdb-4.5.dll 1036k 2007/12/17 d:\cygwin\bin\cygdb_cxx-4.2.dll 1296k 2007/12/17 d:\cygwin\bin\cygdb_cxx-4.5.dll 118k 2008/05/09 d:\cygwin\bin\cygexpat-1.dll 67k 2008/08/07 d:\cygwin\bin\cygexslt-0.dll 286k 2006/08/06 d:\cygwin\bin\cygfcgi++-0.dll 30k 2006/08/06 d:\cygwin\bin\cygfcgi-0.dll 161k 2008/06/01 d:\cygwin\bin\cygfontconfig-1.dll 19k 2008/10/26 d:\cygwin\bin\cygfontenc-1.dll 40k 2006/11/15 d:\cygwin\bin\cygform-8.dll 45k 2001/04/25 d:\cygwin\bin\cygform5.dll 48k 2003/08/09 d:\cygwin\bin\cygform7.dll 430k 2009/01/28 d:\cygwin\bin\cygfreetype-6.dll 414k 2008/06/16 d:\cygwin\bin\cyggcrypt-11.dll 19k 2006/11/19 d:\cygwin\bin\cyggdbm-4.dll 8k 2006/11/19 d:\cygwin\bin\cyggdbm_compat-4.dll 466k 2009/02/07 d:\cygwin\bin\cyggit.dll 2297k 2008/10/29 d:\cygwin\bin\cygGL-1.dll 148k 2006/10/27 d:\cygwin\bin\cygglitz-1.dll 20k 2006/10/27 d:\cygwin\bin\cygglitz-glx-1.dll 219k 2008/10/04 d:\cygwin\bin\cyggmp-3.dll 288k 2008/10/04 d:\cygwin\bin\cyggmpxx-3.dll 13k 2008/03/08 d:\cygwin\bin\cyggpg-error-0.dll 5491k 2008/11/27 d:\cygwin\bin\cyggs-8.dll 17k 2001/06/28 d:\cygwin\bin\cyghistory4.dll 29k 2003/08/10 d:\cygwin\bin\cyghistory5.dll 24k 2008/11/29 d:\cygwin\bin\cyghistory6.dll 72k 2008/10/26 d:\cygwin\bin\cygICE-6.dll 271k 2007/08/24 d:\cygwin\bin\cygicons-0.dll
RE: How can I assign a hotkey to run a cygwin/bash script?
-Original Message- From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On Behalf Of Dave Korn Sent: Thursday, March 05, 2009 9:48 PM To: cygwin@cygwin.com Subject: Re: How can I assign a hotkey to run a cygwin/bash script? Hongyi Zhao wrote: Hi all, I've written a cygwin/bash script and want to run it by a customized hotkey laterly, it this possible? Sure. Create a windows shortcut to bash.exe, open the properties. In Target, after C:\cygwin\bin\bash.exe, add --login -i -c your command here in bash syntax and you can then assign a key-combination to the shortcut (as for any other windows shortcut) by clicking in Shortcut key and typing your ctrl-shift-alt-whatever combination. The your command here part can be any valid shell commands, or you can just pass in the path to a script you want run. (Remember to either chmod +x the script first, or to use the 'source' bash builtin to execute it). You'll probably want to change the Start in dir to your homedir or /tmp or somewhere similar, depending on your needs. cheers, DaveK -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ It appears that Windows XP shortcuts have a limitation. The shortcut must be to a target on the desktop (or to a target in a folder on desktop). -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: How can I assign a hotkey to run a cygwin/bash script?
Arun Biyani wrote: It appears that Windows XP shortcuts have a limitation. The shortcut must be to a target on the desktop (or to a target in a folder on desktop). Surely you can't mean what you've written there exactly how you've worded it: I thought shortcuts can point *to* anywhere, on any windows version. Did you mean that in order for the /hotkey/ to work, the shortcut itself has to be *on* the desktop or in a folder on the desktop? cheers, DaveK -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: How can I assign a hotkey to run a cygwin/bash script?
Arun Biyani wrote: It appears that Windows XP shortcuts have a limitation. The shortcut must be to a target on the desktop (or to a target in a folder on desktop). Surely you can't mean what you've written there exactly how you've worded it: I thought shortcuts can point *to* anywhere, on any windows version. Did you mean that in order for the /hotkey/ to work, the shortcut itself has to be *on* the desktop or in a folder on the desktop? cheers, DaveK Yes. Meant exactly that. I created a shortcut on desktop for mintty. Assigned it the key ctrl+alt+M. I like my desktop to be uncluttered. So after assigning the key, I moved the shortcut icon into my work folder /c/home/wrk. The hotkey stopped working. I then moved the icon back to the desktop and it worked again. Now, all my hot-key-assigned shortcuts sit in a folder shortcuts on the desktop and they all work. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: How can I assign a hotkey to run a cygwin/bash script?
Arun Biyani wrote: Yes. Meant exactly that. I created a shortcut on desktop for mintty. Assigned it the key ctrl+alt+M. I like my desktop to be uncluttered. So after assigning the key, I moved the shortcut icon into my work folder /c/home/wrk. The hotkey stopped working. I then moved the icon back to the desktop and it worked again. Now, all my hot-key-assigned shortcuts sit in a folder shortcuts on the desktop and they all work. Thanks for the tip! :) cheers, DaveK -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: How can I assign a hotkey to run a cygwin/bash script?
Dave Korn wrote on Friday, March 06, 2009 11:21 AM: Arun Biyani wrote: Yes. Meant exactly that. I created a shortcut on desktop for mintty. Assigned it the key ctrl+alt+M. I like my desktop to be uncluttered. So after assigning the key, I moved the shortcut icon into my work folder /c/home/wrk. The hotkey stopped working. I then moved the icon back to the desktop and it worked again. Now, all my hot-key-assigned shortcuts sit in a folder shortcuts on the desktop and they all work. Thanks for the tip! :) While not much done my MS would shock me, that seems sort of strange. I looked at the properties of shortcuts on my Desktop, in the Start Menu, and in a directory outside of C:\Documents and Settings (the equivalent of c:\home\wrk). In none was the option to set a hotkey grayed out. (Granted, MS might have forgotten to do that.) What happens when you assign the hotkey *after* the shortcut is in c:\home\wrk? Think about it. When you assign the shortcut to a hotkey, you are asking Windows to run the shortcut after you hit the hotkey. I would think that Windows keeps a table of hotkeys and shortcuts (not targets) and it looks for the shortcut itself when you hit the hotkey so the shortcut's contents can be read. If you have moved the shortcut after assigning the hotkey, Windows cannot find it and nothing happens. BTW, if assigning the hotkey after the shortcut is in c:\home\wrk really doesn't work, I suspect that the Start Menu may. Of course, I neither use hotkeys (so I don't know from experience) nor have I experimented by actually assigning a hotkey. So YMMV. Good luck. - Barry Disclaimer: Statements made herein are not made on behalf of NIAID. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: How can I assign a hotkey to run a cygwin/bash script?
On Fri, Mar 6, 2009 at 10:59 AM, Arun Biyani abiy...@dickey-john.com wrote: Arun Biyani wrote: It appears that Windows XP shortcuts have a limitation. The shortcut must be to a target on the desktop (or to a target in a folder on desktop). Surely you can't mean what you've written there exactly how you've worded it: I thought shortcuts can point *to* anywhere, on any windows version. Did you mean that in order for the /hotkey/ to work, the shortcut itself has to be *on* the desktop or in a folder on the desktop? cheers, DaveK Yes. Meant exactly that. I created a shortcut on desktop for mintty. Assigned it the key ctrl+alt+M. I like my desktop to be uncluttered. So after assigning the key, I moved the shortcut icon into my work folder /c/home/wrk. The hotkey stopped working. I then moved the icon back to the desktop and it worked again. Now, all my hot-key-assigned shortcuts sit in a folder shortcuts on the desktop and they all work. The hotkey is pointing to the location where you had the shortcut. Since you moved it, there's nothing there for the hotkey to execute. Hotkeys are not attached to the shortcut, even though the horrible UI the Explorer uses seems to indicate they are. They are stored in a systemwide table that doesn't know if you've moved the target of the key. I recommend avoiding the built-in hotkey fields in shortcuts, and instead use any one of the numerous hotkey managers out there, such as the one I've written here: http://directedge.us/content/winhotkey -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: How can I assign a hotkey to run a cygwin/bash script?
Hello, * On Fri, Mar 06, 2009 at 12:07:37PM -0500 Buchbinder, Barry (NIH/NIAID) [E] wrote: I looked at the properties of shortcuts on my Desktop, in the Start Menu, and in a directory outside of C:\Documents and Settings (the equivalent of c:\home\wrk). In none was the option to set a hotkey grayed out. They do not need to be grayed out: You can set these option. Unfortunately, they do not have any effect. This is something different. I would think that Windows keeps a table of hotkeys and shortcuts (not targets) and it looks for the shortcut itself when you hit the hotkey so the shortcut's contents can be read. Well, we can think about many things: However, this is not the way it works on Windows, obviously. BTW, if assigning the hotkey after the shortcut is in c:\home\wrk really doesn't work, I suspect that the Start Menu may. Yes, the start menu works. This was news for me, too. In quick start, it does not work, though. So, start menu and desktop work. Anything else? ;) Best regards, Spiro. -- Spiro R. Trikaliotis http://opencbm.sf.net/ http://www.trikaliotis.net/ http://www.viceteam.org/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: How can I assign a hotkey to run a cygwin/bash script?
On Fri, Mar 6, 2009 at 12:58 PM, Spiro Trikaliotis an-cyg...@spiro.trikaliotis.net wrote: Hello, * On Fri, Mar 06, 2009 at 12:07:37PM -0500 Buchbinder, Barry (NIH/NIAID) [E] wrote: I looked at the properties of shortcuts on my Desktop, in the Start Menu, and in a directory outside of C:\Documents and Settings (the equivalent of c:\home\wrk). In none was the option to set a hotkey grayed out. They do not need to be grayed out: You can set these option. Unfortunately, they do not have any effect. This is something different. I would think that Windows keeps a table of hotkeys and shortcuts (not targets) and it looks for the shortcut itself when you hit the hotkey so the shortcut's contents can be read. Well, we can think about many things: However, this is not the way it works on Windows, obviously. Windows keeps a systemwide table of hotkeys, and when one is pressed Windows runs whatever is in the table as the target. If the target is a shortcut, it opens the shortcut. If it's a document, it opens the document. Whatever the type of the file is that the target is pointing to, Windows will execute it as if you had double-clicked on the file. The filetype must have a program associated with it in order for it to launch correctly. Even though there is a field in the shortcut property dialog box for hot key, it is not tied to the shortcut at all. When you set the hotkey in a shortcut, it updates the systemwide table and that's it. BTW, if assigning the hotkey after the shortcut is in c:\home\wrk really doesn't work, I suspect that the Start Menu may. Yes, the start menu works. This was news for me, too. In quick start, it does not work, though. So, start menu and desktop work. Anything else? ;) Best regards, Spiro. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: [PATCH] New --pe-dll-characteristcs switch for PE ld.
Christopher Faylor wrote: I would like to see an objcopy option at some point. I don't agree with the prevailing cygwin opinion that you need a separate binary to deal with this. It seems silly to have objcopy able to do only some things to a PE and, if objcopy can do this, then I don't see why you need an extra program to manipulate this field. I agree that objcopy should be able to manipulate this (these) field(s). However, having a simple tool that does a simple thing is The Unix Way. Having a giant do-everything tool is...not. For that we have Perl. g [The following gets OT for binutils; I've CC:ed the cygwin list. If you wish to continue this subthread, please take it over there] Seriously, with regards to cygwin though, there are a few important reasons for the bit-twiddler program to be separate from objcopy, even if it duplicates some of its functionality. 1) we're going to recommend that -- until everything in the cygwin distro is rebuilt using a not-yet-available ld with new defaults -- users (including lusers and n00bs) -- run a bit-twiddler tool on many, if not all, of the DLLs and EXEs in their installation. It would be bad if this tool was developer-centric, with lots of confusing (to the uninitiated) options that have the potential to seriously foul up the target object(s) in unrecoverable ways, if used incorrectly. Like objcopy. The bit-twiddler proggie, being so simple and limited in scope, can always revert any changes it makes. Even when used by a n00b. 2) Do we really want all users -- who might not be developers -- who happen to run in to a particular problem be forced to download and install all of binutils, just for objcopy? 3) We're dealing with an issue where EXEs will not operate at all if they do not have the correct DllCharacteristics bits. Which exes suffer from this limitation is not immediately obvious, and we don't know what triggers the misbehavior (on WindowsTS, at least). So far we are lucky -- it appears that the binutils tools such as nm and objcopy are NOT affected by this issue, but we don't know why, nor if our luck will change in the future. In the end, we might be forced to distribute the bit-twiddler as a mingw app, not a cygwin one. I don't think we (cygwin) want to distribute a standalone version of i686-pc-mingw32-objcopy, nor as in #2 above, force all users (who happen to run in to ...) to download mingw-cross-binutils. 4) The behavior of a specific bit-twiddler program can be tweaked to better suit our intended purpose: to be called on a large list of files ONCE to perform similar operations on all of those files, thus avoiding lots of forks. This is important not just for speed, but also because the dynbase issue is the solution to a problem that fails specifically when you're doing a lot of forks. (Granted, you could avoid this latter issue by ensuring that the bit-twiddler program -- be it objdump or peflags -- itself is only shipped with the dynbase flag preset). But AFAIK objdump is not meant to operate in a SIMD manner -- that is, do the same operation on an entire list of target objects. Rather, objcopy takes exactly two file names: one input and one optional output. If the output file isn't specified, then the temporary modified version is renamed over the input (which is the behavior we'd want to exploit for a make-all-dynbase script -- or we'd do the rename manually IN that script, having given objcopy an explicit temporary name for its output). That's a lot of extra disk writes and data copying -- again, slow. peflags operates inplace. 5) Why does cygwin ship rebase? Technically objcopy could and should do this, too (even though that particular operation is a lot more complicated than just setting a value in the PE file's header). But #1 thru #4 above all also apply with regards to rebase.exe, even if objcopy had that capability. -- Chuck -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: [PATCH] New --pe-dll-characteristcs switch for PE ld.
[oops. I replied to a non-existent list, so binutils never saw this and cygwin will see it twice. Sorry about that] Christopher Faylor wrote: I would like to see an objcopy option at some point. I don't agree with the prevailing cygwin opinion that you need a separate binary to deal with this. It seems silly to have objcopy able to do only some things to a PE and, if objcopy can do this, then I don't see why you need an extra program to manipulate this field. I agree that objcopy should be able to manipulate this (these) field(s). However, having a simple tool that does a simple thing is The Unix Way. Having a giant do-everything tool is...not. For that we have Perl. g [The following gets OT for binutils; I've CC:ed the cygwin list. If you wish to continue this subthread, please take it over there] Seriously, with regards to cygwin though, there are a few important reasons for the bit-twiddler program to be separate from objcopy, even if it duplicates some of its functionality. 1) we're going to recommend that -- until everything in the cygwin distro is rebuilt using a not-yet-available ld with new defaults -- users (including lusers and n00bs) -- run a bit-twiddler tool on many, if not all, of the DLLs and EXEs in their installation. It would be bad if this tool was developer-centric, with lots of confusing (to the uninitiated) options that have the potential to seriously foul up the target object(s) in unrecoverable ways, if used incorrectly. Like objcopy. The bit-twiddler proggie, being so simple and limited in scope, can always revert any changes it makes. Even when used by a n00b. 2) Do we really want all users -- who might not be developers -- who happen to run in to a particular problem be forced to download and install all of binutils, just for objcopy? 3) We're dealing with an issue where EXEs will not operate at all if they do not have the correct DllCharacteristics bits. Which exes suffer from this limitation is not immediately obvious, and we don't know what triggers the misbehavior (on WindowsTS, at least). So far we are lucky -- it appears that the binutils tools such as nm and objcopy are NOT affected by this issue, but we don't know why, nor if our luck will change in the future. In the end, we might be forced to distribute the bit-twiddler as a mingw app, not a cygwin one. I don't think we (cygwin) want to distribute a standalone version of i686-pc-mingw32-objcopy, nor as in #2 above, force all users (who happen to run in to ...) to download mingw-cross-binutils. 4) The behavior of a specific bit-twiddler program can be tweaked to better suit our intended purpose: to be called on a large list of files ONCE to perform similar operations on all of those files, thus avoiding lots of forks. This is important not just for speed, but also because the dynbase issue is the solution to a problem that fails specifically when you're doing a lot of forks. (Granted, you could avoid this latter issue by ensuring that the bit-twiddler program -- be it objdump or peflags -- itself is only shipped with the dynbase flag preset). But AFAIK objdump is not meant to operate in a SIMD manner -- that is, do the same operation on an entire list of target objects. Rather, objcopy takes exactly two file names: one input and one optional output. If the output file isn't specified, then the temporary modified version is renamed over the input (which is the behavior we'd want to exploit for a make-all- dynbase script -- or we'd do the rename manually IN that script, having given objcopy an explicit temporary name for its output). That's a lot of extra disk writes and data copying -- again, slow. peflags operates inplace. 5) Why does cygwin ship rebase? Technically objcopy could and should do this, too (even though that particular operation is a lot more complicated than just setting a value in the PE file's header). But #1 thru #4 above all also apply with regards to rebase.exe, even if objcopy had that capability. -- Chuck -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: 1.5.25: Regtool can not find registry?
Josef Wolf wrote: Hello, I had a working cygwin installation for several years on this machine. But then I decided to remove and reinstall it. (I reinstalled cygwin only, not the whole machine). Since the reinstall, regtool refuses to work. It always complains that it can not find the specified file. Strange enough, cygcheck _is_ able to read information from the registry. Here are examples of what I get: $ regtool get '/HKLM/SOFTWARE/Cygnus Solutions/Cygwin Error (2): Das System kann die angegebene Datei nicht finden. $ regtool get '/HKLM/SOFTWARE/Cygnus Solutions/Cygwin/mounts v2' Error (2): Das System kann die angegebene Datei nicht finden. Any ideas how to track down this problem? Two thoughts: 1. Try running this under 'strace' to see if you can spot something. 2. Remove the values from your CYGWIN environment variable and reboot. Either of these two thoughts may lead nowhere but that's the best I can come up with. -- 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? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: How can I assign a hotkey to run a cygwin/bash script?
Hello Brian, * On Fri, Mar 06, 2009 at 01:29:02PM -0500 Brian Mathis wrote: On Fri, Mar 6, 2009 at 12:58 PM, Spiro Trikaliotis xxx...@spiro.trikaliotis.net wrote: Well, we can think about many things: However, this is not the way it works on Windows, obviously. Windows keeps a systemwide table of hotkeys, and when one is pressed Windows runs whatever is in the table as the target. Ok. If you know for sure, I stand corrected. However, from the behaviour, this is not the way it seemed to work to me. Can you explain then why a shortcut I define in the quick start does not get applied? Yes, I defined it directly there, I did not move a file there. Best regards, Spiro. -- Spiro R. Trikaliotis http://opencbm.sf.net/ http://www.trikaliotis.net/ http://www.viceteam.org/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: How can I assign a hotkey to run a cygwin/bash script?
http://directedge.us/content/winhotkey When I execute minty using winhotkey, I get bash: [: too many arguments This is BASH 3.2 - DISPLAY on tty1 Mar 5 07:27:0.0 Fri Mar 6 12:51:45 PST 2009 [Home$:500] This does not happen when I execute mintty directly (or via windows hot key, when that works). I am not supplying any arguments. They are all set to start in the same directory. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: How can I assign a hotkey to run a cygwin/bash script?
Arun Biyani wrote: http://directedge.us/content/winhotkey When I execute minty using winhotkey, I get bash: [: too many arguments This is BASH 3.2 - DISPLAY on tty1 Mar 5 07:27:0.0 Fri Mar 6 12:51:45 PST 2009 [Home$:500] This does not happen when I execute mintty directly (or via windows hot key, when that works). I am not supplying any arguments. They are all set to start in the same directory. Something's wrong in the path or environment, or in the command-line options. Add the -x flag to your invocation of bash and we'll see what's going wrong. cheers, DaveK -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: How can I assign a hotkey to run a cygwin/bash script?
Spiro Trikaliotis wrote on Friday, March 06, 2009 2:59 PM: * On Fri, Mar 06, 2009 at 01:29:02PM -0500 Brian Mathis wrote: On Fri, Mar 6, 2009 at 12:58 PM, Spiro Trikaliotis xxx...@spiro.trikaliotis.net wrote: Well, we can think about many things: However, this is not the way it works on Windows, obviously. Windows keeps a systemwide table of hotkeys, and when one is pressed Windows runs whatever is in the table as the target. Ok. If you know for sure, I stand corrected. However, from the behaviour, this is not the way it seemed to work to me. Can you explain then why a shortcut I define in the quick start does not get applied? Yes, I defined it directly there, I did not move a file there. New data: - On XP, without administrator privileges. - I copied a shortcut from the Start Menu to C:\usr. - I gave it a hotkey. - It did not work. - I deleted the copied shortcut. - I gave the original shortcut the same hotkey. - It worked. - I got rid of the hot key in the Start Menu. - I copied a shortcut from the Start Menu to C:\Documents and Settings\My_User_Name. - I gave it the same hotkey. - It did not work. So it seems as if Windows may not be paying attention setting of hotkeys is reproducible at least under some circumstances. - Barry Disclaimer: Statements made herein are not made on behalf of NIAID. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
ld library problems
I have some Linux code that uses ld and ld finds '.a' archive files when given a -L path. Cygwin's ld is not seeing these files and I have to specifically list them with -l. Anyone shine some light on this ? Do I have to use '.la' ? Or what ? Aaron -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: ld library problems
On Fri, Mar 06, 2009 at 10:09:51PM -, Aaron Gray wrote: I have some Linux code that uses ld and ld finds '.a' archive files when given a -L path. Cygwin's ld is not seeing these files and I have to specifically list them with -l. Anyone shine some light on this ? Do I have to use '.la' ? Or what ? We can't shed light on this without details. Please provide some specific examples. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: ld library problems
On Fri, Mar 06, 2009 at 10:09:51PM -, Aaron Gray wrote: I have some Linux code that uses ld and ld finds '.a' archive files when given a -L path. Cygwin's ld is not seeing these files and I have to specifically list them with -l. Anyone shine some light on this ? Do I have to use '.la' ? Or what ? We can't shed light on this without details. Please provide some specific examples. From what I am seeing (this is not a tested example) Given 'libTest2.a' in '/usr/build/Debug/lib' g++ -share -L/usr/build/Debug/lib test.o -o test.dll This fails to find test2.a on Cygwin where it is found on Linux. Where as the following works :- g++ -share -L/usr/build/Debug/lib test.o -o test.dll -ltest2.a Aaron -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: ld library problems
On Fri, Mar 06, 2009 at 10:41:53PM -, Aaron Gray wrote: On Fri, Mar 06, 2009 at 10:09:51PM -, Aaron Gray wrote: I have some Linux code that uses ld and ld finds '.a' archive files when given a -L path. Cygwin's ld is not seeing these files and I have to specifically list them with -l. Anyone shine some light on this ? Do I have to use '.la' ? Or what ? We can't shed light on this without details. Please provide some specific examples. From what I am seeing (this is not a tested example) Given 'libTest2.a' in '/usr/build/Debug/lib' g++ -share -L/usr/build/Debug/lib test.o -o test.dll This fails to find test2.a on Cygwin where it is found on Linux. I doubt that test2 would be found on any platform since you didn't specify it on the command line. However, we won't get far on untested examples. You need to provide specifics not supposition. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: ld library problems
On Fri, Mar 06, 2009 at 10:41:53PM -, Aaron Gray wrote: On Fri, Mar 06, 2009 at 10:09:51PM -, Aaron Gray wrote: I have some Linux code that uses ld and ld finds '.a' archive files when given a -L path. Cygwin's ld is not seeing these files and I have to specifically list them with -l. Anyone shine some light on this ? Do I have to use '.la' ? Or what ? We can't shed light on this without details. Please provide some specific examples. From what I am seeing (this is not a tested example) Given 'libTest2.a' in '/usr/build/Debug/lib' g++ -share -L/usr/build/Debug/lib test.o -o test.dll This fails to find test2.a on Cygwin where it is found on Linux. I doubt that test2 would be found on any platform since you didn't specify it on the command line. However, we won't get far on untested examples. You need to provide specifics not supposition. Its in a large project. So I will have to produce a bare test case. Will do so tomorrow as I would like to get to the bottom of this. Aaron -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Turning off execute permission
I've been reading: http://cygwin.com/1.7/cygwin-ug-net/ntsec.html#ntsec-files on the execute permissions. Did I read that it was impossible to deny execute permissions?? In my tests, the follow is always true if a file has no execute permissions: (mode 666 or 000) [ -x apachectl ] test -x apachectl for all of the shells Did I uncover a bug somewhere or is this a feature?? I guess my alternative would to use the read permission bit and just rename the file to effective disable it. If there is no real execute bit because of Windows ACLs, then that statement should be explicitly stated if its in order. If that is the reason you'll trying to say in section titled The POSIX permission mapping leak, can/should it be a little more explicit? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
[1.7] Updated: cygwin-1.7.0-42
Hi folks, I just uploaded a new Cygwin 1.7 test release, 1.7.0-42. Cygwin 1.7 is a major jump from Cygwin 1.5.x. The list with all changes related to Cygwin 1.5.25 is attached below. Just download http://cygwin.com/setup-1.7.exe and use that setup tool to install Cygwin 1.7. As usual, please report bugs and problems to the mailing list cygwin AT cygwin DOT com. We also have a new User's Guide for 1.7, which is currently located at http://cygwin.com/1.7/cygwin-ug-net/cygwin-ug-net.html We also now have new API documentation http://cygwin.com/1.7/cygwin-api/cygwin-api.html And we have a new FAQ, though very likely not quite complete since we still don't know what exactly *is* a FAQ realted to Cygwin 1.7. http://cygwin.com/1.7/faq/faq.html Bug fixes and extensions to the documentation in the form of patches to the source SGML files are much appreciated. The SGML sources are located in the CVS repository under the winsup/doc directory, for example here: http://cygwin.com/cgi-bin/cvsweb.cgi/src/winsup/doc/?cvsroot=src Same goes for Cygwin patches in general, of course. === THIS IS STILL A TEST RELEASE. DON'T USE IN PRODUCTION ENVIRONMENTS. Nevertheless I'd like to encourage everyone to give 1.7 a shot. Due to internal changes it is possible to install a 1.7 release in parallel to a 1.5 release and even run 1.7 processes in parallel to 1.5 processes. * The processes will not know about each other! Any try to interact * between 1.7-based and 1.5-based processes will lead to, at least, funny * results. To install a 1.7 release in parallel to a 1.5 release, all you have to do is to choose another root directory (for instance: C:\cygwin-1.7) in setup-1.7's Choose Installation Directory dialog. * NOTE: Due to the way setup-1.7 works, you have to change the directory * right the first time you visit this dialog! If you pressed the Next * button and then Back again, it's already too late and setup-1.7 will * create a broken 1.7 install. If you pressed Next by mistake, exit * setup-1.7 and start it again. === What's new in contrast to 1.7.0-41 === - New functions wprintf, fwprintf, swprintf, vwprintf, vfwprintf, vswprintf. - New setlocale implementation allows to specify POSIX locale strings. You can now use, for instance in bash, `export LC_ALL=en_US.UTF-8'. The language and territory will be ignored for now, the charset will be used by multibyte-releated functions. - wctomb/mbtowc can now handle surrogate pairs. - So far there was a hack in the 1.7.0 Cygwin DLL which disabled DEP (Data Execution Prevention) on a per-application base when running on a Windows Server 2008 Terminal Server. This was necessary to avoid spurious crashes of Cygwin applications due to a bug in a Windows DLL. This DLL (tsappcmp.dll) is only called on Terminal Servers for applications which don't have the TS-awareness flag set in the executable's file header. It turned out that we can simply avoid the crashes by switching on the TS-awareness bit in executables. In future this will be done automatically when building new applications. For older applications there will be a new tool called `peflags', curtesy Charles Wilson, which allows to set this flag (among others) on already existing executables. Therefore, and because the hack to switch off DEP in the DLL is a major performance killer, the hack has now been disabled in the DLL. Bugfixes: = - Fix select(2) on FIFOs. - A long standing problem in newlib's setlocale() function disallows to read the locale specific LC_* environment variables. - Fix mbtowc/wctomb so as not to handle invalid 5 and 6 byte UTF-8 sequences. Fix wctomb singlebyte behaviour in case the icoming wide char doesn't fit. - Fix cygdrive output in mount -m command. FAQ: - Q: How do I know that I'm running Cygwin 1.7.0-41? A: The `uname -v' command prints 2009-03-06 11:28 Have fun, Corinna Here's the list of user-visible changes in 1.7.0 related to 1.5.25: === OS releated changes: - Windows 95, 98 and Me are not supported anymore. The new DLL will not run on any of these systems. File Access related changes: - Mount points are no longer stored in the registry. Use /etc/fstab and /etc/fstab.d/$USER instead. Mount points created with mount(1) are only local to the current session and disappear when the last Cygwin process in the session exits. - PATH_MAX is now 4096. Internally, path names can be as long as the underlying OS can handle (32K). - UTF-8 filenames are supported now. So far, this requires to set the environment variable CYGWIN to contain codepage:utf8. but this will likely disappear at one point. The
