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


Channel log from 15 December 2006   (all times are UTC)

00:30chupacabra has quit IRC
00:48arc_ has quit IRC
01:35patrickb_ has quit IRC
01:36patrickb has joined #ltsp
01:37MoL0ToV has joined #ltsp
02:17galorin has joined #ltsp
02:41jsgotangco has joined #ltsp
02:42galorin has quit IRC
02:49Kodex has joined #ltsp
02:49Kodex has left #ltsp
02:51
<vagrantc>
!seen sbalneav
02:51
<ltspbot>
vagrantc: sbalneav was last seen in #ltsp 13 hours, 36 minutes, and 11 seconds ago: <sbalneav> should be heading to your inbox
03:01Egyptian[Home1 has joined #ltsp
03:03Egyptian[Home] has quit IRC
03:15meduxa has joined #ltsp
03:29jsgotangco_ has joined #ltsp
03:31jsgotangco has quit IRC
03:31jsgotangco_ is now known as jsgotangco
03:42bobby_C has joined #ltsp
03:42Avatara has quit IRC
03:42vagrantc has quit IRC
03:55
<jsgotangco>
ah
04:09jsgotangco has quit IRC
04:15bobby_C has quit IRC
04:26Avatara has joined #ltsp
04:46Empiric has joined #ltsp
04:58
<Empiric>
hi all
04:59
hay am getting anoid things
05:01
i have installed ubunbu with ltsp 4.2
05:01
server is going standby mode
05:01
i dont know why
05:01
am thinking
05:01
abt its going standby
05:14ogra has quit IRC
05:15ogra has joined #ltsp
05:16
<Empiric>
any idea
05:22cntb has joined #ltsp
05:22
<cntb>
\o
05:23
not been here foe ages
05:49egypcio has joined #ltsp
05:53Skarmeth has joined #ltsp
05:53chupacabra has joined #ltsp
06:05fxrsliberty has joined #ltsp
06:19MeBadMagic has joined #ltsp
06:33BadMagic has quit IRC
06:40MeBadMagic has quit IRC
06:41MeBadMagic has joined #ltsp
06:44GiantPickle has quit IRC
07:07andresmujica has joined #ltsp
07:13bobby_C has joined #ltsp
07:21bjohnson_ has joined #ltsp
07:28J45p3r_ has joined #ltsp
07:34Skarmeth has quit IRC
07:53ogra has quit IRC
07:54ogra has joined #ltsp
07:59fxrsliberty has quit IRC
08:07Stevec has joined #ltsp
08:11
<Darke-_>
ogra: Hi again, i just installed edubuntu i386 on a workstation, to test it out outside the regular network.. So i frealy can use it as dhcp-server etc
08:12
But now, it does not seem as if i got the ltsp packages installed..
08:12
and i cant find em with apt either.
08:12
and yes its 6.10
08:12
edgy
08:12
<ogra>
and installed from the install CD, not the live one ?
08:13
<Darke-_>
install CD
08:13
yes
08:13
<ogra>
(the live CD has no server bits at all)
08:13
<Darke-_>
crap
08:13
i got it from a college..
08:14
and he now say that it was a livecd he gaved me.. since i only had the amd64 cd..
08:14
sorry for bothering you :)
08:14
im gonna strangle him.
08:14
<ogra>
the install CD installs in textmode ... if you just hit enter at the bootscreen you are installing the ltsp server
08:19MeBadMagic is now known as BadMagic
08:22andresmujica has quit IRC
08:30J45p3r__ has joined #ltsp
08:35msinhore has joined #ltsp
08:37Arsenick-TC2L has quit IRC
08:38Arsenick-TC2L has joined #ltsp
08:42J45p3r__ has quit IRC
08:46mauricio has joined #ltsp
08:48J45p3r_ has quit IRC
08:58mauricio has quit IRC
08:59mauricio has joined #ltsp
09:00redguy_work has joined #ltsp
09:04
<redguy_work>
hi, I'm considering integration of LTSP into the PLD distro. According to http://wiki.ltsp.org/twiki/bin/view/Ltsp/IntegratingLtsp the LTSP bits I need are: ltspfsd, getltscfg, lp_server and ltspinfod. Where can I get sources to these pacakges? Is there any place where I can find more info on LTSP integration?
09:05mauricio has quit IRC
09:06mauricio has joined #ltsp
09:07
<ogra>
redguy_work, https://launchpad.net/people/ogra/+branch/ltsp/ltsp-mainline has the source for ltsp5
09:08
please use bzr to submit patches to integrate with your distro
09:08
(the above tree has the merged sources from debian and ubuntu and will soon get the integrated redhat bits as well)
09:10
redguy_work, apart from that, the best sources for info on ltsp5 are me, vagrantc, sbalneav and for redhat eharrison (but he's a rare guest here)
09:12MoL0ToV has quit IRC
09:12
<redguy_work>
ogra: as far as I understand, the (ed)ubuntu implementation of MueKow was the first one and all other (Debian and Red Hat) are based on this one. Correct?
09:12
ogra: and in fact : that implementation is the new LTSP 5, True?
09:13meduxa has quit IRC
09:14meduxa has joined #ltsp
09:14
<ogra>
well, the ubuntu one was the first one, but from a year ago to today debian particiapted a lot ... its rather a jiont effort nowadays
09:14
and yes, whats in (ed)ubuntu atm is the ltsp5 prerelease ...
09:15mauricio has quit IRC
09:16sbalneav has joined #ltsp
09:17
<sbalneav>
Morning all
09:17
<ogra>
sbalneav, scottie !!!!!!!!!!!!
09:17
<sbalneav>
Hey hey!
09:17
Power buttons for the win!
09:18
<ogra>
sbalneav, i just checked, sad to disappoint you, but acpi-support is installed by ubuntu-minimal
09:18
so its already there, no idea why you had to install it manually
09:18
and it wont solve session interaction
09:19
<sbalneav>
No, it won't do that, I know
09:19
But, it solves the "hung nbd-swap" problem for me.
09:19
<ogra>
really ?
09:19
thats intresting, because there is no code for it
09:20
<sbalneav>
Sure. If you're using GDM, and you have the users log out, and just press the powerbutton...
09:20
<ogra>
i discussed it with vagrant and we thought about having a pinger in nbdswapd
09:20
i dont use GDM anywhere in ltsp :P you know that ...
09:20
tell me next time if you talk about gdm ;)
09:20
<sbalneav>
if you've got ACPI turned off in the bios, so the machine "just turns off immediately", then the machine gets turned off immediately, but the swapper never gets shut down.
09:21
<ogra>
right
09:21
<sbalneav>
Some of us can't break our old habits. :)
09:21
<ogra>
if you have a proper shutdown sequence or ise ldm who shuts down nbd-client than its fine
09:21
s/ise/use/
09:21
ldm is lacking the integration with the acpi scripts ...
09:22
so it will do a hard shutdown ... since i dont want the whole shutdown sequence in ltsp at all
09:39Lumiere has joined #ltsp
09:39
<Lumiere>
hi all
09:40
anyone here know why a k12ltsp 5.0.0 upgrade would completely kill a computer?
09:50efra has joined #ltsp
09:50
<efra>
Hi everybody
09:52
<Lumiere>
hi
09:57
<sbalneav>
Lumiere: Define "completely kill"
09:57
Like, doesn't boot?
09:57
Smoked the computer
09:57
Went on a killing spree with 43 dead and 841 wounded?
09:57
what?
09:58
<ogra>
k12amok ?
09:58
<sbalneav>
:)
10:02BadMagic has quit IRC
10:04BadMagic has joined #ltsp
10:05pablo has joined #ltsp
10:07mrlinux has joined #ltsp
10:08
<pablo>
hi! ive installed ltsp 4.2 and followed the instructions said in ltsp page when i come to configure the services needed nfs says installed yes, enabled no and runnig yes i also have trouble whit dhcp an tftpd (im using ubuntu 6.06)
10:09dtrask has joined #ltsp
10:09J45p3r_ has joined #ltsp
10:09
<sbalneav>
pablo: Have you installed tftp?
10:09
<pablo>
tftpd: the ltspadmin utility cannt run tftpd (ive installed all the 3 packages that come wiht ubuntu 6.06 but ltspadmin says it cant make it run
10:10
it says its installed, its enabled but not running
10:10
same happens whit dhcp
10:11
when configuring tftpd via ltspadmin says: inetd: no process killed ... The signal has been sent to start tftpd, but it doenst appear to be running
10:11
<sbalneav>
What command did you run to install tftp?
10:12
<pablo>
first i did: apt-get install tftpd
10:13
tftpd was installed by apt but ltspadmin continued to say it could not make it run
10:13
then i tried apt-get install tftpd-hpa
10:13
<sbalneav>
You probably want tftpd-hpa
10:14
<pablo>
the same happended
10:14
then i tried atftpd
10:15
<sbalneav>
do this:
10:15
netstat -an | grep :69
10:16
<pablo>
i did it and thers no output in the consoile :(
10:17
<sbalneav>
grep tftp /etc/inetd.conf
10:17
<pablo>
tftp dgram udp wait nobody /usr/sbin/tcpd /usr/sbin/in.tftpd --tftpd-timeout 300 --retry-timeout 5 --mcast-port 1758 --mcast-addr 239.239.239.0-255 --mcast-ttl 1 --maxthread 100 --verbose=5 /tftpboot
10:18dtrask has quit IRC
10:18
<sbalneav>
Not familiar with that one.
10:19
I use tftpd-hpa, and the line to use for that one is:
10:19
tftp dgram udp wait root /usr/sbin/in.tftpd /usr/sbin/in.tft
10:19
pd -s /var/lib/tftpboot
10:20
then make sure the LTSP kernels get put in /var/lib/tftpboot.
10:20bobby_C has quit IRC
10:20
<pablo>
so... i will remove my tftpd server and install tftpd-hpa
10:20Egyptian[Home1 has quit IRC
10:24
<pablo>
i removed all tftpd stuff and did sudo apt-get install tftpd-hpa
10:25
<mrlinux>
why does flash crash on my clients
10:25
<pablo>
now doing a grep tftp /etc/inetd.conf says:
10:25
tftp dgram udp wait nobody /usr/sbin/tcpd /usr/sbin/in.tftpd --tftpd-timeout 300 --retry-timeout 5 --mcast-port 1758 --mcast-addr 239.239.239.0-255 --mcast-ttl 1 --maxthread 100 --verbose=5 /tftpboot
10:26
<mrlinux>
anyone know?
10:26
<pablo>
running ltspadmin and configuring tftpd still says it cant maker running tftpd :(
10:26
<Lumiere>
sbalneav: can't login, X's charset is dead
10:26
<pablo>
should i change inetd.conf file so it looks like yours?
10:32meduxa has quit IRC
10:34
<sbalneav>
pablo: what does netstat -an | grep :69 show now?
10:35Stevec has left #ltsp
10:35
<sbalneav>
mrlinux: Because flash is a crummy propriatary piece of junk.
10:37
<mrlinux>
so how do i fix this i need to know
10:38
sbalneav, so how do i fix this i need to know
10:43
<sbalneav>
Which version of flash?
10:43pablo has quit IRC
10:44
<mrlinux>
Shockwave Flash 7.0 r69
10:45
<sbalneav>
and does it crash always, or just sometimes?
10:45pablo has joined #ltsp
10:45
<mrlinux>
on the server it works on the clients it crashes
10:45
<sbalneav>
always, or sometimes?
10:45
You didn't answer that
10:46
<mrlinux>
always on the client
10:46
never on ther server
10:46
<sbalneav>
Have you set up sound?
10:47
<mrlinux>
i new i forgot some thing
10:47
how do i set up the sound
10:47
<sbalneav>
It's on our wiki
10:47
wiki.ltsp.org
10:49
<mrlinux>
thx
10:50
i cant find it
10:51
never mind
10:51Egyptian[Home] has joined #ltsp
10:52Egyptian[Home] has joined #ltsp
10:52Egyptian[Home] has joined #ltsp
10:52
<sbalneav>
Never mind, you found it?
10:53
<mrlinux>
your talking about esd right
10:56
how do i detect what version of ltsp i have
11:02pablo has quit IRC
11:03pablo has joined #ltsp
11:06SonnyBurnett has joined #ltsp
11:07g333k has quit IRC
11:09
<sbalneav>
mrlinux: cat /opt/ltsp/i386/etc/version
11:11
<mrlinux>
no such file or dir
11:13
<sbalneav>
How did you install this ltsp?
11:14
<mrlinux>
i didn't it was there i am using edubuntu
11:15
<sbalneav>
ah
11:15
wait
11:15vagrantc has joined #ltsp
11:15RiXtEr has joined #ltsp
11:16
<sbalneav>
What did you run to configure your ltsp?
11:16
<vagrantc>
sbalneav: hey there :)
11:17
<sbalneav>
vagrantc: hey hey
11:17
I updated the postinst in my packaging
11:20
<vagrantc>
sbalneav: ok.
11:20
<mrlinux>
nuthing i didn; config anything
11:21
<sbalneav>
I'm confued.
11:21
You say your running Ubuntu 6.06
11:21
Now you say you're running Edubuntu
11:22
First you say you installed ltsp from us
11:22
now you're saying your using the one that comes with edubuntu.
11:22
So, I'm not really sure what you're using.
11:22
Why don't we start this again.
11:22
What, EXACTLY are you running?
11:23RiXtEr has quit IRC
11:24
<mrlinux>
Edubuntu 6.10 the ltsp is the one that comes with edubuntu
11:25
afk have to go to the food court brb with in 10 min
11:28pablo has quit IRC
11:29pablo has joined #ltsp
11:29brich has joined #ltsp
11:30msinhore has quit IRC
11:30msinhore has joined #ltsp
11:30pablo has quit IRC
11:30
<mrlinux>
back
11:31pablo has joined #ltsp
11:32
<vagrantc>
we need to write a script that detect what distro is being run and if it's ltsp 4.x or 5.x
11:32
there's probably a few simple checks that would narrow it down pretty quickly.
11:33
<sbalneav>
mrlinux: ok, so is this a fresh install of Edubuntu 6.10?
11:33pablo has quit IRC
11:34pablo has joined #ltsp
11:36
<mrlinux>
yes
11:37
<sbalneav>
ok, then sound should work out of the box.
11:38
Have you tried booting a workstation?
11:38
ANd tested sound at all
11:38
i.e. play an .ogg file, or something?
11:39
<mrlinux>
ok i have to go and talk to a teacher be back in 10
11:41pablo has quit IRC
11:41pablo has joined #ltsp
11:45pablo has quit IRC
11:46pablo has joined #ltsp
11:52
<mrlinux>
havent tested sound i'll check
11:56pablo has quit IRC
11:56pablo has joined #ltsp
11:57fxrsliberty has joined #ltsp
11:58Envite has joined #ltsp
11:58
<Envite>
Hola a todos desde España
11:58
Hello all from Spain
11:58knowlton has joined #ltsp
11:59
<knowlton>
s
11:59pablo has quit IRC
12:00
<knowlton>
ogra: what kernel to recommend for smp machine in dapper?the k7?
12:00
or server?
12:00pablo has joined #ltsp
12:00brich has joined #ltsp
12:01
<knowlton>
Scottie?
12:02
<Envite>
knowlton: asking for linux kernel?
12:03
<mrlinux>
sbalneav, sound works
12:03
<sbalneav>
ok
12:03
<mrlinux>
sbalneav, so how do i fix my flash problem
12:03
<knowlton>
this is cliebow..
12:03
<sbalneav>
so how did you install flash?
12:04
<gentgeen__>
OT ... anyone with a Mac browser handy -- FF or Safari? If so could you look at http://www.pavcs.org/index2.html and check the 2nd and 3rd tabs
12:05
<mrlinux>
sbalneav, add remove applications
12:05knowlton has quit IRC
12:07knowlton has joined #ltsp
12:07
<knowlton>
Ho
12:08
<sbalneav>
mrlinux: Well, you can try to set in /etc/firefox/firefoxrc:
12:09
FIREFOX_DSP="esd"
12:09
That might help a bit, but will tend to make your firefox a bit more unstable.
12:10
<mrlinux>
do i do this on the client or server
12:11
<sbalneav>
On the server
12:12
<mrlinux>
ok i will try it
12:15
firefox won't open now
12:20
<sbalneav>
Well, try it at "auto" I suppose.
12:20pablo has quit IRC
12:21pablo has joined #ltsp
12:25
<mrlinux>
the sever firefox will start but the client wont
12:26
<sbalneav>
ok, well, best to set it back to "none" then.
12:29
<mrlinux>
sbalneav, what do you sugest
12:30
<sbalneav>
Did you set it back to none?
12:30
<mrlinux>
yes
12:30pablo has quit IRC
12:30
<sbalneav>
So, firefox loads now?
12:32
<mrlinux>
it opens
12:32
<sbalneav>
ok.
12:33
<mrlinux>
sbalneav, what do you sugest i do about flash
12:34
<sbalneav>
Well, flash has always had trouble in LTSP. Quite frankly, it wasn't designed to run in a thin client. We're currently working on a better sound architechture, which should work better with flash 9 when it comes out.
12:34
<mrlinux>
so i am sol right now your saying
12:35
am i SOL
12:35
<sbalneav>
Well, google around in the ltsp archives. It works for some, not for others.
12:36
The problems not with LTSP, but rather flash, which doesn't properly support network sound.
12:36
<mrlinux>
what would happen if i got the ltsp from LTSP.org
12:36
instead
12:36
<sbalneav>
Wouldn't make much difference.
12:36
Besides, we're switching over to LTSP5 anyway, and that's what's in Edubuntu.
12:37
<mrlinux>
figures
12:47david____ has joined #ltsp
12:47david____ has left #ltsp
13:06mrlinux has quit IRC
13:06i2ambler has joined #ltsp
13:06
<i2ambler>
Hello.. is there a way for me to have the jammin boot to GUI but the server boot in runlevel 3?
13:23
<sbalneav>
i2ambler: are you just trying to avoid gui on the console?
13:27GiantPickle has joined #ltsp
13:45
<brich>
Question about integrating ltsp5 into an rpm distribution (opensuse).
13:45
Is it working as described here?
13:45
http://wiki.ltsp.org/twiki/bin/view/Ltsp/MueKow#Steps_to_build_the_LTSP_Root_Tre
13:46* vagrantc checks
13:46
<brich>
Is there a more update to date version of the fedora attempt to integrate ltsp? The fedora ltsp integration is described at:http://wiki.ltsp.org/twiki/bin/view/Ltsp/MueKow#Fedora_Core_3_Testing
13:46* vagrantc hasn't seen *anything* from the fedora folks.
13:46
<vagrantc>
hey have been quite secretive.
13:47
brich: the Steps_to_build_the_LTSP_Root_Tree thing is theoretical.
13:47ogra has quit IRC
13:48
<vagrantc>
brich: we developed an implementation for debian and ubuntu that is hopefully flexible enough for other distros to plug into.
13:48
<brich>
I justed started to look at the ubuntu wiki ThinClientIntegration page.
13:48* vagrantc looks for links to more info
13:48
<brich>
But there are a lot of links
13:49
<vagrantc>
http://wiki.ltsp.org/twiki/bin/view/Ltsp/Ltsp5
13:49
<brich>
That's a start....
13:50
<vagrantc>
http://wiki.ltsp.org/twiki/bin/view/Ltsp/IntegratingLtsp
13:50
<brich>
I would like to know which packages are really needed, checking now.
13:50
<vagrantc>
though the "more details" bit is missing some of the most important stuff :(
13:50
<brich>
ps: I have seen the ltsp wiki pages that you refer to.
13:51
<vagrantc>
the wiki pages don't really get into the nitty-gritty how to implement it...
13:51
<i2ambler>
yeah, just trying to avoid GUI on the server. however, gui on the ltsp.
13:51
<vagrantc>
but i can explain it.
13:51
<i2ambler>
looks like i can just comment out the default server in defaults.conf
13:52
<brich>
vagrantc : please tell me :)
13:52
I assume the needed modules are:
13:52
ltsp_core ltsp_kernel ltsp_libusb ltsp_localdev ltsp_pciutilsltsp_perl ltsp_scanners ltsp_vnc_module ltsp_x_addtl_fonts ltsp_x_core
13:52
<vagrantc>
brich: modules?
13:52
<brich>
ltsp_core ltsp_kernel etc
13:53* vagrantc knows nothing of such modules.
13:53
<brich>
You know the knows of ltsp4
13:53
<vagrantc>
are these form the LBE ? the LBE is no longer a part of ltsp5
13:53
<i2ambler>
the ones you can download from ltspadmin
13:53
<vagrantc>
the idea is to use as much code as possible from the distro itself.
13:54
<sbalneav>
No, you wouldn't use those at all.
13:54
You'd be using your distro's packages.
13:54
<brich>
Yes I know, but...
13:54
The distro pkgs should be what those modules provided
13:55* vagrantc attempts to write a howto on the fly
13:55
<brich>
I'll provide a list of packages, it's quite a lot:
13:55
audiofile aumix bash busybox e2fsprogs esd freetype getltscfg glibchaltsys kernel lbuscd libgcc_s libpng libusb libvncserver localdev lp_server
13:55
ltspfsd ltspinfod ltsptree module-init-tools modules ltsp_nasd nbd ncurses
13:55
net-tools nfs-utils open openssl pam pci_scan pciutils perl popt portmap prep_swap sane snmpd ssh startsess sysvinit tcp_wrappers udev udev-rules util-linux
13:55
vidlist vnc-module x-core x-fonts xinetd ypbind zlib
13:55
<sbalneav>
Sure. To get the "base" functionality, you'd need: a kernel, and enough infrastructure to support xorg in XDMCP or ssh tunnelling mode using either sdm or ldm
13:56
<brich>
These are the pkgs that were used with ltsp4. I assume that I should get the similar ones from
13:56
my distro and have those installed in /opt/ltsp
13:56
<sbalneav>
At a bare minumum, yes.
13:56
<brich>
with chroot
13:56
<sbalneav>
yes, with chroot.
13:56
<vagrantc>
brich: ok. here's a different approach.... install the absolute minimal system for your distro into a chroot.
13:56
brich: install kernel, X, nbd.
13:56
done.
13:57
<brich>
Is that all?
13:57
What about X?
13:57
<vagrantc>
brich: install kernel, X, nbd.
13:57
<brich>
;)
13:57
<sbalneav>
You'll need X as well
13:57Gadi has joined #ltsp
13:57
<vagrantc>
so, there's obviously more to it, but that summarizes the concept pretty well.
13:58
<brich>
The more to me is: where are the sources for ltspadmin, ltspconfig etc?
13:58
<vagrantc>
it's probably best not to try and translate what was needed in ltsp 4.x to ltsp 5.x
13:58
<brich>
vagrantc: why not?
13:59
<vagrantc>
brich: because it's probably just easier to meet the requirements for ltsp5 in your distro, as the correlations don't always exist.
13:59
but maybe that's just my twisted view of the world, having never done anything with ltsp 4.x, and written a lot of ltsp 5 :)
14:00
<brich>
Okay. Besides kernel, ndb and X I assume that busybox, ssh and such modules are needed too.
14:00
<vagrantc>
bzr get http://people.ubuntu.com/~ogra/bzr-archive/ltsp/mainline/
14:00
<brich>
Thanks.
14:01
Can you refer to the src debian pkgs too?
14:01
<vagrantc>
http://packages.debian.org/src:ltsp
14:01
<brich>
I assume that there no src.rpms available yet?
14:01
YOu read my mind, thanks!
14:01
<vagrantc>
not that i'm aware of.
14:01msinhore has quit IRC
14:02
<brich>
Is ldm really needed?
14:02
<vagrantc>
so, there are two components- the server side (ltsp-build-client) and the client side (the ltsp-client* init scripts)
14:02
no.
14:02
<brich>
It looks to me, it's for a vpn kind of thing.
14:02
<vagrantc>
it allows to do nice stuff with ssh tunnels that are challenging to do through XDMCP
14:03msinhore has joined #ltsp
14:03
<brich>
Something for later, I presume.
14:03
<vagrantc>
the server-side scripts leave a lot of room for sharing code between distros. the init scripts currently need to be rewritten to make more code sharing possible.
14:04
the init scripts are in debian/*init
14:04
just to give you an idea of what they do ...
14:04
<brich>
you really read my mind!
14:04
Where is debian init?
14:04
<vagrantc>
?
14:04
<brich>
Can you refer to the scripts on the web?
14:05
Do you mean:
14:05
<vagrantc>
i don't know of a browseable location at the moment.
14:05
<brich>
http://people.ubuntu.com/~ogra/bzr-archive/ltsp/mainline/server/plugins/common/
14:05
<vagrantc>
yes, that's the plugin infrastructure.
14:05J45p3r_ has left #ltsp
14:05* vagrantc wonders how current that URL is, though ...
14:06
<vagrantc>
definitely old ... i know some of that code was updated in the last two months.
14:06
brich: i really would recommend downloading a branch with bzr.
14:06
<brich>
Hmm...
14:06
<vagrantc>
brich: i don't think there's any up-to-date web-viewable repositories.
14:07
<brich>
understand.
14:07
That's a pity btw.
14:07
<vagrantc>
it's not very big.
14:07
i suppose it wouldn't be hard to set up a cron job to do daily updates ...
14:07
<brich>
But it is different, and I never used bzr. Again something new to learn.
14:07
<vagrantc>
and publish to the web ...
14:08
<brich>
Where are the plugins used for?
14:08
<vagrantc>
bzr is pretty nice. it has two bugs in it i really hate. and i really wish it had useable support for gpg-signed commits ... but overall i really like it.
14:08
brich: the plugins are called by ltsp-build-client, which is responsible for building the /opt/ltsp/ARCH chroot(s)
14:09
<brich>
Is there a more detailed description about the ltsp-build-client, how it works?
14:09
<vagrantc>
i'm giving it right now. someone logging? :)
14:10
<sbalneav>
ltspbot is
14:10
<ltspbot>
sbalneav: Error: "is" is not a valid command.
14:10
<sbalneav>
hush up, you
14:10
:)
14:10
<brich>
I'll definately save this, but it is in html
14:11
<vagrantc>
brich: essentially, ltsp-build-client calls each of the plugins in alpha-numeric order. it loads all plugins from the "common" plugin directory, and the distro-specific plugin directory (e.g. Debian, Ubuntu, OpenSuSE)
14:12
brich: if there is a plugin of the same name, the distro-specific plugin is called.
14:12bobby_C has joined #ltsp
14:12
<brich>
How does it know, on which distro it is running?
14:12
<vagrantc>
brich: there are several phases that each plugin is called in...
14:12* vagrantc vaguely recalls documenting this somewhere ...
14:12
<brich>
Is there a config file, or it /etc/*release used?
14:13
<vagrantc>
lsb_release is used to determine distro.
14:13
but other options are possible.
14:13
<brich>
okay
14:13* vagrantc looks at server/doc/plugins
14:14
<brich>
Is the lsb_release called by the client (during its boot). If so the package providing lsb_release
14:14
<vagrantc>
commandline: builds the list of commandline arguments supported by the loaded plugins
14:14
<brich>
is to be installed in the chroot /opt/ltsp as well
14:14* vagrantc is only talking about ltsp-build-client right now
14:14
<vagrantc>
configure: sets variables for commandline options that are set
14:15
before-install: before the initial chroot is built
14:15
install: where the initial chroot is built (debootstrap, on debian systems)
14:15
after-install: additional package installation(ltsp-client), tweaks, etc.
14:15
finalization: the last steps needed, such as installing kernels, copying the kernels and
14:15
network bootable images into the tftp dir, installing the server's ssh keys
14:15
into the chroot, etc.
14:16
brich: at the moment, we don't make use of lsb_release in the chroot, but i would like to move towards using it there.
14:16
<brich>
okay.
14:16
<vagrantc>
ok, so that's plugins in a nutshell. :)
14:16
<brich>
about the debian/init scripts. Do you refer to those:
14:16
etc/init.d/ltsp-client misc/ltsp-client
14:16
etc/init.d/ltsp-client-setup misc/ltsp-client
14:16
<vagrantc>
yes.
14:17
<brich>
That's taken from ltsp-client client
14:17
<vagrantc>
right.
14:17
<brich>
What do I need to start with, from those pkgs:
14:17
<vagrantc>
that's where almost all of the client-side configuration comes in....
14:17
<brich>
ldm, ltsp-client, ltsp-client-builder, ltsp-server, ltsp-server-standalone
14:17
<vagrantc>
what do you mean by start with?
14:18
<brich>
I have nothing right now on opensuse.
14:18
So I have to start at zero.
14:18
I need to start building pkgs.
14:18patrickb_ has joined #ltsp
14:18galorin has joined #ltsp
14:19
<brich>
I would think that ltsp-client and ltsp-server-standalone are suffient, isn't it?
14:19
<vagrantc>
i would start by trying to build a chroot using ltsp-server's ltsp-build-client + ltsp-build-client's plugins.
14:19
<brich>
Okay!
14:19
<vagrantc>
ltsp-server-standalone does almost nothing.
14:19
<brich>
ah, I see.
14:19
It procides the dhcpd config file ;)
14:20* vagrantc doesn't see why it deserves it's own package.
14:20
<brich>
Is lts.conf still stored in: /opt/ltsp/i385/etc/lts.conf?
14:20
<vagrantc>
by default, there is no lts.conf ... but that drives people crazy so maybe that will change.
14:20
lts.conf is only needed if you need to do something other than the defaults ...
14:21
<brich>
But when something else is needed, than it is located in /opt/ltsp/i386/etc/lts.conf, isn't it?
14:21
<vagrantc>
brich: once you have built a chroot with a reasonable approximation of the right packages, i'd work on adapting the ltsp-client init.d scripts
14:21
brich: on i386, yes. :)
14:22
<brich>
Where are the plugins stored, and which debian pkg provides them?
14:22
<vagrantc>
ltsp-server provides the ltsp-build-client plugins.
14:22
they are in /usr/share/ltsp/plugins/ltsp-build-client/[common|DISTRO]
14:23
<brich>
Yes I see them know.
14:23
s/know/now/
14:23
vagrantc: thanks sofar. for the moment I have enough information to start, I think.
14:24
<vagrantc>
feel free to ask questions.
14:24
<brich>
Good information, would be nice to have it available in a wiki.
14:24
<vagrantc>
ogra and myself are probably the most experienced with it. sbalneav and dberkholz have also messed with it some.
14:25* vagrantc is editing the wiki right now.
14:26
<brich>
vagrantc: CU, thanks a lot for your help!
14:39Arsenick-TC2L has quit IRC
14:45galorin has left #ltsp
14:50* vagrantc updated http://wiki.ltsp.org/twiki/bin/view/Ltsp/IntegratingLtsp
14:50egypcio has quit IRC
14:52
<Envite>
bye all!
14:52Envite has left #ltsp
14:59bjohnson_ has quit IRC
15:09joebaker has left #ltsp
15:12* vagrantc is wiki-challenged
15:12
<vagrantc>
could someone give me a HARD TO USE interface that i can ACTUALLY USE? :)
15:12
<brich>
vagrantc: I just printed the updated ltsp5 wiki page, thanks for updating!
15:13
<vagrantc>
more updates on the way
15:14
i think i'm done fighting with wiki for the day.
15:23Gadi has left #ltsp
15:23* vagrantc could not figure out bulletts
15:24* vagrantc wonders if Ltsp5 shouldn't be more prominent on the main wiki.ltsp.org page
15:24efra is now known as efra_away
15:24* efra_away is away: I'm out to lunch | Sali a comer
15:26LordVorp has joined #ltsp
15:35Lumiere has quit IRC
15:48
<brich>
vagrantrc: where can I obtain the packages: ltspfsd getltscfg lp_server ltspinfod
15:48
can you link to them?
15:49
About:
15:49
"a good first step is to gain an understanding of server/ltsp-build-client. this is the tool used to generate your /opt/ltsp/i386 (or other arch) chroot."
15:49
<vagrantc>
i can find some info about ltspfs, getltscfg is included in the bzr repository, lp_server was included in the bzr repository, but should be removed for unclear licensing, no idea with ltspinfod
15:50
<brich>
Is the /opt/ltsp/arch chroot build each time the client boots, or just once when the server is installed
15:50
<vagrantc>
just once
15:50
it is what is exported over NFS
15:50
<brich>
Can you add that information to the wiki?
15:50
<vagrantc>
i can try ...
15:51
<brich>
I guess other people reading your info, might have the same question(s)
15:51BilboFett has joined #ltsp
15:51
<BilboFett>
I'm looking for a general server log?
15:51
<vagrantc>
/var/log/syslog or /var/log/messages?
15:51
<BilboFett>
hmm
15:52
<brich>
How is the /opt/ltsp kept in synch with than? I mean when the distro packages get updated , how is the /opt/ltsp/arch
15:52
chroot updated?
15:52
<BilboFett>
my district is req "the server log" so they can try to find out why it ran so badly yesterday
15:52
<vagrantc>
brich: yes, you would need to update the chroot
15:52
<BilboFett>
my server isn't load balancing, isn't closing processes when done, lots of things
15:52
<brich>
But how?
15:52
<BilboFett>
they said "send us the log"
15:52
<vagrantc>
brich: on debian: chroot /opt/ltsp/ARCH apt-get update ; chroot /opt/ltsp/ARCH apt-get upgrade
15:52
<brich>
vagrantc: okay
15:53
vagrantc on opensuse it is the same, as apt is available for opensuse as well :))
15:54
<vagrantc>
ah, nice.
15:55
brich: i often configure a cron job to download the packages for me regularly.
15:55
<brich>
vagrantc: I'm the apt pkg maintainer for opensuse:))
15:56
<vagrantc>
i know almost nothing about opensuse
15:57
<brich>
vagrantc: in opensuse I added an option (/etc/sysconfig/...) to yast to configure such automatic update mechanism :)
15:58
<BilboFett>
vagrant I have messages, messages.1 .2 .3 .4 ?
15:59
theres nothing under /var/log/syslog
15:59
<vagrantc>
BilboFett: the .N ones are older ones- probably from previous days.
15:59
<BilboFett>
ok cool
16:00
so send em "messages" I guess
16:00
?
16:03efra_away is now known as efra
16:03* efra is back (gone 00:38:54)
16:05BilboFett has quit IRC
16:12chupacabra has quit IRC
16:12sbalneav has quit IRC
16:14chupacabra has joined #ltsp
16:19
<brich>
vgrantc: thanks to your updated wiki page, I have just checked out ltsp from bzr
16:19
But there is ltspfs there, see:
16:19
find client COPYING debian po server | grep -E "ltspfs|getltscfg|lp_server|Makefile"
16:19
client/getltscfg
16:19
client/getltscfg/Makefile
16:19
client/getltscfg/lexer.l
16:19
client/getltscfg/parser.y
16:19
client/getltscfg/lts.conf
16:19
client/getltscfg/COPYING
16:19
client/getltscfg/getltscfg.1
16:19
client/getltscfg/getltscfg.c
16:19
client/getltscfg/getltscfg.h
16:19
po/Makefile
16:20
What about Makefiles? Shouldn't there be more Makefiles to have the files installed, perhaps with a configure script?
16:23FernandoMM has joined #ltsp
16:30
<vagrantc>
brich: yes, ltspfs is a separate project.
16:30
brich: and sadly, it's scattered across the 4 corners of the earth.
16:31
<brich>
Why is it so scattered?
16:31
<vagrantc>
http://packages.ubuntu.com/edgy/misc/ltspfs
16:31
that's your more consolidated version.
16:32
<brich>
Can you add that to the wiki as well?
16:32
<vagrantc>
i don't know what to add.
16:33
there's numerous bzr branches, all in various states of our of sync, and no real publicly available tarball.
16:33
<brich>
The url, so others could use that to download.
16:33
Or add that ltspfs has:
16:33
there's numerous bzr branches, all in various states of our of sync, and no real publicly available tarball.
16:34
<vagrantc>
i don't even know where you're suggesting to add it.
16:34
<brich>
and needs to be organized, before others can make use of it...
16:34
<vagrantc>
if you want something done, do it yourself :P
16:34
that's the point of the wiki, no?
16:35
<brich>
Yes, I want. But what I want to do is to add ltsp5 to suse. For that I need information, you have given a lot
16:35
and need to do again, if the information is not available. I do a lot already!!
16:36
The point of a wiki is to add information, I don't have that information or at least I did not have it more than
16:36
2 minutes ago!
16:36
<vagrantc>
and i have little better information than you.
16:37
frankly, i'm very frustrated with ltspfs right now, for a variety of reasons, including the unclearness of a source of upstream.
16:37
that's also a problem with ltsp5, but not nearly as bad.
16:38
<brich>
vagrantc: I see your point of frustration now!
16:40
<vagrantc>
i'm also just now uncovering some bugs for debian/etch ltsp, shortly before a release...
16:40
which is probably adding to my ambient frustration...
16:41
<brich>
vagrantc: my frustation at the moment is that I can't login to the wiki, and the wiki does not seem to be able to send my password :(
16:41
<vagrantc>
ah yes, having to work with a wiki at all also drastically increases my frustrations. :)
16:42
i wish there were more wiki*fs filesystems.
16:42
<brich>
I don't twiki, but working with mediawiki is very nice actually.
16:42
<vagrantc>
or ikiwiki, which can use a subversion backend.
16:44
there was a commandline client for mediawiki i used for a while that worked decently. but the upstream makes it hard to package by making major code changes without any mention of it anywhere.
16:46
<brich>
Who could clear up the air around ltspfs? Would it possible to obtain a synergy there?
16:47
<vagrantc>
sbalneav and ogra are the main ones who've worked on it.
16:48FernandoMM has quit IRC
16:48
<brich>
Do you know, why ltspfs is not stored in bzr e.g.?
16:48
<vagrantc>
but in order to get more distros to integrate ltsp and related software, we need a more coherrent vision of "This Is Upstream".
16:48
oh, it's stored in bzr. but not all of it.
16:49
<brich>
I understand, but who is the current owner of ltspfs isn't that sbalneav
16:49
<vagrantc>
we've also got branches for ltspfs-upstream, minus all the debian bits, and several different "debian" directories, all by different people.
16:50
this is part of the problem with a decentralized revision control system. everyone has their own branch, and nobody's is current with the software that's actually released.
16:51
essentially, we're all upstream. :)
16:51
<brich>
There should still be someone taking the decision to take this or that code to be put in a distro...
16:51
This makes it impossible for other distro's to include ltsp, I think.
16:51
<vagrantc>
i've done most of the work for debian's ltsp packages, and ogra's done most of the work for ubuntu's ltsp packages. and that's about all we've seen.
16:52
<brich>
It should at least be clear where the upstream project is located...
16:53
<vagrantc>
for ltspfs, basically the closest thing to upstream is the tarball released by ubuntu.
16:53
and it moves the way ubuntu needs it to move.
16:54* vagrantc contemplates posting to ltsp-developer
16:55fxrsliberty has quit IRC
16:56
<brich>
okay
16:59
vgrantrc: do you know where ltspinfod can be obtained?
16:59
<vagrantc>
maybe try to rip it out of the LBE cvs?
17:00
i don't think we've messed with it for debian or ubuntu.
17:01
<brich>
I don't understand this... This way it is very very hard to integrate ltsp5 in another distribution.
17:01
Would it possible to have all code consolidated on 1 place? Whether it is bzr or the LBE cvs?
17:01
<vagrantc>
ltspinfod is probably not the most important thing.
17:02
<brich>
I know, but ...
17:02
but what?
17:02
<vagrantc>
think of ltspinfod as more of a goal, as nobody else has implemented it yet.
17:02
<brich>
Ah, okay.
17:02
<vagrantc>
eventually, it will probably be ripped out of LBE cvs and imported into the bzr branches, would be my guess.
17:02
that's what happened with getltscfg
17:02
<brich>
It would be good in that case to do not mention it on wikipage!
17:03
<vagrantc>
but getltscfg was more crucial, so it happened very early on.
17:03
i didn't write the top half of that wiki page :P
17:03
<brich>
Is it okay to remove it?
17:03
Do you know what is meant with:
17:04
"Install LTSP supplied packages into the tree" (item 2 on that same page).
17:04
I would think that it should not be stating pkgs, but scripts/executables isn't it?
17:04
<vagrantc>
well, ltsp 5 is essentially an implementation. the more of it you implement, the better. it's still under development.
17:08
<brich>
vagrantc: updated the top half of http://wiki.ltsp.org/twiki/bin/view/Ltsp/IntegratingLtsp
17:11brich has quit IRC
17:22msinhore has quit IRC
17:25
<vagrantc>
anyone with more twiki-fu than i want to touch up http://wiki.ltsp.org/twiki/bin/view/Ltsp/IntegratingLtsp
17:25
?
17:56g333k_work has quit IRC
18:09efra has quit IRC
18:35
<LordVorp>
I came in here to ask about boot-disks for non-rom ethernet cards. then I realized that rom-o-matic did that. then I was about to ask again because my boot disk wouldn't work... but I tried another computer and it worked perfectly.
18:35
LTSP ROCKS!
18:35
<vagrantc>
indeed.
18:35
there's also a cool floppy that does etherboot for many different ethernet cards: http://etherboot.anadex.de/
18:36
<LordVorp>
thx! I'll check it out
18:57fxrsliberty has joined #ltsp
18:59bobby_C has quit IRC
19:12fxrsliberty has quit IRC
19:50Stevec has joined #ltsp
20:16
<LordVorp>
SUH-WEET. P-166 w/ 32mb of ram and no HD booting as X thin client to my server in the other room.
20:19* vagrantc appreciates the enthusiasm
20:39Stevec has left #ltsp
21:23
<LordVorp>
well, knowing it can be done and actually getting it to work are, of course, two different things :)
21:24
just like, getting it to work with VMWare and getting it to work on a piece of actual hardware are two different things.
22:01
<vagrantc>
ah yes. for long stretches of time i have only had virtual thin-clients.
22:01
it's very nice to have the real deal again.
22:41PMantis has joined #ltsp
22:42
<PMantis>
!seen jammcq
22:42
<ltspbot>
PMantis: jammcq was last seen in #ltsp 2 days, 2 hours, 18 minutes, and 46 seconds ago: <jammcq> howdie
22:43PMantis has quit IRC
22:46
<vagrantc>
whoah.
23:40vagrantc has quit IRC
23:49gentgeen__ has quit IRC
23:57cstextiles has joined #ltsp