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


Channel log from 28 November 2009   (all times are UTC)

00:40dfwlinuxguy has joined #ltsp
01:05alkisg has joined #ltsp
01:19dfwlinuxguy has quit IRC
01:24mikkel has joined #ltsp
02:18vagrantc has quit IRC
02:22mikejf1 has joined #ltsp
02:24Ahmuck has quit IRC
02:30
<mikejf1>
I'm trying to setup LTSP with a IBM NetVista and whenever I try and boot of the LTSP server I get a "Boot file server protocol not specified" error.
02:31
I am using DHCP so I haven't forgotten to set something on the NetVista bios
02:32
I have seen a few things online saying that LTSP doesn't work out od the box with the NetVistas but I haven't been able to find a howto or anything to help get it working
02:32
can anyone here point me in the right direction?
02:45
<alkisg>
Does it support PXE? If it doesn't, and it only supports other protocols like RPL, it'd be easier if you used a floppy/cd/usb to boot it...
02:52sene has joined #ltsp
03:02
<alkisg>
mikejf1: also, give it a try to specify option-211: http://www.fredshack.com/docs/ibm_netvista.html
03:38
<mikejf1>
alkisg: I don't know wether it supports PXE but it doesn't have any floppy or cd drives
03:39
it has USB but I doubt it will boot of it
03:40
<alkisg>
Well, all I can tell you is first to try the option-211 above, and if that doesn't work, find and read the netvista manual to see what it supports.
03:40
<mikejf1>
Ok, thanks
04:09artista_frustrad has joined #ltsp
09:35ltspbot has joined #ltsp
09:35sbalneav has joined #ltsp
09:59
<moldy>
hi
09:59
i have one client from which i can only login as a certain user... all other users don't seem to work. manually sshing from the client into the server works fine with any user. what could be the cause for this?
10:00
another problem: my clients don't reboot properly with ubuntu karmic
10:00
i need to hardware-reboot them... software reboot results in a screen with nbd errors
10:04
<alkisg>
moldy: about the second one, it's a bug that was fixed shortly after the karmic release
10:05
ldm.c was changed to call `shutdown -fp` or `reboot -fp` instead of just -p
10:05
About the first one, have a look at ~/.xsession-errors on the users that can't logon
10:05
<moldy>
alkisg: will the fix be backportes to karmic?
10:05
alkisg: ok, thanks, will check that
10:05
<alkisg>
It has, it's in some PPA
10:06
<moldy>
alkisg: cool... if you happen to have the link handy, please tell me :)
10:06
<alkisg>
!stgraber-ppa
10:06
<ltspbot>
alkisg: "stgraber-ppa" :: https://launchpad.net/~stgraber/+archive/ppa
10:06
<moldy>
alkisg: thanks alot
10:06
<alkisg>
yw :)
10:18otavio has quit IRC
10:19otavio has joined #ltsp
10:22
<moldy>
alkisg: .xsession_errors: http://nopaste.linux-dev.org/?5464
10:26
i cannot make much sense of it :-/
10:26
"Unable to open X display 192.168.0.33:7.0" -- but why?
10:29
is it the graphics driver? but why can i then login with one user, but not with others?
10:30
and the accounts that don't work from that client work fine from other ones
10:37Egyptian[Home] has quit IRC
10:38Egyptian[Home] has joined #ltsp
11:22
<Patina>
Had to compile kernel to get rootfs on nfs, but now usb-keyboard doesn't work. Any ideas why?
11:28
<moldy>
Patina: check your kernel config for usb/hid stuff
11:30
<Patina>
moldy: Did that, but don't know what to look for.
11:36
<moldy>
Patina: grep for "hid"
11:36
"HID", actually
11:36
something like: zgrep -i hid /proc/config.gz
11:39
<Patina>
I don't have a /proc/config.gz, I usually use "make menuconfig".
11:41scottmaccal has joined #ltsp
12:00
<Patina>
moldy: Thanks, works know.
12:01
Not exactly sure what I did though.
12:13vagrantc has joined #ltsp
12:16
<moldy>
Patina: enable /proc/config.gz, it's always good to have it
12:29
<alkisg>
moldy: what exactly does it do and the users don't log on/
12:29
?
12:29
Blank screen, gets back to ldm, what?
12:34
<moldy>
alkisg: displays spinner, screen goes dark, back to ldm prompt
12:35
some X issue? graphics driver?
12:35
<alkisg>
Hmmm and what happens for a *new* user?
12:35
<moldy>
alkisg: the user that does not work is a new one
12:35
some older ones work, some older ones don't
12:36
i am about to try a different graphics driver... takes some time, the machine is physically hard to access at the moment
12:36
<alkisg>
moldy: well, just try with XSERVER=vesa in lts.conf then
12:37
<moldy>
yeah, i am trying
12:38
<alkisg>
I wonder if it has anything to do with compiz...
12:38
<moldy>
but that reboto bug makes it hard to reboot the machine :p
12:38
"reboot bug"
12:38
<alkisg>
Heh, do put that ppa to your chroot sources...
12:38
<moldy>
i need to go downstairs 2 floors and climb upon a ladder and operate the box from the top of that ladder :p
12:38avena has joined #ltsp
12:38
<moldy>
how do i tell apt to use the ppa only for ldm, not for other stuff?
12:38
<knipwim>
what happened to the wiki?
12:39
<moldy>
if i do a dist-upgrade with the ppa active, it replaces all sorts of ltsp stuff
12:39
<alkisg>
There's apt-pinning for that (you give it low priority),
12:39
but you can just install the deb with dpkg -i,
12:40
and once just copying the ldm executable worked for me :)
12:40
moldy: https://help.ubuntu.com/community/UbuntuBackports#Use%20pinning%20to%20limit%20the%20backports%20repository
12:40
That's the "correct" (TM) way to do it...
12:41
<moldy>
alkisg: thx
12:42
<alkisg>
knipwim: it's being moved to sourceforge because the server died
12:42
!docs
12:42
<ltspbot>
alkisg: "docs" :: For the most current documentation, see https://sourceforge.net/apps/mediawiki/ltsp/index.php?title=Ltsp_LtspDocumentationUpstream
12:43
<knipwim>
i was looking for the "Integrating LTSP into your favorite distro" page
12:43
didn't see in on the new sf wiki
12:43
<moldy>
alkisg: how do i identify the ppa in references?
12:44
<alkisg>
I've never actually done it, so your google is as good as mine ;)
12:44
<moldy>
i tried googling, but i did not find anything
12:44
<alkisg>
Ah, wait then..
12:45
<moldy>
i know how to pin backports, but ppas seem to be different
12:45
ppas seem to use the same archive names as the official repositories
12:46
<vagrantc>
probably need to pin on other qualities, then
12:47
<moldy>
o= seems to be it
12:47
<alkisg>
moldy: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/270817
12:47
I think a good way is the one that is mentioned on the first comment
12:48
<moldy>
yup, that's what i just found, too. thanks :) trying it now
12:48
<alkisg>
It says that they fixed the problem: "setting Pin: release o=LP-PPA-mvo works now"
12:51
<moldy>
it does not seem to have the desired effect, though
12:51
apt still wants to install stuff from the ppa
12:51* alkisg tries...
12:52
<moldy>
my /etc/apt/references: http://pastebin.com/f44eef48d
12:53
<alkisg>
Is -100 a valid priority?
12:53
<moldy>
not sure... i tried other values, too
12:53
<alkisg>
And, it should be ***p***references
12:54
<moldy>
ahh
12:54
<alkisg>
Or maybe a file in preferences.d/*
12:55
<moldy>
still no success for me, though
12:55
<alkisg>
vagrantc? some help? :) Do files in /etc/apt/preferences.d need some special extension?
12:55
<moldy>
i have it in /etc/apt/preferences, in accordance with the debian documentation
12:57
i think now i have it working
12:57
<vagrantc>
apt-cache policy is your freind
12:57
<alkisg>
Got it
12:57
preferences.d/stgraber, with the following contents:
12:57
<moldy>
this seems to work http://pastebin.com/f29845323
12:57
<alkisg>
Package: *
12:57
Pin: release o=LP-PPA-stgraber
12:57
Pin-Priority: 400
13:00
<moldy>
hmmm
13:00* alkisg is on Karmic
13:00
<moldy>
me too
13:00
but i still don't quite get it :)
13:01
<alkisg>
I didn't have to specify anything else... just this file with those 3 lines
13:01
<vagrantc>
pin priority of 101-499 will typically stay the same version as your primary release, but if the version is already higher, it will handle upgrades and such.
13:01
so typically, you want a pin priority in that range, and then manually select the versions of packages you want from it, and then it'll handle upgrades and whatnot
13:02
apt-cache policy will tell you the priority for each repository
13:03
<alkisg>
I get 100 /var/lib/dpkg/status, 400 http://ppa.launchpad.net karmic/main Packages, and 500 http://gr.archive.ubuntu.com karmic/main Packages. Looks fine to me...
13:03
<moldy>
alkisg: with your 3 lines, dist-upgrade wants to upgrade packages with stuff from the ppa, for me
13:04
<alkisg>
What does `apt-cache policy ldm` tell you?
13:04
<moldy>
http://pastebin.com/f4efd6dbb
13:04
<alkisg>
Also, did you delete the older preferences file?
13:04
<moldy>
yep
13:05
it has priority 500
13:05
but it should be 400.... i must have made a mistake somewhere
13:05
<alkisg>
Do upload that file contents with copy/paste, maybe you mistyped something?
13:05
(preferences.d/stgraber)
13:05
<moldy>
http://pastebin.com/f5c055098
13:08
i am inside my client chroot, btw
13:08
maybe that explains different behaviour?
13:08
<alkisg>
Hm, let me try that..
13:10
Nope, it's fine for me: http://pastebin.com/m1b85a0b5
13:10
Did you add the ppa keys, to mark it as trusted?
13:10
<moldy>
yep
13:12avena has quit IRC
13:13
<moldy>
do you need to refresh anything after changing the preferences stuff?
13:14
<alkisg>
No
13:14
I did one apt-get update after adding stgraber's repository, but just that one time.
13:15
Why don't you also try outside of the chroot, just in case you have some other weird configuration in effect inside the chroot?
13:15
<moldy>
ok
13:17
outside of the chroot, it seems to work
13:18
umm, wait... now it seems to work inside the chroot as well? weird
13:19
hmm
13:19otavio has quit IRC
13:19ftherese has quit IRC
13:20
<moldy>
hmm... maybe it's because i used aptitude, not apt-get?
13:20
aptitude wants to upgrade ldm now, apt-get does not
13:21
<alkisg>
Ah, yes, aptitude also wants to upgrade for me too.
13:21ftherese has joined #ltsp
13:21
<alkisg>
Hmmm that's not a good thing :)
13:21
<moldy>
hm, ok
13:21
indeed
13:23
how do i tell apt to install a single package from the ppa now?
13:23
ah, never mind
13:27* alkisg wonders how synaptic behaves with priority=400...
13:29
<alkisg>
Bah, synaptic and update-manager also want to install the updates... even if I lower the priority to 100.
13:29
So that only works with apt-get? :O
13:30
moldy: got it. Only apt-get looks in preferences.d/*
13:30
Aptitude just looks in /etc/apt/preferences
13:31
So I think it'd be safer if you did `mv /etc/apt/preferences.d/stgraber /etc/apt/preferences`
13:43
<moldy>
alkisg: hm ok, thanks
13:48
<alkisg>
vagrantc: got some time for a couple of packaging questions? :)
13:50
<vagrantc>
alkisg: got some time to ask questions?
13:50
<alkisg>
:D
13:52
One is, I'm creating the whole tree structure in my source, e.g. ./etc/apache2/conf.d/sch-server.conf and usr/share/sch-server/* instead of having a "flat" structure and telling things where to go from my package.install file. Is that OK?
13:53
<vagrantc>
alkisg: you'll want to install it to debian/PACKAGENAME
13:53
<alkisg>
vagrantc: I mean this: http://paste.ubuntu.com/330534/
13:55
That's my *source*, and the tree structure shows where things will finally be installed - but I saw in the ltsp packages that you don't do that, but use e.g. a lot of entries in debian/ltsp-server.install instead...
13:56
While my debian/sch-server.install just says to copy my whole etc dir to the system /etc
13:56
...and while that looks easy for me, maybe it's wrong?
14:00
<vagrantc>
if it works, what's wrong with it?
14:00
<alkisg>
I don't know, I was worried about directory "ownership" of the package system?
14:00
Seems to work fine to me
14:00
<vagrantc>
should be handled by your debian/rules file calls to dh_*
14:00
<moldy>
is there any documentation ltsp-build-client.conf?
14:02
<alkisg>
`ltsp-build-client --extra-help` - I don't know of any documentation about ltsp-build-client.conf..
14:02
vagrantc: Another question is, I want to install that file: /etc/apache2/conf.d/sch-server.conf. That would be a conffile, I guess. But that directory belongs to apache, am I OK in having a file there belonging to my package?
14:02
<moldy>
alkisg: yeah, i am wondering which of the options from --extra-help are supported in the config file
14:02
<alkisg>
Or should I just copy it there in postinst?
14:03
<vagrantc>
ltsp-build-client.conf is simply sourced from ltsp-build-client
14:03
moldy: most of the commandline options have correlary uppercased variable names
14:03
alkisg: yeah, otherwise all those *.d directories would be nearly useless :)
14:04
<alkisg>
Nice :) :)
14:04
<vagrantc>
alkisg: it's not so fussy about directories
14:04
<alkisg>
I tried to put a symlink in /var/www, and when the package was removed, I got a warning about "/var/www not empty so not removing it" and that got me worried :)
14:04
<moldy>
vagrantc: then i am doing something wrong :)
14:05
<vagrantc>
moldy: look in /usr/share/ltsp/plugins/ltsp-build-client/* for the relevent plugins and variable names.
14:05otavio has joined #ltsp
14:05
<moldy>
vagrantc: thanks
14:06
<vagrantc>
alkisg: that's just dpkg being a little too verbose
14:06
<alkisg>
vagrantc: and a last one for now, I want to put some configuration files that need to be changed in postinst. E.g. I need to create an /etc/dnsmasq.d/sch-server.conf file that has the IP of the server there. So I'm thinking of providing an example in /usr/share/docs/sch-server, copying it to /etc/dnsmasq.d, and modifying it from postinst. Sounds OK?
14:07
(of course those won't be conffiles, and I'll remove them from postrm if --purge is passed...)
14:07
<vagrantc>
alkisg: sounds good. though to be proper your postinst needs to respect changed values on upgrades and whatnot, which gets tricky fast.
14:08
<alkisg>
Nah, if the file exists I won't touch it at all :)
14:08
I know my limits :)
14:08
<vagrantc>
heh
14:08
<alkisg>
Thank you!
14:23nubae has quit IRC
14:33klausade has quit IRC
14:42nubae has joined #ltsp
14:55dfwlinuxguy has joined #ltsp
15:17mushroomblue has quit IRC
15:19
<moldy>
btw: the login problem still exists: new users can only login from some clients, but not from others
15:22
<alkisg>
moldy: did you try with xserver=vesa?
15:22mushroomblue has joined #ltsp
15:25alkisg has quit IRC
15:28alkisg has joined #ltsp
15:36alkisg has quit IRC
15:41IHS_Volunteer has quit IRC
15:49klausade has joined #ltsp
16:02wimiko has left #ltsp
16:02dfwlinuxguy has quit IRC
16:05adrianorg has joined #ltsp
17:27adrianorg has quit IRC
18:46pmatulis has quit IRC
20:51dfwlinuxguy has joined #ltsp
20:51
<dfwlinuxguy>
hi...anyone available that can help me with sound?
20:51
anyone here at all?
20:57
<Ryan52>
!question
20:57
<ltspbot>
Ryan52: "question" :: if you have a question about ltsp, please go ahead and ask it, and people will respond if they can. please also mention the linux distro and release you're using. :)
20:58
<Ryan52>
dfwlinuxguy: also explain more what your problem is and what you've tried so far, and have patience.
20:59
<dfwlinuxguy>
I am using debian lenny...pulseaudio and the sound works on my pxe boot clients, but the sound is way too low..I can't turn it up loud enough
21:00
I was using karmic and the sound was fine on one client I was using, but I couldn't boot my hp thin client from it (long time ubuntu fan, but damn karmic) so I switched to lenny
21:01
so I started using pulse audio because I had it working in karmic, but now the sound works, but the volume can not be turned up loud enough
21:02
I know sound on linux is a mess.....esd, pulse, oss, alsa..I have to admit that I'm not quite the expert in that area
21:09
also, I understand the dhcpd and tftp part of the whole thing, but I was wondering if there was some documentation I could read about how everything else works with ltsp. I congratulate the devs on the fact that ltsp "just works", but I'd like to understand it more at the lowest levels
21:21F-GT has quit IRC
21:26johnny has joined #ltsp
21:26
<Ryan52>
dfwlinuxguy: huh. IIRC there was some variable to set the volume.
21:27
<dfwlinuxguy>
where???
21:27
maybe I missed that
21:28
<Ryan52>
in lts.conf.
21:28
!doco
21:28
<ltspbot>
Ryan52: Error: "doco" is not a valid command.
21:28
<Ryan52>
!docs
21:28
<ltspbot>
Ryan52: "docs" :: For the most current documentation, see https://sourceforge.net/apps/mediawiki/ltsp/index.php?title=Ltsp_LtspDocumentationUpstream
21:28
<Ryan52>
oh my.
21:28
dfwlinuxguy: anyways, take a look at the docs, they might say...
21:30
<dfwlinuxguy>
thank you. I've been doing this for 12 years and I didn't just come here bothering everyone without doing some research. I've RTFM and everything else I could find. I was just hoping that someone had experience the same issue and could point me in the right direction
21:30
<johnny>
it has a list of all lts.conf vars
21:30
<Ryan52>
dfwlinuxguy: try setting PCM_VOLUME.
21:30
<johnny>
or should..
21:30
<Ryan52>
dfwlinuxguy: if not, trying changing VOLUME to 100.
21:30
<dfwlinuxguy>
PCM_VOLUME = 100 ????
21:30
<Ryan52>
sure.
21:31
19:30 < dfwlinuxguy> thank you. I've been doing this for 12 years and I didn't just come here bothering everyone without doing some research. I've RTFM and everything else I could find. I was just hoping that someone had experience the same issue and could point me in the right direction
21:31
I did just that.
21:31
those docs I pointed to, chapter 13 is where I got those variable names from.
21:32
<dfwlinuxguy>
yeah...I guess the delay is quite large on my end...thank you
21:39Selveste1 has quit IRC
21:39
<dfwlinuxguy>
I found a couple of examples at https://lists.ubuntu.com/archives/edubuntu-devel/2007-September/002394.html and https://lists.ubuntu.com/archives/ubuntu-users/2008-August/156071.html ...thanks to your suggestions...I'm doing a ltsp-update-image right now...I'll reboot in a second and see if that gets me anywhere....THANK YOU
21:39dfwlinuxguy has quit IRC
21:42dfwlinuxguy has joined #ltsp
21:42
<dfwlinuxguy>
well that didn't seem to do anything
21:43
I still have the same issue
21:44sene has quit IRC
21:44
<dfwlinuxguy>
thank you for the suggestion
21:45
I also have an issue where I can insert a USB keydrive into the client and it is mounted automatically, but cannot be un-mounted by anyone but root....I can deal with this fine, but I was hoping to make it a bit more friendly for my wife
21:51
i know that I can set it up in FSTAB so that this specific device could have the user option, but I was hoping there was a solution so that ANY device connected could be unmounted by root
21:51
sorry...by someone other than root
21:55
well thanks for the suggestions
22:00
would anyone be willing to say if esd or pulseaudio is easier to get setup and working correctly with ltsp and where definitive instructions on doing so can be found?
22:01
please?
22:13dfwlinuxguy has quit IRC
22:14
<Ryan52>
did I not tell him to have patience?
22:15dfwlinuxguy has joined #ltsp
22:15
<Ryan52>
dfwlinuxguy: have some patience.
22:16
dfwlinuxguy: or try asking at another time.
22:16
people might be afk or busy.
22:19
<johnny>
you don't unount them
22:19
dfwlinuxguy, you don't umount the devices
22:19
just unplug em
22:19
they get unmounted automatically after some small number of seconds or so after last access
22:20
esd is dead
22:20
pulse is required
22:20
it's automatic
22:20
no setting up
22:20
dfwlinuxguy, paying attention?
22:20
<dfwlinuxguy>
so if I am having issues with pulse, where to I go to find solutions?
22:21
<johnny>
well.. you understood about the devices right?
22:21
depends on if you can replicate the pulse issue
22:21
on a regular desktop session
22:21
if youc an't.. then here
22:21
if you can, in your distro support chat
22:21
<dfwlinuxguy>
I understand that the USB stick will be automatically unmounted
22:22
<johnny>
and don't use thin client session when troubleshooting with them.. keep it out of the problem altogether
22:22
<dfwlinuxguy>
the issue with pulse is a different story...it works, but the volume is very low and can't be turned up
22:22
<johnny>
if it turns out to be a normal problem on your distro that is..
22:23
<dfwlinuxguy>
I've tried everything and the volume is still too low
22:23
<johnny>
does it work fine in a normal session?
22:23
my clients don't have sound
22:23
so i don't know how it all works
22:23
you might need to try alsamixer in the ltsp local apps xterm
22:24
and change some other control
22:24
<dfwlinuxguy>
yes, I did..there is only one output device and it is turned up all the way
22:24
<johnny>
you need to see the part before pulse takes it over
22:24
i'm just not that familiar
22:24
you'll have to come back here during the week
22:24
<dfwlinuxguy>
what is the relationship between pulse and alsa?
22:24
<johnny>
when people who use sound with clients are about
22:25
alsa talks to the kernel.. pulse talks to alsa
22:25
<dfwlinuxguy>
wow....
22:26
I guess I can try back next week...thank you for responding
22:26
<johnny>
this channel is definitely more active during usa business hours
22:27
<dfwlinuxguy>
yes and it is the thanksgiving holiday...i understand
22:27
<johnny>
and sometimes european ones.. depending..
22:27
<dfwlinuxguy>
just a geek here that never rests
22:27
<johnny>
me too..
22:27
<dfwlinuxguy>
I really love LTSP
22:28
I understand the dchp and tftp parts of the whole thing...can you point to a guide in helping to understand the underpinnings of LTSP...I'd like to understand it better on a deeper level
22:28yanu has quit IRC
22:28
<johnny>
the docs
22:29
most of the deeper level is just standard linux tools
22:29
ltsp is just the glue that ties it altogether
22:29
<dfwlinuxguy>
it's amazing that it works so well
22:29
<johnny>
the docs desccribe how the system fits together iirc
22:29
well. thank the guys who build all the tools then too :)
22:29
ssh, X, and the like
22:30
<dfwlinuxguy>
I understand xdmcp sessions and the like, I was just wanting to find out more about pxe boot clients and how it is working over ssh
22:30yanu has joined #ltsp
22:30
<dfwlinuxguy>
It is unbelievable to me that more people don't use this
22:31
I've always been facinated by thin clients
22:35
well thank yo
22:37dfwlinuxguy has quit IRC
22:40pyxus has joined #ltsp
23:01Lumiere is now known as Ere
23:01Ere is now known as Lumiere
23:14dfwlinuxguy has joined #ltsp
23:17dfwlinuxguy has quit IRC
23:26usuario has joined #ltsp
23:28tinpardo has joined #ltsp
23:28
<tinpardo>
hi
23:29usuario has quit IRC
23:29tinpardo has left #ltsp
23:35tinpardo has joined #ltsp
23:35tinpardo has left #ltsp
23:57rjune has quit IRC
23:59F-GT has joined #ltsp