Hey Lukas, thanks for you reply! To be honest my last attempt on the documentation has been a few years ago, so maybe my lookout on this is quite dated.
At work I proposed to use a linux based "embedded" system as a replacement for our former rtos realtime embedded system. These boxes are used to communicate with large truck scales. Naturally I chose opensuse as operating system of choice. And because we (mostly scale technicians not IT personnel) will install hundreds of these boxes over a very long timespan, I remembered AutoYaST and wanted it to give it a try (again). So our current planning includes: * initial base setup of storage (one disk and some flash drives), com port settings, usb settings, users, services and directory structures with AutoYaST. * After that we want to do customer specific customizations with Ansible (as it does not require a server opposed to salt). I will dig deeper into the documentation and get back to you if there is something unclear to me. Would be happy to help improve documentation there. Cheers and a nice weekend, Bernd On 17.04.20 13:44, Lukas Ocilka wrote: > 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 > -- To unsubscribe, e-mail: yast-devel+unsubscr...@opensuse.org To contact the owner, e-mail: yast-devel+ow...@opensuse.org
