Permissions and users · Lesson 11 of 33 · 8 minutes

Group collaboration

Create a shared lab note and set group-oriented metadata.

Open the lab Course map

Mastery 0/3Run itExplain itApply it

learner@clairos:~ $

↑ history · Tab complete · Ctrl+C cancel · Esc, Tab to leaveExit 0

Your objectives

Hints are always available. Wrong turns never cost XP.

1
Create shared folder
Run mkdir -p lab/shared.
Hint & worked example
Create a directory. -p also creates missing parent directories and accepts an existing directory.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
mkdir -p lab/shared
```
Remember: Creating a folder does not change the current directory.
2
Create shared file
Run touch lab/shared/note.txt.
Hint & worked example
Create an empty file when absent, or update timestamps without truncating an existing file.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
touch lab/shared/note.txt
```
Remember: touch is not a way to empty a file that already has content.
3
Set group
Run chgrp learners lab/shared/note.txt.
Hint & worked example
Change the file group within the permissions of the acting user.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
chgrp learners lab/shared/note.txt
```
Remember: A group name alone does not grant access unless membership and mode bits agree.
4
Set shared mode
Run chmod 664 lab/shared/note.txt.
Hint & worked example
Change permissions using an octal mode or a symbolic adjustment. Each rwx bit belongs to owner, group, or other.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
chmod 664 lab/shared/note.txt
```
Remember: Do not use 777 as a blanket fix. Grant the smallest access needed.

Understand the pattern

Collaboration often depends on group write access.

mkdir: Create a directory. -p also creates missing parent directories and accepts an existing directory.
Creating a folder does not change the current directory.
touch: Create an empty file when absent, or update timestamps without truncating an existing file.
touch is not a way to empty a file that already has content.
chgrp: Change the file group within the permissions of the acting user.
A group name alone does not grant access unless membership and mode bits agree.
chmod: Change permissions using an octal mode or a symbolic adjustment. Each rwx bit belongs to owner, group, or other.
Do not use 777 as a blanket fix. Grant the smallest access needed.

Worked example and expected result

$ mkdir -p lab/shared

(no output; exit 0)

Exit status: 0. The command completed successfully in the training fixture.

$ touch lab/shared/note.txt

(no output; exit 0)

Exit status: 0. The command completed successfully in the training fixture.

$ chgrp learners lab/shared/note.txt

group learners set on /home/learner/lab/shared/note.txt

Exit status: 0. The command completed successfully in the training fixture.

$ chmod 664 lab/shared/note.txt

(no output; exit 0)

Exit status: 0. The command completed successfully in the training fixture.

Try a variation

Repeat this workflow in the sandbox with a different scratch filename. Keep the system fixtures unchanged and compare the observed output with your expectation before moving on.

Explain it

In “Group collaboration”, which interpretation is safe?A command appearing in history proves it completed successfully.A successful first check guarantees that every dependent service is healthy.touch is not a way to empty a file that already has content.

Apply it elsewhere

Before adapting the touch workflow from “Group collaboration” to another server, what should you do?Skip output inspection whenever the command is familiar.Confirm the current directory, target identity, permissions, and the installed command behavior first.Paste the training paths unchanged into production.

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Temporary directory concept Try an incident drill

Anonymous lesson and mastery progress lasts for this session. Sign in to keep synced lesson XP between sessions; mastery stays device-local. No speed bonus, lost lives, or hint penalties.

Keep learning

GNU Coreutils manual · GNU Bash manual