=== praneshp_ is now known as praneshp === harlowja is now known as harlowja_away === harlowja_away is now known as harlowja === harlowja is now known as harlowja_away === evilissimo is now known as evilissimo|afk === evilissimo|afk is now known as evilissimo [09:00] omgwtfbbqlol [09:00] libvirt_type = qemu... [09:01] no wonder my cloud instances are dead slow... [09:01] seriously, why didn't I figure that out like a year ago [09:01] (ok, the hardware is slow but still) [09:01] anyway, centos took a mere 40ish seconds, instead 5+ minutes to boot :p === evilissimo is now known as evilissimo|afk === evilissimo|afk is now known as evilissimo === evilissimo is now known as evilissimo|afk === evilissimo|afk is now known as evilissimo [13:03] harmw, my plan was to ditch the static/silly CONFIG_IFUPDOWN and make that configurable. [13:03] at "runtime". [13:04] ie, just have CONFIG_IFUPDOWN_UDHCPC_CMD_OPTIONS as "" [13:04] and then wrap udhcp or ifupdown or somethign with a shell that reads options from somewhere in the filesystem. === evilissimo is now known as evilissimo|afk === harlowja_away is now known as harlowja [19:01] smoser: so let udhcpc run in way the user wants it to run, according to some config file [19:01] sounds like a plan [19:04] harmw, i think i might even consider patching busybox to call a different udchpc [19:04] ie, udhcpc.ifupdown [19:04] or something. [19:04] then we can just provide that. [19:04] might have to atch busybox to do that [19:05] hmk [19:05] isn't a wrapperscript a little more convenient instead of patching busybox? [19:05] eg. working with a script+config file? [19:06] well, id consider patching busybox to invoke /sbin/udchpc.ifupdown [19:06] so that we'd know when *that*program was called it was from ifupdown [19:07] and not get in the user's way if they ran it : udchpc -i eth0 [19:07] or something like that. [19:07] ah like that [19:08] I didnt venture into things that deep :p [19:08] though I'm starting to like the concept [19:11] I'm guessin' one hour of work [19:11] patching busybox... thats just a configuration file thingy I'd guess, right? [19:12] some of our own config in /etc/sysconfig/udhcpc.options [23:09] harmw, there is some infrastructure for quilt applying patches in cirros now [23:10] and i'd just do that to change the string that busybox invokes [23:10] not bother to do it properly (ie, not do a config option) [23:10] i think its networking/ifupdown.c