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


Channel log from 3 March 2008   (all times are UTC)

00:08
<vagrantc>
time for a new ltspfs upload :)
00:13
alright.
00:14* vagrantc wonders if any buildd's will be lagging when vagrantc gets off the train on the 7th
00:15
<vagrantc>
now it's only the mips buildd that's preventing ltsp and ldm from hitting lenny.
00:15* vagrantc is tempted to do binary-only uploads for mips
00:19rjune__ has joined #ltsp
00:19rjune has quit IRC
00:31steph__ has joined #ltsp
00:44steph_ has quit IRC
00:48steph__ has quit IRC
00:49steph__ has joined #ltsp
00:51
<warren>
vagrantc, hmm... fedora doesn't allow binary only uploads
00:52
vagrantc, where are you going?
00:55
<vagrantc>
warren: buffalo, ny
00:55
warren: ubuntu doesn't allow bin-uploads either
00:57
warren: although, to avoid confusion, a binary-only upload is just an upload with the architecture-specific packages built ... the source still has to be present in the archive
00:57
<warren>
I know
00:58
<vagrantc>
in debian, typically the maintainer's binaries are uploaded, and then all other architectures build the arch-specific binaries on buildd's ...
00:58
in general, i think it would be better if all binaries were built on the buildd's
00:59johnny_ has quit IRC
01:00
<warren>
I find it really strange that binaries are built as root
01:00
<vagrantc>
they're not really built as root
01:00
<warren>
oh?
01:00
<vagrantc>
fakeroot is used
01:00foxxbuntu has joined #ltsp
01:00
<warren>
binaries still run as root user though?
01:00
err builds
01:01
vagrantc, we use fakeroot in some builds in fedora, but fakeroot build processes are running as non-root, as are all builds. If something fails to build as non-root then it is a bug.
01:02
<vagrantc>
i'm not exactly sure with the buildd's ... i know there's a chroot involved, which requires root access of some form ... but i don't know if the build is run with some other user.
01:02
<warren>
every build in fedora a chroot is built up from scratch based upon the package's build requirements.
01:02
<vagrantc>
ditto for debian.
01:04
now, some developers/maintainers may be sloppy with their uploads... that's why i'm all for source-only uploads.
01:05
<warren>
Fedora enforces all behinds only from the centralized CVS
01:05
ww
01:05
wow
01:05
I can't do english
01:05
all BUILDS
01:06
<vagrantc>
there's so many fanboys of different VCS's in debian ... i can't fathom finding one that could be widely agreed upon
01:07
<klausade>
vagrantc: i'll test it, later when I have time. maybe next week. good work, look forward to test it.
01:12
<vagrantc>
klausade: would it be easier to test with sid or with a backport?
01:12
<klausade>
vagrantc: backport.
01:12
<vagrantc>
klausade: ok, i might not get a chance to build a backport till next week anyways
01:13
<klausade>
vagrantc: good.
01:13
<vagrantc>
i don't think the backport actually required anything other than re-building the source from sid
01:17foxbuntu___ has quit IRC
01:17
<vagrantc>
maybe i should just go ahead and build a backport, test it, and upload it :)
01:18
while i still have some time
01:20
ah, now i see what priority is used for
01:21
i just uploaded ltspfs an hour or two ago, and it's no higher than 30 in any of debian's buildd queues ... ldm was uploaded 11 days ago, and it's at 340 in the mips queue ... ltsp was uploaded 17 days ago, and it's 341 in the mips queue
01:21
ltspfs is priority optional, ldm and ltsp are priority extra ...
01:22* vagrantc wonders if vagrantc can make the case for priority optional with ldm ...
01:30chup has quit IRC
01:30chup has joined #ltsp
01:37foxbuntu___ has joined #ltsp
01:39daya has quit IRC
01:51steph__ has quit IRC
01:53foxxbuntu has quit IRC
01:55mikkel has joined #ltsp
02:02
<warren>
vagrantc, have you found that any clients need 8139too and not 8139cp?
02:02* warren is having trouble with 8139too and 8139cp conflicting
02:03
<warren>
vagrantc, kvm-62 supports virtualized e1000 with PXE support. Works so much better than the default rtl8139
02:06
<vagrantc>
warren: haven't say i've encountered the problem, though haven't really troubleshot such problems much either
02:06
<warren>
vagrantc, actually this began with later 2.6.23.x kernels...
02:06
it was fine in earlier 2.6.23 kernels
02:08
<vagrantc>
most of my installations are using 2.6.18 ... most development on 2.6.24
02:08* warren sleep
02:09
<vagrantc>
klausade: well, i went ahead and built the backported ltspfs, tested it, and uploaded it to the pkg-ltsp.alioth.debian.org repository
02:09
klausade: so whenever you want to test it out, feel free :)
02:12chupa has joined #ltsp
02:13chup has quit IRC
02:15
<vagrantc>
klausade: i haven't actually tested that icons show up, but it's creating the .desktop files, and the actual code is only slightly modified from your patch.
02:16
<klausade>
vagrantc: thanks. first a need to figure out why openoffice-calc crashes like snow melting in May, at a site with 1000+ users.
02:19
<vagrantc>
i made a silly mistake and didn't check the script in with the executable bit set ... but on future releases, you should just be able to symlink it to an appropriate location.
02:50chup has joined #ltsp
02:52chupa has quit IRC
02:52doggkatcha has joined #ltsp
02:54vagrantc has quit IRC
02:54
<doggkatcha>
anyone know how to enable local apps on opensuse 10.3 with kiwi-ltsp?
03:08doggkatcha has left #ltsp
03:20
<tarzeau>
HELP!
03:20
good morning
03:20
man ldm isn't very much helpful
03:20
doesn't it have config files?
03:20
i'd like to add a session for software that is not installed as debian package
03:33soneyka has joined #ltsp
03:40soneyka has quit IRC
03:53soneyka has joined #ltsp
04:00cyberorg has joined #ltsp
04:09Q-FUNK has joined #ltsp
04:19Q-FUNK has quit IRC
04:29soneyka has quit IRC
04:31chupa has joined #ltsp
04:33chup has quit IRC
04:34daya has joined #ltsp
04:40Nubae has quit IRC
04:46soneyka has joined #ltsp
04:46Q-FUNK has joined #ltsp
05:09mcfloppy has quit IRC
05:14chup has joined #ltsp
05:16chupa has quit IRC
05:29Guaraldo has joined #ltsp
05:36daya has quit IRC
06:05mhterres has joined #ltsp
06:17TelnetManta has quit IRC
06:26stgraber has quit IRC
06:26stgraber has joined #ltsp
06:34Q-FUNK has quit IRC
07:03joebaker has joined #ltsp
07:11Blinny has joined #ltsp
07:11
<Blinny>
Guten morgen
07:14cliebow has joined #ltsp
07:16
<jammcq>
jj/quit
07:16
oops
07:16jammcq has quit IRC
07:20alekibango has joined #ltsp
07:35chupa has joined #ltsp
07:35chup has quit IRC
07:44slidesinger has joined #ltsp
08:08TelnetManta has joined #ltsp
08:09
<TelnetManta>
Does anyone have a network with multiple PXE boot servers on the same subnet?
08:09
I want to use LTSP but we already have a PXE boot server on each of our subnets for os/software deployment.
08:12Daggett has joined #ltsp
08:14chup has joined #ltsp
08:16chupa has quit IRC
08:16
<cliebow>
TelnetManta, can you use 2 nics and isolate ltsp from reg network?
08:19Daggett has quit IRC
08:24
<laga>
you can probably use alternate dhcp ports
08:25
but that's not exactly easy to set up. i hear ipconfig in ubuntu initramfs doesn't suüpport it anymore and i have yet to prove ogra wrong :)
08:27
<joebaker>
laga: what's alledgedly broken with ipconfig?
08:27
<laga>
joebaker: the ability to use -p
08:27
<joebaker>
Do you mean ifconfig?
08:27
<laga>
no, ipconfig. from klibc-utils
08:28
<joebaker>
There are ip commands I'm becoming familiar with.
08:28
thanks.
08:29
<laga>
it's used by the initramfs to bring up the interface
08:29
part of the whole "early userspace" thing
08:29
<joebaker>
I have an idea what you mean by initramfs and early userspace thing.
08:30
So ipconfig might be a library, not a command.
08:31Gadi has joined #ltsp
08:31
<joebaker>
I see it is a command on my Edbuntu LTSP server.
08:32
/usr/lib/klibc/bin/ipconfig and again at: /opt/ltsp/i386/usr/lib/klibc/bin/ipconfig
08:32
<laga>
it's a command.
08:52Blinny has quit IRC
08:53mccann has joined #ltsp
08:56mikkel has quit IRC
09:01SLBFqtnt3 has joined #ltsp
09:01
<SLBFqtnt3>
!help
09:01
<ltspbot>
SLBFqtnt3: (help [<plugin>] [<command>]) -- This command gives a useful description of what <command> does. <plugin> is only necessary if the command is in more than one plugin.
09:02
<SLBFqtnt3>
help
09:03nookie has joined #ltsp
09:03
<nookie>
hello
09:03
<SLBFqtnt3>
!question
09:03
<ltspbot>
SLBFqtnt3: "question" is is if you have a question about ltsp, please go ahead and ask it, and people will respond if they can. :)
09:04
<SLBFqtnt3>
question
09:04
<nookie>
a little question : how can i do to make the ldm connect to the chroot env rather than the server env?
09:04
<SLBFqtnt3>
is it feasible to use LTSP on an 1.2 mbit network?
09:05
or a 100 mbit network is the absolute minimum?
09:08chup has quit IRC
09:08chup has joined #ltsp
09:08soneyka has quit IRC
09:09
<nookie>
a little question : how can i do to make the ldm connect to the chroot env rather than the server env? please i'm lost :)
09:09
<SLBFqtnt3>
question: is it feasible to use LTSP on an 1.2 mbit network? or a 100 mbit network is the absolute minimum?
09:10gentgeen__ has quit IRC
09:10Faithful has quit IRC
09:11Faithful has joined #ltsp
09:14
<tarzeau>
HELP!
09:15
who is working on ldm sources?
09:15
<nookie>
the ldm on a client just connect me on the server environment. how can i connect to the chroot?
09:18soneyka has joined #ltsp
09:18gentgeen__ has joined #ltsp
09:19
<sutula>
nookie: The purpose of ltsp is to connect you to the server's environment, not the chroot
09:20
<nookie>
okay so the chroot is just a way to have a system able to launch ldm correctly?
09:20Blinny has joined #ltsp
09:20
<nookie>
thanks for answering sutula
09:21
<sutula>
nookie: The chroot's purpose is to keep stuff the clients need in order to connect to the server
09:21
<Blinny>
Hardy Alpha 5 - I have a computer that has been booting for about 15-20 minutes now, and is slowly moving along. It just found the NICs and floppy. It's a Dell GX110 866mhz with 256MB RAM. Is this a known issue or should I be looking at fixing something?
09:21
The last time I tried this computer it booted well in LTSP 4.2
09:21
<nookie>
ok so it's useless to install some softwares on the chroot?
09:23
<sutula>
nookie: Well, it is possible to run apps locally on the client, but that takes a lot more understanding about how the whole system works. I don't know if there's a howto on that. Google might know.
09:23
<nookie>
i spent lots of hours on google searches :)
09:23
<Blinny>
You can install software in the chroot, but it's only easy to use if it's CLI software, not X stuff.
09:24
<nookie>
ok thanks
09:25
<Blinny>
nookie: Localapp support is in the roadmap I believe but I don't think it's anywhere near completion.
09:25
I am however far from a reliable expert on this.
09:26
<nookie>
ok
09:27
<ogra>
tarzeau, https://launchpad.net/~ltsp-upstream
09:31
<SLBFqtnt3>
question: is it feasible to use LTSP on an 1.2 mbit network? or a 100 mbit network is the absolute minimum?
09:31alekibango is now known as alekibangozku
09:33alekibangozku is now known as alekibango
09:36
<nookie>
thanks a lot, bye
09:36nookie has quit IRC
09:38
<daduke>
ogra: hola! where does ldm get its sessions from?
09:38* sutula finds http://wiki.ltsp.org/twiki/bin/view/Ltsp/LocalApps but nookie has quit :)
09:39
<ogra>
daduke, the latest versions from /usr/share/xsessions, former ones on debian and ubuntu from feedback of update-alternatives --list x-session-manager (and x-window-manager)
09:40
<tarzeau>
ogra: which version exactly? any tarball release ?
09:41
<ogra>
tarzeau, since its to be integrated by the distros, the one your current distro has ... beyond that use a bzr checkout
09:41
<daduke>
ogra: yes, tarzeau and daduke work together ;)
09:41
<ogra>
ah :)
09:41
swiss invasion :)
09:46
tarzeau, best is to apt-get source ldm from sid (assuming you are on debian as daduke is)
09:46
<daduke>
ogra: well actually I'm .de
09:46
<ogra>
vagrantc usually does regular checkouts if he considers the tree stable enough
09:46
daduke, oh
09:47
so that should get ou the latest tarball
09:47
<tarzeau>
is vagrant doing the debian/ubuntu packages?
09:47
<ogra>
he does debian
09:47
i do ubuntu
09:47
<tarzeau>
he should update it
09:47
since we had to pick the ubuntu version for some reason
09:47
<ogra>
i think he's currently blocked on a missing m68k build
09:48
<tarzeau>
m68k builds don't block new uploads
09:48
oh wait you mean some build-dependency?
09:48
<ogra>
if you split packages that were on m68k before it does
09:48
<tarzeau>
ah we got the alioth something package
09:48
<laga>
ogra: any idea on the timezone issue i reported last night? that's a bit of a showstopper for mythtv
09:49
<ogra>
he introduced a new source package for a binary that was built from ltsp source before .... since that was in etch on m68k he needs a rebuzild with the new setup before it enters lenny as i understood it
09:49Faithful has quit IRC
09:50
<tarzeau>
i hope he updates to the versions using /usr/share/xsessions/ for login session configuration
09:50
since we got some x window managers not registered by the package manager
09:52chupa has joined #ltsp
09:52chup has quit IRC
09:53
<ogra>
http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/vagrant%40freegeek.org-20080129163359-8my26388ksd3xilt?start_revid=vagrant%40freegeek.org-20080302085354-jqrtbmyy44wz53t3
09:53
thats the relevant patch to ldminfod
09:54
just change the ldminfor script on the server to provide what you want around line 121
09:54
*ldminfo
09:55
i thougth there was a newer checkout in sid already, that change is from end of jan.
09:59jammcq has joined #ltsp
09:59
<jammcq>
g'morning all
10:00
<daduke>
ogra: could I ask you to join irc://irc.ethz.ch/#isgphys for a minute?
10:03SLBFqtnt3 has left #ltsp
10:05dmorar has joined #ltsp
10:06
<dmorar>
Hi, im trying to get ltsp 5.0 on Gutsy, so far i have a ldm screen on my thin client, however unable to log in, i switched to tty1 and made a chroot passwd on the server, now i try to log in... with no success, what am i missing?
10:07
<Gadi>
dmorar: did you update the image with "ltsp-update-image" after you made changes to the chroot?
10:09
<dmorar>
Gadi, no, i dindt knew i had to do it... let me try...
10:09
Gadi: would you explain to me whats the pourpose of the image?
10:09
<Gadi>
also, if you made IP address changes and such, do: ltsp-update-sshkeys prior to ltsp-update-image
10:09
Gutsy does not use NFS
10:09
it exports a squashfs image over NBD
10:09
which improves speed
10:09
<dmorar>
Gadi, oic! nice!! :)
10:10
<Gadi>
downside is after every change to the image, you need to update it
10:10
not instantaneous like NFS
10:11
as a result, also, lts.conf is now in the tftpboot directory, and is d/l'd on boot
10:11
so, lts.conf changes do not require an image update
10:12
<dmorar>
Gadi, you are very kind :) .. now its working... no idea of the image... however, it takes like centuries on ldm: "verifying password"
10:12
is this normal?
10:14
<Gadi>
does it log you in eventually?
10:14
<dmorar>
where is eventually?
10:15
ahh
10:15
<Gadi>
I mean, when you log into ldm, do you get a desktop?
10:15
<dmorar>
yes
10:15
sorry, english isnt my first language, and i missunderstood you
10:16
<Gadi>
ah, ok, it just takes a few seconds to log in?
10:16
<dmorar>
gadi, yeah, but enough to be a little annoying to an user
10:17
when it logs in, its like a charm, really fast and cute
10:17bobby_C has joined #ltsp
10:18spectra has joined #ltsp
10:19
<Gadi>
dmorar: LDM is basically executing ssh, so if it takes a few seconds for you to ssh into your server, you may want to explore why that would be
10:19
that is, see if it happens with regular ssh as well
10:20
<dmorar>
Gadi: ok... ill get to that latter, first im going to enable local devs, since it isnt working.. (maybe this has changed too, im running kubuntu, so i know im not getting the desktop icon, however i know it will appear on Dirves inside my home, am i right?)
10:21
<Gadi>
no - no more ~/Drives - instead it appears in: /media/$USER/
10:21
and, I am not sure if it creates icons in kde automatically
10:22
but, I believe you should see a device in konqueror
10:23
<dmorar>
ok, its not working... have to check that out
10:29
Gadi: you said ltsp.conf isnt on the chroot but on the tftpboot, but i cant see it... should i create it ?
10:29
<Gadi>
yes - it goes in: /va/lib/tftpboot/ltsp/i386/lts.conf
10:29
<dmorar>
ok thanks
10:29
<Gadi>
*var
10:29
<dmorar>
:)
10:32staffencasa has joined #ltsp
10:36Q-FUNK has joined #ltsp
10:39sepski has joined #ltsp
10:43stoney has joined #ltsp
10:44
<stoney>
Hello?
10:44
<Gadi>
...Hello...Hello....Hello....
10:45
<stoney>
how r we today?
10:45milesd has joined #ltsp
10:45
<Gadi>
how r we today....today....today....
10:45
<milesd>
morning everybody. I tried to set up an ltsp environment last night so I could claim a bug and get involved but I couldn't get glibc to build
10:46
it kept complaining about how it couldn't find the sizeof long double
10:46
but when I ran the little test app myself, it seemed to work just fine
10:46
(the log file says "test application was" and gives some code)
10:46
anybody seen this? Is it a common problem?
10:46
<Gadi>
milesd: which ltsp is that?
10:46
<stoney>
i am working on a ltsp project with ubuntu. I can get the thin client to boot and I can log in but it stops at the gnome splash page
10:46
<jammcq>
building glibc ?
10:47
<Gadi>
stoney: look in the user's ~/.xsession-errors
10:47
<stoney>
is there a way to create a specfic image to push to thin clients?
10:48
looking to autologin ubuntu and open a rdp connection to win$ terminal server
10:48
let me look at the errors
10:48
<milesd>
Gadi, I pulled HEAD out of CVS
10:48
<Gadi>
rather than using an rdesktop screen script?
10:48
milesd: what CVS is that?
10:48
ltsp 4.2?
10:49
<milesd>
Gadi, multiple CVS's?
10:49
Gadi, ...I'm not sure
10:49
<jammcq>
if it's cvs, then its' 4.2 or older
10:49
<Gadi>
we don't have a build environment anymore
10:49
<jammcq>
no longer supported
10:49mcfloppy has joined #ltsp
10:49
<jammcq>
it's know for sure to not build on a 64-bit machine
10:50tux_440volt has joined #ltsp
10:50
<ogra>
milesd, https://launchpad.net/~ltsp-upstream the branches are hideen in the code tab
10:51
<stoney>
i want to use rdesktop just not familiar with it.
10:52
any examples?
10:52EDinNY has joined #ltsp
10:52
<milesd>
ogra, huh... launchpad, hu?
10:53
ogra, thanks
10:53
ogra, I'm not sure wehre I got the code I was building last night
10:53
<ogra>
milesd, that was surely old 4.x code
10:53
<milesd>
ogra, but I see some names on here that I recognize. Thanks for the ptr
10:54
ogra, yeah, I think you may be right
10:54
ogra, I'm at work right now but I'll hop on this when I get home tonight
10:54
<ogra>
with ltsp5 we completely switched to bzr from cvs
10:54
<milesd>
oh, thank god
10:54* milesd hates CVS
10:54
<dmorar>
Gadi: is there any place to troubleshoot sound on thin clients?
10:56
<ogra>
dmorar, thats very distro specific :) sound in debian is handled differently from ubuntu (no idea what fedora will use, thats still in the works)
10:56
<dmorar>
ogra im running gutsy
10:56
<ogra>
dmorar, then sound should just work out of the box
10:57
<dmorar>
ogra, im using kubuntu
10:57
<ogra>
whats wrong with it ?
10:57
oh
10:57
right, there it doesnt
10:57
either point your sound settings to alsa or esd
10:57
in the kcontrol tool
10:57
<dmorar>
lol, it doesnt at all?. or it doesnt works out of the box?
10:57
<ogra>
both should be covered
10:58
out of the box :)
10:58
<EDinNY>
can you view movies like .mpg files located on the server on an ltsp terminal? If you do, do you run them on the server and display them locally or run them locally?
10:58
<dmorar>
ogra i always get troubles with this, which one would you use?, esd or nasd?
10:58
<ogra>
the alsa layer is there but i'm not familiar with how to chaneg kde defaults, and nobody sent me a patch for such stuff yet
10:59
dmorar, both, asla and esd will be fine
10:59
dont use nas
10:59
*alsa
10:59
<dmorar>
alsa over the net?
10:59
<EDinNY>
jammcq, you here?
11:00
seen jammcq
11:00
no bots around when you need one
11:00
lol\
11:00
<ogra>
EDinNY, use an exclamation mark in front
11:00
dmorar, yup
11:00
<dmorar>
ogra is there a wiki of this?
11:00
<EDinNY>
!seen jammcq
11:00
<ltspbot>
EDinNY: jammcq was last seen in #ltsp 11 minutes and 16 seconds ago: <jammcq> it's know for sure to not build on a 64-bit machine
11:01
<EDinNY>
tnx ogra
11:01
<ogra>
dmorar, i still didnt manage to write one, sorry ask me if you got questions
11:03
<dmorar>
ok... i dont know where to start. i go inside kcontrol ... and select "enable network sound" (my kde is on spanish, something will be slightly different) , the i go inside Hardware tab and set audio device do Enlightened Sound Server
11:03
ogra should i set esd on lts.conf?
11:03
<ogra>
no
11:03
dont touch lts.conf
11:03
<dmorar>
ok
11:04
<ogra>
the bits and pieces you need are installed by default in the client... ldm setts up all sessin related bits for you
11:05
<jammcq>
EDinNY: hey
11:06
<EDinNY>
hi jim
11:06
how you been?
11:07
<ogra>
dmorar, you can check with aplay /usr/share/sounds/login.wav if the bottom layer works
11:07
that should play out of the client speakers in an ltsp session
11:07
<EDinNY>
jammcq: missed you...bouncing back and forth from here to a new system using the KVM switch
11:07
<jammcq>
EDinNY: been great. extremely busy
11:08
<dmorar>
PULSEAUDIO: Unable to connect: Connection regused, audio open error
11:08
<EDinNY>
I am thinking about using ltsp in a kiosk type application...can your run an mpg on the server and view it on a terminal?
11:08
<jammcq>
mpg?
11:08
<EDinNY>
mpeg
11:08
<jammcq>
like a movie?
11:09
<ogra>
dmorar, what kind of clients ?
11:09
<EDinNY>
yep
11:09
<jammcq>
heh, you should talk to gadi. he's doing cool things like that
11:09
<ogra>
dmorar, looks like the alsa HW detection didnt work on yout clients
11:09
*your
11:09
<EDinNY>
dmorar? you watching movies on terminals?
11:09
<dmorar>
ogra, if i go to tty i can hear the sound
11:09
EDinNY: not yet :)
11:09
<EDinNY>
oh, ok
11:10
<ogra>
dmorar, out of the clients speakers, right ?
11:10
<dmorar>
ogra yes
11:10
but on tty inside chroot (squashfs)
11:10
<ogra>
and not in konsole with the above command ?
11:10
<dmorar>
ogra, not in konsole
11:10
<EDinNY>
can you get it to run on the terminal? if there is enough memory?
11:11
<dmorar>
EDinNY: i dont undersand what you mean
11:11
<ogra>
dmorar, cat ~/.asoundrc.asoundconf |grep {
11:11
wghat does that give you in konsole ?
11:12
should return two lines
11:12
<EDinNY>
I need a way to display a movie...like with mplayer, on multiple terminals
11:12
or rather different movies on 2 or 4 terminals
11:12
<dmorar>
pcm.!default{ type pulse}
11:12
<ogra>
dmorar, right
11:12
<dmorar>
ctm.!default { type pulse }
11:12
<Gadi>
EDinNY: ogra tells me that mythbuntu folks have a mythtv-based ltsp thing
11:12
<ogra>
hmm
11:13
Gadi, i havent tested that at all yet, but laga is your man :)
11:13
<Gadi>
alternatively, look into vlc
11:13
<ogra>
its likely that it will be released as option of the mythbuntu install CD
11:13
<EDinNY>
Gadi: right! actually my 14 yo is playing with that...but it needs pretty hefty terminals
11:14
<Gadi>
I think it depends what does your decoding
11:14
<ogra>
dmorar, weird, looks all good ... can you check that pulseaudio started on the client during boot ? its started by the ldm display manager startup script
11:14
<EDinNY>
Gadi, from what he tells me, it looks like the terminal does...he has one linux "media center" project installed
11:14
<ogra>
(should be in teh processlist in tty on teh running client)
11:15
<Gadi>
EDinNY: its configurable
11:15
<EDinNY>
it is sitting in the den lol
11:15bjorn has joined #ltsp
11:15
<dmorar>
i dont see anything like pulseaudio , maybe another name for the process?
11:15
<ogra>
nope
11:15
<EDinNY>
guess I should be asking questions of him, but, like I said, that project seems to be running locally...will ask him
11:16
<ogra>
any errors on other consoles ? (check tty8)
11:16
(or tty0 )
11:16
<dmorar>
ok, now i see it... PULSE_SERVER=tcp:XXX.XXX.XXX.XXX:4713 ESPEAKER=XXXXXXXXXXX:16001
11:16
<ogra>
aha
11:17
yeah
11:17
the alsa message already indicated it was set right
11:17
and that the server isnt running in the terminal
11:17
did you fiddle anything with lts.conf ?
11:17
<dmorar>
on tty8: failed to detect any sound hardware, but as i said i can hear the sound beeing played on tty ...
11:18
<Gadi>
dmorar: dont confuse beeps with sound
11:18
<dmorar>
Gadi: i played the alsa/Noise.wav
11:18
<Gadi>
ah, ok
11:18
<dmorar>
on /usr/share/sounds/alsa
11:19
<ogra>
there was a bug with a race condition on very fast client HW wheer pulse tried to start while alsa was still detecting HW
11:19
i thought that was fixed though
11:19tux_440volt has quit IRC
11:19
<ogra>
what HW specs do you have there =
11:19
?
11:19
<dmorar>
core duo 1800
11:19
<ogra>
for the client ?
11:19
<dmorar>
ogra, yes.
11:20
<ogra>
lol
11:20
<Gadi>
nice
11:20
<ogra>
ok, that might be it then :)
11:20
<dmorar>
but i also have some pentium mmx
11:20
i cant try with them tough, they are running ltsp 4.2, im deploying an update
11:20
ogra, how do i fix it?
11:21
<Gadi>
dmorar: as a test do this at the tty1:
11:21
pkill -9 ldm
11:22
/etc/init.d/ltsp-client-core start
11:22
<ogra>
sudo cp /etc/init.d/udev /opt/ltsp/i386/etc/init.d/ && sudo ltsp-build-client
11:22
that *might* fix it (and slow down your boot)
11:22
err
11:22
urg
11:23
<dmorar>
ok, its working
11:23
<ogra>
s/ltsp-build-client/ltsp-update-image
11:23
<dmorar>
ogra, how do i fix it permanently?
11:23
<ogra>
the clients udev script has a patch to not wait o all devices ... which works fine on the majority of clients
11:24
that fixes it permanently
11:24
it makes the boot wait for udev to be done
11:24
<dmorar>
ogra, where do i get that patch?
11:24
<ogra>
which is silly on slow thin clients usually
11:24
just try what i wrote above
11:25
that reverts the patch
11:25
udo cp /etc/init.d/udev /opt/ltsp/i386/etc/init.d/ && sudo ltsp-update-image
11:25
err
11:25
sudo not udo :)
11:25
<dmorar>
ogra there is a problem with that
11:25
<warren>
Q-FUNK, ping
11:26
<dmorar>
ogra, like i said, i have both, new clients and old legacy clients, im afraid boot will go too slow on the old clients
11:26
<ogra>
try it
11:26
worst case you can have multiple client setups
11:27
<dmorar>
ogra, you are right, ill give it a try.. if it doesnt works ill set multiple clients setup.. thanks a lot :)
11:27
<ogra>
it can add about ten seconds to your boot i didnt say it has to :)
11:27
<Gadi>
you could probably also add the MODULE_01 for the sound card module for that client in lts.conf
11:27
<Q-FUNK>
warren: yup
11:28
<Gadi>
then, the module would come up early in the process
11:28
<dmorar>
Gadi: thats a very good choice too :)
11:28
<ogra>
Gadi, or in /etc/modules in the chroot, but that still wont give you the full alsa layer if youre unlucky
11:29
its a matter of testing :)
11:29
<Gadi>
right
11:29
<ogra>
hardy wont have that prob
11:29
<Gadi>
but, I bet by the time pulse comes around, with the modules loaded, alsa would be up
11:29
<ogra>
udev theer is a lot faster and doesnt have that hack ...
11:30
<Q-FUNK>
warren: just that without all 3 patches, you won't get any useful result.
11:30
<warren>
Q-FUNK, later in that mail I did indicate that I tried all patches.
11:30
Q-FUNK, it works but only at 800x600
11:31
<Q-FUNK>
800x600 is the fallback resolution. this indicated that DDC is not enabled. either your hardware doesn't have those pins connected or the bios has it disabled.
11:31
<dmorar>
Thanks a lot gadi and ogra, you were very helpful
11:31
<warren>
Q-FUNK, saw my Xorg.0.log? does that confirm that DDC is not available.
11:32
<ogra>
youre welcome :)
11:33
<Gadi>
de nada
11:34
warren: that xorg.log looked rather short
11:34
are you sure it was the whole thing?
11:35* warren looks again
11:36
<warren>
Gadi, yes, that's all
11:36
<Gadi>
(II) AMD(0): VESA VBE DDC read failed
11:37
yeah, ur DDC is not working
11:37
try specifying: Option "NoPanel"
11:37
in your driver section
11:37
of xorg.conf
11:38
also, is this with the patched xserver?
11:39Skarmeth has joined #ltsp
11:41indradg has joined #ltsp
11:43Abstract-yin has joined #ltsp
11:43vagrantc has joined #ltsp
11:50milesd has quit IRC
11:50Q-FUNK has quit IRC
11:50daduke has quit IRC
11:50yanu has quit IRC
11:51milesd has joined #ltsp
11:51daduke has joined #ltsp
11:51yanu has joined #ltsp
12:06Q-FUNK has joined #ltsp
12:13
<warren>
Gadi, patched in what way?
12:13
<Gadi>
warren: bart's patches
12:13
to xserver-xorg-core
12:13
(or fedora equivalent)
12:13
<warren>
Gadi, yes, this is with all of bart's patches
12:14
<Gadi>
ah, then it is just the BIOS that is not allowing for ddc
12:14
what BIOS is it?
12:14
<warren>
Gadi, Phoenix AwardBIOS
12:14
Gadi, TermTek TK-3500
12:14
oops
12:14
3355
12:14
or whatever i tis
12:15
Gadi, I got more than one of them rebadged from different sellers
12:15
god is it an awful machine
12:15
<Gadi>
lol
12:16
well, unless you can enable DDC through the BIOS, chances are its not wired up on the board properly
12:17
at least you *should* be able to force different modes in xorg.conf
12:17Abstract-yin has quit IRC
12:18daduke_ has joined #ltsp
12:18
<warren>
I can't devote more time to this specific machine
12:19
gotta get the base LTSP into shape
12:19
at least 800x600 works
12:20
<Q-FUNK>
warren: anything about DDC in their BIOS menu? which brand of BIOS, btw?
12:20
<Gadi>
(01:14:35 PM) warren: Gadi, Phoenix AwardBIOS
12:20
<warren>
Q-FUNK, i'll take a quick look...
12:21
<Q-FUNK>
ah
12:21
that rings a bell as being the one used in FIC products too
12:39
<warren>
Q-FUNK, I hope you can release 2.7.7.7
12:39
Q-FUNK, I want to shove something into F-9 today that might build with libpciaccess
12:40foefieslide has joined #ltsp
12:40
<Q-FUNK>
warren: I'm still waiting for Bernie to complete his libpciaccess patch.
12:40
<warren>
doh
12:41
<laga>
ogra: do you want/need a patch for the timezone issue then?
12:42phlashg has joined #ltsp
12:51dmorar has quit IRC
12:52
<foefieslide>
hiya anybody here came across Geode LX800 chipset vga driver
12:52
<Q-FUNK>
yup
12:53
<foefieslide>
my terminal halts or flickers just before log in screen
12:53
any other terminal works but these amd babies refuse to go get to log in screen
12:54
<Gadi>
foefieslide: try turning off the splash screen
12:54
<foefieslide>
i figured to add XSERVER = vesa or auto
12:54
<Q-FUNK>
foefieslide: which distro?
12:54
<Gadi>
oh, wait LX800
12:54
<foefieslide>
it passes the splash screen
12:54
edubuntu
12:54
<Q-FUNK>
release?
12:54
<Gadi>
you will need the patches
12:54
<foefieslide>
7.10
12:55
<Q-FUNK>
right, he needs my gutsy PPA
12:55
https://launchpad.net/%7Eq-funk/+archive
12:56
add the sources for the Gutsy repository, fetch the updates and rebuild the image
12:59indradg_ has joined #ltsp
13:00phlashg has left #ltsp
13:03
<laga>
ogra: /etc/init.d/ltsp-client-setup overwrites fstab on every boot. would you accept a patch to make that configurable for hardy?
13:03staffencasa has quit IRC
13:04
<vagrantc>
laga: wouldn't be hard to write a hook to add entries to fstab
13:05
<laga>
vagrantc: i'm working on fat clients so i'd prefer the standard way of just managing /etc/fstab normally
13:05
<vagrantc>
laga: sure, but a hook is available immediately.
13:06
<laga>
vagrantc: i can wait a few days. :)
13:06
<vagrantc>
laga: heh
13:06
laga: this still the mythtv stuff?
13:06
<laga>
although a hook sounds much better than forking ltsp-client-core. i'm already copying way too much, but LTSP never was intended for what i'm doing :)
13:06
vagrantc: yes
13:07
<vagrantc>
laga: i wouldn't say never intended, so much as not the first priority
13:07
<laga>
yes
13:07
it's looking pretty good now, though. i just keep finding quirks like the fstab issue
13:07
<Gadi>
laga: I have my own init script that runs after -setup and before -core to do the things that are way different than what ltsp is intended for
13:08
<vagrantc>
fat clients/diskless workstations was one of the reasons why ltsp5 was attractive
13:08
<Q-FUNK>
foefieslide: does it work better now?
13:08
<laga>
Gadi: i don't run -core at all. instead, i have my own init script which configures X (based on LTSP) if therE's no xorg.conf on the overlay directory.
13:08
vagrantc: yes, muekow makes it easier
13:09
<Gadi>
laga: -core does more than just configure x
13:09
<laga>
Gadi: i know. that's why i don't use it :)
13:09staffencasa has joined #ltsp
13:09
<Gadi>
gotcha
13:09
<laga>
Gadi: but i can't just add my own init script which undeletes /etc/fstab :)
13:10
<vagrantc>
laga: why not?
13:10
<Gadi>
yeah, why not?
13:10
<laga>
well
13:10
because it's deleted?
13:10
<Gadi>
its just another init script that references /etc/fstab
13:10
:)
13:10* Gadi doesnt understand
13:11
<vagrantc>
laga: there's got to be a way to un-unionfs something and just use the underlying file
13:12
or to copy the original file back on top of the unionfs
13:12
<laga>
Gadi: ltsp-client-setup overwrites /etc/fstab. that change is permanent because it's written to a "overlay directory" - i basically use a nfs share instead of tmpfs.
13:12
there's no way to recover it. just copying it from the squashfs isn't useful because each client should be bale to have their own fstab
13:13
<vagrantc>
laga: so you have a separate root filesystem for each client?
13:13
<laga>
heh. let me explain a bit better.
13:14
<vagrantc>
if you don't have a separate root filesystem for each client, you'd need something to customize it for each client anyways...
13:14
<laga>
there is one root file system (squashfs + nbd). there's also a "overlay" which is basically a NFS share. root file system + overlay together form the file system from which the client boots. i'm using aufs (another unionfs) for that
13:14
<Gadi>
and even if you do, fstab doesnt come into play until after the rootfs is there
13:14
laga: then, who cares about fstab?
13:14
<laga>
any changes made on the client go to the overlay directory.
13:15
<vagrantc>
and on each boot, it overwrites the overlay ...
13:15
<laga>
Gadi: people who want to mount stuff, like additional nfs shares for their media files?
13:15
vagrantc: no.
13:15
<vagrantc>
on each boot, ltsp-client-foo is overwriting /etc/fstab on the overlay ... currently.
13:15
<laga>
the overlay is persistent.
13:15
vagrantc: yes.
13:15
<Gadi>
right, but only the *additional* shares need be in fstab
13:15
<laga>
Gadi: yes! but fstab is overwritten every time the client boots!
13:16
<Gadi>
and they can be put there well after -setup
13:16
<vagrantc>
laga: so cache the fstab somewhere else
13:16
put it back
13:16
yes, a configuration option to not overwrite it would be easier :)
13:16
<laga>
yes :)
13:16
<vagrantc>
but still.
13:16
trivial to work around
13:17
<laga>
vagrantc: i'd like a proper fix which also makes it easier for future fat client projects
13:17
i mean, it's a two line patch..
13:17
<vagrantc>
sure.
13:17indradg has quit IRC
13:18
<stoney>
any luck running ltsp on hp thin clients?
13:19
<vagrantc>
laga: well, i'll commit upstream at least ...
13:19
laga: proposed variable name?
13:20
laga: KEEP_FSTAB ?
13:20
<laga>
vagrantc: the shell function is called configure_fstab, so..
13:20
vagrantc: yeah, sounds good.
13:20
<vagrantc>
i would have liked OVERWRITE_FSTAB ... but then we'd have to set a default to true elsewhere
13:20
PRESERVE_FSTAB
13:21
hm...
13:21
<Gadi>
CONFIGURE_FSTAB = N
13:21
(the function is called configure_fstab() )
13:21
<vagrantc>
again, that requires setting a default
13:21
to preserve historical behavior
13:21
<Gadi>
no - just make the code:
13:21
CONFIGURE_FSTAB = N && ....
13:22
<vagrantc>
if [ -n "$FOO" ] && boolean_is_true "$FOO" ; then ...
13:22chupa has quit IRC
13:22chupa has joined #ltsp
13:23
<Gadi>
if [ -n "$FOO" ] && ! boolean_is_true "$FOO" ; then ...
13:23
:)
13:23
<vagrantc>
or ... if [ -z "$CONFIGURE_FSTAB" ] || boolean_is_true "$CONFIGURE_FSTAB"
13:23
<Gadi>
nothing wrong with negatives
13:23
<vagrantc>
except they look stupid.
13:23
<Gadi>
your mother wears combat boots
13:23
:)
13:24
<vagrantc>
ok ... i'm going with the -z ||
13:24* laga hands out "support our troops" stickers to Gadi
13:24
<Gadi>
:D
13:27
<vagrantc>
laga: committed upstream
13:27milesd has quit IRC
13:29
<laga>
vagrantc: thanks. you're a star :)
13:29milesd has joined #ltsp
13:30
<vagrantc>
laga: and next debian upload
13:30
<laga>
vagrantc: now i need to poke ogra to put that in hardy
13:35abcc99x has joined #ltsp
13:36
<abcc99x>
hello, i have some very old machines with debian etch already installed, is there a way of booting into the ltsp server within the debian installation?
13:37
<vagrantc>
!debian
13:37
<ltspbot>
vagrantc: "debian" is is a GNU/Linux based operating system that makes an excellent LTSP server. You can find it at http://www.debian.org. for information about LTSP on debian see http://wiki.debian.org/LTSP
13:37
<vagrantc>
abcc99x: should be a howto mentioned on the wiki page
13:37
<abcc99x>
let me recheck =S
13:37
thanks
13:41
as far as i can tell the question i asked is not answered in that wiki
13:41
<vagrantc>
then i don't understand your question
13:43
abcc99x: oh, you want to connect to an LTSP server from a machine running off of a hard drive?
13:43
that really has little to do with LTSP
13:43
abcc99x: you could install the ldm package onto those machines, and write a custom init script to start LDM ...
13:44
<abcc99x>
thanks, let me see
13:44
<vagrantc>
abcc99x: there's an example ldm init script in newer versions of ldm, but i don't think in the version on etch
13:44
but the same script should work
13:45
abcc99x: or you could install ldm from the backports mentioned on the wiki.
13:45
<abcc99x>
yes, yes
13:45
<vagrantc>
but it would probably be easier to just set up LTSP ...
13:45
and use the hard disks for local swap, if needed.
13:46abcc99x has quit IRC
13:50
<foefieslide>
qfunk IT IS WORKING LIKE A BOMB - You've got the Funk
13:51foefieslide has left #ltsp
14:00
<vagrantc>
laga: funny thing is ... i think i tried to push the fstab configuration years ago...
14:00daduke_ has quit IRC
14:01stoney has left #ltsp
14:01
<laga>
vagrantc: why did you argue then? ;))
14:01
<vagrantc>
laga: i argued for doing what i just committed, and was shot down
14:01
<laga>
vagrantc: i think i have to write out a default fstab in my ltsp-build-client plugin now, though
14:01
or $stuff might explode
14:02
<vagrantc>
laga: there was a lot of stubborness early on and ideas i pushed for that were rejected and only now are getting comitted :)
14:02
<laga>
heh
14:02sepski has quit IRC
14:17Q-FUNK has quit IRC
14:19jtg23 has joined #ltsp
14:20
<jtg23>
hey all, i'm trying to run a fat client setup and had it working with one client, but now i'm getting strange errors as detailed here http://ubuntuforums.org/showthread.php?t=714080&highlight=pxe
14:21
is anybody familiar with troubleshooting issues like this? i can't find much info in the google
14:21
<laga>
jtg23: hum
14:21
jtg23: find out what driver (kernel module) your card uses.
14:21
then check if that driver is in the initramfs
14:22
<jtg23>
ok, i use the e1000 driver and when i boot w the hd, it works properly
14:23
so not to sound like a noob, but i'm not sure how to see if that driver is in the initramfs
14:23
<laga>
jtg23: and that's with LTSP?
14:23
how do you boot the client?
14:24
just pass in nfsroot=... ?
14:24
<jtg23>
ya
14:24
<laga>
jtg23: and if you don't add nfsroot, it works just fine and boots from hdd?
14:25
<jtg23>
ya, if i boot over the network it starts but then when it looks for my nic driver, it seems to fail--when i boot from the hd, on the other hand, it works fine
14:25
and goes online as exspected
14:25
sic
14:26
<laga>
ok
14:26Skarmeth has quit IRC
14:27
<laga>
then i'd suggest you create a new temporary directory somewhere and extract the initramfs. mkdir /tmp/newdir/ && cd /tmp/newdir/ && zcat /boot/initrd.img | cpio -i
14:27
then you can look around for e1000.ko
14:27
<Gadi>
gack
14:28
before you do all that, try adding "e1000" to /opt/ltsp/i386/etc/initramfs-tools/modules
14:28
<jtg23>
hmmmmm, when i search for e1000.ko, it's found in /nfsroot/lib/modules/2.6.22-14-generic/kernel/drivers/net/e1000/e1000.ko
14:28
<laga>
Gadi: he's _not_ using ltsp
14:28
<Gadi>
ah, nm
14:28
sorry
14:28
<jtg23>
yeah, i'm sorry, i'm doing fat client
14:28MeBadMagic has joined #ltsp
14:28
<laga>
jtg23: yeah, but it needs to be in the initramfs too
14:28
Gadi: although that'll be the next step :) (adding it to modules)
14:29
<jtg23>
ok, so i want mkdir /tmp/newdir or mkdir /nfsroot/tmp/newdir?
14:29BadMagic has quit IRC
14:30
<laga>
jtg23: it doesnt matter, just somewhere where it won't clutter up things. and it has to be the initramfs you're using to boot your system, so maybe you just want to boot that computer from hdd
14:31joebaker has quit IRC
14:33
<jtg23>
laga: i get cpio: premature end of archive
14:34
<laga>
jtg23: maybe that was the wrong file name. just pick the highest from /boot/initrd.img-2....
14:34
<jtg23>
ok cool
14:35
ok 39102 blocks?
14:35
<laga>
yeah
14:36
now you can see what was in there :)
14:36
<jtg23>
derrr ok i see
14:37
ok cool so i found the e1000 file in there...i need to wrap this up in my initramfs?
14:37otavio has quit IRC
14:38
<jtg23>
hmmm you know, this boot img is not the one i've been booting from via pxe; perhaps i have specified the wrong img
14:38
<laga>
ah, you booted from another image?
14:39* laga shrugs
14:39
<laga>
well, you gotta know your setup :)
14:39
<jtg23>
yah for sure, i think i get it now--but what i don't get is why this driver's been excluded from the ramfs up until now
14:41
<laga>
well, is it excluded or not?
14:41
i thought it was in there?
14:43Gadi has left #ltsp
14:43BadMagic has joined #ltsp
14:43
<jtg23>
laga: am verifying; it's in the boot img i just cpio'd at your behest, but i have to see if it's in the one i've netbooting off
14:44MeBadMagic has quit IRC
14:49
<jtg23>
laga: ok verified; indeed the e1000 driver is in that img
14:49
so doesn't that suggest it should load the driver on netboot?
14:50
<laga>
yes.
14:50
maybe you need to force it to load
14:51
<jtg23>
via modprobe?
14:51
<laga>
you can write a hook for that, eg based off /usr/share/initramfs-tools/hooks/fuse_utils
14:52
copy that file to /etc/initramfs-tools/hooks/e1000-load
14:52
and remove the copy_exec line
14:52
and write "force_load e1000" instead of "force_load fuse"
14:52
then regenerate your initramfs, eg using update-initramfs -u
14:53
of yourse, make sure the client boots the updated initramfs.
14:54otavio has joined #ltsp
14:54
<jtg23>
ok awesome
14:58
<vagrantc>
otavio: so, clearly, the priority "extra" is what's hurting ltsp and ldm ... ltspfs is priority "optional" and there's builds for almost all architectures...
14:58Q-FUNK has joined #ltsp
14:58
<otavio>
vagrantc: yes, you'd change it now
14:59Blinny has quit IRC
14:59
<vagrantc>
otavio: ltspfs was uploaded last night, and ltsp and ldm were uploaded 17 and 11 days ago ...
14:59
otavio: and still around 250th in the queue
14:59
<otavio>
yes. Consider to change it
14:59
<vagrantc>
otavio: would it be acceptible to do a binary-only upload for mips ?
15:00
<otavio>
vagrantc: yes
15:00
vagrantc: just find someone to do that (aurel32, tbm or someone else)
15:00
<vagrantc>
otavio: reading the descriptions in debian policy really make me think that priority "extra" is appropriate ...
15:00
otavio: why not me? :)
15:00
<warren>
Q-FUNK, the TK-3550 has no DDC in the BIOS
15:00
Q-FUNK, (no DDC options in BIOS)
15:00
<otavio>
vagrantc: you have a mips? that's ok then
15:01
<vagrantc>
otavio: i haven't yet gotten real mips harware working ... most of the stuff i have is unsupported ...
15:01
otavio: qemu works great though :)
15:01
otavio: but i suppose a build done on qemu is bad?
15:01
<otavio>
vagrantc: i'd prefer a real hw build
15:02
vagrantc: talk to them, they're friendly
15:02mhterres has quit IRC
15:02
<otavio>
vagrantc: just ask if they code help you on that since you do need to do another upload and mips is lacking for long time
15:02
<vagrantc>
otavio: where do i find them?
15:02
<otavio>
vagrantc: #debian-boot at oftc
15:02
vagrantc: they're d-i devels :-)
15:04cliebow__ has joined #ltsp
15:04
<cliebow__>
a
15:05jtg23 has quit IRC
15:08cliebow__ has quit IRC
15:09jtg23 has joined #ltsp
15:10
<jtg23>
vagrantc: are you vagrant from ptl fg?
15:10
<vagrantc>
jtg23: if you mean freegeek, yes.
15:11
jtg23: why do you ask?
15:11
<jtg23>
haha thanks for getting back to me last night
15:11
:) i'm here trying to torubleshoot my same issue
15:11
small world
15:12cliebow has quit IRC
15:14
<Q-FUNK>
warren: then it must be that DCC pins are simply not connected
15:14
warren: or that the companion chip's GPIO pins are assigned to something else
15:14
<warren>
Q-FUNK, oh well, not my problem
15:15Egyptian[Home] has quit IRC
15:16daduke_ has joined #ltsp
15:16
<Q-FUNK>
warren: but Gadi and I can both confirm that this thing does DDC just fine, if the pins are connected.
15:17Egyptian[Home] has joined #ltsp
15:28TelnetManta has quit IRC
15:30abstract-yin has joined #ltsp
15:31Q-FUNK has quit IRC
15:36Q-FUNK has joined #ltsp
15:37Guaraldo has left #ltsp
15:38jhp has quit IRC
15:54daduke_ has quit IRC
15:59Q-FUNK has quit IRC
15:59Q-FUNK has joined #ltsp
16:20
<warren>
Can you export only /opt/ltsp and /opts/ltsp/i386 is mountable?
16:20croto_ has joined #ltsp
16:22
<croto_>
hi!, can l change the root path other than /opt???
16:22
can I*
16:24abstract-yin has left #ltsp
16:24abstract-yin has joined #ltsp
16:24subsume has joined #ltsp
16:25
<subsume>
I am attempting to follow https://help.ubuntu.com/community/UbuntuLTSP/LTSPFatClients
16:25
but I am not understanding how to make the client machines link up to this
16:32stoney has joined #ltsp
16:35
<stoney>
anyone had issue pxe booting to edubutu using windows dhcp. i read over all the specs and actually had it working with dapper but edubuntu seems easier to manage
16:35
cannot boot to edubuntu using windows dhcp
16:35Q-FUNK has quit IRC
16:37Q-FUNK has joined #ltsp
16:38
<vagrantc>
warren: yes, by default we only export /opt/ltsp
16:38
<warren>
ok, just checking
16:38
makes it easier this way =)
16:38
<vagrantc>
indeed.
16:39
<croto_>
is it advisable to change the root path to other than /opt?
16:39
<vagrantc>
croto_: unforunately, some of the tools assume /opt/ltsp without manual configuration.
16:39
and some may not be configurable.
16:40
<croto_>
ok, thank you very much
16:40
if i link ltsp to /opt?
16:41
<vagrantc>
you may experience problems ... one way to find out is to try :)
16:41
<croto_>
ln -s /home/x/ltsp /opt?
16:41
ok, i will try and report
16:41
thanks
16:41
<stoney>
do you have to bind ltsp to use a specific nic?
16:42croto_ has quit IRC
16:43
<vagrantc>
stoney: no, but that's *definitely* the easiest way to do it.
16:43slidesinger has quit IRC
16:44
<stoney>
i got a warning after setting up edubuntu saying to configure nic but I could not find where to do it.
16:45
i had windows dhcp working with dapper but when I moved to edubuntu it broke. changed the dhcp options per the docs but still getting pxe errors.
16:47
-
16:47
<subsume>
vagrantc: /opt/ltsp on the server, right?
16:49
<warren>
vagrantc, idea...
16:49
vagrantc, /usr/share/ltsp/ltsp_config
16:50
vagrantc, if SERVER is not defined, then use the configured gateway
16:50
vagrantc, vast majority of cases the gateway will be the server
16:50
vagrantc, if it isn't, then you need to specify that in the lts.conf
16:50
<vagrantc>
warren: most of my networks have no gateway
16:50
<warren>
vagrantc, currently if you have no SERVER defined it sets it to 192.168.0.254
16:50
vagrantc, so this can't possibly be worse
16:51
<vagrantc>
warren: no, currently it tries to detect it from NFS or NBD
16:51
<warren>
where?
16:51
<vagrantc>
warren: in ltsp_config
16:52
warren: the section labled Ensure a default for SERVER
16:52
warren: it only falls back to 192.168.0.254 if nbd or nfs didn't detect anything
16:52
<warren>
server=$(sed -ne '/ltsp.*nfs/ { s/^\([^:]*\):.*$/\1/; p; q }' /proc/mounts)
16:52
my /proc/mounts says
16:53
<vagrantc>
so fix the command and don't break it on debian :P
16:53
<warren>
172.31.100.254:/opt/ltsp/i386 / nfs ro,blahblahblah
16:53
I don't understand that syntax so I don't know if it is working
16:53
<vagrantc>
well, run that command from a shell on a thin client and see what you get
16:54
<warren>
ah
16:54
=)
16:54
<vagrantc>
or echo that line you just posted | that sed command
16:55
<warren>
hmm, that actually worked
16:55
so I have a bug somewhere else
16:55
<vagrantc>
is nbd running ?
16:55
we need better code for detecting nbd vs. nfs ...
16:56
<warren>
I don't have nbd at all yet
16:56
it needs serious work in mkinitrd and the mkinitrd maintainer is too usy now
16:56
busy
16:56
after I get the rest working, I might just use something other than mkinitrd
16:56
<vagrantc>
heh
16:56
that must be a frustrating blocker.
16:57
<warren>
sort of
16:57
vagrantc, are you setting anything in /etc/resolv.conf of your client chroots?
16:58
<vagrantc>
warren: no ... i think it does add a "server" line to /etc/hosts, though
16:58
<warren>
I'm thinking of either setting the SERVER as default DNS server, or copy the server's /etc/resolv conf into the chroot
16:58
both of which are not perfect
16:58
gotta get ready for a meeting
16:58
bbl
17:00Q-FUNK has quit IRC
17:00
<vagrantc>
well, we copy the server's resolv.conf into the chroot ...
17:00
so i guess technically there's some configuration
17:00
and definitely not perfect.
17:03
<subsume>
warren what are you putting together?
17:03
debian or ubuntu?
17:03
<vagrantc>
i should really get off irc and start running errands... see y'all
17:03
subsume: warren's working on fedora
17:03
<subsume>
vagrantc: bye. thanks for your inattention =)
17:04
<vagrantc>
:P
17:04vagrantc has quit IRC
17:04Q-FUNK has joined #ltsp
17:09
<subsume>
I have chrooted a thin client into opt/ltsp but I am not sure how to make clients actually use this when they startup
17:09
I have a tutorial I am following but it doesn't seem to cover it
17:12foxbuntu___ is now known as foxbuntu
17:14stoney has left #ltsp
17:16jammcq has quit IRC
17:26joebaker has joined #ltsp
17:29jtg23 has quit IRC
17:59bobby_C has quit IRC
18:09joebaker has quit IRC
18:11subsume has quit IRC
18:21Q-FUNK has quit IRC
18:24steph_ has joined #ltsp
18:44steph_ has quit IRC
18:54milesd has quit IRC
18:55staffencasa has quit IRC
18:58EDinNY has left #ltsp
19:04abstract-yin has quit IRC
19:30TelnetManta has joined #ltsp
19:46mccann has quit IRC
19:47jammcq has joined #ltsp
20:26chup has joined #ltsp
20:26chupa has quit IRC
21:41alekibango has quit IRC
21:42alekibango has joined #ltsp
21:49alekibango has quit IRC
21:54johnny_ has joined #ltsp
21:58ogra_cmpc has quit IRC
21:58ogra has quit IRC
21:58ogra_cmpc has joined #ltsp
21:59ogra has joined #ltsp
22:06alekibango has joined #ltsp
22:11chupa has joined #ltsp
22:11chup has quit IRC
22:34alekibango has quit IRC
23:06daya has joined #ltsp
23:51chup has joined #ltsp
23:54chupa has quit IRC