Project Home
Project Home
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - /dev/tty woes: (3 Items)
   
/dev/tty woes  
I'm having a problem with a program that I ported to QNX. The program attempts to open /dev/tty, and on the eight 
systems I've tested (2x 4.24 and 6x 4.25), in works on seven and fails on one. None of these systems actually have /dev/
tty listed in the filesystem, mind you. Additionally, the system that fails to open /dev/tty has the exact same version 
of all the modules/daemons that another system that can open /dev/tty, as shown below:

# sin ver
PROGRAM				NAME		VERSION	DATE
/boot/sys/Proc32		Proc			4.25O	Aug 19 2002
/boot/sys/Proc32		Slib16		4.23G	Oct 04 1996
/boot/sys/Slib32			Slib32		4.24B	Aug 12 1997
/bin/Fsys				Fsys32		4.24Y	Apr 23 2002
/bin/Fsys.atapi			atapi			4.25G	Aug 08 2007
//2/bin/Dev32			Dev32		4.23G	Oct 04 1996
//2/bin/Pipe			Pipe			4.23A	Feb 26 1996
//2/bin/Dev32.ser		Dev.ser		4.25A	Feb 14 2003
//2/bin/Dev32.ansi		Dev32.ansi		4.23H	Nov 21 1996
//2/bin/Dev32.par		Dev32.par		4.25A	Jan 08 2001
//2/bin/Dev32.pty		Dev32.pty		4.23G	Oct 04 1996
//2/bin/Net				Net			4.25E	Apr 24 2002
//2/bin/Net.befe124		Net.befe124	4.25C	Nov 27 2004
//2/*/5.0/usr/ucb/Tcpip	Tcpip			5.00A	Jan 26 2001
//2/bin/cron			cron			4.23B	Oct 30 1997

I've created a quick-and-dirty test for this issue, the code for which is attached to this post.

On seven of my systems, I get the following results:
# ./open_test /dev/monkeys
Opening '/dev/monkeys'
Failed: No such file or directory
# ./open_test /dev/null
Opening '/dev/null'
Passed.
# ./open_test /dev/tty
Opening '/dev/tty'
Passed.

On one of my systems, I get the following results:
# ./open_test /dev/monkeys
Opening '/dev/monkeys'
Failed: No such file or directory
# ./open_test /dev/null
Opening '/dev/null'
Passed.
# ./open_test /dev/tty
Opening '/dev/monkeys'
Failed: No such file or directory

Any suggestions on how to correct my one machine so that opening /dev/tty is possible would be greatly appreciated.
Attachment: Text open_test.c 324 bytes
Re: /dev/tty woes  
Hi Mak,

How do you launch the ./open_test? Please provide me a complete instructions: boot, log in, etc... Also note that there 
is no controlling terminal until tinit started.

> # ./open_test /dev/tty
> Opening '/dev/monkeys'
> Failed: No such file or directory

Are you sure?

Respectfully,
Oleg

> I'm having a problem with a program that I ported to QNX. The program attempts
>  to open /dev/tty, and on the eight systems I've tested (2x 4.24 and 6x 4.25),
>  in works on seven and fails on one. None of these systems actually have /dev/
> tty listed in the filesystem, mind you. Additionally, the system that fails to
>  open /dev/tty has the exact same version of all the modules/daemons that 
> another system that can open /dev/tty, as shown below:
> 
> # sin ver
> PROGRAM				NAME		VERSION	DATE
> /boot/sys/Proc32		Proc			4.25O	Aug 19 2002
> /boot/sys/Proc32		Slib16		4.23G	Oct 04 1996
> /boot/sys/Slib32			Slib32		4.24B	Aug 12 1997
> /bin/Fsys				Fsys32		4.24Y	Apr 23 2002
> /bin/Fsys.atapi			atapi			4.25G	Aug 08 2007
> //2/bin/Dev32			Dev32		4.23G	Oct 04 1996
> //2/bin/Pipe			Pipe			4.23A	Feb 26 1996
> //2/bin/Dev32.ser		Dev.ser		4.25A	Feb 14 2003
> //2/bin/Dev32.ansi		Dev32.ansi		4.23H	Nov 21 1996
> //2/bin/Dev32.par		Dev32.par		4.25A	Jan 08 2001
> //2/bin/Dev32.pty		Dev32.pty		4.23G	Oct 04 1996
> //2/bin/Net				Net			4.25E	Apr 24 2002
> //2/bin/Net.befe124		Net.befe124	4.25C	Nov 27 2004
> //2/*/5.0/usr/ucb/Tcpip	Tcpip			5.00A	Jan 26 2001
> //2/bin/cron			cron			4.23B	Oct 30 1997
> 
> I've created a quick-and-dirty test for this issue, the code for which is 
> attached to this post.
> 
> On seven of my systems, I get the following results:
> # ./open_test /dev/monkeys
> Opening '/dev/monkeys'
> Failed: No such file or directory
> # ./open_test /dev/null
> Opening '/dev/null'
> Passed.
> # ./open_test /dev/tty
> Opening '/dev/tty'
> Passed.
> 
> On one of my systems, I get the following results:
> # ./open_test /dev/monkeys
> Opening '/dev/monkeys'
> Failed: No such file or directory
> # ./open_test /dev/null
> Opening '/dev/null'
> Passed.
> # ./open_test /dev/tty
> Opening '/dev/monkeys'
> Failed: No such file or directory
> 
> Any suggestions on how to correct my one machine so that opening /dev/tty is 
> possible would be greatly appreciated.


Re: /dev/tty woes  
>> # ./open_test /dev/tty
>> Opening '/dev/monkeys'
>> Failed: No such file or directory
>
> Are you sure?

Sorry, that was a case of copy-and-paste gone wrong. It actually said: "Opening '/dev/tty'".

> How do you launch the ./open_test? Please provide me a complete instructions: 
> boot, log in, etc... Also note that there is no controlling terminal until 
> tinit started.

I've managed to figure out what is causing the problem. It turns out that the SSH daemon that logs me into this specific
 machine doesn't assign a terminal to the login. So while open_test works while logged in from telnet, it fails from SSH
.

Thank you for your help.