I prefer ed, myself.  It reminds me of the old days, before we had full screen
editors.  Screw up enough fstab or network config files and you get real good
at it.  Always
impresses my younger colleages when I can fix a fstab with a few keystrokes,
even on their precious non-z based Linux servers. It also helps to keep a
"cheat sheet" bookmarked for when your stuck.  My go-to page is:

http://linux.about.com/library/cmd/blcmdl1_ed.htm

Martha


On Thu, 22 Sep 2016 13:07:46 -0400 Robert J Brenneman said:
>the /best/ way to edit linux files on 3270 is not to. Plan ahead and make
>backup copies of important config files before making changes and rebooting
>so you can just rename the backup back in place.
>
>but when one must, ed is available. You have to think of it as a typewriter
>though. It is not capable or aware of a terminal that can display multiple
>lines - basically you have a keyboard with no arrow keys, no PF keys, no
>pgup pgdn home end keys to use to talk to ed, and ed is only able to talk
>back to you by spitting out a single line of output at a time with a
>carriage return at the end.
>
>cat / head / tail / sed can also be used to assemble a new file out of an
>existing but broken one.
>
>
>
>--
>Jay Brenneman
>
>----------------------------------------------------------------------
>For LINUX-390 subscribe / signoff / archive access instructions,
>send email to [email protected] with the message: INFO LINUX-390 or visit
>http://www.marist.edu/htbin/wlvindex?LINUX-390
>----------------------------------------------------------------------
>For more information on Linux on System z, visit
>http://wiki.linuxvm.org/

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Reply via email to