docs/diploma
changeset 40:81ff8b093efe
fixed some FIXMEs; added some cites; stuff
author | meillo@marmaro.de |
---|---|
date | Mon, 13 Oct 2008 15:43:40 +0200 |
parents | e69780171a53 |
children | 44000e96af30 |
files | thesis/tex/0-preface.tex thesis/tex/1-Candidates.tex |
diffstat | 2 files changed, 8 insertions(+), 11 deletions(-) [+] |
line diff
1.1 --- a/thesis/tex/0-preface.tex Mon Oct 13 15:42:36 2008 +0200 1.2 +++ b/thesis/tex/0-preface.tex Mon Oct 13 15:43:40 2008 +0200 1.3 @@ -9,15 +9,13 @@ 1.4 \section*{Audience} 1.5 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. 1.6 1.7 -In each topic, basic knowledge is %FIXME: vorrausgesetzt 1.8 -. Nevertheless introductions are given and sources for further reading will be mentioned. 1.9 +In each topic, basic knowledge is preconditioned. Nevertheless introductions are given and sources for further reading will be mentioned. 1.10 1.11 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. 1.12 1.13 -General information about \unix\ can be found in %FIXME: references 1.14 +General information about \unix\ can be found in \cite{unixprogenv} %FIXME: references 1.15 . %FIXME: references 1.16 -explain about administrating \unix. And developing programs in \NAME{C} may be learned from %FIXME: references (``The C programming language'', ``The Unix programming environment'', ...) 1.17 -. 1.18 +explain about administrating \unix. And developing programs in \NAME{C} may be learned from \cite{cprog} and \cite{advunixprog}. %FIXME: references 1.19 1.20 %TODO: should I tell them to send email to me when having questions? Or somewhere else? 1.21
2.1 --- a/thesis/tex/1-Candidates.tex Mon Oct 13 15:42:36 2008 +0200 2.2 +++ b/thesis/tex/1-Candidates.tex Mon Oct 13 15:43:40 2008 +0200 2.3 @@ -1,7 +1,6 @@ 2.4 \chapter{\unix\ \MTA{}s} 2.5 2.6 -This chapter introduces a group of \mta{}s. These will be presented to the reader in some kind of \emph{Curriculum Vitae}. %FIXME: check spelling 2.7 -The next chapter will show a comparision of the candidates in several disciplines. 2.8 +This chapter introduces a group of \mta{}s. These will be presented to the reader in a short overview and with the most important facts. The next chapter will show a comparison of the candidates in several disciplines. 2.9 2.10 2.11 \section{Types of \MTA{}s} 2.12 @@ -13,11 +12,11 @@ 2.13 \section{The ones not regarded here} 2.14 The candidates for the competition in the next chapter are a subset of the \MTA{}s available. Comparision between totally different programs (apart of one function) makes not much sense. One would not use a program for a job it is not suited for. Therefor \mta{}s that are rarely similar to \masqmail\ are not regarded. 2.15 2.16 -The first group of programs to sort out are the so called \name{groupware} programs. These provide a whole lot of functions, including mail transfer, file storage, calendars, resource management, instant messaging and more. %FIXME: check 2.17 -Examples for this kind of programs are: \name{Microsoft Exchange}, %FIXME: add more 2.18 +The first group of programs to sort out are the so called \name{groupware} programs. These provide a whole lot of functions, including mail transfer, file storage, calendars, resource management, instant messaging and more. 2.19 +Examples for this kind of programs are: \name{Lotus Notes}, \name{Microsoft Exchange}, \name{OpenGroupware.org} and \name{eGroupWare}. 2.20 2.21 -The second group are the \name{relay-only} \MTA{}s. %FIXME: ``dumb'' ? 2.22 -They transfer mail only to a defined ``smart'' mail server, which handles all further processing. Most \MTA{}s can be configured to act as such a forwarder, but as additional functionality. 2.23 +The second group are the \name{relay-only} \MTA{}s. 2.24 +They transfer mail only to defined \name{smart hosts}\index{smart host}\footnote{MTAs that receives email and route it to the actual destination}. Most \MTA{}s can be configured to act as such a forwarder. But this is normally an additional functionality. 2.25 Examples for that group are: \name{nullmailer}, \name{ssmtp} and \name{esmtp}. 2.26 2.27 Third, only \emph{sendmail-compatible} \MTA{}s will be regarded in the competition. The ones not \emph{sendmail-compatible} are not from big interest on \unix\ systems. %FIXME: write it the other way round: the group sorted out.