Darren Spruell wrote:
...
That means your /etc/remote file is still at its defaults (which
perhaps should change):
tty00|For hp300,i386,mac68k,macppc,mvmeppc,vax:\
:dv=/dev/tty00:tc=direct:tc=unixhost:
cua00|For hp300,i386,mac68k,macppc,mvmeppc,vax:\
:dv=/dev/cua00:tc=dialup:tc=unixhost:
See, when you do "tip tty00", you aren't actually saying, "use port
tty00", you are saying, "use /etc/remote entry tty00", which just
so happens to point to port tty00. It doesn't need to. You could
really mess with someone. :)
Try doing this:
# tip tty01
tip: unknown host tty01
unknown HOST, not unknown port (this machine has a second com port).
The "tc=dialup" is what is hurting you. Just change it to "direct".
Depending upon your cable and needs, you may not ever care, but cua
is more forgiving.
Nick.
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
| Bart Van Assche | Integration of SCST in the mainstream Linux kernel |
| Heiko Carstens | Re: -mm merge plans for 2.6.23 -- sys_fallocate |
git: | |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | Re: [GIT]: Networking |
| Jarek Poplawski | [PATCH iproute2] Re: HTB accuracy for high speed |
