woods@robohack.UUCP (Greg A. Woods) (05/02/90)
In article <940@s8.Morgan.COM> amull@Morgan.COM (Andrew P. Mullhaupt) writes: > I'm beginning to use Layers with SCO UNIX System V/386 r3.2; > since I can't seem to get the terminal to do multiscreens. (It's > a PC emulating any one of about five terminals, I thought the > best chance for multiscreens was a Wyse50, but no go...) [ a wyse-50 isn't much good for anything, unless you are replacing a DEC vt52, and don't need any more functionality ] > The Layers work OK, but I have experienced a Double PANIC twice Are you talking about layers, or shell layers (i.e. shl)? There's a big difference, and I'd be surprised to find out SCO had layers. I'd be even more surprised if you found a Wyse terminal which understood layers! Yes shl and the sxt drivers (i.e. shell layers) are known to be buggy in several implementations. I cannot comment on SCO Unix, though I've had problems in other 386 implementations of SysVr3.2. SCO Xenix had several problems with the sxt drivers interacting badly with other tty drivers. -- Greg A. Woods woods@{robohack,gate,eci386,tmsoft,ontmoh}.UUCP +1 416 443-1734 [h] +1 416 595-5425 [w] VE3-TCP Toronto, Ontario; CANADA
guy@auspex.auspex.com (Guy Harris) (05/03/90)
>BTW, while running 'strings' on ksh to find the version number, I >noticed that the pathnames of many standard utilities are hard-coded into >the binary. Why would ksh would want to call cc, make, sed, grep, who, >pr, mail or ls? Because you typed "cc", "make", etc. to it.... >Any why would it care about date, mv, rm, or chmod >when these are just wrappers around system calls? Many modern UNIX shells have mechanisms to avoid doing a full search of PATH every time you run a command. The S5 Bourne shell, the C shell, and the Korn shell all seem to have their own different ones; "ksh" uses aliases. It supports "tracked aliases"; this means that the first time you run a command, it does a path search, and then aliases that command's name to the full path of the copy it found, so that subsequent executions go straight to the right path. As I remember, the Korn shell also includes some pre-defined aliases of that sort, and those are the strings you found.