docs/diploma

annotate thesis/tex/0-preface.tex @ 34:f789b659f094

added formating of names; cleanups
author meillo@marmaro.de
date Tue, 07 Oct 2008 15:40:52 +0200
parents fb9ba63f6957
children 42a2a3565b89
rev   line source
meillo@8 1 \cleardoublepage
meillo@8 2 \chapter*{Preface}
meillo@8 3 \addcontentsline{toc}{chapter}{Preface}
meillo@8 4
meillo@8 5 \section*{Preface}
meillo@33 6 Lorem ipsum dolor sit amet, \cite{brooks95} consectetur\index{Daten} adipisicing elit
meillo@8 7
meillo@8 8
meillo@8 9 \section*{Organisation}
meillo@33 10 %FIXME: write about organisation of the book: parts, chapters, sections. And more thats useful to know.
meillo@33 11 %TODO: have this section after ``Audience''?
meillo@8 12
meillo@33 13
meillo@33 14 \section*{Audience}
meillo@33 15 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 16
meillo@33 17 In each topic, basic knowledge is %FIXME: vorrausgesetzt
meillo@33 18 . Nevertheless introductions are given and sources for further reading will be mentioned.
meillo@33 19
meillo@33 20 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 21
meillo@33 22 General information about \unix\ can be found in %FIXME: references
meillo@33 23 . %FIXME: references
meillo@33 24 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 25 .
meillo@33 26
meillo@33 27 %TODO: should I tell them to send email to me when having questions? Or somewhere else?
meillo@33 28
meillo@8 29
meillo@8 30 \section*{How to read this document}
meillo@33 31 %TODO: what to write here??
meillo@33 32 %TODO: include this in section ``Organisation''?
meillo@33 33
meillo@8 34
meillo@8 35 \section*{Conventions used in the book}
meillo@33 36 %TODO: check if this tells what is really used!
meillo@33 37 %FIXME: make it complete!
meillo@12 38 The following typographic conventions are used in this book:
meillo@12 39
meillo@12 40 \begin{tabular}{ p{0.15\textwidth} p{0.8\textwidth} }
meillo@12 41 \emph{Italic} &
meillo@12 42 is used for names, including command names, file name, hostnames, usernames and email addresses.
meillo@12 43 Further more it is used to emphasize text.
meillo@12 44 \\ &\\
meillo@12 45
meillo@12 46 \texttt{Constant Width} &
meillo@12 47 is used for source code, contents of files and output from programs.
meillo@12 48 \\ &\\
meillo@12 49
meillo@12 50 \texttt{\$} &
meillo@12 51 indicates the the user shell prompt.
meillo@12 52 \\ &\\
meillo@12 53
meillo@12 54 \texttt{\#} &
meillo@12 55 indicates the the root shell prompt.
meillo@12 56 \\
meillo@12 57 \end{tabular}
meillo@12 58
meillo@12 59
meillo@8 60
meillo@8 61 \section*{Regarded versions}
meillo@33 62 %FIXME: do I need this (here)?
meillo@33 63
meillo@8 64
meillo@8 65 \section*{Additional sources}
meillo@33 66 %FIXME: specify the really important external documents here
meillo@33 67 %TODO: write about the bundled CD, and tell what's included
meillo@33 68 \NAME{RFC}s, other books, source code, websites
meillo@8 69
meillo@33 70
meillo@8 71 \section*{Acknowledgements}
meillo@33 72 %FIXME: write this at the very end.
meillo@33 73 % dont forget: proove readers, suggestion makers, supporters, ...