http://bugzilla.novell.com/show_bug.cgi?id=539869
--- Comment #7 from Axel Köllhofer 2009-11-15 14:27:37 UTC ---
after having a thought or two about this issue (and presuming that
CONFIG_IPV6=y was set for the same of speeding up the boot process) it looks to
me as there are three potentiel ways to solve this issu.
a) "Back to the roots"
Setting CONFIG_IPV6=m on all flavors and keeping the way YaST handles disabling
IPv6 via blacklisting the module. If CONFIG_IPV6=y was set for speeding up the
boot process (amongst others, i.e. ext3 has been compiled into the kernel also
since 11.2), this might be undesired.
b) Making disabling IPv6 via YaST "dumb but effective"
When disabling/enabling IPv6 via YaST, the YaST-mdule will disable/enable the
module ipv6 via /etc/modprobe.d/50-ipv6.conf and the boot parameter
"ipv6.disable=1" will be appended/removed from the respective lines in
/boot/grub/menu.lst and /etc/sysconfig/bootloader.
The only drawback will be a warning very early on boot if the system is booting
a kernel-flavor with CONFIG_IPV6=m set, informing the user of an unknown
parameter which will be ignored.
c) Enabling YaST to make an "intelligent" choice:
When disabling/enabling IPv6 via YaST, the YaST-module will search all
/boot/config-*version*-*flavor* files for CONFIG_IPV6 and modify
menu.lst/etc/sysconfig/bootloader only for those flavors with CONFIG_IPV6=y,
while setting "install ipv6 /bin/true" if at least one of the installed flavors
has CONFIG_IPV6=m set.
However, this would have to be repeated automatically if the user installs
another kernel-flavor.
Personally, I would vote for b) at least as a short term solution, but these
are just a few thoughts by someone from the "outside".
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.