| === harlowja is now known as harlowja_away | |
| === harlowja_away is now known as harlowja | |
| === harlowja is now known as harlowja_away | |
| [07:59] <smoser> cirros 0.3.2 released | |
| [08:16] <harmw> coool | |
| [12:51] <harmw> argh, smoser what's the url for the latest kernel image? (and how the hell do I get it myself) | |
| [14:42] <harmw> and isn't there a virtual flavor of 3.13 kernel? | |
| [16:06] <smoser> harmw, its -generic now. | |
| [16:06] <smoser> there is still a virtual, but it depends on the -generic | |
| [16:10] <harmw> the package is called -generic now? (and -virtual is gone, as a file) | |
| [16:10] <smoser> i gave you info on this man. | |
| [16:11] <smoser> http://paste.ubuntu.com/7069858/ | |
| [16:12] <harmw> yup, but 0.3.2 still uses flav=virtual | |
| [16:12] <smoser> right. it uses precise kernel. | |
| [16:12] <harmw> but if it's -generic now, thats just fine | |
| [16:13] <smoser> so they just changd how the packaging is done. | |
| [16:13] <harmw> ok | |
| [16:13] <smoser> previously, there was a '-virtual' which actually confliced with '-generic' | |
| [16:13] <smoser> now there is a -virtual , which depends on -generic | |
| [16:13] <harmw> aha | |
| [16:13] <smoser> er... something like that | |
| [16:13] <harmw> yea well :) | |
| [16:13] <smoser> and then something also depends on -extra-drivers | |
| [16:13] <smoser> so most users will get the virtual kernel +_ the extra stuff | |
| === harlowja_away is now known as harlowja | |
| === harlowja is now known as harlowja_away | |
| === harlowja_away is now known as harlowja | |
| [18:36] <harmw> damn, cirros-status should show the running kernel | |
| [18:39] <smoser> :) | |
| [18:39] <smoser> it should. you're right. | |
| [18:39] <smoser> i think we should branch 0.3 | |
| [18:39] <smoser> and start 0.4 | |
| [18:40] <harmw> ok, and wht will those 2 focus on? | |
| [18:42] <harmw> we could branch 0.3 and merge my buildroot+kernel update stuff with that? | |
| [18:43] <harmw> keep 0.2 the current supported version, but what should 0.4 aim for? | |
| [18:50] <smoser> 0.3.x is "stable" | |
| [18:51] <smoser> 0.4 is buildroot+kernel+mdev+ppc64+world-domination | |
| [19:00] <harmw> uhm right :| obviously | |
| [19:00] <harmw> somewhere my mind came up with 0.2 as beeing current :| | |
| [19:06] <harmw> I'd say make it happen smoser :) | |
| [19:07] <smoser> yeah. so i'd take your 'uname' info for 0.3.X, and i'd like to hvae the fix for more generic dhclient stuff there too. specifically for mtu. | |
| [19:07] <smoser> as it seems that can completely block usage | |
| [19:07] <harmw> agreed | |
| [19:08] <smoser> altough i guess you could send config-drive user-data to run ifconfig | |
| [19:08] <smoser> and fix it | |
| [19:15] <harmw> smoser: http://paste.ubuntu.com/7115837/ | |
| [19:16] <smoser> :) | |
| [19:34] <harmw> smoser: bin/build-release deletes the raw image, could you please not do that? | |
| [19:35] <smoser> why? whats in it? | |
| [19:36] <harmw> I'm uploading just that to openstack | |
| [19:37] <harmw> rather pointless i manually convert back to raw with qemu-img :) | |
| [19:37] <harmw> plus, could you include this to support Hyper-V vm's? (despite the inner workings not beeing in place just yet) | |
| [19:38] <harmw> qemu-img convert -O vpc cirros-0.3.2-pre1-x86_64-rev309.raw cirros.vhd | |
| [22:06] <harmw> smoser: you should update the Changelog as well | |
| [22:06] <harmw> since r307 | |
| [23:17] <smoser> harmw, i admit that part of me doing qcow is to try to teach the world to stop being stupid. | |
| [23:17] <smoser> providing 'raw' does not help with that. | |
| [23:18] <smoser> i dont really care what layout a hypervisor uses to represent a disk as its being used. | |
| [23:18] <smoser> but qcow2 is an open def-facto standard that provides both sparseness and compression. | |