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


Channel log from 4 January 2008   (all times are UTC)

00:06subir has joined #ltsp
00:20open_la1 has joined #ltsp
00:20daya has quit IRC
00:23subir has quit IRC
00:25subir has joined #ltsp
00:26
<AzMoo>
Well it seems that I just wasted a whole bunch of time. One of the websites that we have to be able to access from these kiosks *requires* IE. That pisses me off so much.
00:26
So, no more ltsp for a while. Thanks for the help people.
00:30AzMoo has quit IRC
00:35daya has joined #ltsp
00:38open_lad has quit IRC
00:39daya has quit IRC
00:39subir has quit IRC
00:39open_la1 has quit IRC
00:53subir has joined #ltsp
01:24ogra has quit IRC
01:24ogra has joined #ltsp
01:25open_lad has joined #ltsp
01:42vagrantc has quit IRC
02:32MasterOne has joined #ltsp
02:42
<MasterOne>
well, after a lot of playing around, I am about to give up. Is there really no way, to get direct rendering to work on a thin client? Maybe already seen my attempts to get it to work with help of Gadi in December: glxinfo on the thin client (as local app) reports "direct rendering: YES", but glxinfo on the server (logged in from the thin client) says "direct rendering: NO". This was tested with the radeon and savage graphics dri
02:42
ver, with LDM_DIRECT = YES. If anybody has any additional idea, please tell. As mentioned earlier, someone seems to have got compiz to work in a thin client setup, but this is only possible, if the ltsp server recognizes the direct rendering support on the TC, which is just not the case in my setup.
02:43mikkel has joined #ltsp
02:47wizzy__ has joined #ltsp
02:49
<wizzy__>
Trying to debug Local Devices - edubuntu 7.10. It used to work. I get as far as step 4 of DebugLocalDev - is "/usr/sbin/ltspfsmounter /tmp add" correct ? http://www.opensubscriber.com/message/ltsp-discuss@lists.sourceforge.net/7887911.html thinks otherwise
02:51
With the original, I get "couldn't read LTSPFS_TOKEN atom"
02:51
I have no /var/run/drives directory on the server
02:53MasterOne has quit IRC
02:56
<johnny>
thre is a bug on that
02:56
in launchpad
02:56
if you don't have them working
03:02
<wizzy__>
is the bug in the DebugLocalDev instructions ?
03:02
USB drives have worked before on this setup
03:04open_lad has quit IRC
03:12
<johnny>
aha.. ok
03:23MasterOne has joined #ltsp
03:25open_lad has joined #ltsp
03:25subir has quit IRC
03:26open_lad has quit IRC
03:55meduxa has joined #ltsp
04:06subir has joined #ltsp
04:07makghosh has joined #ltsp
04:14
<wizzy__>
Having read around, my problem was that I was already logged in to the server via ssh -X
04:15
ltspfsmounter has a hard-coded loocalhost:10.0 in it - it should use ssh -X from the client to set the DISPLAY variable
04:17subir has quit IRC
04:17Egyptian[Home] has quit IRC
04:18Egyptian[Home] has joined #ltsp
04:49lns has quit IRC
04:50Guaraldo has joined #ltsp
04:57ari_stress has left #ltsp
05:04Guaraldo has quit IRC
05:04Guaraldo has joined #ltsp
05:09MasterOne has quit IRC
05:30elisboa has quit IRC
05:33rjune_ has quit IRC
06:09poliveira has quit IRC
06:29Guaraldo has quit IRC
06:30Guaraldo has joined #ltsp
06:53Guaraldo has quit IRC
06:53Guaraldo has joined #ltsp
06:57Guaraldo has quit IRC
06:57Guaraldo has joined #ltsp
07:29otavio has joined #ltsp
07:42cliebow has joined #ltsp
07:44rjune_ has joined #ltsp
08:27ari_stress has joined #ltsp
08:50Gadi has joined #ltsp
08:52chup has joined #ltsp
08:53chupacabra has quit IRC
08:55
<cliebow>
anyone an mdadm guru??
08:55npman has joined #ltsp
09:05K_O-Gnom has joined #ltsp
09:09daya has joined #ltsp
09:10
<daya>
is there is any way to get the mo file for ldm,
09:13ari_stress has left #ltsp
09:32cyberorg has quit IRC
09:47cyberorg has joined #ltsp
09:56Q-FUNK has joined #ltsp
09:58sepski has joined #ltsp
10:03tux_440volt has joined #ltsp
10:14daya has quit IRC
10:14mopey has joined #ltsp
10:23jammcq has joined #ltsp
10:58
<cliebow>
hey there little buddy!!
10:58staffencasa has joined #ltsp
11:14bobby_C has joined #ltsp
11:18Topslakr| has quit IRC
11:19Topslakr| has joined #ltsp
11:19Q-FUNK has quit IRC
11:31Guaraldo has left #ltsp
11:32Guaraldo has joined #ltsp
11:36Guaraldo has quit IRC
11:36Guaraldo has joined #ltsp
11:45sonjag has joined #ltsp
11:45vagrantc has joined #ltsp
11:47Guaraldo has quit IRC
11:48Guaraldo has joined #ltsp
12:01tux_440volt has quit IRC
12:02bobby_C has quit IRC
12:07Q-FUNK has joined #ltsp
12:08spectra has joined #ltsp
12:14Q-FUNK has quit IRC
12:14Q-FUNK has joined #ltsp
12:19spectra has quit IRC
12:26meduxa has quit IRC
12:33Gadi has left #ltsp
12:36outofrange has left #ltsp
12:39BadMagic has quit IRC
12:40BadMagic has joined #ltsp
12:53Mauricio_ has joined #ltsp
12:56
<Mauricio_>
Hi... I have trouble with some thin clients that have a new card that requires the e1000 driver from intel... I have already tested the driver and my question is how to compile that driver into the ltsp chroot... the problem that I have rigth now is that when I try to compile the driver, kernel version on the chroot is different from the server (server has 2.6.14-22-server and ltsp chroot has 2.6.14-22-386)
12:57
so the make utility complaint that the kernel source is not available (requests 2.6.22-14-server)
12:59Mauricio__ has joined #ltsp
13:00
<Mauricio__>
Hi... I have trouble with some thin clients that have a new card that requires the e1000 driver from intel... I have already tested the driver and my question is how to compile that driver into the ltsp chroot... the problem that I have rigth now is that when I try to compile the driver, kernel version on the chroot is different from the server (server has 2.6.22-14-server and ltsp chroot has 2.6.22-14-386), so the make utility complaint that the kerne
13:00
l source is not installed (requests 2.6.22-14-server!)
13:00Mauricio_ has quit IRC
13:05mighty-d has joined #ltsp
13:06whitey_ has joined #ltsp
13:06
<mighty-d>
Hi, can you tell me the state of slackware integration for ltsp 5.0, would you advice me to run ltsp 5.0 with the supplied packages on slackware (running ubuntu bits on slack)?? how does it handles it?? is there any unsupported function on this approach?? thanks in advance :)
13:07
<whitey_>
hello all, anyone here intimately or at least very familiar with sunray thin client architecture/technology? I knwo this is a LTSP channel and i am tuning both ltsp and sunray env's and having to do performance testing in each env
13:07
question is why when I sniff the session for ltsp and a pxe boot client it is in teh range of 65-70K packets just to get teh session setup and on sunray arch and a sun ray dtu it's 200-300 packets?
13:08
what are they doing soo differently to save on bw?
13:08
<vagrantc>
mighty-d: we occasionally get reports of people expressing interest in ltsp5 for slackware, but little to no work towards that end
13:09
<whitey_>
I just wouldn't think that running ALP (sunray) v.s. nfs via tcp (ltsp) would be drastically different in terms of network utilization
13:09
freaked me out a bit
13:09
<Q-FUNK>
vagrantc: someone yesterday was asking why LPTS on Debian depends specifically on kernel-nsf-server, instead of kernel | userspace ?
13:09
<vagrantc>
mighty-d: using the ubuntu or debian tarballs, you'll need to compile ltspfs for slackware in order to support local devices, and probably want pulseaudio too
13:09
<whitey_>
thoughts?
13:10
<vagrantc>
Q-FUNK: because nobody has demonstrated that it works with the userspace server?
13:10
Q-FUNK: and i've experienced problems trying to get it working
13:10
<mighty-d>
vagrantc, is there any docs on this? i couldnt find any on the web site??
13:10
<vagrantc>
Q-FUNK: but the most recent version is a recommends instead of a depends
13:10
!tarball
13:11
<ltspbot>
vagrantc: "tarball" is http://wiki.ltsp.org/twiki/bin/view/Ltsp/Ltsp5TarballInstructions
13:11
<Q-FUNK>
vagrantc: people often experience timeouts with the kernel one and tend to trust the suerspace one better.
13:11
<vagrantc>
mighty-d: try that
13:12
<mighty-d>
vagrantc, i have seen thie, but it doesnt say anything about ltspfs
13:12
<vagrantc>
mighty-d: well, fix it then :P
13:12
<whitey_>
heh
13:13
<vagrantc>
Q-FUNK: i think debian-edu has made it possible to use the userspace server, but i haven't heard any reports proving that it works
13:13
<whitey_>
hey vagrantc, I dont knwo if you got my message the other day but I just wanted to pass along a word of thanks for gettin me sorted out on my debian LTSP5 setup and gettin sound/ltspfs working
13:13
<vagrantc>
Q-FUNK: and in the end, file a bug report if there's something broken
13:13
<mighty-d>
ive been running ltsp 4.2 on slack for almost a year now, i remember installation wasnt so smooth, but the results are so great its worth the effort, now we are thinking on an upgrade and i want to try ltsp 5.0, what worries me is that there is so little docs about it...
13:13
<whitey_>
went from the 0.99 version on debian to the 5.0.39 and all is well and smokin now
13:13
<vagrantc>
whitey_: glad to help
13:14
<whitey_>
you were my hero for the evening :-D hah
13:14
<vagrantc>
mighty-d: it would really be best on integrating ltsp5 into slackware, rather than installing ubuntu on top of slackware ... the additional effort is minimal
13:15
a little out of date, but:
13:15
!integration
13:15
<ltspbot>
vagrantc: "integration" is http://wiki.ltsp.org/twiki/bin/view/Ltsp/IntegratingLtsp
13:16
<mighty-d>
vagrantc, i can try to integrate it, if it is possible (for mortals like me), and if i can get some help from you guys or some documents to try it, im not an expert on kernels, and lot of stuff (im not completely ignorant either) ...
13:17
<whitey_>
btw everyone on here who is interested, LTSP5 bits work flawlessly in a virtualized Xen environment and i would assume the same is true for a VMware env as well as older revisions of LTSP
13:17
just a couple of random thoughts
13:17
<Q-FUNK>
yup
13:17
<whitey_>
maybe someone here might find them useful sometime
13:17
<Q-FUNK>
we use it that way for development purposes
13:17
<whitey_>
nice
13:18
<vagrantc>
mighty-d: well, the key thing about ltsp5 is you use the existing infrastructure of the host distro for most everything... you only need focus on the small parts that make an ltsp environment different, for the most part
13:19
<whitey_>
i even have my setup going on a debian box w/ LTSP5 bits serving up TC sessions and installed VMware WS6 on it and have my lady run that for her XP pro needs ontop of LTSP adn it works flawlessly and I dont ever hear her complain about slowness or screen repainting or anything
13:19
and she even uses photoshop cs3 w/ that setup
13:19
I was thouroughly impressed
13:19
<Q-FUNK>
each developer at our company has edubuntu running on ... was it vmware ... and connecting to a second physical NIC.
13:19
<whitey_>
yeah that 5% of 'special bits' that LTSP provides and use 95% of the inherent distro capabilities/p[kgs
13:20
or so I hear :-D
13:20
gotta luv highyl repeatable solutions with minimal modifications needed to redeploy
13:21
or integrate in this case
13:24
hey vagrantc do you have any random thoughts on my bandwidth perplexing/concerning issue that I discovered a bit ago posted here?
13:24
<mighty-d>
vagrantc, where should i start?
13:25
<whitey_>
or do you still have your sanity intact and have the luxury of mostly being exposed to ltsp dev/usage and no sunray experience?
13:29sonjag has quit IRC
13:29sonjag has joined #ltsp
13:32zodman has quit IRC
13:33Guaraldo has quit IRC
13:34Guaraldo has joined #ltsp
13:37Guaraldo has quit IRC
13:37Guaraldo has joined #ltsp
13:38
<mighty-d>
vagrantc, im mostly concerned about speed, do you think i could run an ubuntu 7.10 server with almost 25 clients over CORE 2 DUO 2.0 Ghz 2.0GB RAM, clients will be runing firefox and open office mostly, there will be some others using some rdp x application. Im running ltsp 4.2 on slackware because of its stability and as i said it rocks, but as im seeing is difficult to run ltsp on slackware i was thinking ubuntu could be another good way to g
13:38
o..
13:38
thin clients are pentium mmx with 128 mb ram..
13:39
<vagrantc>
mighty-d: it might be a little low on RAM ... but probably fine
13:39
mighty-d: low on the server ram, that is
13:39
!serversizing
13:39
<ltspbot>
vagrantc: Error: "serversizing" is not a valid command.
13:39
<vagrantc>
!serversize
13:39
<ltspbot>
vagrantc: "serversize" is http://wiki.ltsp.org/twiki/bin/view/Ltsp/ServerSizing
13:40
<mighty-d>
vagrantc, it is currently working and none of my users complain about speed
13:41Guaraldo has quit IRC
13:41
<vagrantc>
mighty-d: switching to xubuntu or or another window manager
13:41Guaraldo has joined #ltsp
13:43
<mighty-d>
vagrantc, i need to run kde on clients, my users are not computer experts and xfce isnt that friendly :( , if it were for ill run blackbox on the clients :P
13:45
<vagrantc>
mighty-d: i've actually found xubuntu to be much more useable than plain xfce... it's really a different thing, i'd say
13:45
mighty-d: but if kde you must, then KDE it is
13:46
mighty-d: local device support in KDE doesn't work as well...
13:47
<mighty-d>
vagrantc, what do you mean, doesnt work as well? , is it like doesnt work at all?
13:47Mauricio__ has quit IRC
13:47
<vagrantc>
mighty-d: well, you may need to make a symlink on the Desktop manually to get an icon to show up on the desktop
13:48
mighty-d: or just have the users know to go to /media/USERNAME/DEVICENAME
13:48
<mighty-d>
vagrantc, this can be automated?, like we are used to in 4.2?
13:48
<vagrantc>
mighty-d: i do not know if it can be automated
13:48
haven't used KDE in years
13:49
from what people have said, you need some way to create a symlink on the user's Desktop dir to get things to show up
13:49
that's all i know
13:49
<mighty-d>
vagrantc, does this function as a udev rule or something?
13:49
<vagrantc>
well, it uses udev on the client side
13:50
but on the server side, where the files are actually mounted, it doesn't use udev ...
13:50
you might be able to put the appropirate hooks in client-side ...
13:50
<mighty-d>
vagrantc, ok ... so your advice is to discard the slackware box, and go for a ubuntu server ?
13:51
<johnny>
that would be your best bet
13:51
or debian..
13:51
<vagrantc>
yeah
13:52
the version in debian stable is admittedly a little outdated ...
13:52
though you can get backports of ltsp-related software pretty easily
13:52
(i mostly work on debian)
13:52* sutula pipes up that vagrantc has done a good job keeping etch-backports current :)
13:52
<sutula>
...or was I supposed to tell your AM that :)
13:52
<vagrantc>
sutula: finally got an i386 build for sid's ltsp/ldm
13:53
sutula: my NM process is stalled ... mostly due to my reluctance to do anything but work on debian packaging...
13:53
mostly ltsp
13:53
<mighty-d>
vagrantc, how is sound doing on kde ?
13:54
<sutula>
vagrantc: My AM got busy with his thesis so mine is stalled as well, and I don't want to prod him because I'm really busy at work
13:54
<vagrantc>
mighty-d: can't say for sure, but the current approach just uses ALSA, and KDE surely supports ALSA
13:54
<johnny>
there seemed to be issues with local devs on kde
13:54
outside of the other local dev bugs
13:54
<vagrantc>
well, uses pulseaudio+alsa ... but still
13:55
mighty-d: i think debian-edu uses KDE, and uses ltsp as well, you might want to ask there about some of the issues
13:56
<mighty-d>
vagrantc, ok thanks
13:57Q-FUNK has quit IRC
13:57
<vagrantc>
mighty-d: irc,debian.org #debian-edu
13:58makghosh has quit IRC
13:58
<mighty-d>
vagrantc, thank you for beeing so kind...
14:00Guaraldo has quit IRC
14:07K_O-Gnom has quit IRC
14:15otavio has quit IRC
14:24sonjag has quit IRC
14:25
<mighty-d>
vagrantc, ok i have decided to try to integrate ltsp on slackware first, i can document my work if it is success and you can use it on the website, however as there is so little documents about it, would you help me to accomplish this?
14:27
<vagrantc>
mighty-d: gladly
14:27
<cliebow>
we will all help as we can
14:28
<vagrantc>
yeah
14:28
mighty-d: i'll be busy the next couple days, but probably be more available next week
14:30
<mighty-d>
cliebow, you have helped me a lot with 4.2 deployment, and i dont know if i thanked you that time :)
14:31
vagrantc, ok... ill get to it then... :)
14:31
<vagrantc>
!integration
14:31
<ltspbot>
vagrantc: "integration" is http://wiki.ltsp.org/twiki/bin/view/Ltsp/IntegratingLtsp
14:31
<vagrantc>
mighty-d: that outlines a lot of it, though the bzr URLs are probably outdated
14:32
<mighty-d>
vagrantc, ok, so as i have been reading, i need to make a new installation of slack 12 inside /opt/ltsp, what packages should i include there?
14:32
<vagrantc>
mighty-d: you'll need to download code from: https://code.launchpad.net/~ltsp-upstream/
14:33
<cliebow>
pleased to share..
14:33
<mighty-d>
vagrantc, how many time do you think this will *cost* ?
14:33
<vagrantc>
depends on how much slackware assumes you're installing to a hard drive
14:34
<mighty-d>
vagrantc, i meant the whole thing, getting ltsp 5.0 to work on my clients under slack with distro integration..
14:35
<vagrantc>
mighty-d: 1-100000 hours
14:35
really, i can't give you an estimate
14:35
it's a fairly simple process, but there probably are some things that will take a long time
14:35
<mighty-d>
vagrantc, lol ... well that was a good reference :) , ok should i download trunk? or is there any stable release?
14:35
<vagrantc>
mighty-d: not really a stable release yet
14:37
anyways, i've gotta go now...
14:37
good luck!
14:37
<mighty-d>
ok, thanks vagrantc ill go for trunk then
14:37
<vagrantc>
oh, you'll need ldm-trunk, ltsp-trunk and ltspfs-trunk ...
14:38
mkdst you'll need later
14:38vagrantc has quit IRC
14:39zodman has joined #ltsp
14:42cyberorg has quit IRC
14:49cliebow has quit IRC
14:54
<yanu>
on ltsp-4.2 : kdm on the client works, i want to log in, but i've been kicking out, any id?
15:02otavio has joined #ltsp
15:04Q-FUNK has joined #ltsp
15:13
<mighty-d>
cliebow, what applications should i install on "Install an instance of the distro into a subdirectory on the server" ??
15:20mikkel has quit IRC
15:23mistik1_ has joined #ltsp
15:23zodman has left #ltsp
15:23mistik1 has quit IRC
15:24mistik1_ is now known as mistik1
15:26cyberorg has joined #ltsp
15:26bobby_C has joined #ltsp
15:33npman has quit IRC
15:54Drakeweb has joined #ltsp
15:57
<Drakeweb>
ogra: you responded to a mailing list question I had about getting audio onto a thin client. One of your points was that the user should be part of the "audio" group. I've checked my users and groups settings, and I have no "audio" group, although there is a tick box for "use audio devices" in user privileges, which is ticked. Should I create an "audio" group, or is there something else?
15:57
<johnny>
check the groups of the sound devices
15:58
<Drakeweb>
how?
15:58
<johnny>
ls -l /dev/snd or whatever it is on ubuntu
15:59
<Drakeweb>
I've got controlC0, lots of pcms, a seq and a timer
15:59sepski has quit IRC
15:59
<johnny>
yes
15:59
what are they set
15:59
with ls -l
15:59Drakeweb has quit IRC
16:00Drakeweb has joined #ltsp
16:01
<Drakeweb>
apologies - My pidgin died!
16:01
please repeat anything I missed in my absence ...
16:01
<johnny>
what are they set to?
16:01
ls -l
16:02
<Drakeweb>
crw-rw----
16:02
<johnny>
that's the group you need to be in for starters
16:02
<Drakeweb>
owner root, group audio
16:02
<johnny>
yes.. audio group
16:02
you do have one
16:02
<Drakeweb>
but "audio" doesn't show up in my group list
16:02
(admittedly, using GUI)
16:03
how do I add a user to the audio group?
16:03
<johnny>
what distro?DE?
16:03
err DE
16:03
<Drakeweb>
edubuntu
16:03
<johnny>
with gnome?
16:03
<Drakeweb>
yep
16:03
<johnny>
i see audio in mine ubuntu
16:04
i don't know what problems you got :)
16:04
you can edit it manually in /etc/group by adding users to the audio group like user1,user2,user3
16:05
<Drakeweb>
system -> admin - > users & groups -> group settings shows no audio group
16:08
just checked, the correct users are already in the audio group.
16:08
but no sound on my thin client
16:14
<johnny>
and you're using ldm?
16:15
<Drakeweb>
yes
16:16
<mighty-d>
Install LTSP supplied scripts/executables into the tree .. what does this means?
16:16
where are these scripts/executables?
16:16
<yanu>
on ltsp-4.2 : kdm on the client works, i want to log in, but i've been kicking out, anyone hints?
16:17
<johnny>
won't find much help with ltsp 4.2..
16:17
you might have to wait awhile to gt an answer unless you're lucky
16:17
hmm..
16:18
Drakeweb, i havent setup sound on my clients, so i don't knowthe issues as of yet
16:18
no speakers there
16:18
i'll test it with headphones sometime
16:18
<yanu>
i had the same thing , but i forgot how to solve it ...
16:18
<Drakeweb>
thanks.
16:19
I've set up a thin client for my daughter, and I'm trying to get her to learn all about linux
16:19
but she wants/needs sound, and I just can't help at the moment.
16:19
everything else works - remote printing, file sharing, internet etc.
16:20
just no sound.
16:30jammcq has quit IRC
16:37
<whitey_>
hey all here is a random thought for the day and a coupel fo features that I dont not know if the dev's of LTSP5 and ongoing are thinking about (I am sure it has crossed their minds though), will LTSP ever have smart card or session mobility support o is that something that really isnt a focus or high priority right now
16:38
also an integrated vpn option, I am sure there is a way to do this fairly easily w/ openvpn/etc but just cant quite wrap my head around how this would be implemented...in teh chrooted env
16:38
?
16:38
<stgraber>
why would you need a vpn in the chroot ?
16:38
everything is supposed to go through SSH no ?
16:39
<whitey_>
also what about a web mgmt interface (tomcat/etc) to control client devices like disabling usb or audio devices on a per client basis
16:40
well yeah I suppose your right...so was or is LTSP never really concerned with remote/WAN deployments or that just takesa a bit fo firewall trickery and all that needs to be forwarded is ssh since it's all wrapped through that and connnecting to the LDM display mgr?
16:40
just trying to figure out how to do WAN deployments of this technology...site to site vpn?
16:40gonzaloaf has quit IRC
16:41
<whitey_>
ssh tunnels/etc
16:41
<stgraber>
once the initrd is loaded the two only ports that will be used (assuming you don't use network swap) is 2000 (nbd) and 22 (ssh)
16:43
<whitey_>
so your essentially sayting that WAN deployments/integration should not be too difficult?
16:43bobby_C has quit IRC
16:43
<stgraber>
I heard of some probjects for the web mgmt interface thing, nothing that could do it live (settings apply at next reboot), for the smart card support I don't really know, that should be easy to implement in the chroot, then you have to manage the authentication part, session mobility is something that many people asked for I think but it's hard to implement that on the current X
16:44
hmm, well as soon as you have a DHCP server giving the next-server variable and the client can access that server on tftp (to get the initrd), nbd (to mount the hdd) and ssh (for auth and the session) that should work yes
16:56staffencasa has quit IRC
16:57
<whitey_>
awesome thanks much!
16:57
btw what's NBD?
16:57
I am guessing network boot something (daemon)
16:59
<loather-work>
network block device
17:04mighty-d has quit IRC
17:06
<whitey_>
ohh cool
17:06
is that what ltspfs uses? that and a combo of fuse on teh client?
17:07
<stgraber>
ltspfs AFAIK is an addon to sshfs (using fuse)
17:07
nbd is what's used instead of NFS since LTSP5
17:09
<whitey_>
well the client bits/env are run from nfs still thourhg right from teh chrooted build env?
17:09
and that's what teh /opt/ltsp nfs share export is there for?>
17:10
very cool btw that ltspfs is sshfs in a sense
17:10
<stgraber>
that's with the old LTSP, the new one uses a squashfs image of /opt/ltsp/i386 exported using nbd
17:10
<whitey_>
when ya say old how old?
17:10
4 rev/release?
17:10
I am using 5.0.39 LTSP5 ion debian etch
17:10
and i see metric tons of nfs (tcp) traff when i am running my sessions
17:10
am i missing something very obvious here
17:11
?
17:11
<stgraber>
the move to nbd was done with gutsy (for Ubuntu)
17:11
maybe Debian hasn't done the move yet
17:11
<whitey_>
hmm I am using backports
17:11
<stgraber>
argh, vagrantc isn't around :)
17:11
<whitey_>
I would think that is teh newest stuff for ltsp
17:11
I hear that
17:11
hah
17:12
<stgraber>
feisty = 5.0.7, gutsy = 5.0.39 and hardy (devel release) = 5.0.39+20071127 (snapshot)
17:12
<whitey_>
maybe we'll get lucky and he'll pop in any time now or fill us/mainly me in later since you seem to be more familiuar w/ the LTSP architecture/underlying components than me as of yet
17:13
well I am running the 5.0.39 release under debian etch via backports as suggested by vagrantc a few days ago
17:13
good times
17:13
<stgraber>
but I doubt Ubuntu 5.0.39 = Debian 5.0.39
17:13
you should ask him how to have nbd working on Debian
17:13
as it's easier to route a single tcp port than the UDP stuff of NFS :)
17:14
<whitey_>
I hear ya
17:14
will do
17:15Top|OLPC has joined #ltsp
17:38Egyptian[Home] has quit IRC
17:47Drakeweb has quit IRC
17:52Top|OLPC has quit IRC
18:11MacGruber has joined #ltsp
18:11
<MacGruber>
Hi, you guys might be able to help me out here...
18:13
One of my clients boots, the other doesn't.
18:13
/var/log/syslog says:
18:13
Jan 4 16:05:14 konan dhcpd: DHCPDISCOVER from 00:1b:eb:02:00:95 via eth0
18:13
Jan 4 16:05:15 konan dhcpd: DHCPOFFER on 10.0.5.249 to 00:1b:eb:02:00:95 via eth0
18:13
Jan 4 16:07:48 konan dhcpd: DHCPDISCOVER from 00:1b:eb:02:00:95 via eth0
18:13
Jan 4 16:07:49 konan dhcpd: DHCPOFFER on 10.0.5.249 to 00:1b:eb:02:00:95 via eth0
18:13
...but the dhcp information is ignored!
18:13
tcpdump says...
18:14
16:07:57.537361 IP 10.0.5.3.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length: 300
18:14
16:07:57.969295 arp who-has 10.0.5.249 tell 10.0.5.3
18:14
(basically)
18:14
The thin client that is not booting says at startup:
18:15
"Intel UNDI, PXE-2.0 (build 078)"
18:15
The thin client that _does_ boot says at startup:
18:16
Intel UNDI PXE 2.1 (Build...)
18:17
what gives?
18:22cliebow has joined #ltsp
19:04MacGruber has quit IRC
19:46allobjects has joined #ltsp
19:52otavio has quit IRC
19:56
<allobjects>
Can someone please tell me if it is reasonable to use ltsp across a wireless network. I'm looking at a tiny environment e.g. maximum 2 clients
20:15
<sutula>
allobjects: The first problem you'll have is booting...some of the boot protocols across a gateway (I'm assuming something about your wireless hardware here)
20:16
allobjects: I hit that and decided it wasn't really worth pursuing
20:17cliebow has left #ltsp
20:34whitey_ has quit IRC
20:59allobjects has quit IRC
21:12
<jgbillings>
so i'm trying to get k12ltsp6 going, and i have the gray screen of death? Anyone know how to turn gdm on?
21:14
oh heh, i just typed 'gdm'
21:15
<johnny>
what is k12ltsp even based on
21:15
i don't know anything about it
21:15
<jgbillings>
fedora 6
21:15
<johnny>
is it based on ltsp 4?
21:16
or ltsp 5
21:16* johnny guesses 4..
21:16
<johnny>
you'll only find on and off help with ltsp 4.x here
21:16
most of the folks hanging out in here use an ltsp5 based setup
21:16
the ones who chat at least
21:16
<jgbillings>
I thought this was ltsp5
21:17
<johnny>
if it uses gdm, then it's prolly not
21:17
it should use ldm
21:17
and it should also use it by default
21:18
<jgbillings>
oh its 4.2
21:20
<johnny>
yeah.. afaik fedora doesn't have a finished ltsp 5 setup
21:20
only debian/ubuntu do
21:21
it is being worked on tho
21:21
you're prolly gonna have to stick with the k12ltsp resources
21:21
if they have an irc channel
21:21
unless you get lucky
21:21
and run into a 4.x person here
21:22
<jgbillings>
seems to be working now
21:23
eventually i'll go with edubuntu, couldn't get it going in gutsy
21:25
<johnny>
i'm using it with gutsy atm
21:27
<jgbillings>
what are your thin clients like
21:28allobjects has joined #ltsp
21:28
<allobjects>
sutula: sorry I was away
21:29
sutula: what assumptions are you making about my network ?
21:31
I really don't have much choice about using wireless without costly cabling... the clients btw will be resonable machines e.g. 700-800mhz boxes with harddrives so I would be happy to boot something minimal locally of their HDD and then connect to ltsp server
21:31
<johnny>
you could..
21:31
no guarantees on the speed tho
21:32
<allobjects>
also the existing machies are already runnning Ubuntu wirelessly with no problems
21:32
<johnny>
but if you actually boot a kernel locally
21:32
then you're not using ltsp anymore
21:34
<allobjects>
so is there something else I should be looking at ? I probably don't need full lightweight client. I have 2 x good 3.0Mhz desktops and 2 x lower end 700-800mhz desktops and would like to leverage processing and graphics of the faster machines for th eother 2
21:36
should the lower powered machines just be using something more conventional (sorry still a bit of a linux newbie) on an application by application basis ? e.g. for some applications, run them off a session on the more powerfull box but display on the less capable machine ?
21:42
<johnny>
you could use nx
21:42
and run them remotely
21:50allobject1 has joined #ltsp
21:51
<allobject1>
sorry lost my connection, not sure which of my questions got through or lost in the ether
21:52
is it reasonable to setup an existing ubuntu desktop machine with ltsp server support and continue to use this machine as a normal desktop workstation ? assuming only one other ltsp client will be connected
21:57allobjects has quit IRC
22:18allobject1 has quit IRC
22:21muh2000_ has joined #ltsp
22:22
<muh2000_>
:(
22:22
when i try to login it just gets back to the logon screen :(
22:22
kdm[28968]: segfault at 0000000000000000 rip 00002b792db6f040 rsp 00007fff7e0427f8 error 4
22:26sid has left #ltsp
22:37
<muh2000_>
is there a way to change the login screen? instead of kdm -> xdm?
22:56F-GT has quit IRC
22:58F-GT has joined #ltsp
23:05tux_440volt has joined #ltsp
23:11rjune_ has quit IRC
23:14vagrantc has joined #ltsp
23:29muh2000_ has quit IRC
23:29muh2000_ has joined #ltsp
23:45makghosh has joined #ltsp
23:51
<muh2000_>
hmmm it is not kdm. gdm produces the same error.