Relax & Recover (rear) F.A.Q.
Why don't you implement my feature wish ?
Because you did not send a patch. Patches are readily accepted, especially if you contact us beforehand about coding style and the best way to implement your desired feature.
The rear developers are not able to do much for rear in their personal free time. The little time we have is spent on dealing with patches and doing things that nobody wants to sponsor, e.g. the documentation and this website you are reading.
You might consider sponsoring the project to push your feature into active development. Please contact the developers for further details.
I need help, where can I turn to ?
First try to find a solution with the documentation or the bug tracker. Then you should subscribe to the mailing list rear-users and ask there. That way your problem (and the solution) will be documented for everybody in the mailing list archives (which you checked first, of course :-) ).
I added a hard disk and the rescue system does not 'see' it !
At the moment (rear 1.6) the rescue system does not pack udev but rather takes the existing device nodes from your host systems /dev directory. If the new device was not present at the creation of the rescue system, the device node will not be there on most recent Linux distros.
As a crude workaround you can use mknod to create the missing device nodes (don't forget the devices for the partitions you plan to create there).
My replacement hardware has different hard disks, recovery fails !
At the moment rear does not automatically adapt the recovery to changed hardware. This is, however, a planned feature still looking for contributors or sponsors !
As a very crude workaround you can try to patch and modify the files in /etc/rear/recovery (or /var/rear/recovery or /var/lib/rear/recovery for newer versions) to suit your new hardware layout. If you do it correctly, then recovery will work again. We would like to implement an automatism for this kind of modifications that guides the user through this possibly very difficult process.
My system is using DHCP but the rescue system just took the IP address as a static address instead of retrieving a new one via DHCP !
At the moment (rear 1.6) we do not support DHCP in the rescue system. The problem is that there is no generic and distribution independant method to determine which network interface was configured with DHCP (and with which DHCP client).
Please do submit a patch for this if you know the solution ! We do have plans to add support for specifying a manual setup command to setup the network connection instead of cloning the network configuration at the time of the rescue system creation.
