docs/diploma

annotate thesis/tex/0-preface.tex @ 95:e83eada077fd

I decided to have no dedication, only the quote
author meillo@marmaro.de
date Sun, 16 Nov 2008 15:29:30 +0100
parents e050221efd38
children 8db526d7a678
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@93 6 %FIXME: write about the motivation to cover this topic: what is it I want?
meillo@93 7 % preface == target of the book, related to the reader
meillo@93 8 % make the topic more concrete and limit it
meillo@92 9 %TODO: have text by oliver here?
meillo@8 10
meillo@8 11
meillo@33 12 \section*{Audience}
meillo@93 13 %TODO: maybe merge mit the intention of the document
meillo@47 14 This document is targeted for \masqmail\ users and for people interested in mail systems in general.
meillo@47 15 Security problems in electronic mail, \unix\ and the \NAME{C} programming language will also be discussed.
meillo@47 16 Additional ones planning to take over an unmaintained software project will find real life experience in here.
meillo@33 17
meillo@47 18 In each topic, basic knowledge is preconditioned.
meillo@47 19 Nevertheless introductions are given and sources for further reading will be mentioned.
meillo@33 20
meillo@47 21 This work focuses on the \unix\ operating system.
meillo@47 22 Experience in usage, administration and program development is assumed.
meillo@47 23 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 24
meillo@40 25 General information about \unix\ can be found in \cite{unixprogenv} %FIXME: references
meillo@33 26 . %FIXME: references
meillo@47 27 explain about administrating \unix.
meillo@55 28 And developing programs in \NAME{C} may be learned from \cite{k&r} and \cite{advunixprog}. %FIXME: references
meillo@33 29
meillo@33 30 %TODO: should I tell them to send email to me when having questions? Or somewhere else?
meillo@33 31
meillo@8 32
meillo@36 33 \section*{Organisation}
meillo@36 34 %FIXME: write about organisation of the book: parts, chapters, sections. And more thats useful to know.
meillo@93 35 %FIXME: explain where the main part lies (theory vs. implementation)
meillo@33 36
meillo@8 37
meillo@36 38 \section*{Conventions used}
meillo@33 39 %TODO: check if this tells what is really used!
meillo@33 40 %FIXME: make it complete!
meillo@93 41 %FIXME: remove everything not needed. Maybe write only a few sentences text.
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, ...
meillo@93 74 % FIXME: if too long, include a file on the CD and refer on it here