On 4/17/20 10:05 AM, Bernd Ritter wrote:
Hi there,
thanks something I can second. I've had some runs to get to use AutoYaST but if I remember correctly I was overwhelmed but the amount of XML that is necessary to make a plain install.
Yes, you have to write quite deep-structured XML file in order to define anything. It's basically because of two things 1. YaST in general uses a very special XML (Josef currently works on a project to simplify that if possible) 2. YaST has too many options to use. Of course, you can usually omit almost everything and use the defaults BTW, the really minimal AutoYaST profile contains just the root user/password. This is the only thing we can't guess (use the defaults).
It would be perfect to have a default installation that represents about the experience when installation through the graphical installer.
It must be already two years since I was trying to somehow push for a simple plain file describing the expected setup. Markdown, YAML, JSON ... anything like that could be used. There wasn't a need for that so far. What would be your use case? PLS share some info :)
Yet the GUI has always been faster than to get into AutoYaST and make a working config file.
Looks like we've failed to educate our users, there are really simple ways how to make it work with some tools we provide with AutoYaST. Thx Lukas -- Lukas Ocilka, Systems Management Team Leader & YaST Product Owner SLE Department, SUSE Linux 🌲 Please consider the environment before printing this e-mail ☂ Handle with care - Your reply can be stored in the cloud 😱 Pie-chart is just a representation of randomly chosen data ⚠ IMPORTANT: The contents of this email and any attachments are confidential. They are intended for the named recipient(s) only. If you have received this email by mistake, please, notify the sender immediately and do not disclose the contents to anyone or make copies of thereof. -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org