docs/diploma
view thesis/tex/0-preface.tex @ 167:74151e26ba6a
this is the correct message for the last commit
I really hate it when I check in too early or too much by accident!
Maybe I should add a confirmation there to prevent me from doing stupid things.
But now what I checked in with the last commit:
- titlepage became the real titlepage, specifying all important info
- cover became the real cover to be the very first page
- the previous cover became pretitle, and moved between the other two
- my confirmation that I wrote the thesis on my own moved to the appendix
- the abstract and keywords moved to the back of the pretitle
- the copyright information extended
- the market share table is in a temporary state! (Needs verification!)
- some cleanups
Ten small commits instead of this huge one with an afterwards added message
are what I intended ... now I am in a bad mood because of this mess :-(
| author | meillo@marmaro.de |
|---|---|
| date | Fri, 19 Dec 2008 20:36:03 +0100 |
| parents | b5f141edee4e |
| children | 2181dc39ec06 |
line source
1 \cleardoublepage
2 \chapter*{Preface}
3 \addcontentsline{toc}{section}{Preface}
5 << preface text (about 1 page) >> %FIXME
7 goal: revive masqmail; make it future save; clean it up; add some missing features; release a new version
9 << write about the motivation to cover this topic: what is it I want? >> %FIXME
11 << preface == target of the book, related to the reader >> %FIXME
13 << make the topic more concrete and limit it >> %FIXME
15 << have text by oliver here? >> %TODO
19 Audience:
21 This document is targeted for \masqmail\ users and for people interested in mail systems in general.
22 Security problems in electronic mail, \unix\ and the C programming language will also be discussed.
23 Additional ones planning to take over an unmaintained software project will find real life experience in here.
25 In each topic, basic knowledge is preconditioned.
26 Nevertheless introductions are given and sources for further reading will be mentioned.
28 This work focuses on the \unix\ operating system.
29 Experience in usage, administration and program development is assumed.
30 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 C language.
32 General information about \unix\ can be found in \cite{unixprogenv} %FIXME: references
33 . %FIXME: references
34 explain about administrating \unix.
35 And developing programs in C may be learned from \cite{k&r} and \cite{advunixprog}. %FIXME: references
37 %TODO: should I tell them to send email to me when having questions? Or somewhere else?
40 \section*{Organisation}
42 << write about organisation of the book: parts, chapters, sections. And more thats useful to know. >> %FIXME
44 << explain where the main part lies (theory vs. implementation) >> %FIXME:
46 << write about the bundled CD, and tell what's included >> %TODO
49 \section*{Typographic conventions}
50 %TODO: check if this tells what is really used!
51 %FIXME: make it complete!
52 %FIXME: remove everything not needed. Maybe write only a few sentences text.
53 The following typographic conventions are used in this book:
55 \begin{tabular}{ p{0.15\textwidth} p{0.8\textwidth} }
56 \emph{Italic} &
57 is used for names, including command names, file name, hostnames, usernames and email addresses.
58 Further more it is used to emphasize text.
59 \\ &\\
61 \texttt{Constant Width} &
62 is used for source code, contents of files and output from programs.
63 \\ &\\
65 \texttt{\$} &
66 indicates the the user shell prompt.
67 \\ &\\
69 \texttt{\#} &
70 indicates the the root shell prompt.
71 \\
72 \end{tabular}
78 \section*{Acknowledgments}
79 %FIXME: write this at the very end.
80 % dont forget: proove readers, suggestion makers, supporters, ...
81 % FIXME: if too long, include a file on the CD and refer on it here