On 2016-12-31 19:33, nicholas wrote:
Well, I find that procedure too complex. One of the reasons I refuse to use btrfs. too complex for a low occurence event?, compared to what in the rest of linux ecosystem?
Compared to what one needs to do on, say, ext4, xfs, or reiserfs for recovery.
The OP mentions having to use a Debian live image instead. see comment regarding argon and krypton.
I saw them. No mention of a rescue image on https://software.opensuse.org/ Not found here: https://software.opensuse.org/search?utf8=%E2%9C%93&q=argon&search_devel=false&search_unsupported=false&baseproject=openSUSE%3ALeap%3A42.2 Hard to find: https://en.opensuse.org/Special:Search --> https://en.opensuse.org/Derivatives Packages built for KDE Git using stable and tested openSUSE technologies to track the latest development state of KDE software. Argon is a live installable image based on openSUSE Leap and Krypton is a live installable image based on openSUSE Tumbleweed. A KDE image... to track the latest development state. Hardly what I expect of a rescue image: tools like gparted, yast, mc, rsync, backup/restore tools, etc. And all those tools for filesystem work. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)