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


Channel log from 6 December 2009   (all times are UTC)

00:07alexqwesa has quit IRC
00:13alexqwesa has joined #ltsp
00:55cyberorg_fossin has quit IRC
02:38FGXR6 has joined #ltsp
02:38F-GT has quit IRC
02:56FGXR6 has quit IRC
02:57FGXR6 has joined #ltsp
03:24ogra has quit IRC
03:25ogra has joined #ltsp
03:43Egyptian[Home] has quit IRC
03:59Egyptian[Home] has joined #ltsp
04:08FGXR6 has quit IRC
05:36antgel has joined #ltsp
05:37mikkel has joined #ltsp
06:19F-GT has joined #ltsp
06:50cyberorg_fossin has joined #ltsp
07:02pmatulis has joined #ltsp
07:45cyberorg_fossin has quit IRC
07:50cyberorg_fossin has joined #ltsp
08:17cyberorg_ has joined #ltsp
08:19cyberorg_fossin has quit IRC
08:19mikkel has quit IRC
08:19Egyptian[Home] has quit IRC
08:19alincoln has quit IRC
08:19squarepeg has quit IRC
08:19kusznir__ has quit IRC
08:19svenl has quit IRC
08:19leio has quit IRC
08:19chrisinajar has quit IRC
08:19artista_frustrad has quit IRC
08:19cliebow_ has quit IRC
08:19Appiah has quit IRC
08:19monteslu_ has quit IRC
08:19sepski has quit IRC
08:19lejo has quit IRC
08:19panthera has quit IRC
08:19korcan has quit IRC
08:19tarzeau has quit IRC
08:19Patina has quit IRC
08:19pmatulis has quit IRC
08:19ogra has quit IRC
08:19alexqwesa has quit IRC
08:19yanu has quit IRC
08:19Ahmuck-Sr has quit IRC
08:19Ahmuck has quit IRC
08:19Selveste1 has quit IRC
08:19spectra has quit IRC
08:19Lumiere_ has quit IRC
08:19_UsUrPeR_ has quit IRC
08:19stgraber has quit IRC
08:19moldy has quit IRC
08:19vmlintu has quit IRC
08:19vlt has quit IRC
08:19F-GT has quit IRC
08:19Sarten-X has quit IRC
08:19evilx__ has quit IRC
08:19staffencasa has quit IRC
08:19mushroomblue has quit IRC
08:19Hyperbyte has quit IRC
08:19foxbuntu has quit IRC
08:19primeministerp has quit IRC
08:19jbrett has quit IRC
08:21barbosa has quit IRC
08:21chrisinajar has joined #ltsp
08:21artista_frustrad has joined #ltsp
08:21cliebow_ has joined #ltsp
08:21Appiah has joined #ltsp
08:21monteslu_ has joined #ltsp
08:21lejo has joined #ltsp
08:21sepski has joined #ltsp
08:22pmatulis has joined #ltsp
08:22F-GT has joined #ltsp
08:22mikkel has joined #ltsp
08:22Egyptian[Home] has joined #ltsp
08:22ogra has joined #ltsp
08:22alexqwesa has joined #ltsp
08:22yanu has joined #ltsp
08:22Ahmuck-Sr has joined #ltsp
08:22alincoln has joined #ltsp
08:22squarepeg has joined #ltsp
08:22kusznir__ has joined #ltsp
08:22Sarten-X has joined #ltsp
08:22evilx__ has joined #ltsp
08:22Ahmuck has joined #ltsp
08:22Selveste1 has joined #ltsp
08:22spectra has joined #ltsp
08:22Lumiere_ has joined #ltsp
08:22staffencasa has joined #ltsp
08:22mushroomblue has joined #ltsp
08:22_UsUrPeR_ has joined #ltsp
08:22vlt has joined #ltsp
08:22jbrett has joined #ltsp
08:22Patina has joined #ltsp
08:22tarzeau has joined #ltsp
08:22stgraber has joined #ltsp
08:22primeministerp has joined #ltsp
08:22foxbuntu has joined #ltsp
08:22Hyperbyte has joined #ltsp
08:22korcan has joined #ltsp
08:22panthera has joined #ltsp
08:22vmlintu has joined #ltsp
08:22moldy has joined #ltsp
08:22leio has joined #ltsp
08:22svenl has joined #ltsp
08:23cyberorg_ is now known as Guest90064
08:31barbosa has joined #ltsp
08:50
<sbalneav>
Morning all
08:58rjune has joined #ltsp
09:25Guest90064 has quit IRC
10:00Kicer86 has joined #ltsp
10:06dro has joined #ltsp
10:06
<dro>
I'm setting up my first 2008r2 server, I ran dcpromo and everything went ok, but after a reboot I can't login!
10:06
says bad username/password
10:13
oops wrong room
10:13
LOL
10:13dro has quit IRC
10:27alkisg has joined #ltsp
12:25alkisg has quit IRC
12:25alkisg has joined #ltsp
12:35ehrenpr has joined #ltsp
12:35
<ehrenpr>
anyone have an opinion, wether I should opt for a faster rocessor or for more cores. in my kiwi-ltsp server?
12:36
processor
12:36Ahmuck-Sr has quit IRC
12:38alexqwesa has quit IRC
12:38alexqwesa has joined #ltsp
12:39
<johnny>
more ram
12:39
if you're not using all the ram you have that is..
12:39
otherwise.. more core
12:41
<ehrenpr>
My ram isnt being affected as much, but my amd 2.0 athalon duals, are screaming. I am thinking about a quad 3.0.
12:42
is that to much!!
12:50dro has joined #ltsp
12:57pem725 has joined #ltsp
12:58
<pem725>
can someone help me setup virtualbox for my thin clients? I want my thin clients to be able to boot Windows when necessary. Any help would be greatly appreciated.
12:59
specifically, I have virtualbox installed but I am not sure how to get the kernel modules to load for the thin client kernels.
13:07
<alkisg>
pem725: vbox clients or vbox server?
13:09
<johnny>
you really don't wanna put vbox in the chroot
13:10
it's gonna be suck
13:10
<pem725>
good question. I am not sure. The vbox client complains that the kernel driver is not loaded.
13:10
so I am not sure.
13:10
<johnny>
if you wanna boot windows.. put a hard drive in there
13:10
<alkisg>
pem725: I didn't understand what you want to do, can you elaborate?
13:10
<johnny>
or.. use rdesktop to talk to windows server via remote desktop
13:10
<pem725>
alkisg
13:11
ok, I have two thin clients that need to use windows but only on rare occasions
13:11
<johnny>
why not install vbox on the server?
13:11
<pem725>
so I wanted to allow them to startup a vbox instance.
13:11
I have vbox on the server and it runs well.
13:11
<johnny>
so use that..
13:11
<pem725>
can my thin clients access it?
13:11
how?
13:11
<johnny>
same way?
13:11
<pem725>
sorry for being so obtuse.
13:11
<alkisg>
pem725: so you need rdesktop on the client, and windows vbox on the server, right?
13:11
<johnny>
it should appear in their menu
13:11
<pem725>
ah.
13:12
yes, it appears in their menu.
13:12
<johnny>
first see if that is fast enough before trying anything else that might be difficult
13:12
<pem725>
alkisg, yes, I think that sounds right.
13:13
I guess I have vbox setup as a user on the server.
13:13
<johnny>
the open version of virtualbox doesn't support rdesktop service does it?
13:13
<alkisg>
ok, you can do it as johnny said, and if the performance doesn't suit you, you can try to run a local rdesktop from the clients
13:13
<pem725>
ok
13:13
<alkisg>
I think it does
13:14
<pem725>
I have vbox setup on the server but one user has an image setup in his directory.
13:14
<johnny>
pem725, if you run vbox headless with rdesktop.. you can login somewhat more directly (but not really ) and tell your clients to rdesktop to it
13:14
altho you probably need the appropriate number of licenses for that..
13:14
<pem725>
when I try to run it using that user's profile on the thin client, the vbox program tells me that the kernel module is not loaded.
13:14
<alkisg>
Put the user in the vboxusers group
13:14
<pem725>
licenses are not an issue.
13:14
ok
13:15
I will try those suggestions. Thanks for your quick responses.
13:20
<johnny>
ah yes.. that is probably the key
13:20
putting the user in the group :)
13:20
hehe
13:45bodkin has joined #ltsp
13:48bodkin has left #ltsp
13:51bobby_C has joined #ltsp
13:51bobby_C has quit IRC
14:10bodkin has joined #ltsp
14:18Kicer86 has quit IRC
14:28ehrenpr has quit IRC
14:31bodkin has left #ltsp
14:42pmatulis has quit IRC
15:13dro has quit IRC
15:19stevesmith1983 has joined #ltsp
15:32mikkel has quit IRC
16:05Ahmuck has quit IRC
16:08Ahmuck has joined #ltsp
16:13vagrantc has joined #ltsp
16:15hersonls has joined #ltsp
16:18alkisg has quit IRC
16:37pmatulis has joined #ltsp
16:53hersonls has quit IRC
16:55hersonls has joined #ltsp
17:33Sarten-X has quit IRC
17:56map7 has joined #ltsp
17:57squarepeg has quit IRC
18:19otavio has quit IRC
18:21otavio has joined #ltsp
18:24stevesmith1983 has quit IRC
18:25damo221 has joined #ltsp
18:26
<damo221>
how do i read mouse events from the local thin client?
18:26
/dev/input is on the server right/
18:26
?
18:27
<vagrantc>
typically, yes.
18:28
you'll have to get them from the X Display somehow...
18:28
damo221: what are you trying to do?
18:29
<damo221>
vagrantc: i want to write a script that reads mouse events and sends them to some sort of audio player so i can set up a transcription tool
18:29
but my machine is an ltsp client.. i got audio to work using pulseaudio
18:30
<vagrantc>
damo221: you'll have to write code that reads it from the X display
18:30
<damo221>
okay....
18:31
can i do it with bash? or i need something like python
18:32
i know that bash "read" can read mouse clicks
18:32
<vagrantc>
it would probably be a bad idea to try in bash.
18:33
<damo221>
can php do it? its the only other language i really know
18:33
lo
18:33
lol
18:34
<vagrantc>
you just need a language with a decent interface to X
18:34
<damo221>
ok
18:37
cant i just read some sort of device node
18:37hersonls has quit IRC
18:37
<damo221>
and parse it
18:38
<vagrantc>
damo221: for the third time, you need to use something that gets it from the X display.
18:38
<damo221>
okay
18:39hersonls has joined #ltsp
18:40artista_frustrad has quit IRC
18:45
<pmatulis>
is setting up multiple ltsp images documented anywhere? i'm using ubuntu 9.04
18:50ehrenpr has joined #ltsp
18:53damo221 has quit IRC
19:27try2free has joined #ltsp
19:41otavio has quit IRC
19:54ehrenpr has quit IRC
20:04
<sbalneav>
vagrantc: You were interested in cnetworkmanager?
20:05
vagrantc: check my ppa. I packaged it.
20:05
I also wrote a manpage for it.
20:09
<pmatulis>
sbalneav: what is cnetworkmanager?
20:11
<sbalneav>
command line interface to network manager
20:11try2free has left #ltsp
20:11
<sbalneav>
you can control network manager without having to use one of the gui apps
20:12
sbalneav@phobos:~$ cnetworkmanager -s
20:12
Active | Name | Type
20:12
-------+-----------------+--------------- | Ifupdown (eth0) | 802-3-ethernet
20:12
* | Auto eth1 | 802-3-ethernet
20:12
So, if you run a low-end laptop, that's running, say, icewm, but you still want the convenience of NM for wireless
20:13
you can control it with cnetworkmanager
20:14
<pmatulis>
sbalneav: sweet
20:14
sbalneav: has it been around for a while?
20:15
<sbalneav>
Not too long
20:15
Anyway there wasn't a debian or ubuntu package for it, so I packaged it.
20:17
brb
20:24sl00 has joined #ltsp
20:25
<sl00>
Hi. I have installed Fedora 12 and then installed the LTSP package. I have been following the guides but it seems the DHCP is not running or something? I have tried 'service dhcp start' but that fails. What is wrong?
21:10rjune has quit IRC
21:12
<sl00>
Now the thin client boots up and I get a login screen but when I try to login it just says "verifying.." for a while then the screen flicker with some console text (cannot read it) and then I am back at the login screen for another attempt. Why can I not login and where can I find logs for these failures?
21:13
<johnny>
do you have sshd running?
21:13
do you have an account on the server?
21:14
<sl00>
'service sshd status' shows it is running and yes I have tried with two accounts that exist on the server.
21:14
<vagrantc>
sbalneav: cool!
21:17
<johnny>
try sshing to one of em..
21:18
the logs are on the chroot, so you could add SCREEN_02=shell
21:18
to your lts.conf and drop into to look at /var/log/ldm.log
21:21
<sl00>
johnny: SSH to the thin client?
21:24
If I just type 'ssh 172.31.100.100' in a terminal at the server then it says 'connection refused'
21:26
<pmatulis>
for multiple client images, after creating them and assigning a different NBD port to each in inetd.conf do i just need to create corresponding pxelinux.cfg files and configure DHCP appropriately?
21:28
<vagrantc>
or configure pxelinux.cfg to have a menu to select which one to use
21:31
<pmatulis>
vagrantc: that sounds good
21:32
<vagrantc>
depends on if you'd prefer specific thin clients to use a different default, or the users choose
21:32
<pmatulis>
vagrantc: right
21:33
<sbalneav>
Back
21:44Egyptian[Home] has quit IRC
21:44vicd has joined #ltsp
21:49
<sl00>
Hm... my /opt/ltsp/i386/etc/lts.conf is empty on the server. Is that correct?
21:49
I just ran ltsp-build-client.
21:50
<vagrantc>
normally, you only need lts.conf entries if the defaults don't work
21:50
and some distros now place it in /var/lib/tftpboot/ltsp/i386/lts.conf now
21:51
<sl00>
Okey.. I will check "/var/lib/tftpboot/ltsp/i386/lts.conf" then.
21:52
<johnny>
it might be empty
21:52
or not there
21:52
in which case you need to be
21:52
need to put*
21:52
[default]
21:53
before
21:53
no.. ssh to a user to make sure it works
21:53
from another computer
21:53
as ldm just does ssh
21:54
<sl00>
I added SCREEN_02=shell now under [default] in "/var/lib/tftpboot/ltsp/i386/lts.conf" but nothing happends when I press ALT+F2. SCREEN_01 is set to ldm.
21:55
johnny: I have no other computer right now. Running the server on a netbook (just to get this working) and the client is connected directly to its wired ethernet port.
21:56
<johnny>
you have to reboot it
21:57
<sl00>
Yes I did... but hm... now the login worked!!
21:57
<johnny>
ah.. well good
21:57
there ya go
21:57
<sl00>
So I guess it works now because I ran ltsp-build.client again... but I do not really understand why it works now and now before tho :(
21:57
<johnny>
maybe you mistyped the password
21:57
or maybe you had changed the ip of your server
21:58
in which case you have to run ltsp-update-sshkeys, which is run after ltsp-build-client
21:58
but can be run manually if your ip changes
21:58
vagrantc, how come we can't detect that the server ip changed and print that in ldm?
21:58
and tell people to run ltsp-update-sshkeys on their server
21:59
<sl00>
johnny: Hmm okey.
21:59
<vagrantc>
johnny: how do you distinguish between a hostile server and one where the keys have changed?
22:00
<johnny>
we can mention that either the server ip changed, or something bad happened
22:00
and say to notify the admin
22:00
i didn't suggest that we take the new key or anything
22:00
<vagrantc>
at any rate, one of the breakages with the switch to NBD was that you have to rebuild the image every time you change ip addresses because of that
22:00
<johnny>
only notify
22:00
since when? i've never had t do that on ubuntu?
22:00
<sl00>
johnny: When and why do I have to run ltsp-build-client after this?
22:00
<johnny>
you won't
22:00
<sl00>
(if you know what I mean)
22:00
<johnny>
just run ltsp-update-sshkeys
22:00
next time
22:00
if your ip changes
22:00
server ip*
22:01
<vagrantc>
johnny: how do you propegate the new keys to the NBD image?
22:01Egyptian[Home] has joined #ltsp
22:01
<vagrantc>
er, key/ip/hostname matching
22:01
<johnny>
oh.. you're right.. :(
22:01
<sl00>
johnny: Okey. So I should not need to run ltsp-build-client ever again?
22:01
<johnny>
duh :(
22:01
<vagrantc>
johnny: you probably don't change the server ip very often.
22:01
<johnny>
you have to urn ltsp-update-image next time..
22:01
sl00, only if you rebuild the image..
22:01
afrer deleting the old one
22:02
if your server ip changes, just run ltsp-update-image then
22:02
unless fedoar doesn't use nbd.. i can't recall
22:02
i know gentoo doesn't
22:02
as we can't control our server kernels
22:02
<sl00>
AFAIK it uses NFS right now.
22:02
<johnny>
ah.. then just ltsp-update-sshkeys
22:03
<sl00>
Okey. I do not think the IP will ever change. What I wonder is what updates to the server requires me to update the image really?
22:04
<johnny>
there is no image
22:04
if you use nfs
22:04
but if you did use nbd.. like ubuntu uses by default.. then you would
22:05
every change to the image (anything affecting client behaviour like ssh keys change, or local apps are installed) would require it then
22:05
<sl00>
johnny: Okey. So if I install say OpenOffice on the server now the client will get it right away?
22:05
<johnny>
yes
22:05
<sl00>
Cool :)
22:05
<johnny>
anyything on the server.. runs on the server..
22:05
so no client mods necessary..
22:06
<sl00>
johnny: But if I were to run NBD I have to ltsp-update-image?
22:06
<johnny>
yes..
22:06
<sl00>
How much faster/better is NBD over NFS?
22:07
<johnny>
fast enough
22:07
never benched.. but i could tell the difference
22:07
<sl00>
So NBD is recommended then I guess.
22:08
<johnny>
it is default on ubuntu..
22:08
not on fedora.. i'm not sure why
22:08
and definitely not on debian
22:08
and not on gentoo.. altho for other reasons..
22:09
/me runs to the store
22:09
brb
22:09
<sl00>
Okey..thanks for the help.
22:16
Seems one of the reasons I could not login with one of the accounts was because the password contains the " character.
22:16
<vagrantc>
if you installed openoffice on the server, you normally wouldn't have to run ltsp-update-image, unless you were using LOCAL_APPS or LTSP_FATCLIENT
22:17
<sl00>
vagrantc: AH I see.
22:18
<vagrantc>
nearly everything happens on the server in a traditional thin client environment: user creation/deletion/managemant, software installs/removals
22:27yanu has quit IRC
22:29yanu has joined #ltsp
22:33
<pmatulis>
vagrantc: re multiple images, i now have separate chroots for TFTP (ltsp and ltsp2) but in the pxelinux.cfg/default i'm not sure how to specify the port to use (i have 2000 and 2001 in inetd.conf)
22:34
(each TFTP chroot has it's own default file)
22:43
<vagrantc>
pmatulis: nbdroot=ip.address.of.server:port
22:44
maybe nbdport too
22:44
<pmatulis>
this is in the default file?
22:45
<vagrantc>
yeah
22:47
<sl00>
vagrantc: Is it possible to get the fedora login screen, the one I get if I login locally on the server, instead of this k12linux one (ldm)?
22:48
<johnny>
sl00, it's an ldm theme
22:48
we can't use gdm themes..
22:48
sl00, try searching the internet to see if somebody has created another ldm theme
22:48
we don't actually have an ldm theme repository...
22:48
<vagrantc>
and i hear recent versions of gdm have dropped support for logging in over the network...
22:48
<sl00>
Okey.
22:49
<johnny>
vagrantc, that has little to do with using their themes :)
22:49
<vagrantc>
johnny: well, it would be trivial to use GDM's theme if you were logging in via XDMCP using GDM
22:49
<johnny>
sl00, or you would work out how to modify that one
22:49
vagrantc, sure.. but we don't really recommend that anyways..
22:50
<sl00>
johnny: Will do!
22:51
Found /opt/ltsp/i386/usr/share/ldm/themes so far... I will play around alittle.
22:52
<johnny>
sl00, there are docs for .gtkrc
22:52
all over the internet i bet.. so you should be able to figure out.. it's not quite css.. but it does about the same thing..
22:52
<sl00>
Okey
23:01pmatulis has quit IRC
23:04alkisg has joined #ltsp
23:31Egyptian[Home] has quit IRC
23:36Egyptian[Home] has joined #ltsp