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


Channel log from 7 October 2014   (all times are UTC)

00:29
<vagrantc>
haha! LTSP booted on cubox-i!
00:30
only local media is u-boot on microsd.
00:41Ark74 has left IRC (Ark74!~quassel@189.220.254.152.cable.dyn.cableonline.com.mx, Remote host closed the connection)
00:43FrankBlues has left IRC (FrankBlues!~alex@c-174-52-202-7.hsd1.ut.comcast.net, Remote host closed the connection)
00:45vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Quit: leaving)
04:21
<work_alkisg>
!learn alkisg-todo as support xnbd-proxy for local caching: https://bitbucket.org/hirofuchi/xnbd/wiki/Home#!scenario-2-simple-proxy-server-distributed-copy-on-write
04:21
<ltsp`>
The operation succeeded.
05:30bauerski has left IRC (bauerski!~witekb@frodo.psp.opole.pl, Remote host closed the connection)
05:32bauerski has joined IRC (bauerski!~witekb@frodo.psp.opole.pl)
06:00vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)
06:06adrianorg has left IRC (adrianorg!~adrianorg@177.156.229.246, Ping timeout: 244 seconds)
06:08adrianorg has joined IRC (adrianorg!~adrianorg@177.156.229.246)
07:06bitcheker has joined IRC (bitcheker!~bitchecke@dynamic-adsl-62-10-106-19.clienti.tiscali.it)
07:27vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Ping timeout: 260 seconds)
08:02mikkel has joined IRC (mikkel!~mikkel@mail.dlvs.dk)
09:22mealstrom has joined IRC (mealstrom!~Thunderbi@46.63.63.163)
09:43adrianor1 has joined IRC (adrianor1!~adrianorg@177.156.229.246)
09:46adrianorg has left IRC (adrianorg!~adrianorg@177.156.229.246, Remote host closed the connection)
10:29khildin has joined IRC (khildin!~khildin@ip-213-49-116-36.dsl.scarlet.be)
10:49adrianor1 is now known as adrianorg
11:23Grembler has joined IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net)
11:37bauerski has left IRC (bauerski!~witekb@frodo.psp.opole.pl, Quit: Leaving.)
11:59freedomrun has joined IRC (freedomrun!~quassel@unaffiliated/freedomrun)
12:00khildin has left IRC (khildin!~khildin@ip-213-49-116-36.dsl.scarlet.be, Remote host closed the connection)
12:10|GuS| has left IRC (|GuS|!~gustavo@unaffiliated/gus/x-663402, Quit: Konversation terminated!)
12:20markit has joined IRC (markit!~marco@host208-38-static.243-95-b.business.telecomitalia.it)
12:29Faith has joined IRC (Faith!~paty@unaffiliated/faith)
12:42moquist has joined IRC (moquist!moquist@2600:3c03::f03c:91ff:fe50:bfa5)
13:18adrianorg has left IRC (adrianorg!~adrianorg@177.156.229.246, Ping timeout: 246 seconds)
13:20adrianorg has joined IRC (adrianorg!~adrianorg@177.134.57.45)
13:37mikkel has left IRC (mikkel!~mikkel@mail.dlvs.dk, Quit: Leaving)
13:46F-GT has left IRC (F-GT!~phantom@ppp59-167-136-109.static.internode.on.net, Ping timeout: 245 seconds)
13:57markit has left IRC (markit!~marco@host208-38-static.243-95-b.business.telecomitalia.it, Ping timeout: 250 seconds)
14:01gvy has joined IRC (gvy!~mike@altlinux/developer/mike)
14:05
<sbalneav>
Morning all
14:15mtsoule has joined IRC (mtsoule!4275eb8a@gateway/web/freenode/ip.66.117.235.138)
14:18
<mtsoule>
nfs is running on my server, but "Failed to mount root directory", using SLES11 sp3 and ltsp 2.6.20.9 i am pterry new to this so please be kind. any suggestions?
14:22
<sbalneav>
Not familiar with SLES. Does it use NFS root mounting or the compressed image method>
14:22
?
14:22markit has joined IRC (markit!~marco@host179-38-static.243-95-b.business.telecomitalia.it)
14:23
<mtsoule>
i beleive compressed image, but i could be wrong.. how can i tell?
14:24
<sbalneav>
check your /etc/exports file.
14:24
Any /opt/ltsp entries in there?
14:24
<mtsoule>
it does say "mounting 192.168.1.6:/opt/ltsp/i386 on /newroot/nfsroot failed input/output error
14:25
yes there are entries there
14:26
<sbalneav>
ok
14:26
Have you restarted your NFS server?
14:26
And exported the filesystem with exportfs -a?
14:26
<mtsoule>
yes i have and it apears to be running
14:27
i dont think i exportfs -a
14:28
<sbalneav>
Try that, as root
14:29
<mtsoule>
i did, and received: neither 'subtree_check' or 'no_subtree_check' specifed. what does that mean?
14:30
<sbalneav>
cat you paste the contents of the /etc/exports lines?
14:31
The line looks like this for me, on debian systems:
14:31
/opt/ltsp *(ro,no_root_squash,async,no_subtree_check)
14:32
<mtsoule>
im not on the same network so i will have to type it
14:34
i have everything but the astrisk and no_subtree_check
14:34
let me add that and restart nfs
14:39
ok, my exportfs -a didnt error on me, no output. but still receiving mounting 192.168.1.6:/opt/ltsp/i386 failed
14:41
<sbalneav>
What dhcp server does sles use? ISC?
14:43
<mtsoule>
i have the server configured as a static ip, 192.168.1.6 i dont know what ISC is, sorry i am a noobe
14:43
<sbalneav>
So which dhcp server is installed?
14:43
Use your distros package management tools to find out.
14:44alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
14:44
<mtsoule>
checking now
14:45
ISC 4.2.4 P2-0 20.1
14:47
<sbalneav>
ok, so you should have a "dhcpd.conf" file somewhere
14:47
try "/etc/dhcp3"
14:47
<mtsoule>
yes, i have /etc/dhcpd.conf
14:47
<sbalneav>
ok, what are the contents?
14:47
!pastebin
14:47
<ltsp`>
pastebin: the LTSP pastebin is at http://ltsp.pastebin.com. Please paste all text longer than a line or two to the pastebin, as it helps to reduce traffic in the channel. Don't forget to paste the URL of the text here.
14:48
<sbalneav>
Paste them to the pastebin
14:48
<mtsoule>
will do, give me a sec
14:49alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Remote host closed the connection)
14:51
<mtsoule>
http://pastebin.com/C9QZEYQp
14:57
<sbalneav>
Well, root path looks right.
14:58
Anything on the server's logs?
14:58
<mtsoule>
lemme check...
15:00vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)
15:00
<sbalneav>
Hey vagrantc
15:00
So, got a jessie server going
15:00
Got a i386 chroot
15:01
got ltsp-pam installed
15:01
I've selected the LTSP option in lightdm
15:01
but I only get an xterm
15:02
So somethingg's not right there.
15:02* vagrantc waves
15:02
<vagrantc>
hm.
15:02
i'll try to reproduce
15:04
<sbalneav>
gotta be something in $CHROOT//usr/share/ltsp-pam/xsession
15:06mtsoule has left IRC (mtsoule!4275eb8a@gateway/web/freenode/ip.66.117.235.138, Ping timeout: 246 seconds)
15:08
<vagrantc>
sbalneav: testing as a thin client?
15:08
<sbalneav>
Yes
15:08
Full thin at this point.
15:10
<vagrantc>
we need to implement some sort of SCREEN_SCRIPTS=nothankyou option :)
15:11
<sbalneav>
Is that what's buggering us up?
15:13
<vagrantc>
dunno yet, i remember having to do an ugly hack for that
15:13
could be some systemd-ism
15:14
haven't yet got my setup with ltsp-pam ... wanted to make sure the basic thin client worked alright before testing this newfandangled stuff
15:16
apparently, ltsp-pam is from april 2013
15:16
really has been a while since i worked on it ...
15:17
well, we did some touch-up in october ... but that's, surprise, a year ago now!
15:17
<sbalneav>
ok, I'll start trying to dig into it.
15:18freedomrun has left IRC (freedomrun!~quassel@unaffiliated/freedomrun, Remote host closed the connection)
15:19freedomrun has joined IRC (freedomrun!~quassel@unaffiliated/freedomrun)
15:19
<vagrantc>
sbalneav: you've set DEFAULT_DISPLAY_MANAGER ?
15:20
<sbalneav>
Yes. Lightdm does come up
15:20
oh, BTW, ltsp-pam needs to depent on net-tools
15:20
since the xsession script executes netstat
15:20
<vagrantc>
ok
15:24
sbalneav: well, i don't even get that far. lightdm fails to start
15:25
<sbalneav>
hm.
15:25
Interesting, even though in the lightdm greeter I've selected the LTSP option, the lightdm log says it's running /etc/X11/Xsession default
15:26
<vagrantc>
sbalneav: that's how it worked
15:29
hrm.
15:29
i don't think ltsp handles .service files
15:29
which are used by systemd
15:30
<sbalneav>
shouldn't it be doing a "/etc/X11/Xsession LTSP"?
15:32
<vagrantc>
ah i had set default-display-manager incorrectly.
15:37
<sbalneav>
You seeing the same thing?
15:37
It gets past the auth, which is good.
15:39freedomrun has left IRC (freedomrun!~quassel@unaffiliated/freedomrun, Remote host closed the connection)
15:39
<vagrantc>
i've got mate installed in the chroot, and it's running that locally
15:39
it's not using the LTSP session
15:39
but i don't see Xsession anywhere
15:39
maybe lightdm doesn't use Xsession anymore... :/
15:40
<sbalneav>
The logs seem to indicate it is.
15:40
<vagrantc>
this time it worked
15:41
<sbalneav>
What did you do?
15:41
<vagrantc>
first time, i selected the session, entered username/password ... ended up running a local session
15:41
second time, i entered username/password, selected session ... ended up running a remote session
15:46
let's see if i can reproduce that reliably
15:49
<sbalneav>
hm, let me try
15:50
yup, that works
15:50
wierd.
15:51
<vagrantc>
the other weird thing was it seemed to be using "xsession" not "Xsession"
15:51
<sbalneav>
let me try again...
15:52
<vagrantc>
sbalneav: so, essentially the weirdness of how this is set up is it runs Xsession (or xsession?) on the local client, and the session handles ssh'ing to the server
15:52
<sbalneav>
right
15:52
<vagrantc>
so all the set up variables (that SSH doesn't helpfully clean out) may be referring to stuff running on the local client ... i.e. dbus, etc.
15:58gvy has left IRC (gvy!~mike@altlinux/developer/mike, Ping timeout: 272 seconds)
15:58
<sbalneav>
Hm, I'm not logging out. I didn't set the symlink to the cleanup script... one sec.
15:59Phantomas has joined IRC (Phantomas!~phantomas@ubuntu/member/phantomas)
16:02
<vagrantc>
when i switch ttys, sometimes the session dies
16:02Grembler has left IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net, Quit: I Leave)
16:04mip5 has joined IRC (mip5!~chatzilla@208.72.71.69)
16:07
<sbalneav>
It's so wierd. When I boot the thin client, the best it can do is 1024x768
16:08
once I get logged in and do an xrandr -q, 1280x1024 is an option. The first, in fact
16:08freedomrun has joined IRC (freedomrun!~quassel@unaffiliated/freedomrun)
16:08
<sbalneav>
xrandr -s 0 works perfectly.
16:08
Why doesn't it figure this out when it boots?!
16:09
nope, still hanging on logout
16:11* vagrantc feels a gear in the head fall off it's rusty axle
16:11
<sbalneav>
ah, wierd.
16:12gvy has joined IRC (gvy!~mike@altlinux/developer/mike)
16:12
<mip5>
Is there up to date documentation for this: https://help.ubuntu.com/community/UbuntuLTSP/ChrootCronjobs, and https://help.ubuntu.com/community/UbuntuLTSP/AutomatedTCShutodwn
16:15
<vagrantc>
mip5: nearly all of that functionality should be built-in now
16:15
you might have to add cron to KEEP_SYSTEM_SERVICES in lts.conf
16:15
<sbalneav>
hmm
16:15
/usr/lib/x86_64-linux-gnu/polkit-mate/polkit-mate-authentication-agent-1 hangs up the logout. The cleanup script doesn't stop it.
16:16
Ah, and setting "user-session" to "ltsp" in the $CHROOT/etc/lightdm/lightdm.conf file fixed the other.
16:17
<vagrantc>
i've also got pulseaudio and xprop -root spy running
16:18
<mip5>
which lts.conf should I be using - in /opt/ltsp/i386/etc ... or /var/lib/tftpboot/ltsp/i386/lts.conf - how do they relate? I'm using 12.04.5
16:19
<vagrantc>
use the one in tftp
16:20
the comments in /opt/ltsp/i386/etc/lts.conf should tell you
16:20
<mip5>
That's what I thought, but I didn't have one in /var/lib/tftp, so I wondered. Should it get created automatically?
16:20
<vagrantc>
no
16:21
ltsp-config lts.conf
16:21
that'll create one for you with some useful comments.
16:22
<mip5>
awesome! Thanks. I'd edit the documentation if I knew enough, but feel that's better done by someone else in the community.
16:22
<vagrantc>
thats pretty much what everyone thinks
16:22
which is why the documentation is almost always out of date
16:23
<mip5>
;-), yeah, I guess so. I do love what y'all do. It's amazing, really.
16:23
<sbalneav>
when we execute the x-session-manager;ltsp-cleanup.sh, shouldnt that be "x-session-manager > .xsession-errors 2>&1 ; ltsp-cleanup.sh?
16:24
<vagrantc>
sbalneav: it's worth a try
16:25
<sbalneav>
k trying
16:26
<vagrantc>
ah, we don't run Xsession at all
16:26
<mip5>
vagrantc: no man page for ltsp-config. Command not found when I try it as: sudo ltsp-config lts.conf
16:27
<vagrantc>
mip5: you're running that on the server?
16:27
the ltsp-server?
16:28
<mip5>
yes
16:29
The only ltsp commands I have in /usr/sbin are: ltsp-build-client ltspfsmounter ltsp-update-kernels
16:29
ltsp-chroot ltsp-update-image ltsp-update-sshkeys
16:29
<vagrantc>
mip5: i don't ubuntu well enough to know when it was introduced.... it was in ltsp 5.4.0-1 in debian.
16:31
sbalneav: probably ">>", though
16:31
<sbalneav>
right.
16:31
duh
16:31* sbalneav smacks forhead
16:31
<mip5>
vagrantc: I'm running ltsp-server 5.3.7, looks like. Ubu 12.04.5
16:33
<vagrantc>
sbalneav: ah, and we're running Xsession locally, presumably...
16:33
sbalneav: i was thinking we should also run Xsession there ...
16:34
<sbalneav>
Probably.
16:34
Ah, good, now at least we're writing to .xsession-errors.
16:34
<mip5>
vagrantc: can I just find a default lts.conf file, and create it in /var/lib/tftpboot/ltsp/i386/lts.conf, or would you recommend I do something else?
16:34
<sbalneav>
LOL
16:35
Now that we're doing that... it logs out properly :D
16:35
<vagrantc>
mip5: sure.
16:35
sbalneav: nice!
16:35
<sbalneav>
vagrantc: Where's the source for the ltsp-pam package, I'll commit the change.
16:35* vagrantc curses having lts.conf in multiple places
16:35* vagrantc shakes fists
16:35
<vagrantc>
sbalneav: i don't remember... *sigh*
16:36
sbalneav: i think mine is in https://code.launchpad.net/~vagrantc/ltsp/ltsp-pam-examples which was forked from your copy, maybe?
16:37
the version in my apt repository is older than the commits in that repository
16:38
well, looks like i should roll a new package, and not hit my head against the wall on things that were already fixed.
16:40
<mip5>
vagrantc: hate to ask this, but I aptitude doesn't find ltsp-config. Which sources should I add to /etc/apt/sources.list to get this? I suspect this will require updating my other ltsp- packages as well. That's okay with me.
16:40
<sbalneav>
lol
16:40
Scotty is usually pretty permissive.
16:40
HAHAHAH
16:41
I am indeed.
16:41
<vagrantc>
:)
16:41
sbalneav: probably should sort out a better license :)
16:41
<sbalneav>
What's better for you? gpl2 or 3?
16:41
What does debian want?
16:42
K, I gotta roll for lunch. If you could get, like, an upstream ltsp-pam package that I'd have write access to sorted out by the end of the day, I think we'd be in business!
16:42
back in an hour or so..
16:42
<vagrantc>
i generally go with gpl2+ ... which allows you to make it GPL3 if you need at some point, but keeps the GPL3 haters at bay.
16:49
<mip5>
vagrantc: can you point me to a default lts.conf example? I can't seem to find one.
16:51
<vagrantc>
/usr/share/doc/ltsp-server/examples/lts.conf ?
16:52
or /usr/share/doc/ltsp-client-core/examples/lts.conf ?
16:53
<mip5>
thanks
16:59andygraybeal has left IRC (andygraybeal!~andy@h62.217.213.151.dynamic.ip.windstream.net, Ping timeout: 240 seconds)
17:14
<mip5>
vagrantc: Still trying to get auto shutdown to work. What's the best way? SHould I just add it to my client crontab?
17:15
<vagrantc>
!lts.conf | echo mip5
17:15
<ltsp`>
mip5 lts.conf: (#1) http://manpages.ubuntu.com/lts.conf, or (#2) lts.conf manpage is available in the ltsp-docs package
17:15mip5_ has joined IRC (mip5_!~chatzilla@c-76-25-142-89.hsd1.co.comcast.net)
17:15
<vagrantc>
mip5: should be CRONTAB_01 .. 09 and SHUTDOWN_TIME ...
17:16
!lts.conf | echo mip5_
17:16
<ltsp`>
mip5_ lts.conf: (#1) http://manpages.ubuntu.com/lts.conf, or (#2) lts.conf manpage is available in the ltsp-docs package
17:18mip5 has left IRC (mip5!~chatzilla@208.72.71.69, Ping timeout: 260 seconds)
17:18mip5_ is now known as mip5
17:20
<mip5>
okay - I'll look at that some more. Thanks.
17:20mip5 has left IRC (mip5!~chatzilla@c-76-25-142-89.hsd1.co.comcast.net, Remote host closed the connection)
17:20mip5 has joined IRC (mip5!~chatzilla@208.72.71.69)
17:21
<mip5>
having some network troubles....
17:30
vagrantc: I have the lts.conf file configured now with a line: CRONTAB_01 = "30 16 * * 1-5 /sbin/halt". But I also had followed the previous documentation, and have a line RCFILE__02 = /etc/ltsp/crontab.sh, which I copied from the old documentation: http://pastebin.com/dcBuiRCU - Should I get rid of the crontab.sh reference and file now in this version of ltsp?
17:31
I couldn't get it to work last night at the end of the day.
17:33
<vagrantc>
mip5: no need for crontab.sh
17:34
at least, there shouldn't be.
17:34
test it and find you
17:34
find out
17:34
<mip5>
okay - will I need to rebuild the client image?
17:34
to get the latest changes to lts.conf
17:37
<vagrantc>
you only need to rebuild the image if you change things inside the chroot.
17:39
sbalneav: uploaded a new ltsp-pam package
17:39* vagrantc really needs to make that a signed repository
17:40gvy has left IRC (gvy!~mike@altlinux/developer/mike, Quit: Leaving)
17:46
<mip5>
thanks - I'll let y'all know how it goes.
17:46mip5 has left IRC (mip5!~chatzilla@208.72.71.69)
17:48
<vagrantc>
sbalneav: yay. new package fixes localapps
17:49championofcyrodi has joined IRC (championofcyrodi!~championo@50-205-35-98-static.hfc.comcastbusiness.net)
17:49championofcyrodi has left IRC (championofcyrodi!~championo@50-205-35-98-static.hfc.comcastbusiness.net)
17:50freedomrun has left IRC (freedomrun!~quassel@unaffiliated/freedomrun, Remote host closed the connection)
18:12
<sbalneav>
awesome
18:14
.bu6
18:15
So, I wonder what we need to do to get localdev going.
18:29
Hm, lightdm seems to ignore the "allow-tcp" option. I have it set to true, but it's still starting X with "-nolisten tcp"
18:54
Yeah, that's a problem... :D
18:56LTSP_at_Home has joined IRC (LTSP_at_Home!6b015ac2@gateway/web/freenode/ip.107.1.90.194)
18:57
<LTSP_at_Home>
Hello, is it possible to have this set-up at home, without connecting it to the outside world? I assume it is as I've seen multiple in-classroom uses and I doubt they want the students to tinker from their own home/methlab/what-have-you
18:57
<vagrantc>
LTSP_at_Home: sure
18:59Phantomas has left IRC (Phantomas!~phantomas@ubuntu/member/phantomas)
19:00
<sbalneav>
vagrantc: I guess I can't write to your ltsp-pam, eh?
19:00
I've made another change to the xsession file.
19:01
<vagrantc>
sbalneav: ok, let's push it to ~ltsp-upstream then
19:02
let's see if i remember how to do that...
19:07
<LTSP_at_Home>
vagrantc: Is it harder than installing a regular desktop OS? I've done about 5 of those, but I haven't done much with servers or anything
19:08
<vagrantc>
LTSP_at_Home: a little harder, but not hugely so
19:08
<LTSP_at_Home>
vagrantc: ok. I just install it, and leave that computer hooked into my home router; do I need a switch to make it work?
19:09
<vagrantc>
but your router doesn't have an internet connection?
19:10
<LTSP_at_Home>
It does.
19:10
<vagrantc>
what did you mean by "without connecting it to the outside world" ?
19:11
sbalneav: i also forgot to push my edits
19:11
sbalneav: you may lso be interested in git-remote-bzr ... :)
19:13
<LTSP_at_Home>
vagrantc: I use a remote desktop at work, and I can access it via the IP from anywhere. I wouldn't necessarily need that from the house.
19:21
does that make more sense or no?
19:21
<vagrantc>
i don't quite follow, no.
19:22
LTSP isn't a protocol like RDP, VNC or NX ... it's about network booted clients.
19:23
<LTSP_at_Home>
vagrantc: OK. So, If I install this at my house and hook it up to my router, will it be accessbile only from inside of my house?
19:23
<vagrantc>
i don't really understand your goal, here.
19:23
LTSP might not be what you want or need...
19:24
<sbalneav>
vagrantc: Are you creating the ~ltsp-upstream branch?
19:25
<vagrantc>
sbalneav: trying to figure out how, yes.
19:25
do this so rarely...
19:26
<sbalneav>
heh
19:26
That's my problem too.
19:27
<LTSP_at_Home>
vagrantc: I want to install it and let me be able to access the same desktop from any of the computers in my house....does it not work that way?
19:28
<sbalneav>
LTSP_at_Home: You'd need to set up a server at home to do that. A diskless workstation can't just boot over the internet.
19:35alkisg-android has joined IRC (alkisg-android!~yaaic@176.92.246.44)
19:37
<alkisg-android>
new openssh... supports socket forwarding!!!
19:37
deprecates arcfour though
19:39
<LTSP_at_Home>
sbalneav: So I put Ubuntu server on, then install LTSP onto that?
19:41
<alkisg-android>
Ubuntu desktop, not server
19:42
<sbalneav>
LTSP_at_Home: yes.
19:42
Hey alkisg-android
19:43
<alkisg-android>
Hi Scotty, hows the hackfest going?
19:43
<vagrantc>
alkisg-android: i seem to recall you thinking socket forwarding will make a lot of LTSP6 dreams possibl
19:43
<sbalneav>
alkisg-android: Good, squashed a couple of bugs so far.
19:43* vagrantc has just barely dusted off the cobwebs
19:43
<vagrantc>
alkisg-android: do you remember how to create new repositories on launchpad?
19:44
<alkisg-android>
Yup it would help a lot... e.g. instead of ltspfs we can have reverse sshhfs
19:44
<LTSP_at_Home>
sbalneav: Easy enough (I guess...) Then how does booting into it work with a desktop machine?
19:44
<sbalneav>
You'd have to install LTSP, make sure you've got DHCP configured correctly, etc.
19:44
<vagrantc>
LTSP_at_Home: actually, you'd probably want to install the ubuntu desktop edition, not server edition
19:44
<alkisg-android>
i think simple bzr push new-dir etc
19:45
<vagrantc>
LTSP_at_Home: since LTSP is essentially a server of Desktops, it needs all the desktop packages.
19:47* alkisg-android is sorry that he doesn't have much free time for the hackfest this month...
19:47
<sbalneav>
NP
19:51
<LTSP_at_Home>
vagrantc: So install it on an Ubuntu desktop box, but then how do I login to it?
19:51
<vagrantc>
LTSP_at_Home: you install the ltsp package, build the ltsp environment ... do all the ltsp things.
19:52
LTSP_at_Home: though from your question about logging in, i'm still not sure if LTSP does what you want/need.
19:52
<LTSP_at_Home>
vagrantc: I'm beggining to doubt it too. haha. Thanks for the help though!
19:55
<vagrantc>
LTSP_at_Home: essentially, LTSP allows you to have a single server on a local network, and network boot several computers on the same local network to log into it.
19:56
LTSP_at_Home: so you can have multiple users logged into the same server with their own independent sessions
19:59
<LTSP_at_Home>
Right. I think that's what I'm trying to say, just using the wrong words. How do I login to LTSP once I have it installed on an Ubuntu desktop?
20:00
<vagrantc>
you network boot a coputer, it comes up with a login screen
20:02
sbalneav: https://code.launchpad.net/~ltsp-upstream/ltsp/ltsp-pam
20:02
<sbalneav>
vagrantc: You are my hero
20:02
I'll push up a patch in a few minutes.
20:02
<vagrantc>
apparently i just had to bzr push to the right URL
20:04alkisg-android has left IRC (alkisg-android!~yaaic@176.92.246.44, Ping timeout: 272 seconds)
20:06
<LTSP_at_Home>
vagrantc: Ah ok. So that machine could theoretically have a local disk with its own OS or switch and boot to the network and have the terminal server, right?
20:07
<vagrantc>
LTSP_at_Home: sure
20:07
LTSP_at_Home: or no disk at all
20:10
<LTSP_at_Home>
vagrantc: Right. OK, that makes more sense. How do I force the computer with network boot to find the LTSP?
20:10
<vagrantc>
LTSP_at_Home: you configure your dhcp server, or set up proxydhcp
20:13
<LTSP_at_Home>
vagrantc: DHCP = Chinese to me, but I'm sure that's beyond the scope of this help board here
20:13
thanks!
20:14
<vagrantc>
!dhcp
20:14
<ltsp`>
dhcp: http://wiki.ltsp.org/twiki/bin/view/Ltsp/DHCP
20:14
<vagrantc>
wow. that's outdated.
20:16
<LTSP_at_Home>
haha. It didn't take me to a DHCP page..
20:18
It's OK, I'll look it up when I actually try to do this. Thanks for the help!
20:18LTSP_at_Home has left IRC (LTSP_at_Home!6b015ac2@gateway/web/freenode/ip.107.1.90.194, Quit: Page closed)
20:56
<sbalneav>
vagrantc: Pushed a mod.
20:58
<vagrantc>
sbalneav: that looks mich simpler :)
20:58
much, also
21:04
<sbalneav>
Well, if TCP's enabled, we don't want to launch TWM :D
21:04
We just want to launch x-session-manager with the DISPLAY variable set.
21:04
Seems to work here.
21:06
<vagrantc>
and that enabled TCP is essentially the correlary to LDM_DIRECTX ?
21:12
<sbalneav>
Yes
21:12
I would say so.
21:14
<vagrantc>
so, rather than the single ltsp.desktop file ...
21:14
we need to generate .desktop files for each session on the server
21:15
localdev needs some plumbing
21:15
anything else?
21:15
sound?
21:15
<sbalneav>
Prolly.
21:15
Lets tackle localdev tomorrow, how's that sound?
21:15
Lenny seems not bad
21:16
<vagrantc>
lenny?
21:16
<sbalneav>
I might skip wheezy here at legal aid and just go straight to lenny
21:16
erm
21:16
<vagrantc>
you mean jessie? :)
21:16
<sbalneav>
jessie, lenny
21:16
One of them thar things.
21:16
:D
21:16
<vagrantc>
what's roughtly 9 years of code going to make a difference? :)
21:16F-GT has joined IRC (F-GT!~phantom@ppp59-167-136-109.static.internode.on.net)
21:17
<sbalneav>
heh
21:17
So tomorrow, we'll get the sound and the usb sticks goin'
21:18
Then we'll generate the .desktop files properly.
21:18* vagrantc wonders if jessie will have a reasonably short freeze
21:19bitcheker has left IRC (bitcheker!~bitchecke@dynamic-adsl-62-10-106-19.clienti.tiscali.it, Quit: { exiting })
21:19
<sbalneav>
hope so.
22:06Faith has left IRC (Faith!~paty@unaffiliated/faith, Quit: Saindo)
22:08here_and_there has left IRC (here_and_there!~ivaylo@193.54.153.250, Ping timeout: 260 seconds)
22:08here_and_there has joined IRC (here_and_there!~ivaylo@193.54.153.250)
22:49freedomrun has joined IRC (freedomrun!~quassel@unaffiliated/freedomrun)
23:12adrianorg has left IRC (adrianorg!~adrianorg@177.134.57.45, Quit: leaving)
23:17adrianorg has joined IRC (adrianorg!~adrianorg@177.134.57.45)
23:24ogra_ has left IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de, Ping timeout: 250 seconds)
23:29ogra_ has joined IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de)