Greetings;
I use ed in that case. It saves me the aggravation of having to
type the entire line completely correct! And in the cases where
I need to issue several commands I put them in a file and
source it. Much quicker in the long run since my error rate
on strange keyboards is about 1 in 10! Slightly better at my desk. ;-)
If you work on wintel systems you need to know edlin. If you work on
*nix systems you need to know ed. That knowledge has saved my bacon
more than once!
Good Luck!
Dennis
Adam Thornton <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 01/30/2002
01:46:22 PM
Please respond to Linux on 390 Port <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject: Re: got GB-ethernet working! was "getting GB ethernet working wit
h SLES7"
On Wed, Jan 30, 2002 at 12:54:16PM -0500, Post, Mark K wrote:
>> echo 'noauto,0x0000,0xedff' >> /etc/chandev.conf
>> echo 'noauto,0xee03,0xffff' > /etc/chandev.conf
>> echo 'add_parms,0x10,0xee00,0xee02,portname:OSA1' > /etc/chandev.conf
> Hmm. You need to spend a few minutes learning some basic vi commands.
> Creating .conf files with echo is certainly feasible, but not very
> desirable!
But if you don't have a network, then you have a 3215 or a 3270 or the
HMC. In which case, vi won't help you.
In these cases, I use cat. Others use echo. I suppose I could learn
ed, since ed is the standard editor, but I prefer not to.
Adam
