IRC chat logs for #ltsp on irc.freenode.net (webchat)


Channel log from 11 March 2011   (all times are UTC)

00:03Kicer86 (~Kicer86@host-5db0eeee.sileman.net.pl) left irc: Quit: KVIrc Insomnia 4.0.2, revision: 4740, sources date: 20100627, built on: 2010-08-08 18:29:00 UTC http://www.kvirc.net/
00:07chupacabra (~chupacabr@cpe-70-112-10-77.austin.res.rr.com) joined #ltsp.
00:35sep (~sep@40.211.jostedal.no) joined #ltsp.
00:43alkisg_work (teacher@pc-181.edu.uoi.gr) joined #ltsp.
01:07gnunux (~emmanuel@194.167.18.244) joined #ltsp.
01:09
<gnunux>
hi
01:23andygraybeal (~andy.gray@obsidian.casanueva.com) joined #ltsp.
01:26
<muppis>
Nicely slow.. Using LTSP VM-client over SSH..
01:34patrickmw (~pwright@ip68-231-4-153.ph.ph.cox.net) left irc: Read error: Operation timed out
01:37stgraber (~stgraber@ubuntu/member/stgraber) left irc: Remote host closed the connection
01:37stgraber (~stgraber@ubuntu/member/stgraber) joined #ltsp.
01:43Gremble (~Ben@cpc12-aztw24-2-0-cust146.aztw.cable.virginmedia.com) joined #ltsp.
01:46patrickmw (~pwright@ip68-231-4-153.ph.ph.cox.net) joined #ltsp.
02:00dobber (~dobber@89.190.197.77) joined #ltsp.
02:22Gremble (~Ben@cpc12-aztw24-2-0-cust146.aztw.cable.virginmedia.com) left irc: Quit: I Leave
02:27alkisg_work (teacher@pc-181.edu.uoi.gr) left #ltsp.
02:45Q-FUNK (~q-funk@ubuntu/member/q-funk) joined #ltsp.
02:57Nick change: ogra_ -> ogra
03:18alkisg_work (teacher@pc-181.edu.uoi.gr) joined #ltsp.
03:53Lynn (~Lynn@178-116-131-63.access.telenet.be) joined #ltsp.
03:55alkisg_work (teacher@pc-181.edu.uoi.gr) left #ltsp.
04:33alkisg (~alkisg@ubuntu/member/alkisg) joined #ltsp.
05:09Q-FUNK (~q-funk@ubuntu/member/q-funk) left irc: Ping timeout: 276 seconds
05:35MorningSon (~MorningSo@cpe-70-114-21-95.satx.res.rr.com) joined #ltsp.
06:17
<mgariepy>
good morning everyone
06:17Naranek_ (~jalahtir@a91-156-151-199.elisa-laajakaista.fi) joined #ltsp.
06:18Naranek (~jalahtir@a91-156-151-199.elisa-laajakaista.fi) left irc: Ping timeout: 246 seconds
07:19shawnp0wers (~Adium@linuxjournal/staff/shawnp0wers) joined #ltsp.
07:48Nick change: Naranek_ -> Naranek
07:49primeministerp (~ppouliot@64.119.153.82) left irc: Read error: Connection reset by peer
07:50primeministerp (~ppouliot@64.119.153.82) joined #ltsp.
07:57alkisg (~alkisg@ubuntu/member/alkisg) left irc: Quit: Leaving.
07:59mikkel (~mikkel@80.71.132.15) joined #ltsp.
08:24jkinney23 (~jason@CPE54d46fa9ecb2-CM54d46fa9ecb0.cpe.net.cable.rogers.com) left irc: Ping timeout: 276 seconds
08:42Roasted_ (~Jason@206.82.22.190) joined #ltsp.
08:43
<Roasted_>
whats up guys
08:43
hate to be a pain but I'm still curious about changing my login screen appearance. any insight on that?
08:43Trixboxer (~Trixboxer@office.supportdepartment.net) joined #ltsp.
08:43Technicus (~Technicus@DSLPool-net209-116.wctc.net) joined #ltsp.
08:54efra_ (~euribe@201.102.63.70) joined #ltsp.
08:55efra (~euribe@201.102.125.226) left irc: Disconnected by services
08:55Nick change: efra_ -> efra
09:11
<Roasted_>
:(
09:19efra_ (~euribe@189.143.189.109) joined #ltsp.
09:23efra (~euribe@201.102.63.70) left irc: Ping timeout: 276 seconds
09:26gnunux (~emmanuel@194.167.18.244) left irc: Quit: Ex-Chat
09:30efra__ (~euribe@201.102.78.39) joined #ltsp.
09:32Lynn (~Lynn@178-116-131-63.access.telenet.be) left irc: Quit: Leaving
09:32efra_ (~euribe@189.143.189.109) left irc: Ping timeout: 250 seconds
09:36patrickmw (~pwright@ip68-231-4-153.ph.ph.cox.net) left irc: Quit: Ex-Chat
09:38Mava (~Mava@a91-154-45-79.elisa-laajakaista.fi) left irc: Ping timeout: 276 seconds
09:50RiXtEr (~blah@72-161-84-210.dyn.centurytel.net) left irc: Ping timeout: 240 seconds
09:50RiXtEr (~blah@69-179-105-91.dyn.centurytel.net) joined #ltsp.
09:55dobber (~dobber@89.190.197.77) left irc: Remote host closed the connection
10:10jkinney23 (~jason@CPE54d46fa9ecb2-CM54d46fa9ecb0.cpe.net.cable.rogers.com) joined #ltsp.
10:23staffencasa (~staffenca@128-193-147-238.oregonstate.edu) joined #ltsp.
10:51vagrantc (~vagrant@c-24-21-191-93.hsd1.or.comcast.net) joined #ltsp.
10:52alkisg (~alkisg@ubuntu/member/alkisg) joined #ltsp.
10:52alkisg (~alkisg@ubuntu/member/alkisg) left irc: Remote host closed the connection
10:56administrator__ (~administr@75-144-154-165-NewEngland.hfc.comcastbusiness.net) left irc: Remote host closed the connection
10:57alkisg (~alkisg@ubuntu/member/alkisg) joined #ltsp.
10:59efra__ (~euribe@201.102.78.39) left irc: Ping timeout: 255 seconds
11:11efra__ (~euribe@201.102.78.39) joined #ltsp.
11:20Trixboxer (~Trixboxer@office.supportdepartment.net) left irc: Quit: "Achievement is not the end, its the beginning of new journey !!!"
11:24Roasted_ (~Jason@206.82.22.190) left irc: Read error: Connection reset by peer
11:26Nick change: efra__ -> efra
11:28Mava (~Mava@a91-154-45-79.elisa-laajakaista.fi) joined #ltsp.
11:30Mava (~Mava@a91-154-45-79.elisa-laajakaista.fi) left irc: Client Quit
11:31Roasted_ (~jason@206.82.22.190) joined #ltsp.
11:31matt___ (4b909aa5@gateway/web/freenode/ip.75.144.154.165) joined #ltsp.
11:44shawnp0wers (~Adium@linuxjournal/staff/shawnp0wers) left irc: Quit: Leaving.
12:06Kicer86 (~Kicer86@host-5db0eeee.sileman.net.pl) joined #ltsp.
12:06
<Roasted_>
Has anybody by chance *successfully* changed the background image at the login screen? I've followed all of the guides that supposedly did the trick yet I keep coming up with a blank slate gray screen instead. I'm unsure of what to do and I'd REALLY like to see it changed.
12:11
<alkisg>
Roasted_: here's a how-to
12:11
1) ltsp-build-client
12:11
2) boot a client
12:11
3) run ltsp-update-image. just to verify that this is not your problem
12:12
4) open the existing .png with gimp and change it a big. Don't put your png just yet
12:12
5) ltsp-update-image
12:12
If you see the changed png, all is well, you can put your own there
12:12
You're doing something very wrong, but I don't know what, so take it step by step
12:13
Did you upload your png somewhere?
12:14
<vagrantc>
Roasted_: which guides did you follow?
12:14
<Roasted_>
vagrantc, https://help.ubuntu.com/community/EdubuntuFAQ
12:15
alkisg, I did not. let me do that quick.
12:15
<vagrantc>
Roasted_: i don't see anything in there about changing the LDM theme
12:15
<Roasted_>
scroll down
12:15
there's 3 commands
12:15
then it says edit accordingly or something
12:15
<vagrantc>
ah, found it
12:16
those instructions are very bad
12:16
<Roasted_>
it's all I could find
12:16
seems as if documentation in this area is pretty scarce
12:16
<vagrantc>
though they would work... until you upgraded your package
12:16
<Roasted_>
they would work?
12:16
I tried it like 9 times
12:16
failed each time
12:16
alkisg, I don't think I can upload this. each image hosting site I go to is un-overrideable by our filter cause theyre all classified as adult.
12:17
<alkisg>
Roasted_, for example, if you use a broken .png, then any instructions would fail
12:17
<Roasted_>
alkisg, maybe that's my issue.
12:17
I'll try locating another png and see whats up
12:17
<alkisg>
Change the existing one
12:17
<Roasted_>
how, just making a change to it in gimp?
12:17
<alkisg>
Open it with gimp, draw something, save
12:17
<Roasted_>
then run the update-image?
12:17
<alkisg>
Yes, but:
12:18
if it's already broken, it won't be fixed
12:18
<Roasted_>
if what's already broken, the png?
12:18
<alkisg>
Didn't you say you tried reverting to the old image, and failed as well?
12:18
<Roasted_>
the default png
12:18
yeah, but I'm running client-update now
12:18
or client-build
12:18
so it should revert it back to square one
12:18
shouldnt it?
12:18
<alkisg>
Which one of the two are you running?
12:18
update or biuld?
12:19
<Roasted_>
the one that takes forever
12:19
build-client
12:19
<alkisg>
So build, then yes, it should work now
12:19
<Roasted_>
it should be done any minute now
12:19
its been running for a while
12:19
annnnd done
12:19
<vagrantc>
simply copy the files: cp -r /opt/ltsp/usr/share/ldm/themes/Edubuntu /opt/ltsp/usr/share/ldm/themes/mytheme
12:19
<Roasted_>
yay for good timing
12:19
<vagrantc>
and set LDM_THEME=mytheme in lts.conf
12:19
<Roasted_>
thats another thing
12:20
I dont have an Edubuntu directory
12:20
just ubuntu
12:20
<vagrantc>
then copy that one
12:20
<Roasted_>
so I just changed the command to ubuntu instead
12:20
<vagrantc>
does ubuntu ship the "ltsp" theme?
12:20
<Roasted_>
not sure. Im on edubuntu tho
12:20
but I dont have an edubuntu folder in /opt/ltsp/usr/share/ldm/themes
12:20
<vagrantc>
doh.
12:21
i should have said /opt/ltsp/i386... sorry
12:21
<Roasted_>
I just assumed the ubuntu folder I had in there was what they meant
12:21
<vagrantc>
any should workl
12:21
<Roasted_>
yeah
12:21
i386
12:21
I forgot that part too
12:21
<vagrantc>
but i'd recommend using LDM_THEME in lts.conf rather than messing around with the default symlink
12:21
<alkisg>
afaik ubuntu ships the ltsp theme, and also there's no separate edubuntu theme for now
12:22
<vagrantc>
(or using update-alternatives to update the default symlink, but i think lts.conf is easier).
12:22
<Roasted_>
vagrantc, so you're saying adjust LDM_THEME to point to mytheme, and then just swapping out the png in mytheme?
12:23
what the...
12:23
I still have a gray screen
12:23
I just ran through build-client and rebooted and I still have a gray screen
12:23
glad I uploaded this server as an image. If I cant get this flying Ill just reimage it to how it was an hour ago when I uploaded it.
12:23
<vagrantc>
build-client?
12:23
<Roasted_>
yeah
12:23
I ran that command and waited forever
12:23
<vagrantc>
ltsp-build-client ?
12:23
<Roasted_>
it was supposed to default everything I guess
12:23
yes
12:24
but I STILL have a gray background
12:24
dklfja;ksldjf;alskdjf;laksdjf;a
12:24
<vagrantc>
i.e. you re-installed the LTSP chroot?
12:24
you removed the old one first?
12:24
<Roasted_>
I ran the command...
12:24
and it completed 10 minutes later.
12:24
I'm not sure?
12:24
<vagrantc>
ltsp-build-client, with no arguments?
12:25
<Roasted_>
it yelled at me about /opt/ltsp/amd64
12:25
so I removed it
12:25
and ran the command again
12:25
and it went through
12:25
<vagrantc>
Roasted_: what about /opt/ltsp/i386 ?
12:25Technicus (~Technicus@DSLPool-net209-116.wctc.net) left irc: Read error: Operation timed out
12:25
<Roasted_>
it didnt yell at me about that
12:25
<vagrantc>
you probably want to build i386 chroot
12:25
<Roasted_>
I suppose thats the issue?
12:25
<vagrantc>
are your clients 64-bit?
12:25
<Roasted_>
server is, clients are not
12:25
<vagrantc>
or do you want i386 clients?
12:25
<Roasted_>
I want 32b clients
12:26
old hardware that isnt 64 bit proc's
12:26
<vagrantc>
sure
12:26
ltsp-build-client --arch i386
12:26
not sure what all the defaults are on ubuntu, but there are some options to cache the downloaded files since it seems like you might have to do this a few times.
12:27
you might have to clean out your old chroots as well
12:27
er, /opt/ltsp/images
12:27
and it might do some configuration in /etc/inetd.conf ... i'm not so familiar with ubuntu's defaults
12:28
but you really should get to a clean state
12:28
<Roasted_>
k, running --arch i386 now
12:28
so back to the background thing
12:28
since this has been a 5 hour project now
12:28
what exactly do you recommend I do? Edit a config file to just point to mytheme instead of default?
12:28* vagrantc notes that LDM_THEME isn't documented in the lts.conf manpage
12:28
<vagrantc>
Roasted_: that's what i'd recommend, yes.
12:29
<Roasted_>
wheres the location of lts.conf?
12:29
I'd like to take that down in my notes here
12:29
<vagrantc>
probably /var/lib/tftpboot/ltsp/i386/lts.conf
12:30
<Roasted_>
so make that change, then whatever is in mytheme is what the theme is
12:31Gremble (~Ben@cpc12-aztw24-2-0-cust146.aztw.cable.virginmedia.com) joined #ltsp.
12:38* vagrantc is documenting LDM_THEME
12:39
<Roasted_>
:)
12:43Gremble (~Ben@cpc12-aztw24-2-0-cust146.aztw.cable.virginmedia.com) left irc: Quit: I Leave
12:46
<vagrantc>
gah, this is hard to explain because everything in LDM_THEME is relative to the chroot ... which baffles people
12:46
hard to explain well.
12:48
<Roasted_>
well, bottom line is, change the directory to mytheme and drop in other png's accordingly and that's it right?
12:48
or are you trying to give an explanation with the directions?
12:50
<vagrantc>
so you'd copy and existing theme to mytheme, set LDM_THEME=mytheme, and then tweak the files in mytheme as you wish
12:50
<Roasted_>
theres no LDM_THEME in lts.conf
12:50
sigh
12:50
just LDM_DEBUG and LDM_REMOTEECMD
12:50
<vagrantc>
unless you're running an ancient version of LDM, it supports it.
12:50
it's just not documented
12:51
<Roasted_>
do I have to ADD LDM_THEME
12:51
or should it be there
12:51
<vagrantc>
Roasted_: there is no lts.conf by default ... what do you mean?
12:51
<Roasted_>
uh
12:51
you told me
12:51
edit lts.conf
12:51
<vagrantc>
yes
12:51
<Roasted_>
k, that's what I'm doing
12:51
what do you mean there's no lts.conf
12:51
<vagrantc>
and there are already values specified there?
12:51
<Roasted_>
when you told me to edit it..
12:51
<vagrantc>
create it if it doesn't exist
12:51
<Roasted_>
it does
12:51
theres no LDM_THEME value in here
12:52
<vagrantc>
but if it does exist, and there are values there, where did those come from?
12:52
<Roasted_>
there's only two instances of "LDM" in the entire document
12:52
<vagrantc>
because by deffault, there's no lts.conf
12:52
<Roasted_>
just LDM_DEBUG and LDM_REMOTEECMD
12:52
<vagrantc>
who edited your lts.conf?
12:52
<Roasted_>
no clue
12:52
I didn't
12:52
if it was edited, it was edited automatically
12:52
this is a pretty vanilla install of Edubuntu
12:52
<vagrantc>
did you mess with mythbuntu or something?
12:52
<Roasted_>
nope
12:52
<alkisg>
Where is your lts.conf?
12:53* vagrantc defers to alkisg on matters of ubuntu's defaults
12:53
<Roasted_>
actually that may be an example
12:53
its buried within /opt/etc/etc/etc/etc/doc
12:53
the doc makes me think its an example
12:53
the only other lts.conf on the entire system is under /opt/ltsp/i386/etc
12:54
<alkisg>
See the path that vagrantc wrote above
12:54
<Roasted_>
which is entirely commented out except [example] key=value
12:54
yeah theres no lts.conf in there
12:54
so create lts.conf and add the LDM_THEME in there
12:55
and thats it in the entire file"?
12:55
<alkisg>
[Default]
12:55
LDM_THEME=...
12:55
I.e. you also need a [Default] section
12:55
<vagrantc>
alkisg: maybe we need a command edit-lts-conf
12:55
<Roasted_>
k, done
12:56
update-client?
12:56
image*
12:56* alkisg proposed a GUI editor but it was rejected ;)
12:56
<vagrantc>
awww
12:56
<Roasted_>
pfft
12:56efra_ (~euribe@189.228.246.254) joined #ltsp.
12:56
<Roasted_>
not sure why it was rejected
12:56
its stupidly obnoxious to edit a damn background image
12:57
<matt___>
gui editor for what?
12:57
<vagrantc>
alkisg: it seems like a script to create and populate a skeletal lts.conf (i.e. [Default] ) and simply edit the existing one if it's already present would be useful
12:57
although people are trying to come up with mastermind alternate schemes to lts.conf anyways ... :)
12:57
<alkisg>
Yup
12:58
<Roasted_>
I dont seem to have a mytheme folder
12:58
<alkisg>
I'm in favor of a ltsp-config.d directory for sysadmins and packages to drop conf there
12:58
(on the server, etc etc :))
12:59efra (~euribe@201.102.78.39) left irc: Ping timeout: 240 seconds
13:00
<Roasted_>
okay, before I just say screw it and stay with the default image... what step am I missing
13:00
I created lts.conf
13:00
I added the entries there
13:00
I edited the bg.png file that I have saved on my desktop, which is the original one I copied and edited
13:01
I wanted to place the bg.png back into mytheme and then proceed to the next step
13:01
but theres no mytheme folder
13:03
<alkisg>
(09:19:44 PM) vagrantc: simply copy the files: cp -r /opt/ltsp/usr/share/ldm/themes/Edubuntu /opt/ltsp/usr/share/ldm/themes/mytheme
13:03
You're missing careful reading :)
13:03
<Roasted_>
my apologies
13:03
simple things not working are aggrivating me to no end
13:03
<alkisg>
Since there's no edubuntu folder, copy the ubuntu one
13:04
<vagrantc>
ok, well, documented LDM_THEME in ltsp-docs bzr
13:05
<Roasted_>
wheres that located at
13:05
<vagrantc>
that's 3 updates from the last version in debian/ubuntu ... should i wait for more changes to upload a new version
13:05mistik1_ (mistik1@unaffiliated/mistik1) joined #ltsp.
13:06
<vagrantc>
Roasted_: well, it's just documenting the use of the variable, not the whole theme setup...
13:07
<alkisg>
vagrantc: I think Natty is frozen, and Wheezy is too new, so there's no rush for tagging
13:07
<Roasted_>
didnt work
13:07
I give up
13:08
Im sick of this fricken gray screen
13:08
and these damn guides that simply. dont. work.
13:08
<vagrantc>
alkisg: we've never tagged ltsp-docs
13:08
<alkisg>
Ah ok then
13:08
<vagrantc>
alkisg: it's still 0.99+bzrXXX
13:08
<Roasted_>
alkisg, I would REALLY like to see your gui idea come to life.
13:08mistik1 (mistik1@unaffiliated/mistik1) left irc: Ping timeout: 240 seconds
13:08Nick change: mistik1_ -> mistik1
13:08
<Roasted_>
this simple idea is retardedly difficult in my opinion
13:08
<alkisg>
Roasted_: are you still trying with the same .png?
13:09
Which may be broken?
13:09
<Roasted_>
alkisg, no.
13:09
I took the default one
13:09
edited it with gimp
13:09
put it in mytheme
13:09
updated
13:09
booted client
13:09
gray screen
13:09
<alkisg>
Did you see the ubuntu logo?
13:09
<vagrantc>
alkisg: would be good to do a coordinated audit of LTSP docs and release ltsp-docs 1.0
13:09
<Roasted_>
during bootup, yes
13:10
<alkisg>
Roasted_: ok, try to put everything back as it was, without running ltsp-build-client
13:10
I'm guessing something else breaks your booting
13:10
<Roasted_>
well I have a username box
13:10
to log in, etc
13:10
its just a gray background
13:10
<vagrantc>
Roasted_: comment out LDM_THEME and try again
13:10
<alkisg>
Ah so you're able to login?
13:11
<vagrantc>
Roasted_: do you still get the gray screen?
13:11
<alkisg>
Because I thought last time it was hanged there
13:11
<Roasted_>
alkisg, trying to log in
13:11
yes I can log in
13:12
guess I forgot my test user password. scared me for a second that I couldnt get in. but Im in under administrator.
13:12
the original image is put back. should I update again?
13:13
<alkisg>
Try what vagrantc proposed
13:13
Change lts.conf, don't update image
13:16
<Roasted_>
alright
13:16
we're back
13:16
default screen
13:18
anything else?
13:31
<vagrantc>
Roasted_: so ... did setting it back to the defaults work as expected?
13:31
<Roasted_>
by commenting it out, yes
13:31
<vagrantc>
i.e. no gray screen
13:31
<Roasted_>
well
13:31
I had already put the original image back
13:31
AND commented it out
13:31
and I was back @ defaul
13:31
t
13:32
<vagrantc>
in troubleshooting, it's kind of important to only change one thing at a time...
13:32
<Roasted_>
I know
13:32
I had already put the image back when you said to comment it out
13:32
want me to duplicate what I did
13:32
with only doing 1 change
13:32
<vagrantc>
ok, so right now, you're essentially booted with the defaults, and it works?
13:33
<Roasted_>
yes
13:33
I'm completely at default
13:33
works fine
13:33
<vagrantc>
so let's delete your mytheme directory
13:33
copy and then copy the ubuntu theme over it
13:34
<Roasted_>
mytheme deleted
13:34
<vagrantc>
then copy the ubuntu theme over it
13:34
<Roasted_>
meaning, copy ubuntu and rename the copy to MyTheme ??
13:34
<vagrantc>
i.e. cp -r ubuntu mytheme
13:34
that's what i'd do
13:35
<Roasted_>
done
13:35
<vagrantc>
and then i'd cp ltsp/background.png mytheme/background.png
13:36
(that's a known good background.png)
13:36
or at least, should be
13:36
i can't remember the last time i played with ldm themes...
13:36
<Roasted_>
done
13:36
boot client?
13:36
<vagrantc>
ltsp-update-image
13:37
<Roasted_>
k
13:37
<vagrantc>
then set LDM_THEME=mytheme in /var/lib/tftpboot/ltsp/i386/lts.conf
13:37
and then reboot
13:37
you should get a blue background
13:38* vagrantc is assuming the ubuntu background isn't blue
13:38
<Roasted_>
yeah
13:38
the ubuntu one is orange/white
13:38
its really nice actually
13:38
I just want to customize it so its more fitting for our lab environments
13:38
<vagrantc>
good. so this will be obvious weather it's changed
13:39
<Roasted_>
k
13:39
booting client
13:40
gray background
13:40
how is it THIS hard to do such a simple thing
13:40
<vagrantc>
bizarre
13:40
<Roasted_>
here, LTSP, one click install, but youll spend 9 hours changing the background
13:41
<vagrantc>
Roasted_: set LDM_THEME=ltsp in lts.conf and try again
13:42
<Roasted_>
update-client or just reboot client?
13:42
<vagrantc>
just reboot it
13:42
<Roasted_>
k
13:43
worked
13:43
blue background
13:43
LTSP.org
13:44
<vagrantc>
is there a bg.png, or background.png?
13:44
<Roasted_>
bg.png
13:45
bg.png is the default white/orange one
13:45
and also my edited one
13:45Gadi (~romm@ool-18bbe47a.static.optonline.net) joined #ltsp.
13:45
<vagrantc>
Roasted_: what version of ldm are you running?
13:45
Roasted_: dpkg --root /opt/ltsp/i386 -l ldm
13:46
<Roasted_>
2:2.1.3
13:46
<alkisg>
Roasted_: run the command "file your-image.png"
13:46
E.g. file /opt/ltsp/i386/usr/share/ldm/themes/ubuntu/bg.png
13:46
/opt/ltsp/i386/usr/share/ldm/themes/ubuntu/bg.png: PNG image, 1680 x 1050, 8-bit/color RGB, non-interlaced
13:47
<vagrantc>
so you're on maverick?
13:47
<alkisg>
But with *your* image
13:47
<vagrantc>
alkisg: we've tested that the ubuntu theme works, the ltsp theme works, but copying the bg.png from ltsp to a copy of the ubuntu theme doesn't appear to work ... ?
13:48
<alkisg>
Ah, I thought he put his modified background there?
13:48* alkisg reads back...
13:48
<Roasted_>
alkisg, I modified the default one
13:48
by scribblng on it in gimp
13:48
<vagrantc>
Roasted_: you did copy the ltsp/bg.png to mytheme/bg.png, yes?
13:48
<Roasted_>
yes
13:48
I have LTSP as the background now
13:48
@ login screen
13:49
not the default white/orange ubuntu one
13:49
<vagrantc>
Roasted_: yes, but did you copy ltsp/bg.png to mytheme/bg.png ?
13:49
<alkisg>
Roasted_: for example, it might not be a .png image anymore, even if it has a .png extension. What does the `file` command say?
13:49
<vagrantc>
then ltsp-update-image, and boot with LDM_THEME=mytheme
13:50* Gadi thinks of the pics Roasted is considering.... :)
13:50
<vagrantc>
Roasted_: it's not clear to me that you tested mytheme using most of the parts from ubuntu, and the bg.png from ltsp
13:50
<Roasted_>
vagrantc, yes, I copied ltsp bg.png over to mytheme/bg.png
13:50
then I rebooted the client
13:50
and I now have ltsp bg.png as my background
13:50
its blue, says LTSP, etc.
13:51
<vagrantc>
gah.
13:51* alkisg insists on a broken .png image :)
13:51
<vagrantc>
Roasted_: we tried two things ... one was simply setting LDM_THEME=ltsp
13:52
Roasted_: the other was i *tried* to get you to copy ltsp/bg.png to mytheme/bg.png, ltsp-update-image, and set LDM_THEME=mytheme
13:52
but it's not clear to me what actually happened
13:52
<Roasted_>
alkisg, file bg.png says PNG Image 640.4580 8 bit color RGBA non interlaced
13:52
<alkisg>
1680 x 1050 ?
13:52
<Roasted_>
no
13:52
640 480
13:52
my bad on typo
13:52
<alkisg>
Then you didn't change the ubuntu one, did you?
13:52
<vagrantc>
that's probably the ltsp/bg.png
13:53
<Roasted_>
alkisg, thats the LTSP one
13:53
yes
13:53
<alkisg>
(10:47:02 PM) alkisg: But with *your* image
13:53
Not with the ltsp one. With the one you had problems with.
13:53
<vagrantc>
alkisg: Roasted_ was following my instructions too
13:53
<Roasted_>
yeah
13:53
I didn't do anything different than what vagrantc said
13:53
<vagrantc>
alkisg: i was trying to test the ubuntu theme with the ltsp/bg.png
13:54
<Roasted_>
the default one errored out, yet ltsp bg.png worked
13:54
<alkisg>
Sorry I didn't mean to intrude
13:54
<vagrantc>
we're all confusing each other :)
13:54
Roasted_: wait, you told me it didn't work till you set LDM_THEME=ltsp
13:54
<Roasted_>
right
13:54
it didnt
13:55
<vagrantc>
Roasted_: even though the bg.png is the same in ltsp and mytheme?
13:55
<Roasted_>
bg.png in ltsp and mytheme are two different things
13:55
mytheme has the ubuntu one
13:55
ltsp has the blue ltsp.org one
13:55
alkisg, how about that gui? :(
13:56
<vagrantc>
a gui is not going to help here
13:56
Roasted_: soooooooo......
13:56
<Roasted_>
if a gui application existed, it would
13:56
but, it doesn't, so we're stuck
13:56
<vagrantc>
Roasted_: what i'm trying to get you to test is the mytheme with the bg.png from the ltsp theme
13:56
Roasted_: but all the other parts from ubuntu
13:56
<Roasted_>
so what do I need to do from here
13:57
<vagrantc>
Roasted_: cp ltsp/bg.png mytheme/bg.png
13:57
Roasted_: ltsp-update-image
13:57
Roasted_: LDM_THEME=mytheme in lts.conf
13:58
reboot, and see if you get the blue background with the ubuntu logo
13:58
if that still grey screens, there's something in the ubuntu theme that puts limitations on what you can use for bg.png
13:59
<Roasted_>
if it gray screens, I quit
13:59
I refuse to spend more HOURS doing something so ridiculous
13:59
please. gui for this task.
13:59
:(
13:59
updating now
13:59* vagrantc is getting rather grumpy with this too
14:00Kicer86 (~Kicer86@host-5db0eeee.sileman.net.pl) left irc: Quit: KVIrc Insomnia 4.0.2, revision: 4740, sources date: 20100627, built on: 2010-08-08 18:29:00 UTC http://www.kvirc.net/
14:01
<Roasted_>
gray background
14:01
fk this
14:01* Gadi thinks of a background picture with rolling meadows and a clear sky....
14:01
<Roasted_>
this is total bullshit
14:01
something so simple should NOT be this retardedly difficult
14:02
running build-client now
14:02
<alkisg>
It's possible that the image needs to be the same dimentions
14:02
<Roasted_>
what..
14:02
you think?
14:02
<alkisg>
That's why I suggested modifying the ubuntu one
14:02
<Roasted_>
I did
14:02
<vagrantc>
there's sometihing in the ubuntu theme that needs the .png configured in a particular way
14:02* Gadi always grabs a png from the internet and overwrites ubuntu/bg.png
14:02
<Roasted_>
I scribbled on it in gimp
14:02
I used the EXACT white/orange one
14:03* alkisg tests locally...
14:03
<Roasted_>
lets put it this way
14:03
where does LTSP look for with the background
14:04
ignore the lts.conf
14:04
which BG.PNG does it pull
14:04
is it the one in default
14:04
ubuntu
14:04
or what
14:04
<vagrantc>
in /opt/ltsp/i386/usr/share/ldm/themes/default/
14:04
in /opt/ltsp/i386/usr/share/ldm/themes/default/bg.png
14:04
<Roasted_>
default isnt a directory
14:04
on my end
14:04Technicus (~Technicus@DSLPool-net209-116.wctc.net) joined #ltsp.
14:04
<Roasted_>
I have a text file it looks like
14:05
<vagrantc>
default *should* point to /etc/alternatives/ldm-theme, and /etc/alternatives/ldm-theme should point to /usr/share/ldm/themes/ubuntu
14:05
<Roasted_>
and it appears to be broken
14:05
<vagrantc>
Roasted_: it's a symlink, and it's broken because the symlink is relative to the chroot
14:05
<Roasted_>
so it being broken is okay
14:05
?
14:05
<vagrantc>
it's only "broken" from the server's perspective
14:06
<Roasted_>
okay
14:06
now
14:06
I dont have a default folder
14:06
<vagrantc>
Gadi: are you saying you grab random bg.png and they work?
14:06
<Roasted_>
why not
14:06
yeah, gadi
14:06
tell us your secret
14:06
Ive been at this for hours
14:06
please make my friday happy and tell me your secret
14:06
<vagrantc>
Roasted_: you told me you followed instructions that said to delete the default symlink
14:06
which is what i said was bad
14:06
<Roasted_>
I did?
14:06
<Gadi>
Roasted_: will it make a happy friday?
14:06
<Roasted_>
I dont think I said that?
14:06
Gadi, please!
14:07
Gadi, a 6 pack depends on it
14:07
Gadi, whats your secret
14:07
<Gadi>
ok, then lets do it
14:07
<vagrantc>
11:14 < Roasted_> vagrantc, https://help.ubuntu.com/community/EdubuntuFAQ
14:07
<Gadi>
first of all, deep breaths all around
14:07
<Roasted_>
Gadi, been there done that
14:07
step 2?
14:07
:)
14:07
vagrantc, what about it
14:07
<Gadi>
this has been quite the scrolling exchange
14:07
wait wat
14:07
ok, now
14:07
you run ubuntu or edubuntu
14:07
<vagrantc>
Roasted_: that includes instructions to remove the /opt/ltsp/i386/usr/share/ldm/themes/default
14:07
<Roasted_>
edubuntu 10.10 64 bit DVD
14:07
<Gadi>
wait wait
14:07
<vagrantc>
Roasted_: which are bad instructions
14:08
<Gadi>
wait wait
14:08
<Roasted_>
vagrantc, then why are they on the damn FAQ
14:08
who is supposed to manage that documentation
14:08
<Gadi>
can I throw a flag
14:08
<Roasted_>
Gadi, this isnt NFL (no fun league)
14:08
this is NHL, where men are men
14:08
<Gadi>
crap
14:08
ok, then Ill whistle
14:08
;)
14:08
<Roasted_>
FACE OFF
14:08
<Gadi>
thru the holes in my teeth
14:08
:D
14:08
<Roasted_>
gadi
14:08
secret?
14:09
<alkisg>
Just tried modifying the default ubuntu/bg.png with gimp. Worked fine
14:09
What other things should I try?
14:09* vagrantc is weary of attempting to help someone and getting hostility back
14:09
<Gadi>
ok, so, edubuntu, by default, is gonna pull from the edubuntu theme
14:09
<vagrantc>
so count me out.
14:09
<Roasted_>
vagrantc, appreciate your help brosef
14:09
Gadi, gotcha
14:09
<Gadi>
what happened to the deep breathing?
14:09
geesh
14:09
anyway
14:09
<Roasted_>
I am
14:09
calm, blood pressure low, smiling
14:10
<Gadi>
so, its gonna go for the theme in the edubuntu directory
14:10
<Roasted_>
what is the path to this edubuntu directory
14:10
is this opt ltsp i386 usr share ldm themes
14:10
<Gadi>
if your chroot is /opt/ltsp/i386, then it is: /opt/ltsp/i386/usr/share/ldm/themes
14:10
I believe
14:10
<Roasted_>
STOP
14:10
I dont have "edubuntu"
14:10
I have "ubuntu"
14:11
not sure if its important
14:11
<Gadi>
aha! well, it may be. let's find out
14:11
now
14:11
<alkisg>
I just tried with a "mytheme" copy of the ubuntu theme, and LDM_THEME=mytheme, it worked fine too.
14:11
<Gadi>
do you know what "alternatives" are?
14:11
<Roasted_>
alkisg, :(
14:11
alkisg, fly to PA and fix this thing for me :)
14:11
Gadi, not ringing a bell
14:12
<alkisg>
Roasted_: there's vnc or screen for that, no need for planes
14:12
<Gadi>
Roasted_: ok, so "alternatives" is a system that packages in ubuntu use when multiple packages may want to set a different default thing (like a theme)
14:12
it is a series of symlinks
14:12
located in /etc/alternatives
14:13
so, in this case, we want to know what: /opt/ltsp/i386/etc/alternatives/ldm-theme points to
14:13
which I believe vagrantc asked about before
14:13
but I didnt catch
14:14
so, can u: ls -ld /opt/ltsp/i386/etc/alternatives/ldm-theme
14:14
<alkisg>
Finally, I just tried copying ubuntu/ to mytheme/, and replacing mytheme/bg.png with ltsp/bg.png. Worked fine too: http://imagebin.org/index.php?mode=image&id=142442
14:15
So no matter how much I tried, I couldn't get a gray image
14:15
<Roasted_>
/usr/share/ldm/themes/ubuntu
14:15
whaaaaaaaaat
14:15
alkisg
14:15
<Gadi>
Roasted_: ok, great! so that tells you by default it uses the ubuntu/ theme directory
14:15* alkisg pauses too and leaves it up to Gadi :)
14:16
<Roasted_>
alkisg, what language is that?
14:16
<alkisg>
Greek
14:16
Shouldn't matter
14:16
<Roasted_>
alkisg, oh Id idnt expect it to
14:16
I was just curious
14:16
Gadi, so more or less we're pulling from ubuntu for my theme
14:16
so
14:16
TECHNICALLY
14:16
should I be allowed to drag/drop bg.png into that directory
14:16
and it act as my new background?
14:17
<Gadi>
ok, so, if you have no LDM_THEME specified, you are pulling from ubuntu/ dir
14:18
in which case, you should be able to overwrite bg.png in that directory, then: sudo ltsp-update-image --arch i386, then reboot the client
14:18
<Roasted_>
do I have to reboot the server
14:18
<Gadi>
no
14:18
that would be insane
14:18
:)
14:18
<Roasted_>
gadi
14:18
I have an edited image in ubuntu directory
14:18
and
14:19
this same process failed before
14:19
but
14:19
Ill try it right now again
14:19
<Gadi>
before you do
14:19
what image are you using in there?
14:19
<Roasted_>
uh
14:19
you mean between 32 and 64?
14:19
<Gadi>
no, I mean the png
14:19
<Roasted_>
I took the default one and edited in gimp by scribbling on it
14:19
saved it as bg.png
14:20
and dropped it in place within root nautilus
14:20
thereby overwriting bg.png
14:20
<Gadi>
ah, try grabbing a random one from the internet
14:20
instead
14:20
<Roasted_>
do I keep the same name
14:20
bg.png?
14:20
<Gadi>
yeah
14:20
make sure you keep it as bg.png
14:20* vagrantc envisions writing an LDM hook to grab a random .png off the internet every time
14:21
<Gadi>
honestly, the rolling hills pics look much nicer than the paint splash
14:21
:)
14:21
<Roasted_>
is there a difference between sudo ltsp-update-image -a i386 vs --archi386
14:21* alkisg used a hill pic in his schools, kids loved it
14:21
<Roasted_>
--arch i386 that is
14:22
<Gadi>
I always use --arch
14:22
<Roasted_>
I used -a i386 before
14:22
<Gadi>
dunno why
14:22
<Roasted_>
wonder if that mattered
14:22
<Gadi>
:)
14:22
<Roasted_>
updating
14:22
crossing fingers
14:22
<Gadi>
what was ur random pic?
14:22
<Roasted_>
tux
14:22* Gadi shakes his head
14:22
<Roasted_>
via google.com/images "png image"
14:22
figured it was suitable
14:22
;)
14:23
<Gadi>
btw, did you say you get a grey screen when it doesnt work?
14:23
<Roasted_>
yes
14:23
<Gadi>
how do you manage to get grey?
14:23
<Roasted_>
all slate gray
14:23
I have no idea
14:23
k
14:23
updated
14:23
boot client?
14:23
<Gadi>
you should at least get black
14:24
yeah
14:24
<Roasted_>
I dont get black
14:24
just gray
14:24
with login box
14:24
and a shutdown option or whatever int he lower left
14:24
<Gadi>
ah, so you get the rest of the greeter
14:24
<Roasted_>
yeah
14:24
it works
14:24
its functional
14:24
I can log in, etc.
14:25
gadi
14:25
itw orked
14:25
what the hell
14:25
<Gadi>
so, grey is gtk's doing
14:25
<Roasted_>
I see a fat image of tux here
14:25
<Gadi>
yeah, so you prolly had a bad png image
14:25
<Roasted_>
but Iw as using the default one
14:25
gahhhhhhhhh
14:25
gadi come to pa
14:25
<Gadi>
but then you "saved"
14:25
<Roasted_>
I give you a 6 pack
14:25
yes
14:25
in gimp?
14:25
<Gadi>
and who knows what gimp saved it as
14:25
I mean
14:25
in terms of interlaces, RGBA, bla bla
14:26
<Roasted_>
hm
14:26
lets see if our in-house image will work
14:26
<Gadi>
I never get all that crap straight
14:26
<Roasted_>
with the mascot I have
14:26
<Gadi>
:)
14:26
anyhow, I gotta run
14:26
<Roasted_>
gadi
14:26
I love you
14:26
<Gadi>
we at least a wee bit happier this Friday?
14:26
<Roasted_>
gadi
14:26
yes
14:26
<alkisg>
Well I was yelling about bad png hours ago
14:26
And about "file yourimage.png" :)
14:26
<Roasted_>
alkisg, I know
14:26
<Gadi>
alkisg: you were yelling in Greek
14:26
<Roasted_>
alkisg, I ran file yourimage.png
14:26
<Gadi>
I just had to translate
14:26
<alkisg>
14:26
<Roasted_>
I told you what it said
14:26
<Gadi>
:)
14:27
<alkisg>
Roasted_: no, you run that on the ltsp image
14:27
Not on your image
14:27
<Roasted_>
uhhhhhh
14:27
<alkisg>
640 x 480 etc
14:27
<Roasted_>
oh
14:27
yeah
14:27
alkisg, appreciate your help too
14:27
<Gadi>
anyhow, have a good weekend, guys
14:27
<Roasted_>
like no other
14:27
<Gadi>
cheers
14:27
<Roasted_>
you too gadi
14:27
and mr vagrantc
14:27
<alkisg>
bb Gadi
14:27Gadi (romm@ool-18bbe47a.static.optonline.net) left #ltsp.
14:27
<Roasted_>
you too
14:28
gah
14:28
our images are gif's
14:28
with the mascot
14:28
is there an intelligent way to convert them
14:28
<alkisg>
Gimp => save as
14:28
<Roasted_>
lol
14:28
thats what I did with the default ubuntu one!
14:28
<alkisg>
Ah you have many?
14:28
<Roasted_>
no, just two
14:28
<alkisg>
Maybe you saved it as xcf
14:28
"file" will tell you
14:28
<Roasted_>
nope
14:28
bg.png
14:29
<alkisg>
The extension doesn't matter
14:29
<Roasted_>
k, let me try this again
14:29
Im in gimp with the gif now
14:30
<alkisg>
Yey I managed to get a gray background :D
14:30
I put an .xcf there, renamed as a .png
14:30
<Roasted_>
yeah I just hit the drop down and selected png
14:30
AND
14:30
named it bg.png
14:30
hopefully the drop down does it, as I think I missed that step before
14:31
so when I get an LTSP update, it'll reverse this, right?
14:31
<alkisg>
If you do
14:31
I've yet to see one
14:31
<Roasted_>
k
14:31
Im making a google doc of notes as I go along
14:32
commands, what to watch out for, small notations, etc
14:32
booting client now. crossing fingers.
14:32
hahahahaha
14:32
winner
14:33
<vagrantc>
Roasted_: well, that's why i said to copy it and use LDM_THEME ... then updates won't break your setup (probably)
14:33
<Roasted_>
I gotcha
14:34
I got some artwork to do this weekend
14:34
to make this image work with the spacing, etc
14:34
<alkisg>
vagrantc: have you tried grub2 pxe booting recently? Is it any good?
14:34
<vagrantc>
alkisg: not recently
14:34
alkisg: it's probably still painfully slow ... being based on *ancient* etherboot code
14:35
<alkisg>
Hrm. And syslinux keeps getting better...
14:35
It even has arch and cpu detection now
14:35
<vagrantc>
alkisg: there's a script to generate the grub2 pxe image in debian now ... although update-grub still borks probing for partitions and such
14:35
it's had that for ages
14:36
alkisg: i'd really like a memory detection correlary
14:36
<alkisg>
Since syslinux 4, I believe
14:36
<vagrantc>
oh, you mean built in? or just add-on programs ... because it had the arch detection in debian lenny, released 2 years ago
14:36
with the ifcpu64.m32
14:37
<alkisg>
That was on debian 2 years ago?
14:37
Wow... we got it on maverick on ubuntu :)
14:37
<vagrantc>
it releases too often to keep up with debian :)
14:38
alkisg: alkisg hdt.c32 is really useful, at least for all the computer refurbishing work we do at freegeek
14:39
<alkisg>
Btw the last 10 "serious" bugs I had to work around for the greek school installations, were ubuntu-specific, didn't exist on debian...
14:39
<vagrantc>
alkisg: it's a simple hardware summary interface
14:39
<Roasted_>
im out of here guys
14:39
thanks SO much for the help
14:39
mucho thanks
14:39
beer for all when you visit PA USA :P
14:39
<alkisg>
bb Roasted_
14:39
<vagrantc>
Roasted_: we try ... just remember, we're volunteers too :)
14:39
<Roasted_>
appreciate your persistence with helping
14:39mgariepy (~mgariepy@ubuntu/member/mgariepy) left irc: Remote host closed the connection
14:39
<Roasted_>
I'm in need of a nap badly tho
14:39
so, I'll cyas
14:39
:)
14:39* vagrantc waves
14:44Roasted_ (~jason@206.82.22.190) left irc: Ping timeout: 248 seconds
15:04alkisg (~alkisg@ubuntu/member/alkisg) left irc: Quit: Leaving.
15:10drdata (~drdata@pool-173-57-189-158.dllstx.fios.verizon.net) left irc: Remote host closed the connection
15:11drdata (~drdata@pool-173-57-189-158.dllstx.fios.verizon.net) joined #ltsp.
15:49mikkel (~mikkel@80.71.132.15) left irc: Quit: Leaving
16:01john_s (a8d4f382@gateway/web/freenode/ip.168.212.243.130) joined #ltsp.
16:01
<john_s>
Hi all, I am having a weird issue with ssh connections not working properly between TC and server
16:02
my TC boots fine but won't let me login unless I do ALTF2 and start an SSH session to the server
16:03
once I appept the servers SSH key, then I can log on via ldm
16:03
So something isn't starting automagically AFAIKT
16:12
hmm
16:12
sure is quiet round here
16:14
...
16:15
<vagrantc>
patience
16:16
john_s: sounds like you've changed the server's ip address
16:16
john_s: you need to run ltsp-update-sshkeys, and depending on your distribution, maybe ltsp-update-image
16:16
<john_s>
:-)
16:17
it is tough to be patient. Thanks vagrantc
16:17
<vagrantc>
which distro?
16:17
<john_s>
I have done ltsp-update-sshkeys to no avail
16:17
ubuntu lucid
16:17
<vagrantc>
then you also need to run ltsp-update-image, and reboot your thin client
16:17
<john_s>
thanks very much. I'll do it now.
16:18
<vagrantc>
good luck
16:19
<john_s>
thanks
16:22
vagrantc if you are still around I have another couple of questions
16:23john_s (a8d4f382@gateway/web/freenode/ip.168.212.243.130) left irc: Quit: Page closed
16:28john_s (a8d4f382@gateway/web/freenode/ip.168.212.243.130) joined #ltsp.
16:28
<vagrantc>
!question
16:28
<john_s>
:-(
16:28
<vagrantc>
aw, our bot is gone
16:28
<john_s>
who dat?
16:29
<vagrantc>
john_s: if you have a question, go ahead and ask it, and people will respond if and when they can...
16:29
<john_s>
sure
16:29
<vagrantc>
be sure to tell your distro and version
16:30
we usually have a bot in here so i don't have to type that all by hand :)
16:30
<john_s>
okay ubuntu 10.04, problem with TC's not initiiating ssh persists
16:30
interesting I know very little about IRC things as you can tell
16:31
<vagrantc>
hmmm... that's odd.
16:31
<john_s>
background is I created this server by tarring up directories from a working ubuntu 10.04 LTSP server and splatting them over a fresh install
16:32
I am looking for a short cut to deploying more servers
16:32
<vagrantc>
oh, that sounds like a recipe for disaster :P
16:32
<john_s>
in the past I built them by hand or with scripts
16:32
I agree with you.
16:32
I've been told that it works, but so far I have had shed many LTSP tears
16:33
<vagrantc>
john_s: oh, you mean tarring up /opt/ltsp/ ?
16:33
or the whole system?
16:34
<john_s>
vagrantc: I tarred the whole system with the exception of /dev /sys /boot /tmp
16:34
and a couple of others
16:34
<vagrantc>
that sounds like a time-consuming shortcut
16:35efra_ (euribe@189.228.246.254) left #ltsp ("Saliendo").
16:35
<john_s>
very much so, however I am trying to set up a system that would be easier in the long run to build
16:36
<vagrantc>
apart from the fact that you may end up with files your package management system is unaware of ... i'm not quite sure how it would break the LTSP key generation bits...
16:36
<john_s>
usually a build by "hand" takes me a half a day of tweaking this and that
16:36
<vagrantc>
john_s: have you made edits to lts.conf?
16:36
<john_s>
vagrantc: I have changed it to reflect my new set up.
16:36
<vagrantc>
john_s: or is it a default LTSP install
16:36
?
16:39
<john_s>
vagrantc: lts.conf specifies my local apps and syslog server, time server etc
16:40
but is essentially the same as the one that is working on the server that was cloaned
16:40
<vagrantc>
john_s: did you specify SERVER ?
16:41
john_s: could you paste your lts.conf to ltsp.pastebin.com and post the URL?
16:42
<john_s>
http://pastebin.com/gvF7Wv1N
16:43
whoops
16:43
ignore those numbers
16:43
they don't appear in the original
16:44
<vagrantc>
that's pastebin
16:44
oh, no ... something funny happened :)
16:45
ok, nothing odd in there
16:45
<john_s>
yes, it's like an ssh connection isn't automatically being made. If I do F2 and start one to the server and accept the key then the TC is happy
16:46
<vagrantc>
john_s: what's in /opt/ltsp/i386/etc/ssh/ssh_known_hosts
16:46
should be a line for each ip address and hostname
16:47staffencasa (~staffenca@128-193-147-238.oregonstate.edu) left irc: Quit: Leaving
16:47
<john_s>
4 entries all for the server
16:48
<vagrantc>
one for each ip address?
16:49
<john_s>
actually there are six entries
16:49
there is an rsa and dsa entry by ip and by hostname
16:50
then one rsa and dsa for "server"
16:50
<vagrantc>
to be expected
16:51
so that sounds right
16:51
and do the keys match /etc/ssh/ssh_*host*.pub ?
16:51
do you have anything in /etc/ltsp/known_hosts.*
16:52
and the other question that occurs to me is do you have another LTSP server on the same network ... and are the clients actually booting from that?
16:53
<john_s>
checking...
16:56
vagrantc: per ssh_*host*.pub question keys match except that the hostname is only appended to the end of /etc/ssh/keys*
16:56
so in the chroot the key ends Z12YyBz/doKhw==
16:57
and in /etc/ssh it ends Z12YyBz/doKhw== root@mcbuntu-lucid
16:58
I don't have /etc/ltsp/known_hosts
16:59
clients are booting from the server that i am having trouble with
16:59
<vagrantc>
john_s: the stuff at the end of the key is essentially a comment
17:00
<john_s>
ok. my other servers don't have a file called /etc/lts/known_hosts either
17:00
so I think that must be ok
17:02
vagrantc: do you have a way of setting up a server with a bunch of changes, tweaks etc that is pretty fast? As I said, I've been building them
17:02
and then running some install scripts etc, but it still takes half a day to get stuff working correctly
17:03
I don't really know how other folks manage muliple servers with different configs etc
17:06
when I look at the log messages on the TC is see that ldm.log says "expect saw: The autheticity of host '10.114.6.222 (10.114.6.222) can't be established
17:06
then it gives me an RSA finger print
17:06
so I must not have the key cached in the chroot right?
17:07
<vagrantc>
john_s: i do a lot with debian-installer and debconf preseeding ... the ubuntu alternate installer would work the same way
17:07
john_s: you've rebooted the client after running ltsp-update-sshkeys and ltsp-update-image ?
17:07
<john_s>
yes I did
17:08
so maybe my write permissions are goofed/
17:08
?
17:08
<vagrantc>
john_s: and is that an IP address in /opt/ltsp/i386/etc/ssh/ssh_known_hosts?
17:08
<john_s>
vagrantc: that ip is in know hosts
17:09
<vagrantc>
john_s: when you ssh from a console, what does ~/.ssh/known_hosts add?
17:10
compare that with /etc/ssh/ssh_known_hosts
17:13
<john_s>
vagrantc: on which device am I looking for /etc/ssh/ssh_known_hosts ?
17:13
sorry
17:14
<vagrantc>
well, if you looking from the perspective of the server, /opt/ltsp/etc/ssh/ssh_known_hosts
17:14
if you're looking from the perspective of the thin client, /etc/ssh/ssh_known_hosts
17:14
they should be the same ... if they're different, something's amiss
17:15
er, /opt/ltsp/i386/etc/ssh/ .../
17:15
i keep forgetting the i386 today
17:16
<john_s>
ah ha!
17:17
from the tc perspective /etc/ssh/ssh_known_hosts contains stale ssh entries for the old ip
17:17
do does that mean that I am either too stupid to correctly run ltsp-update-sshkeys
17:17
or does it mean something else?
17:18
shouldn't ltsp-update-sshkeys update that entr?
17:18
err.. entry
17:19
<vagrantc>
yes, it should
17:19
ltsp-update-image didn't take, for some reason
17:20
ls -l /opt/ltsp/images
17:20
<Roasted>
hm, fired up my laptop here (test server with ltsp) to do some work at home and my desktop isnt booting to it. I get the ubuntu splash screen after the initial pxe boot but iltimately I get initramfs - unable to connect to nbd server. All of the google sources I looked at said to do a build-image, but I did that. Is that normally the fix or is there so mething Im missing?
17:20
<vagrantc>
Roasted: that doesn't sound likely to fix initramfs problems
17:21
<Roasted>
it sits at the ubuntu screen for a long, long time, and errors out to the nbd error
17:21
and below is initramfs
17:21
<john_s>
vagrantc: I am afraid you are going to kick me
17:21
<Roasted>
its REQUIRED to reboot the server after build-image, right
17:21
<vagrantc>
john_s: i don't do kicks, only throws
17:21
Roasted: no
17:21
<Roasted>
oh
17:21
<vagrantc>
Roasted: the thin client
17:21
<john_s>
aikido?
17:22
<Roasted>
I did a build-image then update-image on my server
17:22
<vagrantc>
john_s: yes :)
17:22
<Roasted>
and rebooted the thin client
17:22
and yet no dice
17:22
<john_s>
how did I guess
17:22
:-)
17:22
<vagrantc>
speaking of which, i'd best go soo
17:22
n
17:23
<john_s>
vagrantc: thanks you very much for your help. I realized that I didn't append --arch="i386" to my client rebuild
17:23
<Roasted>
vagrantc, is that an error you ran into before??
17:24
<john_s>
vagrantc: gomen nasai!
17:25
<vagrantc>
Roasted: i've heard it, but don't use NBD much (debian defaults to using NFS)
17:26
john_s: the i386/amd64 thing is all sorts of confusing...
17:26
<john_s>
vagrantc:works now!
17:27
<vagrantc>
john_s: glad to hear it!
17:27
<john_s>
vagrantc: I agree, I like it for memory support. I used to use big-mem kernal.
17:27
vagrantc: thanks again, enjoy your class!
17:28john_s (a8d4f382@gateway/web/freenode/ip.168.212.243.130) left irc: Quit: Page closed
17:35
<Roasted>
hm
17:35
I know I had something haywire go on with this install
17:35
I wonder if I borked something earlier on
17:36
reinstalling might (sadly) be the easiest thing as this was my experimental system earlier when I had absolutely *NO* idea what I was doing
17:46
what would be the remedy to this problem... if someone were to choose wlan as the LTSP interface instead of eth0 during initial installation?
17:50john_s (a8d4f382@gateway/web/freenode/ip.168.212.243.130) joined #ltsp.
17:51john_s (a8d4f382@gateway/web/freenode/ip.168.212.243.130) left irc: Client Quit
17:59Marco` (~Marco@203.78.122.41) joined #ltsp.
18:10Marco` (~Marco@203.78.122.41) left irc:
18:27vagrantc (~vagrant@c-24-21-191-93.hsd1.or.comcast.net) left irc: Quit: leaving
19:22Technicus (~Technicus@DSLPool-net209-116.wctc.net) left irc: Remote host closed the connection
19:37
<Roasted>
wow
19:37
fresh install here and I still get the nbd error
19:37
..?
19:44
cancel that. other systems dont exhibit the same issue. weird.
19:49robbie72 (~rob@CPE-60-231-21-101.qld.bigpond.net.au) joined #ltsp.
19:51
<Roasted>
wow
19:51
what a strange fix
19:51
unplugged the tower, held down the power button + pressed it about 8 times, plugged in, pxe booted, now it works
19:51
so strange
20:25
Has anybody tinkered with the "thin client manager" in the software center? It seems to be great but I'm looking for a way to SEE the user's screens.
20:31RiXtEr (~blah@69-179-105-91.dyn.centurytel.net) left irc: Read error: Connection reset by peer
20:38patrickmw (~pwright@ip68-231-4-153.ph.ph.cox.net) joined #ltsp.
21:45alkisg (~alkisg@ubuntu/member/alkisg) joined #ltsp.
22:46Mava (~Mava@a91-154-45-79.elisa-laajakaista.fi) joined #ltsp.
23:14alkisg (~alkisg@ubuntu/member/alkisg) left irc: Quit: Leaving.
23:14alkisg (~alkisg@ubuntu/member/alkisg) joined #ltsp.
23:14alkisg (~alkisg@ubuntu/member/alkisg) left irc: Client Quit
23:16alkisg (~alkisg@ubuntu/member/alkisg) joined #ltsp.
00:00--- Sat Mar 12 2011