|04:00||vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20, Quit: leaving)|
|06:52||ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)|
|14:53||vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20)|
|16:00||lucascastro has left IRC (firstname.lastname@example.org, Quit: Leaving)|
|18:00||lucascastro has joined IRC (email@example.com)|
|19:09||lucascastro has left IRC (firstname.lastname@example.org, Ping timeout: 240 seconds)|
When I make changes in /etc/lightdm/lightdm-gtk-greeter.conf or /etc/lightdm/lightdm.conf how to I get those changes into the image I'm booting. I'm doing an ltsp image / to create the image.
i would think they would just be pulled in ... but there may be some code that touches those files ...
other option would be to add POST_INIT_SOMETHING rules to ltsp.conf that modifies the files during boot
|19:16||* vagrantc hopes to be remembering correctly...|
yeah, POST_APPLET_x in lts.conf: https://ltsp.org/man/ltsp.conf/
not sure off the top of my head what all the variaous "APPLET" parts are
applets mentioned in https://ltsp.org/man/ltsp/
but confusingly ... says "LTSP clients also have some additional applets, like initrd-bottom, init and login, but they're not runnable by the user." ... though i suspect that's because those applets are used at boot, not when running the "ltsp" command
Biglouadamich[m]: hope that helps
vagrantc: you got everything correctly :) Indeed, `ltsp initrd-bottom`, `ltsp init` and `ltsp login` are called by "the system" (=hooks), not the user
Biglouadamich: if you're using chrootless, anything you change in /etc goes to the image, yeah
If it doesn't, then you're doing something wrong
|19:35||* vagrantc beams :)|
alkisg: calling them both applets is a little confusing, although the most common one, POST_INIT_x is documented in the POST_APPLET_x section in the ltsp.conf
vagrantc: applets are subdirs under ltsp/, there's no reason to separate them based on how they're called
People can still use POST_INITRD_BOTTOM_X, it doesn't matter that they won't invoke it themselves
alkisg: fair, though it was a bit confusing to have the documentation say "go look here" and then
alkisg: the ltsp man page sort of implies they can't be used
I wanted it to mean "and that's why I didn't bother writing man pages about them" :D
I.e. there's `man ltsp image`, but not `man ltsp init`, because you're not supposed to call it
i guess maybe, since you've already split those variables out separately in the above quoted paragraph, maybe it's worth spelling out when they would be used?
not exactly sure what to recommend, as i'm a little fuzzy on how it's all put together :)
Sure a few more details there could help. I sometimes wonder if it would be better to document all the ltsp.conf options under their "applet man pages" instead of "all of them under ltsp.conf"
Anyways the next release will be for bullseye+1, so no hurry :)
I'm rebuilding the image now. I think it may have been a type on my part.
|19:58||lucascastro has joined IRC (email@example.com)|
Working for me now.
|22:29||ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)|