CVSROOT:/cvs/src
Module name:src
Changes by: [EMAIL PROTECTED] 2007-09-26 08:57:35
Modified files:
winsup/cygwin : ChangeLog termios.cc
Log message:
* termios.cc (setspeed): Support new baud rates introduced 2007-02-05.
Patches:
On Sep 25 18:33, Andrew M. Bishop wrote:
In the snapshot versions from mid-February there is indeed support for
other non-standard speeds (like 100, 200, 300) in the
tcsetattr() and tcgetattr() functions in fhandler_serial.cc. There
isn't however the corresponding change to the
Brian Dessent wrote:
$ cd $ttt
bash: cd: /cygdrive/c/Program: No such file or directory
Yes, that's wrong. [...] It's got nothing to do with
cygpath and everything to do with proper portable scripting practice.
Quite true. When you're using bash or sh, you must *quote
your arguments* if
I modified Cygwin.bat to the following,
bash --login -i -c 'cd /cygdrive/c exec bash'
and it still exits.
--
View this message in context:
http://www.nabble.com/Bash--c-without-exiting-tf4518164.html#a12901775
Sent from the Cygwin Users mailing list archive at Nabble.com.
--
Unsubscribe
I have successfully built/linked MATLAB mex files on Windows using GCC in
Cygwin. Unfortunately, it has a runtime error. It appears the error is due to
mismatched calling coventions for parameter passing. The MATLAB interpreter
successfully invokes the mexFunction() in my shared library
On Wed, 26 Sep 2007, Boyd Edmondson wrote:
I have successfully built/linked MATLAB mex files on Windows using GCC
in Cygwin. Unfortunately, it has a runtime error. It appears the error
is due to mismatched calling coventions for parameter passing. The
MATLAB interpreter successfully
Done. Thanks.
Boyd
-Original Message-
From: Igor Peshansky [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 26, 2007 7:24 AM
To: Boyd Edmondson
Cc: cygwin@cygwin.com
Subject: Re: MATLAB mexFunction() with Cygwin GCC Windows
On Wed, 26 Sep 2007, Boyd Edmondson wrote:
I have
Frank wrote:
I try to send the three cygcheck outputs unzipped with this mail.
OnAMD64 sshd is running as sshd_server
SMITHFIELD sshd is running as SYSTEM
on both machines I use public key authentication.
And for my application I shall stick to public key authentication.
Does
No, I don't see allot that clarifies things for me here, but thanks for
sending it. :-)
No problem - you arw elcome. - I might have been helpful...
I do see that FI-WIN and AMD64 don't have '/bin/sh' but
I don't think that's significant in your case (though you should reinstall
the 'bash'
On Sep 26 18:32, Frank wrote:
BTW, I am assuming that you're using 'whoami' from Windows on both of these
machines. If not, then we know why you see the difference reported by
these machines. ;-)
on FI-WIN: which whoami = /usr/bin/whoami
on AMD64: ssh amd64 which
Thanks,
Jerome
Williams, Gerald S (Jerry) wrote:
Brian Dessent wrote:
$ cd $ttt
bash: cd: /cygdrive/c/Program: No such file or directory
Yes, that's wrong. [...] It's got nothing to do with
cygpath and everything to do with proper portable scripting practice.
Quite true. When you're using
patrickinminneapolis wrote:
I modified Cygwin.bat to the following,
bash --login -i -c 'cd /cygdrive/c exec bash'
and it still exits.
I think you can get the effect you want by changing your home directory
in /etc/passwd to /cygdrive/c
--
Unsubscribe info:
I'm adapting to all the changes since B20. I have adopted the following
changes in the way I do things:
1) make sure my backups are *really* working before any upgrades
2) institute protected programs; by linking items in /bin to /localbin
3) now that I better understand setup, go with
Frank wrote:
I do see that FI-WIN and AMD64 don't have '/bin/sh' but
I don't think that's significant in your case (though you should
reinstall
the 'bash' package to fix this).
There is a sh. See:
$ ll /bin/sh
lrwxrwxrwx 1 illenseer None 8 Nov 10 2006 /bin/sh - bash.exe
Ah. Well that is
Why does ssh work but not sftp? What is wrong with my configuration?
sftp works OK in the other direction, from sony06 to dell03.
[EMAIL PROTECTED] ~/cygarc
$ sftp sony06
Connecting to sony06...
Received message too long 1920298606
[EMAIL PROTECTED] ~/cygarc
$ ssh sony06
Last login: Wed Sep
On Wed, 26 Sep 2007, Charles D. Russell wrote:
Why does ssh work but not sftp? What is wrong with my configuration?
sftp works OK in the other direction, from sony06 to dell03.
[EMAIL PROTECTED] ~/cygarc
$ sftp sony06
Connecting to sony06...
Received message too long 1920298606
[EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Larry Hall (Cygwin) on 9/26/2007 4:05 PM:
$ ll /bin/sh
lrwxrwxrwx 1 illenseer None 8 Nov 10 2006 /bin/sh - bash.exe
Ah. Well that is wrong. '/bin/sh' should be a copy of '/bin/bash'.
I'd still recommend reinstalling the bash
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
A new release of bash, 3.2.25-17, has been uploaded for experimental use
(3.2.25-16 remains current for now).
NEWS:
=
This is a minor patch release. It fixes a bug in (times file) | cat,
introduced in -11. It incorporates a patch that retries
Eric Blake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Larry Hall (Cygwin) on 9/26/2007 4:05 PM:
$ ll /bin/sh
lrwxrwxrwx 1 illenseer None 8 Nov 10 2006 /bin/sh - bash.exe
Ah. Well that is wrong. '/bin/sh' should be a copy of '/bin/bash'.
I'd still recommend
Igor Peshansky wrote:
On Wed, 26 Sep 2007, Charles D. Russell wrote:
Why does ssh work but not sftp? What is wrong with my configuration?
sftp works OK in the other direction, from sony06 to dell03.
[EMAIL PROTECTED] ~/cygarc
$ sftp sony06
Connecting to sony06...
Received message too long
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
A new release of bash, 3.2.25-17, has been uploaded for experimental use
(3.2.25-16 remains current for now).
NEWS:
=
This is a minor patch release. It fixes a bug in (times file) | cat,
introduced in -11. It incorporates a patch that retries
21 matches
Mail list logo
