views:

1166

answers:

4

My Shell should understand PATH environment variable. It can be set and modified. It runs in two ways -interactive & batch mode. Shell is capable of taking more than one job like ls;ps;wc file;cal.

I know I will have to use execs, forks and pipes but just cant get started.

Thank you in advance.

Edited: PS:Not a homework question. Newbie to process and thread management. PSS:I want to get my hands dirty on signals too. So I should handle ^K , ^c as well.

+7  A: 

All the unix shells are open-source - so a good place to start may be to read the code.

If you're looking for a good starter article on the subject try Writing Your Own Shell from the Linux Gazette.

Another good starting point is to take a look at the source code of mini-shell just because its one of the smallest to get your head round.

Supertux
+5  A: 

Your main loop is:

  • read a line (use fgets(3) for a simple shell, readline(3) for a fancy one)
  • parse the command
  • execute the pipelines

To parse the command, there are two common choices. Write a recursive descent parser or use yacc(1) to generate one. It's a lot easier to bang out an initial parser using yacc, but you can totally get stuck debugging it and it really wants to be context-free. I prefer recursive descent but just about everyone else in the world prefers using yacc. (Technically, bison.) If the shell is really really simple, like a homework shell, yacc may be overkill.

To do the lexical analysis you can also roll your own or use flex.

DigitalRoss
I would recommend `readline()` be used in any case - it will make your life infinitely easier as long as you have to use said shell. But +1 for getting bogged down in yacc/bison. Good tools, but it's a hard task to simplify.
Chris Lutz
Aviral Dasgupta
Am getting it. But I want to get my hands dirty on signals too. So I should handle ^K , ^c as well.
Alex Xander
+1  A: 

Take a look at this link text - it's more of a skeleton. Get started with it. once you get the hang of it move on to look at mini-shell as @Supertux said.

AJ
+1  A: 

Many of the Unix books that describe the main system calls also implement a shell to illustrate how and why you might use the various calls. Stevens and Rochkind are two such books.

Jonathan Leffler