Michael DeHaan wrote:
Ronald J. Yacketta wrote:
Running through the snippets in an attempt to resolve another issue and
I noticed the following in post_instyall_network_config
if [ -f "/etc/modprobe.conf" ] && [ $IFNAME ]; then
grep \$IFNAME /etc/modprobe.conf | sed "s/\$IFNAME/$iname/" >>
/etc/modprobe.conf.cobbler
grep -v \$IFNAME /etc/modprobe.conf >> /etc/modprobe.conf.new
rm -f /etc/modprobe.conf
mv /etc/modprobe.conf.new /etc/modprobe.conf
fi
not sure about RHEL, but Fedora does not use modprobe.conf for this type
of configuration. I created a similar thread with subject 'Arbitrary NIC
naming' back on 2/24/09 according to Jasper Capel:
Modprobe.conf just isn't used for that purpose in F10
anymore.
I'll file a bug against this as well and update this thread with the bug ID
-Ron
_______________________________________________
cobbler mailing list
[email protected]
https://fedorahosted.org/mailman/listinfo/cobbler
It's probably not hurting things.
_______________________________________________
cobbler mailing list
[email protected]
https://fedorahosted.org/mailman/listinfo/cobbler
I agree that there might be a limited number of endusers renaming
interfaces, but we are installing systems in a VM (Qemu) and would like
to rename the guest interfaces to match the underlying bridge they are
using.
The usage of modprobe.conf over udev rules prevents this from happening
during a cobbler/koan install.
Another issue that I noticed today is that no matter what I try / do the
nic being created for the VM is always the hypervisor default. Tried
everything to get cobbler to build out the proper xml to have a virtio
or e1000 module used.
-Ron
_______________________________________________
cobbler mailing list
[email protected]
https://fedorahosted.org/mailman/listinfo/cobbler
