CHROOT
CHROOT
!! Hints below if you get stuck or don't know where to start. !!
This game is played kind of like a capture the flag or an escape room. Explore the file system to learn information to make progress.
Controls
| Key | Action |
|---|---|
| Enter | submit command |
| Tab | autocomplete/show auto complete options |
| Arrow Up/Down | navigate command in history |
| Arrow Left/Right | move text cursor |
| Page Up/Down | scroll terminal history |
| F1 | toggle mute |
| F2 | toggle text distortion (changes |
Commands
paths accept relative paths (like "folder1/folder2") and absolute paths (like "/home/user")
| Command | Description |
|---|---|
| ls [<path>] | list files and folders in directory, path* is optional. |
| cd <path> | changes the directory to the path*. |
| cat <path to file> | prints the contents of the file |
| echo "string" | prints the string to the console |
| echo "string" > <path to file> | prints the string to the file |
| grep <search string> | filters output from another command |
| cat <path to file> | grep <search string> | filters the output of the file |
| ip link show [<adapter>] | lists network adapter information, like the adapter name, the ip address, and the mac address of the adapter |
| netstat | show process running that are connected to a port. Lists the port, the ip, and process id and name. |
| decode <encoded string> | decodes an encoded string. encoded strings typically appear with "==" at the end |
| su <username> <password> | logs in as the user |
| run <script file> | runs the script file |
| chroot <process id> <path> | isolates a process to a folder |
Hints
This section is meant to be used only if you are stuck and you think you've run out of options. All information can be inferred within the game but perhaps you need a nudge. Go down the list until one of them helps you, each hint is in the order they should be helpful.
hint 1
Read the notice in /etchint 2
check terminal sessionshint 3
the /home directory has folders for users with their usernameshint 4
a_gile doesn't read noticeshint 5
suhint 6
a_gile wasn't successfulhint 7
a_gile holds information that is not theirshint 8
you can decode the informationhint 9
b_tables knows what he's doinghint 10
don't just copy the logs, follow the leaderhint 11
How old is that terminal log anyways?hint 12
Run the commands from the terminal log and see the new outputhint 13
cross reference your dataEaster Egg
What term is E Evans known for?NOTE: This game is a pure work of fiction. Logs, commands, outputs, etc are essentially techno-babble, but are loosely rooted in Linux commands. This is not a real terminal, just a representation of one. Whether or not you know the terminal commands, you should check the help commands to see how they work.
You can find the source code of the game here. Note there is no License, so I am retaining the rights to my code. Feel free to learn from it and adapt bits and pieces how you like, but you are not allowed to copy it in sizeable chunks.
| Status | In development |
| Platforms | HTML5 |
| Author | Ninkolas |
| Genre | Puzzle |
| Average session | About a half-hour |
| Languages | English |
| Inputs | Keyboard |
| Content | No generative AI was used |






Leave a comment
Log in with itch.io to leave a comment.