Advanced Unix Commands

Some more Unix Commands for you in addition to those posted earlier. Watch this space for more.

• jobs --- lists your currently active jobs (those that you put in the background) and their job numbers. Useful to determine which one you want to foreground if you have lots of them.
• bg --- background a job after suspending it.
• fg %jobnumber --- foreground a job
• !! --- repeat the previous command (but CTRL-p, is safer, because you have hit return in addition)
• !pattern --- repeat the last command that starts with pattern
• echo $VARIABLE --- shows the value of an environment variable
• setenv --- lets you set environment variables. For example, if you typed a wrong value for the TERM variable when logging in, you don't have to log out and start over, but you can just do setenv TERM vt100 (or whatever). To see what all your environment variables are set to, type env. The one that you're most likely to have to set is the DISPLAY variable, when using an X-display.
• unset VAR --- lets you un-set environment variables. Useful, for example, if you've usually set autologout but want to stay logged on for a while without typing for some reason, or if you set the DISPLAY variable automatically but want to avoid opening windows for some reason.
• source filename --- you need to source your dotfiles after making changes for them to take effect (or log off and in again)
• load --- will show you the load average graphically
• ispell filename --- will check the spelling in your file. If you're running it on a LaTeX file use the -T option to tell it to ignore the LaTeX commands. You can create and use your own dictionary to avoid having it tell you that your own name, those of fellow linguists, and linguistics terminology are a typos in every paper you write.
• weblint --- checks the syntax of html files
• latex2html --- translates LaTeX files into HTML
• wn word option --- lets you access the WordNet database and display, for example, synonyms, hypernyms, or hyponyms, depending on the option you select

Command editing in the tcsh

These things are the same as in emacs:

Backspace --- delete previous character
CTRL-d --- delete next character
CTRL-k --- delete rest of line
CTRL-a --- go to start of line
CTRL-e --- go to end of line
CTRL-b --- go backwards without deleting
CTRL-f --- go forward without deleting

Other useful things

TAB --- complete filename or command up to the point of uniqueness

CTRL-u --- cancel whole line

CTRL-p --- show the last command typed, then the one before that, etc.

(you can also use the cursor up key for this)

CTRL-n --- go forwards in the history of commands

(you can also use the cursor down key for this)

CTRL-c --- cancel the processes after it has started

CTRL-z --- suspend a running process (e.g. in order to do something else in between)

you can then put the process in the background with bg

CTRL-l --- redraws the screen

| (piping) --- Lets you execute any number of commands in a sequence.

The second command will be executed once the first is done, and so forth, using the previous command's output as input. You can achieve the same effect by putting the output in a file and giving the filename as an argument to the second command, but that would be much more complicated, and you'd have to remember to remove all the junkfiles afterwards. Some examples that show the usefulness of this:
ls | more --- will show you one screenful at a time, which is useful with any command that will produce a lot of output, e.g. also ps -aux
man ls | grep time --- checks whether the man page for ls has something to say about listing files by time - very useful when you have a suspicion some command may be capable of doing what you want, but you aren't sure.
ls -lR | grep dvi --- will show you all your dvi files - useful to solve disk space problems, since they're large and usually can be deleted. 

Basic Unix Commands

Files

• ls --- lists your files
  ls -l --- lists your files in 'long format', which contains lots of useful information, e.g. the exact size of the file, who owns the file and who has the right to look at it, and when it was last modified.
  ls -a --- lists all files, including the ones whose filenames begin in a dot, which you do not always want to see.
  There are many more options, for example to list files by size, by date, recursively etc.
