Joe Whitlock writes:
> I've looked through the MPE/iX Shell and Utilities Reference Manual,
> and have found some device files such as /dev/tty do not seem to
> be implemented.
I couldn't find it either, so I opened an HPRC call. You're supposed to be
able to go into the POSIX shell and say:
mknod /dev/tty c 2 0
But this creates something that doesn't work. As a workaround, from the CI,
do this:
MKNOD.HPBIN.SYS "/dev/tty c 2 0"
A patch will be available eventually. Selected text from the HPRC call:
-> It looks like you ran into a "bug" on this one. SR# 4701273383 was
-> supposed to be fixed in a patch that was never released or incorporated
-> into 5.0 or 5.5. The workaround is to use MKNOD.PUB.SYS to build the
-> /dev/tty device file, which correctly creates a file type of 16
-> (tty_device_link) rather than 15 (device_link). So, logon as
-> MANAGER.SYS, rm /dev/tty from the POSIX shell and back at MPE prompt:
->
-> MKNOD "/dev/tty c 2 0"
->
-> Now, you should be able to redirect I/O to and from /dev/tty correctly.
-> I will most likely have to request a patch for 5.0 and 5.5 on this
-> issue, which means submitting a new SR for this. I'll let you know.
->
-> .....
->
-> PX2JXJ3 patch has been requested for 5.0 and 5.5, but this is a low
-> priority problem, and there is a workaround. From what I understand, it
-> should be an "easy fix", so even though it's low priority they may come
-> up with a patch quickly. I'll let you know.
->
-> Also, it should be "fixing" only the tty issue, and not others, but not
-> positive at this point.
> How does POSIX stdin stdout stderr null map to CI $STDIN $STDLIST
> $NULL etc...
It generally works the way you would expect, except for some caveats that I've
previously mentioned on this list.
--
Mark Bixby E-mail: [log in to unmask]
Coast Community College Dist. Web: http://www.cccd.edu/~markb/
District Information Services 1370 Adams Ave, Costa Mesa, CA, USA 92626-5429
Technical Support +1 714 438-4647
"You can tune a file system, but you can't tune a fish." - tunefs(1M)
|