[02:15] <wolfravenous> I am a teacher trying to setup an edubuntu LTSP system, I have setup K12LTSP in the past, about 5 years ago, but wanted to try edubuntu for the new school I am at, but I am not having any luck can anyone help me?
[02:17] <wolfravenous> I have setup and installed the software but my test thin client doesn't connect and I don't know how to check from the server to see if it is actually working as an LTSP server and broadcasting
[02:19] <wolfravenous> downloaded a GUI tool from the software center, ltsp-manager, but when I launch it from a command line it pops up a window that says "select LTSP network" but the window is completely blank?
[02:22] <wolfravenous> is there anyone in here or is all 23 idents just robots???
[02:23] <HedgeMage> wolfravenous: Calm down...many of us idle here when we aren't at our computers.  The rest of us won't answer unless we know the answer, that's IRC manners.
[02:23] <joe__> He all...
[02:23] <HedgeMage> wolfravenous: I'm sure if you hang out a while, someone with LTSP experience will wake up.  It's not my area of expertise.
[02:23] <HedgeMage> hi, joe__
[02:23] <joe__> Funny :) I'm here for LTSP help :)
[02:24] <HedgeMage> lol, then I'm afraid I won't be of much use to you.
[02:24] <wolfravenous> Ok thanks, I was begining to worry the community page told me to setup IRC and come here for help
[02:25] <wolfravenous> was afraid there was noone here
[02:25] <joe__> I'll try anyway :)  I'm at the very begining... Ever get the LTSP to work on the live cd?
[02:25] <joe__> I don't seem to get it to offer a DHCP response
[02:26] <joe__> I'll try #LTSP... Thanks!
[02:27] <HedgeMage> wolfravenous: np :)
[02:27] <HedgeMage> wolfravenous: The manners on IRC can be a little odd to newbies :)
[02:28] <wolfravenous> I probably made a major mistake, I have an old SCSI server, without DVD rom, so I put an IDE card in a PCI slot then cabled the IDE card over to the DVD rom in my tower and installed the software on the SCSI server that way.
[02:30] <wolfravenous> I had two 10/100 NICs installed in the server when I setup the LTSP immediately after the Edubuntu install.
[02:31] <wolfravenous> I setup the LTSP on Eth0, and tried to test LTSP with my tower, but the CD I burned from ROM-o-Matic wouldn't recognize the Onboard NIC in my tower, SO,
[02:32] <wolfravenous> I went out an bought a Giga NIC to put in the server, and put the other 10/100 in my tower.
[02:33] <wolfravenous> Now the ROM-o-matic CD recognizes my towers (thin client) NIC and tries to boot as a thin client but the server didn't seem to be broadcasting DHCP.
[02:33] <wolfravenous> I went back into the servers network settings and it had named the new Giga NIC eth2
[02:34] <wolfravenous> I changed the name to eth0 but it still doesn't seem to work.
[02:35] <wolfravenous> I even tried downloading the LTSP-Live package from the software center and running that again to establish a "live" LTSP but still no dice!
[02:35] <HedgeMage> :/
[02:37] <wolfravenous> Problem is I am completely new to edubuntu so I don't even know where to start, in K12LTSP five years ago I might have had a clue but I haven't delt with this stuff in five years, heehe
[02:50] <wolfravenous> HedgeMage: Wow, community has changed in 5 years, just went to LTSP channel and asked simple ? of how to check to see if Eth0 is broadcasting DHCP and noone replied out of over 60 idents.
[02:51] <HedgeMage> wolfravenous: it's a Thursday night (at least here in the US) and it's conference season in the tech world (for example Drupalcon is going on right now, not sure what else)
[02:51] <HedgeMage> edubuntu tends to be oddly active in the afternoons (US time) which is abnormal for open source channels in general
[02:52] <wolfravenous> HedgeMage: then went to k12ltsp channel and I was alone in there?  What happened to the K12ltsp community or do you know???  I am in the US, GA to be exact.  Used to run K12 and evangalize Linux up in NC.
[02:52] <HedgeMage> Ahh, I got married in Augusta, GA many moons ago :)
[02:53] <HedgeMage> k12ltsp seems to have dried up a long time ago, though not as long ago as debian-edu
[03:24]  * squidly waves
[10:11] <AlanBell> morning all
[10:12] <AlanBell> if any UK based folk want to express why IT teaching in school sucks please go here http://royalsociety.org/Education-Policy/Projects/ and tell the royal society, they are doing a call for evidence on the subject. It would be good to have a bunch of responses emphasising the importance of programming and Open Source software above teaching proprietary word processing applications as IT
[11:28] <Ferdinand> Hi
[11:29] <Ferdinand> any person here?
[11:29] <alkisg> !ask
[11:31] <Ferdinand> in the Edubuntu version 10.04 has been chosen, as a wallpaper, a picture of Mads Rosendahl. It is actually a modified image from one of my photographs. A I do not care to be used as wallpaper for Edubuntu, in fact I presented as background for Ubuntu. The problem is that I'd like authorship was recognized in Edubuntu documentation and the wiki.
[11:32] <Ferdinand> my original photo: http://www.flickr.com/photos/ferranreyes/3940702899
[11:32] <alkisg> Thank you for the background Ferdinand. highvoltage ^^^ ?
[11:32] <Ferdinand> what?
[11:33] <alkisg> I'm just pinging a person that might know more about the wallpaper
[11:33] <alkisg> Just stick around for a while until he sees your message, if you have time...
[11:33] <Ferdinand> ah, thx :)
[11:34] <Ferdinand> i'm spanish and my english is poor, sorry :$
[11:34] <alkisg> No problem. If you're in a hurry, you can also leave an email, I'm sure he'll contact you later on.
[11:35] <Ferdinand> In the past i try to contact with mail to canonical and edubuntu but i never had a response
[11:35] <Ferdinand> i can expect
[12:11] <Ferdinand> hi?
[13:12] <Ferdinand> alksig new news?
[13:13] <alkisg> Fedriandn: from me? No, I don't know anything about the wallpapers.
[13:14] <alkisg> You can also leave an email for highvoltage to contact you
[13:21] <Ferdinand> how can i leave an email for he?
[13:31] <Ferdinand> alking you can give me his mail?
[13:35] <alkisg> Ferdinand: you can send a mail to the edubuntu mailing list
[13:35] <alkisg> It's on the ste
[13:36] <Ferdinand> but for this i need subscribe me at the mailing list no?
[13:36] <alkisg> No
[13:36] <alkisg> But your mail will be needing moderation
[13:37] <alkisg> (i.e. it will stay for a few days if you are not subscribed)
[13:38] <Ferdinand> ok, thx!
[13:39] <Ferdinand> alkisg what's the best mailist? Edubuntu-users?
[13:40] <alkisg> Either that, or edubuntu-devel
[13:43] <Ferdinand> ok thx
[14:41] <mhall119> highvoltage: can you tell me again where the edubuntu seed files are?
[15:21] <highvoltage> mhall119: https://code.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/edubuntu.maverick
[15:23] <mhall119> thanks
[16:38] <priyanksingh_> how to wireless boot the clients through ltsp??
[17:15] <dgroos> I'm confused.  I went to update my chroot and got a bucket of errors.  So I went to check the sources.lists that is in my chroot (/opt/ltsp/i386/etc/apt) and there were just 3 lines there!  I assumed that I had already populated that but I guess not...
[17:15] <dgroos> So, how do I do that since my server is arch of 64 and my clients are 32?
[17:15] <dgroos> Or am I totally off base!?
[17:19] <alkisg> dgroos: what are those 3 lines? e.g. in "deb http://archive.ubuntu.com/ubuntu lucid main restricted universe multiverse" ==> even multiverse is there
[17:19] <dgroos> deb http://archive.ubuntu.com/ubuntu lucid main restricted universe multiverse
[17:19] <dgroos> deb http://security.ubuntu.com/ubuntu lucid-security main restricted universe multiverse
[17:19] <dgroos> deb http://archive.ubuntu.com/ubuntu lucid-updates main restricted universe multiverse
[17:19] <dgroos> nothing more.
[17:19] <alkisg> Yup, that's fine, are you looking for something more?
[17:20] <dgroos> Don't I need stgraber's and your ppa's?
[17:20] <dgroos> and besides, I get a boat load of errors of not finding repositories (Including the ones I just mentioned)
[17:21] <alkisg> Is your resolv.conf correct?
[17:21] <alkisg> (sorry, visitors, bb in a while...)
[17:22] <dgroos> I just 'fixed' it... so not sure...  I'll un-fix and see what happens...
[17:22] <dgroos> for sure.
[17:27] <mhall119> highvoltage: https://wiki.ubuntu.com/Edubuntu/AppGuide
[17:27] <mhall119> starting my UGJ early
[17:28] <Ricmat> Hello again.....I got some good suggestions yesterday, but can't figure something out.  Once you have set up a computer with apt-proxy, how do you get the other computers on the subnet to go to that computer to download software from there - instead of going to the internet?
[17:37] <Ricmat>  
[17:39] <alkisg> dgroos: to add mine or stgrabers ppa, use add-apt-repository in the chroot
[17:39] <mhall119> sorry Ricmat, I'm not familiar with that
[17:39] <alkisg> (those go in /etc/apt/sources.list.d - you should already have mine if you have sch-client)
[17:42] <Ricmat> In "Software Sources", "Other Software" , "Add", there's an option to enter the complete APT line of the new source repository.  My "server" has a fixed IP, but where is the Edubuntu stuff that I downloaded to the server machine.?  Or am I in the wrong area here totally?
[17:43] <alkisg> Ricmat: is that on a client, trying to make it use apt-proxy on the server? (I didn't see what you said above...)
[17:44] <Ricmat> Yes - I've installed apt-proxy on the server, and downloaded the edubuntu software to that server.  The server has a fixed IP.  I'm trying to set up clients to install from that server instead of going to the internet.
[17:45] <alkisg> Did you follow the steps in https://help.ubuntu.com/community/AptProxy ?
[17:47] <Ricmat> I haven't gone through the document although I do have it.  I was hoping (beyond hope?) that there would be some easy setup from e.g. "software sources" or something.  I'll try to go through the document on a client and see what happens.  When it says "deb" is that something to do with "Debian" or is it a command?
[17:48] <alkisg> For apt-proxy, you need to go through that document
[17:48] <alkisg> The server cache cannot be used without a program
[17:48] <alkisg> You can *copy* the cache though, manually, if that seems easier to you (it isn't)
[17:49] <alkisg> /var/cache/apt/archives/
[17:49] <Ricmat> OK - wish me luck!
[17:49] <alkisg> ==> that's where the .deb files are. If you manually copy all those files, then the clients won't download much data
[17:50] <alkisg> ...of course you'd need to do that for every major update afterwards too... that's why I'm saying apt-proxy is better, because you'll do it just once and never bother with it anymore.
[17:53] <Ricmat> OK - at this point, I think I'll just download everything from the net.  I need to have this stuff up and running X20 by Monday morning.....
[17:54] <Ricmat> Thanks for trying, but I guess I'm more of a windows guy.  :-(
[17:54] <Ricmat> When I get more time, I'll come back and see if I can make this all work.  Bye for now.
[18:07] <mhall119> Nice Qimo review on Linux Today: http://maketecheasier.com/review-of-qimo-linux-for-kids/2010/08/26
[18:10] <highvoltage> mhall119: whoah, nice!!!
[18:10] <highvoltage> (@ the app list stuff)
[18:10] <highvoltage> and nice review on qimo too
[18:10] <mhall119> thanks
[18:10] <highvoltage> we should link to that wiki page from the screenshots page
[18:11] <mhall119> the list and pages were generated from the seed files + apt-cache with a bit of Perl magic
[18:11] <highvoltage> really nice
[18:20] <mhall119> highvoltage: https://wiki.ubuntu.com/Edubuntu/AppGuide/AppDocScript
[18:20] <mhall119> for future reference
[18:34] <dinda> mhall119: can you send me your email addy?  have some good news :)
[19:20] <highvoltage> dinda: that list kind of helps that issue you mentioned where people keep asking what's included :)
[19:24] <dinda> highvoltage: yes, that's exactly what we've been looking for :)
[19:27] <dgroos> hi alkisg.  I've done lots of further attempts and reading and it looks like that I first need to resolve the issue of my /etc/network/interfaces defines the WAN-facing nic as using dhcp not static.
[19:28] <dgroos> I can't get firefox to work on clients with a static setting.  Do I need to do the resolv.conf fix for firefox?
[19:28] <dgroos> ...on lucid?
[19:29] <dgroos> https://help.ubuntu.com/community/UbuntuLTSP/LocalAppsResolvConf
[19:29] <alkisg> OK, let's get this from the start. You don't need a static ip on the wan side, but do you want one?
[19:31] <mhall119> highvoltage: my list doesn't have things like sabayon or ltsp
[19:31] <mhall119> just the contents of ubuntu-edu-*
[19:31] <mhall119> so it's not everything in Edubuntu
[19:31] <highvoltage> mhall119: ah yes, I'll mention that on the page
[19:31] <dgroos> Yes--the server already changed the ip once and that was a hassle since I didn't know what it had changed to...
[19:32] <mhall119> highvoltage: is there a seed file for those kinds of things?
[19:33] <mhall119> ah, desktop-gnome, I see it
[19:41] <alkisg> dgroos: so you want a static wan ip? there are two ways for that, either with network manager and no /etc/network/interfaces, or vice-versa
[19:41] <alkisg> (I usually go for the network manager because it enables the teachers to see the connection info)
[19:41] <dgroos> As per instructions from several web pages I got rid of network manager
[19:41] <alkisg> OK, then post your interfaces to pastebin
[19:41] <dgroos> it seemed to be causing issues when I was trying to do something...
[19:41] <dgroos> right
[19:42] <alkisg> Nah, network manager is fine. Both ways are fine - just a matter of preference...
[19:43] <dgroos> here it is: http://ltsp.pastebin.com/MTCqTr1w
[19:43] <dgroos> I know that the defined address for eth1 is superfluous.
[19:44] <alkisg> You have 3 nics?
[19:44] <alkisg> How are they wired to your network?
[19:44] <alkisg> (you can also change their names if it suits you)
[19:45] <dgroos> Yes, and hoping to do bonding with the 2 gig cards, but for now eth2 isn't plugged in.
[19:45] <alkisg> Are those cards pci-e or just pci?
[19:45] <dgroos> how do I check?
[19:46] <dgroos> Add-on NIC is probably the simple variety, the other 2 were built into this prof. grade server.
[19:46] <alkisg> physically, pci-e cards are very small on their bottoms. But maybe you can also find out with `lspci | grep Ethernet`...
[19:47] <alkisg> I'm guessing pci-e then, ok
[19:47] <dgroos> The gig cards show something like: 03:01.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet (rev 10)
[19:48] <dgroos> The wan facing nic (fast ethernet) is: 06:02.0 Ethernet controller: Intel Corporation 82557/8/9/0/1 Ethernet Pro 100 (rev 08)
[19:49] <alkisg> dgroos: also, paste the result of route -n
[19:49] <alkisg> (you'll need a gateway defined for eth1)
[19:49] <dgroos> http://ltsp.pastebin.com/UzjN1kH1
[19:52] <dgroos> That looks weird-- having multiple lines for eth0 and eth1?
[19:52] <alkisg> Make a backup of your interfaces, run `sudo stop networking`, put this: http://ltsp.pastebin.com/imW9fE8v and then run `sudo start networking`
[19:53] <alkisg> (you'll lose your net connection for a while of course)
[19:53] <dgroos> ah... better go to my laptop :)
[19:54] <alkisg> Also, paste your /etc/resolv.conf
[19:54] <alkisg> (it should be kept with no modifications, but better be cautious...)
[19:55] <dgroos> I type: sudo stop networking
[19:55] <dgroos> it replies: stop: Unknown instance:
[19:56] <alkisg> No problem, go on with the rest...
[19:57] <dgroos> (question--I've got proc mounted or something, in another terminal window--is that an issue?)
[19:58] <alkisg> No, but there's a small posibility that you might need a server reboot if stop/start networking won't make it
[19:58] <alkisg> (for the changes to take effect)
[20:01] <dgroos> upon typing sudo start network I get, "networking stop/waiting"
[20:03] <dgroos> ...though internet works on localapps thin client.
[20:04] <alkisg> What does `ifconfig -a` tell you now?
[20:05] <dgroos> http://ltsp.pastebin.com/PyTWXaCC
[20:09] <alkisg> dgroos: hmm is it easy to reboot the server, so that we don't try more start/stop stuff?
[20:09] <alkisg> (lucid changed networking from init.d to upstart...)
[20:09] <dgroos> for sure, I set up ilo :D
[20:12] <dgroos> famous last words... :(  I'll call someone to open the room...
[20:14] <alkisg> Ah, you don't have physical access? Ouch, you should say that before, to do better checking... :)
[20:15] <dgroos> well, I had ilo working fine before... :)
[20:16] <alkisg> What is "ilo"?
[20:18] <dgroos> "integrated Lights Out" or something.  In other words, it is a special NIC on the server that is used to do remote management, like power on or restart the server when it becomes non-responsive.  I've not had it become unresponsive like this..s
[20:28] <dgroos> alkisg: ok, got physical access, fixed ilo, did reboot.
[20:30] <alkisg> dgroos: is the network working?
[20:30] <dgroos> Yes, client rebooted and firefox on client as well.
[20:32] <alkisg> OK, what's next?
[20:33] <dgroos1> static ip?  here's my network file: http://ltsp.pastebin.com/nHPx7mpa
[20:34] <alkisg> dgroos1: it is static now, isn't it?
[20:35] <alkisg> (with the new interfaces file I gave you, eth1 got 10.51.0.199 == static...
[20:35] <dgroos1> I thought so but there are too many unk variables for me at the moment...
[20:36] <dgroos1> OK, let me check if I can update my chroot...
[20:36] <dgroos1> oh yeah, do I need to mess with this: https://help.ubuntu.com/community/UbuntuLTSP/LocalAppsResolvConf
[20:37] <alkisg> No, that's for 9.04
[20:37] <dgroos1> ... sigh...
[20:37] <alkisg> (and it isn't even needed for updating the chroot)
[20:39] <dgroos1> when trying to update the chroot I get a bunch of these:
[20:39] <dgroos1> Err http://us.archive.ubuntu.com lucid Release.gpg
[20:39] <dgroos1>   Temporary failure resolving 'us.archive.ubuntu.com'
[20:39] <dgroos1> I googled and goggled but to no avail...
[20:40] <alkisg> Try this:
[20:40] <alkisg> sudo chroot /opt/ltsp/i386
[20:40] <alkisg> ping www.google.com
[20:41] <alkisg> What do you get?
[20:41] <dgroos1> do I unmount first?
[20:41] <alkisg> No need
[20:41] <dgroos1> nothing...
[20:42] <alkisg> What's the result of this?
[20:42] <dgroos1> it waits till I hit control-C and still no output except ^c
[20:42] <alkisg> (on the server):
[20:43] <alkisg> (outside the chroot)
[20:43] <alkisg> cat /etc/resolv.conf
[20:43] <alkisg> cat /opt/ltsp/i386/etc/resolv.conf
[20:46] <dgroos1> There's the problem!: http://ltsp.pastebin.com/4Ra4DH5G
[20:46] <dgroos1> it was in the resolve.conf in the chroot!
[20:46] <dgroos1> I guess they should be the same?
[20:47] <alkisg> Yup
[20:47] <alkisg> sudo cp...
[20:47] <dgroos1> right, then rebuild client then things should be hunky dory, perhaps!
[20:49] <alkisg> You don't need to rebuild the client to update the image
[20:49] <alkisg> First update, then rebuild
[20:49] <alkisg> Also, that resolv.conf doesn't matter for the thin clients, it only matters for the updating
[20:49] <dgroos1> I actually meant update image.  Is rebuilding doing the apt-get update and so on?
[20:49] <dgroos1> OK
[20:50] <alkisg> Well, with rebuild we usually mean ltsp-build-client
[20:50] <alkisg> update == apt-get update etc and ltsp-update-image
[20:51] <dgroos1> I see, don't have to do that, I think.
[20:51] <dgroos1> should I reload the new image (logout/login)?
[20:51] <alkisg> If you want. Logout won't do it though, a reboot will be needed
[20:52] <alkisg> But if you were having problem with firefox on the thin clients, it shouldn't matter
[20:52] <alkisg> (because resolv.conf on the thin clients is generated dynamically upon boot)
[20:52] <dgroos1> right--it auto reboots upon logout after image update...
[20:52] <dgroos1> OK I'll try w/out...
[21:05] <dgroos1> Thanks alkisg, I'm now able to advance further in updating the chroot.  When I get to the point where it says:
[21:05] <dgroos1> Lastly, let's exit the chroot, unmount /proc, run ltsp-update-kernels  (in case there was a kernel upgrade in the chroot) and rebuild our NBD  thin-client image
[21:05] <dgroos1> but then the code pasted tells a different order:
[21:05] <alkisg> dgroos1: why don't you do all that with sch-scripts?
[21:05] <alkisg> It takes care of everything automatically
[21:06] <dgroos1> exit sudo ltsp-update-kernels sudo umount /opt/ltsp/i386/proc sudo ltsp-update-image
[21:07] <dgroos1> Well, I was concerned that it might do something that is needed on the Greek setup but that would do something I didn't want on mine...
[21:07] <alkisg> You just invoke the update menu, or the "get a shell inside the chroot" menu etc
[21:07] <alkisg> Where are you getting that code above from?
[21:07] <dgroos1> (If you can tell me which is correct order of events I'll edit the wiki page on: https://help.ubuntu.com/community/UbuntuLTSP/UpdatingChroot
[21:08] <alkisg> The best way is to use the ltsp-chroot script for that
[21:08] <dgroos1> OK, in sch-scripts?
[21:09] <alkisg> no, let me rephrase it:
[21:09] <alkisg> sch-scripts does everything from a menu, but not all people have it, so never mind that
[21:09] <alkisg> ltsp-chroot is a script contained in upstream ltsp
[21:10] <alkisg> Currently, you have it there: /usr/share/ltsp/scripts/ltsp-chroot
[21:10] <alkisg> But it's an old version (yeah even on lucid)
[21:10] <alkisg> On newer versions it'll go on /usr/bin
[21:10] <alkisg> So, instead of the wiki page telling people to do what's inside ltsp-chroot, why not download it instead for previous versions?
[21:10] <alkisg> (that's what I proposed in the mailing list some days ago)
[21:11] <alkisg> Here's the most recent version, in ltsp-upstream: http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/annotate/head%3A/server/scripts/debian/ltsp-chroot
[21:11] <alkisg> So I think that the wiki page should tell people to download that file, save it to /usr/bin, and just use that for updating
[21:12] <alkisg> (for newer ltsp versions, they'll already have it in /usr/bin, preinstalled...)
[21:12] <dgroos1> I say you proposed that on the e-mail and replied and asked you a question an hour or 2 ago :)
[21:14] <alkisg> Sorry, didn't get what you mean with that :-/
[21:17] <dgroos1> basically, I was asking to where you copy that file!
[21:18] <dgroos1> OK I copied it there but can't read if ownership/permissions are correct since with ls -la of /usr/bin/ there are too many items and it goes way off the page.
[21:27] <alkisg> dgroos1: ls -lha /usr/bin/ltsp-chroot
[21:27] <alkisg> sudo chmod +x /usr/bin/ltsp-chroot
[21:27] <alkisg> sudo ltsp-chroot --mount-proc --copy-resolv-conf --mount-package-cache apt-get update
[21:28] <alkisg> sudo ltsp-chroot --mount-proc --copy-resolv-conf --mount-package-cache apt-get dist-upgrade
[21:28] <alkisg> Something like that.
[21:28] <alkisg> (you don't need --copy-resolv-conf, you already copied it, I'm just saying...)
[21:29] <dgroos1> Got this after :27:58 comment: ERROR: ltsp chroot not found: /opt/ltsp/amd64
[21:29] <dgroos1> umount: /opt/ltsp/amd64/proc: not found
[21:29] <dgroos1> umount: /opt/ltsp/amd64/var/cache/apt/archives: not found
[21:30] <alkisg> Do you have an amd64 chroot or an i386 one?
[21:30] <dgroos1> *command
[21:30] <alkisg> --arch i386
[21:30] <dgroos1> i386
[21:30] <dgroos1> but the server is 64 itself
[21:31] <alkisg> sudo ltsp-chroot --arch i386 apt-get update
[21:31] <alkisg> Or you can just run: sudo ltsp-chroot --arch i386
[21:31] <alkisg> That will get you a shell inside the chroot
[21:32] <alkisg> See all the options in the source page: http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/annotate/head%3A/server/scripts/debian/ltsp-chroot
[21:32] <dgroos1> OK did this command, then... ?
[21:32] <dgroos1> will check that out...
[21:33] <alkisg> OK let me give you a full example:
[21:33] <alkisg> sudo ltsp-chroot --mount-proc --arch i386
[21:33] <alkisg> apt-get update
[21:33] <alkisg> apt-get dist-upgrade
[21:33] <alkisg> exit
[21:33] <alkisg> sudo ltsp-update-image
[21:33] <alkisg> That updates your chroot.
[21:34] <dgroos1> so I would do... sudo ltsp-chroot --arch i386 and then the others?
[21:34] <alkisg> Yes
[21:34] <alkisg> If you want to mount /proc too, you just add that parameter
[21:34] <alkisg> It gets unmounted automatically
[21:34] <alkisg> You can also parameters (like ARCH) in a config file, /etc/ltsp/ltsp-chroot.conf
[21:35] <dgroos1> This is probably easier but to eyes blurry from hours of troubleshooting...
[21:35] <dgroos1> You really saved me, again!
[21:35] <alkisg> ...maybe we should write a wiki page specifically for ltsp-chroot...
[21:35] <dgroos1> YES!  I can do those!
[21:35] <dgroos1> :D
[21:35] <alkisg> :D
[21:37] <dgroos1> How about updating the kernel?  I would like to fix this page: https://help.ubuntu.com/community/UbuntuLTSP/UpdatingChroot
[21:38] <alkisg> sudo ltsp-chroot update-initramfs -u && sudo ltsp-update-image --force
[21:39] <alkisg> (that's on lucid only, for previous versions it should be: sudo ltsp-chroot update-initramfs -u && sudo ltsp-update-image && sudo ltsp-update-kernels)
[21:39] <alkisg> Erm, sorry
[21:39] <alkisg> When you say updating the kernel, when do you mean?
[21:40] <alkisg> When a new kernel is available in the repositories?
[21:40] <alkisg> apt-get dist-upgrade takes care of that, so forget about the update-initramfs -u
[21:41] <alkisg> ltsp-update-image && ltsp-update-kernels are still needed
[21:42]  * alkisg thinks he should probably take some time to rewrite that awful wiki page.. :-/
[21:44] <dgroos1> Do I add the --arch 32 like this: sudo ltsp-chroot --arch 32 update-initramfs -u && sudo ltsp-update-image --force
[21:44] <dgroos1> ?
[21:45] <dgroos1> (I got errors about /opt/ltsp/amd64...
[21:45] <alkisg> dgroos1: as a user, would you like that wiki page to tell you about LTSP_HANDLE_DAEMONS and other internal stuff, or would you prefer that page to use ltsp-chroot in its instructions?
[21:45] <alkisg> --arch i386
[21:45] <alkisg> Not 32...
[21:45] <dgroos1> (where do I write that in the command you gave me?)
[21:46] <dgroos1> right :P
[21:46] <alkisg> Execute the series of commands that I wrote above, in the "full example"
[21:46] <dgroos1> I did:
[21:46] <alkisg> Ah, ok, about the kernel
[21:46] <alkisg> A new full example:
[21:46] <dgroos1> sudo ltsp-chroot update-initramfs -u && sudo ltsp-update-image --force
[21:46] <alkisg> sudo ltsp-chroot --arch i386
[21:46] <alkisg> apt-get update
[21:47] <alkisg> apt-get dist-upgrade
[21:47] <alkisg> (that gets you a new kernel, if available)
[21:47] <dgroos1>  and got: ERROR: ltsp chroot not found: /opt/ltsp/amd64
[21:47] <alkisg> exit
[21:47] <dgroos1> OK
[21:47] <alkisg> Wait. You got an error with that? :
[21:47] <alkisg> (11:33:28 μμ) alkisg: sudo ltsp-chroot --mount-proc --arch i386
[21:47] <alkisg> ?
[21:48] <dgroos1> to answer your wiki question, I like explanations but the main thing is what I have to do.  Does that answer your question?
[21:48] <alkisg> Yes, it tells me we should delete half of that page
[21:49] <alkisg> That page contains explanations about how stuff is implemented. It doesn't tell people how to do their work easily.
[21:49] <dgroos1> This is what I did/got: mrg@gcos-server:~$ sudo ltsp-chroot update-initramfs -u && sudo ltsp-update-image --force
[21:49] <dgroos1> ERROR: ltsp chroot not found: /opt/ltsp/amd64
[21:49] <alkisg> dgroos1: forget that command
[21:49] <alkisg> Try this one: sudo ltsp-chroot --mount-proc --arch i386
[21:50] <alkisg> Do you get an error with that?
[21:50] <dgroos1> no error!
[21:50] <alkisg> OK, you're inside the chroot with proc mounted, with LTSP_HANDLE_DAEMONS=false etc
[21:51] <alkisg> You did half of the wiki page. Let's go on. Do you want to update your kernels?
[21:51] <dgroos1> OK :)  I'll believe you!
[21:51] <dgroos1> yes...
[21:51] <alkisg> apt-get update && apt-get dist-upgrade
[21:52] <dgroos1> good--it said 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded
[21:52] <alkisg> That completely updates your chroot, including the kernel. But it doesn't update the server copy of the kernel (we'll do that below)
[21:52] <alkisg> OK. Next: exit
[21:52] <dgroos1> so looks like I'm up to date?
[21:52] <dgroos1> yes, and unmount?
[21:52] <alkisg> Yes
[21:52] <alkisg> After `exit`, the /proc is unmounted and you're outside of your chroot
[21:52] <alkisg> No, you don't bother with mounting/unmounting
[21:53] <dgroos1> right
[21:53] <alkisg> Now, to update the server copies
[21:53] <alkisg> For Lucid: sudo ltsp-update-image --force
[21:53] <alkisg> For less that Lucid: sudo ltsp-update-image && sudo ltsp-update-kernels
[21:54] <alkisg> But, you still need --arch in your case
[21:54] <alkisg> So, sudo ltsp-update-image --force --arch i386
[21:54] <alkisg> Or, for less than lucid, sudo ltsp-update-image --arch i386 && sudo ltsp-update-kernels
[21:54] <dgroos1> oops, I already did sudo ltsp-update-image --force...?
[21:54] <alkisg> If it runs, it's ok then, it autodetected your arch
[21:55] <alkisg> *chroot
[21:55] <dgroos1> cool.
[21:55] <alkisg> That's all
[21:55] <dgroos1> :D :D
[21:55] <alkisg> So, 4 lines in total
[21:55] <dgroos1> and 5 hours later... :D
[21:56] <alkisg> ltsp-chroot, apt-get update && dist-upgrade, exit, update-image && kernels
[21:56] <alkisg> If you think that's simpler than what's already on that wiki page, we should rewrite it...
[21:56] <dgroos1> I really appreciate all the troubleshooting you did with me to fix my chroot/networking issues as well as updating stuff.
[21:57] <dgroos1> Yes it is!  I'd volunteer, but my mind is mush right now...
[21:57] <dgroos1> and I couldn't speak from understanding...
[21:59] <dgroos1> My project wouldn't succeed without all of this help.  Let me know how I can be of help someday...
[22:00] <alkisg> You're welcome. If you're still around 2 years from now, I'll ask for some language proofreading when we internationalize sch-scripts ;)
[22:00] <dgroos1> Con Mucho Gusto!
[22:01] <alkisg> Heh, and maybe a spanish translation too :P
[22:01] <dgroos1> I speak it more or less fluently, my reading/writing, well, I'll ask my wife for help on that!