|00:06||subir has joined #ltsp|
|00:20||open_la1 has joined #ltsp|
|00:20||daya has quit IRC|
|00:23||subir has quit IRC|
|00:25||subir has joined #ltsp|
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.
So, no more ltsp for a while. Thanks for the help people.
|00:30||AzMoo has quit IRC|
|00:35||daya has joined #ltsp|
|00:38||open_lad has quit IRC|
|00:39||daya has quit IRC|
|00:39||subir has quit IRC|
|00:39||open_la1 has quit IRC|
|00:53||subir has joined #ltsp|
|01:24||ogra has quit IRC|
|01:24||ogra has joined #ltsp|
|01:25||open_lad has joined #ltsp|
|01:42||vagrantc has quit IRC|
|02:32||MasterOne has joined #ltsp|
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
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:43||mikkel has joined #ltsp|
|02:47||wizzy__ has joined #ltsp|
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://firstname.lastname@example.org/7887911.html thinks otherwise
With the original, I get "couldn't read LTSPFS_TOKEN atom"
I have no /var/run/drives directory on the server
|02:53||MasterOne has quit IRC|
thre is a bug on that
if you don't have them working
is the bug in the DebugLocalDev instructions ?
USB drives have worked before on this setup
|03:04||open_lad has quit IRC|
|03:23||MasterOne has joined #ltsp|
|03:25||open_lad has joined #ltsp|
|03:25||subir has quit IRC|
|03:26||open_lad has quit IRC|
|03:55||meduxa has joined #ltsp|
|04:06||subir has joined #ltsp|
|04:07||makghosh has joined #ltsp|
Having read around, my problem was that I was already logged in to the server via ssh -X
ltspfsmounter has a hard-coded loocalhost:10.0 in it - it should use ssh -X from the client to set the DISPLAY variable
|04:17||subir has quit IRC|
|04:17||Egyptian[Home] has quit IRC|
|04:18||Egyptian[Home] has joined #ltsp|
|04:49||lns has quit IRC|
|04:50||Guaraldo has joined #ltsp|
|04:57||ari_stress has left #ltsp|
|05:04||Guaraldo has quit IRC|
|05:04||Guaraldo has joined #ltsp|
|05:09||MasterOne has quit IRC|
|05:30||elisboa has quit IRC|
|05:33||rjune_ has quit IRC|
|06:09||poliveira has quit IRC|
|06:29||Guaraldo has quit IRC|
|06:30||Guaraldo has joined #ltsp|
|06:53||Guaraldo has quit IRC|
|06:53||Guaraldo has joined #ltsp|
|06:57||Guaraldo has quit IRC|
|06:57||Guaraldo has joined #ltsp|
|07:29||otavio has joined #ltsp|
|07:42||cliebow has joined #ltsp|
|07:44||rjune_ has joined #ltsp|
|08:27||ari_stress has joined #ltsp|
|08:50||Gadi has joined #ltsp|
|08:52||chup has joined #ltsp|
|08:53||chupacabra has quit IRC|
anyone an mdadm guru??
|08:55||npman has joined #ltsp|
|09:05||K_O-Gnom has joined #ltsp|
|09:09||daya has joined #ltsp|
is there is any way to get the mo file for ldm,
|09:13||ari_stress has left #ltsp|
|09:32||cyberorg has quit IRC|
|09:47||cyberorg has joined #ltsp|
|09:56||Q-FUNK has joined #ltsp|
|09:58||sepski has joined #ltsp|
|10:03||tux_440volt has joined #ltsp|
|10:14||daya has quit IRC|
|10:14||mopey has joined #ltsp|
|10:23||jammcq has joined #ltsp|
hey there little buddy!!
|10:58||staffencasa has joined #ltsp|
|11:14||bobby_C has joined #ltsp|
|11:18||Topslakr| has quit IRC|
|11:19||Topslakr| has joined #ltsp|
|11:19||Q-FUNK has quit IRC|
|11:31||Guaraldo has left #ltsp|
|11:32||Guaraldo has joined #ltsp|
|11:36||Guaraldo has quit IRC|
|11:36||Guaraldo has joined #ltsp|
|11:45||sonjag has joined #ltsp|
|11:45||vagrantc has joined #ltsp|
|11:47||Guaraldo has quit IRC|
|11:48||Guaraldo has joined #ltsp|
|12:01||tux_440volt has quit IRC|
|12:02||bobby_C has quit IRC|
|12:07||Q-FUNK has joined #ltsp|
|12:08||spectra has joined #ltsp|
|12:14||Q-FUNK has quit IRC|
|12:14||Q-FUNK has joined #ltsp|
|12:19||spectra has quit IRC|
|12:26||meduxa has quit IRC|
|12:33||Gadi has left #ltsp|
|12:36||outofrange has left #ltsp|
|12:39||BadMagic has quit IRC|
|12:40||BadMagic has joined #ltsp|
|12:53||Mauricio_ has joined #ltsp|
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)
so the make utility complaint that the kernel source is not available (requests 2.6.22-14-server)
|12:59||Mauricio__ has joined #ltsp|
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
l source is not installed (requests 2.6.22-14-server!)
|13:00||Mauricio_ has quit IRC|
|13:05||mighty-d has joined #ltsp|
|13:06||whitey_ has joined #ltsp|
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 :)
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
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?
what are they doing soo differently to save on bw?
mighty-d: we occasionally get reports of people expressing interest in ltsp5 for slackware, but little to no work towards that end
I just wouldn't think that running ALP (sunray) v.s. nfs via tcp (ltsp) would be drastically different in terms of network utilization
freaked me out a bit
vagrantc: someone yesterday was asking why LPTS on Debian depends specifically on kernel-nsf-server, instead of kernel | userspace ?
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
Q-FUNK: because nobody has demonstrated that it works with the userspace server?
Q-FUNK: and i've experienced problems trying to get it working
vagrantc, is there any docs on this? i couldnt find any on the web site??
Q-FUNK: but the most recent version is a recommends instead of a depends
vagrantc: "tarball" is http://wiki.ltsp.org/twiki/bin/view/Ltsp/Ltsp5TarballInstructions
vagrantc: people often experience timeouts with the kernel one and tend to trust the suerspace one better.
mighty-d: try that
vagrantc, i have seen thie, but it doesnt say anything about ltspfs
mighty-d: well, fix it then :P
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
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
Q-FUNK: and in the end, file a bug report if there's something broken
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...
went from the 0.99 version on debian to the 5.0.39 and all is well and smokin now
whitey_: glad to help
you were my hero for the evening :-D hah
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
a little out of date, but:
vagrantc: "integration" is http://wiki.ltsp.org/twiki/bin/view/Ltsp/IntegratingLtsp
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) ...
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
just a couple of random thoughts
maybe someone here might find them useful sometime
we use it that way for development purposes
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
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
and she even uses photoshop cs3 w/ that setup
I was thouroughly impressed
each developer at our company has edubuntu running on ... was it vmware ... and connecting to a second physical NIC.
yeah that 5% of 'special bits' that LTSP provides and use 95% of the inherent distro capabilities/p[kgs
or so I hear :-D
gotta luv highyl repeatable solutions with minimal modifications needed to redeploy
or integrate in this case
hey vagrantc do you have any random thoughts on my bandwidth perplexing/concerning issue that I discovered a bit ago posted here?
vagrantc, where should i start?
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:29||sonjag has quit IRC|
|13:29||sonjag has joined #ltsp|
|13:32||zodman has quit IRC|
|13:33||Guaraldo has quit IRC|
|13:34||Guaraldo has joined #ltsp|
|13:37||Guaraldo has quit IRC|
|13:37||Guaraldo has joined #ltsp|
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
thin clients are pentium mmx with 128 mb ram..
mighty-d: it might be a little low on RAM ... but probably fine
mighty-d: low on the server ram, that is
vagrantc: Error: "serversizing" is not a valid command.
vagrantc: "serversize" is http://wiki.ltsp.org/twiki/bin/view/Ltsp/ServerSizing
vagrantc, it is currently working and none of my users complain about speed
|13:41||Guaraldo has quit IRC|
mighty-d: switching to xubuntu or or another window manager
|13:41||Guaraldo has joined #ltsp|
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
mighty-d: i've actually found xubuntu to be much more useable than plain xfce... it's really a different thing, i'd say
mighty-d: but if kde you must, then KDE it is
mighty-d: local device support in KDE doesn't work as well...
vagrantc, what do you mean, doesnt work as well? , is it like doesnt work at all?
|13:47||Mauricio__ has quit IRC|
mighty-d: well, you may need to make a symlink on the Desktop manually to get an icon to show up on the desktop
mighty-d: or just have the users know to go to /media/USERNAME/DEVICENAME
vagrantc, this can be automated?, like we are used to in 4.2?
mighty-d: i do not know if it can be automated
haven't used KDE in years
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
that's all i know
vagrantc, does this function as a udev rule or something?
well, it uses udev on the client side
but on the server side, where the files are actually mounted, it doesn't use udev ...
you might be able to put the appropirate hooks in client-side ...
vagrantc, ok ... so your advice is to discard the slackware box, and go for a ubuntu server ?
that would be your best bet
the version in debian stable is admittedly a little outdated ...
though you can get backports of ltsp-related software pretty easily
(i mostly work on debian)
|13:52||* sutula pipes up that vagrantc has done a good job keeping etch-backports current :)|
...or was I supposed to tell your AM that :)
sutula: finally got an i386 build for sid's ltsp/ldm
sutula: my NM process is stalled ... mostly due to my reluctance to do anything but work on debian packaging...
vagrantc, how is sound doing on kde ?
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
mighty-d: can't say for sure, but the current approach just uses ALSA, and KDE surely supports ALSA
there seemed to be issues with local devs on kde
outside of the other local dev bugs
well, uses pulseaudio+alsa ... but still
mighty-d: i think debian-edu uses KDE, and uses ltsp as well, you might want to ask there about some of the issues
vagrantc, ok thanks
|13:57||Q-FUNK has quit IRC|
mighty-d: irc,debian.org #debian-edu
|13:58||makghosh has quit IRC|
vagrantc, thank you for beeing so kind...
|14:00||Guaraldo has quit IRC|
|14:07||K_O-Gnom has quit IRC|
|14:15||otavio has quit IRC|
|14:24||sonjag has quit IRC|
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?
we will all help as we can
mighty-d: i'll be busy the next couple days, but probably be more available next week
cliebow, you have helped me a lot with 4.2 deployment, and i dont know if i thanked you that time :)
vagrantc, ok... ill get to it then... :)
vagrantc: "integration" is http://wiki.ltsp.org/twiki/bin/view/Ltsp/IntegratingLtsp
mighty-d: that outlines a lot of it, though the bzr URLs are probably outdated
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?
mighty-d: you'll need to download code from: https://code.launchpad.net/~ltsp-upstream/
pleased to share..
vagrantc, how many time do you think this will *cost* ?
depends on how much slackware assumes you're installing to a hard drive
vagrantc, i meant the whole thing, getting ltsp 5.0 to work on my clients under slack with distro integration..
mighty-d: 1-100000 hours
really, i can't give you an estimate
it's a fairly simple process, but there probably are some things that will take a long time
vagrantc, lol ... well that was a good reference :) , ok should i download trunk? or is there any stable release?
mighty-d: not really a stable release yet
anyways, i've gotta go now...
ok, thanks vagrantc ill go for trunk then
oh, you'll need ldm-trunk, ltsp-trunk and ltspfs-trunk ...
mkdst you'll need later
|14:38||vagrantc has quit IRC|
|14:39||zodman has joined #ltsp|
|14:42||cyberorg has quit IRC|
|14:49||cliebow has quit IRC|
on ltsp-4.2 : kdm on the client works, i want to log in, but i've been kicking out, any id?
|15:02||otavio has joined #ltsp|
|15:04||Q-FUNK has joined #ltsp|
cliebow, what applications should i install on "Install an instance of the distro into a subdirectory on the server" ??
|15:20||mikkel has quit IRC|
|15:23||mistik1_ has joined #ltsp|
|15:23||zodman has left #ltsp|
|15:23||mistik1 has quit IRC|
|15:24||mistik1_ is now known as mistik1|
|15:26||cyberorg has joined #ltsp|
|15:26||bobby_C has joined #ltsp|
|15:33||npman has quit IRC|
|15:54||Drakeweb has joined #ltsp|
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?
check the groups of the sound devices
ls -l /dev/snd or whatever it is on ubuntu
I've got controlC0, lots of pcms, a seq and a timer
|15:59||sepski has quit IRC|
what are they set
with ls -l
|15:59||Drakeweb has quit IRC|
|16:00||Drakeweb has joined #ltsp|
apologies - My pidgin died!
please repeat anything I missed in my absence ...
what are they set to?
that's the group you need to be in for starters
owner root, group audio
yes.. audio group
you do have one
but "audio" doesn't show up in my group list
(admittedly, using GUI)
how do I add a user to the audio group?
i see audio in mine ubuntu
i don't know what problems you got :)
you can edit it manually in /etc/group by adding users to the audio group like user1,user2,user3
system -> admin - > users & groups -> group settings shows no audio group
just checked, the correct users are already in the audio group.
but no sound on my thin client
and you're using ldm?
Install LTSP supplied scripts/executables into the tree .. what does this means?
where are these scripts/executables?
on ltsp-4.2 : kdm on the client works, i want to log in, but i've been kicking out, anyone hints?
won't find much help with ltsp 4.2..
you might have to wait awhile to gt an answer unless you're lucky
Drakeweb, i havent setup sound on my clients, so i don't knowthe issues as of yet
no speakers there
i'll test it with headphones sometime
i had the same thing , but i forgot how to solve it ...
I've set up a thin client for my daughter, and I'm trying to get her to learn all about linux
but she wants/needs sound, and I just can't help at the moment.
everything else works - remote printing, file sharing, internet etc.
just no sound.
|16:30||jammcq has quit IRC|
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
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
why would you need a vpn in the chroot ?
everything is supposed to go through SSH no ?
also what about a web mgmt interface (tomcat/etc) to control client devices like disabling usb or audio devices on a per client basis
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?
just trying to figure out how to do WAN deployments of this technology...site to site vpn?
|16:40||gonzaloaf has quit IRC|
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)
so your essentially sayting that WAN deployments/integration should not be too difficult?
|16:43||bobby_C has quit IRC|
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
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:56||staffencasa has quit IRC|
awesome thanks much!
btw what's NBD?
I am guessing network boot something (daemon)
network block device
|17:04||mighty-d has quit IRC|
is that what ltspfs uses? that and a combo of fuse on teh client?
ltspfs AFAIK is an addon to sshfs (using fuse)
nbd is what's used instead of NFS since LTSP5
well the client bits/env are run from nfs still thourhg right from teh chrooted build env?
and that's what teh /opt/ltsp nfs share export is there for?>
very cool btw that ltspfs is sshfs in a sense
that's with the old LTSP, the new one uses a squashfs image of /opt/ltsp/i386 exported using nbd
when ya say old how old?
I am using 5.0.39 LTSP5 ion debian etch
and i see metric tons of nfs (tcp) traff when i am running my sessions
am i missing something very obvious here
the move to nbd was done with gutsy (for Ubuntu)
maybe Debian hasn't done the move yet
hmm I am using backports
argh, vagrantc isn't around :)
I would think that is teh newest stuff for ltsp
I hear that
feisty = 5.0.7, gutsy = 5.0.39 and hardy (devel release) = 5.0.39+20071127 (snapshot)
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
well I am running the 5.0.39 release under debian etch via backports as suggested by vagrantc a few days ago
but I doubt Ubuntu 5.0.39 = Debian 5.0.39
you should ask him how to have nbd working on Debian
as it's easier to route a single tcp port than the UDP stuff of NFS :)
I hear ya
|17:15||Top|OLPC has joined #ltsp|
|17:38||Egyptian[Home] has quit IRC|
|17:47||Drakeweb has quit IRC|
|17:52||Top|OLPC has quit IRC|
|18:11||MacGruber has joined #ltsp|
Hi, you guys might be able to help me out here...
One of my clients boots, the other doesn't.
Jan 4 16:05:14 konan dhcpd: DHCPDISCOVER from 00:1b:eb:02:00:95 via eth0
Jan 4 16:05:15 konan dhcpd: DHCPOFFER on 10.0.5.249 to 00:1b:eb:02:00:95 via eth0
Jan 4 16:07:48 konan dhcpd: DHCPDISCOVER from 00:1b:eb:02:00:95 via eth0
Jan 4 16:07:49 konan dhcpd: DHCPOFFER on 10.0.5.249 to 00:1b:eb:02:00:95 via eth0
...but the dhcp information is ignored!
16:07:57.537361 IP 10.0.5.3.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length: 300
16:07:57.969295 arp who-has 10.0.5.249 tell 10.0.5.3
The thin client that is not booting says at startup:
"Intel UNDI, PXE-2.0 (build 078)"
The thin client that _does_ boot says at startup:
Intel UNDI PXE 2.1 (Build...)
|18:22||cliebow has joined #ltsp|
|19:04||MacGruber has quit IRC|
|19:46||allobjects has joined #ltsp|
|19:52||otavio has quit IRC|
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
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)
allobjects: I hit that and decided it wasn't really worth pursuing
|20:17||cliebow has left #ltsp|
|20:34||whitey_ has quit IRC|
|20:59||allobjects has quit IRC|
so i'm trying to get k12ltsp6 going, and i have the gray screen of death? Anyone know how to turn gdm on?
oh heh, i just typed 'gdm'
what is k12ltsp even based on
i don't know anything about it
is it based on ltsp 4?
or ltsp 5
|21:16||* johnny guesses 4..|
you'll only find on and off help with ltsp 4.x here
most of the folks hanging out in here use an ltsp5 based setup
the ones who chat at least
I thought this was ltsp5
if it uses gdm, then it's prolly not
it should use ldm
and it should also use it by default
oh its 4.2
yeah.. afaik fedora doesn't have a finished ltsp 5 setup
only debian/ubuntu do
it is being worked on tho
you're prolly gonna have to stick with the k12ltsp resources
if they have an irc channel
unless you get lucky
and run into a 4.x person here
seems to be working now
eventually i'll go with edubuntu, couldn't get it going in gutsy
i'm using it with gutsy atm
what are your thin clients like
|21:28||allobjects has joined #ltsp|
sutula: sorry I was away
sutula: what assumptions are you making about my network ?
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
no guarantees on the speed tho
also the existing machies are already runnning Ubuntu wirelessly with no problems
but if you actually boot a kernel locally
then you're not using ltsp anymore
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
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 ?
you could use nx
and run them remotely
|21:50||allobject1 has joined #ltsp|
sorry lost my connection, not sure which of my questions got through or lost in the ether
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:57||allobjects has quit IRC|
|22:18||allobject1 has quit IRC|
|22:21||muh2000_ has joined #ltsp|
when i try to login it just gets back to the logon screen :(
kdm: segfault at 0000000000000000 rip 00002b792db6f040 rsp 00007fff7e0427f8 error 4
|22:26||sid has left #ltsp|
is there a way to change the login screen? instead of kdm -> xdm?
|22:56||F-GT has quit IRC|
|22:58||F-GT has joined #ltsp|
|23:05||tux_440volt has joined #ltsp|
|23:11||rjune_ has quit IRC|
|23:14||vagrantc has joined #ltsp|
|23:29||muh2000_ has quit IRC|
|23:29||muh2000_ has joined #ltsp|
|23:45||makghosh has joined #ltsp|
hmmm it is not kdm. gdm produces the same error.