docs/diploma

annotate thesis/tex/0-preface.tex @ 55:56fd50f9bbf3

reworked text; added MTA definitions; added references; more
author meillo@marmaro.de
date Wed, 15 Oct 2008 22:54:56 +0200
parents d52fa2350137
children e050221efd38
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@42 6 %FIXME: write about the motivation to cover this topic
meillo@42 7 %TODO: eventually have some words of oliver here
meillo@8 8
meillo@8 9
meillo@33 10 \section*{Audience}
meillo@47 11 This document is targeted for \masqmail\ users and for people interested in mail systems in general.
meillo@47 12 Security problems in electronic mail, \unix\ and the \NAME{C} programming language will also be discussed.
meillo@47 13 Additional ones planning to take over an unmaintained software project will find real life experience in here.
meillo@33 14
meillo@47 15 In each topic, basic knowledge is preconditioned.
meillo@47 16 Nevertheless introductions are given and sources for further reading will be mentioned.
meillo@33 17
meillo@47 18 This work focuses on the \unix\ operating system.
meillo@47 19 Experience in usage, administration and program development is assumed.
meillo@47 20 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@40 22 General information about \unix\ can be found in \cite{unixprogenv} %FIXME: references
meillo@33 23 . %FIXME: references
meillo@47 24 explain about administrating \unix.
meillo@55 25 And developing programs in \NAME{C} may be learned from \cite{k&r} and \cite{advunixprog}. %FIXME: references
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@36 30 \section*{Organisation}
meillo@36 31 %FIXME: write about organisation of the book: parts, chapters, sections. And more thats useful to know.
meillo@36 32
meillo@36 33
meillo@8 34 \section*{How to read this document}
meillo@33 35 %TODO: what to write here??
meillo@33 36 %TODO: include this in section ``Organisation''?
meillo@33 37
meillo@8 38
meillo@36 39 \section*{Conventions used}
meillo@33 40 %TODO: check if this tells what is really used!
meillo@33 41 %FIXME: make it complete!
meillo@12 42 The following typographic conventions are used in this book:
meillo@12 43
meillo@12 44 \begin{tabular}{ p{0.15\textwidth} p{0.8\textwidth} }
meillo@12 45 \emph{Italic} &
meillo@12 46 is used for names, including command names, file name, hostnames, usernames and email addresses.
meillo@12 47 Further more it is used to emphasize text.
meillo@12 48 \\ &\\
meillo@12 49
meillo@12 50 \texttt{Constant Width} &
meillo@12 51 is used for source code, contents of files and output from programs.
meillo@12 52 \\ &\\
meillo@12 53
meillo@12 54 \texttt{\$} &
meillo@12 55 indicates the the user shell prompt.
meillo@12 56 \\ &\\
meillo@12 57
meillo@12 58 \texttt{\#} &
meillo@12 59 indicates the the root shell prompt.
meillo@12 60 \\
meillo@12 61 \end{tabular}
meillo@12 62
meillo@12 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, ...