> > > Do you have something like "LD_LIBRARY_PATH=/usr/pkg/lib" in your
> > > shell startup file (e.g., ~/.profile)? That's a bad idea in
> > > general. I doubt it's the source of this problem but I'd advise
> > > against it.
>  
> > No, only in the PATH variable (on its end).

I meant that I have /usr/pkg/bin and sbin at the end of PATH what's not
relevant, sry.

> Did you add /usr/pkg/lib to your /etc/ld.so.conf? That would be even
> worse because it affected every user and e.g., you might have two or
> more versions libiconv.so and libpthread.so in different paths. I mean
> your sh or tput isn't linked against anything from /usr/pkg/lib, is
> it?

No they are not linked against it (built with tools). And yes I had 
/usr/pkg/lib in /etc/ld.so.conf,
because there are libs that otherwise had not been found by some
non-pkgsrc programs I tested once. But now it's not
longer needed. I've removed it. Thanks.

> > > $ env|grep TERM
>  
> > Should I recompile the kernel with ``options WSEMUL_VT220'' (*argh*)
> > to give you the output?
> 
> Don't you still have the old kernel as /onetbsd?

Nope for that kernel not. But I've compiled a new one.

Okay, here's the output of env|grep TERM on a ttyE*:
<snip>
TERM=vt220
</snip>

Here's the output of env|grep TERM on a xterm (ttyp*):
<snip>
TERM=xterm
TERMCAP=xterm|vs100|xterm terminal emulator (X Window
System):am:bs:km:mi:ms:ut:xn:co#80:it#8:li#24:Co#8:pa#64:AB=\E[4%dm:AF=
\E[3%dm:op=\E[m:@1=\EOE:@7=\EOF:@8=\EOM:k;=\E[21~:ac=``aaffggjjkkllmmnn
ooppqqrrssttuuvvwwxxyyzz{{||}}~~:AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%d
B:IC=\E[%d@:K1=\EOw:K2=\EOy:K3=\EOu:K4=\EOq:K5=\EOs:LE=\E[%dD:RI=\E[%dC
:UP=\E[%dA:ae=^O:al=\E[L:as=^N:bl=^G:bt=\E[Z:cd=\E[J:ce=\E[K:cl=\E[H\E[
2J:cm=\E[%i%d;%dH:cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:dl=\E[M:do=^J:e
c=\E[%dX:ei=\E[4l:ho=\E[H:im=\E[4h:is=\E7\E[r\E[m\E[?7h\E[?1;3;4;6l\E[4
l\E8\E>:k1=\EOP:k2=\EOQ:k3=\EOR:k4=\EOS:k5=\E[15~:k6=\E[17~:k7=\E[18~:k
8=\E[19~:k9=\E[20~:kD=\E[3~:kI=\E[2~:kN=\E[6~:kP=\E[5~:kd=\EOB:ke=\E[?1
l\E>:kh=\EOH:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:ku=\EOA:le=^H:md=\E[1m:me=\E[
m:mr=\E[7m:nd=\E[C:rc=\E8:sc=\E7:se=\E[m:sf=^J:so=\E[7m:sr=\EM:st=\EH:t
a=^I:te=\E[2J\E[?47l\E8:ti=\E7\E[?47h:ue=\E[m:up=\E[A:us=\E[4m:ve=\E[?2
5h:vi=\E[?25l:vs=\E[?25h::ZZ=0x80a8000:kb=\010:
</snip>

And the output after executing ``login'' on a xterm (ttyp*):
<snip>
TERM=networ
</snip>

> There's no termcap description for "su" which would explain the
> tgetent failure. 

If I su on a ttyE* or a ttyp* (after using ``login'') it works -- given
that I use sh or csh as standard shell for root (compiled with tools).

But, if I set tcsh as standard shell (for root) that's compiled
from pkgsrc it works only on ttyE*, on ttyp* (after using ``login'')
I get the following:

<snip>
<*_*> su
Password:
_tcsh: No entry for terminal type "networ"
_tcsh: using dumb terminal settings.
www# clear
tput: tgetent failure: No such file or directory
</snip>

> The other output from your
> first login screen appears still strange. TERM was probably set to
> vt220 or xterm but not vt100 due to the '2' but it wasn't interpreted
> at all. This might be a bug in the terminal emulator (i.e., in the
> kernel) but I'm not sure. Maybe, it's that in /etc/ttys the terminals
> are set to vt100?

/etc/ttys:
console is set to vt100.
ttyE0 is set to vt220 but with status off.
ttyE1 to ttyE7 are set to vt220.

The ttyp* are set to network what's the reason why the last snip above
has as TERM networ (where's the terminating k? :)

I'm willing to do more testing, say what I have to provide.

Thanks for the help (and that you are concering you with this)!

> -- 
> Christian

Hernani