I seem to have a fairly unique question here. I am curious about messaging another person that I can see through etherape though a terminal window. Is there a program that I have to use it though, or is it just a command? I would really be greatful for any help I can get.
-
-
Re: terminal messaging
Where is this other person located? is she on another terminal on your CPU, another computer on your LAN, or another computer on the net? -
Re: terminal messaging
Thanks for getting back to me... I thought is was a nill question or something. Well they are either. Some are on the LAN, and some are on the net.Comment
-
Re: terminal messaging
Actually, if you know the IP addresses of the other computers on your lan (usually 192.168.*..*, or 169.254.*.*)or all the computers on the LAN share a hostname (e.g. athena.mit.edu) then you can treat internal and external addresses in exactly the same manner. Use the command "write" to send a message to another user at a console. Of course, if the user is using a GUI, they might not get the message for a while.Comment
-
Re: terminal messaging
this is great news. Now, when I send a message, say to a generic ip address, (192.168....) will it go to everyone? if so, how do I localize it? Another thing, I typed write, then asked it for help, and it told me it was a invalid command. How do I turn write back on?Comment
-
Re: terminal messaging
Write is a very primitive program. The only way to get help is to type "man write". You may do better with "talk", but you will have to install the "talk" (and possibly the "talkd") package. Talk is not installed by default in Kubuntu. You will have to activate your universe repository to get it.
Every computer on your lan has an individual IP address, so only the person at the console of the computer that you're writing or talking to will see the message. 192.168.*.* addresses are limited to local nets only. No one outside your local net will see the message, if you have a 192.168.*.* address. Conversely, if someone on another net has such an address on THEIR local net, you can't talk to them with a 192.168.*.* address, you need the real IP address that they are assigned by their net.
All this information may be wrong in detail, it's been at least a decade since, I last used the write command.Comment
-
Re: terminal messaging
so I should use talk. The same method I take it. now, could this generic ip thing be what is causing my machine to not receive pictures through gaim? I also can't get to it through a remote desktop connection. It receives text just fine, but nothing else.... every time I start a client for it, it only gives me the 192.168... I have dsl from wall to box, then to the computer.Comment
-
Re: terminal messaging
Your dsl modem, or your local router (if you have one), or both, should do Network Address Translation in a seamless manner. Whenever you start your computer (or router) it asks your ISP for a network address, and the ISP responds with a DHCP lease, which is a temporary network address on the ISP's network. You shoudn't even need to know what that is because it may change every 42,000 seconds, or less. It's enough that your ISP knows how to reach you and you know how to reach the net. If you're in school, substitute University Computer Services for ISP, but the principal is exactly the same.
If you can send and receive messages on GAIM you should be able to send and receive images. They're just big messages. The problem is probably a question of formats. You may need to download some proprietary software in order to view images, and if your box is an AMD64 that software might not exist. Please take a look at the Restricted Formats Page at the Ubuntu Community Help Wiki.Comment
-
Re: terminal messaging
I took a look at the restricted formats page, and I didn't see anything that really had to do with my problem. I don't run a 64 so that's just one less thing I have to worry about.... I am really curious to know what I need in order for this to work. I really like remotely controlling this machine, and recieving files from other users.Comment
Comment