meillo@274: \clearpage
meillo@8: \chapter*{Preface}
meillo@98: \addcontentsline{toc}{section}{Preface}
meillo@8: 
meillo@101: << preface text (about 1 page) >> %FIXME
meillo@8: 
meillo@302: << \textbf{say what you want to say} >>
meillo@302: 
meillo@302: << the overall goal of the document >>
meillo@302: 
meillo@101: goal: revive masqmail; make it future save; clean it up; add some missing features; release a new version
meillo@101: 
meillo@101: << write about the motivation to cover this topic: what is it I want? >> %FIXME
meillo@101: 
meillo@101: << preface == target of the book, related to the reader >> %FIXME
meillo@101: 
meillo@101: << make the topic more concrete and limit it >> %FIXME
meillo@101: 
meillo@316: << have text by Oliver here? >> %TODO
meillo@101: 
meillo@277: usage examples:
meillo@8: 
meillo@277: debian popcon stats
meillo@96: 
meillo@277: << hikernet >>
meillo@277: 
meillo@277: 
meillo@277: \subsubsection*{Audience}
meillo@96: 
meillo@47: This document is targeted for \masqmail\ users and for people interested in mail systems in general.
meillo@136: Security problems in electronic mail, \unix\ and the C programming language will also be discussed.
meillo@47: Additional ones planning to take over an unmaintained software project will find real life experience in here.
meillo@33: 
meillo@47: In each topic, basic knowledge is preconditioned.
meillo@47: Nevertheless introductions are given and sources for further reading will be mentioned.
meillo@33: 
meillo@47: This work focuses on the \unix\ operating system.
meillo@47: Experience in usage, administration and program development is assumed.
meillo@316: This includes the basic tool chain (e.g.\ \name{tar}, \name{grep}, etc.), user, file and permission management, as well as writing, compiling and installing programs written in the C language.
meillo@33: 
meillo@210: General information about \unix\ can be found in \cite{kernighan84} %FIXME: references
meillo@33: . %FIXME: references
meillo@47: explain about administrating \unix.
meillo@210: And developing programs in C may be learned from \cite{k&r} and \cite{rochkind85}. %FIXME: references
meillo@33: 
meillo@33: 
meillo@8: 
meillo@316: \section*{Organization}
meillo@33: 
meillo@316: << write about organization of the book: parts, chapters, sections. And more that's useful to know. >> %FIXME
meillo@8: 
meillo@98: << explain where the main part lies (theory vs. implementation) >> %FIXME:
meillo@33: 
meillo@98: 
meillo@98: 
meillo@280: \section*{Conventions}
meillo@302: %TODO: check it!
meillo@280: The following typographic conventions are used in this thesis:
meillo@150: 
meillo@304: \begin{enumerate}
meillo@316: \item \emph{Italic shape} is used to emphasize text, to introduce new terms, and for names, including product, host, and user names, as well as email addresses.
meillo@150: 
meillo@304: \item For names of persons \textsc{Small Caps} are used.
meillo@304: 
meillo@316: \item File and path names, source code excerpts, contents of files, and output from programs are displayed in \texttt{Typewriter font}.
meillo@304: \end{enumerate}
meillo@150: 
meillo@302: References to external resources are marked using one of three styles, distinguished by the type of resource.
meillo@210: 
meillo@302: \begin{enumerate}
meillo@316: \item References to books, articles, and similar documents looks like this: \cite{kernighan84}. The letters represent the author(s) (here \person{Kernighan} and \person{Pike}), the number represents the year of publication (here 1984).
meillo@150: 
meillo@302: \item Websites differ from documents as they are less of a text written by some author but more a place where information is gathered. They are only indicated by numbers, like for example: \citeweb{masqmail:homepage}.
meillo@210: 
meillo@302: \item \name{Request for Comments}---documents that define Internet standards---are referenced in a third way, by specifying the unique number of the \RFC\ directly: \RFC821.
meillo@302: \end{enumerate}
meillo@234: 
meillo@302: The Bibliography is located at the end of the thesis. It also includes a list of the relevant \RFC{}s and how they can be retrieved.
meillo@150: 
meillo@150: 
meillo@150: 
meillo@150: 
meillo@150: 
meillo@98: \section*{Acknowledgments}
meillo@33: %FIXME: write this at the very end.
meillo@33: % dont forget: proove readers, suggestion makers, supporters, ...
meillo@302: % FIXME: if too long, think about a page in the appendix