El lun, 04-05-2020 a las 11:56 +0200, Vojtěch Zeisek escribió:
Dne pondělí 4. května 2020 9:27:36 CEST, Ancor Gonzalez Sosa napsal(a):
On 5/2/20 11:14 AM, Vojtěch Zeisek wrote:
Dne pátek 17. dubna 2020 9:10:52 CEST, Imobach González Sosa napsal(a):
[...] it's probably out of purpose of AutoYaST, but I wonder if it could be usable as kind of backup and restore of configuration. E.g. if there could be some automated way to create profile describing actual configuration (what is installed and how everything is set up). Something like that.
Isn't that one of the main use cases of Machinery?
I wasn't aware of this, thank You. And after reading its homepage such use isn't obvious for me... Then I also wonder about difference/overlap among these two tools.
Hi, They are not related at all and, to be honest, there is some confusion about what AutoYaST really is. I like to see AutoYaST as a 'YaST driver': it takes a XML based description (an AutoYaST profile) and installs (or even configures) the system using YaST. Everything which is not supported by YaST is not supported by AutoYaST. On the other hand, the purpose of Machinery (if I got it right) is to analyze a system and build a system description (services, configuration, etc.). And that description can be used by other tools. Actually, Machinery is able export the description to an AutoYaST profile[1]. However, not all information found by Machinery would have an AutoYaST counterpart. Regards, Imo [1] http://machinery-project.org/docs/machinery-export-autoyast.1/ -- Imobach González Sosa YaST Team at SUSE LLC https://imobachgs.github.io/