[10:28] <neil_d> where is the config file for the dhcpd server for the ltsp clients?
[10:29] <alkisg> /etc/ltsp/dhcpd.conf
[10:29] <neil_d> ah found it... don't worry.
[14:57] <JuanMarquez> buenas
[14:57] <JuanMarquez> alguien habla español?
[14:58] <JuanMarquez> i need build image ltsp client kernel 386 NOT generic, tell me more?
[16:02] <sbalneav> JuanMarquez: Not sure what you mean
[16:03] <sbalneav> You can build your image with ltsp-build-client --arch i386
[16:03] <sbalneav> Morning all
[16:04] <ogra> sbalneav, he wants a 486 compatible kernel, we discussed it in #ltsp
[16:06] <alkisg> Wow, is a 486 capable of booting (assuming it has the correct kernel)? I don't think I've seen a 486 with 64MB RAM yet :)
[16:08] <ogra> there are some x86 chips that only support the 486 instructions
[16:08] <ogra> early VIAs etc
[16:08] <ogra> and i think the very early geodes too
[16:10] <sbalneav> right.
[18:40] <JuanMarquez> i need in mi client LTSP Karmic linux-image-2.6.31-14-386 (not linux.image-2.6.31-14-generic), how to????
[18:43] <nubae> JuanMarquez: check the documentation, its in there...
[18:43] <nubae> !doc
[18:43] <nubae> or better check !doc in #ltsp
[18:44] <JuanMarquez> nubae, thks, the doc not help me
[18:45] <nubae> JuanMarquez: check the #ltsp channel and type !doc there
[18:45] <JuanMarquez> ok
[18:45] <nubae> the ubuntu docs are outdated
[18:52] <sbalneav> JuanMarquez: if there's no specific i386-instructions-only kernel available from Ubuntu directly, then I'd expect you'll have to compile your own kernel package...
[18:52] <sbalneav> JuanMarquez: https://help.ubuntu.com/community/Kernel/Compile
[18:53] <sbalneav> That should tell you how to rebuild a kernel package with whatever options you want.
[18:53] <JuanMarquez> sbalneav, thks
[18:53] <sbalneav> Once you have a compiled kernel .deb, you can then install it in the chroot manually
[18:53] <sbalneav> and after that, ltsp-update-kernels should install the custom kernel in the tftp area.
[18:59] <JuanMarquez> edubuntu pack can be install Xubuntu?
[19:02] <alkisg> JuanMarquez: how much RAM do your clients have?
[19:02] <sbalneav> alkisg: 64 meg
[19:02] <sbalneav> but they're pure 486's
[19:02] <alkisg> ok
[19:03] <JuanMarquez> 32MB and CPU P2 450MHz
[19:03] <JuanMarquez> Intel Board
[19:03] <alkisg> JuanMarquez: you can't boot LTSP with 32 MB RAM
[19:04] <alkisg> You need 64 MB
[19:04] <alkisg> (at least, not LTSP 5.0)
[19:05] <alkisg> And, P2 isn't a 486...
[19:05] <nubae> :-)
[19:06] <nubae> picky alkisg
[19:07] <JZA> highvoltage: ping
[19:07] <highvoltage> JZA: pong
[19:09] <JZA> highvoltage: hi, so let's try to get some work done on OOo4Kids
[19:09] <JZA> highvoltage: what can I do to help
[19:10] <highvoltage> JZA: that's the attitude! What's the project's website/webpage/wikipage? is it this page? http://wiki.services.openoffice.org/wiki/Education_Project/OOo4Kids
[19:12] <highvoltage> (sorry I see it points me to http://wiki.ooo4kids.org/index.php/Main_Page on that page)
[19:13] <JZA> yep
[19:14] <JZA> we spin it off to it's own wiki
[19:14] <JZA> http://download.ooo4kids.org/ is the download link
[19:15] <highvoltage> JZA: I hope you're patient enough to bear with my ignorance a bit... how do translations work? can it use openoffice translations?
[19:16] <JZA> highvoltage: yeah, we just have patches for specific diff
[19:17] <highvoltage> ok downloading binaries first (going to kill my connection for a bit)
[19:17] <JZA> ok
[19:17] <highvoltage> ah, going nice and fast, will be finished in 3 minutes :)
[19:21] <JZA> great
[19:39] <highvoltage> JZA: is there currently a PPA or any kind of debian packages done for OOo4kids?
[19:41] <mhall119|work> there are deb packages
[19:41] <mhall119|work> but no ppa
[20:22] <JuanMarquez>  can be generate hardy client in karmic server ltsp?????
[22:02] <jza_> hi
[22:02] <jza_> highvoltage: what are PPA?
[22:03] <highvoltage> jza_: Personal Package Archive. it's a repository hosted in launchpad where you can host development packages
[22:03] <jza_> highvoltage: is it somekind of proprietary debian/ubuntu thing?
[22:04] <jza_> highvoltage: so is it a package or a tree?
[22:04] <highvoltage> jza_: nope, although it only works with the debian packaging format so you wouldn't be able to use it with non-debian-like systems
[22:05] <highvoltage> jza_: it's a place where you can host packages
[22:05] <jza_> highvoltage: is it only works on debian, thats the definition of proprietary
[22:05] <highvoltage> jza_: https://help.launchpad.net/Packaging/PPA provides a pretty good overview
[22:06] <jza_> highvoltage: I see so why do we want to be there?
[22:06] <jza_> if we already have a development environment
[22:06] <highvoltage> jza_: you certainly don't want to move your development environment to a ppa
[22:06] <jza_> highvoltage: ok
[22:06] <highvoltage> jza_: however, getting a package into a PPA is very commonly the first step towards getting it into Ubuntu
[22:07] <jza_> highvoltage: so is like cooker for mandriva
[22:07] <highvoltage> jza_: it allowes users to easily install and test the package and also more developers to see it so that it can be in the best shape possible when included in the distribution(s)
[22:07] <highvoltage> jza_: yes, almost like cooker!
[22:07] <highvoltage> jza_: except that every developer has their own little cooker
[22:07] <jza_> highvoltage: I see
[22:08] <jza_> highvoltage: and it has to be derived from launchpad? or we can put that repo on our own server?
[22:08] <jza_> highvoltage: by our own I mean any server
[22:09]  * jza_ clicking on the url
[22:10] <jza_> ok got it
[22:11] <jza_> is like CWS (Child Workspace)
[22:11] <highvoltage> jza_: yep, it doesn't prevent you from hosting the package(s) anywhere else. you could even use debmirror to automate the mirroring of it to any ohter server.
[22:13] <JZA> highvoltage: ok I will talk to eric about this, to see what we can do. He is the core developer of the build guy.
[22:13] <JZA> highvoltage: I am sure we can do something about this.
[22:14] <highvoltage> JZA: great. feel free to point Eric to here and #ubuntu-motu as well if he's interested in learning packaging.