Skip to content

Latest commit

 

History

History
189 lines (132 loc) · 5.47 KB

README.md

File metadata and controls

189 lines (132 loc) · 5.47 KB
Raw

C - Simple Shell

  • By Julien Barbier
  • Project to be done in teams of 2 people (your team: Elvin Allahverdiyev, Sakina Mammadzade)

Tasks

0. README, man, AUTHORS

mandatory

  • Write a README
  • Write a man for your shell.
  • You should have an AUTHORS file at the root of your repository, listing all individuals having contributed content to the repository. Format, see Docker

Repo:

  • GitHub repository: simple_shell
  • File: README.md, man_1_simple_shell, AUTHORS

1. Betty would be proud

mandatory

Write a beautiful code that passes the Betty checks

Repo:

  • GitHub repository: simple_shell

2. Simple shell 0.1

mandatory

Write a UNIX command line interpreter.

  • Usage: simple_shell

Your Shell should:

  • Display a prompt and wait for the user to type a command. A command line always ends with a new line.
  • The prompt is displayed again each time a command has been executed.
  • The command lines are simple, no semicolons, no pipes, no redirections or any other advanced features.
  • The command lines are made only of one word. No arguments will be passed to programs.
  • If an executable cannot be found, print an error message and display the prompt again.
  • Handle errors.
  • You have to handle the "end of file" condition (Ctrl+D)

You don't have to:

  • use the PATH
  • implement built-ins
  • handle special characters : ", ', ```, \, `*`, `&`, `#`
  • be able to move the cursor
  • handle commands with arguments
julien@ubuntu:~/shell$ ./shell
#cisfun$ ls
./shell: No such file or directory
#cisfun$ /bin/ls
barbie_j       env-main.c  exec.c  fork.c  pid.c  ppid.c    prompt   prompt.c  shell.c  stat.c         wait
env-environ.c  exec    fork    mypid   ppid   printenv  promptc  shell     stat test_scripting.sh  wait.c
#cisfun$ /bin/ls -l
./shell: No such file or directory
#cisfun$ ^[[D^[[D^[[D
./shell: No such file or directory
#cisfun$ ^[[C^[[C^[[C^[[C
./shell: No such file or directory
#cisfun$ exit
./shell: No such file or directory
#cisfun$ ^C
julien@ubuntu:~/shell$ echo "/bin/ls" | ./shell
#cisfun$ barbie_j       env-main.c  exec.c  fork.c  pid.c  ppid.c    prompt   prompt.c  shell.c stat.c         wait
env-environ.c  exec    fork    mypid   ppid   printenv  promptc  shell     stat test_scripting.sh  wait.c
#cisfun$ julien@ubuntu:~/shell$

Repo:

  • GitHub repository: simple_shell

3. Simple shell 0.2

mandatory

Simple shell 0.1 +

  • Handle command lines with arguments

Repo:

  • GitHub repository: simple_shell

4. Simple shell 0.3

mandatory

Simple shell 0.2 +

  • Handle the PATH
  • fork must not be called if the command doesn't exist
julien@ubuntu:~/shell$ ./shell_0.3
:) /bin/ls
barbie_j       env-main.c  exec.c  fork.c  pid.c  ppid.c    prompt   prompt.c  shell_0.3  stat    test_scripting.sh  wait.c
env-environ.c  exec    fork    mypid   ppid   printenv  promptc  shell     shell.c    stat.c  wait
:) ls
barbie_j       env-main.c  exec.c  fork.c  pid.c  ppid.c    prompt   prompt.c  shell_0.3  stat    test_scripting.sh  wait.c
env-environ.c  exec    fork    mypid   ppid   printenv  promptc  shell     shell.c    stat.c  wait
:) ls -l /tmp
total 20
-rw------- 1 julien julien    0 Dec  5 12:09 config-err-aAMZrR
drwx------ 3 root   root   4096 Dec  5 12:09 systemd-private-062a0eca7f2a44349733e78cb4abdff4-colord.service-V7DUzr
drwx------ 3 root   root   4096 Dec  5 12:09 systemd-private-062a0eca7f2a44349733e78cb4abdff4-rtkit-daemon.service-ANGvoV
drwx------ 3 root   root   4096 Dec  5 12:07 systemd-private-062a0eca7f2a44349733e78cb4abdff4-systemd-timesyncd.service-CdXUtH
-rw-rw-r-- 1 julien julien    0 Dec  5 12:09 unity_support_test.0
:) ^C
julien@ubuntu:~/shell$

Repo:

  • GitHub repository: simple_shell

5. Simple shell 0.4

mandatory

Simple shell 0.3 +

  • Implement the exit built-in, that exits the shell
  • Usage: exit
  • You don't have to handle any argument to the built-in exit

Repo:

  • GitHub repository: simple_shell

6. Simple shell 1.0

mandatory

Simple shell 0.4 +

  • Implement the env built-in, that prints the current environment
julien@ubuntu:~/shell$ ./simple_shell
$ env
USER=julien
LANGUAGE=en_US
SESSION=ubuntu
COMPIZ_CONFIG_PROFILE=ubuntu
SHLVL=1
HOME=/home/julien
C_IS=Fun_:)
DESKTOP_SESSION=ubuntu
LOGNAME=julien
TERM=xterm-256color
PATH=/home/julien/bin:/home/julien/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
DISPLAY=:0
$ exit
julien@ubuntu:~/shell$

Repo:

  • GitHub repository: simple_shell

7. What happens when you type ls -l *.c in the shell

mandatory

Write a blog post describing step by step what happens when you type ls -l *.c and hit Enter in a shell. Try to explain every step you know of, going in as much details as you can, give examples and draw diagrams when needed. You should merge your previous knowledge of the shell with the specifics of how it works under the hoods (including syscalls).

  • Have at least one picture, at the top of the blog post
  • Publish your blog post on Medium or LinkedIn
  • Share your blog post at least on LinkedIn
  • Only one blog post by team
  • The blog post must be done and published before the first deadline (it will be part of the manual review)
  • Please, remember that these blogs must be written in English to further your technical ability in a variety of settings