[01:21] <Micksa> suspend-to-ram is working like a charm
[01:21] <Micksa> and all it right with the world once more
[01:58] <zul> jbailey: dont start hacking on the kernel? sheesh thats what i did :)
[02:18] <jbailey> I didn't say don't start there.  I said it's possible not the best place to start.
[02:18] <zul> hehe..
[02:26] <jbailey> And really, to start by doing kernel hacking requires a whole lot of drive.
[02:26] <jbailey> Someone with it will do it regardless of what I say.
[02:26] <jbailey> (Esp as I don't mean to be discouraging.  It is a daunting place to start on its own without my help)
[02:28] <zul> oh i know...
[02:28] <zul> its a rough place to start if you are just starting out
[05:50] <lamont> now to figure out if I really care about the bug
[05:51] <lamont> new oo.o2 and gcc-3.3 sigh
[05:51] <lamont> and gcc-3.4
[05:51] <lamont> that explains why it's taking forever. :=(
[05:58] <dilinger> jbailey: ping
[06:18] <fabbione> morning
[09:52] <chmj> fabbione, ping
[09:53] <fabbione> pong
[09:55] <chmj> fabbione, is it possible to merge the last patch in kernel-debian--pre1,3--2.6.1 1.93 to the new playground ?
[09:57] <fabbione> chmj: i think so yes.. but that change needs to be reverted in that branch
[09:58] <chmj> ok, I don't know my way around baz that much
[10:01] <fabbione> chmj: ok i will try to clean up
[11:40] <jbailey> dilinger: pong =)
[11:45] <fabbione> hey jbailey
[11:46] <jbailey> g'm Fabio
[01:17] <zul> morning
[01:18] <fabbione> hi zul
[01:19] <zul> how is the external-modules going?
[01:19] <fabbione> i didn't work on it yet
[01:19] <zul> ah
[01:19] <fabbione> doing other stuff atm
[01:20] <fabbione> looking at the new kernel-package and kernel-wedge
[01:49] <chmj> zul, where are the external-modules packages ?
[01:49] <chmj> if there are any packages
[01:51] <fabbione> there are no packages
[01:58] <jbailey> fabbione: *poke*
[01:59] <fabbione> jbailey: ?
[01:59] <jbailey> I think in ppc32 mode this thing has gotten farther.
[01:59] <jbailey> It's got a bunch of XMLTO lines on the screen now.
[01:59] <fabbione> jbailey: why am i not surprised? :)
[01:59] <fabbione> yeah that's it
[01:59] <fabbione> i think
[01:59] <fabbione> let it finish
[01:59] <jbailey> Will do.
[01:59] <fabbione> i will deal with it soon.. i think i know what it is
[02:00] <jbailey> I think I'm going to have a nap.  I woke up crazy early this morning because of the cats.
[02:00] <fabbione> i noticed :)
[02:00] <fabbione> thanks a lot
[02:00] <jbailey> =)
[02:18] <fabbione> speaking of which.. a nap is a really good idea
[02:19] <fabbione> zul: i did upload the new kernel-package
[02:19] <chmj> u have cats ?
[02:19] <fabbione> so you can build again
[02:19] <fabbione> chmj: no... i have a wife :P
[02:19] <chmj> who has cats I assume ?
[02:20] <fabbione> chmj: i am not following you :)
[02:20] <fabbione> anwyay.. later
[02:20] <chmj> later
[04:12] <jbailey> fabbione: Build finished fine.
[04:14] <dilinger> jbailey: i was just curious what you thought regarding cdbs2 testing framework stuff
[04:15] <jbailey> dilinger: When I read it, it made my brain hurt, so I went to bed. =)
[04:16] <jbailey> I'll take a look again today.
[04:16] <dilinger> jbailey: writing it made my brain hurt a little.  i should probably try and make it a bit more coherent or something ;)
[04:16] <jbailey> I wrote the original testsuite, and it's basically the one from cdbs1 ported up.
[04:16] <jbailey> I agree that it would be nice to make it a bit more generic.
[04:19] <lamont__> fabbione: ping
[04:19] <jbailey> I do occasionally run the testsuite by hand while I'm hacking, largely with debugs turned on so that I can see what's happenning.
[04:20] <dilinger> jbailey: yea, basically the abi checking stuff fits right in w/ this..
[04:20] <jbailey> Right.
[04:20] <jbailey> I need to learn a bit more about how that's happening.
[04:20] <jbailey> But if we could unify it with stuff that we're developping collectively, then that would be lovely.
[04:43] <zul> fabbione: ping
[04:54] <lamont__> "BTW, nobody should be using transport mode over the Internet anyway."
[05:16] <jbailey> context?
[05:21] <dilinger> ipsec?
[05:27] <lamont__> ipsec
[05:27] <fabbione> pong
[05:27] <lamont__> vs tunnel mode
[05:30] <fabbione> lamont__: dunno why.. but you can use tunnel mode between 2 hosts exactly as you use transport
[05:30] <fabbione> lamont__: i am pretty sure that what he sais is ok, given he is one of the Ipsex developer :)
[05:30] <fabbione> zul: pong?
[05:30] <lamont__> fabbione: ok
[05:32] <zul> fabbione: i made some changes my arch you can sync if you want
[05:32] <fabbione> zul: ok thanks
[05:35] <lamont__> fabbione: what I'd really like is a comprehensive tutorial on the subject. :-)
[05:37] <fabbione> lamont__: i remember i read all the RFC's 5 years ago... and i met who wrote them. you really don't want to go there.. do you? ;)
[05:37] <jbailey> lamont__: Step 1: Install checkpoint Step 2: Slit wrists.
[05:38] <lamont__> fabbione: all the stuff from 6 months ago is completely incorrect
[05:38] <fabbione> lamont__: probably the linux implementation sucks....
[05:38] <fabbione> i did use fbsd+racoon against an ericsson ipsec implementation at that time
[05:39] <fabbione> and it was working
[05:39] <dilinger> heh
[05:39] <dilinger> ipsex?
[05:39] <fabbione> but i didn't even attempt firewalling
[05:39] <fabbione> dilinger: yeah.. isn't ipsec sexy??
[05:39] <lamont__> fabbione: that's the thing - none of the ipsec howto's address firewalling
[05:39] <fabbione> i even wwrote ipsex several times in my test reports for ericsson...
[05:39] <fabbione> nobody bothered to correct them :)
[05:39] <dilinger> hehe, nice
[05:40] <lamont__> Jun 14 09:39:57 localhost racoon: NOTIFY: the packet is retransmitted by <IP_ADDRESS>[500] .
[05:40] <fabbione> lamont__: right, because ipsec and firewalling are 2 separate issues...
[05:40] <fabbione> lamont__: one to protect data/connection , one to protect the host
[05:42] <lamont__> right.
[05:43] <lamont__> many of the ipsec tutorials tell you that to make ipsec work, you need iptables -A INPUT -p esp ACCEPT
[05:43] <lamont__> which isn't necessarily so
[06:27] <lamont__> what is /dev/vcsN ?
[06:28] <zul> virtual console screen
[06:28] <lamont__> ah, ok
[06:57] <fabbione> hey thombot
[06:59] <fabbione> ok
[07:01] <thom> yo
[07:06] <lamont__> fabbione: note that you're making it harder and harder to build 2.6.12 on hoary. </grumble>
[07:21] <thom> fabbione: dude, ipw2100 is at 1.1.0 which is apparently the version we have
[07:26] <zul> for breezy?
[07:27] <fabbione> lamont__: you are not even supposed to build 2.6.12 on hoary :)
[07:27] <fabbione> thom: is it???
[07:27] <lamont__> fabbione: yeah, and?
[07:27] <fabbione> ipw2100            | 1.1.0                      | ok     | 12/04/2005   | http://ipw2100.sourceforge.net/
[07:27] <fabbione> oh yeah indeed
[07:28] <fabbione> lamont__: i know.. but there are a bunch of assholes sitting on #ubuntu-toolchain that keeps breking things... and i have to put pieces back together again
[07:28] <fabbione> ;)
[07:33] <lamont__> gcc-3.4 (>= 3.4.4-0ubuntu6) [powerpc i386]  | gcc-3.4 (= 3.4.3-9ub
[07:33] <lamont__> untu4) [i386] , gcc-3.4 [!powerpc !i386]
[07:34] <fabbione> i didn't do it :)
[07:34] <lamont__> that's my addition in between the | and the ,
[07:34] <lamont__> and makes hoary happy again
[07:39] <zul> i hate sql
[07:43] <lamont__> zul: I've never met anyone who claimed otherwise.
[07:46] <zul> good so im not alone
[08:44] <thom> bleah. EIP is at ieee8011_wx_get_scan
[08:50] <lamont__> fabbione: the ones doing the breaking are all here, too. :-)
[09:05] <lamont__> cache hit                             65
[09:05] <lamont__> cache miss                         17642
[09:05] <lamont__> grumble
[09:06] <thom> fabbione: right, this ipw2100 problem is a regression from 2.6.10
[09:25] <jbailey> Should the kernel be part of ubuntu-minimal?
[09:27] <fabbione> thom: it's an upstream problem. ipw2100 is using an old version of ieee$randomnumbers
[09:27] <fabbione> i remember very well that from when i did the merge
[09:27] <fabbione> so we need to wait upstream to sync
[09:27] <fabbione> both ipw2100 and 2200 have this ieee code duplication
[09:28] <fabbione> and they often go out of sync
[09:28] <fabbione> lamont__: that was the point of my comment :P
[09:29] <thom> fabbione: grah, k
[09:42] <lamont__> 6000 more misses, 20 more hits.  woot!
[10:22] <zul> fabbione: new inotify
[11:19] <jbailey> dilinger: Around?
[11:20] <dilinger> yep
[11:21] <jbailey> dilinger: cdbs2 thoughts for you.  Once we're done this testsuite and some basic docs.  What all do you think there is left before we can include it for some basic usage?  I know that the debhelper and autotools need a bunch of variables populated and help things written for them.  Is there other just basic functionality that's missing before people can at least start peeking at it for basic apps?
[11:22] <dilinger> yea, the main thing that's missing/broken is per-module pass stuff
[11:22] <dilinger> right now, if you have CDBS_MODULES := autotools, foo_CDBS_MODULES := autotools debhelper, debhelper gets run for both
[11:23] <dilinger> i think that's a bug i introduced, with the way i'm keeping track of stuff
[11:23] <dilinger> that's the main thing that's remaining
[11:23] <jbailey> Nice. =)
[11:23] <jbailey> I haven't dug through everything yet that you've done.
[11:23] <dilinger> after that, we just start porting modules
[11:23] <jbailey> My initial targets for modules are just autotools, python, ant, gnome and kde.
[11:24] <jbailey> Those are ones that I feel confident writing testscripts for.
[11:24] <dilinger> the framework is there, debian/rules help will spit out all variables, hooks, etc; i'm not too concerned about the test suite stuff, but if we decide to make it built in (w/ the way i'd prefer, test-specific hooks), it wouldn't be too hard to add in there
[11:24] <jbailey> I'm hoping to be more hardcore about features needing testcases for this so that we don't have the kind of fuckage debian had from robert in the last few months of cdbs.
[11:24] <dilinger> jbailey: that would be nice
[11:25] <dilinger> i'd certainly appreciate it if you pushed for the test stuff
[11:26] <dilinger> because i can pretty much guarantee how it'll go if i do it (first, i'll say i just want to get stuff working, so i won't concentrate on the test suite.  after stuff is working, i'll say things need enhancements before i can get to the test stuff.  finally, i'll say it's time for the test suite, and i'll get distracted and work on some other project that's bugging me)


