>>> On 5/5/2011 at 12:49 PM, Christian Paro <[email protected]> wrote: -snip- > Putting the ipv6 kernel module in the initrd should solve the problem of the > module not being loaded on time. But I'm not sure it would solve the issue > of the sysctls not having the corresponding sysfs nodes to configure (since > these, I gather, are created as the network is being brought up). And,
To my knowledge, the sysctl command doesn't even look at /sys, only /proc. > unless there's an easier and "safer" way to modify the initrd for SLES than > unpacking it to a temporary location, adding/modifying files, and repacking > it with gzip and cpio, I'm not sure this is an approach I would advocate for > administrators who aren't used to building kernels/ramdisks (or are nervous > about breaking support agreements and assumptions). I know I'm used to doing > these kinds of modifications on personal systems, but personally would > prefer to stick with the distro-provided kernel and initial ramdisk for > anything being used in a production environment. This I can help with. Add "ipv6" to the INITRD_MODULES string in /etc/sysconfig/kernel and re-run mkinitrd. That's why it's there. -snip- > Also, using a layer-3 vswitch prevents autoconfiguration. But it also > prevents the use of IPv6 altogether for interfaces backed by that switch, Oh? That's news to me. If correct, that sounds like a bug in CP. Mark Post ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
