1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
|
%
% Copyright (C) 2003-2009 FAUmachine Team <info@faumachine.org>.
% This program is free software. You can redistribute it and/or modify it
% under the terms of the GNU General Public License, either version 2 of
% the License, or (at your option) any later version. See COPYING.
%
If things don't work, you can send us a bugreport. Some known caveats and
problems are listed in section \ref{s:bugs.caveats}.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{Creating Bugreports}
\label{s:bugs.bugreports}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
If things do not work, please let us know about it, so that we have a
chance to fix it! If you feel
confident that you can solve it, please go ahead, and don't forget to
include your fix in the bugreport!
In any case, please create a bugreport (simple text file) and mail it
to \bugsfaum. Please try to use the bugreport-script \binbugreport
provided. It will ask you about the things we need to know to have a
chance to reproduce the bug, find the cause and fix it.
A word of caution is appropriate here: \binbugreport is designed for
internal use with \command{cvs} and the full \package-sources, so it
might splutter some warnings, when used externally. These should not
worry you!
To create a bugreport use
\binbugreport, which will be installed along with \package.
To create a new bug do \command{\binbugreport --new --offline}. It
will ask you a few questions and then create a directory
\Filename{BUGREPORTS} in which it will put the bug-file.
The name of the bug-file is constructed out of the current time and your
username. The file is ASCII and you can edit it if
you like (try not to destroy the formatting, though). Send this file to
\bugsfaum.
If \binbugreport isn't for you
feel free to inform us about the bug anyway at \bugsfaum!
If you've downloaded the source-distribution, please use the appropriate
make targets to create bugreports.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{Caveats}
\label{s:bugs.caveats}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Finally a few caveats and known bugs.
\begin{itemize}
\item{
\package has not been tested/developed with
internationalization in mind. It has worked fine so far with "US
English" locales, keyboard layouts etc.
}
\item{
Syntax errors in configuration files are not tolerated. There
may not even be error messages, processes may simply terminate.
If something doesn't work, try using the \wizard (see section
\ref{s:configwizard}) to generate the config-files. That's what
the \wizard is there for!
}
\item{
If you find things, which you think should work on a virtual
Linux machine (because they
work on a real Linux machine), send in a bug report and we'll see what we can do.
}
\item{
If you don't know much about Linux, there are a few good books around.
Please do not ask us any general Linux questions.
To give an example, we consider questions like \asis{How do I
install an X-Server?}, \asis{What are boot parameters?} or
\asis{How should I partition my harddisk?} to be general Linux
questions. A starting point for finding answers to general Linux
questions is \ulink{http://www.linux.org}.
}
\end{itemize}
|
