~/hier(7)
en
NAME
hier - the filesystem, and who owns which part of it
SYNOPSIS
hier
DESCRIPTION
A small machine, and this is the shape of it. Only the parts worth walking into are here — enough that what you know about a Linux filesystem holds.
/- the root. Everything is somewhere under it.
/bin- one
sh, as on NixOS, where it is the only thing in/bin. /etc- the machine’s own configuration.
/etc/passwdsays who exists and where their home is, and is the answer to most questions about this shell./etc/shadowisroot’s, and refuses to be read, as it should. /home- home directories. There is one, and you are standing in it.
/home/tilen- what
~means here, and what the site is: every note Hugo rendered from the vault. It belongs totilen, so you may read all of it and write none of it — untilsusays otherwise.Not all of it, in fact: some of what
ls -aturns up is-rw-------— the shell history, the key in.ssh..planis the exception, world-readable because that is what a.planis for. Seeman su. /nix/store- where what nginx serves actually lives. The hash in the name is a stand-in — the real one changes with every build, and this page is one of the things being built.
/rootroot’s home, which you may see the name of and nothing else./srv- nothing, which is what NixOS keeps here.
/tmp- yours. It belongs to nobody (
drwxrwxrwt, sticky, as/tmphas always been), and it is the one place in this filesystem you may write. What lands there lives in your browser and nowhere else — seeman sh. /usr/share/man- the manual, as files.
ls /usr/share/man/man1is this manual, and each.1opens the page it is the source of. /var/log- the log, which needs a user you are not.
Where it stops
Nothing here is a real machine, and the places a real one would have that
this one does not — /dev, /proc, /sys — are simply absent rather than
faked: a directory you can enter and find empty would be a worse lie than one
that says it is not there.
EXAMPLES
ls /
cat /etc/passwd
ls -l /tmp