\section{One Big Filesystem}
\begin{frame}
   {One Big Filesystem}
   \begin{itemize}
      \item
      Seen as one big filesystem
      \item
      Inverted tree with \file {/} root directory at the top
      \item
      Additional partitions and filesystems can be
      \textbf{mounted} on subdirectories
      \item
      Standardized prescriptions followed by \textbf{Linux}
      distributions about what goes where
   \end{itemize}

\end{frame}

\cprotect\note{

   \textbf{Linux}, like all \textbf{UNIX}-based operating
   systems, consists of one big filesystem tree. Actually, it
   is usually diagrammed as an inverted tree with the root
   directory, \verb?/?, being at the top of the tree.

   Within this one large logical filesystem there may be more
   than one, even many, distinct filesystems, \textbf{mounted} at
   various points, which appear as subdirectories. These
   distinct filesystems are usually on different partitions,
   which can be on any number of devices, including those which
   are on a network.

   Regardless of exactly how things are joined together, it all
   just looks like one big filesystem; applications do not
   usually care at all about what physical device files
   actually reside on.

   Once upon a time, different \textbf{UNIX}-like operating
   systems organized this one big tree in varying ways; even
   among the various \textbf{Linux} distributions there were many
   differences. This made both writing applications and
   accomplishing system administration tasks on more than one
   kind of system difficult and often frustrating.

   As a consequence, the \textbf{Linux} ecosystem has worked
   hard to establish standardized procedures to minimize such
   pain.

}
