06-15-2007
you should think about what you like most --- dealing with networking issues or dealing with computer issues ...
if you prefer the networking side, do as rhfromm suggested ...
if you prefer the computer side, look into getting certified in solaris, hp-ux or aix ... linux is also good but the majority of corporate it environments require that you know one of the three main unix flavors i mentioned ...
or you can combine both ... get certified in both a unix flavor and in networking ... this way you have more to bring to the table when you talk to recruiters ...
good luck!
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi, all!
I'm a 37 year-old Electrical Engineer with a BSEE and 12 years of experience. I was laid off last week, and have been considering a career change (I've had enough of electrical design). I've used computers for the past 20 years as a hobby (building computers, playing games,... (5 Replies)
Discussion started by: Snapster
5 Replies
2. What is on Your Mind?
Hi,
I've been in the IT field for a few years now, less than 10. I've done a little of everything from database administration, development, systems administration, and unix administration. Although, I wouldnt say I'm a senior level in any of those. Unix definitely stands out in my preferences... (5 Replies)
Discussion started by: NycUnxer
5 Replies
3. Programming
Hi,
I am having experience on Perl and C# and worked as Windows Sytem Admin and now iam planning to become a UNIX developer.
I am having knowledge on basic UNIX..
can any one suggest me any good material for c/c++ UNIX programming.
on what all things a UNIX Programmer needs to... (0 Replies)
Discussion started by: chandrareddy1
0 Replies
4. UNIX for Dummies Questions & Answers
I am working in a company in which my work includes working on Linux nodes. The "uname -arv" command outputs -
"Linux clx28ap01 2.6.18-238.12.1.el5 #1 SMP Sat May 7 20:18:50 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux".
I generally use various command to stop/start the servers, checking space,... (7 Replies)
Discussion started by: csrohit
7 Replies
5. What is on Your Mind?
Hi Admins and Moderators,
I am already in job for more than 2 years.
I need some guidance in deciding the career path.
Please suggest what should be the correct forum to post this to ?
Rgrds,
Rohit
Moved thread to appropriate forum. (0 Replies)
Discussion started by: csrohit
0 Replies
6. What is on Your Mind?
First I like to say hi to all the people in this community. The reason I am here is because I am lost and looking for advice on my career path.
Here is a short history. I worked in the IT industry for about 10 yrs, sys admin, QA, and developer. During 911 I lost my job. Since then I have... (4 Replies)
Discussion started by: navy
4 Replies
7. What is on Your Mind?
Hi All,
This question is regarding career path. I was not sure about which forum I should drop it, so putting it here.
I have 12 years of experience on UNIX i.e. majority of Solaris and some of Linux (Suse & Red Hat). Since starting I have been working on 100% administration side and I am not... (0 Replies)
Discussion started by: solaris_1977
0 Replies
8. What is on Your Mind?
Hello,
Just wanted to have a suggestion on UNIX carrier path and I couldn't found any proper forum/blog where I can put this question better than this one.
I have been working on Solaris from past 13 years and some years on Linux. It was completely on Admin side and never on development or... (12 Replies)
Discussion started by: solaris_1977
12 Replies
TALK(1) BSD General Commands Manual TALK(1)
NAME
talk -- talk to another user
SYNOPSIS
talk person [-x] [ttyname]
DESCRIPTION
Talk is a visual communication program which copies lines from your terminal to that of another user.
Options available:
person If you wish to talk to someone on your own machine, then person is just the person's login name. If you wish to talk to a user on
another host, then person is of the form 'user@host' ( or 'host.user' or 'host!user' or 'host:user' ).
-x If you wish to talk to a user who has dot character in username, the -x argument will force 'user@host' form of the person and talk
will take dots as part of user name.
ttyname If you wish to talk to a user who is logged in more than once, the ttyname argument may be used to indicate the appropriate terminal
name, where ttyname is of the form 'ttyXX' or 'pts/X'.
When first called, talk contacts the talk daemon on the other user's machine, which sends the message
Message from TalkDaemon@his_machine...
talk: connection requested by your_name@your_machine.
talk: respond with: talk your_name@your_machine
to that user. At this point, he then replies by typing
talk your_name@your_machine
It doesn't matter from which machine the recipient replies, as long as his login name is the same. Once communication is established, the
two parties may type simultaneously; their output will appear in separate windows. Typing control-L (^L) will cause the screen to be
reprinted. The erase, kill line, and word erase characters (normally ^H, ^U, and ^W respectively) will behave normally. To exit, just type
the interrupt character (normally ^C); talk then moves the cursor to the bottom of the screen and restores the terminal to its previous
state.
As of netkit-ntalk 0.15 talk supports scrollback; use esc-p and esc-n to scroll your window, and ctrl-p and ctrl-n to scroll the other win-
dow. These keys are now opposite from the way they were in 0.16; while this will probably be confusing at first, the rationale is that the
key combinations with escape are harder to type and should therefore be used to scroll one's own screen, since one needs to do that much less
often.
If you do not want to receive talk requests, you may block them using the mesg(1) command. By default, talk requests are normally not
blocked. Certain commands, in particular nroff(1), pine(1), and pr(1), may block messages temporarily in order to prevent messy output.
FILES
/etc/hosts to find the recipient's machine
/var/run/utmp to find the recipient's tty
SEE ALSO
mail(1), mesg(1), who(1), write(1), talkd(8)
BUGS
The protocol used to communicate with the talk daemon is braindead.
Also, the version of talk(1) released with 4.2BSD uses a different and even more braindead protocol that is completely incompatible. Some
vendor Unixes (particularly those from Sun) have been found to use this old protocol.
Old versions of talk may have trouble running on machines with more than one IP address, such as machines with dynamic SLIP or PPP connec-
tions. This problem is fixed as of netkit-ntalk 0.11, but may affect people you are trying to communicate with.
HISTORY
The talk command appeared in 4.2BSD.
Linux NetKit (0.17) November 24, 1999 Linux NetKit (0.17)