On Tue, 25 Aug 2015 10:47:35 +0200 Ancor Gonzalez Sosa <ancor@suse.de> wrote:

During the implementation of support for high and low memory in yast2-kdump[1], I found some AutoYaST things I'd like to understand better. I'm sending the questions to the list so we have an archive of the reply.

Chapter 1: workflow

Yast::Kdump.Write seems to have (pretty weird) code to support these two scenarios.

a) Mode.autoinst && Kdump.Read found a given param in current bootloadr b) Mode.autoinst && (Kdump.Read not called || Kdump.Read found nothing)

Since I was curious about the role of Read during autoinst, Imo ran autoinstall and autoupgrade processes for me and we examined the logs. We found no calls to Func=Read for the kdump_auto client, neither in autoinst or autoupgrade. Based on that I assume scenario (a) will never happen.

So the question: Is Read actually called during auto(inst/upgrade)? When?

Read is called if you generate autoyast profile either during installation or calling yast2 clone_system. ( schubi can correct me )

Chapter 2: autoinst profile

The kdump->crash_kernel used to be a single string and now it can support several values. We simply started to use it with config:type="list" as you can see at [2]. Adapting the Kdump code was really easy.

So the question: Do we need to adapt some DTD, validator, reference documentation or something similar to reflect that crash_kernel can now be a list?

you have to update https://github.com/yast/yast-kdump/blob/master/src/autoyast-rnc/kdump.rnc , just ensure old single value still works. I am missing third question ;) Josef

Cheers.

[1] https://bugzilla.suse.com/show_bug.cgi?id=882082 [2] https://github.com/imobach/autoyast-integration-test/blob/multi-crashkernel/...

-- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org