|04:50||vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20, Quit: leaving)|
|05:04||quinox has left IRC (email@example.com, Quit: WeeChat 3.5)|
|05:07||quinox has joined IRC (firstname.lastname@example.org)|
|05:28||ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)|
Hi I got one question. When I use an iso as an image, the client can see the option and boot from there but it doesn't appears the file system. Is because it's not possible or am I doing something wrong? Thanks for the help
daniel891: not sure what you mean "it doesn't appear the file system"
Do you want to run `ls` on a client and see the iso itself?
ltsp-bottom mounts the iso, then gets the filesystem.squashfs inside it and mounts it, then does an overlayfs with tmpfs over it, and THAT'S the live file system
Good day , how can i make sure that my ltsp client can change password at their own. when they try passwd ,its give passwd: Authentication token manipulation error
jannyboy: you need to use ldap for that
* manipulation error. I triedchmod 640 /etc/shadow , then ltsp initrd
E.g. if you run `ltsp remoteapps gnome-about-me`, then that runs on the server even if it's displayed on the client, so the password change happens on the server where it hsould
(or mate-about-me if you're using mate)
this command refuse , command not found
or i have to install remoteapps first ?
jannyboy: ltsp remoteapps is available in the latest ltsp version from the ppa
Which ltsp version are you using? dpkg -l ltsp
<alkisg> "ltsp-bottom mounts the iso, then..." <- I mean that the filesystem.squashfs doesn't get mounted and I don't know why
<alkisg> "Which ltsp version are you using..." <- 22.01-1 ubuntu20.04.1
|12:25||Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Ping timeout: 240 seconds)|
|12:32||Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas)|
daniel891: paste a screenshot of the boot process
jannyboy: I guess you're running `ltsp-remoteapps` instead of `ltsp remoteapps`. Read https://ltsp.org/man/ltsp-remoteapps/
Don't use a dash, try e.g.: ltsp remoteapps xterm
|13:49||Cueball has left IRC (Cueballemail@example.com, Ping timeout: 252 seconds)|
|14:35||oh207 has joined IRC (firstname.lastname@example.org)|
|14:36||oh207 has left IRC (email@example.com, Client Quit)|
|14:37||oh207 has joined IRC (firstname.lastname@example.org)|
<alkisg> "daniel891: paste a screenshot of..." <- Mmm which part? I'm following the instructions from here: https://ltsp.org/man/ltsp-kernel/
daniel891: I thought you said that the client fails to boot. Show us a screenshot of that failure message.
No no, the client can boot fine. I think I misunderstood. Should I see the same file system when I boot from an iso than when I boot from a vm image? (Because I don't)
When you boot from a live CD you see a normal file system that is similar but not identical to the file system that you see when you boot from a VM
I'm not sure what you expect to see but you may mention specific files if you want to do a comparison
Okey I'm explaining terribly. My doubt is that if you should see your saved work when boot from an iso.
Isos do not have sshfs installed. You either need to use NFS home, or provide the sshfs binary at /etc/ltsp
Back later with more details 🐱
This section describes how to serve home over nfs
And the section describes how to include sshfs in the initrd because it is not included in live CDs
|17:55||oh207 has left IRC (email@example.com, Ping timeout: 246 seconds)|
You can use either one of them to provide /home to clients that boot from the iso
|19:00||woernie has joined IRC (woernie!~werner@2001:9e8:e27b:3c00:28e4:9960:ba19:6f06)|
|20:08||ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)|
Thank you very much!!
|21:34||woernie has left IRC (woernie!~werner@2001:9e8:e27b:3c00:28e4:9960:ba19:6f06, Ping timeout: 248 seconds)|