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


Channel log from 29 October 2021   (all times are UTC)

02:50shored1 has left IRC (shored1!~shored@user/shored, Ping timeout: 245 seconds)
03:14shored has joined IRC (shored!~shored@user/shored)
06:00ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
06:04
<vsuojanen>
hello, has anyone used double quotes in ltsp.conf defined parameter value? do you escape with backslash like normally
06:04
<alkisg>
vsuojanen: ltsp.conf is a shell script, so yeah, you do whatever you do in shell scripts
06:04
The only thing that's different is the [section headers]
06:05
E.g. VAR="value\" with quote"
06:05
or VAR='value" with quote'
06:05
Hmm sorry the first one was cut by IRC, it was supposed to have a backslash
06:06
Let's see if I get the IRC escaping right: `VAR="value\" with quote"`
06:06
I think that should appear properly
06:13
<vsuojanen>
thanks, I had some issues to figure out what you meant with the difference in [section headers] but never mind :)
06:16
<alkisg>
It means that [section headers] aren't valid shell language, they're being automatically rewritten as shell functions
06:16
E.g. when you type [mac:address]
06:19
<vsuojanen>
interesting, can you actually call for another client settings with another client [mac:address]? POST_INIT="section mac:address" ?
06:21
<alkisg>
vsuojanen: see the last example in the man page: https://ltsp.org/man/ltsp.conf/
06:21
But of course you can also use: INCLUDE=section
06:22
<vsuojanen>
I was asking as in theory is it possible if you have the [mac:address] something just specially for shell scripts
06:23
and then other clients call [section mac:address] ?
06:23
<alkisg>
vsuojanen: yes, I have already written an example in the man page exactly for that, please read it so that I don't have to type it again here :)
06:24
<vsuojanen>
sorry :)
06:25
I have used your instructions already like that local login with couple client machines but hadn't thought further the section call
06:26
<alkisg>
Read from this line and below, i.e. the last paragraph of the man page:
06:26
> Since ltsp.conf is transformed into a shell script and sections into functions, it's possible to directly include code or to call sections at POST_APPLET_x hooks....
07:52shored1 has joined IRC (shored1!~shored@user/shored)
07:52shored has left IRC (shored!~shored@user/shored, Ping timeout: 245 seconds)
07:59antares2021 has joined IRC (antares2021!~antares20@84.78.244.18)
08:00
<antares2021>
Good morning. I have a ltsp setup with up to 6 raspberry pi clients. Trying to install new software I am having trouble sedtting ADMINISTRATIVE CLIENT ltsp.conf parameter (seems no to work). hnowever, I'm trying to chroot into the raspios
08:01
<alkisg>
Are you setting it inside /usr/share/raspios/etc/ltsp/ltsp.conf?
08:01
<antares2021>
no, in the server
08:02
I couldnt' get simple instruction (miss ltsp-chroot sooooo much) so I've tried to emulate what ltsp-chroot did. I've mounted /dev, devpts, proc (imitating what the ltsp-chroot made) and copied /etc/resolvconf, etc...
08:03
<alkisg>
antares2021: do it in that ^ file that I mentioned, in the chroot of the server
08:03
<antares2021>
However, when now I try chroot /srv/ltsp/raspios/ I get a chroot: failed to run command ‘/bin/bash’: Exec format error
08:03
<alkisg>
ADMINISTRATIVE client goes there, not in /etc/ltsp/ltsp.conf
08:03
antares2021: yes, that's handled by qemu, the emulator; you can't chroot into a different architecture without emulation
08:03
So you'd need to install qemu-static-arm32 or something like that first
08:04
<antares2021>
OK I'll take it into account because it is more complicated than trying the administrative client thing
08:05
by the way, the proper line for the ltsp.conf is [MAC-OF-RASPI] followed by ADMINISTRATIVE_CLIENT=1 or just ADMINISTRATIVE_CLIENT=[MAC]
08:06
<alkisg>
[b8:27:eb:c4:a5:4a]
08:06
HOSTNAME=rpi2
08:06
ADMINISTRATIVE_CLIENT=1
08:07
<antares2021>
OK, I'll give feedback in a while
08:11
well, inside the chroot the file is at /srv/ltsp/raspios/usr/share/ltsp/common/ltsp/ltsp.conf
08:15
<alkisg>
antares2021: please use the path that I said
08:16
antares2021: you don't need to run `ltsp initrd` or anything, just put these 3 lines in that file: /usr/share/raspios/etc/ltsp/ltsp.conf?
08:16
*without the ?
08:17
<antares2021>
ok you mean that path IN THE SERVER ITSELF? or inside the chroot dirs, so the absolute path would be, in my case /srv/ltsp/raspios/usr/share/raspios/etc/ltsp.conf?
08:18
<alkisg>
Oh my sorry
08:18
I wrote it wrong
08:18
I mean this path in the server itself: /srv/ltsp/raspios/etc/ltsp/ltsp.conf
08:18
This is the correct path; anything different that I wrote was mis-typing, sorry . ^
08:20
<antares2021>
ok, in that folder I don't have any ltsp.conf, so I guess I should copy the ltsp.conf from the server?
08:20
(I do have a ltsp.conf inside the chroot but at /srv/ltsp/raspios/usr/share/ltsp/common/ltsp/ltsp.conf, and it is different from the server's)
08:22
<alkisg>
Create a new one, with just these 3 lines
08:22
<antares2021>
OK
08:22
<alkisg>
So that you know it's for a completely different goal than your main one
08:23
<antares2021>
I guess I'll have to log in with the user pi (which was the one I installed raspios?)
08:28
<alkisg>
antares2021: yes
08:52antares2021 has left IRC (antares2021!~antares20@84.78.244.18, Ping timeout: 256 seconds)
09:17antares2021 has joined IRC (antares2021!~antares20@84.78.244.18)
09:21
<antares2021>
hi agasin, sorry for the disconnection - difficult to work onboard a ship - I managed to login as the pi user and install things. Now I guess I should log out and then compress the image, etc as usual, isn't it?
09:23
<alkisg>
antares2021: right
09:24
<antares2021>
should I log out pi user, shutdown, etc?
09:24
<alkisg>
Yes
09:24
It should also be possible to do it while the administrative client is running, but don't install any programs etc while doing it
09:25
Or just power it off to be 100% safe
09:25
<antares2021>
alksig: OK, Thank yo VERY VERY VERY MUCH for your help. I'll try to update the wiki page I created with today's lesson. Have a nice day!!
09:28
<alkisg>
Great!
09:30
<antares2021>
mmm the last!!! Guess now should be nice to set ADMINISTRATIVE_USER to 0!!
09:37
<alkisg>
antares2021: ADMINISTRATIVE_CLIENT? (not user)
09:37
Yes, to be able to reuse that client
09:38
<antares2021>
sorry, yes, ADMINISTRATIVE _CLIENT, Sorry
10:23antares2021 has left IRC (antares2021!~antares20@84.78.244.18, Quit: Client closed)
12:09shored1 has left IRC (shored1!~shored@user/shored, Ping timeout: 264 seconds)
15:00shored has joined IRC (shored!~shored@user/shored)
17:11vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100b)
17:16vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100b, Ping timeout: 265 seconds)
17:17vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100b)
19:16vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100b, Ping timeout: 268 seconds)
19:22vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100d)
20:34ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
23:01vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100d, Quit: leaving)