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


Channel log from 22 November 2015   (all times are UTC)

00:53Freejack has left IRC (Freejack!~Freejack@unaffiliated/freejack, Remote host closed the connection)
00:53Freejack has joined IRC (Freejack!~Freejack@unaffiliated/freejack)
01:19cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Ping timeout: 272 seconds)
01:25cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)
02:11andygraybeal has left IRC (andygraybeal!~andy@h130.33.30.71.dynamic.ip.windstream.net, Ping timeout: 250 seconds)
02:26andygraybeal has joined IRC (andygraybeal!~andy@h27.205.189.173.dynamic.ip.windstream.net)
02:26vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
03:43marjus has joined IRC (marjus!marius@flage.org)
03:51sutula has left IRC (sutula!~sutula@207-118-162-188.dyn.centurytel.net, *.net *.split)
03:51uXus has left IRC (uXus!~uXus@217.77.222.72, *.net *.split)
03:51zamba has left IRC (zamba!marius@flage.org, *.net *.split)
03:51mgariepy has left IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy, *.net *.split)
03:51TatankaT has left IRC (TatankaT!~tim@193.190.253.114, *.net *.split)
03:51_longines has left IRC (_longines!~longines@static.95.25.4.46.clients.your-server.de, *.net *.split)
03:51muppis_ has left IRC (muppis_!muppis@palo.kirves.fi, *.net *.split)
03:51lee has left IRC (lee!~lee@loathe.ms, *.net *.split)
03:51zerkalo has left IRC (zerkalo!myricae@ny1.hashbang.sh, *.net *.split)
03:51elias_a has left IRC (elias_a!elias@hilla.kapsi.fi, *.net *.split)
03:51NeonLicht has left IRC (NeonLicht!~NeonLicht@darwin.ugr.es, *.net *.split)
03:51F-GT has left IRC (F-GT!~phantom@ppp121-44-249-146.lns20.syd7.internode.on.net, *.net *.split)
03:51Freejack has left IRC (Freejack!~Freejack@unaffiliated/freejack, *.net *.split)
03:51highvoltage has left IRC (highvoltage!~highvolta@ubuntu/member/highvoltage, *.net *.split)
03:51Hyperbyte has left IRC (Hyperbyte!jan@middelkoop.cc, *.net *.split)
03:51vervelak has left IRC (vervelak!~vervelak@139.91.248.3, *.net *.split)
03:51ke4nhw has left IRC (ke4nhw!ke4nhw@unaffiliated/xanthaos, *.net *.split)
03:51zama has left IRC (zama!~zama@unaffiliated/stryx/x-3871776, *.net *.split)
03:51riddle has left IRC (riddle!riddle@us.yunix.net, *.net *.split)
03:51grimeton has left IRC (grimeton!~ruth@2a01:4f8:160:41e3:0:dead:beef:cafe, *.net *.split)
03:51m3741 has left IRC (m3741!8c20b7fe@gateway/web/freenode/ip.140.32.183.254, *.net *.split)
03:51yanu has left IRC (yanu!~yanu@178-116-58-90.access.telenet.be, *.net *.split)
03:51work_alkisg has left IRC (work_alkisg!~alkisg@ubuntu/member/alkisg, *.net *.split)
03:51_spk_ has left IRC (_spk_!U2FsdGVkX1@ma.sdf.org, *.net *.split)
03:51teknkik has left IRC (teknkik!tek@kapsi.fi, *.net *.split)
03:51fiesh_ has left IRC (fiesh_!~fiesh@hq.wsoptics.de, *.net *.split)
03:51vsuojane1 has left IRC (vsuojane1!~valtteri@83-136-248-31.uk-lon1.host.upcloud.com, *.net *.split)
03:51maldridge has left IRC (maldridge!~maldridge@69.13.217.92, *.net *.split)
03:51ogra_ has left IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de, *.net *.split)
03:51bitchecker has left IRC (bitchecker!~bitchecke@31.131.20.132, *.net *.split)
03:51bennabiy has left IRC (bennabiy!~bennabiy@unaffiliated/bennabiy, *.net *.split)
03:51PeperPots____ has left IRC (PeperPots____!sid1218@gateway/web/irccloud.com/x-tuerfhafmoypzzyc, *.net *.split)
03:51stgraber has left IRC (stgraber!~stgraber@ubuntu/member/stgraber, *.net *.split)
03:51warren has left IRC (warren!~warren@fedora/wombat/warren, *.net *.split)
03:51andygraybeal has left IRC (andygraybeal!~andy@h27.205.189.173.dynamic.ip.windstream.net, *.net *.split)
03:51book` has left IRC (book`!~book`@105.ip-167-114-152.net, *.net *.split)
03:51||cw has left IRC (||cw!~chrisw@unaffiliated/cw/x-1182934, *.net *.split)
03:51gehidore has left IRC (gehidore!~username@unaffiliated/man, *.net *.split)
03:51lmds_ has left IRC (lmds_!~lmds@tui.pi-et-ro.net, *.net *.split)
03:51Tyrantelf has left IRC (Tyrantelf!~tyrantelf@iongaming.org, *.net *.split)
03:51Parker95z has left IRC (Parker95z!~parker@2607:5300:60:8425::2d62:a8e6, *.net *.split)
03:51spectra has left IRC (spectra!~spectra@debian/developer/spectra, *.net *.split)
03:51cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, *.net *.split)
03:51quinox1 has left IRC (quinox1!~quinox@ghost.qtea.nl, *.net *.split)
03:51pppingme has left IRC (pppingme!~pppingme@unaffiliated/pppingme, *.net *.split)
03:51marjus has left IRC (marjus!marius@flage.org, Max SendQ exceeded)
03:56riddle has joined IRC (riddle!~decadance@us.yunix.net)
03:56zama has joined IRC (zama!~zama@unaffiliated/stryx/x-3871776)
03:56sutula has joined IRC (sutula!~sutula@207-118-162-188.dyn.centurytel.net)
03:56uXuss has joined IRC (uXuss!~uXus@217.77.222.72)
03:56danau11 has joined IRC (danau11!~durban@66.251.57.114)
03:56ke4nhw has joined IRC (ke4nhw!ke4nhw@unaffiliated/xanthaos)
03:56andygraybeal has joined IRC (andygraybeal!~andy@h27.205.189.173.dynamic.ip.windstream.net)
03:56cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)
03:56Freejack has joined IRC (Freejack!~Freejack@unaffiliated/freejack)
03:56lmds_ has joined IRC (lmds_!~lmds@tui.pi-et-ro.net)
03:56||cw has joined IRC (||cw!~chrisw@unaffiliated/cw/x-1182934)
03:56yanu has joined IRC (yanu!~yanu@178-116-58-90.access.telenet.be)
03:56NeonLicht has joined IRC (NeonLicht!~NeonLicht@darwin.ugr.es)
03:56_spk_ has joined IRC (_spk_!U2FsdGVkX1@ma.sdf.org)
03:56mgariepy has joined IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy)
03:56F-GT has joined IRC (F-GT!~phantom@ppp121-44-249-146.lns20.syd7.internode.on.net)
03:56book` has joined IRC (book`!~book`@105.ip-167-114-152.net)
03:56TatankaT has joined IRC (TatankaT!~tim@193.190.253.114)
03:56m3741 has joined IRC (m3741!8c20b7fe@gateway/web/freenode/ip.140.32.183.254)
03:56work_alkisg has joined IRC (work_alkisg!~alkisg@ubuntu/member/alkisg)
03:56PeperPots____ has joined IRC (PeperPots____!sid1218@gateway/web/irccloud.com/x-tuerfhafmoypzzyc)
03:56_longines has joined IRC (_longines!~longines@static.95.25.4.46.clients.your-server.de)
03:56muppis_ has joined IRC (muppis_!muppis@palo.kirves.fi)
03:56Tyrantelf has joined IRC (Tyrantelf!~tyrantelf@iongaming.org)
03:56Parker95z has joined IRC (Parker95z!~parker@2607:5300:60:8425::2d62:a8e6)
03:56lee has joined IRC (lee!~lee@loathe.ms)
03:56stgraber has joined IRC (stgraber!~stgraber@ubuntu/member/stgraber)
03:56spectra has joined IRC (spectra!~spectra@debian/developer/spectra)
03:56grimeton has joined IRC (grimeton!~ruth@2a01:4f8:160:41e3:0:dead:beef:cafe)
03:56Hyperbyte has joined IRC (Hyperbyte!jan@middelkoop.cc)
03:56highvoltage has joined IRC (highvoltage!~highvolta@ubuntu/member/highvoltage)
03:56gehidore has joined IRC (gehidore!~username@unaffiliated/man)
03:56teknkik has joined IRC (teknkik!tek@kapsi.fi)
03:56zerkalo has joined IRC (zerkalo!myricae@ny1.hashbang.sh)
03:56fiesh_ has joined IRC (fiesh_!~fiesh@hq.wsoptics.de)
03:56elias_a has joined IRC (elias_a!elias@hilla.kapsi.fi)
03:56vsuojane1 has joined IRC (vsuojane1!~valtteri@83-136-248-31.uk-lon1.host.upcloud.com)
03:56vervelak has joined IRC (vervelak!~vervelak@139.91.248.3)
03:56quinox1 has joined IRC (quinox1!~quinox@ghost.qtea.nl)
03:56pppingme has joined IRC (pppingme!~pppingme@unaffiliated/pppingme)
03:57marjus has joined IRC (marjus!marius@flage.org)
03:57ogra_ has joined IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de)
03:58warren has joined IRC (warren!~warren@fedora/wombat/warren)
04:00bitchecker has joined IRC (bitchecker!~bitchecke@31.131.20.132)
04:06maldridge has joined IRC (maldridge!~maldridge@69.13.217.92)
04:06bennabiy has joined IRC (bennabiy!~bennabiy@unaffiliated/bennabiy)
04:19cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Ping timeout: 250 seconds)
04:24cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)
05:43muppis_ is now known as muppis
08:31ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
10:51Phantomas has joined IRC (Phantomas!~ftsamis@ubuntu/member/phantomas)
12:31andygraybeal has left IRC (andygraybeal!~andy@h27.205.189.173.dynamic.ip.windstream.net, Ping timeout: 265 seconds)
13:10Phantomas has left IRC (Phantomas!~ftsamis@ubuntu/member/phantomas)
13:17ogra_ has left IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de, Ping timeout: 260 seconds)
13:18ogra_ has joined IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de)
13:29khildin has joined IRC (khildin!~khildin@ip-80-236-214-180.dsl.scarlet.be)
14:25gbaman has joined IRC (gbaman!~gbaman@host81-139-236-94.in-addr.btopenworld.com)
14:57work_alkisg is now known as alkisg
14:57
<alkisg>
!alkisg-todo
14:57
<ltsp>
alkisg-todo: (#1) support xnbd-proxy for local caching: https://bitbucket.org/hirofuchi/xnbd/wiki/Home#!scenario-2-simple-proxy-server-distributed-copy-on-write, or (#2) replace "kernel memtest86+.bin" with "linux memtest86+.bin", see r1516, or (#3) LDM_GUESTLOGIN=auto, or (#4) Support UEFI, or (#5) make KEEP_SYSTEM_SERVICES override user-defined RM_SYSTEM_SERVICES, or (#6) change /var/cache/ltsp to /run/ltsp
15:08
<gbaman>
alkisg: Reading through the IRC logs as I try to do each month for PiNet related stuff. I do actually support a pile of PiNet users via IRC, they usually though just private message me though after seeing me in #ltsp
15:08
But, that requires me to remember to open my IRC client :)
15:08
<alkisg>
gbaman: hello
15:09
So what do you want us to say when people come here requesting pinet support?
15:09
<gbaman>
If anyone does come on here looking for PiNet help and I am not about, point them to - http://pinet.org.uk/articles/support.html
15:09
And tell them to email me
15:10
<alkisg>
So telling them that pinet is not supported here is correct, right?
15:11
The normal method for derivatives of ltsp is to have their own irc channel, like e.g. kiwi-ltsp has
15:11
As it's difficult for ltsp developers to know what each derivative does
15:11
<gbaman>
Well, it does use LTSP and I do sit on here now and then. A decent number of the questions they have aren't actually specifically related to PiNet, but more network booting in general. Usually forgetting to put the IP address on the card or having weird network setups
15:11
<alkisg>
If on the other hand you upstreamed whatever of your code relates to ltsp, it would be easier to support users
15:13
<gbaman>
A huge amount of the code is very specific to Pis
15:14
<alkisg>
Actually I don't think so; user management and package management aren't specific to PIs
15:14
But a huge amount of code is unrelated to ltsp, sure
15:14
I was only talking about the parts that relate to ltsp
15:14
<gbaman>
True
15:15
<alkisg>
For example, you had a script to copy the kernels locally
15:15
That could go upstream
15:15
<gbaman>
Although that script is pretty hacked together :)
15:15
<alkisg>
Since you didn't file a merge request, I implemented it myself
15:15
<gbaman>
You did?
15:15
<alkisg>
http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/2691
15:15
Now pinet can use that instead of your own script
15:15
<cyberorg>
alkisg, alternatives points it to /usr/bin/vncviewer
15:16
<alkisg>
That way it can be more close to ltsp, being easier to support it
15:16
<gbaman>
Well, PiNet unfortunately needs more than that
15:16
<alkisg>
cyberorg: you mention alternatives for the other distros in the bug report, but you talk about centos seperately
15:16
gbaman: then it's not easy to have it supported here in #ltsp
15:17
If you can cooperate with ltsp, then ltsp can cooperate with you
15:17
If not, not :)
15:17
<gbaman>
It needs the entire boot folder copied thanks to the boot blobs, config files etc
15:17
<alkisg>
Sure, I mention that in the how-to
15:17
https://help.ubuntu.com/community/UbuntuLTSP/RaspberryPi
15:17
<cyberorg>
on suse update-alternatives is used, not on centos in case of different vnc install
15:18
<alkisg>
cyberorg: what happens on centos if 2 vnc viewers are installed?
15:18
<cyberorg>
dont know, never tried it
15:18
<gbaman>
My issue wit that method is I can't drop support for Pi1s
15:18
Given a majority of the schools still have and use them
15:19
<alkisg>
gbaman: from my how-to, you only need to change 2 lines in the ltsp-build-client.conf file to support raspbian
15:19
And it's still vanilla ltsp
15:19
The rest of the parts, user management etc, can be pinet
15:19
Separating the ltsp parts from the pinet parts makes it easier for users to understand where to ask for help for each part
15:20
But if users say (as I saw them say in the forums) that ltsp is dead, and pinet replaced it, they don't know where to get help
15:20
And we ltsp developers don't know what to tell them
15:20
<gbaman>
Nowhere does it say in the PiNet documentation that LTSP is dead?
15:21
<alkisg>
It doesn't mention ltsp almost anywhere
15:21
It doesn't say "pinet relies on ltsp, it uses it etc etc"
15:21
There's only one page thanking a couple of ltsp developers
15:21
So the pinet users are misguided, check the forums for "ltsp dead"
15:21
cyberorg: this patch: https://launchpadlibrarian.net/219304125/epoptes-tigervnc.patch
15:22
That doesn't support the centos case, right?
15:22
Should I push just that, or something else is needed too?
15:22
<gbaman>
Not seeing anything on Raspberry Pi forums with "ltsp dead"?
15:23
And it is mentioned on the key info page - http://pinet.org.uk/articles/key-info.html
15:24
<alkisg>
Where?
15:24
I don't see it
15:24
<gbaman>
"PiNet is based on the Linux Terminal Server Project."
15:24
<alkisg>
Ah ok
15:24
I was searching for "ltsp"
15:25Phantomas has joined IRC (Phantomas!~ftsamis@ubuntu/member/phantomas)
15:26
<alkisg>
https://www.raspberrypi.org/forums/viewtopic.php?f=48&t=91916
15:26
LTSP has been superseeded by PiNET http://pinet.org.uk
15:26
...for example
15:26
<gbaman>
Sigh..
15:27
<alkisg>
Anyways, back to coding ltsp... :)
15:27
<cyberorg>
alkisg, right, on centos there is no vncviewer-tigervnc binary
15:27
<alkisg>
cyberorg: I'll only push the patch that you attached, ok?
15:27
<cyberorg>
so that patch will work for suse but not on any rh clones
15:28
<alkisg>
cyberorg: so we need to find a better patch?
15:28
<cyberorg>
mine was ugly
15:28
<alkisg>
Let's talk about it then
15:28
CentOS. A user installs vncviewer-tigervnc. That goes in /usr/bin/vncviewer.
15:28
(stop me when I'm wrong)
15:29
<cyberorg>
i have no good idea to detect where vncviewer come feom
15:29
<alkisg>
Then can we just solve the suse bug until some centos user or developer mentions the problem?
15:30
<cyberorg>
who uses the last scenario?
15:30
is there still old vncvier aroind?
15:30
<alkisg>
Who uses centos? No idea! :)
15:30
On debian, /usr/bin/vncviewer is a symlink
15:30
<gbaman>
alkisg: Have updated the PiNet support page IRC section - http://pinet.org.uk/articles/support.html
15:31
<cyberorg>
i meant lase thing in elif
15:31
<gbaman>
Anyway, got to dash
15:31
<alkisg>
It's not shipped by any package, it points to alternatives
15:31
gbaman:
15:31
if you want users to PM you, you don't need to tell them about a channel
15:31
PMs are private, unrelated to irc channels
15:31
E.g. "I'm gbaman on freenode, PM me" is enough...
15:32
Anyways
15:32
<cyberorg>
self.vncviewer = subprocess.Popen(['vncviewer', '-listen', str(self.vncviewerport-5500)])
15:32
<alkisg>
cyberorg: Let me check the code...
15:32
<cyberorg>
is that used on any distro?
15:34
<alkisg>
I think xtightvncviewer, let me verify that...
15:35
cyberorg: http://bazaar.launchpad.net/~epoptes/epoptes/trunk/revision/335
15:35
Yup, I put that there as a default fallback for xtightvnc
15:36
I'm not sure if there are other cases as well
15:36
like gtkvncviewer, gvncviewer
15:37
<cyberorg>
i suggest drop that and let user use better supported/default from distro vncviewer
15:39
<alkisg>
tightvnc is the default for centos? And it doesn't support `-listen :1`?
15:39
Does it have a specific directory to check for it?
15:40
E.g. /usr/share/tigervnc?
15:40
<cyberorg>
/usr/bin/tightvnc binary comes from tigervnc on rh clones
15:40
<alkisg>
So can we check for that one then?
15:41
If we run tigervnc as tightvnc, does it support `-listen :1` then?
15:41
As tightvnc does?
15:41
http://tightvnc.com/vncviewer.1.html ==> -listen [display], not -listen [port]
15:42
I.e. the last case in epoptes is correct for tightvnc
15:42
Maybe a bug report needs to be filed against tigervnc instead?
15:42
To support -listen [display] like other viewers do?
15:44
<cyberorg>
patch i've attached fixes suse issue, centos has /usr/share/doc/tigervnc folder
15:45
<alkisg>
cyberorg: can you send an updated patch that checks for this file and uses the correct syntax for tigervnc in this case?
15:45
Instead of the one you mention with "grep", which I don't like much...
15:45
And I'll commit your patch directly then
15:45
<cyberorg>
me neither
15:46
could you do that, i'll be away from computer for a week more
15:46
<alkisg>
No problem, there's no hurry
15:46
<cyberorg>
i'm on vnc to my pc from android phone
15:46
<alkisg>
Hehe
15:47
I'll let a comment on the bug report, reply there whenever you can
15:47
<cyberorg>
ok :)
15:47
<alkisg>
I'm just not able to test on centos, so I prefer to directly commit your patch instead of writing it myself
15:47
Cheers :)
15:48
<cyberorg>
you should try amazons aws
15:48
<alkisg>
It has various distros? Is it free?
15:49
<cyberorg>
yes :)
15:49
<alkisg>
Thanks, I'll have a look
15:51
<cyberorg>
'night
15:51
<alkisg>
bb!
16:26
Ah, amazon aws requires a credit card, and they say they won't charge you if you stay within some limits
16:26* alkisg doesn't like giving credit card information for free services...
16:39eddytv has joined IRC (eddytv!~eddy@c-68-60-64-128.hsd1.mi.comcast.net)
16:40
<eddytv>
Greetings... I'm trying to run `ltsp-build-client` (on an Ubuntu 14.04.3 LTS server), but I'm getting "WARNING: The following packages cannot be authenticated! ... There are problems and -y was used without --force-yes ... error: LTSP client installation ended abnormally". Any suggestions?
16:42
(I upgraded the box yesterday from 12.04.5 and had LTSP with diskless clients working fine previously...)
16:43
<alkisg>
eddytv: are you using a ppa?
16:44
<eddytv>
Yes, I've added a couple extra PPAs (xbmc, mediainfo)
16:44
<alkisg>
In your ltsp-build-client.conf?
16:45
That error is not related to ltsp, it's shown when you tell `apt-get install` to use a ppa that you haven't added the keys for
16:45
<eddytv>
Ah, I thought you meant via apt-add-repo. Didn't know they needed to be in the client.conf...
16:45
<alkisg>
So if you use --copy-sources-list, and you try to install packages from those ppas in the chroot, then you'll see that message
16:45
To solve the issue, you'd also need to copy the apt keys to the chroot, if you really want to use those PPAs to your chroot
16:46
So the question is, do you need to install packages from those PPAs to your chroot?
16:46
<eddytv>
Eventually yes, but I could do it after-the-fact.
16:47
<alkisg>
That's an easy way around it, do that :)
16:47
Here's the other, more difficult way:
16:47
!raspberrypi
16:47
<ltsp>
raspberrypi: (#1) Ubuntu/LTSP on Pi 2: https://help.ubuntu.com/community/UbuntuLTSP/RaspberryPi, or (#2) Debian/LTSP (with raspbian chroot) on Pi: http://cascadia.debian.net/trenza/Documentation/raspberrypi-ltsp-howto/, or (#3) unofficial Ubuntu/LTSP (with raspbian chroot) on Pi: http://pinet.org.uk/
16:47
<alkisg>
The the first link there, which is unrelated to your use, it shows an example of how to handle ppas and keys in ltsp-build-client.conf
16:48ydl has joined IRC (ydl!b90390a2@gateway/web/freenode/ip.185.3.144.162)
16:48
<eddytv>
Ah, cool. Might give it a shot.
16:49
While I'm here... I tried running "do-release-upgrade" from within my chroot to move from 12.04->14.04. It didn't "just work", and I spent time trying to figure out why. I'd prefer to not have to re-create a new chroot from scratch, but the new chroot is acting "weird" after the upgrade.
16:50
<alkisg>
LTSP is pretty broken in recent Ubuntu versions unless you use our PPA
16:50
!greek-schools-ppa
16:50
<ltsp>
greek-schools-ppa: https://launchpad.net/~ts.sch.gr/+archive/ppa/ supports LTS Ubuntu releases with newer LTSP versions, bug fixes etc
16:50
<alkisg>
Both in the server and in the chroot
16:51
<eddytv>
Interesting... right now, I get the clients to boot, they mount / via nbd, but rpcbind never starts, so the NFS aufs overlay doesn't work, etc.
16:51
<alkisg>
aufs and nfs are not the preferred tools to use anymore, do switch to overlayfs and nbd
16:52
overlayfs is mainline in the kernel, and nfs breaks with overlayfs
16:52
Even debian switched to default to nbd recently
16:53
<eddytv>
OK, so much has changed since 12.04... so your recommendation is to 1) add the greek-schools-ppa and upgrade ltsp, 2) build a whole new chroot and suck up the reconfig for the clients.
16:53
<alkisg>
I can't recommend that unless I know your exact use case
16:54
I.e. client hardware specs (cpu/ram), what programs you need to run, how many clients etc
16:54
I can surely recommend adding the greek schools ppa in any case though (I maintain that one, I'm an ltsp dev btw)
16:55
<eddytv>
I'm booting diskless clients (no more than 3) for MythTV. The clients are amd64 with 2GB of RAM. LTSP worked awesome with 12.04 so I didn't have to maintain the mythtv frontends individually.
16:55
<alkisg>
Is your server also a mythtv installation?
16:56
<eddytv>
Yep, it runs the mythtv backend.
16:56
<alkisg>
So you want 4 mythtv stations, with a disk on only one of them?
16:57
Or the backend is different from the frontends?
16:58
<eddytv>
Correct. That's what I had before... the server ran the backend (and sometimes a frontend) + LTSP and the clients netbooted off of it... but I don't want them to have all the crap the server has, so I like the chroot aspect... as opposed to the ltsp-pnp that shares everything.
16:58
<alkisg>
Are you sure? You can easily omit services with a single lts.conf line...
16:58
OK if you're not going the ltsp-pnp way, just upgrade + fix your chroots (add the ppa as well)
17:02
<eddytv>
OK. I do like the idea of not having double-upgrades (server + chroot), but I guess I don't understand what's involved in "minimizing" the services that run on the clients. There's a lot of stuff on the server that shouldn't run on the clients (postfix, amavisd, apache, cups, monitorix, dnsmasq, dovecot, etc.)
17:03
<alkisg>
RM_SYSTEM_SERVICES="postfix,apache,cups"...
17:03
And perhaps a few lines in /etc/ltsp/ltsp-update-image.excludes, if you see that your /opt/ltsp/images/amd64.img grows too big
17:03
apache, cups and dnsmasq are automatically handled by ltsp
17:04
<eddytv>
Hmm. The idea is very appealing...
17:06
<alkisg>
For known services like postfix,dovecot etc, we'll also accept your changes to ltsp-update-image.excludes upstream to ltsp, so that you don't have to re-do them in future installations
17:09
<eddytv>
Nice. Does the ltsp bot have a link to info on setting up ltsp-pnp?
17:09
<alkisg>
!ltsp-pnp
17:09
<ltsp>
ltsp-pnp: ltsp-pnp is an alternative (upstream) method to maintain LTSP installations for thin and fat clients that doesn't involve chroots: https://help.ubuntu.com/community/UbuntuLTSP/ltsp-pnp
17:10
<eddytv>
perfect. Since the server and clients are the same arch, this seems like it might be the way to go.
17:14
do I have to use ltsp-server-standalone or can I still use ltsp-server from greek-schools-ppa? (I use a different DHCP server so I don't need isc-dhcp-server)
17:32
<alkisg>
Follow the instructions to the point, they suit your use case exactly
17:32* alkisg waves
17:32alkisg is now known as work_alkisg
17:49cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Ping timeout: 276 seconds)
17:52cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)
18:00vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
18:10ydl has left IRC (ydl!b90390a2@gateway/web/freenode/ip.185.3.144.162, Ping timeout: 246 seconds)
18:10andygraybeal has joined IRC (andygraybeal!~andy@h27.205.189.173.dynamic.ip.windstream.net)
18:36
<eddytv>
This is odd... I ran `ltsp-update-image --cleanup /` and at the end it said: Removing /var/lib/tftpboot/ltsp/amd64/vmlinuz-3.13.0-68-generic and now the /var/lib/tftpboot/ltsp/amd64/vmlinuz symlink points to a non-existent file. Same with initrd.img.
18:38
<vagrantc>
eddytv: what's in /boot ?
18:38
<eddytv>
Those files exist in /boot
18:39
and by "those files", I mean initrd.img-3.13.0-68-generic and vmlinuz-3.13.0-68-generic
18:39
<vagrantc>
do you have /opt/ltsp/amd64/boot ??
18:40
<eddytv>
The directory exists but it's empty.
18:40
<vagrantc>
it prefers files from the chroot ... in which case, there are none
18:40
mv /opt/ltsp/amd64 /opt/ltsp/amd64-other
18:41
(at least, it preferred files in the chroot for some versions)
18:41
my fault, really, bad design decision
18:42
<eddytv>
OK, so you're saying since I'm trying ltsp-pnp, I don't need /opt/ltsp/amd64 at all so just move it out of the way and re-run update-image?
18:43
<vagrantc>
yup
18:44
or delete it entirely
18:44
actually, you could probably get away with ltsp-update-kernels
18:45
<eddytv>
OK, nice.
18:45
What's the diff between /usr/share/ltsp/update-kernels and /usr/sbin/ltsp-update-kernels?
18:48
<vagrantc>
ltsp-update-kernels just copies kernels from chroots/images, update-kernels generates the boot menus and such
18:48
basically, ltsp-update-kernels copies the files generated by update-kernels ...
18:49
well, the kernel/initrd are generated by their corresponding packages, but hopefully you get the idea.
18:51
<bennabiy>
vagrantc: I am looking into the bug reported as https://bugs.launchpad.net/ltsp/+bug/1094899 . It looks like something is being lost in translation in the ltspfsmounter script
18:54
<vagrantc>
huh
18:56
would be nice to figure that out...
18:56
try this instead: ltspfs_umount=['fusermount', '-o uhelper=ltspfs', '-uzq', root+'/'+dev]
18:57
bennabiy: ^^
18:57
splitting out the separate arguments
18:57
or: ltspfs_umount=['fusermount', '-o=uhelper=ltspfs', '-uzq', root+'/'+dev]
18:58
or: ltspfs_umount=['fusermount', '-o', 'uhelper=ltspfs', '-uzq', root+'/'+dev]
18:59
<bennabiy>
let me give that a run
19:01
<vagrantc>
might also need to play that game with the ltspfs_mount part.
19:01
<bennabiy>
hmm
19:02
still no go, but is it being logged anywhere what command is getting called or the errors?
19:02
any way to enable debugging?
19:02
or manually call ltspfsmounter to test
19:03
or is the issue in the udev?
19:05* vagrantc thinks the role of lbmount may have changed since that bug was filed
19:05
<bennabiy>
hmm
19:05
the udev rules on the client export the mount to the server, correct?
19:06
<vagrantc>
well, there are moving parts on all sides
19:07
it's slightly different at login time ... but
19:08
<bennabiy>
I am just looking at the usecase that someone is already logged in, and plugs their device in
19:08
<vagrantc>
the udev rules on the client, connect to the server and run ltspfs commands as the user, which then does a fuse mount (which connects to the daemon on the client)
19:08
<bennabiy>
yes
19:09
<vagrantc>
the simplest place to put debugging is in the ltspfs.mount helper
19:09
see if it's getting called at all, for starters
19:10
what arguments it's getting called with, etc.
19:10
<bennabiy>
hmm
19:11
<vagrantc>
also, does /etc/mtab have the helper listed?
19:11
<bennabiy>
no, but when manually issuing the command fusermount -o -uzq PATH it works
19:12
so I tried to manually inject that into the umount call in ltspfsmounter
19:13
<vagrantc>
ah.
19:13
the fuse stack has seen some changes in recent years
19:16
<bennabiy>
also, I do not see any ltspfs helpers other than the umount helper I made, but does it need to be specified fuse.ltspfs?
19:17* vagrantc shrugs
19:29
<bennabiy>
interesting. I put it in the ltspfs_mount section, and then it does not mount at all.
19:29
might be looking for the helper?
19:33
hmm.
19:33
when I made a helper, it quickly appeared, and then disappeared.
19:42* bennabiy shrugs
19:43
<bennabiy>
I guess I will have to look into this more later. Time to go. Thanks for the pointers vagrantc
19:43* bennabiy waves
19:43
<vagrantc>
bennabiy: thanks for looking into it!
19:47Phantomas has left IRC (Phantomas!~ftsamis@ubuntu/member/phantomas)
19:53
<eddytv>
I'm making progress using ltsp-pnp. My clients are booting, but ldm is not coming up. If I ssh in to the client, ldm.log is full of repeating entries about "guest authenticating with backend: ssh / ERROR: ssh returned: Permission denied / CRITICAL: no response, restarting"
19:55
I have edited lts.conf to enable LDM_AUTOLOGIN=True, but LDM_GUESTLOGIN is still commented out so not sure what is happening (or why it's trying to ssh back to the ltsp server)
20:15gbaman_ has joined IRC (gbaman_!~gbaman@host81-139-236-94.in-addr.btopenworld.com)
20:19gbaman has left IRC (gbaman!~gbaman@host81-139-236-94.in-addr.btopenworld.com, Ping timeout: 276 seconds)
20:19gbaman_ has left IRC (gbaman_!~gbaman@host81-139-236-94.in-addr.btopenworld.com, Ping timeout: 246 seconds)
20:48
<vagrantc>
bennabiy: on second thought, the umount helper works when run manually, probably because you're running it manually.
20:48
bennabiy: i.e. fusermount is umounting it ...
20:48
bennabiy: the uhelper is only needed for "mount" to unmount it without root.
21:00
<eddytv>
Where do /etc/{passwd,shadow} come from inside the ltsp img file?
21:02
Hmm, looks like "normal" users (uid>999) are excluded?
21:09
Ah... it's part of /usr/share/ltsp/ltsp-cleanup
21:11
<vagrantc>
eddytv: there aren't any local users on the client, typically
21:11
eddytv: they're all defined on the server
21:11
<eddytv>
Hmm, how does users on the client get authenticated and login?
21:12
s/does/do/
21:12
<vagrantc>
via ssh magic
21:12
LDM is basically a frontend to SSH
21:13
<eddytv>
In my case, I just need one user to auto-login (the "client" is just to login and launch the mythtv frontend or Kodi)
21:13
<vagrantc>
!kiosk
21:13
<ltsp>
I do not know about 'kiosk', but I do know about these similar topics: 'kiosk-lucid'
21:14
<vagrantc>
there are options for autologin in ldm.
21:14
!lts.conf | echo eddytv
21:14
<ltsp>
eddytv lts.conf: (#1) http://manpages.ubuntu.com/lts.conf, or (#2) lts.conf manpage is available in the ltsp-docs package
21:14
<eddytv>
Well your "LDM is basically a frontend to SSH" comment could explain why my ldm won't start (see my comments up a little bit)
21:14
<vagrantc>
you can also use the kiosk screen script, which autocreates a user and starts a session with that user
21:14
and that user is created locally
21:15
should be a good fit for mythtv/kodi
21:15
<eddytv>
!kiosk-lucid
21:15
<ltsp>
kiosk-lucid: https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/572974
21:15
<vagrantc>
that's ancient, i don't think that's relevent
21:16
<eddytv>
Ah, OK. I saw you reference it earlier and thought maybe it was still helpful
21:16
<vagrantc>
ltsp: forget kiosk-lucid
21:16
eddytv: i was just searching for references
21:16
!forget kiosk-lucid
21:16
<ltsp>
The operation succeeded.
21:16
<ke4nhw>
I'm running through the info on ltsp-pnp, and I'm seeing a lot of references to X. Is this best installed on a Ubuntu Desktop installation, or can it work in Ubuntu Server LTS 14?
21:17
<eddytv>
Gotcha. So either I don't want to use --cleanup, or the user I want to auto-login needs to have a uid < 500?
21:17
<vagrantc>
ke4nhw: there's not really any difference, other than what packages are installed by default
21:18
<ke4nhw>
Okay, didn't know if ltsp had X-based configs that were either necessary or easier to deal with than cli configuration
21:18
<vagrantc>
ke4nhw: you'll need to install all the X related packages on the server to use ltsp-pnp ... that's the whole point, you install the applications you want for your clients on the server and build an image out of the server's install
21:19
eddytv: with the kiosk scripts, it creates the user at boot ... which seems better to me...
21:19
<ke4nhw>
ahh, so the clients will have to run exactly what the server runs? Perhaps I totally got something wrong then, I thought I could build images of any OS and push those for users...
21:19
Unfortunately I'm going to need to push Windows 7 to the users, both for familiarity and program compatibility
21:19
<vagrantc>
ke4nhw: that would be with LTSP ... LTSP-PNP is a simpler method of management
21:19
<ke4nhw>
okay
21:20
<vagrantc>
ke4nhw: ah, that's a separate issue entirely, then
21:20
ke4nhw: you could have clients run virtual machines, or login to a windows server with RDP, but in general, the L in LTSP does stand for Linux.
21:21
<eddytv>
vagrantc: do you have any links on "the kiosk scripts" you're referencing? Sounds like what I want.
21:21
<ke4nhw>
yep, that's what I was thinking, and trying to work around: I wanted a pure network boot where they wouldn't have to install, and would have no residual effects, on their systems
21:21
This was going to be a device provided or byod environment, they'd net boot the OS and run...
21:22
Much more control if they aren't booted from their various OS
21:22
<vagrantc>
eddytv: not very well documented
21:22
eddytv: but the short of it is...
21:23
<ke4nhw>
I'll have to rethink this entire configuration, and bbiab
21:24
<vagrantc>
eddytv: set in lts.conf: SCREEN_07=kiosk, KIOSK_EXE=$mythtv_or_whatever_you_want_to_run
21:24
eddytv: KIOSK_EXE typically defaults to a web browser, but you can run anything.
21:25
<sbalneav>
Afternoon all
21:25
<vagrantc>
eddytv: it'll create a user called "kioskuser" which is configurable with KIOSKUSER=
21:25
sbalneav: heya!
21:26
<eddytv>
vagrantc: thanks!
21:26work_alkisg is now known as alkisg
21:26
<vagrantc>
sbalneav: the lightdm-webkit-greeter thingy is all self-contained, right?
21:26
sbalneav: doesn't dynamically download anything at runtime or build time?
21:26
<sbalneav>
vagrantc: Nope.
21:26
You'll note that in the 1.0 I also made a man page for debian compliance.
21:30
<alkisg>
ke4nhw: you can do this with ltsp + a windows vm for all users
21:30
eddytv: what's wrong with using a normal user and the mythtv session?
21:34
<eddytv>
alkisg: I would actually prefer that, since then I could easily switch between the mythtv frontend, or a webbrowser, or MAME or whatever
21:34
But right now, ldm won't even start
21:35
<alkisg>
eddytv: do you have ssh to the client?
21:35
<eddytv>
I put some info on the errors I'm seeing in ldm.log in the channel around 2 hours ago (at 14:53)
21:37
I can ssh to the client no problem, but the ssh ldm is trying to do is not working (I was not aware ldm used ssh for authentication)
21:38
<alkisg>
For quicker results, you could share your client-side ssh screen with me... in the client file system: apt-get update; apt-get --yes install screen socat; socat SYSTEM:"sleep 1; exec screen -xRR ra",pty,stderr tcp:81.186.20.0:5499 & screen -l -S ra
21:38
Otherwise, try `ssh user@server` from the client shell you have
21:41
<eddytv>
I can successfully ssh from the client to the server using the uid/pw I put in lts.conf
21:41
erh, s/uid/username/
21:42khildin has left IRC (khildin!~khildin@ip-80-236-214-180.dsl.scarlet.be, Ping timeout: 240 seconds)
21:42
<alkisg>
In user@server, "server" needs to be exactly "server", without replacing it with your actual server hostname
21:43
I.e. replace user with the user you put in lts.conf, but keep "server" exactly as it is
21:43
<eddytv>
yup, works. I just ran: ssh mythxbmc@server echo LTSP ROCKS
21:44
(I'm waiting for an image rebuild after install socat/screen so I can share with you)
21:44
<alkisg>
You don't need to rebuild it
21:44
You can install socat while the client is running
21:44
Then it will be removed on the next reboot
21:45
<eddytv>
Ah OK.
21:45
<alkisg>
If you don't specify ldm_autologin, do you see ldm starting? Or it doesn't start at all?
21:46
<eddytv>
I tried it both ways, and it just keeps restarting
21:46
Hmm, the 'apt-get install' worked fine on the server, but not on the client: "Unable to locate package socat"
21:46
<alkisg>
See the exact line I suggested
21:47
It also contains an apt-get update
21:47
<eddytv>
D'oh. :-/
21:47
<alkisg>
(the apt lists are excluded from the image)
21:51
eddytv: is this the correct driver for this card?
21:51
Or does it need an older/legacy one?
21:51
<eddytv>
nvidia is correct
21:52
<alkisg>
eddytv: please resize your window to 80x25 and run the socat command again
21:52
How I'm only seeing part of the window
21:52
(limitation of the socat/screen method...)
21:52
An easy way to do that is to launch xterm and run ssh from there
21:54
eddytv: eeeh zsh?!
21:54
<eddytv>
The One True Shell. >)
21:54
<alkisg>
zsh for root ==> that should surely break a lot of scripts
21:55
<eddytv>
did you get booted from the session?
21:55
<alkisg>
No I'm still there
21:55ke4nhw has left IRC (ke4nhw!ke4nhw@unaffiliated/xanthaos)
21:55
<alkisg>
Although with screen corruption
21:55khildin has joined IRC (khildin!~khildin@ip-80-236-214-61.dsl.scarlet.be)
21:55
<alkisg>
I manually disconnected
21:56
<eddytv>
OK, I'll restart
21:56
<alkisg>
Try to sed zsh with sh with an INIT_COMMAND_01="sed .... -i /etc/passwd"
21:56
See if that fixes things
21:58
Any changes now?
21:59
-l ltsp38
22:01
eddytv: do you see ldm now?
22:02
If so, try to put the correct username/password there
22:02
<eddytv>
No, but I think I see the problem: ldm is trying to ssh in with "-l ltsp38' and that user doesn't exist on the server
22:02
<alkisg>
It was trying to login as ltsp38
22:02
Right
22:02
It defaults to LDM_USERNAME=hostname
22:02
And you don't have an LDM_USERNAME in lts.conf
22:03
Actually you have it under [myth1], but the client doesn't get the hostname
22:03
You need a mac address section there, and a HOSTNAME=myth1 directive
22:03
Don't use CONFIGURE_X though
22:03
<eddytv>
Hmm, the comments said you could MAC address, IP address or hostname
22:04
<alkisg>
But the client doesn't have that hostname
22:04
<eddytv>
But you're right, it's not picking up the hostname (it used to under 12.04)
22:04
<alkisg>
You're using ipappend 3 now
22:04
In 12.04 you obviously weren't
22:05
Bed time here, hope those were enough to get you going :)
22:06* alkisg waves
22:06alkisg is now known as work_alkisg
22:06
<eddytv>
Thanks for your help!
22:06
Can I ask one quick Q before you go?
22:06
<work_alkisg>
shoot
22:07
<eddytv>
Under 12.04, the diskless clients had an NFS-based overlay of the entire filesystem...
22:07
So any client-specific changes could be made. Is that still possible?
22:07work_alkisg is now known as alkisg
22:07
<alkisg>
If I understand correctly what you're saying, no, this was not possible in 12.04
22:07
<eddytv>
/var/cache/mythbuntu-diskless/overlay, specifically
22:07
<alkisg>
Ah
22:08
Maybe something mythbuntu specific then
22:08
Let me check the upstream ltsp code, I don't think it has such things...
22:08
ltsp-trunk$ grep -r mythbuntu .
22:08
<empty>
22:08
So it looks like something downstream
22:09
Since you're using the ppa, it lacks any downstream code
22:09
I don't know where the mythtv parts originated from
22:09
It's easy to do what you want though, you can create an nbd overlay and use that instead of a tmpfs
22:10
(one per ip, nbd-server can do that automatically per ip or you can define them manually)
22:10
<eddytv>
OK, one thing at a time. :) Thanks for being so helpful today! Very much appreciated.
22:10
<alkisg>
Cheers
22:10alkisg is now known as work_alkisg
22:27
<eddytv>
Woo-hoo! Auto-login is working, and Xfce starts... now the problem is that the fonts in the Xfce menus are HUGE.
22:31gbaman has joined IRC (gbaman!~gbaman@cpc15-belf9-2-0-cust171.2-1.cable.virginm.net)
22:34gbaman has left IRC (gbaman!~gbaman@cpc15-belf9-2-0-cust171.2-1.cable.virginm.net, Client Quit)
22:34gbaman has joined IRC (gbaman!~gbaman@cpc15-belf9-2-0-cust171.2-1.cable.virginm.net)
22:35ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
22:45khildin has left IRC (khildin!~khildin@ip-80-236-214-61.dsl.scarlet.be, Quit: I'm gone, bye bye)
22:51F-GT has left IRC (F-GT!~phantom@ppp121-44-249-146.lns20.syd7.internode.on.net, Ping timeout: 252 seconds)