From Netkit Wiki
Revision as of 16:35, 19 May 2011 by Admin (Talk | contribs)
(diff) ← Older revision | Current revision (diff) | Newer revision → (diff)
Jump to: navigation, search
Ok, so you would like a certain feature to appear in future releases of Netkit. Or, nastier, you have found a bug in Netkit.

As of May 2011, all wishes and complaints are tracked using Github's issue tracker (existing open bug reports have been migrated). Each Netkit component has its issue tracker:

* Netkit core issue tracker
* Netkit kernel issue tracker
* Netkit filesystem issue tracker

We invite you to proceed as follows:

  • Are you sure that feature does not already exist in Netkit? Are you sure that it is really a bug? Please browse again through the Netkit documentation and the FAQs: maybe the feature is there or a workaround already exists.
  • Search in the tracking system: feature requests or bug reports may already have been filed and patches may already exist.
  • Log in (or create an account on) the tracking system and file a feature request or bug report. When filing bug reports, please mark them with the red BUG label and include:
    • A description (e.g., expected and actual behaviour).
    • Command lines that can be used to reproduce the bug and their output (better if --verbose options are used when producing this report).
    • Netkit version. You can get it by invoking a command with the option --version (e.g., vstart --version).
    • Name and release of the Linux distribution being used on the host (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 applicable.
Personal tools