-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-11-06 06:02, Andrei Borzenkov wrote:
05.11.2015 21:36, Carlos E. R. пишет:
On 2015-11-05 19:27, Andrei Borzenkov wrote:
05.11.2015 21:02, Carlos E. R. пишет:
I never understood why it had to be created.
Well, I don't have download figures, but it is quite popular.
OK, I added to scores by downloading it yesterday :)
:-)
chroot to the installed system, do things.
If you chroot you do not use rescue system at all.
Except what is already in memory, I understand.
Or don't, and configure some things in the rescue system.
You can use the partitioner module, for example (I did).
Will it also configure main system (add/remove mount points in /etc/fstab, update /etc/crypttab etc)?
Good point. I guess not.
I installed packages on it, using zypper or rpm (I don't remember which).
Yes, zypper may be useful. Except how many users know about -R option? And it requires full mount tree to be reconstructed manually.
No, I meant install packages onto the rescue usb stick itself. Installing things onto the system being rescued is another possibility I haven't tried, but should work: it is what the install system does, I understand.
Kernel ... OK, that is valid argument.
The same tool set as the computer under repair. Some things requires similar tools and versions, but others are simply more familiar.
That's really too vague. The only truly unique tool is snapper - can you use snapper on rescue medium to manage your main system(s)?
I don't use btrfs, but I do use XFS repair tools. Yes, of course they work.
snapper in *rescue* to manage snapshots in *main* installation? OK, it has -r option so may be something can be done. But it does not explain, what - says "works only for some commands".
Did I say "only"? :-?
Are XFS repair tools something that is SUSE specific and is not present in other distributions?
You have to use xfs tools corresponding to your setup, or things may break. XFS is still under development, and they add things to the on disk format. I have seen the tools fail because they are either too old, or too new (both!). They may also be built with different options.
In fact, people on 13.2 had to use TW rescue image to repair breakage on 13.2 btrfs root filesystem, unrepairable because of bug on 13.2.
Any rescue media with newer kernels/btrfs tools would do.
Perhaps. But SUSE considers some btrfs features experimental and they may not be included on all rescue media. They have to match the feature set that we use, anyway.
So basically the advantage of this image are matching kernel version (but your last example shows that it is questionable advantage) and ability to manage packages using native tool.
I have used other rescue media, and the one made by openSUSE has been the best in most cases I had. The exception are specific tools, like for instance, clonezilla. Having an almost fully featured XFCE graphical environment is a plus. Of course I can work in text mode (some people I know will absolutely refuse to, though), but I like having a bunch of xterms to see things at a glance and copy-paste text. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlY8ee8ACgkQja8UbcUWM1z8BAEAi+VbkZzu2kyf0+HRNvsamMWm ydluOLkNNN3BCH++PvAA/jNCZ/d+7RxFFsn9wwJbCqZP/E7xYZsFUvkmDF1cdfDm =fT17 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org