On Thu, 2009-07-16 at 00:43 -0400, Warren Togami wrote: > Attached is the parser of this bridging plan. Bridge details if parsed > from cmdline are written to /tmp/bridge.info for later use by network > scripts with the following behavior. Any comments? I was under the impression that you could swizzle IP addresses from "real" userspace even if the root filesystem was mounted over the network. That said, did you have a specific use case in mind? > SYNTAX > ====== > bridge=<bridgename>:<ethname> > If bridge without parameters, assume bridge=br0:eth0 > > BASIC IDEA > ========== > * When <ethname> would be configured by network scripts, instead create > a bridge named <bridgename> then add <ethname> to that bridge. > * <bridgename> automatically inherits the MAC address of <ethname>. > BOOTIF thus should be optionally workable. > * Then $netif becomes <bridgename> instead of <ethname> and all existing > scripts process netroot mount via this new $netif instead of <ethname>. > * Try only the one specified <ethname> interface, do not try others. (I > suppose trying others in the "bridge root=dhcp" case would be possible, > but let's get the basics working first.) > * write-ifcfg.sh writes out both ifcfg-<bridgename> and ifcfg-<ethname> > files for later use by NetworkManager. > > BOOT EXAMPLE > ============ > ifconfig eth0 up > brctl addbr br0 > brctl setfd br0 0 > brctl addif br0 eth0 > dhclient br0 > ifconfig br0 <parameters> > mount -t nfs server:/path /sysroot > switch_root /sysroot > > ifcfg-br0 example > ================= > # Generated by dracut initrd > DEVICE=br0 > TYPE=Bridge > ONBOOT=yes > BOOTPROTO=dhcp > STP=off > USERCTL=no > > ifcfg-eth0 example > ================== > # Generated by dracut initrd > TYPE=Ethernet > DEVICE=eth0 > HWADDR=52:54:00:12:34:56 > ONBOOT=yes > BRIDGE=br0 > USERCTL=no > > Warren Togami > wtogami@xxxxxxxxxx -- Victor Lowther RHCE# 805008539634727 LPIC-2# LPI000140019 -- To unsubscribe from this list: send the line "unsubscribe initramfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
