\section{/sys}
\begin{frame}
   {/sys}

   \begin{itemize}
      \item Another pseudo-file system: not stored
      anywhere on disk
      \item Contains information about devices and drivers,
      kernel modules, system configuration
      structures
      \item Can be used to examine or modify system
      behavior and parameters
      \item Better controlled than \filelink{/proc}

   \end{itemize}

\end{frame}

\cprotect\note{

   This directory is the mount point for the
   \textbf{sysfs} \textbf{pseudo-filesystem} where all
   information resides only in memory, not on disk.
   Like \filelink{/dev} and \filelink{/proc}, the
   \filelink{/sys} directory is empty on a non-running
   system.

   \textbf{sysfs} is used to both gather information
   about the system, and modify its behavior while
   running.  In that sense it resembles
   \filelink{/proc}, but it is younger than and has
   adhered to strict standards about what kind of
   entries it can contain.  For example, almost all
   pseudo-files in \filelink{/sys} contain only one
   line, or value; there are none of the long entries
   you can find in \filelink{/proc}.

   As with \filelink{/proc}, we will examine entries in
   \filelink{/sys} throughout this course, and it will
   become relevant in upcoming chapters about kernel
   configuration and system monitoring.
   \begin{figure}[H]
      \includegraphics[width=4.0in]{IMAGES/lssys}
      \caption{/sys Directory}
   \end{figure}


}

