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


Channel log from 28 September 2021   (all times are UTC)

00:01Jonny[m] has joined IRC (Jonny[m]!~jonnymatr@2001:470:69fc:105::b958)
00:04alkisg has joined IRC (alkisg!~alkisg@2001:470:69fc:105::2d3)
01:01eu^273447147 has joined IRC (eu^273447147!~eu^273447@27.34.47.147)
01:01
<eu^273447147>
Hello there
01:02
I was wondering about /etc/ltsp/ltsp.conf. Do I have to run some commands after changing the file? For some reason, the changes I make in the file don't seem to take effect. And when it does, I can't figure out which phase of the moon it is dependent on.
01:03
<vagrantc>
ltsp initrd
01:03
<eu^273447147>
Hey, Mr. vagrantc, the one who works for debian and also guix, good to see you here!
01:03
I see. Thank you.
01:04
But I don't think the clients are respecting the conf file.... strange. Any ideas?
01:04
<vagrantc>
https://ltsp.org/docs/installation/
01:04
eu^273447147: ltsp initrd
01:04
<eu^273447147>
I see. Thank you.
01:05
<vagrantc>
https://ltsp.org/man/ltsp-initrd/
01:05* vagrantc is happy to be able to answer ltsp questions :)
01:06
<eu^273447147>
The man page doesn't explicitly state ltsp initrd. Perhas that ought to be added (?)
01:06
<vagrantc>
kind of felt a little rusty, but have more experience again recently
01:06
<eu^273447147>
It's so good to meet a celebrity here. (:
01:06
<vagrantc>
not sure what you mean
01:06
"ltsp initrd" is mentioned in both the links i gave you, and mentions when you should run it
01:06
<eu^273447147>
You are vagrantc of debian fame
01:07
<vagrantc>
yes, i'm aware of that part :)
01:07
<eu^273447147>
Ah! I read it wrong
01:07
Thanks
01:07
I thought it was ltsp conf
01:07
Ah, yeah I read even that wrong
01:07
<vagrantc>
might be leftovers from ltsp5 era commands in your m ind :)
01:08
<eu^273447147>
I see. 1 more question. I have a nfs share running on my server that I want to mount to /usr/share/tuxtype/words for ALL clients
01:09
I tried adding FSTAB_TUX="/nfs/dir/here /usr/share/tuxtype/words..." under [*:*:*:*] (for [clients]) in the conf file.
01:10
I suppose that looks okay to you? I realize that it must be me not running `ltsp initrd` that was causing that to be not respected?
01:10
<vagrantc>
you might need to create the directory first
01:10
<eu^273447147>
It is there already
01:10
Must be the initrd part I suppose
01:10
<vagrantc>
but yeah, you'll need to run "ltsp initrd" for changes to ltsp.conf to take effect
01:11
rather than downloading it separately, all the stuff ltsp uses is included in the ltsp initrd ...
01:11
<eu^273447147>
Ah.... I see.
01:12
Also, I wanted to know, what should I read up to know what things LTSP is using under the hood? Is there any documentation regarding that? Or should I just start reading the source?
01:12
I mean rather....
01:12
this kind of compartmentalization.....
01:12
"ltsp initrd does so and so and handles this part"
01:13
Or maybe I just don't understand the man page enough
01:13
idk
01:13
<vagrantc>
i think https://ltsp.org/docs covers that
01:13
<eu^273447147>
I did read through it once. I suppose I'll just have to read through it over and over again.
01:14
Thank you very much for your help. I'll try to fix up my installation today. Hope you have a good time!
01:14eu^273447147 has left IRC (eu^273447147!~eu^273447@27.34.47.147, Quit: Client closed)
01:55vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100e, Quit: leaving)
03:40Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection)
03:40Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas)
04:16quinox has left IRC (quinox!~quinox@ghost.qtea.nl, Quit: WeeChat 3.0.1)
04:19quinox has joined IRC (quinox!~quinox@ghost.qtea.nl)
05:22alkisg_web has joined IRC (alkisg_web!~alkisg_we@srv1-dide.ioa.sch.gr)
05:24* alkisg is glad to see vagrantc giving ltsp advice once more!
05:24
<alkisg>
vagrantc: `ssvnc` is a much better default viewer than xtightvncviewer; we avoided it due to it recommending default-jre,
05:24
...which it uses to implement ultravnc-like ftp transfers (so it's a bit of a rarely used functionality),
05:25
do you think we'd have any chances of convincing its debian maintainers to suggest it instead of recommending it?
05:25
So that we avoid installing default-jre when once `apt installs epoptes`...
05:37eu^273447240 has joined IRC (eu^273447240!~eu^273447@2400:1a00:b1c0:ebc4:443b:3be6:56e1:f09d)
05:38
<eu^273447240>
Hello there, it seems that ltsp is not respecting my `ltsp.conf` file (despite running `ltsp initrd`)
05:38
My suspicion - is it because I'm keeping the file in a separate place (`/home/etc/ltsp.conf`) and symlinking to it?
05:39
Here's my ltsp.conf file: https://termbin.com/6xa6
05:39
The clients don't boot quietly. The nfs folder isn't mounted. And the hostname isn't set. Is there something I'm missing?
05:40
<alkisg>
eu^273447240: hello
05:40
<eu^273447240>
Hey there! So good to see you again!
05:40
<alkisg>
KERNEL_PARAMETERS go to [common] or [server] or [MAC_ADDRESS]
05:40
They can't be under [clients], as they actually run on the server
05:41
After you boot a client, if you `cat /etc/fstab`, do you see your line inside it?
05:41
> Hey there! So good to see you again! ==> it helps if you use any static username, e.g. "johnsmith1234", as it's impossible to remember "eu^273447240" :)
05:42
You may type `/nick username` to change it
05:42
Regarding the symlink, yeah it's most probably the fault. You may uncompress your ltsp.img to see if it went inside it or not; I would imagine "not"
05:44woernie has joined IRC (woernie!~werner@p5b296ebb.dip0.t-ipconnect.de)
05:45eu^273447240 has left IRC (eu^273447240!~eu^273447@2400:1a00:b1c0:ebc4:443b:3be6:56e1:f09d, Ping timeout: 256 seconds)
05:57eu^273447240 has joined IRC (eu^273447240!~eu^273447@2400:1a00:b1c0:ebc4:a920:63e4:a2a0:768b)
05:57
<eu^273447240>
alkisg I am sorry (power outage) Thanks, retrying now (looked at the irc logs)
05:58
<alkisg>
👍️
06:00
<eu^273447240>
So it's a real file (no symlink now) and here's the conf file https://termbin.com/h06u and 1. it still is not booting quietly
06:01
2. the hostname is now being respected. So that is good
06:02
<alkisg>
> After you boot a client, if you cat /etc/fstab, do you see your line inside it?
06:02
<eu^273447240>
Yes, sir. The line is inside it. But it isn't mounting
06:04
Ah! I tried `mount -a` in the client and it seems that I lack `nfs-common` in the clients
06:04
let me check with another image
06:05
wait that's not right... I can mount.nfs that... let me check some more
06:09ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
06:10
<alkisg>
mount.nfs is a symlink to a small klibc program that ltsp puts
06:10
It can only do "nolock" nfs3 mounts
06:10
Do install nfs-common, run ltsp image, then reboot the clients
06:10
<eu^273447240>
what is nolock? Should I add that option?
06:11woernie has left IRC (woernie!~werner@p5b296ebb.dip0.t-ipconnect.de, Ping timeout: 252 seconds)
06:12
<alkisg>
No, do what I wrote above
06:18eu^273447240 has left IRC (eu^273447240!~eu^273447@2400:1a00:b1c0:ebc4:a920:63e4:a2a0:768b, Ping timeout: 256 seconds)
06:32woernie has joined IRC (woernie!~werner@p5b296ebb.dip0.t-ipconnect.de)
06:42woernie has left IRC (woernie!~werner@p5b296ebb.dip0.t-ipconnect.de, Ping timeout: 252 seconds)
09:00fottsia[m] has left IRC (fottsia[m]!~fottsiama@2001:470:69fc:105::48bb, Quit: You have been kicked for being idle)
09:37Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Quit: Ping timeout (120 seconds))
09:37Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas)
09:45woernie has joined IRC (woernie!~werner@p5b296ebb.dip0.t-ipconnect.de)
12:18aluno26^semed-la has joined IRC (aluno26^semed-la!~aluno26^s@2804:fc:8db2:9300::f)
12:18aluno26^semed-la has left IRC (aluno26^semed-la!~aluno26^s@2804:fc:8db2:9300::f, Client Quit)
12:41eu^273447240 has joined IRC (eu^273447240!~eu^273447@2400:1a00:b1c0:ebc4:e881:b60:a54b:5b40)
12:41
<eu^273447240>
Hey there,
12:41fottsia[m] has joined IRC (fottsia[m]!~fottsiama@2001:470:69fc:105::48bb)
12:42
<eu^273447240>
so installing `nfs-common` on the client image does fix the nfs mount issue. Thank you
12:42
Now, I have this issue where netbooting the clients with the ltsp server times out at tftp
12:42
unless I manually restart dnsmasq
12:42
any ideas what might be causing that?
12:51eu^273447240 has left IRC (eu^273447240!~eu^273447@2400:1a00:b1c0:ebc4:e881:b60:a54b:5b40, Quit: Client closed)
12:59eu^273447240 has joined IRC (eu^273447240!~eu^273447@2400:1a00:b1c0:ebc4:956f:dc93:9e54:f137)
13:00eu^273447240 has left IRC (eu^273447240!~eu^273447@2400:1a00:b1c0:ebc4:956f:dc93:9e54:f137, Client Quit)
13:34
<alkisg>
Yes, bind-interfaces in /etc/dnsmasq.d/something-with-lxc-or-qemu
13:58vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100e)
15:18shored has joined IRC (shored!~shored@user/shored)
15:37lucascastro has joined IRC (lucascastro!~lucascast@177-185-130-35.dynamic.isotelco.net.br)
15:45alkisg_web has left IRC (alkisg_web!~alkisg_we@srv1-dide.ioa.sch.gr, Quit: Client closed)
16:00fottsia[m] has left IRC (fottsia[m]!~fottsiama@2001:470:69fc:105::48bb, Quit: You have been kicked for being idle)
16:17vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100e, Quit: leaving)
16:20vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100b)
17:57vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100b, Quit: leaving)
18:32lucascastro has left IRC (lucascastro!~lucascast@177-185-130-35.dynamic.isotelco.net.br, Quit: Leaving)
18:39vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100b)
21:19superdad has joined IRC (superdad!~wrender@cpe7824af7d7910-cmf0f249403bc0.cpe.net.cable.rogers.com)
21:38
<superdad>
I've got a debootstrap chroot working great for booting Ubuntu 20.04. Does this method work well for versions 16.04, and 18.04 of Ubuntu as well? https://github.com/ltsp/ltsp/wiki/chroots
21:39fottsia[m] has joined IRC (fottsia[m]!~fottsiama@2001:470:69fc:105::48bb)
22:47ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
23:51vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100b, Quit: leaving)