search for: eol2

...^Z, it doesnt work. Please let me know if there are any settings to control it. telnet works fine. my settings, version: OpenSSH_6.6p1, OpenSSL 1.0.1h 5 Jun 2014 stty -a speed 38400 baud; rows 24; columns 80; line = 0; intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>; eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0; -parenb -parodd cs8 -hupcl -cstopb cread -clocal -crtscts -ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon -ixoff -iuclc -ixany -imaxb...

...ntation onto the wire and back again. So OpenSSH interoperates with itself between homogeneous platforms, but not with conforming implementations; for instance, from another client to OpenSSH on Linux (where _POSIX_VDISABLE appears to be '\0'): client$ stty -a [...] eol = <undef>; eol2 = <undef>; [...] server$ stty -a [...] eol = M-^?; eol2 = M-^?; [...] The attached patch against 4.0p1 fixes this for systems where _POSIX_VDISABLE is defined. Compiled and tested on Linux. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are wat...

...name -a Linux ubuntu 3.8.0-19-generic #29-Ubuntu SMP Wed Apr 17 18:16:28 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux $ sudo stty -F /dev/ttyS0 raw 4800 $ sudo stty -F /dev/ttyS0 -a speed 4800 baud; rows 0; columns 0; line = 0; intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>; eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0; -parenb -parodd cs8 hupcl -cstopb cread clocal -crtscts -ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr -icrnl -ixon -ixoff -iuclc -ixany -imaxb...

I setup a ssh chroot jail following this[1] guide. It works for my user to login, use ls and use scp which is all I really want. I do have a problem I cannot solve: when connected and navigating the filesystem, the backspace key actually moves the cursor forward and does not delete what I type. I may have found a hint from some googling that readline will read in /etc/inputrc on login but if

...Red Hat Enterprise). Some of the other characteristics of the serial port are changing too. After I try to start upsdrvctl, it looks like this: [root@]# stty -F /dev/ttyS0 -a speed 9600 baud; rows 0; columns 0; line = 0; intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>; eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0; parenb parodd cs7 hupcl -cstopb cread -clocal -crtscts -ignbrk -brkint -ignpar -parmrk inpck istrip -inlcr -igncr icrnl ixon ixoff -iuclc -ixany -imaxbel -...

...cr -igncr ixon -ixoff ixany imaxbel -ignbrk brkint -inpck -ignpar -parmrk oflags: opost onlcr -ocrnl tab0 -onocr -onlret cflags: cread cs8 -parenb -parodd hupcl clocal -cstopb -crtscts -dsrflow -dtrflow -mdmbuf cchars: discard = ^O; dsusp = ^Y; eof = ^D; eol = <undef>; eol2 = <undef>; erase = ^?; erase2 = ^H; intr = ^C; kill = ^U; lnext = ^V; min = 1; quit = ^\; reprint = ^R; start = ^Q; status = ^T; stop = ^S; susp = ^Z; time = 0; werase = ^W; Thanks, -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since 2.2.8 [not Pro-Audio.... YET!!] &...

When running R from the terminal on Linux (Ubuntu 16.04), it core dumps whenever / wherever I press Ctrl-4 or Ctrl-\. You get thrown back to the terminal with "Quit (core dump)" being the only message. Grepping the R source code, it doesn't look like that message is generated by R itself. Over on Twitter, it has been confirmed to also happen on macOS. $ R -d valgrind --vanilla

I have the following gnome terminal profile settings: Backspace = ASCII DEL Delete Key = Escape Sequence If the logged in session in the terminal window is my own user id then the delete key does nothing. If however, I su -l in the same terminal window then the delete key removes the character under the cursor and left shifts the rest of the line. I am fairly confident that the delete

...erence to be that the telnet session thought of itself as being on a 9600 baud terminal, while the SSH session thought of itself as 38400 baud. $ stty -a speed 38400 baud; rows = 34; columns = 80; ypixels = 0; xpixels = 0; intr = ^c; quit = ^|; erase = ^h; kill = ^u; eof = ^d; eol = <undef>; eol2 = <undef>; swtch = <undef>; start = ^q; stop = ^s; susp = ^z; dsusp = <undef>; rprnt = ^r; flush = ^o; werase = ^w; lnext = ^v; -parenb -parodd cs8 -cstopb hupcl cread -clocal -loblk -parext -ignbrk brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl -iuclc ixon -ixany -ixof...

Hey, I''ve installed Xen 3.0 on a freshly installed Debian Sarge. dom0 is working nicely (kernel 2.6.12.6-xen0). Then I created a domU, again with Debian Sarge, booting Xen''s vmlinuz-2.6.12-xenU. Unfortunately ctrl-c does not work in the domU''s console, neither if I create the domU with "xm create -c ..." nor if I attach to it later. It doesn''t matter

Hello everyone, recently I've found something I consider a bug. Correct me if I'm wrong, but I always thought that Linux' EOL is 0x0A. Imagine my surprise when I saw that all messages that are being output on to the stderr (on any Linux I've tested - Fedora and Ubuntu) are terminated with 0x0D, 0x0A. Maybe that's standard behaviour of all stderr messages in all Linux

...a calling 'kill -s QUIT <pid>'. One can disable the QUIT signal send by the terminal by: $ stty quit '' such that one gets: $ stty --all speed 38400 baud; rows 33; columns 80; line = 0; intr = ^C; quit = <undef>; erase = ^?; kill = ^U; eof = ^D; eol = <undef>; eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V; discard = ^O; min = 1; time = 0; -parenb -parodd -cmspar cs8 -hupcl -cstopb cread -clocal -crtscts -ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon -ixoff -iuclc -ix...

...230331 vmin_ -1, vtime_ 0 0.240345 COM1: device reports different attributes than what were set 0.240345 tcsetattr(): gfmt1:cflag=8bb:iflag=84:lflag=2:oflag=0: 0.240345 discard=0: 0.250360 eof=0: 0.250360 eol=2a: 0.250360 eol2=0: 0.250360 erase=0: 0.250360 intr=0: 0.250360 kill=0: 0.250360 lnext=0: 0.260374 min=1: 0.260374 quit=0: 0.260374 reprint=0: 0.260374 start=11: 0.260374 stop=13:...

Turns out another user reported the same issue with a slightly different model: https://github.com/networkupstools/nut/issues/231 <https://github.com/networkupstools/nut/issues/231> The "stty -f /dev/cuaU0 raw" trick should help, but I am confused as to why FreeBSD has different "raw" settings than what is set up at the same time as the baud rate:

...> telnet works fine. >> >> my settings, version: >> >> OpenSSH_6.6p1, OpenSSL 1.0.1h 5 Jun 2014 >> >> stty -a >> speed 38400 baud; rows 24; columns 80; line = 0; >> intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol =<undef>; >> eol2 =<undef>; swtch =<undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = >> ^R; >> werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0; >> -parenb -parodd cs8 -hupcl -cstopb cread -clocal -crtscts >> -ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrn...

Im trying to run this program called Thinkboxx and wen it tryes to comunicate over the comm port it hangs. Here are som output to read. earlier on i get: Call kernel32.VirtualAlloc(43050000,00001000,00001000,00000004) ret=0058557c Ret kernel32.VirtualAlloc() retval=43050000 ret=0058557c thats from vhere the com port gets an virtual memory space, i think. and in the end i have: Call