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


Channel log from 12 May 2012   (all times are UTC)

00:23ddave7 has left IRC (ddave7!~Miranda@ip-94-113-119-192.net.upcbroadband.cz, Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org)
00:43toscalix has left IRC (toscalix!~toscalix@114.202.219.87.dynamic.jazztel.es, Read error: Connection reset by peer)
01:13eddytv has joined IRC (eddytv!~anonymous@slashdev.com)
01:14
<eddytv>
Anybody around who'd like to help me with an LTSP issue? I upgraded my Ubuntu server to 12.04 today, and now my diskless clients won't boot because of a problem with 'nbd'
01:15
From what I can tell, 'nbd' was previously configured to run from inetd on port 2000...
01:16
and it seems LTSP now expects to use a "named port", and possibly have nbd running NOT from inetd?
01:49Phantomas has joined IRC (Phantomas!~Phantomas@unaffiliated/phantomas)
01:52Phantomas has left IRC (Phantomas!~Phantomas@unaffiliated/phantomas)
02:35
<eddytv>
Any there any docs on setting up a COW overlay for LTSP diskless clients via NFS?
05:13bobby_C has joined IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at)
05:16komunista has joined IRC (komunista!~slavko@adsl-195-168-232-196.dynamic.nextra.sk)
05:23
<muppis>
eddytv, did you upgrade chroot as well?
05:30alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
05:38
<Hyperbyte>
eddytv, in 12.04 NBD runs as a standalone daemon, not from inetd. Type 'service nbd-server status' to see if it's started, and 'service nbd-server start' to start it.
07:00bobby_C has left IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at, Ping timeout: 272 seconds)
07:43epoptes_user2 has joined IRC (epoptes_user2!c3616e6c@gateway/web/freenode/ip.195.97.110.108)
07:43epoptes_user2 has left IRC (epoptes_user2!c3616e6c@gateway/web/freenode/ip.195.97.110.108)
07:58bobby_C has joined IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at)
08:29
<knipwim>
alkisg: i'm working on the source hierarchy for the wiki now, and i'm not sure about the contents of some of the server dirs
08:29
<alkisg>
knipwim: like?
08:29
<knipwim>
what should be in /server/configs /server/docs /server/services /server/xinetd.d ? Can't they be merged?
08:30
ehm /server/docs/examples
08:30
it seems like /server/services can be merged with that one
08:30
and the xinetd.d stuff also
08:31
<alkisg>
xinetd and services seem like fedora to me
08:31
Maybe they should go under distro-specific dirs
08:31
<knipwim>
i also use the nbdswapd
08:31
<alkisg>
You use xinetd?
08:31
<knipwim>
for nbdswapd only
08:32
<alkisg>
OK, debian/ubuntu use inetd instead
08:32
So I guess something like an etc/ directory with those would be better
08:32
I think that in the next BTS the code directory layout should be discussed
08:33
Maybe we could put all those in examples too, yeah
08:33
And have the packages that need them ship them in the appropriate service place too
08:33
<knipwim>
a /server/doc/examples/nbdswap-xinetd.d would be in line with recent changes
08:35daya has joined IRC (daya!~daya@unaffiliated/daya)
08:38daya has left IRC (daya!~daya@unaffiliated/daya, Read error: Connection reset by peer)
08:52mikkel has joined IRC (mikkel!~mikkel@80-71-132-15.u.parknet.dk)
08:59daya has joined IRC (daya!~daya@unaffiliated/daya)
09:06ddave7 has joined IRC (ddave7!~Miranda@ip-94-113-119-192.net.upcbroadband.cz)
09:19Steve_The_Pirate has joined IRC (Steve_The_Pirate!~Gary@cpc16-haye17-2-0-cust169.haye.cable.virginmedia.com)
10:38ogra_ has left IRC (ogra_!~ogra@p5098ed03.dip0.t-ipconnect.de, Ping timeout: 252 seconds)
10:59ddave7 has left IRC (ddave7!~Miranda@ip-94-113-119-192.net.upcbroadband.cz, Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org)
11:03ddave7 has joined IRC (ddave7!~Miranda@ip-94-113-119-192.net.upcbroadband.cz)
11:06Trixboxer has joined IRC (Trixboxer!~Trixboxer@115.124.115.71)
11:17daya has left IRC (daya!~daya@unaffiliated/daya, Ping timeout: 272 seconds)
11:32
<eddytv>
muppis: I didn't "upgrade" the chroot after moving to 12.04, I mv'd /opt/ltsp to /opt/ltsp-save, and then ran ltsp-built-client. Unfortunately, there is no longer a "--mythbuntu" option, and that's why I think I'm screwed. I didn't know that option was gone before upgrading.
11:33
<muppis>
eddytv, did you test that what Hyperbyte said?
11:34
<eddytv>
Hyperbyte: I figured out that 'nbd-server' needed to run as a service, so I commented out the lines for ports 9571 (ldminfod), 9572 (nbdswapd) and 2000 (nbdrootd) from 'ineted' and started nbd-server... after adjust some other files, I *did* get the diskless clients to at least start booting
11:36
However, they booted to an 'ldm' login screen
11:36ddave71861 has joined IRC (ddave71861!~Miranda@ip-94-113-119-192.net.upcbroadband.cz)
11:36ddave7 has left IRC (ddave7!~Miranda@ip-94-113-119-192.net.upcbroadband.cz, Read error: Connection reset by peer)
11:37
<eddytv>
I assume there's some way to "autologin" a user (ala 'mythtv'), but while researching that, I found a much bigger issue, and that is the apparent lack of an NFS-based copy-on-write for the root filesystem (/) that the diskless clients rely on :(
11:38toscalix has joined IRC (toscalix!~toscalix@114.202.219.87.dynamic.jazztel.es)
11:38
<alkisg>
eddytv: you can probably just create a fat chroot and install the mythbuntu packages inside it
11:39
The mythbuntu ltsp-build-client plugin was unmaintained, it didn't work anymore
11:39
<eddytv>
Apparently one of the things the now-gone '--mythbuntu' option did was set up an NFS-based overlay, which stored any changes from the base .img in /var/cache/mythbuntu-diskless/overlay/HOSTNAME
11:40
<alkisg>
Such things should be upstream, not in an unmaintained distro postinst script
11:40
<eddytv>
alkisg: I did create a "fat" /opt/ltsp and it did install the mythbuntu packages
11:41
<alkisg>
Why would one need an overlay for mythtv?
11:41
<eddytv>
It's the lack of the NFS overlay that is the issue now. Each of the diskless clients has a tweaked xorg.conf, asound.conf, etc. that is specific to its hardware/display/etc.
11:41
<alkisg>
...mythbuntu or however it's called?
11:41
There are standard ltsp ways to provide custom xorg.confs
11:41
No need to invent new ones
11:41
What do they need in asound.conf?
11:42
<eddytv>
Every diskless client is different. Some use HDMI for audio, some use analog, etc.
11:42
<alkisg>
There are lts.conf parameters for xorg and audio
11:42
!lts.conf
11:42
<ltsp`>
alkisg: lts.conf: http://manpages.ubuntu.com/lts.conf
11:42
<alkisg>
E.g. you can just a custom resolution by just specifying XRANDR_MODE_0=1024x768
11:43
Or you can select a custom xorg.conf with X_CONF
11:43
There shouldn't be need for different chroots just to finetune some hardware differences
11:43
(or overlays)
11:44
If you find out that you need something that's not covered by upstream code, then you should file a feature request bug
11:44
<eddytv>
The NFS overlay allowed this to be adjusted very easily -- you could tweak files on the diskless clients "like normal", and it would copy-on-write to the NFS overlay, no tweaking on the "backend" for all the files. Plus, it also worked great for things like /var/log
11:45
<alkisg>
An NFS (or other filesystem) overlay can be handy, but the developer should have pushed the code upstream and should be willing to maintain it
11:45
I don't even know who developed that plugin, the code never came upstream
11:45
<eddytv>
asound.state is another good example -- it's a "state" file for each diskless client, and can change
11:46
<alkisg>
There are volume settings in lts.conf, and per user volume settings too
11:46
<eddytv>
Anyway, long story short: I'm in a heap of trouble with the family because nobody can watch TV :(
11:47
<alkisg>
Just try to cover your needs by using upstream code, and see what's missing so that you can report it
11:47
NFS overlays can be dangerous, they can break things on upgrades
11:47
Saving/restoring files should be a monitored process
11:48
<eddytv>
I just wish the mythbuntu folks had made it very obvious that moving to 'precise' would break any installs that use diskless frontends
11:49
I had no clue that that --mythbuntu option was so "unsupported"
11:49
<alkisg>
Indeed, you're right on that complain
11:50
<eddytv>
I tried reverting back to my original /opt/ltsp, but no joy there either... I set up nbd-server with 'oldstyle = true' and told it to listen on port 2000, re-ran ltsp-update-kernels to populate /var/lib/tftpboot/ltsp/amd64 with "the right stuff" and I just get a bunch of nbd I/O errors on the clients
11:51
So I assume there is some compatibilty issue with the (old) nbd code that gets run on the clients and the new nbd code running on the server
11:55ddave71861 is now known as dsorf
11:55dsorf has left IRC (dsorf!~Miranda@ip-94-113-119-192.net.upcbroadband.cz, Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org)
11:55
<alkisg>
eddytv: which version did you use previously? 10.04? 11.10?
11:56ddave7 has joined IRC (ddave7!~Miranda@ip-94-113-119-192.net.upcbroadband.cz)
11:56
<eddytv>
I was on 11.04 (natty). I upgraded to 11.10 and then 12.04 because I wanted to get to the LTS level.
11:57
<alkisg>
eddytv: so your chroot is from 11.10?
11:57
<eddytv>
no, 11.04. I did the upgrade to 11.10/12.04 back-to-back.
11:57
<alkisg>
(in which ubuntu version it was genenated)
11:57
Ah
11:57
Try putting nbd-proxy=false in pxelinux.cfg/default
11:57
nbd_proxy=false, sorry
11:59
!nbd-proxy
11:59
<ltsp`>
alkisg: nbd-proxy: Ubuntu 10.04 and 10.10 use a wrapper called nbd-proxy, which is causing networking problems for some people. See https://bugs.launchpad.net/ltsp/+bug/589034. It's been disabled by default in 11.04, see http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/1803
11:59
<alkisg>
Hmm ok then, not there in 11.04
12:00
You can try removing /etc/nbd-server/conf.d/config and putting nbd-server in /etc/inetd.conf like it was in 11.04
12:01
And you'll also need appropriate parameters in /var/lib/tftpboot/ltsp/amd64/pxelinux.cfg/default
12:01
<eddytv>
I did try that originally...
12:01
<alkisg>
But all those are temporary solutions, the correct one would be to move to a new chroot and see what's missing and how it can be fixed, e.g. move to X_* commands in lts.conf etc
12:01
<eddytv>
and pxelinux.cfg/default has 'autoconf=dhcp nbdport=2000'
12:02
<alkisg>
Other than the X and sound issues, did the mythbuntu desktop work for you as expected?
12:03
<eddytv>
I didn't get that far; 'ldm' came up and there are no keyboards on the clients... I was going to try setting up autologin, but then I stumbled across the overlay issue and thought that was a bigger issue
12:04
<alkisg>
It shouldn't be. Autologin is easy, just a couple of lines in lts.conf.
12:04
<eddytv>
Sorry, was referring to the overlay thing being the bigger issue
12:04
<alkisg>
Yup, me too.
12:04
It shouldn't be an issue.
12:05
What other problems do you want to solve with an overlay?
12:05
You mentioned X, which there's support for in lts.conf, and asound.conf, and while that's not saved/restored on boot, you can set volume levels from lts.conf, and your DE can save/restore the user sound settings on login/logout
12:05
Anything else?
12:06
<eddytv>
OK. Well it's an issue currently because files like xorg.conf, asound.conf and asound.state are all "overlaid"...
12:06ddave7 has left IRC (ddave7!~Miranda@ip-94-113-119-192.net.upcbroadband.cz, Read error: Connection reset by peer)
12:06ddave71861 has joined IRC (ddave71861!~Miranda@ip-94-113-119-192.net.upcbroadband.cz)
12:07ddave71861 is now known as dsorf
12:07
<alkisg>
As I said, you can have custom xorg.conf files from lts.conf. And you probably don't even need them.
12:07dsorf has left IRC (dsorf!~Miranda@ip-94-113-119-192.net.upcbroadband.cz, Client Quit)
12:07
<alkisg>
You can customize many xorg options without xorg.conf nowadays
12:07
Screen resolution, mirroring etc
12:07ddave7 has joined IRC (ddave7!~Miranda@ip-94-113-119-192.net.upcbroadband.cz)
12:08
<eddytv>
What about log files in /var/log? Are they maintained, or just stored on a tmpfs?
12:09
<alkisg>
lts.conf supports remote logging, if you need it
12:09
So that client log files go on the server
12:12
<eddytv>
Looking through the lts.conf page you linked to, I see that for syslog. mythtv logs directly to /var/log/mythtv/*, so remote syslogging probably won't help in that regard. But that's not a showstopper. If I can get ldm autologin working, and set up lts.conf with whatever options I need, maybe I can get the front-ends functional enough.
12:12
Although I just thought of another issue, the lircd.conf (for remote control) is different on each client as well since not all the remotes are the same.
12:13
<alkisg>
The LTSP way would be to make a script that reads its environment for lts.conf variables, and writes lircd.conf on client boot
12:13
It's very easy, see the examples in $chroot/usr/share/ltsp/init-ltsp.d
12:15
<eddytv>
OK. Thanks alkisg! At least you've give me a ray of hope. I was thinking I was really screwed; now with a little luck and some hacking at lts.conf I might be able to get this going again. Appreciate your insight.
12:16
<alkisg>
You're welcome, feel free to file bugs for things you think that will interest others, e.g. a lircd.conf script
12:16
<eddytv>
OK. Will do. Thanks again!
12:17
One other question I had: is there an LTSP-supported way to disable all the Ubuntu auto-update checks / notifications on the clients/
12:17
<alkisg>
They are automatically disabled for gnome and for some parts in KDE
12:18
E.g. $chroot/usr/share/ltsp/init-ltsp.d/50-disable-cronjobs, $chroot//usr/share/ltsp/init-ltsp.d/50-rm-session-services
12:18
There's an RM_SESSION_SERVICES list there, you can add to it from lts.conf
12:20
<eddytv>
OK... thanks a bunch.
12:20
<alkisg>
np
12:20alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
13:00ddave7 has left IRC (ddave7!~Miranda@ip-94-113-119-192.net.upcbroadband.cz, Ping timeout: 245 seconds)
13:08ddave7 has joined IRC (ddave7!~Miranda@ip-94-113-119-192.net.upcbroadband.cz)
13:20risca has left IRC (risca!~risca@wnpgmb0903w-ds01-249-233.dynamic.mtsallstream.net, Quit: Lämnar)
14:05BigBear has joined IRC (BigBear!4dfb53b7@gateway/web/freenode/ip.77.251.83.183)
14:06
<BigBear>
hi, quick ltsp newbie question: what thin client hardware works with Ubuntu+LTSP ??
14:08
i was looking at some HP thin clients (5520, 5530) but i don't know if those will work with LTSP ??
14:11
<Hyperbyte>
BigBear, generally speaking, if it works with Ubuntu and can do PXE boot, it will work.
14:11
<BigBear>
oke that helps, thanks. any experience with HP thin clients ?
14:12
<Hyperbyte>
Only one. I thought it sucked pretty badly for the money I paid for it.
14:13
But it booted LTSP fine...
14:13
<knipwim>
i have on old one, bought secondhand, but working like a charm
14:14
<BigBear>
i was looking at some secondhand HP thin clients 5520, 5530... for only €19,- or € 29,- a piece
14:15
well, i guess i'll just buy one and see if and how it works and then buy more
14:15
€ 19,- isn't the end of the world... ;)
14:15
<knipwim>
i got a t5710
14:17alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
14:17
<BigBear>
ok thanks guys i'll just try some of those...
14:18toscalix has left IRC (toscalix!~toscalix@114.202.219.87.dynamic.jazztel.es, Read error: Connection reset by peer)
14:19
<wafflecone>
so ... we are 2 weeks away from deployment of an LTSP project and I get an email from the customer with this link in it
14:19
http://www.engadget.com/2012/05/10/hp-t410-smart-zero-client-poe/
14:20
I see disklessworkstations.com carries HP stuff ... is there a high likelihood that this model will be available upon release?
14:21
<alkisg>
BigBear: I have an HP T5000, it boots LTSP and works for basic office work but that's it, don't expect full screen video or localapps to work
14:33
<wafflecone>
I am hoping they will go with the LTSP Term 1720's ... double the ram ... intel proc ... better video ... available for sale now ... etc. But this customer loses all perspective on reality anytime PoE is mentioned.
14:34
<knipwim>
is that t410 a true zero client? i don't think ltsp will run on those
14:35
on a zero client nothing is done locally right? only the viewport is pushed toward it?
14:36BigBear has left IRC (BigBear!4dfb53b7@gateway/web/freenode/ip.77.251.83.183)
14:37
<wafflecone>
it says pxe
14:37
and we would swtich to vmware view if necessary
14:37
it seems a bit of a headache to remove one wire from each desk
14:38
and you have to add that wire back in to get better than 10/100
14:38
especially since we are 2 weeks from deployment and the things are not on sale yet
14:39Phantomas has joined IRC (Phantomas!~Phantomas@unaffiliated/phantomas)
14:41
<knipwim>
you'd have to use a distro which supports arm thin clients
14:42
don't know if ubuntu or debian support arm
14:46
<Hyperbyte>
wafflecone, I have LTSP Term 1720's at my work.
14:47highvolt1ge has joined IRC (highvolt1ge!~highvolta@modemcable104.153-23-96.mc.videotron.ca)
14:47
<wafflecone>
we have a LTSP Term 1220 that we use for testing
14:47
it is just perfect
14:47
but somebody always has to have a better idea at the last minute
14:49highvoltage has left IRC (highvoltage!~highvolta@ubuntu/member/highvoltage, Read error: Connection reset by peer)
14:49
<Hyperbyte>
The 1720 required some tweaking to work with dual screens, but DLWS released a fix for that... and I'm not happy with the sound quality the onboard soundcard produces, but we're using USB headsets now, so... I really like the way they look though, and the specs they carry... plus they're quite robustly built I think.
14:52highvolt1ge has left IRC (highvolt1ge!~highvolta@modemcable104.153-23-96.mc.videotron.ca, Ping timeout: 260 seconds)
14:52highvoltage has joined IRC (highvoltage!~highvolta@ubuntu/member/highvoltage)
14:58
<wafflecone>
hyberbyte. It is a shame they don't have the VESA monitor mounts for them
15:14bobby_C has left IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at, Ping timeout: 272 seconds)
15:24
<alkisg>
stgraber, knipwim, cyberorg: instead of hardcoding BOOTPROMPT_OPTIONS in the code, I think it would be better if they were shipped as a configuration file in $chroot/etc/ltsp/update-kernels.conf as part of the ltsp-client package, would you mind if that was a requirement? Example content:
15:24
NBD_CMDLINE='ro initrd=$INITRD root=/dev/nbd0 init=/sbin/init-ltsp nbdroot=$SERVER:$PORT$NBD_NAME'
15:24
NFS_CMDLINE='ro initrd=$INITRD root=/dev/nfs init=/sbin/init-ltsp'
15:26
That way an e.g. Ubuntu LTSP server can properly identify a Gentoo chroot cmdline, and also different ltsp-client package versions can ship with different command lines and the user can more easily see where he should edit the cmdlines.
15:26
The variables are evaluated by update-kernels / ltsp-update-kernels
15:28
In other words, if that file isn't there, ltsp-update-kernels will die with "I don't know how to generate a pxelinux.cfg/default for this chroot".
15:28
<Hyperbyte>
wafflecone, I mount all my clients under the desk anyways, with tie-wraps. I know it sounds primitive as hell, but it works surprisingly well and it is surprisingly cheap as well.
15:29ddave7 has left IRC (ddave7!~Miranda@ip-94-113-119-192.net.upcbroadband.cz, Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org)
15:42mikkel has left IRC (mikkel!~mikkel@80-71-132-15.u.parknet.dk, Quit: Leaving)
15:55
<knipwim>
alkisg: sure
16:04
<alkisg>
Cool, ty, will implement it this way unless someone objects
16:06
<wafflecone>
Hyberbyte ... I am all about zip-ties, duct-tape AND baling wire
16:15
<Hyperbyte>
wafflecone, so create your own frankenvesamount. :)
16:16SmallR2002 has left IRC (SmallR2002!~quassel@c-98-253-173-240.hsd1.il.comcast.net, Ping timeout: 260 seconds)
16:17adrianorg has joined IRC (adrianorg!~adrianorg@177.18.169.90)
16:17SmallR2002 has joined IRC (SmallR2002!~quassel@c-98-253-173-240.hsd1.il.comcast.net)
16:23alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
16:27SmallR2002 has left IRC (SmallR2002!~quassel@c-98-253-173-240.hsd1.il.comcast.net, Ping timeout: 245 seconds)
16:36SmallR2002 has joined IRC (SmallR2002!~quassel@c-98-253-173-240.hsd1.il.comcast.net)
17:35ddave7 has joined IRC (ddave7!~Miranda@ip-94-113-119-192.net.upcbroadband.cz)
18:11[GuS] has joined IRC ([GuS]!~gustavo@unaffiliated/gus/x-663402)
18:52loather has left IRC (loather!~khudson@wsip-98-175-250-115.sd.sd.cox.net, Ping timeout: 240 seconds)
19:55alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
20:28vagrantc has joined IRC (vagrantc!~vagrant@75-150-46-245-Oregon.hfc.comcastbusiness.net)
20:28vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)
20:37Trixboxer has left IRC (Trixboxer!~Trixboxer@115.124.115.71, Quit: "Achievement is not the end, its the beginning of new journey !!!")
21:18alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
21:27loather has joined IRC (loather!~khudson@wsip-98-175-250-115.sd.sd.cox.net)
21:29komunista has left IRC (komunista!~slavko@adsl-195-168-232-196.dynamic.nextra.sk, Quit: Leaving.)
21:54ddave7 has left IRC (ddave7!~Miranda@ip-94-113-119-192.net.upcbroadband.cz, Read error: Connection reset by peer)
21:54Steve_The_Pirate has left IRC (Steve_The_Pirate!~Gary@cpc16-haye17-2-0-cust169.haye.cable.virginmedia.com, Quit: Leaving)
22:16
<eddytv>
Hey guys... I added the line "X_CONF=/etc/X11/frontend-xorg.conf" to lts.conf, and then place the file 'frontend-xorg.conf' in /opt/ltsp/amd64/etc/X11... but the diskless clients don't seem to be using that file. Do I need to do something after updating lts.conf? Is there any "debug logging" I can turn on?
22:26
<Hyperbyte>
eddytv, have you updated the client chroot image after you put the new xorg config in /opt/ltsp/amd64/ ?
22:28
<eddytv>
Via 'ltsp-update-image'?
22:32
I didn't know the image had to be rebuilt after updating lts.conf... I was under the (apparently mistaken?) impression that lts.conf would allow me to specify different 'xorg.conf' files depending on the hostname of the diskless client that was booting.
22:34
<Hyperbyte>
I wasn't talking about lts.conf
22:34
I was talking about the xorg config file you put in the chroot
22:34
Anything you change in /opt/ltsp/ requires ltsp-update-image to work
22:34
You've specified a new xorg config in lts.conf, which is read by the client - but if you don't update the chroot image, the xorg config file won't be there.
22:35
<eddytv>
Ah, OK. Gotcha. I misunderstood. I did run ltsp-update-image after putting 'frontend-xorg.conf' in /opt/ltsp/amd64/etc/X11
22:36
If I ssh in to the frontend, I can see the file in /etc/X11, but X doesn't appear to be using it when it starts
22:37
(that's why I was wondering if there was any sort of debug logging that would show if it processed the corresponding section of lts.conf when it booted)
22:38
Here's a thought: do I need to set CONFIGURE_X to set X_CONF?
22:38
<Hyperbyte>
Well, I have no idea about this issue specifically... never modified an xorg config... not with ltsp, not period...
22:38
But since LTSP clients are just Linux, you could find any debug information in /var/log/ and dmesg.
22:39
<eddytv>
Unfortunately X just keeps exiting without one
22:39
<Hyperbyte>
My advice... wait around for someone who has experience with this. :)
22:40
Which might be tomorrow...
22:40
I'm off to bed. :) If you figure it out on your own, let us know.
22:40
<eddytv>
OK. Will do.
22:41
Thanks for your help in any case.
22:41
<Hyperbyte>
Sure, you're welcome.
22:48
<vagrantc>
eddytv: you'll want to look at the code in /opt/ltsp/amd64/usr/share/ltsp/screen-session.d/XS*
22:50
<eddytv>
Ah, interesting.
22:50
<vagrantc>
in particular, XS90-set-x-conf
22:50
dunno what version of LTSP or OS you're running
22:50
<eddytv>
For the X process, I see the '-config /etc/X11/frontend-xorg.conf' when I do 'ps'
22:50
and when I look at the /var/log/Xorg.7.log file, I see it referencing that file...
22:51
<vagrantc>
sounds like the LTSP part of it is doing what it's supposed to
22:51
<eddytv>
...but it seems to be using a bunch of stuff in /usr/share/X11/xorg.conf.d/* first?
22:51
<vagrantc>
probably
22:51
<eddytv>
"No device specified for "My Screen"
22:52
and "No monitor specified for "My Screen"
22:52
<vagrantc>
let's back up a bit ...
22:52
<eddytv>
which are referenced in 10-nvidia-current-latitude-e6530.conf...
22:52
<vagrantc>
eddytv: why are you needed a custom xorg.conf ?
22:52
needing
22:53
<eddytv>
I (made the mistake) of upgrading my mythtv backend to Ubuntu 12.04 yesterday... wanted to get to a LTS level.
22:53
I have several diskless clients that are mythtv frontends that were working splendidly with ltsp previously...
22:54
But I didn't realize that ltsp-build-client "lost" the --mythbuntu option
22:54
and now all of my front-ends are dead, much to the chagrin of the family, who can't watch any TV
22:55
<vagrantc>
by "front-end" are you meaning the thin client? or something else? i'm not too familiar with mythbuntu, other than the basic idea of it
22:56
<eddytv>
Last night, I "fought" with the new changes to 'nbd' (old release ran it from inetd; in 12.04 it wants to run as a service with "named ports") and 'alkisg' here in #ltsp helped me get the diskless clients to at least start booting last night.
22:57
They are "thick" clients, so I ran ltsp-build-clients --fat-client-desktop mythbuntu-desktop --mount-package-cache --keep-packages --copy-sourceless
22:58
With the old --mythbuntu option, it must've pre-set the ltsp environment to automatically login to an XFCE-based "desktop" (not really needed) and then auto launch the 'mythtv-frontend' binary.
22:58
So it was a simple matter of just powering on the diskless clients, and 30 seconds later, MythTV was running and usable by non-techies :)
22:59
So... getting back to original question: the diskless clients are connected to various TVs by various means (some VGA, some HDMI, etc.) and they each have a custom xorg.conf that sets the proper modeline for the TV to display at their "native resolution"
22:59
<vagrantc>
aha
23:00
<eddytv>
In prior release, this was accomplished by an NFS-based copy-on-write overlay of the root (/) filesystem...
23:00
So while the client was up, you'd just edit xorg.conf "normally", and when you saved it, it got written to a client-specific overlay via NFS
23:01
<vagrantc>
ah, ok.
23:02
<eddytv>
Once I got each client configured properly, everything was "good"... but now things are "much different" and I'm trying to get it working in the Ubuntu 12.04 world without a specialized '--mythbuntu' option for ltsp-build-client to do everything for me
23:03
So I guess I need to figure out why the /usr/share/X11/xorg.conf.d/* stuff seems to be messing up the use of my custom xorg.conf
23:35risca has joined IRC (risca!~risca@wnpgmb0903w-ds01-249-233.dynamic.mtsallstream.net)
23:36
<eddytv>
So I added a "ServerLayout" section to my xorg.conf, and now it is referencing "my" screen config instead of the one in 10-nvidia-current-* in the conf.d directory...
23:37
But now .xsession-errors just fills constantly with "X session started" and then "open: Permission denied" over and over again...
23:41
This isn't good... on my diskless client, the permissions on /tmp are "drwxr-xr-x" instead of "drwxrwxrwt". Any idea how to fix that?
23:44
As soon as I reset the defaults of /tmp on a diskless client, X started up
23:45
But that's only a temporary fix, as on each boot /tmp reverts to a standard "755" permission
23:54Phantomas has left IRC (Phantomas!~Phantomas@unaffiliated/phantomas, Read error: Operation timed out)
23:54
<vagrantc>
eddytv: that's bizarre.
23:55
wonder if the mythbuntu packages added did something strange ...
23:57
<eddytv>
Such a subtle problem; no idea how to track that down. Obviously the permissions for /tmp in /opt/ltsp/amd64 are correct
23:58
<vagrantc>
i'll see if i can reproduce on recent versions of debian ... but i suspect not.