[01:22] tlee2, you have to use the mkimage command [01:22] tlee2, we made that change to make other things in our backend work a bit more sanely :-) [10:20] Anyone awake? [10:21] I tried rootstock. [10:21] It did a whooole lot of work. [10:21] I'm wondering if it made anything. [10:21] No new files in current directory. [10:21] Where should I be looking? [10:27] there should be files in the current dir [10:27] what was the commandline you used, which release are you on ? [10:29] I'm running on a Hardy-based x86 host. [10:29] So probably I'm hosed? [10:30] sudo ./rootstock -f name.example.com -l erikcorry -p foobar [10:31] hardy is to old [10:31] damn [10:32] you can bootstrap a jaunty chroot (using the jaunty debootstrap) and run rootstock inside there [10:32] OK [10:32] (well, hardy isnt necessarily to old, but i never tested it on hardy and didnt develop it on hardy so i wouldnt know what issues can come up there) [10:33] When it says I: Switching to Virtual Machine for second stage processing [10:34] I can't see anything. [10:34] Would I be able to see the VM running if I had my X display set up right? [10:35] nope, it doesnt use graphical output [10:35] it spawns the VM with a serial terminal and the script interacts through that with the VM [10:36] might be that hardy's qemu doesnt work for armel [10:37] we didnt support that arch back then, so i dont know if anyone paid attention to arm stuff [10:38] though if you say it switches to the VM, did you wait long enough ... it can take quite a while until it moves on [10:38] It's running at 100% CPU so it's doing something. [10:38] I have qemu 0.91 [10:39] how long did you wait yet [10:39] I waited a long time and it continued. [10:39] ah [10:39] yeah, the qemu part is very slow [10:39] Now it's scrolled off the top of the scrollback buffer so I can't see what happened [10:39] i hope to fix that for karmic [10:39] I'm running it again. [10:39] I'll report what happens. [10:39] Is it just because the qemu ARM emulator is slow? [10:40] yeah [10:41] I: Unpacking required packages... [10:41] looks good :) [10:42] just let it run... make some coffee ... drink it ... take a walk and then look again :) [11:12] ogra: Could you blacklist older dists in rootstock [11:12] ogra: Also could you stop installing ubuntu-minimal by default? It's pulled by debootstrap in all cases and breaks on Debian [11:12] rootstock only builds for jaunty and karmic and is only packaged for karmic [11:13] Oh so it refuses a hardy target already ok [11:13] i cant stop people from pulling from bzr [11:13] We could runtime check for the qemu version if that's the issue [11:14] -minimal was explicitly added as a no-op ... i didnt take debian into account back when i created rootstock [11:14] there is apparently no issue, its just the general slowness [11:14] Yeah could you make it "" instead of ubuntu-minimal? [11:14] indeed [11:14] Cause it's always pulled [11:15] though it will still break on debian without additional changes i guess [11:15] dpkg: failed to write status record about `libxslt1.1' to `/var/lib/dpkg/status': No space left on device [11:15] $DIST defaulting to karmic for example (though you can override it) [11:16] erikcorry, you picked the imagesize wrong [11:16] take a bigger value [11:16] Yeah, I just let it use the default. [11:16] 1G [11:16] 4G is big enough? [11:16] future versions will properly compute the size they need based on the package selection [11:17] what do you install ? a desktop will need 4G, yes [11:17] Thx [11:17] starting it again [11:17] I think I probably ran out of host disk space first time I ran it. [11:17] Target disk space second time. [11:18] oh, yeah, you will need some space for that on your host :) [11:18] at least the amount of the imagesize [11:18] plus whatever comes out of the script at the end as tarball [11:19] 1.5 times imagesize should be a good measure [11:27] lool, that will require more than "" [11:28] ogra@osiris:~/Devel/branches/rootstock-0.1.1$ LANG=C sudo apt-get -y install "" [11:28] Reading package lists... Done [11:28] Building dependency tree [11:28] Reading state information... Done [11:28] E: Couldn't find package [11:28] You need me to help fix that? :) [11:28] nah [11:35] fixed and pushed [11:36] thanks [11:55] dpkg-preconfigure: unable to re-open stdin: [11:55] It looks like it might be harmless [12:17] OK that didn't work. [12:17] Looks like my old Qemu isn't up to the task, as you predicted. [12:25] Any tips on making a jaunty chroot area with debootstrap? [12:28] https://help.ubuntu.com/community/DebootstrapChroot [12:28] " the debootstrap that is bundled with Hardy cannot prepare a Jaunty chroot." [12:28] Damn [12:29] its just scripts ... you can pull the jaunty one and just dpkg -i it [12:31] It seemed to build something anyway. [12:31] But when I chroot into it apt-get doesn't work. [12:32] # apt-get install svn [12:32] Reading package lists... Done [12:32] Building dependency tree... Done [12:32] E: Couldn't find package svn [12:32] doh! [12:32] It's called subversion [13:44] Standard debootstrap from jaunty doesn't seem to have a script for karmic. [13:44] no, for jaunty [13:44] But if I want the latest greatest ARM stuff I have to use karmic, right? [13:44] if you want the unstable arm stuff you want karmic :) [13:44] For some reason the debootstrap I had on hardy already had that script. [13:44] indeed that also has the latest and greatest [13:45] Is there any other kind of arm stuff? [13:45] :-) [13:45] heh [13:46] What's the best way to upgrade one single package? Just download it as a deb or should I do something to my sources.list file? [13:47] Sorry about all these newbie questions. [13:49] what package ? [13:50] It's OK. [13:50] I found a newer debootstrap than the one that came with jaunty and installed it. [13:50] Now I have the karmic script. [13:51] ok [13:52] Enhancement request for rootstock: If the /usr/share/debootstrap/scripts/karmic file is not there then give a good error message. [13:52] it does if the debootstrap version isnt right [13:52] Debootstrap was newer than 1.0.10 [13:53] Which I think is what it tests for. [13:53] it looks for something that can build jaunty [13:53] in karmic it is packaged and the package depends hard on the right version [13:53] But the -d option defaults to karmic [13:54] The standard debootstrap in jaunty is 1.0.12 which can't build karmic. [13:54] The 1.0.13~jaunty1_all version can [13:56] right, but i dont want to force jaunty users to update debootstrap, they should use -d jaunty [13:56] Whatever -d option they use that should be the one that you check for in /usr/share/debootstrap/scripts/ [13:57] At the moment it bombs out with a cryptic error message and leaves the image mounted. [13:57] thats a bug indeed [13:57] it should clean up after itself [13:58] i will make $DIST default to the host distro and make it throw an error if its pre jaunty [14:01] But you do expect that one can build a karmic ARM system on a Jaunty host? [14:01] If you install debootstrap probably [14:02] sure [14:02] and thats why the script has a -d option [14:02] the default for that options is picked wrong though [14:07] I sent you a patch. [14:08] oh, thanks ! [14:08] It's not tested :-/ [14:08] It's just to illustrate what I mean. [14:08] * ogra waits for it [14:08] essentially it should just be: DIST=$(lsb_release -cs) [14:09] and probably an error message telling you you cant build for future distros without future debootstrap [14:09] ah, there it is [14:10] perfect, that and the lsb_release change together will make it work right [14:10] * ogra adds that to bzr [14:13] erikcorry, mind if i move that check a bit earlier so it fails before it actually uses diskspace ? [14:15] committed and pushed [14:18] Sounds fine. === bjf-afk is now known as bjf- === bjf- is now known as bjf [16:13] lool, ogra, would you like to look over my flash-kernel changes? (I'm about to do an install with them in place to make sure they work as excepted, but I'd like any input: http://paste.ubuntu.com/263860/) [16:23] hi has anyone seen bug #416313 [16:23] Launchpad bug 416313 in samba "On samba of ubuntu-arm, large file copy fails " [Undecided,New] https://launchpad.net/bugs/416313 === bjf is now known as bjf-afk [16:55] ogra: You kicked some live builds? [16:55] I mean livefs [17:24] ogra: How do I use hte linux-mvl-dove from uboot? [17:24] NCommander, ^^^ [17:24] tlee, is your root filesystem ext2 or ext3? [17:24] If the answer is no, then you can't load it directly :-/ [17:24] ext3 on sata [17:24] Well [17:25] That will work :-) [17:25] tlee, are you using a separate boot partition or no? [17:25] yes. [17:25] I can configure it anyway you like. [17:25] * NCommander thinks he just found a test victim :-) [17:25] Is there a wiki howto? [17:26] tlee, its not fully up to dat eyet, I'm currently working on extending u-boot's boot scripts to automatically scan usb and SATA HDDs for the ubuntu boot.scr file :-) [17:26] tlee thinks he just been victimized. :-) [17:26] I play with boot.scr before. [17:26] tlee, we do have working live images, but the installer kinda fubar'ed [17:26] tlee, http://people.canonical.com/~mcasadevall/karmic-desktop-armel+dove.img [17:27] tlee, download that, stick it on a pendrive, and then you can start the live environment :-) [17:27] Which uboot do I need to support this scan function? [17:27] tlee, the one I haven't written yet ;-) [17:28] Would the default Y0 uboot work? (Whatever default means...) [17:28] tlee, (I'm working off the Marvelll 4.2.3 source drop with a few patches to turn the Hush shell on) [17:28] tlee, you need Y0 4.2.3 [17:28] (check the version string) [17:28] Will check which one I have now. [17:28] but thats just to start the live image, I'll have a new u-boot binary that sits in NAND flash (vs. spi-nor) which handles the scanning [17:40] NCommander, my uboot is 4.1.7. Do I get the updated uboot from u? [17:40] or MVL [17:40] tlee, I'm not sure if I can post u-boot binaries or not [17:40] but you'll need a newer one :-/ [17:41] Will email u.... === bjf-afk is now known as bjf [19:02] NCommander: what is a dove board? :) [19:03] armin76, upcoming hardware [19:04] rabeeh: i want one :P [19:04] without knowing what it is? :) [19:05] suihkulokki: it's new, therefore it must be cool [19:05] suihkulokki, be sure you want one too once they are on the market [19:05] armin76, wow, your a real ARM diehard :-) [19:05] armin76, :-) [19:05] NCommander: i always like to try new stuff :) [19:10] armin76, I should send you my MIPS laptop [19:17] NCommander: got bored of it? :) [19:17] armin76, it doesn't work too well with lenny [19:17] and the Xorg I need is still stuck in sid I think [19:17] and sid is extra broken recently === bjf is now known as bjf-afk === cbrake is now known as cbrake_away