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


Channel log from 15 February 2008   (all times are UTC)

00:03Vasanth has joined #ltsp
00:03makghosh has quit IRC
00:13
<Vasanth>
hi everyone.. i'm new to ltsp..i have a prob with my ltsp installation.. i've installed edubuntu 7.10..the client boots up properly but when trying to login an error msg stating that client has no authentication to connect to server comes.. can anybody help on this...
00:21Vasanth has quit IRC
00:28
<vagrantc>
only if you stuck around longer...
00:31lnxnubie has joined #ltsp
00:32lnxnubie has left #ltsp
00:36cyberorg has joined #ltsp
00:41
<daduke>
vagrantc: hey. how's it look today? Got some minutes?
00:42
<vagrantc>
daduke: well, a number of things aren't looking so great... but i've got a few minutes :)
00:42
<daduke>
vagrantc: cool. I updated ldm, you might remember. Basically, we got 3 issues left:
00:43
<vagrantc>
daduke: which linux distro and version?
00:44
<daduke>
vagrantc: ah sorry, latest alioth on etch.
00:44
<vagrantc>
daduke: on debian etch?
00:44
<daduke>
vagrantc: yup.
00:44
<vagrantc>
i do enough troubleshooting that i can't possibly keep everything in memory :)
00:45
<daduke>
vagrantc: of course, didn't think about it. Never mind.
00:45
<vagrantc>
daduke: so your 3 remaining issues?
00:46
<daduke>
vagrantc: right. 1) is the kiosk autologin that we patched into ldm until we did the upgrade. Are there any plans to include this patch? Looking for the URL right now...
00:47
vagrantc: it's here https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/161794
00:48esrin has quit IRC
00:48
<daduke>
vagrantc: patch itself is pretty much in the middle
00:49
<vagrantc>
daduke: patch was included upstream, and i had hoped to have a new package uploaded to debian some hours ago, but it got rejected ... i think because the m68k buildd is so slow it thought i was trying to hijack ldm from the ltsp package
00:50
<daduke>
vagrantc: great! then we just wait. thanks for your work anyway, greatly appreciated.
00:51
<vagrantc>
daduke: see http://bugs.debian.org/ldm
00:51
<daduke>
vagrantc: 2) would be the long delay if the user provides a wrong password. It takes minutes to get back to ldm. Any idea why? I tell ppl to just power cycle the thin client, it's faster ;)
00:52
<vagrantc>
daduke: very, very glad to hear the boot takes less than a minute! :)
00:52
daduke: i haven't experienced it taking minutes when entering an invalid password.
00:52
<daduke>
vagrantc: booting is fast. we use http://pcengines.ch/alix1c.htm, they're pretty cool.
00:53
vagrantc: ok, I will try to debug this a little. We have experienced this for some versions of ldm now. Not a big deal, teaches ppl to type their stuff right...
00:54
<vagrantc>
daduke: there are a couple patches floating around that only ask the password once
00:55
daduke: there's also a patch by gadi that just respawns the greeter on password failure, rather than respawning all of ldm ... both of those would probably help some.
00:55
<daduke>
vagrantc: 3) would be: I'm still fighting with multiple local USB devices. We auth users against of OpenLDAP server and we don't want to create a global fuse group. Where could I put the useradd so that it's executed upon login?
00:55
vagrantc: ok, I'll have a look at those patches. thanks.
00:55
<vagrantc>
daduke: what do you mean by useradd ?
00:56
daduke: how to add them to the group on login?
00:56
<daduke>
vagrantc: adduser, sorry, still early in the morning around here...
00:56
<vagrantc>
daduke: you want to know how to add them to the group on login?
00:57
<daduke>
vagrantc: is there any execute-upon-successful-login-script for ldm?
00:57
vagrantc: exactly. haven't figured out this one
00:58
<vagrantc>
daduke: well, in /opt/ltsp/i386/usr/[share|lib]/ldm/rc.d/ you can drop files
00:58
daduke: and they can connect to the server and run programs there ...
00:58
daduke: using the ssh tunnel
00:59
<daduke>
vagrantc: great! missed that one somehow. That's all we need.
00:59sri_j has quit IRC
00:59
<vagrantc>
daduke: but those will be run as the user- you'll need root access to add a user to a new group
00:59
<daduke>
vagrantc: oh.
01:00
<vagrantc>
daduke: the simplest approach, if you don't mind enabling fuse for all users, is to allow all users write access to fuse
01:00
/dev/fuse, i mean
01:01
<daduke>
vagrantc: that's the whole reason behind the fuse membership? we can do that no prob
01:02
<vagrantc>
daduke: simply add MODE="0666" to the fuse line in /etc/udev/rules.d/020_permissions.rules ... i think ... haven't tried it myself
01:03
<daduke>
vagrantc: we'll figure it out. I thought there was more to it than just write permission to /dev/fuse
01:04
<vagrantc>
daduke: i'm pretty sure that's it. you can test it by chmod o+w /dev/fuse
01:05
<daduke>
vagrantc: great. thanks a lot for your help, the LTSP clients are received enthusiastically around here.
01:06
<vagrantc>
daduke: whereabouts is here? :)
01:06
<daduke>
vagrantc: Physics Dept. of the Swiss Federal Institute of Technology in Zurich
01:07
vagrantc: I'll write a blog posting about the whole installation soon and send you the link.
01:07
<vagrantc>
daduke: that wouldn't happen to be where madduck worked?
01:07
<daduke>
vagrantc: hmm, what's his real name?
01:08
<vagrantc>
daduke: martin f krafft
01:09* vagrantc disputes conceptions of real
01:09
<vagrantc>
or rather, i failed to dispute them :)
01:09
<tarzeau>
good morning
01:09
<daduke>
vagrantc: he's working at the University of Zurich
01:09
vagrantc: :)
01:10
<vagrantc>
daduke: ah. well, zurich's all one place from 4,000+ miles away :)
01:10
<daduke>
vagrantc: you got it. what's your base?
01:11
<vagrantc>
daduke: the far side of north america ... i like to call it cascadia :)
01:12
<daduke>
vagrantc: WA? been there last spring
01:12
<vagrantc>
daduke: if you're ever this way again, swing by freegeek in portland :)
01:13
<daduke>
vagrantc: ah, OR then. I'll do!
01:13
<vagrantc>
that's where i cut my teeth on thin-clients, so to speak.
01:16
daduke: did make a slight change with ldm's autologin support. it now requires LDM_AUTOLOGIN=True to enable it, and then specifying LDM_USERNAME/LDM_PASSWORD override the default (which is to just use the hostname of the thin-client)
01:16
<daduke>
vagrantc: cool. I'll test the new version as soon as it's out then
01:17
<vagrantc>
daduke: i could release a new backport before the other version hit's sid... wouldn't be the first time :)
01:18
<daduke>
vagrantc: for us it's not urgent at all, we
01:18
vagrantc: oops. we'd just like to have kiosk terminals at some point
01:18
<vagrantc>
daduke: and you only need autologin?
01:19
<daduke>
vagrantc: only as in? we created a local user and have it autologin with a fullscreen FF/icedoveweaselwhatever
01:20
<vagrantc>
RyanRyan52 wrote a patch that also can display a button at the login screen that behaves almost identical to autologin, but it also allows you to log in with other account names
01:20
daduke: local user, as in local to the thin-client ?
01:21
daduke: or local to the server?
01:21
<daduke>
vagrantc: ah nice, but auto autologin is what we need. nope, local to the terminal server as opposed to LDAP
01:21
<vagrantc>
daduke: ah, got it.
01:21
local is a complicated term in the land of networked computing.
01:21* daduke agrees
01:22
<daduke>
vagrantc: excellent! all my issues seem to be or will be solved then.
01:23
<vagrantc>
daduke: so sounds like 2 out of 3 issues is mostly addressed ... and the remaining issue, i know there is some effort towards improving it. just not sure how quickly it will manifest.
01:24
<daduke>
vagrantc: that's the least important one. learn to type ppl!
01:24
<vagrantc>
heh
01:25
<daduke>
vagrantc: all right, I guess some of us are gonna hit the pillow soon, and it sure ain't me. thanks again.
01:35Faithful has joined #ltsp
01:38Q-FUNK has joined #ltsp
01:40misui has joined #ltsp
01:40misui is now known as llun
01:42aarrccchh has quit IRC
02:01Daggett has joined #ltsp
02:15vagrantc has quit IRC
02:41lexa_ has joined #ltsp
02:44soneyka has quit IRC
02:59Daggett has quit IRC
03:04mikkel has joined #ltsp
03:16Daggett has joined #ltsp
03:30sri_j has joined #ltsp
03:38nepali has quit IRC
03:49zodman has quit IRC
03:59q_ has joined #ltsp
04:01ogra has quit IRC
04:01lns has quit IRC
04:01yanu has quit IRC
04:01ikonia has quit IRC
04:01dberkholz has quit IRC
04:02dberkholz has joined #ltsp
04:07ari_stress has left #ltsp
04:07ogra has joined #ltsp
04:07lns has joined #ltsp
04:07ikonia has joined #ltsp
04:07yanu has joined #ltsp
04:08alekibango has quit IRC
04:09cyberorg has quit IRC
04:09cyberorg has joined #ltsp
04:16Egyptian[Home] has quit IRC
04:19Egyptian[Home] has joined #ltsp
04:27ogra has quit IRC
04:43ogra has joined #ltsp
04:50kysucix has joined #ltsp
04:50
<kysucix>
hi
04:51
anybody has changed usplash on a ltsp with success?
04:51
I'm following https://help.ubuntu.com/community/USplashCustomizationHowto but without luck :\
04:52
and is it possible to use bootchart with ltsp?
05:02cyberorg has quit IRC
05:02cyberorg_ has joined #ltsp
05:02
<ogra>
yes, it is
05:03cyberorg_ is now known as cyberorg
05:04
<kysucix>
great :)
05:08K_O-Gnom has joined #ltsp
05:08
<ogra>
just install the package in the chroot and run ltsp-update-kernels afterwards
05:09
but note that it will slow down your boot significantly ...
05:10
<kysucix>
ok
05:26sep has quit IRC
05:27gonzaloaf has quit IRC
05:35sep has joined #ltsp
05:38ogra has quit IRC
05:38ogra has joined #ltsp
05:38cyberorg has quit IRC
05:39cyberorg has joined #ltsp
05:44llun has left #ltsp
05:47ari_stress has joined #ltsp
05:47
<ari_stress>
good evening :)
06:00mhterres has joined #ltsp
06:17Q-FUNK has quit IRC
06:18slidesinger has quit IRC
06:41vlt has joined #ltsp
06:48jammcq has quit IRC
06:50
<vlt>
Hello. Our LTSP server is quite big and fast. I notice a huge difference between our clients (from 233 MHz to 1.2 GHz machines). On the faster ones everything is fine, on the rather slower clients everything is s-o-o-o s-l-l-o-w-w-w. Maybe my opinion of "thin" clients is a bit different, but (how) can I optimize performance?
06:55
<johnny>
how about the ram?
06:55
<ogra>
vlt, which distro/LTSP release ?
06:56ari_stress has quit IRC
06:59
<johnny>
morning ogra
07:00
<ogra>
wow, the daily iso with my new merged packages just works ... :)
07:00
<johnny>
i'm sure you were hoping for that to happen someday :)
07:01
<ogra>
well, i didnt test the uploads i did :)
07:01
usually i do soem extensive testing, but time to the freeze date was to short so i was expecting at least a handfull of new bugs :)
07:04
<johnny>
hmm.. i couldn't get in touch with seb128 yesterday, maybe today..
07:04
nor federico
07:08Q-FUNK has joined #ltsp
07:22Q-FUNK has quit IRC
07:30ogra has quit IRC
07:30ogra has joined #ltsp
07:39K_O-Gnom has quit IRC
07:39kysucix has quit IRC
07:43Q-FUNK has joined #ltsp
07:43kysucix has joined #ltsp
07:47nicoAMG has joined #ltsp
07:52|mathesi| has quit IRC
07:53
<vlt>
ogra: Hmmm, I'm still with Ubuntu Dapper LTS ...
07:53* johnny still thinks linux/gnome is too early to stablize, but maybe i'm crazy..
07:54
<johnny>
maybe i don't like being stuck with versions over a year old :)
07:54
vlt, lots has changed in ltsp since then
07:55
<vlt>
johnny: Things that could improve performance for the slower clients?
07:55
<johnny>
always ..
07:55
but how much ram do they have?
07:55
hmm..
07:55
maybe i think local apps too often :)
07:55
<vlt>
32 to 256 MB plus 512 MB NBD swap.
07:56
no local apps involved here
07:57
<johnny>
any difference on the network card?
07:57
or all they all just generic 10/100 ?
07:58
<ogra>
and the ones with 32 boot ?
07:58
<vlt>
All 100 Mbit
07:59
<johnny>
ogra, no scott lately?
07:59
<ogra>
!seen sbalneav
07:59
<ltspbot>
ogra: sbalneav was last seen in #ltsp 1 week, 1 day, 23 hours, and 17 seconds ago: <sbalneav> What are we looking at?
07:59
<ogra>
not the last week it seems
07:59
<johnny>
hmm.. i wish i could afford to dedicated a chunk of mine time to code on ltsp :(
08:00
<ogra>
scott likely spent more time on ltsp than on his RL job during gutsy development ...
08:00
<johnny>
much better than coding crappy websites for people ..
08:00
<vlt>
ogra: I checked: No 32 MB machines running atm, but I think I remember booting one of them successfully.
08:00
<johnny>
so when you say slower? which are the ones that are slower?
08:00
<ogra>
vlt, but thats not the ubuntu ltsp then i suppose
08:00
<johnny>
if you don't even have a 32mb up
08:00
<vlt>
Most clients are HP's T5000 series
08:01
<johnny>
ogra, i'm assuming that he didn't have another volunteer job like i have
08:01
<ogra>
(i dont think the dapper kernel fits in less than 48M unpacked)
08:01
no, he has actually a fulltime job
08:01
<johnny>
yes
08:01
i mean another one on top
08:01
<ogra>
caring for huge piles of lawyer desktops :)
08:02
well, he has a family and bought a cottage last year ... i guess his family and the new house demand time as well :)
08:03
he'll be back :)
08:03
<vlt>
johnny: Slower CPU -> slower working. I have 256 MB machines with 400 MHz that are slow, others with 64 MB but 800 MHz are fast.
08:03
<ogra>
vlt, which ltsp version is that ?
08:04
the one shipped with dapper or the old ltsp 4.x from ltsp.org
08:07
<vlt>
ogra: The dapper packaged one.
08:07
<johnny>
ogra, did dapper have ltsp5?
08:07
<vlt>
johnny: I think so
08:07
<johnny>
i had no idea
08:07
<ogra>
yes, dapper was the second release
08:07
we started with breezy
08:07
<johnny>
so it has that DIRECTX flag?
08:07
<ogra>
nope
08:07
<johnny>
oh
08:08
did it use ssh ?
08:08
<ogra>
but it didnt have localdev ;)
08:08
so it does not much harm to switch to XDMCP apart from the fact that your passwords go through the net in cleartext
08:08
<vlt>
johnny: Runnning `top` on the slow clients shows X and ssh as the top most cup consuming processes.
08:08
<johnny>
just like in ltsp4 ..
08:08
right?
08:08* ogra cant remember if dapper had sound support ...
08:09
<ogra>
damned
08:09
seems i'm getting old
08:09
<johnny>
?
08:09
<vlt>
s/cup/cpu/
08:11
I added the 512 MB nbd swap after having complaints about crashing X over and over again.
08:12
<ogra>
well, if the machine starts swapping over the net it will get extremly slow anyway
08:12
nbd swap is only a saftey net that makes it possible to save your stuff ...
08:12
<vlt>
ogra: Usually they don't need the swap space at all.
08:12
<ogra>
but in case it gets yused you will find yur system to slow to do actual work
08:13
there is a little trick that speeds it up a bit
08:14Faithful has quit IRC
08:14
<ogra>
you mount a tmpfs (indeed your server needs enough ram) and configure the nbd server in a way that it uses the swapfiles from that tmpfs ...)
08:14
<vlt>
ogra: But everytime a user opens an email containing quite large jpg attachments (which happens often here) the client's X server uses up to 400 MB of RAM :(
08:14
<ogra>
that way you actually use the servers ram for the clients
08:15
400M RES or VIRT ?
08:15* ogra cant imagine it uses real 400M
08:16
<vlt>
ogra: I think it was RES, leading to the kernel kicking X ...
08:18
Isn't there a better way to display a 640x480 image on the client than unpacking it to 400+ MB on the client?
08:18Gadi has joined #ltsp
08:19
<ogra>
depends on your mailer
08:19
saldy the xserver allows that
08:19
so its up to your mail app how it handles the images
08:20
<vlt>
Ok, back to the speed issue: Because the swap ram is only needeed when displaying large images (in kmail) I don't think I need to occupy gigs of server's RAM just for the nbd swapfiles ... Any other improvement possible?
08:20
<ogra>
firefox is known pretty bad here, so if your users have thunderbird that might be a similar prob
08:20
<johnny>
don't use kmail :)
08:20
how is firefox3 in that reg ard?
08:21
seems like it should be better
08:21
<ogra>
well, as i said, the biggest improvements for the slow CPUs might be to switch to XDMCP
08:21
ff3 is a lot better
08:21
<vlt>
ogra: How to do this?
08:21
<johnny>
i'm waiting for the epiphany patch to hit
08:21
<ogra>
but i doubt you wil get it easily running on dapper
08:22
<vlt>
ogra: xdmcp or ff3?
08:22
<ogra>
vlt, you put SCREEN_07=startx in your lts.conf and make sure XDMCP support is switched on in gdm's config
08:22
but i doubt you wil get ff3 easily running on dapper :)
08:23
<vlt>
ogra: gdm? Aren't we using ldm?
08:28
<ogra>
right
08:29
ldm uses ssh tunnels for the X transport
08:29
*encrypted* ssh tunnels :)
08:29
that means you need CPU power to do the de/encrypting
08:30
the SCREEN_07=startx tells ltsp to query for XDMCP connections instead of using ldm
08:30
gdm on the server needs to provide XDMCP so that the client gets an answer
08:31
later ldm versions have the ability to switch off encryption for everything but the login
08:32
<vlt>
ogra: Switching off ssh encryption? This is possible? Coll.
08:32
Cool.
08:35K_O-Gnom has joined #ltsp
08:40
<vlt>
ogra: hmmmm, "SCREEN_07=startx" lets my client "freeze". It doesn't react on any kb input. `top` (over ssh) tells me X is running on 99.9% cpu load. Not killable :(
08:42
ogra: `pstree` shows X as child of startx ... so at least this worked ;)
08:44gonzaloaf has joined #ltsp
08:56
<vlt>
I checked on a client where I don'
08:56
oops
08:57
... don't need to run X with vesa driver and there X started but I couldn't see more than the grey bg and the X cursor.
08:57
What do I have to setup on the server axactly?
08:57
exactly*
08:57
<Gadi>
vlt: allow remote connections in Administration > Login Screen
08:57
then, logout completely
08:57
and restart gdm
08:58
<vlt>
Gadi: "Adinistration"? "Login Screen"? What files do I have to edit?
08:58
<Gadi>
you'll know its working if you get a response to: netstat -anp|grep :177
08:59
vlt, well, gdm usually keeps a custom gdm conf file in /etc/gdm
08:59
you are advised no to edit /etc/gdm/gdm.conf directly, but rather put the diffs in the custom file
08:59
much easier to do correctly from the GUI
09:01cliebow_ has joined #ltsp
09:01
<vlt>
Gadi: Ok, I logged in as a user .. aah, it's Kubuntu btw ... does it matter?
09:01
<Gadi>
hmm... do they use gdm or kdm?
09:02
<Q-FUNK>
gadim :D
09:02
<Gadi>
either way, find the login control in the control panel
09:02
and enable remote connection
09:02
Q-FUNK: !!
09:02
<vlt>
Gadi: I think it's kdm. But it's an LTSP only machine so I've never seen it ;)
09:07
Does anyone know how to enable XDMCP remote login on Kubuntu (kdm)?
09:09
<Gadi>
http://www.faqs.org/docs/Linux-HOWTO/XDMCP-HOWTO.html
09:10
/etc/kde3/kdm/kdmrc:
09:10
[Xdmcp]
09:10
Enable=true And in
09:10
/etc/kde3/kdm/Xaccess, uncomment:
09:10
* #any host can get a login window
09:10
* CHOOSER BROADCAST #any indirect host can get a chooser
09:14
<warren>
OK... Eric Harrison's old K12LTSP had a script called ltsp-initialize that sets all the server settings to enable terminal server.
09:14
What is the equivalent in upstream's ltsp?
09:14
Aside from this and ldm's broken chooser I'm almost done with the basics.
09:15
<Gadi>
warren: there should be none in upstream - the distros should configure their own packages
09:15
<warren>
no...
09:15
I mean... we ship the packages to do terminal server stuff
09:15
<vlt>
Gadi: Thanks.
09:15
<warren>
but there is no upstream standard script name to set it up?
09:15* vlt is trying
09:15
<warren>
like ltsp-build-client is the standard name to setup a chroot
09:15
<Gadi>
warren: no - bec we would have to configure other server packages
09:15
that we know nothing about
09:16
the chroot is selfcontained
09:16
<warren>
so what or how are the server stuff configured to serve?
09:16
chkconfig tftp on
09:16
add stuff to /etc/exports
09:16
etc.
09:16
<Gadi>
well, ubuntu and debian configure the other packages in post-install
09:16
assuming certain dependencies
09:16
<warren>
oh!
09:16
Ubuntu enables services by default upon package install?
09:17
We do the opposite. It is against our policy.
09:17
<Gadi>
so, when ltsp-server is installed, it relies on other packages to be there and it enables/configures them
09:17
<warren>
oh
09:17
OK, so I need to add the equivalent of Eric's old script then.
09:17* Gadi nods - in fedora specific pkg
09:21
<Q-FUNK>
warren: btw, that RH France guy's address bounced: user mailbox locked.
09:21
<warren>
eh?
09:21
Q-FUNK, what was his address?
09:24
btw
09:24
ltsp-build-client plugins
09:24
case "$MODE" in
09:24
commandline)
09:24
add_option "kickstart" "`eval_gettext "Path to kickstart file"`" "advanced" "false"
09:24
add_option "installrepo" "`eval_gettext "Repository to pull packages from"`" "advanced" "false"
09:24
what does the two fields at the end of each option mean?
09:39
<vlt>
Gadi: Thank you. Seems to work. Now the main load is X, no more ssh involved (it's quite save environment here).
09:48
<ogra>
warren, advanced/regular is for the help location (--help or --extra-help) i think vagrant wanted to kep the help text smaller with that and kept the options in two categories
09:48
true/false stands for arguments ... true means the option takes args, false makes it a boolean on/off switch iirc
09:49
<warren>
ogra, ah, thanks.
09:53
<vlt>
Now the user sees kdm for login and logout. Any idea how they should switch off the client now?
10:19
<Gadi>
vlt: press the power button
10:23
<vlt>
Gadi: ;)
10:24
Can't I have mor than one [client] sections in lts.conf?
10:24
it seems as if options are ignored otherwise.
10:28sepski has joined #ltsp
10:28
<Gadi>
vlt: are you specifying by MAC or hostname?
10:32
<vlt>
both
10:33
the more hw related thing like vesa driver by MAC
10:33
user specipic settings via IP
10:34* Gadi doesnt understand
10:34
<Gadi>
I mean in lts.conf
10:34
lts.conf configures machines not users
10:35
each stanza in lts.conf should be for a specific workstation
10:35
and only one per workstation
10:35
<cliebow_>
how do you set tall_blonde=yes in lts.conf?
10:36
<Gadi>
and set [default] for unspecified workstations
10:37
<vlt>
Gadi: Ok, I'll try it this way. Thank you.
10:40bobby_C has joined #ltsp
10:41
<warren>
I can have afterinstall) in multiple plugin files?
10:41
after-install)
11:03
<ogra>
sure, why not ? it just defines a point in the build process
11:04staffencasa has joined #ltsp
11:19
<lns>
cliebow_, for some reason I think you have to deny using linux thin clients all together for tall_blonde=yes to work
11:24
<cliebow_>
8~)
11:24
<johnny>
lns, think so? i disagree :)
11:25
a guy can be a tall blonde
11:25
<lns>
johnny, tmi my friend =p
11:25
<johnny>
i'm sure there are plenty of tall blonde guys around here
11:25
that i might be a tall blonde guy?
11:26
how is that tmi?
11:26
<lns>
lol...well maybe i was missing cliebow_'s comment
11:26
<johnny>
i might have blue eyes too.. ON HO
11:26
err
11:26
OH NO*
11:26
<cliebow_>
how about tall_blonde_lady=yes
11:27
<johnny>
how about you keep it non gender specific to get more females to perhaps stick around
11:27
it's endemic in any IT and open source projets
11:27
s/any/many/
11:28
my ltsp deployement is in a very feminist friendly bookstore, so i hear that kinda thing often
11:28
about often sexist geeks
11:31
<lns>
i'd use that rather than johnny's blue_eyes=yes...no offense, that's just my position ;)
11:32
johnny, if you don't mind me asking, how is your bookstore feminist friendly?
11:38
<johnny>
the sheer number of books in that category
11:38
or rather %
11:38
<lns>
ah
11:39
<cliebow_>
must be regional..we have very few tall blonds of any kind..
11:40
<johnny>
people need to retire the thing about male linux geeks not having girlfriends
11:40
it's so 1999
11:40
<cliebow_>
heh
11:42
<johnny>
the problem never has to do with them using linux, it has to be with them being socially inept in general
11:43
i was the only linux user in my group of friends for users.. and one of the two computer geeks..
11:43
err for years
11:43
never had a problem
11:44
<lns>
I honestly don't hold that stereotype at all, i was just running with cliebow_'s comment
11:44
<johnny>
sorry.. i didn't say you did
11:44
<lns>
=)
11:44
<johnny>
it just reminded me
11:44
of comments i'd seen on the internet
11:45
even recently
11:45
<lns>
the intarweb?
11:45
<johnny>
netterwebs
11:45
<lns>
hehe
11:45
<johnny>
or webbernets
11:45
both good..
11:45
or as my friend micah calls it
11:45
the internerd
11:46Q-FUNK has quit IRC
11:46
<johnny>
as he uses his iphone.. hehe
11:46
<cliebow_>
hhe
11:46
<johnny>
he does an interesting job..
11:46
<lns>
personally, if i were going to have my choice of lts.conf options it would be "just make everything work=yes" =p
11:46
<johnny>
writes graphical displays for gas pumps
11:46
using imagemagick and perl
11:47
lns, but what happens to those of us who need to get paid :)
11:47
if everything worked we'd be out of a job :)
11:47
<lns>
ugh...graphical displays on gas pumps... "DO YOU WANT A CAR WASH??" NO I DONT FREGGIN WANT ONE! STOP SHOWING ME COMMERCIALS!
11:47
<johnny>
he's doing one for the weather
11:47
which is actually good idea
11:47
<lns>
well that is nice
11:47
<johnny>
until everybody has graphical cell phones
11:49
<lns>
Does anyone have an answer to the issue I've had on all of my servers, when I log in with GDM then LDM (or could be due to something else, I just can't figure it out) where it complains about applets not loading and keyboard settings in X differing from Gnome kb settings?
11:50
Sometimes cascading error dialogs when I log in of 3-4
11:51
<johnny>
i got that one
11:51
the keyboard settings thing
11:51
i'll figure it out someday
11:52Daggett has quit IRC
11:54
<lns>
thinking about it makes me wonder if gdm caches keyboard settings and conflicts with ldm/X's autoconfiguration while booting the thin client...
11:54
<johnny>
i get it without using gdm at all
11:55kysucix has quit IRC
11:55
<lns>
hmm
11:55
<johnny>
except on the server itself that is
11:55
but that wouldn't count
11:56
<lns>
why not?
11:56Q-FUNK has joined #ltsp
11:56
<lns>
Q-FUNK!
11:56
<johnny>
why would it?
11:57
<lns>
johnny, well when you log in with gdm, does it cache hardware (i.e. keyboard) settings somewhere for your user?
11:57
<Q-FUNK>
hey :)
11:57
<johnny>
you mean for the same user?
11:57
<lns>
johnny, yes
11:57
<johnny>
oh.. lemme restate then
11:58
i get it without using gdm at all for any thin client accounts
11:58
i only use gdm to login to the point of sale accoun t
11:59
<lns>
Q-FUNK, I'm the one with the Koolu thin clients in bug 180742
11:59
johnny, oh gotcha
12:00
<Q-FUNK>
lns: ah!
12:00
<johnny>
there's a mismatch between the default gconf schema for your user accounts and the generated xorg.conf for the thin clients it seems
12:01
<Q-FUNK>
lns: did you contact Koolu about whether or not their BIOS has DDC enabled?
12:01
<lns>
Q-FUNK, i was actually grabbing their support e-mail to contact them, i just saw your latest comment
12:02
<Q-FUNK>
ok
12:02
brb
12:02Q-FUNK has quit IRC
12:07
<lns>
johnny, that's strange that gconf would have a 'default' kb config that causes an error to pop up asking the user what they want to do if it detects a (better?) different config
12:08
seems kind of unnecessary.. wonder if there's a way to globally turn that off
12:08
<johnny>
who said it's better?
12:08
and it isn't an error
12:09
<lns>
well
12:09
aside from error/non error definition, it confuses students
12:09
<johnny>
agreed
12:10Q-FUNK has joined #ltsp
12:10
<johnny>
ogra, do you know anything about that?
12:12
<Q-FUNK>
lns: ok, so you were saying that you're about to contact Koolu about their BIOS?
12:12
<lns>
I did just send an e-mail to their support channel
12:12
<Q-FUNK>
ok
12:12
<lns>
Q-FUNK, i'm trying right now to boot bypassing my kvm - i did that earlier but not with 2.7.7.6 amd drivers i think
12:12
<johnny>
lns, there's probably some setting you an edit in /etc/gconf
12:13
<Q-FUNK>
lns: I wouldn't be surprised if their BIOS had broken DDC. many vendors have the same problem.
12:13
<johnny>
/desktop/gnome/peripherals/keyboard/kbd/model and/or /desktop/gnome/peripherals/keyboard/kbd.sysbackup/model
12:13
<lns>
johnny, yeah i wonder if setting a mandatory setting in gconf would surpress that msg?
12:13
<Q-FUNK>
here, we barely got around fixing it recently and we're lucky enough to have a license that includes access to the source code. other ODM might not have that.
12:13
<johnny>
you'd do better to set a default imo
12:14
<lns>
Q-FUNK, hmm...seems like that's a (fairly) common problem then
12:14
<johnny>
yes
12:14
<lns>
Q-FUNK, nope - still 800x600.
12:15
<Q-FUNK>
lns: there's not many BIOS vendors who cover the Geode and most ODM seem to pick the two worst ones.
12:15
<lns>
Q-FUNK, yeah - i was dealing with another geode tc from synertrontech using general software bios...ugh
12:15
that was a horrible experience
12:16
<Q-FUNK>
you updated both xserver-xorg-core and xserver-xorg-video-amd to what's in my PPA and reuilt the chroot image?
12:16
sudo ltsp-update-image
12:16
<lns>
Q-FUNK, well i updated both 2 days ago from your PPA using apt-get and it pulled in new xorg core and geode drivers
12:16
(in chroot, yes - and rebuilt image)
12:16
yesterday i saw the new 2.7.7.6
12:17
<Q-FUNK>
you need to regenerate the squashfs image too
12:17
<lns>
but for some reason it wasn't wanting to pull down
12:17
i downloaded the 2.7.7.6 manually and installed in chroot (and yes, ltsp-update-image afterwards)
12:17
i didn't see another updated xorg-core package from less than 7 days ago so i didn't bother downloading that manually
12:21vagrantc has joined #ltsp
12:22
<lns>
man, i've got to start asking questions in this chan earlier than i do.. i try at about 3-4 PST and it's deeead
12:22
everyone here actually has a normal work schedule ;)
12:22
<Q-FUNK>
yup
12:22
<lns>
or at least lives in different timezones
12:23
<vagrantc>
otavio: would you have time for an ldm upload?
12:25
<otavio>
vagrantc: sure
12:26
<vagrantc>
otavio: as best i can figure, the debian-maintainer checks are messing up, i think because m68k hasn't yet built new ltsp or ldm packages, and so the installer rejected my upload yesterday. this puts both unstable and testing into a bad state.
12:26
<otavio>
vagrantc: I did all d-i modules today, why not one more? :P
12:27
vagrantc: send the packages to my mail and I do them asap
12:27
<vagrantc>
otavio: should i just do the normal source package stuff? or could i send you the binaries too? sometimes i386 buildd is a bit slow and i think i386 is the most used architecture...
12:28
<otavio>
vagrantc: i386 will be done as soon as amd64 gets in archive. It's done fastly now
12:28
vagrantc: i guess it's best to let it to be autobuild
12:28
<vagrantc>
otavio: ok. i've had 4 day delays in recent times...
12:29
<otavio>
vagrantc: we had been in trouble with buildds. People are working to get it sorted out properly
12:29
<vagrantc>
otavio: that's great :)
12:29zodman has joined #ltsp
12:36
<dberkholz>
i love how random architectures like m68k can hold up the whole thing
12:36
that async nature of gentoo is one thing i really like
12:36
<vagrantc>
m68k isn't even a release candidate at the moment
12:36
dberkholz: i think it's actually a bug in the checks, more than anything.
12:37
<dberkholz>
hopefully it's an architecture-specific one on an arch nobody knows anything about. those are fun
12:44
<vagrantc>
seems like mips and mipsel have picked up speed over the last few days ... dropped from nearly 300th in the queue to 180 on mips ... and 350+ to 279 on mipsel
12:45skipper has joined #ltsp
12:46
<skipper>
I have a problem
12:47
I have figured out that when I load my thin clients, I end up in busybody in text mode. No x-windows loads or runs.
12:52Q-FUNK has quit IRC
12:54
<cliebow_>
ohh..so x is not startingt
12:54
look in the users .xsession-errors..anything there?
12:55
<vagrantc>
skipper: you mean busybox?
12:55
haven't even gotten / mounted, is my guess
12:55
<cliebow_>
yeah..you are right..
12:59vagrantc has quit IRC
13:13
<skipper>
I am still here, I had to do some work. I will look at the error log
13:13
<vlt>
Hello. I switched from ldm login to kdm via XDMCP. Any idea how the users can switch off the client now? I don't really want them to press the power button for at least 8 seconds ...
13:15
<Gadi>
vlt: you can usuall make it Instant Off in the BIOS
13:15
otherwise, install acpid in the chroot
13:17
<vlt>
Gadi: Before there was this tiny off switch on the lower left corner. How can installing acpid help?
13:17jammcq has joined #ltsp
13:17
<Gadi>
acpid will allow you to tie a command to the power button
13:17
<skipper>
re: My thin client problem --I cannot find the .xsession-errors file. Where do I look?
13:17
<Gadi>
so it will halt the system immediately
13:18
<vlt>
Gadi: Aah, I understand.
13:18
<Gadi>
since you use a remote display manager, it has no way of turning off your client
13:18
(thank goodness)
13:19
<vlt>
Gadi: Must I really use kdm when connecting via XDMCP?
13:19
<Gadi>
vlt: you can use gdm or xdm
13:19
the whole "DM" part of XDMCP is that it is a remote DM
13:22* vlt must admit that he doesn't know eactly what XDMCP means ...
13:24
<Gadi>
X Display Manager Control Protocol - basically a protocol for controlling access to the display manager over the network
13:25
ie getting a login screen (greeter) or choice of servers (chooser)
13:25
<vlt>
Another question: When someone has open an OpenOffice window on one client and then---from another pc but logged in as the same (maybe guest account) user---opens an office document it opens on the first pc. Is this an OOo or KDE problem? Any idea how to prevent this?
13:25
<johnny>
you're not supposed to login to hte same user
13:25
dont' do it :)
13:25skipper has quit IRC
13:26mfc_alpha has joined #ltsp
13:26
<vlt>
johnny: Ok ;)
13:26
<mfc_alpha>
hello!
13:27
Is there someone who know how nbd-server works?
13:28
I have some problem with the boot of my client and it seems to come from that
13:28
<cyberorg>
mfc_alpha, ask
13:28
<mfc_alpha>
Is that right that nbd-server is use instead of NFS for ubuntu gutsy?
13:29
<cyberorg>
yes
13:29
<mfc_alpha>
in fact my client get the kernel but after i get a error during the boot
13:29
Mounting /rofs on /root/rofs failed: Invalid Argument
13:30
and after the same for /root/dev
13:30
and /sys
13:30
and /proc
13:30
and finaly "Target filesystem doesn't have /sbin/init"
13:31
that's look like if the FS is not mounting isn't?
13:32
<cyberorg>
mfc_alpha, can you mount nbd from other clients?
13:32
<mfc_alpha>
no... :(
13:32
<cyberorg>
nbd-client serverip port /dev/nbd0 ?
13:33
<mfc_alpha>
cyberborg, humm sorry?
13:34
cyberborg, I have to run this command on the client?
13:36
<cyberorg>
yes
13:36
<mfc_alpha>
cyberborg, I run this command on the client ... no feddback
13:36
feedback*
13:36
<cyberorg>
replace port and ip according to your setup
13:36
<mfc_alpha>
yes sure ;)
13:37
I use the port 2000 ( I found it in /etc/inetd.conf), Is that right?
13:39
<cyberorg>
yes
13:39
<Gadi>
cyberorg: what distro?
13:40
<mfc_alpha>
ubuntu, gutsy for me
13:40
<cyberorg>
Gadi, mfc_alpha uses gutsy, i use suse
13:40
<Gadi>
oops
13:40
sorry
13:40
:)
13:40
<mfc_alpha>
;)
13:40
<cyberorg>
:)
13:41
<Gadi>
mfc_alpha: the server is used for dhcp+tftp+nbd, yeah?
13:41
ur not using a different server for part of it?
13:41
<mfc_alpha>
no everything is on the same server
13:41
dhcp+tftp+nbd
13:41
<Gadi>
good - that makes life easier
13:42
can you run: sudo ltsp-update-kernels
13:42
and reboot the thin client
13:42
<mfc_alpha>
ok!
13:44
done... I get the same error
13:44
<Gadi>
on the server, do: sudo which nbdrootd
13:45
<mfc_alpha>
I get : /usr/sbin/nbdrootd
13:45
<Gadi>
good
13:45
how about: grep nbdrootd /etc/inetd.conf
13:46
<mfc_alpha>
2000 stream tcp nowait nobody /usr/sbin/tcpd /usr/sbin/nbdrootd /opt/ltsp/images/i386.img
13:46
<Gadi>
excellent
13:46
now, ls /opt/ltsp/images/i386.img
13:47
<mfc_alpha>
/opt/ltsp/images/i386.img
13:47
<Gadi>
so far so good
13:47
<mfc_alpha>
:D
13:47
<Gadi>
any firewalls up?
13:47
<mfc_alpha>
no :(
13:47
and it's a direct ethernet connection
13:47
<Gadi>
ok, can you pastebot your dhcpd.conf and output of ifconfig?
13:48
!pastebot
13:48
<ltspbot>
Gadi: "pastebot" is The LTSP pastebot is at http://pastebot.ltsp.org. Please paste all text longer than a line or two to the pastebot, as it helps to reduce traffic in the channel. A link to the content will be pasted in the channel.
13:49
<mfc_alpha>
ok for ifconfig : the interresting interface is eth0
13:49
<Gadi>
also, you could install telnet on the server (apt-get install telnet) and try to: telnet localhost 2000
13:49
<mfc_alpha>
pastebot
13:50
humm! the connection by telnet is refuse!
13:50
<Gadi>
thats ok
13:50
<mfc_alpha>
Trying 127.0.0.1...telnet: Unable to connect to remote host: Connection refused
13:50
<Gadi>
ah ok
13:50
yeah it should accept it and then close it
13:51
try: /etc/init.d/inetd restart
13:51
er, sudo /etc/init.d/inetd restart
13:51
<ltsppbot>
"mfc_alpha" pasted "my dhcpd.conf" (22 lines) at http://pastebot.ltsp.org/450
13:52
<mfc_alpha>
no, he still refuse the connection
13:53
<ltsppbot>
"mfc_alpha" pasted "my ifconfig" (28 lines) at http://pastebot.ltsp.org/451
13:54
<mfc_alpha>
( good idea the pastebot! :) )
13:54
<Gadi>
hmm.. well, the issue seems to be inetd refusing to connect you
13:55
<mfc_alpha>
:(
13:55
:'(
13:56sepski has quit IRC
13:56
<mfc_alpha>
a idea of the reason ?
13:56
<Gadi>
do you have any thing special in /etc/hosts.allow or /etc/hosts.deny?
13:57
<mfc_alpha>
in hosts.allow i have
13:57
nbdrootd: ALL: keepalive
13:58
and nothing in /etc/hosts.deny
13:59
<Gadi>
hmm thats right
13:59
how about: lsmod|grep nbd
14:00
<mfc_alpha>
ha! no output!
14:00
<Gadi>
there ya go
14:00
sudo modprobe nbd
14:00
actually, maybe thats not it
14:00
<mfc_alpha>
and /etc/init.d/inetd restart and restart the client?
14:00
<Gadi>
well, try
14:01
you shouldnt need nbd if ur the nbd server, I dont think
14:01
hmm...
14:01
worth a shot tho
14:01
<mfc_alpha>
:'( not working....
14:01
<Gadi>
hmmm
14:02
sudo netstat -anp|grep 2000
14:02
<ltsppbot>
"mfc_alpha" pasted "the error screen" (13 lines) at http://pastebot.ltsp.org/452
14:02
<mfc_alpha>
i get : unix 2 [ ] DGRAM 20003 6158/xinetd
14:02
<cyberorg>
you dont need nbd module loaded on server
14:03
<Gadi>
sorry: sudo netstat -anp|grep :2000
14:03
<mfc_alpha>
nothing!
14:03
<Gadi>
do you have xinetd installed by any chance?
14:03
<mfc_alpha>
i will check it:D
14:04
yes... and the last version said apt
14:04
<Gadi>
thats the problem
14:04
do you use xinetd?
14:04
if you can: apt-get remove xinetd
14:04
then: /etc/init.d/inetd restart
14:04
<mfc_alpha>
I don't think i use it
14:04
<Gadi>
and you should be fine
14:05
(also make sure xinetd processes are dead
14:05
<mfc_alpha>
ho! apt-get remove xinetd want to remove ltsp-server!
14:05
<Gadi>
do it
14:06
then reinstall ltsp-server
14:06
<mfc_alpha>
ok!
14:06
<Gadi>
(your chroot should be safe
14:07
<mfc_alpha>
/etc/init.d/inetd restart bash: /etc/init.d/inetd: Aucun fichier ou répertoire de ce type
14:07
taht's mean: inetd : nor file or repertory found
14:08
<Gadi>
apt-get install ltsp-server-standalone
14:08
that should take care of everything
14:08
<mfc_alpha>
yes, that's already done
14:08
<Gadi>
do it again
14:09
<mfc_alpha>
yes, i do it after the apt-get remove xinetd
14:09
<Gadi>
ltsp-server or ltsp-server-standalone?
14:09
<mfc_alpha>
the standalone one
14:09
<Gadi>
hmm
14:10
<mfc_alpha>
dpkg -reconfigure ltsp-server-standalone?
14:10
<Gadi>
ah
14:10
no
14:10
<mfc_alpha>
ok :D
14:10
<Gadi>
do: apt-get install ltsp-server
14:11
(since xinetd took that out)
14:11
<mfc_alpha>
already install...
14:11
:(
14:11
<Gadi>
apt-get install openbsd-inetd
14:11
<mfc_alpha>
already installed and the last version
14:12
<Gadi>
ah
14:12
duh
14:12
im sorry
14:12
its: /etc/init.d/openbsd-inetd restart
14:12
<mfc_alpha>
:D
14:12
ok!
14:13
and that's working!
14:13
Thank a lot gadi :D
14:13
<Gadi>
np
14:13
<mfc_alpha>
you'are my guru geek ;)
14:13
<Gadi>
aw, shucks....
14:13
<mfc_alpha>
:D
14:13
<Gadi>
mfc_alpha: is that french?
14:13
<mfc_alpha>
you are in the dev team?
14:14* Gadi nods
14:14
<Gadi>
im the pain in the butt one
14:14
:)
14:14
<mfc_alpha>
yes i am french... but not this pseudo
14:14
You will i recognize my accent :D
14:15
<Gadi>
mfc_alpha: heh
14:15
<mfc_alpha>
ho sorry i don't get "butt", what does it mean?
14:15* Gadi needs to improve his french - lots more french speakers in this channel lately
14:15
<mfc_alpha>
:D
14:16
<Gadi>
butt = what you sit on
14:16
:)
14:16
<mfc_alpha>
ok :D
14:16
But it's very nice to you to help people like that!
14:16* Gadi took spanigh in high school - lo siento
14:16
<Gadi>
er, spanish
14:16
<mfc_alpha>
So thank to everybody on the channel :D
14:17
<cliebow_>
8~)
14:17
<Gadi>
rien de tu - or something
14:17
right?
14:17
<mfc_alpha>
are you English?
14:17
:D
14:17
near :D
14:17
<Gadi>
heh
14:17
thats why I didnt take french
14:17
<mfc_alpha>
it's "de rien"
14:17
<Gadi>
spelling is never the same as how it sounds
14:17
:)
14:17
<mfc_alpha>
:)
14:18
that's why i first take German
14:18
:D
14:18
<Gadi>
heh
14:19
<mfc_alpha>
and , is it's not too private, what are you doing in life?
14:19
i mean, what kind of work?
14:19
IT i suppose... :)
14:19
<Gadi>
ah, I was going to say "trying to find my way - maybe the next leap will be the leap home"
14:19
but, that doesnt make any sense
14:19
www.thesymbiont.com
14:20
that's us - Symbio Technologies
14:20
we develop technology based on all this great stuff
14:20
:)
14:20
<mfc_alpha>
that's why you know so much about light client :D
14:20
<Gadi>
yeah - kinda in the business
14:20
:)
14:21
but, Im the only Symbio guy in the group
14:21
the rest of the dev team does their own thing
14:21
<mfc_alpha>
and do you know all the other guy of the group?
14:21
<Gadi>
some work for canonical, some actually have day jobs
14:21
:)
14:22
well, not all 74 folks in the channel at the moment
14:22
<johnny>
i'd like a job hacking on ltsp..
14:22
that'd be fun
14:22
<Gadi>
but, a group of us get together at least once a year in person
14:22
<mfc_alpha>
ho cool :D
14:23
even working for the open community, it's must be fun :D
14:23
<Gadi>
fun and rewarding
14:23
<mfc_alpha>
yep :D
14:24
<Gadi>
and you?
14:24
<mfc_alpha>
ok, so i will enjoy my client and certainly make a document for ubuntu-fr.org
14:24
<Gadi>
ou est tu trabajo?
14:24
:)
14:24
<mfc_alpha>
:D
14:24* Gadi says in frenish
14:24
<mfc_alpha>
I am student
14:24
and for the moment I am in Cork
14:25
in Erasmus program
14:25
lot of fun :D
14:25* Gadi smiles and nods - and has no clue what that means
14:25
<Gadi>
but, judging from the excellent wines, Im sure france has a lot of folks in cork
14:25
:)
14:25
<mfc_alpha>
ho, you may already know it, but the "linux magazine" in france publish a article on ltsp
14:26
<Gadi>
ah, I never said I could read
14:26
:)
14:26
<lns>
Gadi, you work at Symbio?
14:26
<mfc_alpha>
:D
14:26
<Gadi>
lns: depends - who's asking? ;)
14:26* Gadi hides under desk
14:26
<lns>
A customer of yours? =p
14:26
<mfc_alpha>
Yes, too many french in Irlande.... I don't speak enough english :D
14:27
<Gadi>
lns: talk to me
14:27
<mfc_alpha>
(erasmus is a program of internationnal student exchange)
14:27
<Gadi>
ah! Cork, Ireland
14:27
<lns>
Well, almost a customer of yours - I've been talking with Lew Tischler about getting some of your units to test out
14:27
<Gadi>
ah, cool
14:27
Lew is a good guy
14:27
<lns>
Never got around to getting one to test w/ltsp, but i guess i could just straight-up ask you if they work in gutsy or not ;)
14:28
<Gadi>
well, its my job to make them work
14:28
:)
14:28
<lns>
nice!
14:28skipper has joined #ltsp
14:28
<lns>
=) that's so cool.
14:28
<Gadi>
more specifically with our own products which are based on LTSP
14:28
but, even so
14:28
<lns>
small thin-client world
14:28
<Gadi>
:)
14:28
<mfc_alpha>
I can now testify that ltsp is working with gutsy :D
14:28
<lns>
mfc_alpha, lol
14:29
<skipper>
I am back...I had the problem with the thin clients that do not give my an X window
14:29
<lns>
Gadi, do you guys use General Software BIOS in SYM1112 ?
14:29
<skipper>
I seem to get a Busybox prompt on every thin-client
14:30
<Gadi>
we do, and I know ur gonna ask about the amd driver (which we have worked so hard to get fixed in gutsy) :)
14:30
<lns>
;)
14:30
<Gadi>
we not only have it working - but have it producing 1680x1050 widescreen resolution :)
14:30
<mfc_alpha>
skipper, have you xinetd install?
14:30
<lns>
oooo!! spicy
14:30
<cliebow_>
skipper:what distro..
14:31
<Gadi>
lns: its been the subject of a lot of dev work
14:31
:)
14:31
specifically bec the amd devs aren't aloud to help us officially
14:31
<lns>
Gadi, i saw your products after being referred to Synertron Tech - don't know if you know them, their thin-clients look exactly like yours
14:31
<Gadi>
(unless we are OLPC)
14:31
<skipper>
I am running edubuntu 7.10 from an amd64 server with all thin clients being i386
14:31
<lns>
but their tc's seem to be horribly broken
14:31
<Gadi>
lns: our value-add is not so much in the thin client, its our boot appliance that gives it life
14:32
remember, in our world, thin clients are dumb
14:32
<lns>
Gadi, Yeah...it's a slow road to openness, but it seems to be working so far.. =)
14:32
Gadi, what are the boot appliances based on?
14:32
<Gadi>
pixie dust
14:32
:)
14:32
<lns>
lawlz. =p
14:32
<Gadi>
jk
14:32
<mfc_alpha>
what irc client are you using?
14:33
<Gadi>
for the longest time, a very modified LTSP 4.1
14:33
we are releasing an LTSP5 (also modified) based one this spring
14:33
<mfc_alpha>
ok, I have to go
14:33
<Gadi>
but, a lot of that is transparent
14:33
<mfc_alpha>
So thank everybody
14:34
<Gadi>
most of our customers use Windows or Citrix
14:34
:)
14:34
<lns>
I might be interested in checking those out.
14:34
<mfc_alpha>
Gabi, special thanks and go luck for the futur!
14:34
<Gadi>
I might be interested in having you check them out
14:34
:)
14:34
<lns>
=p
14:34
<Gadi>
mfc_alpha: np
14:34
come again
14:34
<mfc_alpha>
skipper, good luck to you ;)
14:34
<lns>
Gadi, what are the specs? how many clients can it handle?
14:34
<mfc_alpha>
ok ;)
14:34
++
14:34
<lns>
maybe i should just check the site. =p
14:34
<Gadi>
lns: do me a favor and email me
14:34mfc_alpha has quit IRC
14:35
<Gadi>
I prolly wont be able to get back to you today, but will draft an extensive email first thing monday
14:36
<skipper>
Can someone talk to me about my problem?
14:36
My system worked fine until I upgraded it to edubuntu 7.10
14:37
<lns>
skipper, you need to tell us what errors are coming up and give us more details
14:37
<Gadi>
skipper: whats it doing? (or not doing)
14:38
<cliebow_>
Gadi:he is dropped to busybosx
14:38
more or less
14:39
<Gadi>
skipper: what distro?
14:39
oh, sorry
14:39
edubuntu
14:39
heh
14:39* Gadi should drink more
14:39
<skipper>
As the thin-client loads, it goes through the usual stuff and appears to be doing fine, except at the last minute it stops at a Busybox prompt. The message at this point is "Target filesystem doesn't have /sbin/init"
14:39
<cliebow_>
8~)
14:39
<Gadi>
skipper: do you have xinetd installed?
14:39
dpkg -l xinetd
14:40
<skipper>
on the server or client?
14:40
<cliebow_>
server
14:40
<Gadi>
yeah - what he said
14:40
:)
14:40
<skipper>
Do I just run that command?
14:40
<Gadi>
yes
14:41
at the terminal
14:41
<skipper>
apparently not...what do I do?
14:42
<Gadi>
skipper: no, thats a good thing
14:42
what do you get when you do: sudo iptables -L
14:43
<skipper>
I had to run the ltsp-build-client to get the i386 system installed
14:43
<cliebow_>
suppose he has an elderly build-client?
14:43
<Gadi>
skipper: sudo apt-get install ltsp-server-standalone
14:44
then, sudo rm -rf /opt/ltsp/i386
14:44
and: sudo ltsp-build-client
14:44
also, make sure that: dpkg -l ltsp-server
14:44
<lns>
skipper, remember to do 'sudo ltsp-build-client -a i386'
14:44
(i think it's -a)
14:44
<Gadi>
returns a version of 5.0.39
14:44
<cliebow_>
skipper:build-client may take quite a while
14:46
<skipper>
OK I will try all of that, wish me luck!
14:46
<Gadi>
skipper: good luck
14:46
<lns>
skipper, remember to use --arch i386
14:46
<cliebow_>
good luck..happy haunting
14:47
<lns>
with ltsp-build-client
14:47
good luck
14:48
<skipper>
I ran the ltsp-server-standalone and was told it is the latest version...now what
14:48
<vlt>
Before using LTSP our local http server could see the source IP and from which desk a request came from. So it could do magic things like letting the right phone ring on a callback click ... Now obviously every request comes from the same IP. Has anyone an idea how to tell the http server where the request comes from?
14:49
<cliebow_>
get rid of your old /opt/ltsp/i386
14:50
<vlt>
The users authenticate to apache with the same username as they login to ltsp.
14:51
<Gadi>
vlt: check if "w" works
14:51
or who
14:51
<vlt>
Can I run `who` or similar ...
14:51
<Gadi>
or: last -a |grep still
14:52
<vlt>
Gadi: `w` didn't show me the clients when using ldm and ssh ... haven't tested with XDMPC yet.
14:52
<Gadi>
should with XDMCP
14:52
with ldm, we lack the script to update utmp
14:52
its on the TODO list
14:52
:)
14:52
<vlt>
What's utmp?
14:52
<lns>
Gadi, that irked me for the longest time...why 'w' didn't show ltsp users. =p
14:52
<Gadi>
thats what who looks at
14:53
utmp/wtmp
14:53
yeah, well
14:53
actually, it may work in gutsy
14:54
nah, prolly not
14:54
I forget
14:54* Gadi needs to check
14:54
<cliebow_>
weekend coming Gadi!
14:54
<Gadi>
last may work
14:54
<lns>
i think it actually does in gutsy
14:54
<Gadi>
but only log the sentinel connection
14:55
yeah, thats right
14:55
I think
14:55
it works bec of the sentinel
14:55
which keeps a bash connection open
14:55
and bash update utmp/wtmp
14:55
cliebow_: not soon enough
14:55
<cliebow_>
sounds like a Dr. Who
14:56
character..
14:56
<Gadi>
gah! its 4PM already.
14:56* Gadi has to get going before he turns into a pumpkin
14:56
<cliebow_>
heh..
14:56loather-work has quit IRC
14:56
<vlt>
(10 pm)
14:57
<Gadi>
sorry -9 PM UTC - so universal it inaccurate for most of the world
14:57
:)
14:57
<lns>
lol
14:57
take it easy Gadi
14:57
<Gadi>
u2
14:57
good weekend all
14:57
<cliebow_>
nite Gadi!!
14:58
8~)
14:58
<skipper>
I am doing another build for the i386 client
14:59
What does "dpkg -l ltsp-server" do?
15:00
<cliebow_>
dpkg -l lists all packages
15:00
dpkg -l ltsp-server gives you info on that package
15:00
but dont quote me
15:00
<skipper>
So what should I se, just a list of packages?
15:00
<lns>
skipper, yes
15:00
if you're trying to see if ltsp-server-* is installed, do a 'sudo dpkg -l | grep ltsp-server'
15:01
that's what i do anyway
15:01
<skipper>
Ok
15:03
I got ltsp-server 5.0.39 and ltsp-server-standalone 5.0.39
15:03
<lns>
that's a good thing(tm)
15:04
<cliebow_>
skipper..so to build a new chroot run sudo ltsp-build-client
15:04
assuming you tossed or set aside the old one
15:05
<lns>
skipper, cliebow_ with --arch i386!!
15:05
<skipper>
Well when my thin client start loading they look fine, they get assigned addresses and seem to be going along until the final message I indicated "Target5 filesystem doesn't have /sbin/init"
15:05
<cliebow_>
oh yeah..guess that isnew..
15:06
<skipper>
I am running the ltsp-build-client --arch=i386 now
15:06
<lns>
skipper, not sure if the = will work
15:07
<cliebow_>
must have defaulted to that before...
15:07
<skipper>
That is what I have been using
15:07
<lns>
skipper, you said you had an amd64 server?
15:07
<skipper>
Roger that
15:07
<lns>
skipper, the ltsp-build-client defaults to the server installation arch
15:07
<cliebow_>
ahh-hahh
15:08
<skipper>
what does that mean
15:08
<cliebow_>
you would need amd64 clients
15:08Gadi has left #ltsp
15:08
<skipper>
that is why I am running the ltsp-build-client for
15:08
<lns>
unless you use '--arch i386' when ltsp-build-client of course.
15:08
<cliebow_>
if you did not specify arch
15:09
<lns>
skipper, ltsp-build-client creates the filesystem that the CLIENTS use to boot with
15:09
<skipper>
Well it has finished and It did install /opt/ltsp/i386
15:09
<lns>
ok
15:09
then you should be golden
15:09cliebow_ has quit IRC
15:09
<skipper>
Well I will reboot and give it a try, see you on the other side
15:09skipper has quit IRC
15:12skipper has joined #ltsp
15:13
<skipper>
I am back...All four of my thin-clients have the same Busybox text prompt. No windows!
15:15
<lns>
skipper, well if it's giving you the /sbin/init issue still...
15:15
<skipper>
It is
15:15
<lns>
it's not correctly mounting / xferring the filesystem, as /sbin/init is one of the first files read
15:15
at least as far as i can imagine
15:15
so there's something going on there
15:16
<skipper>
I with you so far...
15:16
<lns>
skipper, you did reboot the server after the gutsy upgrade yes?
15:16
<skipper>
Yep
15:16
<lns>
have you checked /var/log on the server for clues?
15:16
particularly in syslog or messages..?
15:16
<skipper>
The thin clients all seem to get the proper addresses assigned
15:17
No, but I will.. is that the location?
15:17
<lns>
/var/log is where your logs are stored
15:18
<skipper>
I see that, which one do I want?
15:18
<lns>
check daemon.log, syslog, messages
15:20
<skipper>
Looks like it is still trying to send the amd64 file
15:20
<lns>
skipper, ok
15:20
if that is the case
15:20
do it all over - do the following
15:20
sudo rm -rf /opt/ltsp
15:21
sudo ltsp-build-client --arch i386
15:21
<skipper>
I have done this twice, what is going to be different?
15:22
<lns>
skipper, i have no idea
15:22
besides removing the /opt/ltsp/images dir as well
15:22
which might be keeping ltsp-update-image from updating
15:22
but i would think it should anyway
15:22
try just doing that if you want - sudo ltsp-update-image
15:23
i gotta run though, good luck. Damn these non-LTSP customers of mine, always wanting help with their XP and their email... blah I say!
15:23
<skipper>
Thanks anyway
15:24abadger1991 has joined #ltsp
15:24
<lns>
skipper, also verify in your dhcpd.conf file it's passing the correct stuff. the upgrade really should have taken care of it, but going over the processes that happen while booting might give you a clue.
15:25
whilst giving you a very good grasp of the boot process
15:25
<skipper>
I did make the changes necessary in dhcpd.conf
15:29skipper has quit IRC
15:31abadger1999 has quit IRC
15:32abadger1991 has left #ltsp
15:32abadger1999 has joined #ltsp
15:37skipper has joined #ltsp
15:38moquist has quit IRC
15:38
<skipper>
I have a question? What tells the thin client which image to load?
15:39
Is it dhcpd.conf
15:47
<vlt>
Hello. Another "Before switching to XDMPC ..." question: ... I could assist the users by running `x11vnc -display :6` on the client. Now running them with "SCREEN_07=startx" I can't start x11vnc anymore. Any idea?
15:50
... Or is there an easier way now that the clients don't do "ssh -X" anymore?
15:51skipper has quit IRC
15:58mhterres has quit IRC
15:59
<vlt>
How can I find out on which $DISPLAY X is running?
16:04bobby_C has quit IRC
16:20jammcq has quit IRC
16:29moquist has joined #ltsp
16:30vagrantc has joined #ltsp
16:32nicoAMG has quit IRC
16:37Egyptian[Home] has quit IRC
16:50mikkel has quit IRC
17:11loather-work has joined #ltsp
17:23ogra_cmpc has joined #ltsp
17:34ogra_cmpc has quit IRC
17:39zodman has quit IRC
17:41ogra_cmpc has joined #ltsp
17:48ogra_cmpc_ has joined #ltsp
17:49ogra_cmpc has quit IRC
17:50K_O-Gnom has quit IRC
18:02lns_ has joined #ltsp
18:03
<lns_>
This is a shot in the dark, but has anyone gotten sound to work on an LTSP workstation while using terminal services into a Windows machine (virtualized on the same ltsp server) ?
18:08lns_ has quit IRC
18:20ogra_cmpc_ has quit IRC
18:44ogra_cmpc has joined #ltsp
18:47staffencasa has quit IRC
18:49cliebow has joined #ltsp
19:09ogra_cmpc has joined #ltsp
19:27jammcq has joined #ltsp
19:28
<jammcq>
hey all
19:28* vagrantc waves
20:02
<cliebow>
hey!!!
20:05ogra_cmpc has quit IRC
20:07cliebow has left #ltsp
20:10ogra_cmpc has joined #ltsp
21:19lns-eee has joined #ltsp
21:19lns_ has joined #ltsp
21:21
<lns_>
hey why does X crash hard with the whole Firefox Pixmap issue, when ltsp is supposed to have a network swap on the server?
21:22ogra_cmpc has quit IRC
21:39lns_ has quit IRC
21:39lns-eee has quit IRC
21:51vagrantc_ has joined #ltsp
22:04ogra_cmpc has joined #ltsp
22:04vagrantc has quit IRC
22:25Ryan52_ has joined #ltsp
22:26RyanRyan52 has quit IRC
22:26Ryan52 has quit IRC
22:26RyanRyan52 has joined #ltsp
22:27Ryan52_ has quit IRC
22:28Ryan52 has joined #ltsp
22:28topslakr_ has quit IRC
22:30Ryan52 has quit IRC
22:31Ryan52 has joined #ltsp
22:34topslakr_ has joined #ltsp
22:38Joris_ has joined #ltsp
22:54vagrantc_ has quit IRC
22:54Joris has quit IRC
23:07
<sutula>
lns: Yes, RE your question 5 hrs ago
23:11
lns: IIRC, there were a bunch of hurdles: a) get sound working at all, b) enable sound under the Windows terminal services (there's a checkbox somewhere that's off by default), c) use the right rdesktop option to enable remote audio, and d) use "padsp rdesktop"
23:11* sutula could look all of that up sometime, but needs to do non-computer work now...later guys
23:13* sutula finds some of the magic: exec padsp rdesktop -u $USER -g "$resolution" -a 16 -r sound:local windows
23:13
<sutula>
...where "windows" is a hostname
23:21joebaker has joined #ltsp
23:25
<MacIver>
sutula: there is a patch for rdeskop to use alsa
23:42
<lns>
sutula, MacIver, Thank you for that info! The interesting bit is, I cannot even get this far (yet) because there is no sound card in the host system - for whatever reason, VMWare relies on hardware audio to emulate the guest OS's audio. So I need to do that first.
23:43
I wish it would just emulate a common sound interface..would have made it much easier on me anyway. =p
23:43
<MacIver>
lns: you could try running vmware server psadsp :-p
23:43
er padsp
23:44* lns gets the image of the last playing card stacked on top, collapsing the whole card castle. ;)
23:46
<lns>
hmm, i wonder though.
23:46
that would be so awesome if it did work (stable at that)
23:47
<MacIver>
after all the layers you'll be lucky to not have a several second delay ;-)
23:47
<lns>
that is true
23:47
i've already got enough of those!
23:48
but the vm in ubuntu is much better than 35 students on a PII NT4 Terminal Server
23:48
<MacIver>
would be nice if java used pa or alsa natively
23:48
<lns>
heh
23:48
yeah have fun with the browser plugin battle
23:49
<MacIver>
i use mostly jnlp
23:49
<lns>
ah
23:50
how is java doing performance wise with ltsp?
23:50
gfx, etc
23:50
<MacIver>
lns: it's decent, once you set the correct options
23:50
about like any other native program
23:50
<lns>
nice
23:51
I wish there was a java layer for emulating any app in any other OS
23:51
<MacIver>
i've been deploying thing clients in a manufacturing environment
23:51
er thin!
23:51
<lns>
what do you use them for?
23:52
<MacIver>
workers use them to see what to work on next, and to barcode scan items through for tracking
23:53
<lns>
and you use ltsp?
23:53
<MacIver>
yup, works nicely
23:53
<lns>
what OS?
23:53
<MacIver>
here's the java hack: http://scribere.no-ip.org/LTSP#Installation
23:53
edubuntu :-D
23:53
<lns>
nice ;)
23:55
MacIver, i've seen that page before
23:56
<MacIver>
lns: lol, yeah i think i remember you now
23:56
<lns>
that's where i got the gnome-watchdog and i talked to you about it....
23:56
heh
23:56
still haven't tried it out
23:56
it'd be nice to see 90% of that stuff get integrated by default
23:56
they're all little annoying thigns to me to (like the monitor staying on)
23:56
<MacIver>
yeah, it's good right now but definitely room for improvement