I’ve solved my problems, so I post here the correct code in case someone needs similar stuff. Open Port int USB = open( “/dev/ttyUSB0”, O_RDWR| O_NOCTTY ); Set parameters struct termios tty; struct termios tty_old; memset (&tty, 0, sizeof tty); /* Error Handling */ if ( tcgetattr ( USB, &tty ) != 0 ) { … Read more
http://lists.berlios.de/pipermail/gpsd-dev/2005-April/001288.html : The idea is to supplement software in sharing a line between incoming and outgoing calls. The callin device (typically /dev/tty*) is used for incoming traffic. Any process trying to open it blocks within the open() call as long as DCD is not asserted by hardware (i.e. as long as the modem doesn’t have … Read more
As suggested by the error message you obtain, you should try to use winpty (which is installed by default with Git-Bash) and thus run: winpty docker run –rm -v “/c/users/vipul rao/documents/github/wappalyzer:/opt/wappalyzer” -it wappalyzer/dev If this works, you may want to set a Bash alias to avoid manually prepending winpty all the time: echo “alias docker=”winpty … Read more
How can it be that writing to physical disk is WAY faster than writing to the “screen” (presumably an all-RAM op), and is effectively as fast as simply dumping to the garbage with /dev/null? Congratulations, you have just discovered the importance of I/O buffering. 🙂 The disk appears to be faster, because it is highly … Read more
tty originally meant “teletype” and “pty” means “pseudo-teletype”. In UNIX, /dev/tty* is any device that acts like a “teletype”, i.e: a terminal. (Called teletype because that’s what we had for terminals in those benighted days.) A pty is a pseudotty, a device entry that acts like a terminal to the process reading and writing there, … Read more
The -t option goes to how Unix/Linux handles terminal access. In the past, a terminal was a hardline connection, later a modem based connection. These had physical device drivers (they were real pieces of equipment). Once generalized networks came into use, a pseudo-terminal driver was developed. This is because it creates a separation between understanding … Read more
Granting the user to use that command without prompting for password should resolve the problem. First open a shell console and type: sudo visudo Then edit that file to add to the very end: username ALL = NOPASSWD: /fullpath/to/command, /fullpath/to/othercommand eg john ALL = NOPASSWD: /sbin/poweroff, /sbin/start, /sbin/stop will allow user john to sudo poweroff, … Read more
With docker 1.3, there is a new command docker exec. This allows you to enter a running container: docker exec -it [container-id] bash Note: this assumes bash is installed on your container. You may run sh or whatever interactive shell is installed on the container.