[00:33] <dijenerate> hi all
[00:34] <dijenerate> I've just created a custom build of ubuntu-mobile for a trial enterprise deployment...
[00:34] <dijenerate> I need to make an easy installer/recovery disk from the prototype build
[00:35] <dijenerate> what is the easiest/fastest way to make a bootable iso that will install this build to new hardware
[00:36] <dijenerate> I can do this presently by using the 'dd' command to overwrite the target device
[00:36] <dijenerate> I'd prefer to automate
[00:36] <persia> Do you know the set of changes you made to a default image?
[00:37] <dijenerate> they are documented but the list is looooong
[00:37] <dijenerate> I'd prefer to just have an auto-installer dump this onto a new drive
[00:37] <persia> Was it just package changes, or config changes as well?
[00:37] <dijenerate> configs as well
[00:37] <dijenerate> plus custom packages etc
[00:38] <persia> Hrm.  That gets tricky then.
[00:38] <persia> So, there's no good way to get an installed system back into an installer
[00:38] <dijenerate> it no longer uses hildon, but boots to the company's custom window manager
[00:38] <dijenerate> oh... that sucks
[00:38] <persia> And using dd has a number of frustrating associated issues related to install-time stuff.
[00:39] <persia> But there are a number of tools that can help to modify a live image.
[00:39] <dijenerate> well I have prepped an image that is ready to be configured
[00:39] <persia> And that can then be used for an install of the modified system.
[00:39] <dijenerate> so it boots up, creates the new /etc/udev/rules.d/70*persistent-net... etc
[00:39] <persia> You've already prepared a custom live image for your target?
[00:39] <dijenerate> as well as prepping all necessary scripts for the stuff that's unique for the hardware
[00:40] <dijenerate> yes, that's what I dump using dd
[00:40] <dijenerate> it takes care of the filesystem (ext4) and the mbr
[00:40] <dijenerate> so I was just looking for an automated way to do this from a cd/usb drive that someone who isn't from engineering could use
[00:41] <persia> I think we're running into a definition issue.    An "installed image" is the result of having performed an install.
[00:41] <dijenerate> we currently dump with dd, then grow the fs to fill the new drive
[00:41] <persia> Which have you prepared?
[00:41] <dijenerate> installed, but ready for setup
[00:41] <dijenerate> so in the 'first time' state
[00:41] <persia> Right.  I get it.
[00:42] <persia> Are you using oem-config?
[00:42] <dijenerate> nope... actually a lot of the custom ubuntu stuff has been stripped to give a lighter thinner ubuntu
[00:42] <dijenerate> needs only 170MB RAM and 800MB disk space
[00:43] <dijenerate> so the special oem-config stuff is no longer there
[00:43] <persia> OK.  I think I understand your current state.
[00:43] <persia> I don't know of any tools that would construct an installer image from that.
[00:43] <dijenerate> oh... crap
[00:43] <persia> I can walk you through the process of modifying an installer image to include the changes.
[00:44] <dijenerate> hmmm...  I'd probably would be better off, scripting the dd and grow fs commands then creating a tarball in a folder on a live cd image
[00:44] <persia> But that is mostly for changes in package selection.  If you have additional configuration, that usually involves a combination of a special foo-default-setttings package and some changes to existing packages.
[00:44] <dijenerate> just set to boot then run the script
[00:44] <persia> There are a number of issues with using dd on an installed image for mass-production.
[00:45] <dijenerate> some of the packages are from our own repo and are foreign to ubuntu
[00:45] <persia> Some examples are that all installed devices would have the same initial cryptographic salt.
[00:45] <persia> Some tools contain information about volume sizes that are confused by grow_fs
[00:46] <persia> And some configuration of the system is *only* done by the installer.
[00:46] <dijenerate> hmmm... the thing is, so far we have done multiple lab trials and tests with the image and used dd for each install on test hardware
[00:46] <persia> Using foreign packages is not a problem at all.
[00:46] <dijenerate> we have scripts for the configs
[00:46] <dijenerate> so that is taken care of on first boot
[00:47] <dijenerate> it's a seriously hacked build
[00:47] <persia> Indeed.  I wish I'd caught you earlier in the process :)
[00:47] <dijenerate> lol... that would have saved us both a lot of probs at this stage eh?
[00:48] <persia> Yeah.
[00:48] <dijenerate> I wonder if we can still call this ubuntu or should it be renamed 'xyz distro based on ubuntu'?
[00:48] <persia> Are you using a swap partition?
[00:48] <dijenerate> sorta like mer
[00:48] <dijenerate> no swap part
[00:48] <dijenerate> single part install
[00:48] <persia> You can't call it "Ubuntu" if you modified it with stuff not in Ubuntu.
[00:49] <dijenerate> figured... we'll have to come up with a name for this one
[00:49] <dijenerate> it's extremely lightweight, like linux distros of old
[00:49] <persia> No swap partition solves some of the issues with resizing the filesystem.
[00:50] <dijenerate> yeah, we used the single ext4 from the get go to make installations 'easier'
[00:50] <dijenerate> so much for that
[00:50] <persia> Rather than using the installer :)  Heh.
[00:51] <dijenerate> the image is stored as a clean tarball with no lost+found, no bash history, no log files, not apt cache... it's clean as a whistle
[00:52] <dijenerate> just needs to be extracted to a bootable ext4
[00:52] <dijenerate> we created a dd image to take care of the installation of grub
[00:52] <persia> And the bootloader installed, etc.?
[00:52] <dijenerate> one less step
[00:52] <persia> I thought that grub stored the disk geometries in the config.
[00:52] <dijenerate> all scripts installed just needs the mbr
[00:53] <dijenerate> the mbr needs to know what the first boot device is
[00:53] <dijenerate> and what the fs of that device is... so still need to have the right mbr entry
[00:54] <dijenerate> other than the mbr entry, everything is in the tarball
[00:54] <persia> And how are you deploying the tarball, or is that what brings you here?
[00:56] <dijenerate> that's why I'm here
[00:57] <persia> Right.
[00:57] <dijenerate> I was trying to find an automated way to do it
[00:57] <persia> So, we have two installers.
[00:57] <dijenerate> it just needs to be extracted to root of a single bootable ext4 partition
[00:57] <dijenerate> then we install grub to the mbr and we're ready to go
[00:57] <persia> One of them does the base setup, then installs each package from a pool, then does final setup.
[00:58] <dijenerate> actually, they both do the same
[00:58] <dijenerate> neither has to install any packages
[00:58] <persia> The other puts the result of an installation of all the packages in a chroot into a squashfs, and then boots with that as a unionfs and runs some special scripts in the initramfs.
[00:58] <dijenerate> everything is in an installed state in the tarball
[00:59] <dijenerate> not even necessary
[00:59] <persia> I don't think the first will help you, as I have the impression that you'd end up needing to massively rework your configuration scripts.
[00:59] <dijenerate> we literally just have to extract the tarball to the bootable ext4 partition, install grub to the mbr and the system is ready to boot
[01:00] <persia> The second relies on there being an installer tool included in the squashfs, which would require modifications to your image that would not be preserved on deployment, which would probably mess up your prior testing.
[01:00] <dijenerate> the initial setup is for user id and network security config of the terminal
[01:01] <persia> So, if you wanted to use an Ubuntu installer, I'd suggest attempting to stuff your tarball into a squashfs, and trying that.
[01:01] <persia> But that might well be fairly painful as you have to differentiate the boot of the live image and the first-time boot.
[01:01] <persia> So, I think you need a new installer.
[01:02] <persia> Are you expecting mass-installs or end-user installs?
[01:03] <dijenerate> is there no way to get a live ubuntu disk to just boot, format the host drive according to a script, install grub to the mbr then extract the tarball to root?
[01:03] <dijenerate> mass installs
[01:03] <dijenerate> but it needs to be 'non-tech' proof for recovery or emergency installs
[01:03] <persia> There are lots of ways to do it, none happen to be recommended as an install method.
[01:04] <dijenerate> lol
[01:04] <persia> For your specific case, you might want to perform a minimal installation of Ubuntu Server (without any servers) onto a USB stick.
[01:04] <persia> Then copy your installation images into that media
[01:05] <dijenerate> well the installed doesn't need to be x-based either... a simple terminal with progress output is fine
[01:05] <persia> And then create an initscript that would perform the required actions to partition, create the filesystem, copy the data, etc.
[01:05] <persia> Ubuntu Server doesn't include X by default, which is why I suggested it :)
[01:05] <dijenerate> ok, perfect
[01:05] <persia> For mass-installs, bringing up a whole GUI is often considered slow.
[01:06] <persia> Again, this is not a recommended way to install, and I predict you'll encounter issues later.
[01:06] <persia> When that happens, I do encourage you to come back, and we'll look at how to create a mass-install image in a recommended fashion.
[01:06] <dijenerate> ok, thanks
[01:06] <dijenerate> lol
[01:08] <persia> Good luck.
[01:08] <dijenerate> thanks


