| 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@33
|
11 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
|
12
|
|
meillo@40
|
13 In each topic, basic knowledge is preconditioned. Nevertheless introductions are given and sources for further reading will be mentioned.
|
|
meillo@33
|
14
|
|
meillo@33
|
15 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
|
16
|
|
meillo@40
|
17 General information about \unix\ can be found in \cite{unixprogenv} %FIXME: references
|
|
meillo@33
|
18 . %FIXME: references
|
|
meillo@40
|
19 explain about administrating \unix. And developing programs in \NAME{C} may be learned from \cite{cprog} and \cite{advunixprog}. %FIXME: references
|
|
meillo@33
|
20
|
|
meillo@33
|
21 %TODO: should I tell them to send email to me when having questions? Or somewhere else?
|
|
meillo@33
|
22
|
|
meillo@8
|
23
|
|
meillo@36
|
24 \section*{Organisation}
|
|
meillo@36
|
25 %FIXME: write about organisation of the book: parts, chapters, sections. And more thats useful to know.
|
|
meillo@36
|
26
|
|
meillo@36
|
27
|
|
meillo@8
|
28 \section*{How to read this document}
|
|
meillo@33
|
29 %TODO: what to write here??
|
|
meillo@33
|
30 %TODO: include this in section ``Organisation''?
|
|
meillo@33
|
31
|
|
meillo@8
|
32
|
|
meillo@36
|
33 \section*{Conventions used}
|
|
meillo@33
|
34 %TODO: check if this tells what is really used!
|
|
meillo@33
|
35 %FIXME: make it complete!
|
|
meillo@12
|
36 The following typographic conventions are used in this book:
|
|
meillo@12
|
37
|
|
meillo@12
|
38 \begin{tabular}{ p{0.15\textwidth} p{0.8\textwidth} }
|
|
meillo@12
|
39 \emph{Italic} &
|
|
meillo@12
|
40 is used for names, including command names, file name, hostnames, usernames and email addresses.
|
|
meillo@12
|
41 Further more it is used to emphasize text.
|
|
meillo@12
|
42 \\ &\\
|
|
meillo@12
|
43
|
|
meillo@12
|
44 \texttt{Constant Width} &
|
|
meillo@12
|
45 is used for source code, contents of files and output from programs.
|
|
meillo@12
|
46 \\ &\\
|
|
meillo@12
|
47
|
|
meillo@12
|
48 \texttt{\$} &
|
|
meillo@12
|
49 indicates the the user shell prompt.
|
|
meillo@12
|
50 \\ &\\
|
|
meillo@12
|
51
|
|
meillo@12
|
52 \texttt{\#} &
|
|
meillo@12
|
53 indicates the the root shell prompt.
|
|
meillo@12
|
54 \\
|
|
meillo@12
|
55 \end{tabular}
|
|
meillo@12
|
56
|
|
meillo@12
|
57
|
|
meillo@8
|
58
|
|
meillo@8
|
59 \section*{Additional sources}
|
|
meillo@33
|
60 %FIXME: specify the really important external documents here
|
|
meillo@33
|
61 %TODO: write about the bundled CD, and tell what's included
|
|
meillo@33
|
62 \NAME{RFC}s, other books, source code, websites
|
|
meillo@8
|
63
|
|
meillo@33
|
64
|
|
meillo@8
|
65 \section*{Acknowledgements}
|
|
meillo@33
|
66 %FIXME: write this at the very end.
|
|
meillo@33
|
67 % dont forget: proove readers, suggestion makers, supporters, ...
|
