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


Channel log from 9 November 2007   (all times are UTC)

00:35fox2k has joined #ltsp
00:35sadmin has joined #ltsp
00:35
<sadmin>
hi all
00:36
how i enale usb and cdrom in ubuntu gutsy
00:37
<johnny_>
good question :)
00:37
working on that
00:37
and autologin
00:37
i can't seem to find the proper docs tho
00:39
sadly i can only work on the machines at night
00:40
<sadmin>
johny_ i hear its enabled by default
00:40
<johnny_>
auto login?
00:40
<sadmin>
i can plug usb but it wont picked
00:40
do i need to do any thing on lts.conf
00:41
<johnny_>
i assume that this localdev tutorial is still semi relevant
00:41
on the wiki
00:41
to at least debug why
00:41
<sadmin>
hum
00:41
<johnny_>
https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/158989
00:41
that's the bug that is the same problem i'm having
00:43
related to localdev that is
00:43
doesn't solve my autologin problem tho :(
00:46BadMagic has quit IRC
00:46
<johnny_>
is that the same problem you're having ?
00:47User-1 has joined #ltsp
00:47daya has quit IRC
00:48
<User-1>
Does anyone know anything about LTSP? I am in the middle of install and fail to start DHCP. Anyone can help please?
00:48
<johnny_>
sorry, i don't use the packaged dhcp
00:48
i use dnsmasq for my ltsp dns
00:48
err dhcp
00:49
<User-1>
is dhcp needed or can I let my router switch assign IP?
00:49
<johnny_>
a dhcp server is needed, one that can hand off the chroot
00:49
err hand off the kernel image
00:49
<User-1>
I see
00:50
<johnny_>
or rather tell where the tftp server is
00:50
uggh
00:50
<User-1>
anyone who can help me please? I am not experienced with linux and LTSP
00:50
<johnny_>
if you're using some off the shelf router without custom firmware, you prolly can't use it
00:50
<sadmin>
ok
00:50
not i wont see any error
00:50
either
00:50
<johnny_>
not when you switch to the console?
00:51
cuz that's where i see the errors
00:52
<User-1>
is there a way to understand why when I run /etc/init.d/dhcpd start it fails?
00:52
<johnny_>
User-1, look at the logs in /var/log ?
00:52
i think you'll have better luck if you come here during a normal day in either the US or Europe
00:52
so.. in like 2 hours i guess
00:52
at the very least
00:52
i've been here for hours
00:53
pretty dead
00:53
<User-1>
any file in particular to read in /var/log?
00:53
<johnny_>
messages prolly
00:54
if you can't diagnose it yourself, maybe you should setup edubuntu, and follow their recommended wiring and setup guide
00:54
<User-1>
I get: "Nov 9 07:54:17 localhost dhcpd: Configuration file errors encountered -- exiting"
00:55
If you did not get this software from ftp.isc.org, please
00:55
get the latest from ftp.isc.org and install that before
00:55
requesting help.
00:55
what should I do?
00:55
<johnny_>
wait
00:55
<User-1>
sure
00:55
<johnny_>
or install edubuntu :)
00:55
i don't use that dhcp so i can't really help you with that
00:55
<User-1>
ok, I will ask in centos
00:56
does UBUNTU offer any good server distro?
00:56
<johnny_>
really tho.. i don't think i'd ever use a redhat distro
00:56
if all you plan on doing with this box is ltsp
00:56
use edubuntu
00:56
it's meant for ltsp
00:57
<User-1>
ok, i will tyr
00:57
<johnny_>
if edubuntu would have existed when i set this box up, i'd be using it
01:04
where the hell did the docs for this go
01:04
:(
01:04* johnny_ tris to think of new terms
01:08
<User-1>
I got my issues fixed and have my server (centos) ready to run LTSP I believe
01:08
I wish toa sk
01:08
ask a question, no.
01:08
On the client, I do have a PC with a network boot NIC. What do I need in order to let the client boot?
01:09
Can I just use my NIC or do I need a software to boot off?
01:10
<johnny_>
depends on if the nic has pxe boot rom alrady
01:10
already*
01:10
if it does, then you don't
01:10
if it offers network boot somewher ein the bios, then you don't
01:11
if neither, then yes.. i use etherboot
01:11
<User-1>
ok, let me check
01:15
<johnny_>
i meant that i use etherboot on the floppies of the 4 terms, it could also be run from hard disk or any other bootable media
01:16sadmin has quit IRC
01:18vagrantc has joined #ltsp
01:19
<User-1>
just a quick question (Yes, I have boot agent on my nic.) Do I have anything to open with my firewall?
01:19
<johnny_>
who knows
01:19
it depends on your setup
01:19
<User-1>
I ask this because my PC found my server but it faild at tftpd
01:19
<johnny_>
look up howtonat
01:19
with ltsp
01:19
i saw that doc, but didn't read it
01:20
<User-1>
which document?
01:20
<johnny_>
howto nat ltsp
01:20
you'll find it
01:20
<User-1>
ok
01:24
<vagrantc>
User-1: you'll need to make sure that tftp, DHCP, and NFS or NBD related ports are allowed if you have any firewalling on the LTSP server.
01:25fox2k has quit IRC
01:25daya has joined #ltsp
01:26
<daya>
channel, I follow the lower step in the wiki, http://wiki.debian.org/LTSP/Howto, but the sound is still not working
01:26
in my clinet syste, do i need some extra configuration for pulse audio for making it to work in client,
01:27
<vagrantc>
daya: does your thin client detect sound?
01:28
<daya>
vagrantc, no, its get played in the server,
01:29
<vagrantc>
daya: look at /usr/share/doc/ltsp-server/README.Debian.sound
01:29
<daya>
vagrantc, ok
01:29
<User-1>
I am getting this error from my PC (booting with Managed PC Boot Agent (MBA)): PXE-E32: TFTP open Timeout
01:29
What does it mean?
01:30
<vagrantc>
User-1: tftp is what is used to download the boot loader, which then downloads the operating system
01:30
<User-1>
correct
01:31
<daya>
vagrantc, one question please, do I need to do all the step in the readme file although I follwed the lower step of thewiki,
01:31
<User-1>
why do I get this error?
01:31
<johnny_>
hmm.. i still can't find any docs related to autologin in gutsy ltsp
01:31
i had it working with a hacked python version of ldm from gomi
01:31
<vagrantc>
User-1: so ... sounds like either your tftp server isn't configured properly, you have a firewall blocking those ports ... or something else that's stopping tftp from working
01:31
<johnny_>
but the paramters don't work anymore
01:32
<User-1>
vagrantc, I believe it could be firewall.
01:32
vagrantc, I use centos. How to find out what to do or how to add ports for the firewall?
01:32BadMagic has joined #ltsp
01:32
<vagrantc>
User-1: i don't use centos, so i have no idea.
01:32
<User-1>
vagrantc, [root@localhost log]# /etc/init.d/xinetd start
01:32
Avvio di xinetd: [ OK ]
01:32
the service is started
01:33
vagrantc, are ports I can disable from my firewall?
01:33
<vagrantc>
User-1: is xinetd configured to start a tftpd ?
01:33
User-1: you need udp port 69
01:34
<User-1>
how to find out?
01:34
<johnny_>
all i see is people talking about the feature being added, but nobody talking about how to enable it
01:34
<vagrantc>
!tftp
01:34
<ltspbot>
vagrantc: Error: "tftp" is not a valid command.
01:34
<vagrantc>
johnny_: what variables are you setting ?
01:35
!troubleshooting
01:35
<User-1>
vagrantc, from ltspcfg I get this" tftpd Yes Yes Yes Has '-s' flag"
01:35
<ltspbot>
vagrantc: "troubleshooting" is http://wiki.ltsp.org/twiki/bin/view/Ltsp/TroubleShooting
01:35
<johnny_>
LDM_USERNAME="hostname|"
01:35
LDM_PASSWORD="guest"
01:35
that's what i had working before
01:35
but those parameters are not in the official docs
01:35
<vagrantc>
User-1: see anything on the troubleshooting web page ?
01:35klausade has joined #ltsp
01:36
<User-1>
vagrantc, which file should I look to check if xinetd is configured to start a tftpd?
01:37
<johnny_>
damn.. it's almost 3am.. i haven't even done any of my paid work :( wtf :(
01:37
been too busy with my non-profit work :(
01:38
<User-1>
vagrantc, solved
01:38
it was port 69 that needed to be opened
01:38
from firewall
01:39
vagrantc, now, I am left to solve NFS issues I got now
01:39
<vagrantc>
johnny_: looking at the code, i don't *think* LDM supports the "hostname|" syntax ... i think it just copies the value
01:39
johnny_: but i'm not sure, my C is poor.
01:39
<johnny_>
hmm.. got a link to the src?
01:39
or did you have it downloaded
01:40
<vagrantc>
User-1: NFS uses *lots* of ports
01:40
<johnny_>
but the parameters are correct?
01:40
<vagrantc>
johnny_: parameters are correct, but i think you have to specify the username
01:41
<johnny_>
or fix the src
01:41
depending
01:41
<vagrantc>
well, sure.
01:41
<johnny_>
does that gideon romm fellow ever come in here?
01:41
<vagrantc>
gadi
01:41
yeah, gadi's around pretty often
01:42
<User-1>
vagrantc, This is the error on the client I get: Failed to mount the root direcotry via NFS! .... Kernel panic - not syncing: Attempted to kill init!"
01:42
vagrantc, what do you suggest doing?
01:42
<johnny_>
ok, for now.. i'll hack it by machien
01:43
via the lts.conf
01:43
<vagrantc>
User-1: did you look at that troubleshooting page i mentioned earlier?
01:43
<johnny_>
and then i'll ask gadi if he wants the former feature enabled
01:43
sadly it's just duplication :(
01:43jvanrooyen has joined #ltsp
01:43
<vagrantc>
johnny_: i think something like that is a good feature, and i was talking to sbalneav about it a couple weeks ago... something related, anyways
01:44daya has quit IRC
01:44Q-FUNK has joined #ltsp
01:44
<johnny_>
hmm.. ok.. well guess tonight was wasted :(
01:44
<User-1>
vagrantc, here is a post of /var/log/message http://pastebin.com/m4da2a2bd
01:45
<vagrantc>
!pastebot
01:45
<ltspbot>
vagrantc: "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.
01:45
<johnny_>
after that.. i'll look into getting the local devices working again
01:45
where is the ldm src on the web vagrantc ?
01:45
<vagrantc>
all over the place :)
01:46
<johnny_>
i mean the versioned src
01:46
<vagrantc>
all over the place
01:47
it's maintained in bzr, which is a distributed revision control system. there's been very recent work to start making more upstream source repositories soon.
01:47
User-1: so, at any rate, can you mount the NFS volume from the server itself ?
01:47
<johnny_>
sure, but where is the release pulled from?
01:48
<vagrantc>
User-1: mount -o ro 127.0.0.1:/opt/ltsp /mnt
01:48
johnny_: currently, the release system is not fully established
01:49
johnny_: so there is, technically no release
01:49
<User-1>
vagrantc, this is what I have: http://pastebin.com/m2372b367
01:49
<johnny_>
what distro's version of src did you look at then ?
01:49
<vagrantc>
User-1: if you're not going to gigve me the information i asked, i'm not going to be able to help you.
01:50
<User-1>
vagrantc, thi info I gave you displays the mount list
01:50
<vagrantc>
johnny_: i looked at the debian branch, but it's very close to ubuntu.
01:50
<User-1>
vagrantc, is not this what you asked?
01:50
vagrantc, I get nfsd on /proc/fs/nfsd type nfsd (rw)
01:50
<vagrantc>
User-1: please run this command: mount -o ro 127.0.0.1:/opt/ltsp /mnt
01:50
<User-1>
sure
01:51
vagrantc, I get: mount: 127.0.0.1:/opt/ltsp failed, reason given by server: Permission denied
01:51
<vagrantc>
User-1: ok, good.
01:51
User-1: grep ltsp /etc/exports
01:52
<User-1>
vagrantc, # on: ven nov 9 07:36:28 2007, by the ltspcfg configuration tool. /opt/ltsp 192.168.0.0/255.255.255.0(ro,no_root_squash,sync) /var/opt/ltsp/swapfiles 192.168.0.0/255.255.255.0(rw,no_root_squash,async)
01:52
<vagrantc>
User-1: ps aux | egrep nfs
01:53
<User-1>
vagrantc, as being severla lines I posted the output here http://pastebin.com/m7e7d4e2b
01:53
<vagrantc>
User-1: there's also a pastebot for this channel.
01:54
!pastebot
01:54
<ltspbot>
vagrantc: "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.
01:54
<User-1>
vagrantc, ok, will do so, thks
01:55
<ltsppbot>
Someone pasted "# ps aux | egrep nfs root 3382" (11 lines) at http://pastebot.ltsp.org/342
01:55
<User-1>
vagrantc, here it is: http://pastebot.ltsp.org/paste
01:55
<vagrantc>
User-1: you don't have to tell me where it is, that's the ltsppbot 's job
01:56
User-1: anyways ...
01:56
<User-1>
vagrantc, sorry I did not get this part. When I post it don't I have to give you the url?
01:56
<vagrantc>
User-1: are all the ports that nfs and all related services open on your firewall?
01:57
<User-1>
here we are again. I believe all issues come from my firewall.
01:57
<vagrantc>
User-1: if you use pastebot.ltsp.org, ltsppbot will paste the URL automatically
01:57
<User-1>
I see
01:57
<vagrantc>
User-1: can you disable the firewall?
01:57
<User-1>
let me see howto.
01:57
<vagrantc>
at least for testing?
01:57* User-1 checking...
01:58
<vagrantc>
nfs uses lots of ports ... i don't know all the ones to tell you
01:58
<User-1>
vagrantc, I disabled it. Let me now try
01:58
<vagrantc>
although, if you can even mount from 127.0.0.1 ... unless your firewall is also blocking local access ...
02:00
<User-1>
vagrantc, thank you. My firewall was causing all these issues.
02:01
vagrantc, I am now at the login page. I should find out which ports to open for when I enable my firewall again. Any advice for this? Could it be written on the LTSP webpage?
02:01
<vagrantc>
ah good, because i don't know much about centos, or LTSP 4.x for that matter
02:02
User-1: don't know anything off the top of my head ... look around on the wiki
02:02daya has joined #ltsp
02:02
<User-1>
vagrantc, it works perfectly!
02:02
thank you!
02:02
<vagrantc>
User-1: http://wiki.ltsp.org/twiki/bin/view/Ltsp/FirewallPorts
02:03
i guess it wasn't as bad as i thought
02:03
ltspbot: learn firewall as http://wiki.ltsp.org/twiki/bin/view/Ltsp/FirewallPorts
02:03
<ltspbot>
vagrantc: The operation succeeded.
02:04
<vagrantc>
!firewall
02:04
<ltspbot>
vagrantc: "firewall" is http://wiki.ltsp.org/twiki/bin/view/Ltsp/FirewallPorts
02:04
<johnny_>
uggh.. blackscreen again
02:08
<vagrantc>
black screen?
02:09
not a grey screen?
02:16
!greyscreen
02:16
<ltspbot>
vagrantc: "greyscreen" is No login, and only a grey screen? See http://wiki.ltsp.org/twiki/bin/view/Ltsp/Troubleshooting-GrayScreen
02:18
<daya>
vagrantc, do i have to create asound.conf file manually,
02:18
<vagrantc>
daya: probably
02:19
<daya>
vagrantc, I have installed pulseaudio, but sound still not working,
02:19
I am trying it with totem player,
02:20
but now it also doesn't get played in the server also,
02:21
<vagrantc>
daya: you probably need to configure the sound system that totem uses to use ALSA
02:21
does it use gstreamer?
02:23
<daya>
yes , might be I am not sure of that,
02:23
<vagrantc>
when i tested sound, i used xine, alsaplayer, xmms and rhythmbox .... alsaplayer was the trickiest
02:23
<daya>
ok I use then, xmms,
02:24
<vagrantc>
xmms, if i remember correctly, i had to tell it to use alsa instead of oss
02:24
<johnny_>
that troubleshooting gray screen does not mention ldm, which works differently
02:24
<daya>
vagrantc, but when I use , sound doesn't came either in client nor i server,
02:24
<vagrantc>
johnny_: true true
02:25
<johnny_>
and it was working before i enabled autologin like
02:25
[wsname]
02:25
LDM_USERNAME="wsname" LDM_PASSWORD="guest"
02:25mistik1 has quit IRC
02:25
<vagrantc>
johnny_: can you disable autologin and try entering in that user and password ?
02:26
daya: when you use what ?
02:26
<johnny_>
yes, that worked
02:27mistik1 has joined #ltsp
02:27
<daya>
I have used xmms now, using alsa,
02:27
in the choice menu from the optin of the xmms pref.
02:28
<vagrantc>
daya: and you've configured /etc/asound.conf like it says in the README.Debian.sound file?
02:28
<daya>
vagrantc, do i need to edit asound.conf in chrooted file also,
02:28
<vagrantc>
daya: no
02:29
<johnny_>
ok vagrantc .. i'mma finally move my lts.conf out of my chroot and then update the image, and comment out the ws stuff
02:29
and try one more time
02:30
<vagrantc>
daya: dpkg --root=/opt/ltsp/i386 -l ltsp*
02:30
daya: dpkg --root=/opt/ltsp/i386 -l ltsp* | egrep ^ii
02:30
<johnny_>
silly ltsp-update-image should default to the only installed chroot
02:30* vagrantc has no fondness over ltsp-update-image
02:32
<daya>
vagrantc, http://ltsp.pastebin.org/7526
02:33
vagrantc, http://pastebin.com/m2a01e211
02:34
<vagrantc>
daya: dpkg -l ltsp* | egrep ^ii
02:35
daya: try pastebot.ltsp.org
02:35
<daya>
vagrantc, ok sorry
02:35
<vagrantc>
no need to re-send those ...
02:35
but for the next question
02:36
<ltsppbot>
"daya" pasted "root@nepalinux:~# dpkg -l ltsp" (6 lines) at http://pastebot.ltsp.org/343
02:36
<vagrantc>
ok.
02:37
daya: this is a standard debian etch installation?
02:37
<daya>
vagrantc, You mean My system,
02:37
vagrantc, yes, localised,
02:38sepski has joined #ltsp
02:38
<vagrantc>
daya: what do you mean by localised?
02:38
<daya>
vagrantc, I mean localisation in nepali language,
02:38
<johnny_>
vagrantc, i just commented out all the autologin stuff, i get a prompt and can login
02:39
<vagrantc>
johnny_: well, that's something
02:39
daya: so a lot of custom packages?
02:39
<johnny_>
so..
02:39
what next then ?
02:39
<vagrantc>
johnny_: figure out what's wrong with the C code?
02:40
<daya>
vagrantc, yes , But we use the repo from debian etch,
02:40
<johnny_>
vagrantc, but.. which copy :)
02:40
<vagrantc>
johnny_: probably the one you're using ... which is ... ubuntu gutsy?
02:40
<johnny_>
this is sad to see a reversing of the functionality :(
02:40
yeah.. but where ?
02:41
i'm not debian/ubuntu person really.. i use gentoo, but here at the store.. it's all ubuntu
02:41
<vagrantc>
http://packages.ubuntu.com/gutsy/misc/ldm
02:42
johnny_: there's a bzr branch at: http://bazaar.launchpad.net/~ubuntu-core-dev/ltsp/gutsy-ltsp/
02:42
<johnny_>
that's empty
02:42
<vagrantc>
johnny_: it's a bzr URL
02:42
bzr get URL
02:43
johnny_: but the first link i posted was a regularly old web browser URL
02:43
johnny_: at the bottom is a link to download the source code
02:44
http://packages.ubuntu.com/gutsy/misc/ldm
02:44
<johnny_>
yeah.. i'm at the first
02:44
oh.. you have to use bzr to see it ..
02:44
:(
02:45
<vagrantc>
daya: so, when you're logged in: echo $ESPEAKER ; echo $PULSE_SERVER
02:45
johnny_: there's also some way to browse code on launchpad ...
02:46
johnny_: http://codebrowse.launchpad.net/~ubuntu-core-dev/ltsp/gutsy-ltsp/files
02:46
gah. i got to get some sleep.
02:47
<johnny_>
aha.. thanks for the help tho vagrantc
02:47
<daya>
vagrantc,
02:47
sh-3.1$ echo $ESPEAKER
02:47
192.168.2.247:16001
02:47
sh-3.1$ echo $PULSE_SERVER
02:47
tcp:192.168.2.247:4713
02:47
sh-3.1$
02:47
vagrantc, I have taken it from client machine,
02:48
<vagrantc>
daya: ok, looks good.
02:48
daya: no idea what's wrong.
02:48
good luck, i'm getting some sleep.
02:49
<daya>
vagrantc,:0
02:49
vagrantc, thanks :),
02:49vagrantc has quit IRC
03:05daya has quit IRC
03:20Egyptian[Home] has joined #ltsp
03:21Egyptian[Home] has left #ltsp
04:00johnny_ has quit IRC
04:13plamengr has joined #ltsp
04:36plamengr has quit IRC
04:43rjune_ has quit IRC
05:10exodos has joined #ltsp
05:11
<exodos>
!past
05:11
<ltspbot>
exodos: Error: "past" is not a valid command.
05:11
<exodos>
!paste
05:11
<ltspbot>
exodos: Error: "paste" is not a valid command.
05:12
<exodos>
sbalneav: can you check this: http://pastebin.com/m50400bdf
05:12
i think thit is caused by your modifications to sabayon-apply
05:13Egyptian[Home1 has joined #ltsp
05:16fox2k has joined #ltsp
05:17
<exodos>
can anyone that knows python check http://pastebin.com/m50400bdf and say how can I fix it?
05:17
j #python
05:17
sry
05:20Guaraldo has joined #ltsp
05:52Joris_ is now known as Joris
06:10sepski has quit IRC
06:30cyberorg has quit IRC
06:34cyberorg has joined #ltsp
06:50rjune__ has joined #ltsp
06:51User-1 has quit IRC
07:08elisboa has joined #ltsp
07:22RiXtEr has quit IRC
07:34Nubae has joined #ltsp
07:43BGomes has joined #ltsp
07:45cliebow__ has joined #ltsp
07:46outofrang1 has joined #ltsp
07:48
<outofrang1>
Anyone have xorg.conf for Bondi iMacs? I think I've got blue and green iMacs.
07:49
<cliebow__>
outofrang: you mean just an xserver=??
07:49
<outofrang1>
no, the entire config.
07:50
xserver = ati, right?
07:50
<cliebow__>
i used i think xserver=fbdev
07:51
<outofrang1>
Does that just set the driver in xorg.conf or does that actually select a different pre-defined configuration?
07:52
I ask because goggle finds posts about altering the refresh to make the old iMacs work.
07:54
<cliebow__>
it creates an ltsp xf86cobfig on the fly...
07:55
prob there are many ways to skin the cat
07:56
<outofrang1>
At this point I'm trying to find a way that takes the fewest number of days. ;P
07:59ronalde_ has joined #ltsp
08:03
<outofrang1>
cliebow__: is XSERVER used by an init.d script? I'm not finding it when I grep /opt/ltsp/<arch>/etc for it.
08:04
<cliebow__>
you are using ltsp on it?? xserver goes in lts.conf..
08:05
<outofrang1>
Yes, I'm just trying to look for the scripts to get an understanding of how thing work.
08:07
<ronalde_>
We can't use usb disks on gutsy: all steps from https://wiki.ubuntu.com/DebugLocalDev check out ok; except for the last one: ssh -S /var/run/ldm_socket_vt7_192.168.0.254 192.168.0.254 "/usr/sbin/ltspfsmounter /tmp add". This results in: X connection to localhost:10.0 broken (explicit kill or server shutdown).Error: /tmp/.auser-ltspfs/usbdisk-sdb1 is not mounted
08:08ogra has joined #ltsp
08:09
<ronalde_>
ogra: We can't use usb disks on gutsy: all steps from https://wiki.ubuntu.com/DebugLocalDev check out ok; except for the last one: ssh -S /var/run/ldm_socket_vt7_192.168.0.254 192.168.0.254 "/usr/sbin/ltspfsmounter /tmp add". This results in: X connection to localhost:10.0 broken (explicit kill or server shutdown).Error: /tmp/.auser-ltspfs/tmp is not mounted
08:22Gadi has joined #ltsp
08:28
<cliebow__>
!g
08:28
<ltspbot>
cliebow__: "g" is Gadi!!!!!!!!!!!!!!!!!!!!!!!!
08:29redguy_work has quit IRC
08:39upro has joined #ltsp
08:40
<upro>
Hi everybody! This is a X resolution question: My server has a "normal" display (4:3), my cvlient has a 16:9 display. Everything on it looks "streched". How can I change the resolution on that display?
08:43
<Gadi>
morning, cliebow
08:43
upro: it depends if your client's video chip can support widescreen video modes
08:43
many don't
08:43
also, my guess is your client has 16:10 not 16:9
08:44
<upro>
Gadi: How can I find out this?
08:44
<Gadi>
most computer monitors are the former
08:44
what chip do you have?
08:44
<upro>
I'm not sure about that. The client is a HP
08:45
<Gadi>
well, in lts.conf, set: SCREEN_07=shell
08:45
<upro>
HP t5000
08:45
<Gadi>
then, on the client, switch to ctrl-alt-f7 on boot
08:45
and do an lspci
08:45
to see what video chip it is
08:45
<upro>
Gadi, wai, I have to switch it on...
08:45
<Gadi>
or actually,
08:45
look in /etc/X11/xorg.conf
08:46
to see what driver it uses
08:46
<upro>
Gadi: on xorg.conf on the client or the server?Iguess the clienthasno data?
08:46
<Gadi>
(you may need to set CONFIGURE_X=True in lts.conf as well)
08:46
client
08:46
this is all about the client
08:46
you could just as easily boot the client off a livecd
08:46
if it makes it easier for you
08:47
<upro>
Gadi: the client has no drives...
08:47
<Gadi>
usb?
08:47
;)
08:47
<upro>
usb, yes...
08:47
<Gadi>
anyhow, find out the video driver for the client
08:47jvanrooyen has quit IRC
08:47
<Gadi>
then google for it and widescreen xorg.conf
08:48
see what you get
08:48
:)
08:48
some drivers can be forced into non-native moddes
08:48
with modelines in the xorg.conf
08:48
note: widescreen support on thin clients as default modes is currently lacking across almost all mjor vendors
08:48
<upro>
Gadi: Dies evyr client has it's own xorg.conf?
08:49
<Gadi>
upro: every client has one generated on the fly
08:49
in LTSP
08:49Nubae has quit IRC
08:49
<Gadi>
in gutsy LTSP5, you will probably have to specify: CONFIGURE_X=True
08:50
because its version of Xorg will not need a xorg.conf by default
08:50
<upro>
Gadi: I upgraded to gusty yesterday, and this is the frst time I boot the client. It hangs after the login screen abd goes back to it after a while... I had this before but I don't remember what I did to it...
08:51
<Gadi>
upro: you should probably regenerate the chroot
08:51
<upro>
Gadi: How did I do this?
08:51
<Gadi>
sudo mv /opt/ltsp/i386 /opt/ltsp/i386.feisty
08:51
sudo ltsp-build-client
08:52
<upro>
Gadi: oh...
08:52
and then everything will be fine?
08:52
<Gadi>
well, not the widescreen stuff
08:52
but, the other everything :)
08:52
<upro>
biut the rest I guess? The login problem?
08:52
<Gadi>
upro: yes, probably
08:53burnerx has joined #ltsp
08:54
<upro>
Gadi: ok, this willtake a while. For the 16:9 where would I then put the settings for widescreen?
08:54
<Gadi>
upro: it depends on what is needed
08:54
but, it could be astrivial as an X_MODE_0 line in lts.conf
08:54
<upro>
Gadi: sounds complicated...
08:55
<Gadi>
or as complicated as a special static xorg.conf for those client (X_CONF= in lts.conf)
08:55sgonzalez has joined #ltsp
08:55
<Gadi>
yeah, widescreen can involve some playing
08:55
especially if you need to force the driver to do something it wasnt built for
08:56
but, find out what the driver is first
08:56
and then, you'll know ur options
09:02
<outofrang1>
Gadi: X_CONF is a custom xorg.conf file?
09:03
How does it relate to XF86CONFIG_FILE?
09:04* outofrang1 just posted wondering about this.
09:04
<Gadi>
outofrang1: they are the same (and there should be backwards compat in there for the var)
09:04
just changed the param name
09:04
to reflect, well X rather than XF86
09:05
;)
09:05
<outofrang1>
and it's relative to /opt/ltsp/<arch>/etc, correct?
09:06
<Gadi>
it is relative to /opt/ltsp/<arch>
09:06
iirc
09:06
no, you may be right
09:06
best to put an absolute path, tho
09:06
to be sure
09:06
:)
09:06
<outofrang1>
Is lts.conf parsed in a shell script?
09:06
<Gadi>
it is parsed in several
09:06
with getltscfg
09:07
<outofrang1>
I see. It's a binary -- no wonder I couldn't find where it did its work.
09:09
And then are things like XSERVER and X_HORZSYNC used directly by whatever bulids xorg.conf? I couldn't find those in any shell scripts, either.
09:10
<Gadi>
look in /opt/ltsp/i386/usr/lib/ltsp/configure_x.sh
09:10
and /opt/ltsp/i386/etc/init.d/ltsp-client-core
09:11
brb
09:11
<outofrang1>
I don't have /opt/ltsp/i386/usr/lib/ltsp/configure_x.sh. And ltsp-client-setup just copies $X_CONF to xorg.conf.
09:14sonjag has joined #ltsp
09:14
<outofrang1>
Ah /opt/ltsp/i386/usr/lib/ltsp/configure-x.sh
09:26outofrang1 has left #ltsp
09:27BadMagic has quit IRC
09:27BadMagic has joined #ltsp
09:29Nubae has joined #ltsp
09:37
<exodos>
upro: server's display doesn't matter here
09:49exodos has quit IRC
09:58ogra has quit IRC
10:10spectra has joined #ltsp
10:25Egyptian[Home] has joined #ltsp
10:37yopla has joined #ltsp
10:38
<yopla>
hello! In ltsp5, howto change keyboard Layout?
10:43
<sutula>
yopla: "XKBLAYOUT = us" (for example) in /opt/ltsp/i386/etc/lts.conf
10:45staffencasa has joined #ltsp
10:45
<yopla>
sutula: nope it doesn't work
10:46* sutula shrugs...what Linux distro?
10:46
<yopla>
i've used etch ltsp-build-client
10:47
<sutula>
yopla: That worked for me using the etch-backports recently
10:47* sutula defines "recently" as about 2 months ago
10:48
<yopla>
i've dpkg-build(ed) from http://pkg-ltsp.alioth.debian.org/debian etch-ltsp-backports main
10:48ogra has joined #ltsp
10:48
<yopla>
caus mys server is amd64
10:48
<Q-FUNK>
*yawn*
10:48
<sutula>
yopla: Do you want the same settings for all the clients?
10:49* sutula is wondering if yopla could just change it in the chroot
10:49
<yopla>
sutula: yes in /etc/lts.conf I have adde XKBLAYOUT=fr
10:50Nubae has left #ltsp
10:51
<yopla>
** /opt/ltsp/i386 on server
10:51
which script does maintain lts.conf?
10:52
<sutula>
yopla: look for vagrantc in this channel...he's not here now
10:53
<yopla>
stugula: thank you :)
10:54
oups sutula
10:55
<sutula>
yopla: With your different machine architectures, can you sudo chroot /opt/ltsp/i386 on the server?
10:56
<yopla>
yes i can
10:58
<sutula>
yopla: Just a minute...looking something up
11:00
yopla: After doing that, how about "dpkg-reconfigure console-data"
11:02ronalde_ has quit IRC
11:02
<yopla>
I try...
11:03ronalde has quit IRC
11:03DonSilver has joined #ltsp
11:04
<yopla>
argh! i'm still in qwerty
11:05
<sutula>
yopla: You've exhausted my ideas :)
11:05
<yopla>
lol thanks anyways
11:05* warren looks for jim
11:11Guarald1 has joined #ltsp
11:13IRCzito has joined #ltsp
11:14ogra_cmpc has joined #ltsp
11:17ogra_cmpc has quit IRC
11:24ogra has quit IRC
11:32DonSilver has quit IRC
11:35K_O-Gnom has joined #ltsp
11:36Egyptian[Home1 has quit IRC
11:40ronalde has joined #ltsp
11:41IRCzito has left #ltsp
11:49burnerx has quit IRC
11:58vagrantc has joined #ltsp
12:05ronalde has quit IRC
12:07sepski has joined #ltsp
12:13ronalde has joined #ltsp
12:15outofrange has joined #ltsp
12:22johnny has joined #ltsp
12:29yopla has quit IRC
12:32sepski has quit IRC
12:35sgonzalez has quit IRC
12:43Guaraldo has left #ltsp
12:51Guarald1 has joined #ltsp
12:55fox2k has left #ltsp
12:55fox2k has joined #ltsp
13:05sgonzalez has joined #ltsp
13:07sonjag has quit IRC
13:10dniel has joined #ltsp
13:28
<outofrange>
When is the lts.conf file normally copied to the tfptboot directory? I have /var/lib/tftpboot/ltsp/i386/lts.conf but missing the one for powerpc.
13:28
<sbalneav>
outofrange: In the initramfs.
13:29
But none of the ppc stuff was tested, at least by me, as I don't have a ppc box to test against.
13:29
<outofrange>
sbalneav: sorry, don't follow. Are you saying it's *in* the initramfs for powerpc?
13:29
<sbalneav>
No, it's fetched via tftp within the initramfs
13:30
<outofrange>
Oh, so I don't have one, but I can just create it in the tfptboot/ltsp/powerpc/ dir and be fine.
13:30
<johnny>
i tried lts.conf in my tftproot for ltsp, and it never red it
13:31
read it*
13:31scrapbunny has joined #ltsp
13:31
<outofrange>
Oh it reads the one in i386.
13:31
<johnny>
lucky you :)
13:31
<outofrange>
I think. I think I watched it in Wireshark.
13:32
<sbalneav>
outofrange: Not sure if it's "powerpc" or "ppc"
13:32* johnny tries to figure out why the new ldm won't work withou autologin anymore
13:32
<johnny>
it's powerpc
13:32
<outofrange>
Yes powerpc for Edubuntu
13:32
<cliebow__>
is that feisty..or gutsy?
13:32
<outofrange>
Gutsy
13:32
<sbalneav>
What's not working?
13:33
<johnny>
uggh.. the C version of ldm does not autologin
13:33
i just get a black screen
13:33krishna has joined #ltsp
13:33
<johnny>
were you planning on putting the hostname| style in the new ldm ?
13:33
LDM_USERNAME="hostname|" like the python hack
13:33
<vagrantc>
sbalneav: on debian based systems, it should be "powerpc"
13:34
<cliebow__>
yes powerpc
13:35
<johnny>
when i try to force autologin by hostname i have [ahostname] LDM_USERNAME="ahostname" LDM_PASSWORD="guest"
13:35krishna has quit IRC
13:36
<johnny>
i get a black screen, and when i set the console to shell, i get just the word hostname printed on the screen, in the function get_userid
13:36
when i try to start ldm that is
13:36krishna has joined #ltsp
13:40
<sbalneav>
johnny: The hostname| thing isn't currently in there.
13:40
I didn't get time to code it up
13:40
Does the ldm work if you use a greeter?
13:41
<vagrantc>
sbalneav: the "hostname|" thing sounds very similar to the stuff i was talking about for obsoleting SDM
13:41
<johnny>
not if the LDM_USERNAME and LDM_PASSWORD are set
13:42
but if i don't have themset, then i can login with thatvery same user/pass combo
13:42
<sbalneav>
ok
13:42
can I see your lts.conf? Paste to the pastebot, please
13:42
!pasetbot
13:42
<ltspbot>
sbalneav: Error: "pasetbot" is not a valid command.
13:42
<sbalneav>
!pastebot
13:42
<ltspbot>
sbalneav: "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:43
<outofrange>
This old iMacs sure are slow.
13:44
<sbalneav>
outofrange: Have you set LDM_DIRECTX?
13:44
<outofrange>
Not that's I'm aware of. Where?
13:44
<ltsppbot>
"johnny" pasted "lts.conf" (23 lines) at http://pastebot.ltsp.org/344
13:44
<johnny>
note that they are all commented out
13:44
so i can have a working install :)
13:46
<sbalneav>
outofrange: In the lts.conf file
13:46
<outofrange>
Trying now.
13:46
<sbalneav>
johnny: Try LDM_USERNAME=foo LDM_PASSWORD=bar
13:46
no quotes
13:47
<johnny>
you really think that would affect it?
13:47
<sbalneav>
Yup
13:47
<johnny>
if so.. i'll rebuild the image in a lil while
13:47
i just copy and pasted my old one
13:47
which did have the quotes
13:47
<sbalneav>
Why not just put your lts.conf in the tftp dir
13:48
<johnny>
me? cuz it didn't work
13:48
<sbalneav>
Should
13:48
/var/lib/tftpboot/ltsp/i386/lts.conf
13:48
<johnny>
yes, i put it there
13:48
<sbalneav>
make it world readable?
13:48
<johnny>
but it never read it
13:48sgonzalez has quit IRC
13:48
<johnny>
hmm.. that might have been it!
13:48
<sbalneav>
tftp runs as nobody, so it has to be at least 444
13:48
<johnny>
actually it is
13:49
644
13:49K_O-Gnom has quit IRC
13:49
<sbalneav>
Should work then. Try it again.
13:49
<johnny>
too many terminal users atm, i can't even get on one of the PCs
13:50dniel has quit IRC
13:50
<johnny>
i just talked now cuz people are actually here
13:50
<outofrange>
sbalneav: Seems a little faster. Can I see anything in my Xorg.0.log that would indicate it's enabled?
13:50
<sbalneav>
Well, we come and go as we can.
13:50krishna has left #ltsp
13:50
<sbalneav>
outofrange: In a gnome-terminal, echo $DISPLAY
13:50
what does it say?
13:51
<johnny>
i know, i'm not expecting you to be on call at all times, i just figured more people would be around during this time period
13:51
so i could get some suggestions for later
13:51
<outofrange>
192.168.0.18:6.0
13:51
<sbalneav>
johnny: Another thing I'd suggest, the hostname addressing might not work for you. Try MAC addressing in the lts.conf file.
13:51
it;s the preferred way.
13:52
outofrange: Yep, it's enabled.
13:52
<johnny>
well the IP should work
13:52
by the time it's required
13:52
<sbalneav>
Are you doing dynamic IP addressing
13:52
or assigned addresses?
13:52
<johnny>
dhcp assigned IPs by mac, so not really dynamic
13:53
i don't want to put the mac or IP in yet another place
13:53
thus why the hostname| thing was so convenient
13:53
<sbalneav>
I haven;t had a chance to do it yet.
13:53
<johnny>
sure.. this'll be fine until thne
13:53
then*
13:53
<cliebow__>
sbalneav ROCKS!!!
13:54jammcq has joined #ltsp
13:54
<cliebow__>
!j
13:54
<ltspbot>
cliebow__: Error: "j" is not a valid command.
13:54
<cliebow__>
hah
13:54
<jammcq>
heh
13:54
<cliebow__>
guess i dont need to flood the channel anyway..you Know what i mean
13:55BGomes has quit IRC
13:57
<outofrange>
Hum, other than switching to F1, is there a way to get a local shell? I want to look at logs on the thin client.
13:58
<vagrantc>
outofrange: set SCREEN_NN=shell
13:58
<outofrange>
I mean in an xterm.
13:58dniel has joined #ltsp
13:59
<sbalneav>
outofrange: not without work, no.
13:59
<vagrantc>
might be a nice debugging feature for LDM, though ... to spawn a local xterm
13:59
<outofrange>
During development do you just switch between F1 and F7?
13:59
<sbalneav>
You could install sshd in the chroot, and then set up a user to ssh in as.
13:59
outofrange: Yup.
13:59
<scrapbunny>
hi i am getting an error on my clients, "Could not look up internet address for (none). This will prevent XFCE from operating properly." Is there a fix for this or would it b easier to switch back to GNOME?
13:59
<sbalneav>
Over and over and over and over and over and over and over and over.
14:00
scrapbunny: Where are you getting this error?
14:00
vagrantc: localapps will allow that.
14:00
<vagrantc>
sbalneav: i'm thinking about before even running as a user ...
14:01
sbalneav: just spawning an xterm like you spawn the greeter
14:01
<outofrange>
So, sound worked on my newer powerpc iBook, but not on this Bondi iMac. Any suggestions where to look?
14:02
<scrapbunny>
on my clients and server when I log in
14:02
<vagrantc>
sbalneav: would be useful to debug login problems and such ...
14:02
<scrapbunny>
I can click "Continue Anyway" or "Try Again"
14:02
<sbalneav>
vagrantc: feel free to add.
14:02
<vagrantc>
:)
14:02ary has joined #ltsp
14:03
<sbalneav>
I have to sit down this weekend and try to re-do all the packaging for Ubuntu.
14:04
<jammcq>
sbalneav: try it standing up
14:04
<vagrantc>
sbalneav: have you had a chance to look at the work i did so far?
14:05
<sbalneav>
No, where is it? The jetpipe stuff, or have you done others too?
14:05ogra has joined #ltsp
14:05
<sbalneav>
ogra!!!
14:05
<vagrantc>
sbalneav: i posted to ltsp-developer
14:05
<sbalneav>
Ah, ok, haven't checked that for a day or two.
14:05prpplague has joined #ltsp
14:05
<sbalneav>
ogra: Hey, how's allhands?
14:06
<vagrantc>
sbalneav: i think i've got ldm building for debian, though i haven't actually tried it yet
14:06
sbalneav: also merged the changes from debian
14:06
<prpplague>
jammcq: greetings
14:06
<sbalneav>
code changes to ldm?
14:07
anything serious?
14:07
Oh, hey.
14:07
Here's a question.
14:07
<Q-FUNK>
*yawn* autumn fatigue really sucks.
14:07
<vagrantc>
sbalneav: mostly just theme stuff, added "ltsp" theme and Debian theme ... but i really think all but one (or maybe two) example theme shouldn't be in ldm upstream
14:08
<sbalneav>
I've ripped out some of the goo I wrote for the expect stuff, and am trying the libexpect functions.
14:08
vagrantc: Well, like the debian dir, I'm gonna leave all that in place 'till I'm SURE I don't need it.
14:09
<vagrantc>
sbalneav: all what stuff ?
14:09
<sbalneav>
the only problem is, I can't install libexpect.so without installing libexpect-dev
14:09
the stuff in sshutils.c in ldm. I wrote my own whacky expect stuff, I'd rather use something tried-tested-and-true.
14:09
<vagrantc>
ah, yes.
14:10
<scrapbunny>
any ideas on what I did?
14:10
<vagrantc>
i thought you meant the themes
14:10
<sbalneav>
so libexpect stuff seems to work, but I have to install a -dev package to get the .so's
14:10* vagrantc is all for tried-tested-and-true
14:11dniasdel has joined #ltsp
14:11
<sbalneav>
now USUALLY, you'd just install libexpect, which would get you the .so, and the -dev package usually just has the headers
14:11
any reason why in debian/ubuntu this package is different?
14:11* vagrantc sees no libexpect package
14:12
<vagrantc>
sbalneav: expect and expect-dev ?
14:12dniasdel has quit IRC
14:13
<jammcq>
prpplague: howdie
14:13
<prpplague>
jammcq: hey, whats the smallest ltsp thin client you've seen?
14:13
<stgraber>
sbalneav: I have a working iTalc :) (1.0.4 which will be released soon has the VNC thing patched)
14:15
<jammcq>
prpplague: umm, the e2300 is pretty small, about the same size as your old tsx-1. I've heard of a small client that fits in an electrical box on the wall
14:16
<vagrantc>
sbalneav: i see libexpect.so.5 in the expect package ...
14:16
sbalneav: so.5*
14:16Gadi has left #ltsp
14:17
<sbalneav>
bbiab
14:17
<vagrantc>
ah, but the regular .so is only part of libexpect-dev ...
14:17* vagrantc is pretty clueless with shared library stuff
14:17DonSilver has joined #ltsp
14:18
<prpplague>
jammcq: ahh, i made one out of our Hammer board this week, just for testing purposes
14:18
jammcq: 10baseT with usb keyboard and mouse
14:18
<jammcq>
heh, what about video?
14:18
<prpplague>
jammcq: the vga output is limited 4096 colors and 800x600
14:18
jammcq: not exactly a power house
14:18
jammcq: but cute
14:19
jammcq: everything fit in a small box just a little smaller than an altoid box
14:21dniel has quit IRC
14:22
<johnny>
if you use the startx screen script, you do get a root xterm
14:22
or at least i did
14:23
<Q-FUNK>
window manager missing
14:24
<outofrange>
Would a different window manager change performance much on these old iMac?
14:24
<johnny>
not a differet window manager per se, but losing the gnome stack in general woudl help
14:25
but metacity isn't that good on it's own, so you would want to use a different window manager in any case
14:25
<Q-FUNK>
icewm works well as a small DE
14:25
<outofrange>
I like icewm -- that's on my desktop.
14:25
<cliebow__>
icewm rocks..from an admin perspective
14:25ary has quit IRC
14:26
<cliebow__>
i use icewm/nautilus..
14:26
<outofrange>
my thin client powerpc environment is on an i386 server. Eh, how do I install new packages?
14:26
<cliebow__>
apt-get..assuming you are not doing localapps
14:27
<Q-FUNK>
cliebow__: architecture differnet. dpkg will barf.
14:27
<cliebow__>
not what runs on server..
14:27
<vagrantc>
you don't normally install packages in the chroot
14:27
<cliebow__>
gd endians
14:27
<johnny>
i did install strace on the chroot.
14:27
<outofrange>
Right.
14:27
<Q-FUNK>
you cannot even make a ppc chroot from an i386 host.
14:28
<prpplague>
jammcq: it was zippy enough to do some desktop basics
14:28
<vagrantc>
Q-FUNK: that's besides the point.
14:28
<Q-FUNK>
dpkg complains that you are trying to install a ppc package on an i386 host and stops.
14:29
<vagrantc>
you won't even get that far
14:29
<Q-FUNK>
vagrantc: no it's not. see outofrange's question.
14:29
<cliebow__>
i believe ogra said ltsp-update-image woild work fine with a powerpc
14:29
<outofrange>
So, changing window manager's not going to make the *client* run faster (My P4 clients run really fast).
14:29
<vagrantc>
Q-FUNK: outofrange is asking how to install a window manager, and it doesn't matter what the chroot environment is, the program installs and runs on the server itself, not the chroot environment
14:29
<outofrange>
Yes
14:30
<vagrantc>
unless it's localapps
14:30
<Q-FUNK>
vagrantc: you still need a way to enter the chroot from the correct architecture.
14:30
<outofrange>
If my p4 client is fine but the imac is slow it's either network or just slow machne. Right?
14:30
<vagrantc>
Q-FUNK: no.
14:30
Q-FUNK: i mean, if you need to do something in the chroot, sure. but what is being asked about is not happening in the chroot.
14:31
<Q-FUNK>
vagrantc: yes. dpkg won't allow you to install for another acrhitecture.
14:31
<cliebow__>
i read it that way as well
14:31
<vagrantc>
and even lots of things being done in the chroot don't require the same architecture (edited configuration files)
14:31
Q-FUNK: and there is no cross-architecture installation happening.
14:32
<Q-FUNK>
he needs to install ppc packages into an ltsp environmnet hosted on i386. think.
14:32
<vagrantc>
Q-FUNK: when installing a window manager on an i386 client with an i386 server, where do you install the window manager? in the server, or in the chroot? it's no different with a powerpc client.
14:32* vagrantc suspects vagrantc has thought *way* more about this than many, many, many people.
14:32sadmin has joined #ltsp
14:33
<vagrantc>
Q-FUNK: no need to tell me to think, i've done cross-chroot hosted diskless and LTSP environments on many occasions.
14:33
<Q-FUNK>
*sigh*
14:34
<vagrantc>
*if* it was installing the window manager to run as a local application, then it would need to be done with an appropriate architecture, but that does not seem to be the case here.
14:34
<outofrange>
vagrantc: correct.
14:35
O
14:35
<vagrantc>
in a typical LTSP environment, all applications are installed on the server itself.
14:35
which means, no need to worry about the client architecture.
14:35* sbalneav wonders again about the viability of using qemu in ppc mode to manage ppc chroots on an i386 box.
14:35
<cliebow__>
sbalneav:my head hurts..
14:35
<vagrantc>
sbalneav: haven't had much luck.
14:36
<Q-FUNK>
precisely my point.
14:36
<vagrantc>
i've tried qemu's ppc, arm and sparc emulation without a lot of luck ... though it's been a while.
14:36
Q-FUNK: are we even talking about the same thing here?
14:36
<outofrange>
I'm just curious because OS 9 is reasonably snappy on this machine. But it's a bit slow as a thin client. Yet, my P4 thin clients are very responsive. So, maybe LAN??
14:36
<sutula>
vagrantc: Since the question comes up and there's sometimes need to install (or dpkg-reconfigure) something in the chroot, what would be the best way to do it?
14:37
<sbalneav>
outofrange: is it a 10 or 100 megabit network card?
14:37
<vagrantc>
sutula: boto a machine of the appropriate architecture and modify the chroot.
14:37
s,boto,boot,
14:37
<cliebow__>
i just use an ibook to build my chroot..
14:37
<Q-FUNK>
vagrantc: I'm beging to wonder about that.
14:37
<outofrange>
How can I tell?
14:37
<sbalneav>
No idea. I know nothing about mac hardware.
14:37
Google knows, I bet.
14:38
<vagrantc>
Q-FUNK: what i'm talking about is hosting an existing chroot on a different architecture.
14:38
<outofrange>
Any reason you couldn't F1 on the thin client, mount the chroot and then sudo chroot?
14:38
<Q-FUNK>
outofrange: which hardware?
14:38
<vagrantc>
Q-FUNK: creating the chroot is a different matter.
14:38
<cliebow__>
outofrange, is you name to ip resolution good?
14:38
<outofrange>
You mean is it a dns issue?
14:39
<Q-FUNK>
vagrantc: hosting is easy. it's just a big folder; it can go anywhere. creating a chroot and adding/removing packages for another architecutre is a whole other ball game.
14:39
<sutula>
outofrange: Sounds reasonable if the client can write the file system
14:39
<vagrantc>
Q-FUNK: agreed.
14:39
Q-FUNK: and normally, you don't install the window manager in the chroot ... hence ...
14:39
<outofrange>
It's more that menus are sluggish. Just slow GUI.
14:40
<vagrantc>
Q-FUNK: X windows becomes the cross-architecture platform ...
14:40
<Q-FUNK>
vagrantc: ideally, yes
14:40
<vagrantc>
Q-FUNK: and in a typical LTSP environment, the window manager is installed on the server ...
14:40
Q-FUNK: architecture doesn't matter.
14:41
the only thing running on the thin client is basically X
14:41
<Q-FUNK>
outofrange: if you have speed mismatches, it could explain the sluggish behavior. e.g. 10baseT old Mac connecting to 100bseT or, even worse, to Gigabit network.
14:41
<outofrange>
http://www.everymac.com/systems/apple/imac/stats/imac_ab.html shows 100Base-T
14:41
<Q-FUNK>
sbalneav: speaking of X, does the patch work for you?
14:42
outofrange: another thing to check is how fast of a server you have in terms of MHz.
14:44
<outofrange>
It's just a P4 3.2Ghz with 1GB, but I'm comparing the performance of the iMac with another P4 3.2Ghz thin client. The P4 is running at 2048x1536, too.
14:45
<Q-FUNK>
ah. screen resolution might be an issue too. the bigger, the more data needs to be drawn by remote.
14:45
<vagrantc>
but the bigger one is working fine
14:45
<outofrange>
The point is that the iMac is just running X, nothing else, and should be 100Mbit LAN (just like the other P4 client) but it's a bit slow. SO maybe it's just because it a slow machine.
14:45
Right
14:46
<vagrantc>
outofrange: video hardware differences, possibly
14:46
<outofrange>
Makes sense. I need to boot back to OS 9 and compare again. Maybe I'm remember it faster than it really is.
14:47
<vagrantc>
outofrange: better yet would be to get it running linux and see if the xserver is slow ...
14:47
outofrange: might just be poorly supported graphics card for X.org
14:47
<outofrange>
Good idea.
14:48gentgeen__ has joined #ltsp
14:48
<outofrange>
/var/log/syslog isn't written on the clients? All sent to syslogd?
14:49
Looks like it.
14:50
When I enable syslogd on the server the messages seem to come in once every 5 seconds. Is that configured that way?
14:52cliebow__ has quit IRC
14:54
<sutula>
outofrange: Do you need the encryption or have you already turned it off? That burns CPU on both the client and server.
14:54
<outofrange>
No, I don't. That's server wide, correct?
14:55
Oh, I already have LDM_DIRECTX=True
14:56* sutula isn't sure of the answer to that, but knows that you could skip ldm completely to avoid it
14:56
<sutula>
However, suggesting using xdmcp would surely bring down the wrath of this channel upon me :)
14:56
...but you can pick that per-client
14:57
<outofrange>
Yes, if it's in lts.conf. I didn't connect LDM_DIRECTX with un-encrypted session.
14:58
One last issue -- any ideas about sound? It works on my iBook but not on this iMac.
15:00
<vagrantc>
LDM_DIRECTX=True is basically using the same technology as XDMCP for the vast majority of traffic with the exception of login
15:02
outofrange: check if $ESPEAKER and $PULSE_SERVER are set ...
15:02
<jammcq>
LDM_DIRECTX=True says "Use X protocol on the wire, rather than wrapping it in SSH"
15:02
<vagrantc>
outofrange: might be that the sound hardware wasn't autodetected
15:03
<jammcq>
it really has nothing at all to do with XDMCP
15:03
<outofrange>
Those are not in the environment
15:03
<vagrantc>
jammcq: yes and no
15:03
<jammcq>
XDMCP is the protocol for logging in and creating a session
15:03
<outofrange>
I don't see sound in lspci, either.
15:03
<vagrantc>
true true
15:03
<outofrange>
or in dmesg
15:03
<jammcq>
once the session has been created, it's X all the way, baby
15:03
<vagrantc>
jammcq: but once the login happens, it's using the same technology
15:03
<jammcq>
it's no longer using XDMCP, it's using X Protocol
15:04
<vagrantc>
jammcq: whereas when LDM_DIRECTX=false, there's an ssh layer thrown in there.
15:04
<jammcq>
XDMCP starts and stops the session
15:04
right
15:04
it's either X by itself or X over SSH
15:04
the only way you'll use XDMCP is if you use GDM, KDM or XDM
15:05Q-FUNK has quit IRC
15:05
<jammcq>
and even then, you'll only see about 6 XDMCP packets on the wire, cuz once you've logged in and created the session, it's just X
15:05Q-FUNK has joined #ltsp
15:05
<vagrantc>
so the only difference between XDMCP and using LDM with LDM_DIRECTX=True is basically the login ... after that, it's essentially the same (except local devices and remote sound assumes you're using LDM mostly)
15:06
<jammcq>
well, you comparing LDM with [GKX]DM ?
15:06
or LDM with/without DIRECT_X
15:07
apples and bananas
15:07* jammcq is just pointing out the fact that there's a difference between the 'XDMCP' protocol and the 'X' protocol
15:08
<vagrantc>
i am comparing people's performance expectations when using LDM_DIRECTX vs. XDMCP (gdm/kdm/xdm/wdm)
15:11
so yes, there's logging in using XDMCP, there's logging in using LDM with LDM_DIRECTX=True ... and both of these, once logged in, are essentially the same (using the X protocol). when logging in with LDM using LDM_DIRECTX=False, there's ssh X11 forwarding in addition to the X protocol.
15:11
<jammcq>
right
15:11
s/essentially/exactly/
15:12
<vagrantc>
well, i chose essentially, because there are subtle differences, in that your local device and sound plumbing will be easier to set up.
15:12
<outofrange>
vagrantc: $ESPEAKER and $PULSE_SERVER are not in the environment on my iBook, either. But sound works there.
15:12
<vagrantc>
:)
15:13
outofrange: you're doing that when logged from the thin client ?
15:13
<outofrange>
Yes, switching to F1
15:13
<vagrantc>
no
15:14
do it from the login on the server
15:14
<outofrange>
Oh in an xterm
15:14
<vagrantc>
yes
15:14upro has quit IRC
15:15
<outofrange>
Just $ESPEAKER are set on both
15:15
<vagrantc>
what linux distro is this?
15:16
<outofrange>
Edubuntu Gutsy on the server. I used Xubuntu to build the thin client env.
15:17
<vagrantc>
outofrange: coudl you paste your lts.conf to the pastebot?
15:17
!pastebot
15:17
<ltspbot>
vagrantc: "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.
15:17* vagrantc wishes there was a way to tell the ltspbot to direct the comment to someone else
15:17
<ltsppbot>
Someone pasted "moseley@ltsps0:/var/lib/tftpbo" (7 lines) at http://pastebot.ltsp.org/345
15:18
<vagrantc>
odd.
15:18
i thought gutsy enabled pulseaudio by default ...
15:18
<outofrange>
I think it is
15:19
<vagrantc>
doesn't seem like it, or $PULSE_SERVER would be set
15:19
<outofrange>
Maybe so.
15:19
But I have sound. ;)
15:19
It is, when I run auxmix I see plus audio.
15:19
alsamixer, that is.
15:19
<vagrantc>
sure
15:19* vagrantc can't keep up with gutsy
15:20
<outofrange>
When I run it on the iMac I get connection refused.
15:20upro has joined #ltsp
15:20
<vagrantc>
well, there's something
15:20
<outofrange>
Yes. I wish I had /var/log/syslog on the iMac
15:21
<vagrantc>
outofrange: if $ESPEAKER is set but $PULSE_SERVER isn't, i would think your sound system is using esound instead of pulseaudio
15:21
<upro>
Hi again! After upgrading to gutsy I have agina an old problem: My clients can't login. It stalls for a while, then goes back to the login screen. I don't remember how I resolved this before, could someone please point me there?
15:21
<outofrange>
Well, when I run alsamixer it says "PLUSEAUDIO: Unable to connect: Connection refused"
15:22
upro: ltsp-update-sshkeys?
15:22
<upro>
outofrange: let's see...
15:23
<outofrange>
Would need to also do ltsp-update-image, IIRC, so that the clients get the new keys.
15:23
<vagrantc>
outofrange: can you get a login on the thin client itself (not using ldm)
15:23
<outofrange>
Yes, F1
15:23
<vagrantc>
outofrange: ps aux | egrep pulse
15:23
<upro>
outofrange: I updated the entire ltsp section (moved the opls opt/ltps/i386)
15:24
outofrange: still no success after ltsp-update-sshkeys
15:24
<outofrange>
Not running on the iMac
15:24
<vagrantc>
outofrange: the working machine?
15:24
<outofrange>
Not there either.
15:24
<vagrantc>
i'm at a loss.
15:24sadmin has quit IRC
15:24DonSilver has quit IRC
15:25
<outofrange>
weird
15:25
<vagrantc>
outofrange: ps aux | egrep esound
15:25
outofrange: ps aux | egrep 'esound|esd'
15:25Amaranth has quit IRC
15:25Amaranth_ has joined #ltsp
15:25DonSilver has joined #ltsp
15:25
<outofrange>
upro: you would need to update the images, too, I thnk.
15:26
<upro>
outofrange: ltsp-update-image is the same as upgrading the ltsp image?
15:26
outofrange: I'm doing it right now
15:26
<outofrange>
vagrantc: nope, no sound|audio.
15:26
<vagrantc>
outofrange: ??
15:26
<outofrange>
Wait.
15:27
Ya pulseaudio is running on the ibook
15:27* vagrantc gives outofrange a funny look
15:28
<outofrange>
Hey, I'm sitting in front of six screens and two keyboards... ;)
15:28
<vagrantc>
yes, i'm i'm behind another trying to help you :P
15:28
<outofrange>
:-)
15:28
So pluseaudio is running on the iBook but not on the iMac -- maybe I should just try running it and see what it says.
15:29sepski has joined #ltsp
15:29
<vagrantc>
outofrange: my guess is that it didn't autodetect your sound card
15:31scrapbunny has left #ltsp
15:31
<outofrange>
Hum, how do I su to user "pulse"?
15:32
su pulse -c pulseaudio just returns
15:33
<vagrantc>
outofrange: i would first figure out what your sound card is, and if it's detected
15:33
outofrange: it's probably as simple as telling it to load a kernel modules from lts.conf
15:34
outofrange: lspci ; lsmod
15:36
<ltsppbot>
Someone pasted "moseley@ltsps0:~$ cat lsmod.im" (29 lines) at http://pastebot.ltsp.org/346
15:36
<outofrange>
Smallest lspci I've seen!
15:36
no snd
15:37
<vagrantc>
hmm... yeah. no idea what to load
15:38
<outofrange>
I loaded snd but still need to load the pulseaudio server on the client.
15:38
modprobe snd did load the modules
15:39Amaranth_ is now known as Amaranth
15:39
<vagrantc>
outofrange: what modules did it load?
15:39
outofrange: usually you need a specific module for your specific sound card ...
15:39
<outofrange>
snd-powermac (if google is right)
15:39
<vagrantc>
ok
15:39
sounds more promising. ...
15:40
<outofrange>
Don't have that module.
15:40
<vagrantc>
ah, well...
15:40
if you find the module that loads your sound system ...
15:40
<outofrange>
Maybe the K12LTSP list would be a good place to ask.
15:41
<vagrantc>
add: MODULE_00=foo to lts.conf and reboot your thin client
15:41
<outofrange>
When developing how do you look at syslog?
15:41
<vagrantc>
outofrange: cliebow also has done some mac stuff ...
15:42
outofrange: generally i enable remote syslogging ont he server
15:42plamengr has joined #ltsp
15:42
<outofrange>
Do you see the messages come in once every 5 seconds? It was too slow when I had it enabled.
15:42
Took forever just to get the boot messages...
15:42
<vagrantc>
they usually come in about as fast as they get sent
15:43
<outofrange>
Something odd in the config, perhaps.
15:43
<vagrantc>
the boot log will be a little slow, in that it only kicks in when syslogd starts ...
15:43
although, maybe it's different on ubuntu- i don't know if they've switched the syslog system yet
15:44
<outofrange>
It was like clock work -- once every 5 seconds. Maybe syslogd throttled.
15:44
vagrantc++ thanks for all your time.
15:46johnny_ has joined #ltsp
15:46
<johnny_>
finally back to the terminals :)
15:47
<cliebow>
outofrange, jim kronebush did some sound work on Bondi
15:48
<outofrange>
Hey. Did you have sound?
15:48
Sorry, read that wrong. I'll post to K12LTSP.
15:53
<cliebow>
jim@winonacutter...something like that
16:04
<Q-FUNK>
yes, those G3 imacs use snd-powermac
16:04
I have one here
16:06
G4 and more recent hardware uses snd-aop
16:10
<cliebow>
ahh!
16:12
<Q-FUNK>
there's some kind of data bus that the old G3's and older PPC lack that prevents them form being migrated to snd-aop
16:12
<outofrange>
Great, and I don't have snd-powermac.
16:12
<Q-FUNK>
no?
16:13
<outofrange>
No, it's there. I just didn't see scrolling
16:13
<Q-FUNK>
isn't it included in stock kernels?
16:13
it's not loaded by udev, if that's what you meant
16:14
<outofrange>
Maybe so -- I must have just missed it.
16:14
<Q-FUNK>
too many oddball old PPC subarch covered by that driver and nobody ever bothered sorting thru this to have them autodetected by udev
16:15
<outofrange>
MODULE_00 = snd-powermac should do it. Let me try
16:20
<johnny_>
ok.. tested with mac addresses instead of hosts and ips, still no dice
16:21
<outofrange>
Odd. It beeped at me in an xterm but still not pluseaudio running.
16:21
<johnny_>
i'm not sure what else to try
16:22jammcq has quit IRC
16:23sepski has quit IRC
16:23
<outofrange>
So all my sound modules are loading, but Pulseaudio is not loaded. Maybe when syslog catches up I'll see something.
16:25
<johnny_>
ldm2 just says hostname when i run it manually
16:30
<outofrange>
Anyone know what starts pulseaudio on the client? /etc/default/pulseaudio has the init.d script disabled. (that way on the working iBook, too).
16:34moquist has quit IRC
16:34* johnny_ tries to think of something else to try
16:40
<johnny_>
anybody else here trying to use ldm autologin ?
16:40
oh.. with gutsy
16:43
<outofrange>
Well, I guess this is it:
16:43
Sound requested but /dev/dsp is missing.
16:44
But it's there. Maybe starting sound is happening before loading snd-powermac?
16:44DonSilver has quit IRC
16:45prpplague has quit IRC
16:47K_O-Gnom has joined #ltsp
16:49
<johnny_>
sbalneav, sorry to call you out, but did you have any more suggestions, as i tried with mac addresses too
16:52plamengr has quit IRC
17:37Q-FUNK has quit IRC
17:52moquist has joined #ltsp
18:07staffencasa has quit IRC
18:15laprag has joined #ltsp
18:21fox2k has quit IRC
18:22K_O-Gnom has quit IRC
18:33laprag has quit IRC
18:33Egyptian[Home] has quit IRC
18:39spectra has quit IRC
19:11vagrantc has quit IRC
19:19upro has quit IRC
19:40hersonl2 has joined #ltsp
19:42jammcq has joined #ltsp
19:42
<jammcq>
hey all
19:46
<hersonl2>
say
19:49
<johnny_>
ugghz
19:52fgiraldeau has joined #ltsp
19:53
<jammcq>
hey fgiraldeau
19:53
<fgiraldeau>
hi there!
19:53
Hope that you're all fine
19:54
Jesus, Bar Harbor is quite lost in the world
19:55
When I went back to home, the road was blocked by a tree that felt by night
19:55
<johnny_>
anybody here used autologin with gutsy ltsp?
19:56
<fgiraldeau>
jammcq : I had the meeting with my thesis director, and NX will be the subject of my reseach
19:57
<jammcq>
wow
19:57
<fgiraldeau>
jammcq : the NBD enhancement proposal may be done by other student team, but solutions are more obvious...
19:58
In many papers I'm reading, the main concern for the user's experience is about latency
19:59
I think I will have great time to dig into this
19:59
<jammcq>
yes, lots to learn there
19:59
<fgiraldeau>
What about the day I missed?
20:00
BTW, my brother didn't succeed ;)
20:00
<jammcq>
bummer :(
20:00
on sunday, we went driving around, searching for breakfast. we had to go over to Bar Harbor and found a great place to eat
20:00
<fgiraldeau>
he lost with 35% of casts
20:00
<jammcq>
then, we drove around and went to the top of Mt.Cadilac
20:01
didn't get back to the seawall until about 2pm
20:01
<fgiraldeau>
What a nice place
20:01
<jammcq>
yeah, then we hacked all the rest of the day
20:02
a great time was had by all
20:02
<fgiraldeau>
I'm pretty sure! And does the package source have been refactored?
20:02
<jammcq>
umm, much work was done on that
20:02
I'm not sure if it's complete yet
20:03
<fgiraldeau>
I will sync my branch from there and start from there
20:04
Ok, thanks for the info, I will stay tuned
20:04
<cliebow>
fgiraldeau, !!!!!!NX rocks!!
20:05
<johnny_>
sure.. but how about we get non NX working first :)
20:05
hehe
20:06
<cliebow>
Good grief!
20:06
<fgiraldeau>
cliebow : I think so. I wish to know more about how does it works, how it compares to other techno and how we could improve it.
20:07
<johnny_>
i heard rdp works well.. but only tested it over a really bad network
20:07
<fgiraldeau>
The code is open source, but the research behind it seems secret.
20:08
johnny_ : and so, you have a problem with autologin?
20:08
<cliebow>
fgiraldeau, well i am only an end user..but had some time with "the happy packet" fabian franz...
20:08
<fgiraldeau>
cliebow : what it that, the happy packet?!
20:08
<jammcq>
the "Happy Packet Dance"
20:09
Fabian does a great presentation about how NX works
20:09
<fgiraldeau>
What the hell is that?!
20:09
<cliebow>
at uds in Montreal he did a presentation that became know n as the " hapy packet" dance
20:09
<jammcq>
Fabian is the guy behind FreeNX
20:09
<fgiraldeau>
Fabian Rodrigues?
20:09
<johnny_>
freenx is pretty neat .. i almost had that working once
20:09
<jammcq>
Fabian Franz
20:10
<johnny_>
fgiraldeau, yes :)
20:10
<fgiraldeau>
Franz, don't know.
20:10
<jammcq>
fgiraldeau: is your research going to be published in English or French ?
20:10
<cliebow>
he waltzed from end to end of the room showing us how the packets would aggregate and traverse the network together
20:11
i use freenx every day...err now the nomachine free client
20:11
free server
20:11
<fgiraldeau>
jammcq : I will write articles in english
20:11
<jammcq>
excellent
20:11
i'm looking forward to reading them
20:12
<fgiraldeau>
cool
20:12
<johnny_>
fgiraldeau, yes.. i had autologin working previously
20:12
in the python version of ldm
20:12
<cliebow>
fgiraldeau, happy to proofread for you 8!~)
20:13
<fgiraldeau>
johnny_ : ... and now with the new LDM, it's not working the same?
20:13
<johnny_>
correct
20:13
<fgiraldeau>
Il will get a look, wait a minute.
20:13
<johnny_>
fgiraldeau, i heard the development of ldm is relatively spread out, so if you're not using debian/ubuntu.. it might not even be the same
20:13
:(
20:15
<fgiraldeau>
johnny_ : if (getenv("LDM_USERNAME") || getenv("LDM_PASSWORD")) {ldminfo.autologin = TRUE;}
20:15
<cliebow>
johnny, ldm is the creation of sbalneav....for all practical purposes
20:15
<fgiraldeau>
So, LDM_USERNAME and LDM_PASSWORD should be set in the lts.conf file.
20:16
<johnny_>
they are
20:16
when they are set, i just get a black screen
20:16
with cursor
20:18
<fgiraldeau>
If you do a login by hand, does it works?
20:18
<johnny_>
correct
20:18
i get down to seeing the words In get_userid
20:18
which is a function
20:18
i have some version of the new ldm src
20:18
link given to me my vagrantc
20:19
err by*
20:19
<fgiraldeau>
Do you see if the ssh login is working correctly on the server side?
20:19
<johnny_>
hmm... good idea
20:19
i do see the fact it says starting ldm too
20:19
and then i just see the word hostname
20:19
on the client
20:19
when i switch to console mode that is
20:19
<fgiraldeau>
server:/var/log/auth.log
20:20
<johnny_>
i think seeing the plain word hostname is a problem
20:20
but i'll look into the auth log
20:20
brb
20:20
<fgiraldeau>
ok, right. And doing "ps fax" on the thin-client may help to see what's happening
20:20
<cliebow>
fgiraldeau, anyway...pleasur meeting you at bts..
20:21
<fgiraldeau>
cliebow : Really nice, but I'm sorry that the netvista you had is so misterious
20:22
<cliebow>
it is an old piece of crap client..but it is all i have 8~)
20:24
<johnny_>
it never tries fgiraldeau
20:24
i never get anything in the /var/log/auth.log
20:25
<cliebow>
Gadi spent some time with me on Sunday with the netvista...until it became clear it was not worth the efort
20:25
<johnny_>
neither failure nor success
20:26
<fgiraldeau>
johnny_ : Ok, what about ps fax in a console on the thin-client?
20:26
There are also logs on the thin-client
20:26
<johnny_>
hmm.. which one shoudl i check
20:27
the last one i see is in /var/log/ldm.log
20:27
i'll look for a few
20:29
<fgiraldeau>
ok
20:29
I'm starting my own thin-client right now...
20:29
<cliebow>
later/////
20:30
<johnny_>
ok, checked all the logs, nothing i saw is relevent
20:31
the biggest indicator was seeing the word hostname on the console when i switched back to the vt1 after starting ldm
20:31
it seems like it echos the phrase hostname in ldm, but doesn't execute it in that case
20:31
but i don't really know C that well
20:37
<fgiraldeau>
I agree, it's a bit strange. I'm trying to reproduce the error, give me few minutes.
20:38
<johnny_>
what distro are you using?
20:38
<fgiraldeau>
gutsy
20:39
<johnny_>
awesome
20:39
<fgiraldeau>
If there is a bug, let's find it
20:48hersonl2 has quit IRC
20:49burnerx has joined #ltsp
20:49andre has joined #ltsp
20:54
<fgiraldeau>
As far as I see, it seems to have a problem. I got ldm that is launching X, but no SSH connexion is started
20:55
In get_userid, as you said
20:56
<andre>
I have a bizzare sound issue, for some reason the sound on all my ltsp terminals only plays once. No matter what app is using sound, and they all work the first time, only works once. Not that each app only works once the system only works once, or the first sound to play is the only one that works. There are no errors on either the ltsp server (sound client) or the ltsp terminal (sound server) so I am at a loss
20:59
<johnny_>
fgiraldeau, ok good. i'm glad i'm not the only one
21:02
<fgiraldeau>
johnny_ : I will open a bug about it, but I need a bit more info before that. I will add some debugging info to ldm.
21:03
Thanks for reporting the bug.
21:04
<johnny_>
well i didn't know it was a bug, i thought i messed up :)
21:04
i'd like to know what you come up with from your debugging
21:04
as well as have a bug to read
21:09
<fgiraldeau>
cool, I will probably post on the devel mailing list about it.
21:11andre has quit IRC
21:27fgiraldeau has quit IRC
21:30
<johnny_>
uggh.. i wnated the post :)
21:33happywithed has quit IRC
21:40fgiraldeau has joined #ltsp
22:08johnny_ has quit IRC
22:11
<fgiraldeau>
johnny_ : Are you there yet?
22:11
https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/161794
22:44fgiraldeau has quit IRC