Re: [opensuse-autoinstall] Network interface configuration and systemd's predictable network interface names
Damn you, gmail android app. Again for the list. ---------- Forwarded message ---------- From: Christopher 'm4z' Holm […] Date: Thu, Feb 6, 2014 at 9:29 AM Subject: Re: [opensuse-autoinstall] Network interface configuration and systemd's predictable network interface names To: Joschi Brauchle <joschi.brauchle@tum.de> Cc: opensuse-autoinstall@opensuse.org On Jan 28, 2014 6:52 PM, "Joschi Brauchle" <joschi.brauchle@tum.de> wrote:
Hi, I am having the same problem.
Could anyone post an XML snipped on how to provide these options to the kernel for the installation system and with autoyast to the installed system?
(Mobile right now, all from the top of my head.) For the installation, you need to get the boot parameters ("biosdevname=0 net.ifnames=0") on the kernel commandline (either manually or by baking a custom image) or use the alternative ways for each (which I don't know by heart, IIRC for PNIN you have to remove or create some udev file, should be explained in the URL of my earlier message; CNDN was somewhat similar IIRC). For the installed system, if you choose to use the boot parameters, you need to get them into grub.cfg: - in 13.1 by patching /etc/default/grub for future kernels and /boot/grub2(?)/grub.cfg for the current kernel, or run "grub2-mkconfig -o /boot/grub2(?)/grub.cfg"[0] for the latter after you've patched /etc/default/grub; - for 12.3 I don't remember if the former or the following instructions will work; - for previous oS releases use /etc/sysconfig/bootloader instead of /etc/default/grub). 0: Although this alternative might not work; I haven't yet figured out how exactly GRUB config creation works, IIRC /etc/default/grub or /etc/sysconfig/bootloader contains a comment to the effect of something like "If there are custom parameters in grub.cfg, they will be taken from there (or merged with those in /etc/default/grub), else they will be taken from /etc/default/grub." For the custom image for stage1 I can give you a crude script. For the installed system (stage 2 and later), I'm still working on the 13.1 (and maybe 12.3, too) variant. -- I'm unsure whether this is what you asked for, but nobody else answered. (; Christopher 'm4z' Holm / 686f6c6d "Faith is what you have in things that don't exist." --Homer Simpson -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner@opensuse.org
On Thu, Feb 6, 2014 at 11:40 AM, 686f6c6d <686f6c6d@googlemail.com> wrote:
For the installed system, if you choose to use the boot parameters, you need to get them into grub.cfg: - in 13.1 by patching /etc/default/grub for future kernels and /boot/grub2(?)/grub.cfg for the current kernel, or run "grub2-mkconfig -o /boot/grub2(?)/grub.cfg"[0] for the latter after you've patched /etc/default/grub; - for 12.3 I don't remember if the former or the following instructions will work; - for previous oS releases use /etc/sysconfig/bootloader instead of /etc/default/grub).
0: Although this alternative might not work; I haven't yet figured out how exactly GRUB config creation works, IIRC /etc/default/grub or /etc/sysconfig/bootloader contains a comment to the effect of something like "If there are custom parameters in grub.cfg, they will be taken from there (or merged with those in /etc/default/grub), else they will be taken from /etc/default/grub."
Clarified here: https://bugzilla.novell.com/show_bug.cgi?id=851734#c5 -- Kind regards Christopher 'm4z' Holm / 686f6c6d "We must respect the other fellow's religion, but only in the sense and to the extent that we respect his theory that his wife is beautiful and his children smart." --H. L. Mencken -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner@opensuse.org
participants (1)
-
686f6c6d