would like to edit the source of a simple C program and compile using
GCC.

Got the toolkit for Linux GCC compiler installed.

I am running my 170 44P in safe mode because the KDE desktop is too
slow.

Now I would like to create the text file and edit it. I run "vi
hello.c" hoping it will create a file named hello.c and put me in the
editor. What I get instead is my dtterm window filled with lines
starting with ~ and no apparant response from the keyboard. ( ctrl-Z
gets me back to a command line. )

Am I going down a dead end with safemode? Smit works well. Sorry for
the lameness of the question but how do I create and edit a source
file?

thanks,

-Steve

StephenRichter@gmail.com wrote:
> would like to edit the source of a simple C program and compile using
> GCC.
>
> Got the toolkit for Linux GCC compiler installed.
>
> I am running my 170 44P in safe mode because the KDE desktop is too
> slow.
>
> Now I would like to create the text file and edit it. I run "vi
> hello.c" hoping it will create a file named hello.c and put me in the
> editor. What I get instead is my dtterm window filled with lines
> starting with ~ and no apparant response from the keyboard. ( ctrl-Z
> gets me back to a command line. )

ok, cancel this question. I got emacs installed and it works from the
dterm command line.

-Steve

On Tue, 19 Sep 2006 14:37:12 -0700, StephenRichter wrote:

>
> StephenRichter@gmail.com wrote:
>> would like to edit the source of a simple C program and compile using
>> GCC.
>>
>> Got the toolkit for Linux GCC compiler installed.
>>
>> I am running my 170 44P in safe mode because the KDE desktop is too
>> slow.
>>
>> Now I would like to create the text file and edit it. I run "vi
>> hello.c" hoping it will create a file named hello.c and put me in the
>> editor. What I get instead is my dtterm window filled with lines
>> starting with ~ and no apparant response from the keyboard. ( ctrl-Z
>> gets me back to a command line. )
>
> ok, cancel this question. I got emacs installed and it works from the
> dterm command line.

Like evil from Pandora's box, your question cannot be taken back...

First off, what you've described sounds like vi working normally; do you
actually know how to use vi? If you're planning to be a UNIX sys admin,
it would behoove you to learn vi, at least enough to get around (and,
maybe some ed too..)

Wil

Wil Cooley wrote:
> On Tue, 19 Sep 2006 14:37:12 -0700, StephenRichter wrote:
>
> >
> > StephenRichter@gmail.com wrote:
> >> would like to edit the source of a simple C program and compile using
> >> GCC.
> >>
> >> Got the toolkit for Linux GCC compiler installed.
> >>
> >> I am running my 170 44P in safe mode because the KDE desktop is too
> >> slow.
> >>
> >> Now I would like to create the text file and edit it. I run "vi
> >> hello.c" hoping it will create a file named hello.c and put me in the
> >> editor. What I get instead is my dtterm window filled with lines
> >> starting with ~ and no apparant response from the keyboard. ( ctrl-Z
> >> gets me back to a command line. )
> >
> > ok, cancel this question. I got emacs installed and it works from the
> > dterm command line.
>
> Like evil from Pandora's box, your question cannot be taken back...
>
> First off, what you've described sounds like vi working normally; do you
> actually know how to use vi? If you're planning to be a UNIX sys admin,
> it would behoove you to learn vi, at least enough to get around (and,
> maybe some ed too..)

I am hacking my way thru this foreign land. Things are a bit
cumbersome with my keyboard. It works fine on windows but in AIX the
insert, delete and backslash characters dont work. Now that GCC is
working for me I might write a C program that displays what scan codes
those keys are sending to the system. I appreciate the help. The whole
process is fun ( at least that is what I am telling myself ) - there is
a lot to learn.

-Steve

StephenRichter@gmail.com wrote:
> I am hacking my way thru this foreign land. Things are a bit
> cumbersome with my keyboard. It works fine on windows but in AIX the
> insert, delete and backslash characters dont work. Now that GCC is
> working for me I might write a C program that displays what scan codes
> those keys are sending to the system. I appreciate the help. The whole
> process is fun ( at least that is what I am telling myself ) - there is
> a lot to learn.

