Custom Query (684 matches)
Results (19 - 21 of 684)
| Ticket | Owner | Reporter | Resolution | Summary |
|---|---|---|---|---|
| #111 | wontfix | -V option ignores Ctrl-C | ||
| Description |
Carol Anne Ogdin said: I decided to run mondoarchive -V to verify a set of DVDs I just created. Then I changed my mind. So, I tried Ctrl-C (which works elsewhere in mondoarchive). No effect. Short of rebooting, I just have to let it keep going, because simply closing the xterm window from which mondoarchive was launched still leaves something running. |
|||
| #131 | duplicate | Exclude /var/log/lastlog from mondoarchive ? | ||
| Description |
Hello, Despite it is explained in the FAQ (http://trac.mondorescue.org/wiki/FAQ Q16). I think it will be great to exclude this file for users without a lot of experience with Mondo / Linux. The best will be an option to include it if needed. Best regards. René |
|||
| #160 | fixed | kernel version reported in messages.txt may be inaccurate | ||
| Description |
a minor cosmetic issue. When I create a failsafe rescue disk using my older 2.6.16.27-0.6-smp kernel and modules, the booting rescue disk reports version number from message.txt of 2.6.18.8. This is not the failsafe version used. This version will appear on top of the first boot screen where you enter expert, compare, nuke or whatever. The kernel version reported at the top of that screen was the running kernel version 2.8.18 when the rescue disk was made. I think it should actually report 2.6.16 the version of the failsafe kernel and modules that the rescue disk finally boots to and uname -a will report, 2.6.16, later because I used those different kernel and modules as a failsafe kernel to create the rescue disk? |
|||