• more filename --- shows the first part of a file, just as much as will fit on one screen. Just hit the space bar to see more or q to quit. You can use /pattern to search for a pattern.
• emacs filename --- is an editor that lets you create and edit a file. 
• mv filename1 filename2 --- moves a file (i.e. gives it a different name, or moves it into a different directory (see below)
• cp filename1 filename2 --- copies a file
• rm filename --- removes a file. It is wise to use the option rm -i, which will ask you for confirmation before actually deleting anything. You can make this your default by making an alias in your .cshrc file.
• diff filename1 filename2 --- compares files, and shows where they differ
• wc filename --- tells you how many lines, words, and characters there are in a file
• chmod options filename --- lets you change the read, write, and execute permissions on your files. The default is that only you can look at them and change them, but you may sometimes want to change these permissions. For example, chmod o+r filename will make the file readable for everyone, and chmod o-r filename will make it unreadable for others again. Note that for someone to be able to actually look at the file the directories it is in need to be at least executable. 
• File Compression
  • gzip filename --- compresses files, so that they take up much less space. Usually text files compress to about half their original size, but it depends very much on the size of the file and the nature of the contents. There are other tools for this purpose, too (e.g. compress), but gzip usually gives the highest compression rate. Gzip produces files with the ending '.gz' appended to the original filename.
  • gunzip filename --- uncompresses files compressed by gzip.
  • gzcat filename --- lets you look at a gzipped file without actually having to gunzip it (same as gunzip -c). You can even print it directly, using gzcat filename | lpr
• printing
  • lpr filename --- print. Use the -P option to specify the printer name if you want to use a printer other than your default printer. For example, if you want to print double-sided, use 'lpr -Pvalkyr-d', or if you're at CSLI, you may want to use 'lpr -Pcord115-d'. See 'help printers' for more information about printers and their locations.
  • lpq --- check out the printer queue, e.g. to get the number needed for removal, or to see how many other files will be printed before yours will come out
  • lprm jobnumber --- remove something from the printer queue. You can find the job number by using lpq. Theoretically you also have to specify a printer name, but this isn't necessary as long as you use your default printer in the department.
  • genscript --- converts plain text files into postscript for printing, and gives you some options for formatting. Consider making an alias like alias ecop 'genscript -2 -r \!* | lpr -h -Pvalkyr' to print two pages on one piece of paper.
  • dvips filename --- print .dvi files (i.e. files produced by LaTeX). You can use dviselect to print only selected pages. S

Directories

Directories, like folders on a Macintosh, are used to group files together in a hierarchical structure.

• mkdir dirname --- make a new directory
• cd dirname --- change directory. You basically 'go' to another directory, and you will see the files in that directory when you do 'ls'. You always start out in your 'home directory', and you can get back there by typing 'cd' without arguments. 'cd ..' will get you one level up from your current position. You don't have to walk along step by step - you can make big leaps or avoid walking around by specifying pathnames.
• pwd --- tells you where you currently are.

Finding things

• ff --- find files anywhere on the system. This can be extremely useful if you've forgotten in which directory you put a file, but do remember the name. In fact, if you use ff -p you don't even need the full name, just the beginning. This can also be useful for finding other things on the system, e.g. documentation.
• grep string filename(s) --- looks for the string in the files. This can be useful a lot of purposes, e.g. finding the right file among many, figuring out which is the right version of something, and even doing serious corpus work. grep comes in several varieties (grep, egrep, and fgrep) and has a lot of very flexible options. Check out the man pages if this sounds good to you.

About other people

• w --- tells you who's logged in, and what they're doing. Especially useful: the 'idle' part. This allows you to see whether they're actually sitting there typing away at their keyboards right at the moment.
• who --- tells you who's logged on, and where they're coming from. Useful if you're looking for someone who's actually physically in the same building as you, or in some other particular location.
• finger username --- gives you lots of information about that user, e.g. when they last read their mail and whether they're logged in. Often people put other practical information, such as phone numbers and addresses, in a file called .plan. This information is also displayed by 'finger'.
• last -1 username --- tells you when the user last logged on and off and from where. Without any options, last will give you a list of everyone's logins.
• talk username --- lets you have a (typed) conversation with another user
• write username --- lets you exchange one-line messages with another user
• elm --- lets you send e-mail messages to people around the world (and, of course, read them). It's not the only mailer you can use, but the one we recommend.

About your (electronic) self

• whoami --- returns your username. Sounds useless, but isn't. You may need to find out who it is who forgot to log out somewhere, and make sure *you* have logged out.
• finger & .plan files
  of course you can finger yourself, too. That can be useful e.g. as a quick check whether you got new mail. Try to create a useful .plan file soon. Look at other people's .plan files for ideas. The file needs to be readable for everyone in order to be visible through 'finger'. Do 'chmod a+r .plan' if necessary. You should realize that this information is accessible from anywhere in the world, not just to other people on turing.
• passwd --- lets you change your password, which you should do regularly (at least once a year). 
• ps -u yourusername --- lists your processes. Contains lots of information about them, including the process ID, which you need if you have to kill a process. Normally, when you have been kicked out of a dialin session or have otherwise managed to get yourself disconnected abruptly, this list will contain the processes you need to kill. Those may include the shell (tcsh or whatever you're using), and anything you were running, for example emacs or elm. Be careful not to kill your current shell - the one with the number closer to the one of the ps command you're currently running. But if it happens, don't panic. Just try again :) If you're using an X-display you may have to kill some X processes before you can start them again. These will show only when you use ps -efl, because they're root processes.
• kill PID --- kills (ends) the processes with the ID you gave. This works only for your own processes, of course. Get the ID by using ps. If the process doesn't 'die' properly, use the option -9. But attempt without that option first, because it doesn't give the process a chance to finish possibly important business before dying. You may need to kill processes for example if your modem connection was interrupted and you didn't get logged out properly, which sometimes happens.
• quota -v --- show what your disk quota is (i.e. how much space you have to store files), how much you're actually using, and in case you've exceeded your quota (which you'll be given an automatic warning about by the system) how much time you have left to sort them out (by deleting or gzipping some, or moving them to your own computer).
• du filename --- shows the disk usage of the files and directories in filename (without argument the current directory is used). du -s gives only a total.
• last yourusername --- lists your last logins. Can be a useful memory aid for when you were where, how long you've been working for, and keeping track of your phonebill if you're making a non-local phonecall for dialling in.

Connecting to the outside world

• nn --- allows you to read news. It will first let you read the news local to turing, and then the remote news. If you want to read only the local or remote news, you can use nnl or nnr, respectively. To learn more about nn type nn, then \tty{:man}, then \tty{=.*}, then \tty{Z}, then hit the space bar to step through the manual. Or look at the man page. 
• rlogin hostname --- lets you connect to a remote host
• telnet hostname --- also lets you connect to a remote host. Use rlogin whenever possible.
• ftp hostname --- lets you download files from a remote host which is set up as an ftp-server. This is a common method for exchanging academic papers and drafts. If you need to make a paper of yours available in this way, you can (temporarily) put a copy in /user/ftp/pub/TMP. For more permanent solutions, ask Emma. The most important commands within ftp are get for getting files from the remote machine, and put for putting them there (mget and mput let you specify more than one file at once). Sounds straightforward, but be sure not to confuse the two, especially when your physical location doesn't correspond to the direction of the ftp connection you're making. ftp just overwrites files with the same filename. If you're transferring anything other than ASCII text, use binary mode.
• lynx --- lets you browse the web from an ordinary terminal. Of course you can see only the text, not the pictures. You can type any URL as an argument to the G command. When you're doing this from any Stanford host you can leave out the .stanford.edu part of the URL when connecting to Stanford URLs. Type H at any time to learn more about lynx, and Q to exit.

Miscellaneous tools

• webster word --- looks up the word in an electronic version of Webster's dictionary and returns the definition(s)
• date --- shows the current date and time.
• cal --- shows a calendar of the current month. Use e.g., 'cal 10 1995' to get that for October 95, or 'cal 1995' to get the whole year.  

Top 10 Interview Tips

Great interviews arise from careful groundwork. You can ace your next interview if you:

1. Enter into a state of relaxed concentration. This is the state from which great basketball players or Olympic skaters operate. You'll need to quiet the negative self chatter in your head through meditation or visualization prior to sitting down in the meeting. You'll focus on the present moment and will be less apt to experience lapses in concentration, nervousness, self-doubt and self-condemnation.
2. Act spontaneous, but be well prepared. Be your authentic self, professional yet real. Engage in true conversation with your interviewer, resting on the preparation you did prior to coming to the meeting. Conduct several trial runs with another person simulating the interview before it actually occurs. It's the same as anticipating the questions you'll be asked on a final exam.
3. Set goals for the interview. It is your job to leave the meeting feeling secure that the interviewer knows as much as he or she possibly can about your skills, abilities, experience and achievements. If you sense there are misconceptions, clear them up before leaving. If the interviewer doesn't get around to asking you important questions, pose them yourself (diplomatically) and answer them. Don't leave the meeting without getting your own questions answered so that you have a clear idea of what you would be getting yourself into. If possible, try to get further interviews, especially with other key players.
4. Know the question behind the question. Ultimately, every question boils down to, "Why should we hire you?" Be sure you answer that completely. If there is a question about your meeting deadlines, consider whether the interviewer is probing delicately about your personal life, careful not to ask you whether your family responsibilities will interfere with your work. Find away to address fears if you sense they are present.
5. Follow up with an effective "thank you" letter. Don't write this letter lightly. It is another opportunity to market yourself. Find some areas discussed in the meeting and expand upon them in your letter. Writing a letter after a meeting is a very minimum. Standing out among the other candidates will occur if you thoughtfully consider this follow up letter as an additional interview in which you get to do all the talking. Propose useful ideas that demonstrate your added value to the team.
6. Consider the interviewer's agenda. Much is on the shoulders of the interviewer. He or she has the responsibility of hiring the right candidate. Your ability to do the job will need to be justified. "Are there additional pluses here?" "Will this person fit the culture of this organization?" These as well as other questions will be heavily on the interviewer's mind.
7. Find ways to demonstrate your qualities above and beyond just doing the job.
   Expect to answer the question, "Tell me about yourself." This is a pet question of prepared and even unprepared interviewers. Everything you include should answer the question, "Why should we hire you?" Carefully prepare your answer to include examples of achievements from your work life that closely match the elements of the job before you. Obviously, you'll want to know as much about the job description as you can before you respond to the question.
8. Watch those nonverbal clues. Experts estimate that words express only 30% to 35% of what people actually communicate; facial expressions and body movements and actions convey the rest. Make and keep eye contact. Walk and sit with a confident air. Lean toward an interviewer to show interest and enthusiasm. Speak with a well-modulated voice that supports appropriate excitement for the opportunity before you.
9. Be smart about money questions. Don't fall into the trap of telling the interviewer your financial expectations. You may be asking for too little or too much money and in each case ruin your chances of being offered the job. Instead, ask what salary range the job falls in. Attempt to postpone a money discussion until you have a better understanding of the scope of responsibilities of the job.
10. Don't hang out your dirty laundry. Be careful not to bare your soul and tell tales that are inappropriate or beyond the scope of the interview. State your previous experience in the most positive terms. Even if you disagreed with a former employer, express your enthusiasm for earlier situations as much as you can. Whenever you speak negatively about another person or situation in which you were directly involved, you run the risk (early in the relationship) of appearing like a troubled person who may have difficulty working with others.

Resume Preparation

Your resume is the first interface you have with your employer. Make the most of this opportunity............. The employment market is changing all the time and so have resumes, evolving from a one-size-fits-all standard. Here are our tips to convert your resume into a catching one.
Follow These Basic Standards....

• Don't overcrowd your resume; allow for plenty of white space.
• Keep your resume to one page whenever possible.
• Keep the number of fonts you use to a minimum -- two at the most.
• Use a font that is easy to read. Times Roman works well.
• Do not justify the lines of type on your resume. Allow the right side of the page to "rag."
• Do not overuse capitalization, italics, underlines, or other emphasizing features.
• Make sure your name, address, and a phone number appear on your resume and all correspondence, preferably at the top of the page.
• Print your resume on white or cream paper using a good-quality printer.
• Second- and third-generation photocopies must be avoided.
• Print on one side of the paper only.

Avoid Mistakes:

Spelling Mistakes:

To avoid spelling mistakes:

• Don't use words with which you aren't familiar.
• Use a dictionary as you write.
• Perform a spell check on your finished resume.
• Carefully read every word in your resume.
• Have a friend or two proof read your resume for you.
• Punctuation Mistakes:

Things to look for:

• Periods at the end of all full sentences.
• Be consistent in your use of punctuation.
• Always put periods and commas within quotation marks.
• Avoid using exclamation points.

Grammatical Mistakes:

Grammar hang-ups to watch for:

• Do not switch tenses within your resume.
• The duties you currently perform should be in present tense (i.e., write reports)
• Duties you may have performed at past jobs should be in past tense (i.e., wrote reports).
• Capitalize all proper nouns.
• When expressing numbers, write out all numbers between one and nine (i.e., one, five, seven), but use numerals for all numbers 10 and above (i.e., 10, 25, 108).
• If you begin a sentence with a numeral, spell out that numeral (e.g. Eleven service awards won while employed.).
• Make sure your date formats are consistent (i.e.11/22/01 or Nov. 22, 2001, or 11.22.01. Choose one and stick with it.).

Choose Your Words Carefully:

Be on the lookout for the following easily confused words:

• accept (to receive), except (to exclude),
• all right (correct), alright (this is not a word)
• affect (to bring about change), effect (result),
• personal (private), personnel (staff members)
• role (a character assigned or a function), roll (to revolve).
• Use action words (i.e., wrote reports, increased revenues, directed staff).

References:

• In most instances it is not necessary to include names and address of references on the resume. If you include a reference, make it sure that the referenced person knows very well about you. It is also advisable to add the persons as references, whom the employer can contact easily. If possible add the phone number and e-mail ID of the reference. Never add a person as a reference, about whom you know nothing
  STICK TO THE POINT
  Employers have a busy schedule, so don't expect them to read through a long resume. Ideally, resumes should be of one page, or of two pages only if absolutely necessary, to describe relevant work experience.
  WORDS COUNT
  Use of language is extremely important; you need to sell yourself to an employer quickly and efficiently. Address your potential employer's needs with a clearly written, compelling resume. Avoid large paragraphs (five or six lines). If you provide small, digestible pieces of information, your resume will be read. Use action verbs. Verbs such as "developed", "managed", and "designed" emphasise your accomplishments. Don't use declarative sentences like "I developed the ..." or "I assisted in ...", leave out the "I". Avoid passive constructions, such as "was responsible for managing". Just say, "managed": that sounds stronger and more active.
  MAKE THE MOST OF YOUR EXPERIENCE
  Employers need to know what you have accomplished to have an idea of what you can do for them. Don't be vague. Telling someone that you "improved the company's efficiency" doesn't say much. But if you say that you "cut overhead costs by 20 per cent and saved the company Rs 20 lakh during the last fiscal year", you are more specific.
  HONESTY IS A GOOD POLICY
  Employers will feel more comfortable hiring you if they can verify your accomplishments. There is a difference between making the most of your experience and exaggerating or falsifying it. A falsified resume can cost you the job later.
  DOUBLE-CHECK FOR MISTAKES
  Check your resume for correct grammar and spelling - evidence of good communication skills and attention to detail. Nothing can ruin your chances of getting a job faster than submitting a resume filled with preventable mistakes. Make your resume easy on the eye. Use normal margins (1" on the top and bottom, 1.25" on the sides) and don't cram your text on the page. Allow for some space between the different sections. Avoid unusual or exotic fonts. Preferred fonts: Arial and Times Roman

GROUP DISCUSSION Tips

A group discussion (GD) is a simulated exercise, where you cannot suddenly put up a show, since the evaluators will see through you easily. In this page you can find tips on GD and how to handle them to ensure a positive outcome. Here's how most group discussions work :

1. Normally groups of 8-10 candidates are formed into a leaderless group, and are given a specific situation to analyze and discuss within a given time limit.
2. The group may be given a case study and asked to come out with a solution for a problem.
3. The group may be given a topic and asked to discuss on the same. A panel will observe the proceedings and evaluate the members of the group. OBJECTIVELets start from the basic.
4. One needs to know what one's objective in the group is. A good definition of your objective is - to be noticed to have contributed meaningfully in an attempt to help the group reach the right consensus. What does this essentially mean?
   The first implication is that you should be noticed by the panel. Merely making a meaningful contribution and helping the group arrive at a consensus is not enough. You have to be seen by the evaluating panel to have made the meaningful contribution. What does that mean in practice?
5. You must ensure that the group hears you. If the group hears you, so will the evaluator. That does not mean that you shout at the top of your voice and be noticed for the wrong reasons.
6. You have to be assertive. If you are not a very assertive person, you will have to simply learn to be assertive for those 15 minutes. Remember, assertiveness does not mean being bull-headed or being arrogant.
7. And most importantly, you have to make your chances. Many group discussion participants often complain that they did not get a chance to speak. The fact is that in no group discussion will you get a chance to speak. There is nothing more unacceptable in a GD than keeping one's mouth shut or just murmuring things which are inaudible.
8. Participate in as many practice GDs as possible before you attend the actual GD. There is nothing like practice to help you overcome the fear of talking in a GD.
   

The second important implication is that making just any sort of contribution is not enough. Your contribution has to be meaningful. A meaningful contribution suggests that
You have a good knowledge base
You are able to put forth your arguments logically and are a good communicator.

The quality of what you said is more valuable than the quantity. There is this myth amongst many group discussion participants that the way to succeed in a group discussion is by speaking loudly and at great length. One could not be more wrong. You must have meat in your arguments. Therefore, think things through carefully. Always enter the room with a piece of paper and a pen. In the first two minutes jot down as many ideas as you can. When you jot down points, keep these pointers in mind.If it is a topic where you are expected to take a stand, say for example, "Should India sign the Comprehensive Test Ban Treaty?" note down points for both sides of the argument. It will be useful on two counts -

• One, if you do not start the GD and are not amongst the first five speakers and find that everyone in the group is talking for the topic, then it makes sense to take the alternate approach and oppose the topic even if you initially intended to talk for the topic.
• Second, it helps to have a knowledge of how group members who take a stand diametrically opposite to yours will put forth their argument and to be prepared with counter arguments.
• Everybody else will state the obvious. So highlight some points that are not obvious. The different perspective that you bring to the group will be highly apprecaited by the panel.
• Some pointers on being relevant while having a different perspective are:

1. Be careful that the "something different" you state is still relevant to the topic being debated.
2. Can you take the group ahead if it is stuck at one point?
3. Can you take it in a fresh and more relevant direction?
4. The last implication is that you must be clearly seen to be attempting to build a consensus.
5. Gaining support or influencing colleagues is the mantra adopted by many a successful Business Leaders.
6. Nobody expects a group of ten intelligent, assertive people, all with different points of view on a controversial subject to actually achieve a consensus. But what matters is "Did you make attempts to build a consensus?"

The reason why an attempt to build a consensus is important is because in most work situations you will have to work with people in a team, accept joint responsibilities and take decisions as a group.
You must demonstrate the fact that you are capable and inclined to work as part of a team.