[12:37] <rhce7321> I have got my ist thin client up to a boot prompt,   But I get the message :
[12:37] <rhce7321> "This workstation isn't authorized to connect to server"
[12:38] <rhce7321> I'm updatein ssh-keys & image in attempt to fix.
[12:41] <rhce7321> Woo-hoo!!
[12:41] <rhce7321> got my 1st client desktop.
[12:43] <ogra> congrats :)
[16:21] <LaserJock> morning all
[16:50] <sbalneav> Morning LaserJock
[16:51] <LaserJock> why, it's my favorite Canadian!
[16:52] <sbalneav> So, when do you want to do a triage day?  Maybe Next week sometime? I can take a work-at-home day.
[16:54] <LaserJock> sbalneav: whenever you're available dude
[16:54] <LaserJock> the sooner the better
[16:54] <sbalneav> Why don't we tentatively say next wed.
[16:54] <LaserJock> ok, that sounds lovely
[16:55] <LaserJock> today I think I should have the meta packages worked out
[16:55] <LaserJock> so we're making some progress towards Intrepid
[16:55] <LaserJock> Caroline has been doing some wicked triaging :-)
[16:56] <LaserJock> right now we have ~ 220 open bugs
[16:56] <LaserJock> I think we need to get through them all before Intrepid is out
[16:57] <LaserJock> I've seen a number of really old or misfiled ones
[18:41] <Goosemoose> My auto install using preseed.cfg is stopping and asking for kerberos servers
[18:41] <Goosemoose> I don't see what command should be answering that questions, any ideas?
[18:42] <sbalneav> Hmm, not sure, I've never done a preseed.
[18:42] <sbalneav> This on Hardy>
[18:42] <sbalneav> ?
[18:42] <Goosemoose> yes
[18:43] <Goosemoose> I didn't have this issue with feisty
[18:49] <sbalneav> Hmm.  Not sure.
[18:49] <sbalneav> ogra's not around at the moment, he'd be the one to ask, likely
[18:58] <Goosemoose> ok
[18:58] <Goosemoose> i cant find anything on it online either
[22:15] <Goosemoose> hmm, my preseed has : tasksel tasksel/first multiselect edubuntu-desktop but when them machine booted just came to the terminal
[22:15] <Goosemoose> why didnt it start with the desktop?
[22:18] <Eghie> Goosemoose: I think you should also select a desktop with taskel
[22:19] <Eghie> ltsp-build-client also works without a desktop
[22:19] <Goosemoose> hmm
[22:20] <Goosemoose> so edubuntu-desktop, standard ?
[22:21] <Eghie> you could do that yes
[22:21] <Eghie> but you can also choose xubuntu-desktop or just ubuntu-desktop
[22:22] <Eghie> ltsp is building a client which can be loaded via PXE (network) and it connects to X of the server
[22:22] <Eghie> then you can choose which desktop you want to run
[22:22] <Goosemoose> im not running ltsp
[22:22] <Goosemoose> they are getting an actual install on the hard drive
[22:23] <Eghie> ah, sorry, I've read it wrong i guess
[22:23] <Goosemoose> no problem , answer minght be the same
[22:23] <Eghie> edubuntu-desktop should indeed install a full desktop
[22:23] <Eghie> and also boot up in X
[22:24] <Goosemoose> ok
[22:24] <Eghie> it could be a advantage above ubuntu-desktop, because they both use gnome
[22:24] <Eghie> if that's so, you also should install ubuntu-desktop
[22:28] <Goosemoose> ok
[22:28] <Goosemoose> how do i set which loads then?
[22:29] <Eghie> they both run on Gnome, so that shouldn't matter
[22:29] <Goosemoose> ok
[22:29] <Goosemoose> do you have any idea why this would give me an error:
[22:29] <Goosemoose> d-i preseed/late_command string wget http://10.0.2.131/post_install_tasks && chmod +x ./post_install_tasks && ./post_install_tasks
[22:29] <Eghie> but you can set the edubuntu theme if you want on ubuntu-desktop, if it's not already showing up
[22:30] <Goosemoose> the file is publicly accessible
[22:30] <Eghie> what error?
[22:30] <Goosemoose> but im getting a error 127
[22:30] <Eghie> ah
[22:30] <Goosemoose> failed with exit code 127
[22:30] <Goosemoose> the file just joins the domain
[22:31] <Eghie> is it wget which returns 127 or the post_install_tasks?
[22:31] <Goosemoose> i cant tell
[22:31] <Eghie> you could try to leave the executing of post_install_taks of
[22:32] <Eghie> off
[22:32] <Eghie> and then see if it still gives the error
[22:32] <Goosemoose> ok, just to see if wget works
[22:32] <Goosemoose> ok, just asec
[22:32] <Eghie> ok
[22:36] <Eghie> Goosemoose: what about the command: eval `wget -q http://10.0.2.131/post_install_tasks -O-`
[22:37] <Goosemoose> what does that change?
[22:37] <Eghie> the same as you try to achieve
[22:37] <Eghie> but in 1 command
[22:37] <Goosemoose> lol, gotcha
[22:37] <Goosemoose> ahh isee
[22:37] <Goosemoose> so that gets rid of the chmod statement?
[22:37] <Eghie> although eval must exists when you run it
[22:37] <Eghie> yes
[22:37] <Goosemoose> i've never seen -0-
[22:38] <Eghie> it says, -O- = output to STDOUT
[22:38] <Eghie> so output as normal text
[22:38] <Eghie> and eval will execute that text
[22:39] <Goosemoose> gotcha
[22:39] <Goosemoose> ill see how the normal wget works in a minute, its almost there
[22:39] <Eghie> ok
[22:39] <Eghie> ah man, I don't like using gnome-watchdog :S
[22:40] <Goosemoose> I have it down to just asking one questions during preseed which is about overwriting an exist partition
[22:40] <Eghie> ok
[22:40] <Goosemoose> but it set it to say yes in the preseed.cfg
[22:40] <Goosemoose> so im not sure why
[22:40] <Goosemoose> i had to figure out a bunch of kerberos stuff earlier that i dont remember doing in feisty
[22:41] <Eghie> it depends if you want to use kerberos or not
[22:41] <Goosemoose> ahh it must be asking because i installed likewise-open as a package
[22:41] <Eghie> if you are using an active directory domain, well kerberos would by handy
[22:41] <Eghie> ah
[22:41] <Goosemoose> yeah
[22:41] <Goosemoose> thats why it added it in there
[22:41] <Goosemoose> it took awhile as i haven't figured out how to discern the correct commands for each screen yet
[22:41] <Eghie> kerberos is a bit difficult, but really nice
[22:42] <Goosemoose> likewise is nice
[22:42] <Goosemoose> i had AD working with kerberos before with a manual job
[22:42] <Goosemoose> took like 45 minutes to do
[22:42] <Goosemoose> likewise joins in seconds
[22:42] <Goosemoose> install and go
[22:42] <Eghie> hehe, that's correct
[22:42] <Eghie> they are doing a great job
[22:42] <Goosemoose> i love it
[22:42] <Goosemoose> if i can just get it working during preseed ill be set
[22:42] <Goosemoose> i did see it was installed last go
[22:42] <Eghie> I hope it will work at the same speed on a Samba 4 server
[22:42] <Goosemoose> just need the script to execute to join automatically
[22:43] <Goosemoose> im sure it will
[23:06] <Lns> Did I miss the meeting?
[23:08] <Lns> I see nothing on the fridge regarding it, though the link in topic is valid..
[23:11] <HedgeMage> Lns:  if there is a meeting, it will likely be in #ubuntu-meeting
[23:12] <Lns> HedgeMage: thanks.
[23:12] <HedgeMage> np :)
[23:12] <Lns> I sure did miss a hot thread on edubuntu-users the past couple days!
[23:16] <LaserJock> Lns: *next* Wednesday
[23:16] <Lns> LaserJock: oh
[23:16] <Lns> damn.. i was hoping to have every single bug fixed by today. :p
[23:25] <LaserJock> heh
[23:25] <LaserJock> good luck with that
[23:26] <Lns> I have an idea
[23:27] <Lns> although a bad thing to ask here... it seems as though there are so many issues going on here, and so many people voicing their issues on the mailing list, it seems impossible to track them all and see HOW many people are having specific issues.
[23:27] <Lns> I think LTSP needs its own tracker for LP bugs...
[23:28] <Lns> maybe just a static page that lists LTSP, Edubuntu specific things (related and non-related directly to LTSP packages, such as issues with Gnome and it's LTSP integration)
[23:34] <LaserJock> Lns: well, we do have a bug tracker, it's called Launchpad :-)
[23:34] <Lns> LaserJock: i know :)
[23:34] <LaserJock> if a bug is LTSP specific it should be filed against ltsp
[23:34] <Lns> right
[23:34] <LaserJock> if it's not LTSP specific we need to find the right package to file against
[23:34] <Lns> but most bugs people encounter aren't ltsp specific
[23:35] <LaserJock> right!
[23:35] <Lns> though they are happening because of the thin-client env
[23:35] <Lns> it's at that point, imho, people stop trying to help
[23:35] <LaserJock> so that's why we need to get some people to help triage these things so they can find proper homes
[23:35] <Lns> because they came to where they thought they should
[23:35] <Lns> mmk
[23:35] <Lns> i'm not very familiar with triaging
[23:35] <Lns> maybe that's what i'm missing
[23:36] <LaserJock> well, I think that's a very general problem around Edubuntu
[23:36] <LaserJock> we don't generate a ton of bugs so we're not very familiar with bug processes
[23:36] <Lns> true
[23:36] <LaserJock> but I think if we were generating more bug reports and doing more triaging, things would start to flow better
[23:36] <Lns> i agree
[23:37] <LaserJock> instead of sending complaints to mailing list threads that will be forgotten next week :-)
[23:37] <Lns> mmk..i'll do some reading on triaging bugs...maybe the best place is to look in LP for ltsp specific bugs and start churning through everything
[23:37] <Lns> LaserJock: exactly
[23:37] <Lns> which, unfortunately, usually contains the data necessary to troubleshoot effectively
[23:37] <Lns> (along with all the harsh commentary)
[23:38] <LaserJock> I've been thinking a little about how to help people do better with bugs in Edubuntu
[23:39] <LaserJock> Ubuntu runs (and just did one) the Ubuntu Developer Week every so often
[23:39] <LaserJock> I wonder if we could do something sort of smaller scale for Edubuntu
[23:39] <LaserJock> the main problem I've seen is that most edu people don't like IRC
[23:39] <LaserJock> which makes running tutorials or help sessions very difficult
[23:40] <Lns> that's what i see is a larger issue as well - too many facilities
[23:40] <Lns> people aren't dumb, but fragmented information gets nowhere fast
[23:41] <LaserJock> well, it isn't so much fragmented, IMO
[23:41] <LaserJock> but Edubuntu people don't seem to "plug in" to Ubuntu resources very well, from what I've seen
[23:42] <Lns> i agree, and i'm one of them
[23:42] <LaserJock> which I suppose comes from it being sort of a niche area
[23:42] <LaserJock> if I could just get everybody on IRC for *1* hour we'd be on a roll
[23:42] <johnny> how about web based..
[23:42] <johnny> so they don't have to setup a client
[23:42] <johnny> just go to a web page
[23:43] <Lns> johnny: that's exactly what i was thinking
[23:43] <LaserJock> well, that requires a lot
[23:43] <johnny> a lot of what?
[23:43] <LaserJock> time, resources
[23:43] <johnny> huh?
[23:43] <Lns> i'll help
[23:43] <johnny> to set it up
[23:43] <johnny> not really
[23:43] <LaserJock> not set up
[23:43] <Lns> web-based irc client?
[23:43] <LaserJock> oh wait
[23:43] <Lns> 2 birds/1 stone.. heh
[23:44] <LaserJock> johnny: did you mean a web-based IRC client?
[23:44] <johnny> yes
[23:44] <LaserJock> I was thinking you meant replacing IRC with web-based learning
[23:44] <Lns> we don't need another facility :p
[23:44] <LaserJock> well, there are web-based clients around aren't there?
[23:45] <LaserJock> is it port blocking that's the issue?
[23:45] <Lns> it would be so cool to have a central - *buntu thin-client environment - facility that links to everything
[23:45] <Lns> including web-based EVERYTHING..irc, list archive, etc
[23:45] <LaserJock> Pidgin is installed by default and is fairly easy to set up for IRC (even though it's not the best client)
[23:47] <LaserJock> I've been thinking of writing a "Contributing to Edubuntu" guide to stick on edubuntu.org
[23:47] <LaserJock> just to get people on to the right resources around Ubuntu and familiar with how things work
[23:48] <LaserJock> a bit of a problem is I'm not entirely sure what people need, I've been doing this too long :-)
[23:48] <Lns> you know what i think might be better...and i'll do it if people think it's a good idea
[23:48] <Lns> if we're talking about trying to centralize information and communications
[23:49] <Lns> is create a completely new domain that covers Edubuntu, Ubuntu, Xubuntu, others such as RH/Fedora/Mandrake/whatever, in thin-client environments
[23:50] <LaserJock> something like ltsp.org ? :-)
[23:50] <Lns> lol
[23:50] <johnny> just trying to remove more barriers
[23:50] <johnny> well.. i think ltsp.org needs a web admin
[23:50] <Lns> johnny: i couldn't agree more
[23:50] <johnny> it doesn't really have anybody that takes care of it
[23:50] <Lns> that site is ancient
[23:50] <Lns> it *is* the perfect domain name though
[23:50] <johnny> anyways.. i have to run and i'll be back in a few
[23:50] <Lns> thx johnny
[23:52] <Lns> there isn't much software that is so boundary-less like ltsp is
[23:52] <Lns> cross-distro, cross-package, cross-community
[23:52] <LaserJock> right
[23:52] <LaserJock> well, there clearly is a need for LTSP to document itself
[23:52] <LaserJock> and sbalneav has done a lot of that in the past
[23:53] <Lns> but where to put the awesome documentation?
[23:53] <Lns> so people can find it easily
[23:53] <LaserJock> well, we *did* put it right on their computers
[23:53] <Lns> which seems sensible
[23:53] <LaserJock> but we didn't have enough "hands" to get it updated for Hardy so it was not shipped
[23:53] <Lns> but doesn't cover irc, list communications, current issues
[23:54] <LaserJock> no
[23:54] <Lns> brb