rbp@investor.pgh.pa.us (Bob Peirce #305) (11/14/89)
I have been playing with shl as a way to simulate a windowing environment. It works pretty well except for a few things which either it can't do or I don't know how to make it do. I hope somebody can help. 1. Write doesn't work to a shl layer. We have a number of programs to write to users and I would like to have them work when a user is in a shl layer. Part of the problem is the who command shows sxt### instead of tty##, but even a "write user tty##" fails. 2. Is there any way to start a shl session automatically? I want to put together something so users can type a command and have the system create all the necessary layers. I have already discovered that shl sets PS1 and I can use that in my .cshrc file to initialize pre-defined layers once they are created, but I want to symplify the task for novice users. 3. We use Wyse 60s. If you are in 43-line, 132-column mode and try to switch layers, the terminal stays set. Is there any way to have a local term setting and to activate it when you select that layer? 4. Is there any documentation on shl that you can point me to? -- Bob Peirce, Pittsburgh, PA 412-471-5320 ...!uunet!pitt!investor!rbp rbp@investor.pgh.pa.us
paul@dy4.uucp (Paul Burry) (11/22/89)
In article <1989Nov14.145043.5428@investor.pgh.pa.us> rbp@investor.pgh.pa.us (Bob Peirce #305) writes: > >1. Write doesn't work to a shl layer. We have a number of programs >to write to users and I would like to have them work when a user is in a >shl layer. Part of the problem is the who command shows sxt### instead >of tty##, but even a "write user tty##" fails. > >-- >Bob Peirce, Pittsburgh, PA 412-471-5320 >...!uunet!pitt!investor!rbp rbp@investor.pgh.pa.us I once worked around this bug in "write" by linking the special files in /dev/sxt/ to special files in /dev/. It seems that "write" didn't realize that the sxt??? devices recorded in /etc/utmp really refer to the special files /dev/sxt/???. ie. --------------------------- cut here ------------------------- : cd /dev/sxt for node in * do ln $node /dev/sxt$node done --------------------------- cut here ------------------------- Hope this helps, =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Paul Burry PHONE: (613)-596-9911 UUCP: ...!cognos!dy4!paul POST: Dy4 Systems Inc., 21 Fitzgerald Road, or ...!cognos!dy4!seu13!paul Nepean, Ontario, Canada K2H 9J4 -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Paul Burry PHONE: (613)-596-9911 UUCP: ...!cognos!dy4!paul POST: Dy4 Systems Inc., 21 Fitzgerald Road, or ...!cognos!dy4!seu13!paul Nepean, Ontario, Canada K2H 9J4
ckl@uwbln.UUCP (Christoph Kuenkel) (11/28/89)
In article <148@dy4.UUCP>, paul@dy4.uucp (Paul Burry) writes: > In article <1989Nov14.145043.5428@investor.pgh.pa.us> rbp@investor.pgh.pa.us (Bob Peirce #305) writes: > > > > >1. Write doesn't work to a shl layer. We have a number of programs > >[...] > I once worked around this bug in "write" by linking the special files > in /dev/sxt/ to special files in /dev/. It seems that "write" > didn't realize that the sxt??? devices recorded in /etc/utmp really > refer to the special files /dev/sxt/???. Not only write(1). ttyname(3) fails on most systems, when the link into /dev/sxt* is not done. the bug is to move the sxt devices into a subdirectory cause this breaks fundamental assumptions in many unix tools. -- # include <std/disclaimer.h> Christoph Kuenkel/UniWare GmbH Kantstr. 152, 1000 Berlin 12, West Germany ck@tub.BITNET ckl@uwbln {unido,tmpmbx,tub}!uwbln!ckl