NetkitBugs

Sometimes (probably more often than it should) Netkit exhibits bugs. In this case, your collaboration becomes incredibly precious for making the system better. We therefore invite you to proceed as follows:

• Before filing a bug report, please consider again the suggestions that are found in the Netkit documentation and the FAQ area. Maybe what you have found is not really a bug, or a workaround already exists.
• Search for known bugs in the bug tracking system to check whether a bug report has already been filed or, even better, a patch is already available. Searching does not require logging into the bug tracker.
• Log in (or create an account on) the bug tracking system and file a bug report. For the report to be useful, you should include at least the following information:
  • Bug description (e.g., expected and actual behaviour).
  • One or more command lines that can be used to reproduce the bug.
  • Name of the offending command and Netkit version. You can get it by invoking a command with the option --version (e.g., vstart --version).
  • Output of the offending command (better if --verbose options are used when producing this report).
  • Name and release of the Linux distribution being used on the host machine (e.g., Debian, Ubuntu, Mandrake, Red Hat, Fedora, Gentoo, etc.).
  • Host kernel release and platform. You can get these information by using the uname -a command.
  • Description of any patch or changes applied to kernels (host and UML) and filesystems, if any.