[19:07] <foxmask> Jason-KR: I found the font I have in korean book i was looking for. "Batang" eg http://www.cours-coreen.fr/index.php?page=polices01 "UnBatang" or Baekmuk Batang. Remains one that mimics letters written by hand.
[22:02] <Jason-KR> 아~ 손글씨 비슷한? ㅋ     바탕 font를 보통 많이 씁니다. 순서(순위)없이 바탕체, 명조체, 고딕체, 굴림체 등등


[10:13] <kalikiana> timp: https://code.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/dontSkipTheEntiretyOfTstTextfield11Qml/+merge/308099
[10:34] <timp> kalikiana: happroved
[11:01] <kalikiana> timp: Another one
[11:01] <kalikiana> https://code.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/dropQuestionableColorTestsFromTstTextarea11Qml/+merge/308106
[11:01] <timp> kalikiana: standup :)
[18:39]  * ahoneybun pokes ahayzen
[18:39] <ahoneybun> alright so I have my JSON data here: http://api.openweathermap.org/data/2.5/forecast?q=32055&appid=753a953085551461ddf5555c772c06c2
[18:40] <ahoneybun> I need to figure out how to get each hour report out of there
[19:00] <ahayzen> ahoneybun, use JSON.parse() on it, like output=JSON.parse(input) then you should be able to loop through the result in output["list"] .. then each one you can get the info for
[19:01] <ahoneybun> well I have it like this now: locationModel.append( { id: entry["id"], name: entry["name"], weather: entry["weather"][0]["main"] } )
[19:01] <ahayzen> ahoneybun, also paste it in here, it helps you alot http://jsonprettyprint.com/ ... bbl o/
[19:01] <ahoneybun> but yea tried something like that
[19:01] <ahoneybun> ahayzen: http://pastebin.ubuntu.com/23309533/
[19:01] <ahoneybun> I have it working like that
[19:02] <ahayzen> gotta go shops, be back in a bit
[19:02] <ahoneybun> changing the api to just looking for one city weather works like a charm
[19:02] <ahoneybun> just trying to use a forecast is different
[19:04] <ahoneybun> seems I am using it: currentData = JSON.parse (request.responseText);
[20:09] <ahayzen> ahoneybun, it looks like what you have is going in the right direction :-)
[21:39] <ahoneybun> ahayzen: though I got the code from someone I think
[21:40] <ahoneybun> also not sure how to get data from that large json
[21:41] <ahoneybun> ["weather"][0]["main"] seems to grab all the items weather but I need more control on which it gets
[21:41] <ahoneybun> I want to list the first 3 or 4 items
[21:41] <ahoneybun> giving a 3 hour forecast for each