Wrapping eatmydata around dpkg "fixes" the problem; details below.
Trent Buck wrote (offlist):
> As I now understand it, the facts are these:
>
> - lucid's dpkg uses an fsync-per-file
>
> - lucid-security's dpkg uses a sync-per-rename, because fsync was
> slow (only on ext4/btrfs, I think
On Thu, 2011-02-03 at 09:09 -0800, Dean Mao wrote:
> You can just add a new bridge with "brctl addbr br7" if you wanted to
> add a bridge 7... then configure it with "ifconfig br7 172.16.0.1
> netmask 255.255.255.0 up" and you'll have a new network on the same
> computer.
Didn't know that... I th
On 02/03/2011 10:51 PM, Gary Ballantyne wrote:
>
> On 2/3/2011 1:47 PM, Trent W. Buck wrote:
>> Gary Ballantyne
>> writes:
>>
>>> # /usr/bin/lxc-execute -n foo -f
>>> /usr/share/doc/lxc/examples/lxc-veth.conf /bin/bash
>>>
>>> The container fired up, and I could ping to/from the host. However, wh
On 2/3/2011 1:47 PM, Trent W. Buck wrote:
> Gary Ballantyne
> writes:
>
>> # /usr/bin/lxc-execute -n foo -f
>> /usr/share/doc/lxc/examples/lxc-veth.conf /bin/bash
>>
>> The container fired up, and I could ping to/from the host. However, when
>> I left the container (with "exit") things got weird
On 02/03/2011 07:08 AM, Trent W. Buck wrote:
> t...@cybersource.com.au (Trent W. Buck)
> writes:
>
>> I'm being a bit more patient than last time, and I think they ARE
>> proceeding, just REALLY slowly. Meanwhile aptitude consumes a 100% of a
>> core busy-waiting for a response from dpkg :-/
>>
>>
The bridges are essentially dummy interfaces -- you can add as many as you
want, and have them on random networks if you want, and have complicated
routing schemes between them. I don't think you need to create a dummy
interface anywhere. You can just add a new bridge with "brctl addbr br7" if
yo
On Thu, 2011-02-03 at 09:13 -0200, Andre Nathan wrote:
> eth0 -> external network
> eth1 -> 10.0.0.0/16 network
> containers -> 192.168.0.0/16 network
Hmm I managed to do this creating a dummy interface and setting up a
bridge on it, so now I have
eth0 -> external network
eth1 -> 10.0.0.0/16 netw
On Wed, 2011-02-02 at 12:07 -0800, Dean Mao wrote:
> Yeah, it's quite easy to do this. Here's my lxc network config from
> one of my machines:
>
>
> lxc.network.type = veth
> lxc.network.flags = up
> lxc.network.link = br1
> lxc.network.ipv4 = 192.168.0.4/24
>
>
> My outside network is eth0/br
