> 	For some reason I'm having some terminal problems... not on the
> console, but when I telnet in using ncsa telnet 2.7b4 from another
> machine, my ^C doesn't kill a process, it suspends it. And, ^U doesn't

i don't think it suspends the process....just suspends the dump on your
screen (which is independant of NetBSD). i could be wrong though.

> erase your command line input. I'm using vt100 on both the console and in
> my telnets, but when I telnet I get the above behavior, and when I am on
> the console the ^C and ^U keystrokes work normally.... any ideas? 

yeah NCSA has problems doing that. i think NCSA telnet has remapping
functions available for control-c, etc.

> 	Oh... one thing, is that since I use pico alot I erased the
> Interrupt Process Key (in ncsa telnet, it gives you an option of your
> Interrupt, Suspend Output and Resume Output keys. When it's ^C (the
> default) the ^C function in pico (shows which line you are on) doesn't
> work, and when I'm programming I pretty much NEED that function, so I know
> where errors are, etc. 

yeah, suspend output, that must be it. since those functions are either
annoying or what-not, just set them to obscure keys, so they'll get out of
your way.

> 	But, would disabling that key, or changing it to something else
> affect both the ^C and the ^U characters? Do you think it's a
> NetBSD/terminal emulation problem, or a ncsa telnet problem?

definately a NCSA telnet problem. i've seen the problem in all
cases...whether other systems or MUDs.
you could reduce the problem by getting Bettertelnet, which is basically a
modified NCSA Telnet. it's pretty good, but i don't use it because it has
some kinda wierd bug where it won't transmit all characters you type in
while something is heavily scrolling down the screen - pretty obscure, but
annoying sometimes.

good luck,

  - a