[06:44] <reever> hi
[08:47] <neil_d> I am going to be setting up a LTSP system for a company soon :)   What I am wondering is if instead of using Gnome would it be better to use XFce for the desktop ?
[08:50] <ogra> neil_d, thats totally up to you :)
[08:50] <ogra> it will save you small amounts of ram
[08:51] <ogra> (usually we say you need 128M on the server per running session, xfc would likely lower that to something like 90M ...)
[09:17] <neil_d> not enough to make any difference.  thanks for the response.
[09:41] <zoon> Hi guys, I'm stuck with edubuntu 8.04. /etc/ltsp/dhcpd.conf is set to give dhcp from a certain range, and when I start a thin client, it gets the same IP as my server ! Duh ?
[09:41] <zoon> Karma points for those who have an idea...
[09:46] <neil_d> zoon: could there be two dhcp server (e.g. a broadband modem)
[09:46] <zoon> yes indeed, but they don't have the same range
[09:46] <zoon> and my server has a static IP
[09:47] <zoon> the thin client gets the same (the static one)
[09:47]  * neil_d oh!
[09:48] <zoon> any idea ?
[09:48] <vtkix> hello
[09:49] <zoon> hello
[09:49] <vtkix> Im trying to get a local bluetooth usb dongle to work on a ltsp client
[09:49] <vtkix> is this possible?
[09:49] <vtkix> local usb memory stick works ok
[09:49] <zoon> I've no idea, I'm trying to get an dhcp problem fixed...
[09:53] <neil_d> vtkix: you might have to make sure the ltsp image has the driver installed in it (not user me ltsp newbie)
[09:53] <vtkix> ok, seems quite silent here
[09:53] <vtkix> Well even if I don't have the driver, the device should show up when doing lsusb, right?
[09:54] <vtkix> I tried googling but can't find any good info on it
[09:54] <vtkix> same goes for local webcam support
[09:54] <vtkix> that sould be possible, I just can't find any good directions
[09:55] <neil_d> vtkix: tried doing the lsusb on the actual terminal in a 'screen' terminal.
[09:55] <vtkix> Ill try!
[09:55] <vtkix> same, shows no usb devices
[09:56] <vtkix> mmm it also doesnt show the usb memory stick that does actually work
[09:56] <vtkix> what I see with lsusb are the devices on the server
[09:57] <vtkix> You maybe know how to show the client usb devices?
[09:58] <neil_d> I have a "SCREEN_02 = shell" in lts.conf and then I can access this via <ctrl><alt><F2> on the client to get a local shell (not a shell on the server)
[09:59] <vtkix> what are the default credentials?
[09:59] <ogra> zoon, disables the dhcpd in your router
[09:59] <neil_d> credentials?
[09:59] <vtkix> login / password for the shell you mentioned
[10:00] <ogra> you are logged in as root if you use the SCREEN_02=shell parameter
[10:00] <neil_d> its a root shell, auto loged in.
[10:00] <vtkix> ok thanks, rebooting test client now :)
[10:01] <zoon> my server is set to 'authoritative', and on the thin client login screen, I can see on the bottom right that the ip is good ! but when I log in and do and ifconfig eth0, it's the server IP...
[10:01] <ogra> zoon, if you run two dhcp servers in the same network and one is used for netbooting you cant guarantee the one having the netboot info answers first
[10:02] <neil_d> zoon: thats because the ifconfig is being run on the server, the client is just a remote keyboard and screen for the server.
[10:02] <zoon> ok so it's normal ?
[10:02] <neil_d> yes! same happens here.
[10:02] <vtkix> ok, now lspci shows the device
[10:03] <neil_d> vtkix: lspci?   don't you mean lsusb ?
[10:03] <ogra> zoon, the desktop session runs *on the server* imagine the client as additional keyboard/mouse/monitor/etc, not as a separate machine
[10:03] <vtkix> sry
[10:03] <vtkix> y
[10:03] <vtkix> i mean lsusb
[10:04] <ogra> zoon, so if you are logged in you will only see the server HW
[10:04] <ogra> (is in turn only seen the servers NIC and its IP)
[10:04] <ogra> *see
[10:05] <zoon> ... ok... so the IPs are just there for remote control ?
[10:06] <ogra> the IPs are for the actual machines on a low level
[10:07] <zoon> okidoki... Was it different on gutsy ?
[10:07] <ogra> the sound, usbdisk and display forwarding use them on the lower layer
[10:07] <zoon> it seems to me that before I could see thin clients IPs when running ifconfig eth0
[10:08] <ogra> no, hardy is just an improved (with lot of bugfixes and small improvements) gutsy ltsp .... we kept the changes at a minimal level for the LTS release
[10:08] <zoon> ogra: ok many thanks for your help
[10:08] <ogra> you culd never see the client IP from a desktop session
[10:09] <neil_d> zoon: no, only if run used a ifconfig in a shell on the client (see above)
[10:09] <ogra> (you cn if you use the SCREEN setting and do it in the rootshell on tty2 on the client though)
[10:09] <zoon> ok guys, I'm daring another question then :)
[10:09] <ogra> *can
[10:09] <ogra> and its shown on the bottom right in the login manager on the client
[10:10] <zoon> How do I 'lock' a thin client (remove terminal, menu items and stuff) without changing the main user layout on the server ?
[10:10] <vtkix> ok orga, so I should recompile the kernel in chroot with the correct bluetooth driver?
[10:10] <ogra> vtkix, i dont know a way how to forward bluetooth between client and server
[10:10] <neil_d> zoon:  have a seperate login for when using the client
[10:11] <zoon> so if I have 30 students, I need to login on each one of them and change the settings ?
[10:11] <vtkix> ok, but you know how to get this to work for a local webcam?
[10:11] <ogra> vtkix, to get it working on the client you first need to install the bluetooth stack of apps, we dont have that by default in the client environment
[10:11] <vtkix> or do you know where I could search for this?
[10:11] <vtkix> ok, ill do
[10:12] <zoon> I thought I could have one generic image for all ? And I'm wondering how to modify this particular image...
[10:12] <ogra> then you need to find a protocol to froward the output of these devices somehow ... there is no code or anything supporting that, if you implement it, feel free to send me a patch :)
[10:13] <vtkix> ok, too bad, I only can code some perl and php :)
[10:14] <neil_d> zoon: if by image you mean login  (not the image sent to the clients for booting) you can as far as I know.
[10:14] <ogra> zoon, the image is the same for all clients but i guess you want settings in the desktop which is sitting on the server and works per user
[10:14] <ogra> vtkix, python isnt to hard if you have that background though :)
[10:14]  * neil_d likes python
[10:14] <vtkix> Ok orga, so for example a bluetooth keyboard or mouse is currently not supported?
[10:15] <vtkix> What im trying to do is using the wiimote to control a ltsp client. On default hardy it works perfectly
[10:16] <ogra> vtkix, well, thats different since they are handled by the local setup on the client, there is nothing to forward to the session
[10:16] <zoon> ogra: huh I don't get it, what I mean is on the server, I have a user, say 'zoon' with access to a terminal and all the menus items. And I want the student not to be able to see some menu items for example.
[10:16] <zoon> ogra: without modifying the 'zoon' user
[10:16] <zoon> ogra: but the common kernel boot image or whatever
[10:17] <vtkix> ok, so if I setup the local bluetooth and wiimote driver, that should work?
[10:17] <ogra> vtkix, keyboard and mice apply to X on the client ... but you want the output of your webcam in the session on the server so you need something that forwards this stream and something on the server side to connect to
[10:17] <neil_d> zoon: have another user defined says 'terminal' and change the menus etc. for this user, then only use that user (i.e. teminal) on the clients.
[10:17] <vtkix> First I want the wiimote to work, webcam is for later :)
[10:17] <ogra> zoon, you have to configure the desktop settings on the server then
[10:18] <ogra> zoon, https://wiki.ubuntu.com/kioskGnome might be helpful
[10:18] <vtkix> I saw some succes story on ubuntu, they used amsn as a local application to get the webcam to work
[10:18] <ogra> sabayon and pessulus might be helpful apps as well
[10:18] <ogra> and i'D suggest a look at the gnome administrator guide which has plenty of helpful tips how to lock down the desktops
[10:19] <zoon> ogra: So I'll lock myself out and won't get access to a terminal ? I'll check your links
[10:20] <vtkix> vtkix: ok, so if I setup the local bluetooth and wiimote driver, that should work?
[10:21]  * neil_d thinks it will
[10:21] <vtkix> that would be great
[10:21] <vtkix> going to try it :)
[10:25] <vtkix> thanks for your help guys :)
[10:28] <vtkix> ogra?
[11:02] <vtkix> hello?
[11:43] <Mary_ux> hi every1
[11:46] <vtkix> hi
[11:46] <Mary_ux> just a qst
[11:46] <Mary_ux> i am using ltsp
[11:47] <Mary_ux> I want to create an user who can only login in a specific machine
[11:47] <Mary_ux> you know how can i doit?
[11:48] <vtkix> you could use the autologin feature, then you can specify what machine uses what username?
[11:48] <Mary_ux> how can i specify this?
[11:48] <vtkix> in lts.conf
[11:48] <vtkix> you put something like this:
[11:49] <vtkix> [00:0C:29:5B:72:42]
[11:49] <vtkix> LDM_AUTOLOGIN=true
[11:49] <vtkix> LDM_USERNAME=computer
[11:49] <vtkix> LDM_PASSWORD=computer
[11:49] <Mary_ux> but this doesnt restrict others to login in the machine
[11:50] <vtkix> it does
[11:50] <vtkix> you won't get a login screen
[11:50] <vtkix> on that machine
[11:50] <Mary_ux> but i want askin for that
[11:51] <vtkix> then I dunno, sorry, also new user here ;)
[11:51] <Mary_ux> ok
[11:51] <Mary_ux> thanks anyway
[11:51] <Mary_ux> and dot answer qst that u dont know pls
[11:51] <Mary_ux> u confuse plp even more
[11:51] <vtkix> Have you looked here: https://help.ubuntu.com/community/UbuntuLTSP/
[11:52] <Mary_ux> yep
[11:52] <Mary_ux> have you??
[11:52] <vtkix> lol
[11:52] <Mary_ux> :)
[11:52] <vtkix> Just tried to help you out
[11:53] <Mary_ux> k thanks
[11:54] <Mary_ux> any1 here knows...
[11:54] <Mary_ux> how can I create a user who only can login in a specific machine?
[11:54] <Mary_ux> I am using d LTSP
[11:57] <Mary_ux> any1 out there??
[12:01] <Mary_ux> ...
[13:29] <mary_lix> hi every1
[13:29] <mary_lix> how is it goin?
[13:29] <mary_lix> ﻿How can I lock the "edit menu" option in gnome to an user??
[17:47] <stgraber> ogra: I have an iTalc package with that ICA crashed fixed (well, workarounded). Do you think we should upload it or wait for the final 1.0.9 ?
[17:47] <stgraber> as I said, it's only a workaround and we hope to get a fix from x11vnc upstream.
[17:47] <ogra> well, given that ltsp likely wont work yet in intrepid i dont think its urgent
[17:48] <stgraber> ok, I don't like uploading pre-versions anyway :)
[17:48] <ogra> but if oyu feel better havig a fixed version in, tell me and i'll upload :)
[17:48] <ogra> s/fixed version/version with a workaround/
[17:49] <stgraber> I'll probably blog about it, giving a link to the testing packages (I can't use the PPA as it doesn't give you the -dbgsym) for people interested in getting a fixed version ASAP
[17:49] <stgraber> and asking for more testers, AFAIK it's the only iTalc bug that was reported
[17:49] <stgraber> so I'd like people to make sure we don't have another VNC bug before 1.0.9 is released
[17:50] <ogra> well, then lets upload, thats what devel releases are for
[17:50] <ogra> if you need feedback, alpha1 might be a good opportunity
[17:51] <ogra> (if alpha1 ever happens :) )
[17:52] <stgraber> http://www.stgraber.org/download/ubuntu/italc/
[17:52] <stgraber> the changelog is minimal, ask me if you want something better
[18:10] <ogra> uploaded (in case yu didnt notice the accepted mail)
[21:25] <stgraber> ogra: We have an upstream fix for the x11vnc issue !!!
[21:25] <stgraber> that was fast, only 4 hours to get one :)