What I do is use my favorite editor, emacs, to create a scipt of command and then I copy and paste it into the telnet session. You have to be careful that the script is not too long because evidently the cisco 675 does not do flow control and a big script will cause it to crash. Yik! Mike Bresnahan ----- Original Message ----- From: "AAAunderground" <spencer at sihope.com> To: <tclug-list at mn-linux.org> Sent: Friday, June 22, 2001 7:29 PM Subject: [TCLUG] telnet and command history > I am a somewhat erratic typist at times. This causes me much greif when I > telnet into my cisco 675. The device will not keep an editable command > history. Sure, it will give you your last command, but you can not edit any > mistake you may have made in syntax. This is no problem for short command and > such. It is a real PITA when setting filter rules though. Is it possible to > have linux remember the history? > -- > Spencer Underground > mailto:spencer at sihope.com > deltree c:\windows /y > _______________________________________________ > tclug-list mailing list > tclug-list at mn-linux.org > https://mailman.mn-linux.org/mailman/listinfo/tclug-list