| === robbiew is now known as robbiew_ | ||
| === [1]sassyn is now known as sassyn | ||
| === [1]sassyn is now known as sassyn | ||
| === [2]sassyn is now known as sassyn | ||
| === robbiew_ is now known as robbiew | ||
| === robbiew is now known as robbiew-afk | ||
| === robbiew-afk is now known as robbiew | ||
| mbiebl | Keybuk: hi, remember my problem I had with bridge devices on karmic? | 21:54 |
|---|---|---|
| Keybuk | yes | 21:55 |
| Keybuk | remember that I said they don't work? :p | 21:55 |
| mbiebl | I thought I turn the libvirt-bin sysv init script into an upstart job | 21:55 |
| mbiebl | and use start on (net-device-up IFACE=br0 and net-device-up IFACE=br1 and filesystem) | 21:55 |
| mbiebl | but that didn't work as expected | 21:55 |
| Keybuk | you'd still have the fundamental problem that br0 and br1 won't come up | 21:55 |
| mbiebl | /etc/init/networking.conf only seemed to bring up br0 | 21:56 |
| mbiebl | although I had both br0 and br1 configured as auto in /e/n/i | 21:56 |
| Keybuk | you were lucky it even did that | 21:57 |
| mbiebl | what happens is, that "initctl emit" in /etc/network/if-up.d/upstart is blocking | 21:57 |
| mbiebl | so ifup -a hangs at that point | 21:57 |
| Keybuk | you know how mountall carefully waits for devices, and has code to know that it needs two or more devices, and then only fscks and mounts devices when they are ready? | 21:57 |
| Keybuk | we need an equivalent for network devices | 21:58 |
| Keybuk | which we don't have | 21:58 |
| mbiebl | I used -n in the if-up.d hook and now it works fine for me | 21:58 |
| Keybuk | yes, the -n will break other things | 21:58 |
| Keybuk | (most particularly, the UEC images iirc) | 21:58 |
| Keybuk | the right fix is to get rid of "ifup -a" as a "bring up anything we forgot" tool | 21:59 |
| mbiebl | yeah | 21:59 |
| mbiebl | the -n hack is just a workaround for my particular setup | 22:00 |
| === robbiew is now known as robbiew_ | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!