Re: State of Autoyast for OpenSUSE 13.1
Ivan De Masi <[email protected]> Thu, 30 Jan 2014 15:46:15 +0100
| Newsgroups | gmane.linux.suse.autoinstall |
|---|---|
| Organization | AStA TU Darmstadt |
| Message-ID | <[email protected]> |
Am 30.01.2014 12:18, schrieb Thomas Fehr: > Hi Ivan, > Hello Thomas, > On Thu, Jan 30, Ivan De Masi wrote: > >> wouldn't a independant autoyast-repository make sense for quicker fixing >> and updating?! >> >> A OS 13.1 rollout of clients and servers with these bugs in autoyast is >> hard to do, when you always have to be aware if the tool that should >> help and ease a roolout needs "help" too. ;-) > > The fix for this needs to be in installation media, so having the fixed > package in a repository where it gets installed from would not help to > avoid this bug. OK, thanks for this explanation. I was wondering for a while... > > As I already wrote in my answer to Joschi, there is a driver update disk > attached to https://bugzilla.novell.com/show_bug.cgi?id=846011 which > avoids the problem. > > you just need to use e.g. > > netsetup=dhcp autoyast=http://10.120.4.28/autoinst.xml dud=http://10.120.4.28/bnc_846011_131.dud > > as kernel boot commandline (of course with URLs adapted ;-) and place the > DUD where you get the autoyast control file from. Since I assume, most of > you have means to avoid typing the parameters manually (e.g. PXE boot, > modified isolinux.cfg on install medium, whatever) it ist just a one-time > change in setup that can be used for all 13.1 based installations. Also thanks for this! I will try it (hopefully soon) and report. Regards, Ivan -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]