jbm@uncle.UUCP (11/25/87)
Ok, enough. I've heard too many problems about feeding /dev/window to
getty. Sure, sure everyone want an extra window to fall back on. I am assuming
that everyone out there has windy from THE STORE! by now. I use ksh as my
shell, and this is how I have it set up:
At the end of ~/.profile:
--
ENV=$HOME/.env; export ENV
SHELL=/bin/ksh; export SHELL
NAME=`tty`
if [ "`expr $NAME : '/dev/w' `" != "0" ]
then
windy -n "Login shell" -l "Login shell"
windy -b -n "Extra shell" -l "Extra shell" $SHELL
fi
--
The first windy line just names the current window. The second one spins up
a new shell in thet background. You can add as many of the -b windy lines as
you like, within reason. What you see here is for NO ua, just shells. To use
this idea with ua, delete the first windy line, then put "exec /usr/bin/ua"
AFTER THE LAST windy line.
Some useful stuff to put in the .env file mentioned above:
function wsh { windy $*; }
function vi { windy vi $*; }
function sudo { su root -c "$*"; }
alias bord="windy -f40"
alias wbsh="windy -b -n 'Extra shell' -l 'Extra shell' $SHELL"
alias wfix="windy; windy -p '' -c '' -1 '' -2 ''; clear"
For those of you who run shells all the time, then ua once in a while,
the wfix alias will put the screen back into a usable state. The bord
alias will turn a full screen window back into a "mouseable" window. The
wbsh alias does just what the multi-window stuff in .profile does. This is
good if you've used up all the extra windows and you need one more. The
wsh and vi functions do what you would think. Also note my solution to
the slide/sudo wars.
John
--
John Bly Milton IV {ihnp4|cbosgd}!n8emr!uncle!jbm (jbm@uncle.UUCP)
(614)294-4823 (home, where the ATT 7300 [uncle] lives)
(614)424-7677 (work, for a little while anyway)allbery@ncoast.UUCP (Brandon Allbery) (12/02/87)
As quoted from <198@uncle.UUCP> by jbm@uncle.UUCP (John B. Milton): +--------------- | that everyone out there has windy from THE STORE! by now. I use ksh as my +--------------- ...or from unix-pc.sources... +--------------- | alias wfix="windy; windy -p '' -c '' -1 '' -2 ''; clear" | | For those of you who run shells all the time, then ua once in a while, | the wfix alias will put the screen back into a usable state. The bord +--------------- Isn't it easier to say alias ua="windy ua" ? Works fine for me.... -- Brandon S. Allbery necntc!ncoast!allbery@harvard.harvard.edu {hoptoad,harvard!necntc,cbosgd,sun!mandrill!hal,uunet!hnsurg3}!ncoast!allbery Moderator of comp.sources.misc
wtm@neoucom.UUCP (12/04/87)
Brandon mentions that his printer caused a preculiar slow motion effect similar to what I had accompanied by the "too many windows" message. I have a printer set for remote printing via uucp on neoucom's imagen 2400, so I don't have anything currently attacted to my Centronics port. The had the peculiar slow motion effect once since I removed the one additional escape-hatch getty. The only job running at the time was vi, and I had been using vi for about 10 minutes. Neoucom had just finished a big uucp transfer just as I began vi. Of course, the necessary daemons were running too. So far my system has been up since Nov 21 (knock on wood) and there haven't been any of those weird happenings since then. I really haven't changed anything radical (other than temporarily unloading The STORE! from my disk). Perhaps, the machine was just burning-in for the fist few weeks and needed to make friends with me. About the only other thing I can think of is that for the first few weeks, the electrolytic caps in the power supply were unstable. Judging from the date-code stickers inside my machine, it was sitting in a warehouse someplace for about a year before I got it. In that time the filter caps might have degraded. Apparently, the 72 meg (er, I mean 67 meg) drive was popped into the machine just before it shipped from AT&T last month. I used to manage a student lab with about a dozen Apple II computers. Almost every Apple we received crashed repeatedly for the first few days, and then would be fine for several years there after. It must have been filter caps, as the power supply light blinked and chirp! chirp! would be briefly emitted (presumably) from the switching regulator xformer core. I'm getting almost bold enought to put the escape-hatch back in and see what happens. Thanks to all the Net People that have written with their suggestions. Happy holidays, Bill