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


Channel log from 6 August 2015   (all times are UTC)

02:17pppingme has joined IRC (pppingme!~pppingme@unaffiliated/pppingme)
02:20Cruz4prez has left IRC (Cruz4prez!~pppingme@unaffiliated/pppingme, Ping timeout: 256 seconds)
02:25elias_a has left IRC (elias_a!elias@hilla.kapsi.fi, Ping timeout: 252 seconds)
02:27pppingme is now known as Cruz4prez
02:27elias_a has joined IRC (elias_a!elias@hilla.kapsi.fi)
04:22Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas, Ping timeout: 240 seconds)
05:27Fenuks has joined IRC (Fenuks!~Fenuks@mail.c-lan.ru)
05:31ricotz has joined IRC (ricotz!~rico@p5B2A999B.dip0.t-ipconnect.de)
05:31ricotz has joined IRC (ricotz!~rico@ubuntu/member/ricotz)
06:00Fenuks has left IRC (Fenuks!~Fenuks@mail.c-lan.ru, Ping timeout: 246 seconds)
06:16Fenuks has joined IRC (Fenuks!~Fenuks@mail.c-lan.ru)
06:18uXus has left IRC (uXus!~uXus@217.77.222.72, Remote host closed the connection)
06:19gdi2k has left IRC (gdi2k!~gdi2k@119.94.4.10, Ping timeout: 244 seconds)
06:21uXus has joined IRC (uXus!~uXus@217.77.222.72)
06:22Fenuks has left IRC (Fenuks!~Fenuks@mail.c-lan.ru, Ping timeout: 250 seconds)
06:23mikkel has joined IRC (mikkel!~mikkel@mail.dlvs.dk)
06:31vmlintu has joined IRC (vmlintu!~vmlintu@a91-152-200-13.elisa-laajakaista.fi)
06:38Fenuks has joined IRC (Fenuks!~Fenuks@mail.c-lan.ru)
06:41telex has left IRC (telex!teletype@freeshell.de, Remote host closed the connection)
06:41epoptes_user1 has joined IRC (epoptes_user1!bcc03458@gateway/web/freenode/ip.188.192.52.88)
06:42telex has joined IRC (telex!teletype@freeshell.de)
06:49epoptes_user1 has left IRC (epoptes_user1!bcc03458@gateway/web/freenode/ip.188.192.52.88, Quit: Page closed)
06:51vmlintu has left IRC (vmlintu!~vmlintu@a91-152-200-13.elisa-laajakaista.fi, Ping timeout: 252 seconds)
07:23Grembler has joined IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net)
07:25Grembler has left IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net, Read error: Connection reset by peer)
07:26Grembler has joined IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net)
07:26GremblerBean has joined IRC (GremblerBean!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net)
07:33vmlintu has joined IRC (vmlintu!~vmlintu@37-219-101-92.nat.bb.dnainternet.fi)
08:26vmlintu has left IRC (vmlintu!~vmlintu@37-219-101-92.nat.bb.dnainternet.fi, Ping timeout: 244 seconds)
08:47cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Ping timeout: 244 seconds)
08:55vmlintu has joined IRC (vmlintu!~vmlintu@finlandiahall.info)
09:19Grembler has left IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net, Quit: I Leave)
09:32vmlintu has left IRC (vmlintu!~vmlintu@finlandiahall.info, Ping timeout: 240 seconds)
09:57alkisg is now known as work_alkisg
10:06cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)
10:39Fenuks has left IRC (Fenuks!~Fenuks@mail.c-lan.ru, Read error: Connection reset by peer)
10:45gvy has joined IRC (gvy!~mike@altlinux/developer/mike)
10:48Fenuks has joined IRC (Fenuks!~Fenuks@mail.c-lan.ru)
10:55Shoeb has joined IRC (Shoeb!cbc0df3a@gateway/web/freenode/ip.203.192.223.58)
10:59Shoeb has left IRC (Shoeb!cbc0df3a@gateway/web/freenode/ip.203.192.223.58, Client Quit)
11:05gdi2k has joined IRC (gdi2k!~gdi2k@180.191.109.246)
11:10vmlintu has joined IRC (vmlintu!~vmlintu@37-219-101-92.nat.bb.dnainternet.fi)
11:12Faith has joined IRC (Faith!~paty@unaffiliated/faith)
11:31vmlintu has left IRC (vmlintu!~vmlintu@37-219-101-92.nat.bb.dnainternet.fi, Ping timeout: 240 seconds)
11:35Shoeb has joined IRC (Shoeb!cbc0df3a@gateway/web/freenode/ip.203.192.223.58)
11:46danau11 has joined IRC (danau11!~durban@static-72-89-243-139.nycmny.fios.verizon.net)
11:54danau11 has left IRC (danau11!~durban@static-72-89-243-139.nycmny.fios.verizon.net)
12:23
<Hyperbyte>
Shoeb, hi
12:23
!ask
12:23
<ltsp>
ask: Don't ask to ask a question, simply ask it, and if someone knows the answer, they'll respond. Please hang around for at least a full hour after asking a question, as not everybody constantly monitors the channel.
12:23
<Hyperbyte>
:-)
12:32danau111 has joined IRC (danau111!~durban@static-72-89-243-139.nycmny.fios.verizon.net)
12:33danau111 has left IRC (danau111!~durban@static-72-89-243-139.nycmny.fios.verizon.net)
12:49
<zamba>
anyone used raspberry pi as a thin client?
12:54Shoeb has left IRC (Shoeb!cbc0df3a@gateway/web/freenode/ip.203.192.223.58, Quit: Page closed)
12:57
<gvy>
zama, yandex search suggests http://cascadia.debian.net/~vagrant/rpi-ltsp-howto.txt as the first result
13:19
<zamba>
i was more thinking about the performance
13:19
if it in fact works
13:20* gvy would ask the same folks but theoretically should be fine as it's roughly PI..PII
13:37Fenuks has left IRC (Fenuks!~Fenuks@mail.c-lan.ru, Ping timeout: 250 seconds)
13:43ben_roose has joined IRC (ben_roose!~roose@roose.cs.wichita.edu)
13:49vmlintu has joined IRC (vmlintu!~vmlintu@a91-152-200-13.elisa-laajakaista.fi)
13:50
<work_alkisg>
zamba, I think it's OK as a thin client... but, thin clients in general suck, and as a *fat* client pi sucks as well... so imho it's not worth it :)
13:50work_alkisg is now known as alkisg
13:50danau11 has joined IRC (danau11!~durban@static-72-89-243-139.nycmny.fios.verizon.net)
13:50danau11 has left IRC (danau11!~durban@static-72-89-243-139.nycmny.fios.verizon.net)
14:13mikkel has left IRC (mikkel!~mikkel@mail.dlvs.dk, Quit: Leaving)
14:23
<zamba>
alkisg: agreed
14:24
alkisg: that's my conclusion working with the pis myself.. they work fine headless running a simple task, but if you put a human in front of it, complaints starts coming
14:26Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
14:29vmlintu has left IRC (vmlintu!~vmlintu@a91-152-200-13.elisa-laajakaista.fi, Ping timeout: 265 seconds)
14:57danau111 has joined IRC (danau111!~durban@static-72-89-243-139.nycmny.fios.verizon.net)
14:57danau111 has left IRC (danau111!~durban@static-72-89-243-139.nycmny.fios.verizon.net)
15:06telex has left IRC (telex!teletype@freeshell.de, Remote host closed the connection)
15:08telex has joined IRC (telex!teletype@freeshell.de)
15:57vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
16:02
<alkisg>
vagrantc: about https://bugs.launchpad.net/ltsp/+bug/1352038, different /boot partition and ltsp-pnp,
16:02
I can't find any way to do it properly with the newer overlayfs system, other than running bind-mount *on top* of the cow system,
16:03* vagrantc waves from UTC+2
16:03
<vagrantc>
my network connection is questionable at best for the moment
16:03
<alkisg>
so for precaution, I can remount it ro
16:03
Wow, welcome :)
16:03
Jet lag etc?
16:03
<vagrantc>
yeah, a bit travel-weary
16:04
alkisg: what's different from how the aufs code handles it?
16:04
<alkisg>
I think in aufs you can tell it the mount path
16:05
In overlayfs you can't, so even multiple overlays can't solve that problem...
16:05
<vagrantc>
hrm.
16:06
<alkisg>
I sent a simplified question in the overlayfs mailing list: http://blog.gmane.org/gmane.linux.file-systems.union
16:06
Multiple lower dirs are only available in 4+ kernel, but one cannot specify the path there either
16:06
<vagrantc>
i thought i tested that with debian's overlayfs ... maybe it's ubuntuisms?
16:07
ah, that would make sense ... when i tested it was with upstream 4.x
16:07
<alkisg>
With the patched overlayfs, in previous ubuntu versions, it works working fine
16:07
Now I think Ubuntu's using the upstream kernel implementation...
16:07
<vagrantc>
with no custom changes?
16:08
<alkisg>
4.x doesn't work for me either
16:08
I didn't look at the sources
16:08* vagrantc will try again at some pont
16:08
<alkisg>
Is mounting the submounts RO on top of the overlay acceptable?
16:09
It would produce errors if someone tried to e.g. remove things from /boot or /home or whatever other submount he has...
16:09staffencasa has left IRC (staffencasa!~staffenca@8-220.ptpg.oregonstate.edu, Read error: Connection reset by peer)
16:09
<alkisg>
But in 99% of the cases it should work fine
16:09
<vagrantc>
i guess it's the best workaround we have...
16:10
<alkisg>
We don't want to prefer aufs when it's available, do we?
16:10
<vagrantc>
so you can't mount a unionfs on top of a unionfs?
16:10
<alkisg>
I can, but it's worthless without submounts
16:10
<vagrantc>
s,unionfs,overlayfs,g
16:10
<ogra_>
union-inception ? :)
16:11
<alkisg>
And if I create a directory structure, and mount the overlay where I want it, e.g. mkdir /fakedir/home and then mount the home partition to /fakedir/home, and then try to use that in an overlay, I won't see the home submount at all
16:11* vagrantc smiles
16:12
<alkisg>
At least, I wasn't able to... maybe someone else needs to take a look there, but personally I could only find the RO bind-mounts workaround
16:13
Just for the logs, here's what I tried:
16:14
1) to create the desired structure with bind-mounts, and then use that as the lower dir. Overlayfs there discards the submounts, so it's unusable
16:14
2) to use multiple lowerdirs, as allowed in the 4+ kernel. They don't support specifying paths, so it's unusable.
16:15vmlintu has joined IRC (vmlintu!~vmlintu@a91-152-200-13.elisa-laajakaista.fi)
16:15
<alkisg>
3) to construct the desired structure incrementally, using overlayfs in each step. This again doesn't work because it doesn't provide for specifying a path.
16:16
and 4), like (3) but with mkdir/bind-mount before the overlayfs => again unusable because it's like (1)
16:16
So the only thing I got is (5), use only the lowerdir + overlayfs, and then bind-mount all the submounts as RO
16:16
<vagrantc>
i don't get what you can't mount multiple overlayfs on $mnt/, $mnt/home, $mnt/boot, etc.
16:17
<alkisg>
Are you talking about (3), i.e. overlayfs that has a lowerdir=another overlayfs?
16:21vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Ping timeout: 260 seconds)
16:24alkisg is now known as work_alkisg
16:29staffencasa has joined IRC (staffencasa!~staffenca@8-220.ptpg.oregonstate.edu)
16:59vmlintu has left IRC (vmlintu!~vmlintu@a91-152-200-13.elisa-laajakaista.fi, Ping timeout: 260 seconds)
18:15
<zamba>
Updating /srv/tftp directories for chroot: /opt/ltsp/i386
18:15
error: LTSP client installation ended abnormally
18:16
ok?
19:13
no actual error message
19:20
<Hyperbyte>
zamba, sure there's no error a bit higher up?
19:25
<zamba>
Hyperbyte: i'll re-run it.. one sec
19:25
.. or rather.. maybe not one sec
19:25danau11 has joined IRC (danau11!~durban@static-72-89-243-139.nycmny.fios.verizon.net)
19:28
<Hyperbyte>
:-)
19:28
I kinda mean... you pasted the last two lines, but there's probably more information above that -why- it failed
19:29
Would be more helpful if you had the whole output log, or at least more of the last lines.
19:29danau11 has left IRC (danau11!~durban@static-72-89-243-139.nycmny.fios.verizon.net, Ping timeout: 240 seconds)
19:33gvy has left IRC (gvy!~mike@altlinux/developer/mike, Quit: Leaving)
19:52
<zamba>
Hyperbyte: can't see anything in the preceeding lines either
19:54
Hyperbyte: running the command yet again
20:12ben_roose has left IRC (ben_roose!~roose@roose.cs.wichita.edu, Ping timeout: 245 seconds)
20:12ben_roose has joined IRC (ben_roose!~roose@roose.cs.wichita.edu)
20:15
<zamba>
Hyperbyte: http://pastebin.com/gXkiCrbq
20:16
Hyperbyte: can you spot any problems there?
20:19ricotz has left IRC (ricotz!~rico@ubuntu/member/ricotz, Quit: Ex-Chat)
20:29work_alkisg has left IRC (work_alkisg!~alkisg@srv1-dide.ioa.sch.gr, Ping timeout: 240 seconds)
20:58
<Hyperbyte>
zamba, it actually looks like it made it
20:58
Weird.
20:58
You could try running ltsp-update-image
20:58
And then ltsp-update-kernels
20:59
Oh wait
20:59
This is probably NFS right?
20:59
If so then skip the first.
21:09Faith has left IRC (Faith!~paty@unaffiliated/faith, Quit: Saindo)
21:39telex has left IRC (telex!teletype@freeshell.de, Remote host closed the connection)
21:40telex has joined IRC (telex!teletype@freeshell.de)
22:47staffencasa has left IRC (staffencasa!~staffenca@8-220.ptpg.oregonstate.edu, Read error: Connection reset by peer)
22:52staffencasa has joined IRC (staffencasa!~staffenca@8-220.ptpg.oregonstate.edu)
23:25highvoltage has left IRC (highvoltage!~highvolta@ubuntu/member/highvoltage, Ping timeout: 256 seconds)
23:26highvoltage has joined IRC (highvoltage!~highvolta@ubuntu/member/highvoltage)
23:45Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas, Ping timeout: 264 seconds)