[00:06] hugin is a pano stitcher [00:06] RichEd: [03:26] anyone here? [03:31] LaserJock: ??? [03:39] nubae: yep? [03:45] ah just checking... :-) but wanted to quickly touch base vis a vis sugar... should I include it in the apps? [03:45] for edubuntu [03:45] the website [03:46] no [03:46] cool, so u think it will be after Jaunty? [03:47] I'd like to see it *for* Jaunty [03:47] still requires many bug fixes I believe, but would be nice for sure [03:47] but since it's not in I don't think it's a good idea to put it on a list [03:49] btw, I wrote an article about collaboration on gnome/ubuntu: http://nubae.com/telepathy-empathy-and-collaboration [03:54] nubae: do you have app lists for hardy and intrepid? [03:55] just intrepid I believe [03:56] is it different from hardy? [03:56] yes [03:57] nubae: is the intrepid list up on edubuntu.org? [03:57] not yet... almost finished [03:57] I'm using the spreadsheet riched gave me [03:57] I'm not trying to rush ya, just wondered ;-) [04:00] its just html at the moment, no database [04:01] no problem [04:19] nubae: i'm glad ur here [04:19] nubae: no blender [04:48] http://ultrastardx.sourceforge.net/about-ultrastar-deluxe/ - singing [06:02] nubae: just got done reading through your telepathy post [06:02] nubae: looking at your screenshot of empathy, it does look much improved since I last tried it [07:23] lpairs is an interesting childs memory game [11:59] I found this cute computer http://www.norhtec.com/products/mcjrsx/index.html it has a CPU without a floating point unit, can I use it as a LTSP terminal ?\ === bddebian2 is now known as bddebian [16:12] looking at fat clients, possible to boot from wireless and use the fat client via wireless? [16:53] hey Ahmuck, am back now [16:53] I live in Austria, so times are slightly different for me :-) [16:55] yes, i wondered about that [16:55] i'm back as well [16:55] Ahmuck: I'm working on just that... since ltsp cannot normally do wireless due to bandwidth restrictions, fatclient is perfect for it [16:55] so, it does not appear i have fat clients yet. should i just re-run the script? [16:55] nubae: u have a wireless fatclient? [16:57] well lets analyse the problem first... pastebin me your /etc/inetd.conf [16:57] and your /etc/ltsp/dhcpd.conf [16:57] I'm working on wireless fat client, don't have it yet [16:58] k, brb [16:59] whats holding up the wirless fat client? [16:59] time :-) [17:00] i was just thinking one could turn just about any wireless laptop into a fat client so it wouldn't matter what os the client had installed [17:00] er, just got to thinking after what you said [17:01] right, the idea though for wireless is that it has the most minimal kernel for booting up the wireless drivers and then connect to the dhcp server [17:02] to download the rest to memory [17:10] ltsp is a powerful concept that i think could be expanded further with software addons by default [17:11] software addons? [17:11] http://pastebin.be/15560 [17:12] http://pastebin.be/15561 [17:13] \o/ two in a row, 15560 n 15561 [17:13] oh and your fatclient pxe config file [17:13] /var/lib/tftpboot/ltsp/fati386/pxelinux.cfg/default [17:14] the error is probably in there, needs to be set to port 2001 [17:14] otherwise indeed it just loads up your regular thin client [17:17] Ahmuck, your server has ip address 192.168.0.1? [17:17] http://pastebin.be/15562 [17:17] the server is default [17:17] until i can get this nailed down [17:17] i'm still testing though the thin client side is working [17:18] ok, theres your problem [17:19] u need nbdport 2001 at the end of your default [17:20] k, i assume that was missing from your script or didn't complete ? [17:21] well, we manually copied the whole /var/lib/tftpboot/ltsp/i386 dir over [17:22] i think we still have a problem, no blender [17:23] hrmmm... yeah looking at my own setup, one doesnt seem to need the nbdport def in default anymore... [17:23] ok, just delete /opt/ltsp/fati386 and redo the image [17:24] so, copy the new script, and then rebuild the image? [17:25] yeah, just to be sure, download the script from my site again [17:26] er, did you remove the script link ? [17:27] no, just the hardy one... [17:28] let me look :-) [17:28] * Ahmuck-Jr can't find the intrepid one either [17:29] oops [17:29] :) [17:32] so is ltsp currently the only way to get centralized login, storage, etc. for students? [17:32] on linux [17:32] ok, check now [17:32] more or less yes, one can also use drbl, and various commercial solutions [17:33] but LTSP is by far the best and most vibrant solution [17:39] /usr/share/ltsp/plugins/ltsp-build-client/ubuntu/030-fatclient !== /usr/share/ltsp/plugins/ltsp-build-client/(U)buntu/030-fatclient [17:43] nubae: k, building [17:43] catch the syntax error i noted for ubuntu/Ubuntu on the blog entry? [17:44] think so, did I? [17:44] it's baaack :) [17:44] It has been fully tested on Ubuntu Intrepid Ibex. Instructions are to save the corresponding file to /usr/share/ltsp/plugins/ltsp-build-client/ubuntu/030-fatclient [17:45] changed, thanks... [17:49] managed ltsp servers, with load balancing ? would this have to be done with every one? [17:50] not sure what u mean [17:50] isn't there a way to have multiple ltsp servers and they hand leases off to clients as they get them? [17:51] * Ahmuck digs around in my logs [17:51] ltsp-cluster [17:51] u mean [17:53] yes [17:53] i'm still learning the ltsp terms and etc. [19:17] greets LaserJock [19:36] hi nubae [20:37] nubae: http://pastebin.be/15567 [20:49] nubae: it appears that worked. it's working now, i know because i now have a edubuntu login screen [20:52] oh yikes, erk, erm. that replaced the entire ubuntu desktop with edubuntu desktop, applications, menu's, and all [20:57] rihgt [20:57] right [20:57] so u have blender? [21:04] yes, i now have fat clients. but i've lost my customized menus, and the webpage opens up to say welcome to edubuntu 8.04 [21:04] this is a good thing. [21:04] i'd like to post your blog post as part of documentation i'm going to do on step by step ltsp setup with screenshots and all [21:04] if you'll let me. i do have some other questions [21:05] awsome... [21:05] ask away [21:05] i learn by theory first and then by syntax [21:05] so, i somewhat interested in the theory of how this works. but for another day [21:06] I'm here now so any questions I can answer [21:06] secondly, i noticed you have "packaged" applications in your script. i assume that the script could be customized to create a set of applications and without replacing the menus? [21:06] absolutely [21:07] i need to look over your script, and then layout the how and why this works [21:07] as i believe in education as well as why it works. [21:08] its really quite simple, I took the existing thin client script and adapted it to install the apps we want, there are some basic requierd apps, and then the rest is cutomised to how u want it [21:09] something i noticed is that you used the edubuntu icon set and theme. i would assume i could pull this from edubuntu itself as an icon set and theme and then do similar to what kde does and just apply it as a theme, therefor creating a set of "canned" themes students could choose from [21:09] I've also use it do adapt to creating a xubuntu desktop and a kubuntu desktop [21:09] ah, ok. that sounds interesting [21:10] do you have sepearte scripts for xubuntu and kubuntu? [21:10] well its pretty simple, as a base. pull in xubuntu-desktop or kubuntu-desktop [21:10] and then layer on top [21:13] so i assume that your fat client has a customized menu? [21:13] is that "local apps" ? [21:13] nope [21:13] * Ahmuck is still confused about the "local apps" thingy [21:13] this was before localapps, its just what u put into the package list [21:14] local apps is regular thin clients with one or two apps running on the fat client [21:14] fatclient is everything running on the client [21:14] ah, ok [21:15] there are advantages and disatvantages on both sides, though I believe fatclient is much more cutomisable [21:15] so if you have a fat client why would you need a local app unless your running mixed clients ? [21:15] u dont [21:15] so the local app applies only to the thin client [21:15] right [21:15] and the fat client gets a fully loaded local app menu [21:15] *blink* *blink*, a light bulb comes on [21:16] floresant of course to save power [21:17] so now i need to start looking at sugar, course management, etc. [21:17] the foundations done, now i need the walls [21:17] and then the roof and all the nice apps for the furniture [21:18] is there a way for ltsp to query a thin client every 30 boots and set the hardware specs for that client and then lockout certian desktops? [21:30] italc [21:30] but its not time based [21:30] its manual [21:37] it's doesn't do it automagially by client hardware specs either i don't suppose [21:38] give me a use case scenario [21:44] bring in 3 new pc's or deploy a new ltsp server to usd xx in the county school district, the server starts, peeks at the config of the pc's connecting, builds a profile of each one and sets thin/thick clients in the dhcpd.conf based on mac address and specs [21:44] or a gui to do so. [21:44] like a spec, with a green icon for fat client and an option to check [21:44] k, anyhow, i'm getting ahead of myself [21:45] the school distircit here is on citrix, which i understand is a real pain to get around in [22:05] well citrix is the microsoft ltsp solution [22:05] though it sucks [22:08] lol, did not realize that [22:08] it uses ltsp ? [22:08] really? [22:08] no [22:08] the thin clients are already there, the network is already there [22:08] just seems like it :-)