XP embedded
Hi all, While searching though the mail list archives, I found a posting back on March 9th asking about XP Embedded SP2 and the error "/dev/null: No such file or directory". Everyone blasted the poster for running a really old version of Cygwin. Well I'm running into the exact same problem, except that I'm running the latest version of Cygwin. When I start a console I get the message "bash: /dev/null: No such file or directory" I did a little playing around and if I try to pipe anything out /dev/null I get the error. just for kicks I tried creating /dev/null using mknod, but it failed saying that the file already exists I have the exact same installation on regular XP SP2 and this problem does not exist Let me know if you have any ideas on what the issue might be. Thanks! -Jeff -- 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: XP embedded
/dev/zero does work properly. I changed line 68 in /etc/profile to use /dev/zero instead of /dev/null and I no longer get the bash error on start up. Perhaps the cygwin libraries should be modified so that if the windows NUL device doesn't exist, it should use a different method. Thanks. -Jeff On 4/12/06, Corinna Vinschen <[EMAIL PROTECTED]> wrote: > On Apr 11 14:22, Jeff Lange wrote: > > Hi all, > > While searching though the mail list archives, I found a posting > > back on March 9th asking about XP Embedded SP2 and the error > > "/dev/null: No such file or directory". > > > > Everyone blasted the poster for running a really old version of Cygwin. > > > > Well I'm running into the exact same problem, except that I'm running > > the latest version of Cygwin. When I start a console I get the message > > "bash: /dev/null: No such file or directory" > > > > I did a little playing around and if I try to pipe anything out > > /dev/null I get the error. just for kicks I tried creating /dev/null > > using mknod, but it failed saying that the file already exists > > > > I have the exact same installation on regular XP SP2 and this problem > > does not exist > > > > Let me know if you have any ideas on what the issue might be. > > /dev/null in Cygwin is a direct connection to the NUL device of > Windows. It looks like this device simply doesn't exist on > embedded XP. However, further debugging would be required by > somebody actually owning embedded XP (e.g. you). > > As a workaround, try redirecting output to /dev/zero which is not > implemented using the Windows NUL device. > > > Corinna > > -- > Corinna Vinschen Please, send mails regarding Cygwin to > Cygwin Project Co-Leader cygwin AT cygwin DOT com > Red Hat > > -- > 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/ > > -- 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: making .bat to launch .exe and .sh
I use a bat file that looks like this: @echo off c: chdir c:\cygwin\bin bash --login -i -c /script.sh -Jeff On 4/18/06, gohans <[EMAIL PROTECTED]> wrote: > > hello, > > i was wondering if it was possible to make a .bat file that could launch > .exe and .sh files, on windows. > If you have any idea about that, i would really appreciate. > > -- > View this message in context: > http://www.nabble.com/making-.bat-to-launch-.exe-and-.sh-t1466778.html#a3964281 > Sent from the Cygwin Users forum at Nabble.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/ > > -- 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/
terminal escape codes
Hi, I have a program that will connect to another host via telnet and work like a terminal emulator. This works fine in Linux, but under cygwin, when the host sends out the vt220 command (B cygwin apparently doesn't know how to handle this escape code, and it ends up displaying the B on the screen, In Linux if I type "echo ^[(Btest" at a command prompt it comes back as "test", but if I do the exact same thing at a cygwin prompt it comes back as "Btest" Does anyone know a simple way around this? like modifying /etc/termcap? Thanks in advance. -Jeff -- 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: terminal escape codes
While that does work, It unfortunately isn't an acceptable solution for me. I really need to be running this from a plain text console. Any other ideas? Thanks. -Jeff On 5/5/06, Larry Hall (Cygwin) <[EMAIL PROTECTED]> wrote: Jeff Lange wrote: > Hi, > I have a program that will connect to another host via telnet and > work like a terminal emulator. This works fine in Linux, but under > cygwin, when the host sends out the vt220 command (B cygwin > apparently doesn't know how to handle this escape code, and it ends up > displaying the B on the screen, > > In Linux if I type "echo ^[(Btest" at a command prompt it comes back > as "test", but if I do the exact same thing at a cygwin prompt it > comes back as "Btest" > > Does anyone know a simple way around this? Run rxvt (or xterm if you're running X) instead? -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- 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/ -- 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: terminal escape codes
We attempted to use rxvt, but the issue is that the application that is running uses F key's that don't appear to map correctly when using rxvt, but do work when using the normal cygwin shell. The root of the question is though, why doesn't the standard shell handle the ESC(B code correctly? This is a bug is it not? -Jeff On 5/8/06, Andrew DeFaria <[EMAIL PROTECTED]> wrote: Igor Peshansky wrote: > On Fri, 5 May 2006, Andrew DeFaria wrote: >> Jeff Lange wrote: >>> While that does work, It unfortunately isn't an acceptable solution >>> for me. I really need to be running this from a plain text console. >> How is running rxvt not a plain text console?!? I use rxvt all the >> time. I don't like the "Windows window" as it's cut and paste >> semantics are horrible as well as it's resizing (in)ability. > Windows has a notion of a "console window". rxvt, xterm, ssh, and > pretty much any other Cygwin program that doesn't allocate an explicit > console window uses ptys to emulate console output. Some Windows > programs cannot understand ptys, and thus don't work properly via ssh, > or in rxvt. So the OP's need may be valid. I'm well aware of this and indeed this is about the only drawback I've ever seen with using rxvt instead of the console window. But there are not that many "Windows only, I need a console and I can't deal with pty's" applications that I run. Indeed many Windows users shy away from anything command line oriented. My question was more to affirm whether or not the OP was running into a pty problem or just didn't understand that he could use rxvt... -- If olive oil comes from olives, where does baby oil come from? -- 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/ -- 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/
High F-Keys
I've found an issue with the Sifted F-Keys in Cygwin, Shift-F1 (or
F13) is sending out the same escape sequence as F11, and the all the
rest of the High F-Keys have the same sort of issue.
I've created a patch that fixes this, as well as adds support for F23
and F24 (which weren't implemented before).
Can this get merged into the actual source tree?
Thanks
-Jeff Lange
--- cygwin-1.5.19-4/winsup/cygwin/fhandler_console.cc 2006-01-16
12:14:35.0 -0500
+++ cygwin-1.5.19-4-JKL/winsup/cygwin/fhandler_console.cc 2006-05-15
15:26:44.914514300 -0400
@@ -1694,18 +1694,18 @@
{VK_END, {"\033[4~", "\033[4~","\033[4~","\033\033[4~"}},
{VK_INSERT, {"\033[2~", "\033[2~","\033[2~","\033\033[2~"}},
{VK_DELETE, {"\033[3~", "\033[3~","\033[3~","\033\033[3~"}},
- {VK_F1, {"\033[[A", "\033[23~", NULL, NULL}},
- {VK_F2, {"\033[[B", "\033[24~", NULL, NULL}},
- {VK_F3, {"\033[[C", "\033[25~", NULL, NULL}},
- {VK_F4, {"\033[[D", "\033[26~", NULL, NULL}},
- {VK_F5, {"\033[[E", "\033[28~", NULL, NULL}},
- {VK_F6, {"\033[17~", "\033[29~", "\036", NULL}},
- {VK_F7, {"\033[18~", "\033[31~", NULL, NULL}},
- {VK_F8, {"\033[19~", "\033[32~", NULL, NULL}},
- {VK_F9, {"\033[20~", "\033[33~", NULL, NULL}},
- {VK_F10, {"\033[21~", "\033[34~", NULL, NULL}},
- {VK_F11, {"\033[23~", NULL, NULL, NULL}},
- {VK_F12, {"\033[24~", NULL, NULL, NULL}},
+ {VK_F1, {"\033[[A", "\033[25~", NULL, NULL}},
+ {VK_F2, {"\033[[B", "\033[26~", NULL, NULL}},
+ {VK_F3, {"\033[[C", "\033[28~", NULL, NULL}},
+ {VK_F4, {"\033[[D", "\033[29~", NULL, NULL}},
+ {VK_F5, {"\033[[E", "\033[31~", NULL, NULL}},
+ {VK_F6, {"\033[17~", "\033[32~", "\036", NULL}},
+ {VK_F7, {"\033[18~", "\033[33~", NULL, NULL}},
+ {VK_F8, {"\033[19~", "\033[34~", NULL, NULL}},
+ {VK_F9, {"\033[20~", "\033[35~", NULL, NULL}},
+ {VK_F10, {"\033[21~", "\033[36~", NULL, NULL}},
+ {VK_F11, {"\033[23~", "\033[37~", NULL, NULL}},
+ {VK_F12, {"\033[24~", "\033[38~", NULL, NULL}},
{VK_NUMPAD5, {"\033[G",NULL, NULL, NULL}},
{VK_CLEAR,{"\033[G",NULL, NULL, NULL}},
{'6', {NULL, NULL, "\036", NULL}},
--
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/
console question
I've come across an anomaly with the standard cygwin console regarding cursor advancement. If I have a console 80 chars wide, and echo the following text: ^[[H12345678901234567890123456789012345678901234567890123456789012345678901234567890^M I would expect to see the following output (as I do in Linux or rxvt): 901234567890123456789012345678901234567890123456789012345678901234567890 however, if the console is 80 chars wide, I instead see 12345678901234567890123456789012345678901234567890123456789012345678901234567890 The cursor is being advanced to the second line when the 80th character is written to the screen, this shouldn't be the default behavior. Can someone who is familiar with the source point me to the correct location so I can address this? Thanks! -Jeff -- 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: console question
well I've given up on that, now I'm hacking away at puttycyg to make it do what I need it to do, like send out the correct high F keys, and adding an argument to make it full screen on startup. =) Thanks, -Jeff On 5/16/06, Samuel Thibault <[EMAIL PROTECTED]> wrote: Hi, Jeff Lange, le Tue 16 May 2006 09:50:41 -0400, a écrit : > I've come across an anomaly with the standard cygwin console regarding > cursor advancement. What you call "standard cygwin console" is the _windows_ console. > If I have a console 80 chars wide, and echo the following text: > > ^[[H12345678901234567890123456789012345678901234567890123456789012345678901234567890^M > > I would expect to see the following output (as I do in Linux or rxvt): > 901234567890123456789012345678901234567890123456789012345678901234567890 That depends on the terminal type. Some do wrap at the right side, others don't, see the "am" capability in man 5 terminfo. In addition to that, some do wrap as soon as the 80th position is filled, see the "sam" capability. > The cursor is being advanced to the second line when the 80th > character is written to the screen, this shouldn't be the default > behavior. That's the way the windows console behaves. Not much can be changed here. Just run rxvt ;) Samuel -- 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/ -- 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: console question
Although it seems like a waste, I need it to look exactly like a dumb terminal, which by setting the screen size to 80x25, and telling it to resize the font on window resize works perfectly. -Jeff On 5/16/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: On Tue, May 16, 2006 at 11:03:01AM -0400, Jeff Lange wrote: > well I've given up on that, now I'm hacking away at puttycyg to make > it do what I need it to do, like send out the correct high F keys, and > adding an argument to make it full screen on startup. =) > > Thanks, > -Jeff Do you use a 640x480 screen? Full screen for a console sounds like a grand waste of field of vision. -- 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/ -- 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/
