Version 27 (modified by Bruno Cornec, 18 years ago) ( diff )


Welcome to Mondo Rescue devel pages

As all Wiki pages, this page is editable, which means that you can modify the contents of this page simply by using your web-browser, as long as you're registered. Simply click on the "Edit this page" link at the bottom of the page. To Register click on the "register" link at the top right of this page. WikiFormatting will give you a detailed description of available Wiki formatting commands.

The Mondo Rescue Dev Team

Starting Points

This knowledge base contains information that is still too much in flux or immature to be put into the proper documentation. Some like the Roadmap will (hopefully!) always be that way.


Boot Process Unraveled

Distribution Packaging


Standards Compliance



Using Virtualisation Tools With Mondorescue

Customer Experience and Feedbacks With Mondorescue

TroubleShooting Mondorescue

Ideas for

FTP Setup

The repository on the ftp server is organized in the following way:

|---- src (contains the .tar.gz files required for the mondorescue project)
|---- distro-a
|      |
|      |---- 1.0 (contains all packages made for that release of distro-a)
|      |---- 2.0
|---- distro-b
       |---- 1.1 (contains all packages made for that release of distro-b)
       |---- 2.3

Development hints

There are 2 mondorescue versions managed under SVN.

The first one is called 'stable'. From it we derive the official mondorescue releases. Currently the latest official releases are 2.0.9 for mondo & 1.0.9 for mindi in r762. Old 2.0x names are there for historical reasons. The published releases now use the classical schema:

x.y.z with

x for major versions and rewrite of the code. y for minor versions (even numbers for stable ones, and odd numbers for unstable ones) z for incremental releases inside a minor version.

The second one is called 'trunk' and is currently dedicated to a rewrite of the memory management in mondorescue, including first the removal of sprintf/strcat/strcpy functions in the code. It's NOT stable. It may even NOT compile. Once it is, it will probably lead to a 3.0.x version.

Development evolution is shown by this diagram:

trunk  ------------------------------------------------------>>>
            |            |           |
          3.0.0        3.0.1      3.0.2
          r10xx         r11xx       r12xx ........
            |            |           |
            \_______>>   \_______>>  \________________
stable -----------------------------------------------|------>>>
            |            |           |                |
          2.06         2.0.7      2.0.8            2.0.n
          r266         r5xx       r6xx ........    r5xx
            |            |           |                |
            \_______>>   \_______>>  \_______>>       \_______>>

So patches on the stable version should be produced against the stable version and then ported back to trunk using svn merge. Conflicts have to be expected and resolved due to the massive rewrite of code for memory management.

Do not use version 2.10/1.10 of mondo and mindi of the official site as they are broken and not maintained at the moment. Not sure they will be one day either :-). Be conservative and either use the latest cvs versions of the official site or, better, the published 2.0.9/1.0.9 versions of this site at


If you have any ideas on what needs to be done, please use the enhancement feature of our Trac system... For improvements around ntfsclone look at


Andree's Stuff - mixed bag of things I'm just jotting down for now...

BrunoSandBox - same for me :-)

For a complete list of local wiki pages, see TitleIndex.

Note: See TracWiki for help on using the wiki.