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


Channel log from 10 April 2019   (all times are UTC)

00:02mmarconm has joined IRC (mmarconm!~mmarconm@unaffiliated/mmarconm)
00:03fnurl has left IRC (fnurl!url@host81-154-10-111.range81-154.btcentralplus.com, Ping timeout: 258 seconds)
00:03mmarconm has left IRC (mmarconm!~mmarconm@unaffiliated/mmarconm, Remote host closed the connection)
00:04mmarconm has joined IRC (mmarconm!~mmarconm@unaffiliated/mmarconm)
00:13fnurl has joined IRC (fnurl!fnurl@host81-154-10-70.range81-154.btcentralplus.com)
03:40mmarconm has left IRC (mmarconm!~mmarconm@unaffiliated/mmarconm, Quit: Leaving)
03:48vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
04:26map7 has joined IRC (map7!~user@103.232.216.31)
04:31
<map7>
I've got a problem that everytime I to a ltsp-update-image I have to go and edit my pxelinux.conf/default file and enter in the default & timeout as ltsp-NBD-4.9.0-0.bpo.7-686-pae. They seem to be reset to ltsp-NBD everytime. I know I should be editing /opt/ltsp/i386/etc/ltsp/update-kernels.conf but it doesn't seem to be reading that file
04:32
The update-kernels.conf has ONTIMEOUT=ltsp-NBD-4.9.0-0.bpo.7-686-pae and LIST_KERNELS_DEFAULT=ltsp-NBD-4.9.0-0.bpo.7-686-pae is this correct?
04:35
<vagrantc>
you have to also regenerate the config within the chroot after editing update-kernels.conf
04:35
ltsp-chroot /usr/share/ltsp/update-kernels
04:35
and then ... maybe rebuild the image ... i'm not 100% sure ...
04:36
and then run ltsp-update-kernels
04:36
so if you edit update-kernels.conf to be the way you want... it should generate /opt/ltsp/i386/boot/pxelinux.cfg/* ...
04:37
and /opt/ltsp/i386/boot/pxelinux.cfg/* is what gets copied to your tftp directory
04:37
yes, it's confusing.
04:50
<map7>
vagrantc: that half worked. It updated my pxelinux.conf/default file but only for timeout, it didn't change my default
04:52
Dont' worry I got it
04:52
vagrantc: Is this already documented on the wiki?
05:10
<vagrantc>
no idea what the state of the documentation is
05:26statler has joined IRC (statler!~Georg@p5489790B.dip0.t-ipconnect.de)
05:34
<map7>
vagrantc: Ok well I've added it to here just incase others ask: http://wiki.ltsp.org/wiki/Configuration#Updating_kernel
05:34
vagrantc: I didn't need to do the ltsp-update-image, just the ltsp-update-kernels to update the pxelinux.conf/default
05:40
<alkisg>
map7: using nbd or nfs?
05:41
I think some ltsp versions prefer pxelinux.cfg/default from the chroot, while others from the image
05:42
In any case, this whole infrastructure will get replaced by a simple, user editable file
05:42
<map7>
alkisg: I'm using nbd on the same machine we worked on the other day
05:42
<alkisg>
So at this point I'm not sure updating the wiki will help anyone
05:43
<map7>
It's better to have some documentation than none though, so I just put it up there incase others were looking for the same answer
05:44
When is the whole infrastructure getting replaced?
05:44
Are you talking about LTSP 6?
05:45
<alkisg>
Yes
05:45
Hopefully this summer
05:45
But even if it's not done this summer, I will do that pxelinux.cfg part this summer anyway
05:45
To add support for uefi etc
05:46
And the site move
05:46
<map7>
oh ok, is there still going to be a wiki?
05:47
<alkisg>
Documentation will be maintained in github, and user contributions will need to be in the form of pull requests
05:47
If someone is very dedicated, he'll be added to the team
05:47
<map7>
that sounds great to me
05:48
<alkisg>
I'm not yet sure if it's going to be a "github wiki" or a "github pages, markedown+jekyll", but there's not much difference between them anyway
05:52
<map7>
alkisg: ok well I'll look out for when you move your documentation and I'll send pull requests then.
05:57
<alkisg>
Great
05:57
I would say I'd back up the old wiki, but it has so much spam that I'm not sure it's worth the effort
05:57os_a has joined IRC (os_a!~Thunderbi@195.112.116.22)
06:00
<map7>
alkisg: On the new github wiki you are creating we could put up there LTSP 5.x and LTSP 6.x documentation
06:00
and a migration path for those on the old version
06:00
<alkisg>
Nah, I want the new site to be completely unrelated
06:00
With no migration path :D
06:00
!ltsp-discuss
06:00
<ltsp>
ltsp-discuss: at https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
06:00
<alkisg>
E.g. that one will only be for ltsp 5
06:00
While ltsp 6 will be "github issues"
06:01
Searchable, linkable, reusable etc
06:01
Since we're keeping the same name, the migration path would be: ltsp-config remove-ltsp5
06:02
...which would move all the old configs to a backup folder
06:02
I never liked the idea of mailing lists for product support; this is a good time to move forward :)
06:03
<map7>
yes I agree
06:03
github issues is much better
06:03
<alkisg>
I would prefer a forum too, for "general talk", but since github etc don't provide one, the issues will have to be enough
06:04
Fortunately they do support "issue templates" where we can set up "bug report", "question", "enhancement" templates etc
06:05
<map7>
Cool
06:05
<alkisg>
map7: if you have time to contribute, here's something that would really help:
06:05
<vagrantc>
is there a way to backup the issues in github?
06:05ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
06:06
<alkisg>
set up a github page, similar to epoptes.org, using markdown and jekyll,
06:06
then we can take the result as a starting point for the new ltsp.org
06:07
vagrantc: I think they're a git repository as well
06:07
<vagrantc>
alkisg: i didn't think the issues were in git ... though that would be nice.
06:09
<alkisg>
In any case, they have an API for accessing the data, so it shouldn't be hard: https://developer.github.com/v3/issues/
06:09
<map7>
alkisg: I'll see how I go I'm pretty strapped for time right now. I do document everything I do with LTSP though so when it comes to documenting the new LTSP6 I can help there
06:09
<alkisg>
I see various scripts around for backing up the issues
06:09
I think the old documentation won't really help in ltsp6, it'll be obsolete
06:10
<vagrantc>
though, i can see in the worst case scenario, loosing all old crufty issues and starting fresh isn't the worst thing
06:10
:)
06:10
<alkisg>
Ah sure, for ltsp7, losing the ltsp6 issues won't really matter :)
06:10
<map7>
I know, but when I setup LTSP6 on our system I can add to the documentation
06:11
<vagrantc>
i do like the idea of pull requests for documentation updates ...
06:11
<alkisg>
E.g. now I really don't care about the ltsp5 issues we have in launchpad - to migrate them to ltsp6, that is
06:11
<vagrantc>
it keeps it fairly easy to edit, without the pages become a free-for-all
06:11
<alkisg>
I guess only 1 out of 10 would be valid for ltsp6
06:12
<vagrantc>
yeah, i think starting with a clean slate is a huge part of the attraction
06:15
<alkisg>
It's a pitty github/gitlab don't offer integration for translations, and we'll need to maintain the bzr-based launchpad mirrored branches...
06:15
Ah btw, if we won't have ldm anymore, do we really care about translations for ltsp?
06:16
Personally I feel fine to request that people using the command line also know basic english
06:16
(while for GUI programs, I surely like the translations)
06:20
vagrantc: what's the exact meaning of "vsc-git" etc in debian/control? Are the following correct?
06:20
Vcs-Git: https://github.com/sch-scripts/sch-scripts.git
06:20
Vcs-Browser: https://github.com/sch-scripts/sch-scripts
06:24kjackal has joined IRC (kjackal!~quassel@2a02:587:3119:ef00:550e:e9d8:ce19:9e42)
06:31kjackal has left IRC (kjackal!~quassel@2a02:587:3119:ef00:550e:e9d8:ce19:9e42, Ping timeout: 258 seconds)
06:37davschr has joined IRC (davschr!~ds@p200300E22BC6C500DE85DEFFFE98CDD1.dip0.t-ipconnect.de)
06:49
<vagrantc>
alkisg: if that includes the branch with the debian directory, that's fine
06:49
<alkisg>
Great
06:49
<vagrantc>
it's used by tools like "debcheckout PACKAGE" to get the sources for PACKAGE
06:50
<alkisg>
vagrantc: the vcs-browser? or just vcs-git?
06:50
The browser is just the github landing page, it lists the commits but I don't think it's usable by tools
06:50
<vagrantc>
alkisg: vcs-git ... vcs-browser is for people who like to look at vcs in ... you guessed it, a browser! :)
06:50
<alkisg>
:D
06:51
<vagrantc>
see, even in debian sometimes things make some sense
06:51
<alkisg>
vagrantc: wait, does it work if it's a debian/ dir in the master branch, as is in sch-scripts?
06:51kjackal has joined IRC (kjackal!~quassel@static062038141122.dsl.hol.gr)
06:52
<vagrantc>
alkisg: yes, it should either point to a vcs with only the debian dir, or preferrably with debian dir + upstream source
06:52
alkisg: from a quick glance at it, yours looks "correct"
06:52
<alkisg>
vagrantc: ah, I mean that sch-scripts only have a master branch that includes a debian dir with the source too
06:52
<vagrantc>
e.g. i visited the github page
06:52
<alkisg>
OK, ty
06:53
<vagrantc>
for the ltsp packaging, i specify my crazy merged upstream + debian dir in a separate branch
06:54
<alkisg>
Sure, I respect your preference there
06:54
<vagrantc>
where "crazy == recommended norms for debian"
06:55
<alkisg>
I still think that's only appropriate where that repository is NOT the upstream one, but a clone that a debian maintainer did; but I don't mind, no objections
06:56
<vagrantc>
there are definitely cases where just including in master makes sense
06:56
though if you ever start diverging upstream, then it gets ugly
06:56
diverging from the upstream debian dir, that is
06:57
<alkisg>
Ah sure, then upstream would maintain its own debian dir, and the debian maintainer would need a small script to exclude it while cloning
06:59
<vagrantc>
eesh.
06:59
<alkisg>
I'm sure that debian doesn't *enforce* upstream NOT to have a debian dir... it's their right, isn't it?
06:59
<vagrantc>
or some fancy merge exlucdes
07:00
of course
07:01
it's developer's rights to do all sorts of things; some may not be a good idea.
07:01
or some may only work in certain contexts
07:02
<alkisg>
Personally I like the idea of upstream maintaining the packaging for all distros where the maintainer is also involved upstream
07:03
But I think we've talked enough about this is the past ;)
07:03
<vagrantc>
like all things, it has it's advantages and disadvantages
07:03
and yes, we've hashed over this more than a few times already :)
07:04
too bad phantomas isn't around to back me up anymore!
07:04
<alkisg>
Hehe
07:04
<vagrantc>
well, time to test u-boot again...
07:04* vagrantc waves
07:05
<alkisg>
Bye vagrant
07:05vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
07:32statler has left IRC (statler!~Georg@p5489790B.dip0.t-ipconnect.de, Remote host closed the connection)
07:49woernie has joined IRC (woernie!~werner@pD9E8BADB.dip0.t-ipconnect.de)
08:59davschr has left IRC (davschr!~ds@p200300E22BC6C500DE85DEFFFE98CDD1.dip0.t-ipconnect.de, Quit: WeeChat 1.6)
09:29statler has joined IRC (statler!~Georg@gwrz.lohn24.de)
09:56kjackal has left IRC (kjackal!~quassel@static062038141122.dsl.hol.gr, Ping timeout: 255 seconds)
10:07kjackal has joined IRC (kjackal!~quassel@2a02:587:3119:ef00:550e:e9d8:ce19:9e42)
11:30woernie has left IRC (woernie!~werner@pD9E8BADB.dip0.t-ipconnect.de, Remote host closed the connection)
11:50Faith has joined IRC (Faith!~Paty_@unaffiliated/faith)
12:33kjackal has left IRC (kjackal!~quassel@2a02:587:3119:ef00:550e:e9d8:ce19:9e42, Remote host closed the connection)
12:43kjackal has joined IRC (kjackal!~quassel@2a02:587:3119:ef00:c1b8:3d99:9e40:4bc1)
13:59os_a has left IRC (os_a!~Thunderbi@195.112.116.22, Quit: os_a)
15:02lopta has joined IRC (lopta!~ball@74-84-114-18.client.mchsi.com)
17:04statler has left IRC (statler!~Georg@gwrz.lohn24.de, Remote host closed the connection)
17:29vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
17:49kjackal has left IRC (kjackal!~quassel@2a02:587:3119:ef00:c1b8:3d99:9e40:4bc1, Ping timeout: 252 seconds)
17:49kjackal_v2 has joined IRC (kjackal_v2!~quassel@athedsl-173858.home.otenet.gr)
18:08woernie has joined IRC (woernie!~werner@pD9E8BADB.dip0.t-ipconnect.de)
19:49lopta has left IRC (lopta!~ball@74-84-114-18.client.mchsi.com)
19:59woernie has left IRC (woernie!~werner@pD9E8BADB.dip0.t-ipconnect.de, Remote host closed the connection)
20:39kjackal_v2 has left IRC (kjackal_v2!~quassel@athedsl-173858.home.otenet.gr, Ping timeout: 246 seconds)
20:51Faith has left IRC (Faith!~Paty_@unaffiliated/faith, Quit: Leaving)
21:49ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Remote host closed the connection)
22:47map7 has left IRC (map7!~user@103.232.216.31, Killed (barjavel.freenode.net (Nickname regained by services)))
22:47Guest5179 has joined IRC (Guest5179!~user@103.232.216.31)
23:05vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Ping timeout: 252 seconds)
23:05vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)