Ex01: Shell01

If you describe the exact requirement (e.g., "display a specific string", "create files with certain permissions", "use ls with particular options"), I can give you the precise solution.

However, Shell01 Ex01 often introduces a twist: files starting with a dot ( . ) are hidden in Linux. A standard ls command will not reveal them. The student must discover the -a (all) flag.

However, for Ex01, the evaluator will set the variable cleanly. This nested solution is overkill unless explicitly required. Shell01 Ex01

user@shell01-ex01:~$

You cannot hardcode student . You must use $FT_USER . If you describe the exact requirement (e

Shell01 Ex01 is not about writing a program. It is about knowing that the program already exists ( id or groups ), and your job is to glue it to the environment. Many students overthink this, writing 10-line bash scripts with loops and conditionals. The correct solution is (excluding the variable).

Some students encounter this: "I run echo $FT_USER , it prints my name, but id -Gn $FT_USER says 'no such user'." A standard ls command will not reveal them

echo "Groups: $(id -Gn $FT_USER)"

Place that in a file, chmod +x if needed, and submit. Then move on to Ex02, where you will face the infamous ls forbidden challenge.

There are no icons to click, no folders to drag. The user is forced to interact with the system through text commands alone.

If you describe the exact requirement (e.g., "display a specific string", "create files with certain permissions", "use ls with particular options"), I can give you the precise solution.

However, Shell01 Ex01 often introduces a twist: files starting with a dot ( . ) are hidden in Linux. A standard ls command will not reveal them. The student must discover the -a (all) flag.

However, for Ex01, the evaluator will set the variable cleanly. This nested solution is overkill unless explicitly required.

user@shell01-ex01:~$

You cannot hardcode student . You must use $FT_USER .

Shell01 Ex01 is not about writing a program. It is about knowing that the program already exists ( id or groups ), and your job is to glue it to the environment. Many students overthink this, writing 10-line bash scripts with loops and conditionals. The correct solution is (excluding the variable).

Some students encounter this: "I run echo $FT_USER , it prints my name, but id -Gn $FT_USER says 'no such user'."

echo "Groups: $(id -Gn $FT_USER)"

Place that in a file, chmod +x if needed, and submit. Then move on to Ex02, where you will face the infamous ls forbidden challenge.

There are no icons to click, no folders to drag. The user is forced to interact with the system through text commands alone.