Tag Info

New answers tagged


Assuming that the missing space /sbin/agetty/dev/ttyS2 is not real, otherwise you have serious issues. It's likely that you haven't asked agetty to monitor Data Carrier Detect. When asserted DCD means that there is a session in progress. DCD in turn requires DTR to be present, as Data Terminal Ready when asserted means that the other RS-232 lines from the ...


look at: man 1 script for example: script -f /dev/tty1


I'm actually trying to solve this very same problem. I worked it out by reading through this thread email exchange that took place some time ago. visit here. I still need to try this out . I'll report back if I get it to work. Edit: I was able to create the PSF font but have not tried to use it as a TTY font. I believe that was the implication of the ...


I had the same issue but for me, I had not provided the correct port for the memory card. I had to edit the script.fex and generate another script.bin and the system booted successful. Different boards have different ports. My board was an ITEAD AW2041, and it previous hanged at the same point awaiting on the mmcblk0p2


Your shell, or whatever process was in the foreground, was already reading the terminal to which is was attached, which was /dev/ttys011. Then you started another process, a cat also reading the same terminal at the same time. Now there are two processes competing for the same input from the terminal. Each time you type a key in the terminal, it is ...


On UNIX, a tty (like many other things) appears as a file. Data written to the tty device goes to the terminal and data coming from the terminal is available for reading on the tty. If the tty is a hardware serial port, then data written to it gets sent on the wire and data coming from the wire appears on the tty. If the tty is a machine's video console ...


So, as @muru points out in the comments, there doesn't seem to be a simple way to interface the pty created for you with just the shell. I managed all of it but the unlockpt() part. According to something I read here it may be there are some compile-time options in the kernel for disabling newly created pty locking, but I didn't want to do that. So, I did ...


If X is the usr who wants to pop a message on y machine. Fisrt take the terminal id of y machine and both should be on the same host. you can send a message like below. Type who command and see the terminal id of y machine( for example pty/1 is the terminal ID of y) echo "Hello" 1> pty/1(this will display the message on y machine.

Top 50 recent answers are included