docs/diploma

annotate thesis/tex/0-preface.tex @ 102:95ebdfe51a55

moved some old text about masqmail
author meillo@marmaro.de
date Wed, 19 Nov 2008 18:25:33 +0100
parents 1b7dba16c74a
children b5f141edee4e
rev   line source
meillo@8 1 \cleardoublepage
meillo@8 2 \chapter*{Preface}
meillo@98 3 \addcontentsline{toc}{section}{Preface}
meillo@8 4
meillo@101 5 << preface text (about 1 page) >> %FIXME
meillo@8 6
meillo@101 7 goal: revive masqmail; make it future save; clean it up; add some missing features; release a new version
meillo@101 8
meillo@101 9 << write about the motivation to cover this topic: what is it I want? >> %FIXME
meillo@101 10
meillo@101 11 << preface == target of the book, related to the reader >> %FIXME
meillo@101 12
meillo@101 13 << make the topic more concrete and limit it >> %FIXME
meillo@101 14
meillo@101 15 << have text by oliver here? >> %TODO
meillo@101 16
meillo@8 17
meillo@96 18
meillo@98 19 Audience:
meillo@96 20
meillo@47 21 This document is targeted for \masqmail\ users and for people interested in mail systems in general.
meillo@47 22 Security problems in electronic mail, \unix\ and the \NAME{C} programming language will also be discussed.
meillo@47 23 Additional ones planning to take over an unmaintained software project will find real life experience in here.
meillo@33 24
meillo@47 25 In each topic, basic knowledge is preconditioned.
meillo@47 26 Nevertheless introductions are given and sources for further reading will be mentioned.
meillo@33 27
meillo@47 28 This work focuses on the \unix\ operating system.
meillo@47 29 Experience in usage, administration and program development is assumed.
meillo@47 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 \NAME{C} language.
meillo@33 31
meillo@40 32 General information about \unix\ can be found in \cite{unixprogenv} %FIXME: references
meillo@33 33 . %FIXME: references
meillo@47 34 explain about administrating \unix.
meillo@55 35 And developing programs in \NAME{C} may be learned from \cite{k&r} and \cite{advunixprog}. %FIXME: references
meillo@33 36
meillo@33 37 %TODO: should I tell them to send email to me when having questions? Or somewhere else?
meillo@33 38
meillo@8 39
meillo@36 40 \section*{Organisation}
meillo@33 41
meillo@98 42 << write about organisation of the book: parts, chapters, sections. And more thats useful to know. >> %FIXME
meillo@8 43
meillo@98 44 << explain where the main part lies (theory vs. implementation) >> %FIXME:
meillo@33 45
meillo@98 46 << write about the bundled CD, and tell what's included >> %TODO
meillo@98 47
meillo@98 48
meillo@98 49 \section*{Acknowledgments}
meillo@33 50 %FIXME: write this at the very end.
meillo@33 51 % dont forget: proove readers, suggestion makers, supporters, ...
meillo@93 52 % FIXME: if too long, include a file on the CD and refer on it here