Una shell con un comportamiento exactamente igual a la shell tradicional Bourne Shell. Para la construcción se tuvieron en cuenta conceptos como el flujo de una shell, que son los pid y ppid, cómo manejar procesos en linux, diferencias entre un syscall y una funcion, cómo manipular el entorno y trabajar con el PATH y por supuesto, el manejo cuidadoso de la memoria para evitar fugas.

stack

• C
• gcc new build
• Linux
• github repo

User guide

simple_shell project

Description In simple_shell project we code from zero our own custom printf function. Our shell must have the same behavior than sh shell in output and error. We had to learn about the workflow of a command line interpreter, what’s a pid and ppid, learn about manage processes, how to manipulate the environment of the current process, the difference between a function and system call, how to create processes, how to get PATH variables, execute commands with execve. And off course be carefull with memory leaks and write beautiful code with Betty style.

Usage First, you have to clone this repo $git clone https://github.com/davidgonzalezfx/simple_shell.git

Compile

gcc -Wall -Werror -Wextra -pedantic *.c -o executable_filename

Execute: see more in examples

Interactive mode:
$ ./hsh
./hsh$ [put_commands and_arguments]

Non-interactive mode
$ echo "[put_commands and_arguments]" | ./hsh

$ echo "/bin/pwd" | ./hsh
$ /home/davidgonzalezfx/simple_shell

$ ./hsh
./hsh$ /bin/echo hello world
helo world
./hsh$ exit
$

$ echo "pwd" | ./hsh
$ /home/davidgonzalezfx/simple_shell

$ ./hsh
./hsh$ echo hello world
helo world
./hsh$ exit
$

$ echo "exit" | ./hsh
$ echo $?
0

$ ./hsh
./hsh$ exit 98
$ echo $?
98

$ ./hsh
./hsh$ ls /non_existing_folder
ls: cannot access '/non_existing_folder': No such file or directory
./hsh$ exit
$ echo $?
2

$ echo "non_valid_command" | ./hsh
./hsh: 1: non_valid_command: not found
$ echo $?
127