https://bugzilla.novell.com/show_bug.cgi?id=825473 https://bugzilla.novell.com/show_bug.cgi?id=825473#c1 Felix Miata changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mrmazda@earthlink.net --- Comment #1 from Felix Miata 2014-04-12 21:44:27 EDT --- What's iexplicable to me is that when doing network installation with network configuration on cmdline, network gets correctly configured according to the cmdline content, whereas with the same installation cmdline except for the source being an iso provided on the HD instead of e.g. HTTP, the cmdline network configuration is apparently discarded. It seems to me to make sense to always use any valid network configuration information present on installation cmdline to configure the network regardless of the installation source or absence or presence of autoyast. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=825473 https://bugzilla.novell.com/show_bug.cgi?id=825473#c3 Felix Miata changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|mrmazda@earthlink.net | --- Comment #3 from Felix Miata 2014-04-14 13:52:16 EDT --- (In reply to comment #2)

You mean he hostip option should trigger network setup?

Why not? Except for hostname, it apparently already does when the installation source is HTTP, so why not always? Maybe not "always", as if hostip were the only networking parameter on cmdline, but when present in conjunction with others sufficient that YaST doesn't need to probe or ask for others to be able to create a working configuration. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.