|02:50||shored1 has left IRC (shored1!~shored@user/shored, Ping timeout: 245 seconds)|
|03:14||shored has joined IRC (shored!~shored@user/shored)|
|06:00||ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)|
hello, has anyone used double quotes in ltsp.conf defined parameter value? do you escape with backslash like normally
vsuojanen: ltsp.conf is a shell script, so yeah, you do whatever you do in shell scripts
The only thing that's different is the [section headers]
E.g. VAR="value\" with quote"
or VAR='value" with quote'
Hmm sorry the first one was cut by IRC, it was supposed to have a backslash
Let's see if I get the IRC escaping right: `VAR="value\" with quote"`
I think that should appear properly
thanks, I had some issues to figure out what you meant with the difference in [section headers] but never mind :)
It means that [section headers] aren't valid shell language, they're being automatically rewritten as shell functions
E.g. when you type [mac:address]
interesting, can you actually call for another client settings with another client [mac:address]? POST_INIT="section mac:address" ?
vsuojanen: see the last example in the man page: https://ltsp.org/man/ltsp.conf/
But of course you can also use: INCLUDE=section
I was asking as in theory is it possible if you have the [mac:address] something just specially for shell scripts
and then other clients call [section mac:address] ?
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 :)
I have used your instructions already like that local login with couple client machines but hadn't thought further the section call
Read from this line and below, i.e. the last paragraph of the man page:
> 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:52||shored1 has joined IRC (shored1!~shored@user/shored)|
|07:52||shored has left IRC (shored!~shored@user/shored, Ping timeout: 245 seconds)|
|07:59||antares2021 has joined IRC (firstname.lastname@example.org)|
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
Are you setting it inside /usr/share/raspios/etc/ltsp/ltsp.conf?
no, in the server
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...
antares2021: do it in that ^ file that I mentioned, in the chroot of the server
However, when now I try chroot /srv/ltsp/raspios/ I get a chroot: failed to run command ‘/bin/bash’: Exec format error
ADMINISTRATIVE client goes there, not in /etc/ltsp/ltsp.conf
antares2021: yes, that's handled by qemu, the emulator; you can't chroot into a different architecture without emulation
So you'd need to install qemu-static-arm32 or something like that first
OK I'll take it into account because it is more complicated than trying the administrative client thing
by the way, the proper line for the ltsp.conf is [MAC-OF-RASPI] followed by ADMINISTRATIVE_CLIENT=1 or just ADMINISTRATIVE_CLIENT=[MAC]
OK, I'll give feedback in a while
well, inside the chroot the file is at /srv/ltsp/raspios/usr/share/ltsp/common/ltsp/ltsp.conf
antares2021: please use the path that I said
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?
*without the ?
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?
Oh my sorry
I wrote it wrong
I mean this path in the server itself: /srv/ltsp/raspios/etc/ltsp/ltsp.conf
This is the correct path; anything different that I wrote was mis-typing, sorry . ^
ok, in that folder I don't have any ltsp.conf, so I guess I should copy the ltsp.conf from the server?
(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)
Create a new one, with just these 3 lines
So that you know it's for a completely different goal than your main one
I guess I'll have to log in with the user pi (which was the one I installed raspios?)
|08:52||antares2021 has left IRC (email@example.com, Ping timeout: 256 seconds)|
|09:17||antares2021 has joined IRC (firstname.lastname@example.org)|
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?
should I log out pi user, shutdown, etc?
It should also be possible to do it while the administrative client is running, but don't install any programs etc while doing it
Or just power it off to be 100% safe
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!!
mmm the last!!! Guess now should be nice to set ADMINISTRATIVE_USER to 0!!
antares2021: ADMINISTRATIVE_CLIENT? (not user)
Yes, to be able to reuse that client
sorry, yes, ADMINISTRATIVE _CLIENT, Sorry
|10:23||antares2021 has left IRC (email@example.com, Quit: Client closed)|
|12:09||shored1 has left IRC (shored1!~shored@user/shored, Ping timeout: 264 seconds)|
|15:00||shored has joined IRC (shored!~shored@user/shored)|
|17:11||vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100b)|
|17:16||vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100b, Ping timeout: 265 seconds)|
|17:17||vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100b)|
|19:16||vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100b, Ping timeout: 268 seconds)|
|19:22||vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100d)|
|20:34||ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)|
|23:01||vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100d, Quit: leaving)|