meillo@8: \cleardoublepage
meillo@8: \chapter*{Preface}
meillo@8: \addcontentsline{toc}{chapter}{Preface}
meillo@8: 
meillo@8: \section*{Preface}
meillo@33: Lorem ipsum dolor sit amet, \cite{brooks95} consectetur\index{Daten} adipisicing elit
meillo@8: 
meillo@8: 
meillo@8: \section*{Organisation}
meillo@33: %FIXME: write about organisation of the book: parts, chapters, sections. And more thats useful to know.
meillo@33: %TODO: have this section after ``Audience''?
meillo@8: 
meillo@33: 
meillo@33: \section*{Audience}
meillo@33: This document is targeted for \masqmail\ users and for people interested in mail systems in general. Security problems in electronic mail, \unix\ and the \NAME{C} programming language will also be discussed. Additional ones planning to take over an unmaintained software project will find real life experience in here.
meillo@33: 
meillo@33: In each topic, basic knowledge is %FIXME: vorrausgesetzt
meillo@33: . Nevertheless introductions are given and sources for further reading will be mentioned.
meillo@33: 
meillo@33: This work focuses on the \unix\ operating system. Experience in usage, administration and program development is assumed. This includes the basic toolchain (e.g. \name{tar}, \name{grep}, etc.), user, file and permission management, as well as writing, compiling and installing programs written in the \NAME{C} language.
meillo@33: 
meillo@33: General information about \unix\ can be found in %FIXME: references
meillo@33: . %FIXME: references
meillo@33: explain about administrating \unix. And developing programs in \NAME{C} may be learned from %FIXME: references (``The C programming language'', ``The Unix programming environment'', ...)
meillo@33: .
meillo@33: 
meillo@33: %TODO: should I tell them to send email to me when having questions? Or somewhere else?
meillo@33: 
meillo@8: 
meillo@8: \section*{How to read this document}
meillo@33: %TODO: what to write here??
meillo@33: %TODO: include this in section ``Organisation''?
meillo@33: 
meillo@8: 
meillo@8: \section*{Conventions used in the book}
meillo@33: %TODO: check if this tells what is really used!
meillo@33: %FIXME: make it complete!
meillo@12: The following typographic conventions are used in this book:
meillo@12: 
meillo@12: \begin{tabular}{ p{0.15\textwidth} p{0.8\textwidth} }
meillo@12: \emph{Italic} &
meillo@12: is used for names, including command names, file name, hostnames, usernames and email addresses.
meillo@12: Further more it is used to emphasize text.
meillo@12: \\ &\\
meillo@12: 
meillo@12: \texttt{Constant Width} &
meillo@12: is used for source code, contents of files and output from programs.
meillo@12: \\ &\\
meillo@12: 
meillo@12: \texttt{\$} &
meillo@12: indicates the the user shell prompt.
meillo@12: \\ &\\
meillo@12: 
meillo@12: \texttt{\#} &
meillo@12: indicates the the root shell prompt.
meillo@12: \\
meillo@12: \end{tabular}
meillo@12: 
meillo@12: 
meillo@8: 
meillo@8: \section*{Regarded versions}
meillo@33: %FIXME: do I need this (here)?
meillo@33: 
meillo@8: 
meillo@8: \section*{Additional sources}
meillo@33: %FIXME: specify the really important external documents here
meillo@33: %TODO: write about the bundled CD, and tell what's included
meillo@33: \NAME{RFC}s, other books, source code, websites
meillo@8: 
meillo@33: 
meillo@8: \section*{Acknowledgements}
meillo@33: %FIXME: write this at the very end.
meillo@33: % dont forget: proove readers, suggestion makers, supporters, ...