Well, why don't you just use the keyboard on your M$-box
and connect to the 7043-170 via SSH? This also will take
the burden of having to run KDE from your 7043-170. You
may have to stop the related processes first, though.
Putty has been a reasonable SSH Client back when i last
used M$-stuff. You might have to install a SSHd on the
7043-170 first. Look here:
http://sourceforge.net/projects/openssh-aix
And no, i don't encourage anyone to use telnet, just
it's already installed ;-)

Regards,

Frank

Spare him.. Anyway life for him is bad without knowledge of vim. my
advise to you is

:qall!

... don't take my bantering seriously

Thanks and regards,
Rajbir Bhattacharjee


Wil Cooley wrote:
> On Tue, 19 Sep 2006 14:37:12 -0700, StephenRichter wrote:
>
> >
> > StephenRichter@gmail.com wrote:
> >> would like to edit the source of a simple C program and compile using
> >> GCC.
> >>
> >> Got the toolkit for Linux GCC compiler installed.
> >>
> >> I am running my 170 44P in safe mode because the KDE desktop is too
> >> slow.
> >>
> >> Now I would like to create the text file and edit it. I run "vi
> >> hello.c" hoping it will create a file named hello.c and put me in the
> >> editor. What I get instead is my dtterm window filled with lines
> >> starting with ~ and no apparant response from the keyboard. ( ctrl-Z
> >> gets me back to a command line. )
> >
> > ok, cancel this question. I got emacs installed and it works from the
> > dterm command line.
>
> Like evil from Pandora's box, your question cannot be taken back...
>
> First off, what you've described sounds like vi working normally; do you
> actually know how to use vi? If you're planning to be a UNIX sys admin,
> it would behoove you to learn vi, at least enough to get around (and,
> maybe some ed too..)
>
> Wil

There are something known as Terminal Definition files.. Also there is
an environment variable called TERM. If none of them work, there is
something called stty.

You can look these up in publib.

Thanks and regards,
Rajbir Bhattacharjee


StephenRichter@gmail.com wrote:
> Wil Cooley wrote:
> > On Tue, 19 Sep 2006 14:37:12 -0700, StephenRichter wrote:
> >
> > >
> > > StephenRichter@gmail.com wrote:
> > >> would like to edit the source of a simple C program and compile using
> > >> GCC.
> > >>
> > >> Got the toolkit for Linux GCC compiler installed.
> > >>
> > >> I am running my 170 44P in safe mode because the KDE desktop is too
> > >> slow.
> > >>
> > >> Now I would like to create the text file and edit it. I run "vi
> > >> hello.c" hoping it will create a file named hello.c and put me in the
> > >> editor. What I get instead is my dtterm window filled with lines
> > >> starting with ~ and no apparant response from the keyboard. ( ctrl-Z
> > >> gets me back to a command line. )
> > >
> > > ok, cancel this question. I got emacs installed and it works from the
> > > dterm command line.
> >
> > Like evil from Pandora's box, your question cannot be taken back...
> >
> > First off, what you've described sounds like vi working normally; do you
> > actually know how to use vi? If you're planning to be a UNIX sys admin,
> > it would behoove you to learn vi, at least enough to get around (and,
> > maybe some ed too..)
>
> I am hacking my way thru this foreign land. Things are a bit
> cumbersome with my keyboard. It works fine on windows but in AIX the
> insert, delete and backslash characters dont work. Now that GCC is
> working for me I might write a C program that displays what scan codes
> those keys are sending to the system. I appreciate the help. The whole
> process is fun ( at least that is what I am telling myself ) - there is
> a lot to learn.
>
> -Steve

Frank Fegert wrote:
> StephenRichter@gmail.com wrote:
> > I am hacking my way thru this foreign land. Things are a bit
> > cumbersome with my keyboard. It works fine on windows but in AIX the
> > insert, delete and backslash characters dont work. Now that GCC is
> > working for me I might write a C program that displays what scan codes
> > those keys are sending to the system. I appreciate the help. The whole
> > process is fun ( at least that is what I am telling myself ) - there is
> > a lot to learn.
>
> Well, why don't you just use the keyboard on your M$-box
> and connect to the 7043-170 via SSH? This also will take
> the burden of having to run KDE from your 7043-170. You
> may have to stop the related processes first, though.
> Putty has been a reasonable SSH Client back when i last
> used M$-stuff. You might have to install a SSHd on the
> 7043-170 first. Look here:
> http://sourceforge.net/projects/openssh-aix

thanks!

-Steve