On Jan 26, 2012, at 8:10 AM, Bruce Dubbs wrote:
>> BTW, any thoughts on how bridgeutils will be used by the bootscripts?
>> As nice as my script was, it did require 2 seperate ifconfig.br0
>> files. (Well, easier w/ Qrux's changes, but we wouldn't want to add
>> support for every variation of network addresses into the bind script
>> [dhcp, ipv4, ipv6]).
Nathan--you're totally right. I hadn't thought about downstream stuff when I
hacked the 'ip addr add' stuff into your /lib/services/bridge...
> SERVICE="bridge ipv4-static"
>
> and call the services in that sequence. That would require changes to
> ifup and ifdown, but not a lot. I haven't thought it trough yet, but it
> may work.
Nice idea. I put something together this morning. I've uploaded my
/lib/services/bridge, /sbin/ifup, and /sbin/ifdown:
https://github.com/qrux/xlapp/tree/master/xlapp-bridge
The gist is that /sbin/ifup looks at SERVICE, and runs a loop like this
(simplified):
====
SERVICES=$SERVICE
for _S in $SERVICES ; do
<orig ifup code>
done
====
In /sbin/ifdown, I just reverse the order of the services (and do the same
loop).
====
SERVICES=""
for _S in $SERVICE ; do
SERVICES="${_S} $SERVICES"
done
# SERVICES should be SERVICE, but reversed
for _S in $SERVICES ; do
<orig ifdown code>
done
====
On a related note...I've been able to get a pure-64-bit version of Xen running
on a LFS/BLFS system (I brought up my first VM yesterday). Bridging was my
last LFS/BLFS-related hurdle, and I think that's basically resolved now. I've
committed the entire build at GitHub for anyone interested in a 64-bit-only Xen
source-build-from-scratch:
https://github.com/qrux/xlapp
Thanks, Bruce, Nathan, and Ken, for your help in putting these pieces together
and also for being so helpful to the community.
Q
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
