=== TuxPurple_ is now known as TuxPurple
[02:05] <dgroos> ping sbalneav
[02:18] <sbalneav> pong
[02:18] <dgroos> good eve
[02:19] <dgroos> You were right about the space in the login name.
[02:20] <dgroos> Did you see the comments I made soon after you left?
[02:23] <sbalneav> Something about the thin client failing to boot?
[02:24] <dgroos> I'll copy and paste...
[02:24] <dgroos> (from earlier, right after testing...) wow-- I put a space before the username and login seemed to work initially, but it stalled before the login screen appeared.
[02:25] <dgroos> (continues...) I did, "sudo du -sh *" inside this users home folder.  I watch the dev directory quickly grow in size.  It started at 176 KB, did it again 45 seconds later and it was 100 MB.  Did it a minute or two later and it was 548 MB, a minute or so later and it was 921 MB. And there it stays.
[02:25] <dgroos> (and ends...) On the client it now says, "An add-in card in the system appeared to not work correctly on the last boot attempt...  (then there's a note that says to push F1 to boot).  Which I did, then it didn't login and instead went to the screen it normally shows when the thin client fails to boot.
[02:25] <dgroos> that's it.
[02:32] <sbalneav> So, the users login is hosed is what you're saying?
[02:41] <dgroos> hmmm... not sure how to answer that.
[02:42] <dgroos> do you mean that if I tried to login as that user again, I wouldn't be able to?
[02:44] <dgroos> it could be.  I think you are right.  I could try and login through ssh w/his user info.  would that be useful?  I don't think that's what you mean though.
[02:49] <sbalneav> Well, I mean, removing something from the users home dir shouldn't cause the thin client to have trouble booting.
[02:49] <sbalneav> so if you're not able to log in as that user, then the user itself's been hosed somehow.
[02:51] <dgroos> I know that I will be able to log in after removing the fd directory, it worked fine before.
[02:51] <dgroos> I'm not sure if he can log in *until* I remove that rogue directory.
[02:53] <sbalneav> right, so remove it.
[02:54] <dgroos> For sure.
[02:54] <sbalneav> did you put the space before or after the name?
[02:54] <dgroos> before
[02:54] <sbalneav> and, please paste the sources.list that's in your chroot.
[02:55] <dgroos> I'll get it.  I've got to go vpn a moment...
[02:55] <sbalneav> k
[03:07] <dgroos_> OK here it is: http://pastebin.ubuntu.com/342326/  this is the source list at: /etc/apt/sources.list  this is NOT the source list at opt/ltsp/i386/etc/apt/sources.list.  Right?
[03:08] <sbalneav> no, I want the one in /opt/ltsp...
[03:11] <dgroos_> http://pastebin.ubuntu.com/342329/  Shouldn't it be the same?
[03:13] <sbalneav> well ideally.
=== dgroos_ is now known as dgroos
[03:14] <sbalneav> did you update the packages in the chroot and rebuild?  because stgraber fixed this bug I thought.
[03:15] <dgroos> ahhh... update in the --chroot--?  how again does one do that?
[03:20] <dgroos> isn't it just sudo apt-get upate/upgrade then sudo ltsp-update-image?
[03:22] <sbalneav> Should be.
[03:22] <sbalneav> chroot /opt/ltsp/i386
[03:23] <dgroos> I did do that, then.  You aren't saying chroot /opt/ltsp/i386 is some command?
[03:25] <sbalneav> yeah
[03:25] <sbalneav> that's how you switch into the chroot
[03:25] <sbalneav> chroot /opt/ltsp/i386
[03:25] <sbalneav> apt-get update
[03:25] <sbalneav> apt-get upgrade
[03:26] <sbalneav> exit
[03:26] <sbalneav> ltsp-update-image
[03:26] <dgroos> Do I sudo to get into chroot? su?
[03:26] <sbalneav> sudo chroot /opt/ltsp/i386
[03:26] <sbalneav> Looks like *SOMEONE* hasn't been reading the docs :)
[03:27] <dgroos> My brain is basically spaghetti now, actually for some time :)
[03:28] <sbalneav> https://help.ubuntu.com/community/UbuntuLTSP/UpdatingChroot
[03:28] <sbalneav> That's probably your problem.  the fix is in the chroot
[03:29] <sbalneav> so if you haven't updated the chroot, you haven't picked up stgrabers fix yet.
[03:29] <dgroos> Thanks for all this.  I'll do it tonight and have it ready for tomorrow morning.
[03:30] <dgroos> I'm going to write this into my blog--I'll probably find I already wrote it a year ago :(  should have anyway.
[03:42] <sbalneav> dgroos: Where's yer blog?
[03:43] <dgroos> Well, it's in a similar state to my brain, but here it is... http://groosd.blogspot.com
[03:44] <dgroos> I tried to do the above procedure but got these errors: http://pastebin.ubuntu.com/342343/
[03:45] <sbalneav> got a valid resolv.conf in your chroot?
[03:45] <dgroos> I'm looking at the docs link and see it says a couple of different things for example it says to 'mount -t proc proc /proc  it also talks about...
[03:45] <dgroos> I'll check
[03:47] <dgroos> looks like there are lots of /home/username/cow/etc/resolv.conf is that right?
[03:48] <dgroos> and I see there is one in the opt/ltsp/i386/etc/resolv.conf
[03:48] <dgroos> check this latter one?
[03:48] <sbalneav> yeah
[03:49] <sbalneav> since, when you're in the chroot command, that's the one it's going to use.
[03:50] <dgroos> right.  makes sense.
[03:50] <sbalneav> basically, you should cp /etc/resolv.conf /opt/ltsp/i386/etc/resolv.conf
[03:50] <dgroos> checked it out. it's wack.
[03:50] <sbalneav> there you go.
[03:50] <dgroos> it's got the ip of when I had it in my house this summer!
[03:51] <dgroos> for nameserver, what do I put?
[03:51] <sbalneav> basically, you should cp /etc/resolv.conf /opt/ltsp/i386/etc/resolv.conf
[03:54] <dgroos> Much better!
[03:55] <dgroos> still some errors--GPG errors-- NO_PUBKEY
[03:57] <sbalneav> that;s fine, it should still upgrade the packages.
[03:58] <sbalneav> so the update then the upgrade
[03:58] <sbalneav> and when it's done, type "exit"
[04:02] <dgroos> Great.  It's in process... again, thanks a bundle.  btw--did you see your name on the blog?
[04:04] <sbalneav> No, lemme look
[04:04] <sbalneav> Was it something like "That Fr*ggin sbalneav *sshole..." :)
[04:07] <dgroos> well, I used exclamation marks instead of asterisks ;)
[04:08] <dgroos> Actually, as you can see I've not done much of anything on the blog since mid summer I'm so busy chasing my tail, but there is the 'lick and a promise' registered there :)
[04:08] <sbalneav> heh
[04:09] <sbalneav> so when the update's done, then do the exit, ltsp-update-image, and voila
[04:11] <dgroos> am doing now... there were a few errors hope not big ones...
[04:16] <sbalneav> quick way to tell is if you retry the upgrade
[04:16] <sbalneav> if there's nothing left to upgrade then you're ok
[04:20] <dgroos> I'll check after the image is done updating...
[04:28] <dgroos> said this when I tried to update-upgrade: http://pastebin.ubuntu.com/342380/
[04:31] <dgroos> and said this: http://pastebin.ubuntu.com/342384/ when I said "Y" to the upgrade...
[04:35] <sbalneav> ok, so exit out of the chroot
[04:36] <sbalneav> export LTSP_HANDLE_DAEMONS=false
[04:36] <sbalneav> sorry, do this first
[04:36] <sbalneav> sudo -i
[04:36] <sbalneav> export LTSP_HANDLE_DAEMONS=false
[04:36] <sbalneav> chroot /opt/ltsp/i386
[04:36] <sbalneav> mount -t proc proc /proc
[04:37] <sbalneav> apt-get upgrade
[04:37] <sbalneav> it should finish
[04:37] <sbalneav> umount /proc
[04:37] <sbalneav> exit
[04:37] <sbalneav> then rebuild
[04:37] <dgroos> doing it... and said that mount: proc already mounted whe I gove the mount command...
[04:38] <dgroos> *when I gave
[04:40] <sbalneav> ok
[04:40] <sbalneav> so you had done the mount previously then?
[04:41] <dgroos> no, not knowingly at least.
[04:44] <sbalneav> do this
[04:45] <sbalneav> cat /etc/ltsp_chroot
[04:45] <sbalneav> what do you get
[04:46] <dgroos> I'm still root... and I got 'no such file or directory'
[04:48] <sbalneav> then you're NOT IN THE CHROOT!!!!!
[04:48] <sbalneav> export LTSP_HANDLE_DAEMONS=false
[04:48] <sbalneav> chroot /opt/ltsp/i386
[04:48] <sbalneav> mount -t proc proc /proc
[04:49] <sbalneav> alt-get upgrade
[04:49] <sbalneav> it should finish
[04:49] <sbalneav> umount /proc
[04:49] <sbalneav> exit
[04:49] <sbalneav> I can't make this any simpler :)
[04:50] <dgroos> I'm guessing alt-get is to be apt-get?
[04:52] <sbalneav> yep
[04:53] <dgroos> It went so smooooooth!  Nary a hiccup
[04:53] <sbalneav> there you go.
[04:53] <sbalneav> remember the umount
[04:53] <sbalneav> then exit
[04:54] <sbalneav> ltsp-update-image
[04:54] <sbalneav> done.
[04:54] <dgroos> got it and got it
[04:55] <dgroos> now that yes.  Thanks for staying up and helping me through all of this.  I can't wait to fire up the thin clients tomorrow :)
[04:58] <sbalneav> Well, that should fix the phantom disk eater for sure
[04:58] <sbalneav> and a lot of other niggling problems as well.
[05:02] <dgroos> for sure.
[05:04] <sbalneav> Got sabayon bug database access today.
[05:04] <sbalneav> Closed 30 some odd bugs for sabayon :)
=== TuxPurple_ is now known as TuxPurple
[14:47] <sbalneav> Morning all
[14:52] <mhall119|work> morning
=== Ahmuck-Sr is now known as Ahmuck-Jr
=== Ahmuck-Jr_ is now known as Ahmuck-Sr
=== Guest84476 is now known as juliux
=== jussio1 is now known as jussi01
=== ikonia_ is now known as ikonia
=== Ahmuck-Jr_ is now known as Ahmuck-Jr
=== isforins1cts is now known as isforinsects