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


Channel log from 8 February 2023   (all times are UTC)

02:17wyre is now away: Auto away at Wed Feb 8 02:15:53 2023 UTC
06:32wyre is back
06:58wyre is now away: Auto away at Wed Feb 8 06:56:14 2023 UTC
07:26ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
08:18wyre is back
08:25book` has left IRC (book`!~book`@static.38.6.217.95.clients.your-server.de, Quit: Leaving)
08:27wyre has left IRC (wyre!~wyre@user/wyre, Quit: ZNC 1.8.2 - https://znc.in)
08:28wyre has joined IRC (wyre!~wyre@user/wyre)
08:28wyre is now away: Auto away at Wed Feb 8 08:27:57 2023 UTC
08:28wyre is back
08:44book` has joined IRC (book`!~book`@static.38.6.217.95.clients.your-server.de)
08:53ogra is back
09:52
<err404[m]>
hello, did you have somewhere a WORKING EXAMPLE documentation for a chrooted config? (https://github.com/ltsp/ltsp/wiki/chroots is not working in may case)
09:52
s/may/my/
09:53
<alkisg>
err404: well, it's working for me, so you'd need to mention what's not working for you
10:02
<err404[m]>
thanks,... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/f2bb68185c4e3ecfd74b2219443c47cf6f54b009>)
10:04
so, the isssue is not really from the ltsp itself in my case (vmlinuz is missing),
10:06
<alkisg>
err404: do you have any special reason not to use the proper directories?
10:06
The /srv/tftp directory is described in the filesystem hierarchy standard, and it's what ltsp uses
10:06
There's no tutorial for "non-standard directories" if you're looking for that
10:06
<err404[m]>
I have also another issue, but seem working:
10:06
```
10:06
ltsp initrd
10:06
Could not parse output of: ip -o route get 192.168.67.1
10:06
Generated ltsp.img:
10:06
-rw-r--r-- 1 root root 158208 Feb 8 10:46 /srv/tftp/ltsp/ltsp.img
10:06
```
10:06
<alkisg>
Yes that means that your routing is problematic, but it's not a fatal error
10:09
<err404[m]>
I made a symlink from /srv to /data/srv
10:09
but I remmember that nfs doesnot support symlink or something like this,
10:09
at the beginning, I was affraid about space disk, but it seem unnecessary to move /srv to another partition
10:09
I will retry all the config with /srv on /, not on /data/srv
10:09
<alkisg>
You can mount /data/srv as /srv directly if it helps
10:10
You can also bind-mount a directory if you prefer
10:11
<err404[m]>
my /data is an encrypted lvm partition, but for the moment I will try to have a working config on /srv
11:24woernie has left IRC (woernie!~werner@p5dded9bd.dip0.t-ipconnect.de, Ping timeout: 260 seconds)
11:24woernie_ has joined IRC (woernie_!~werner@p5dded046.dip0.t-ipconnect.de)
11:30ogra is now away: currently disconnected
12:01ogra is back
12:06woernie_ has left IRC (woernie_!~werner@p5dded046.dip0.t-ipconnect.de, Ping timeout: 248 seconds)
12:07woernie has joined IRC (woernie!~werner@p5dded046.dip0.t-ipconnect.de)
13:36ogra is now away: currently disconnected
13:36ogra is back
14:02wyre is now away: Auto away at Wed Feb 8 14:01:59 2023 UTC
14:04wyre is back
14:11woernie has left IRC (woernie!~werner@p5dded046.dip0.t-ipconnect.de, Ping timeout: 268 seconds)
14:11woernie_ has joined IRC (woernie_!~werner@93.222.206.210)
14:45
<err404[m]>
ok, it is working on my side now 😄
14:45
- kernel linux image was not installed on chroot, (probably because debootstrap assume is for chroot, so using the original kernel is ok?)
14:45
- after adding the kernel on the chrooted, (and executing `ltsp image ltspdeb` followed by `ltsp ipxe) ltsp was abble to load it.
14:45
- but the system was mounted readonly (it is normal, ok) so the ligthdm was not abble to start (same issue if your disk is full).
14:45
I edited the file /etc/exports.d/ltsp-nfs.exports to make the exported folder writable, and update nfs with `exportfs -ra`
14:45
I executed in root (in the ltsp client): `mount -n -o remount,rw /` to make the `/` writable
14:45
fews second later the graphical env was launched and I was abble to login
14:46
so, may be on ubuntu the kernel is installed with debootstrap?
14:47
I know that it is actualy not secure to have nfs export in rw mode
14:49
* ok, it is working on my side now 😄
14:49
- kernel linux image was not installed on chroot, (probably because debootstrap assume is for chroot, so using the original kernel is ok?)
14:49
- after adding the kernel on the chrooted, (and executing `ltsp image ltspdeb` followed by `ltsp ipxe`) ltsp was abble to load it.
14:49
- but the system was mounted readonly (it is normal, ok) so the ligthdm was not abble to start (same issue if your disk is full).
14:49
I edited the file /etc/exports.d/ltsp-nfs.exports to make the exported folder writable, and update nfs with `exportfs -ra`
14:49
I executed in root (in the ltsp client): `mount -n -o remount,rw /` to make the `/` writable
14:49
fews second later the graphical env was launched and I was abble to login
14:49
* ok, it is working on my side now 😄
14:49
- kernel linux image was not installed on chroot, (probably because debootstrap assume is for chroot, so using the original kernel is ok?)
14:49
- after adding the kernel on the chrooted, (and executing `ltsp image ltspdeb` followed by `ltsp ipxe`) ltsp was abble to load it.
14:49
- but the system was mounted readonly (it is normal, ok) so the ligthdm was not abble to start (same issue if your disk is full).
14:49
I edited the file `/etc/exports.d/ltsp-nfs.exports` to make the exported folder writable, and update nfs with `exportfs -ra`
14:49
I executed in root (in the ltsp client): `mount -n -o remount,rw /` to make the `/` writable
14:49
fews second later the graphical env was launched and I was abble to login
14:51
I read that sshfs can be used intead of nfs, but I dont know how to configure it on ltsp (I use ssh and sshfs is working on my side)
14:56woernie_ has left IRC (woernie_!~werner@93.222.206.210, Ping timeout: 252 seconds)
14:57woernie has joined IRC (woernie!~werner@p5ddecd73.dip0.t-ipconnect.de)
14:57
<err404[m]>
`ltsp initrd `<-- was also used
14:57
<vsuojanen[m]>
did you check in the chroot that you have the /boot in The root hierarchy? Did you install there on chroot at any point linux-generic initramfs-tools?
14:59
<err404[m]>
may be, I am not sure, anyway I need to make another try, on a cleaner environement, because I tried many thinngs and it is remain confused to me for the moment
15:01
but the loading kernel, initrd and the environement through GBits ethernet is fast as expected (the ltsp server is on a disk drive, not a SSD, I not demand instant loading :p)
15:02
<vsuojanen[m]>
before you do another try read again the top of the wiki page you linked.
15:02
> before you do another try read again the top of the wiki page you linked.... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/1472804b8976d0c378908a2710f8eb23086db0a5>)
15:02
<err404[m]>
and yes, my /boot was empty, so I installed kernel in the chroot
15:03
yes, I need to re-read again the docs
15:04
<vsuojanen[m]>
sorry i meant reality the top to be precise. My wast was not related to that, sorry
15:05
cd /srv/ltsp
15:05
debootstrap focal focal
15:05
chroot focal
15:05
apt install --no-install-recommends linux-generic initramfs-tools
15:05
echo focal > /etc/hostname
15:05
passwd
15:05
exit
15:07
<err404[m]>
debootstrap focal focal <-- is for ubuntu, but I use Debian, so I tried bullseye, and I remmember seen an error, but I let it continue
15:08
apt install --no-install-recommends linux-generic initramfs-tools <-- I dont know why the kernel was not installed at this step, next time I will be more attentive
15:18
<vsuojanen[m]>
that /boot in root hierarchy is needed before you can configure the ipxe and tftp (and that's a separate task)
15:20woernie has left IRC (woernie!~werner@p5ddecd73.dip0.t-ipconnect.de, Ping timeout: 260 seconds)
15:37
<err404[m]>
about sshfs, I found an answer: https://github.com/ltsp/ltsp/discussions/789
16:06
<vsuojanen[m]>
About the nfs vs. sshfs issue are you already netbooting the clients? yes i think the wiki instruction should link to ltps.org main Installation page
16:21wyre is now away: Auto away at Wed Feb 8 16:21:03 2023 UTC
17:11
<alkisg>
err404: the main things to consider are:
17:11
1) Why are you using a chroot instead of chrootless or VM? The chroot method is the hardest one.
17:11
2) Remember to run `ltsp image chroot-name`, before booting the client. This makes a squashfs file out of the image. Serving this over NFS works fine. While serving a chroot over NFS has issues with recent kernels (as it was reported, I haven't tested myself)
17:23vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:40)
17:35lcurl_ has joined IRC (lcurl_!~UserNick@115.79.27.26)
17:39lcurl has left IRC (lcurl!~UserNick@115.79.27.26, Ping timeout: 268 seconds)
17:40lcurl_ has left IRC (lcurl_!~UserNick@115.79.27.26, Ping timeout: 268 seconds)
18:07
<err404[m]>
> The chroot method is the hardest one.
18:07
this is not documented as hardest one 😛
18:07
I can try to build a VM and use it (with image linked to the vmdk as documented in ltsp)
18:07
* > The chroot method is the hardest one.
18:07
this is not documented as hardest one 😛
18:07
I can try to build a VM and use it (with image linked to the vmdk as documented in ltsp)
18:09
actualy, the diskless client is booting fine with a chrooted env for ltsp, but the / is readonly (as configured by ltsp nfs)
18:09
s///`/`/
18:10
running ltsp image chroot-name took long time to finish, but it will not really an issue
18:11
<alkisg>
It's supposed to be read only, yeah
18:11
<err404[m]>
I will try by VM
18:37
<vsuojanen[m]>
I have seen that chroot wiki document purpose has been to be one advanced use case and not so much guiding about the ltsp server Installation.
18:38
<alkisg>
https://ltsp.org/docs/installation/#maintaining-a-client-image ==> it is the easiest method ==> it's talking about chrootless there :D
20:08
<err404[m]>
ah yes, it was not working in my case, but may be I had already fogoten some step 😛
20:09
s/fogoten/forgoten/
20:16wyre is back
20:30ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
22:19vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:40, Quit: leaving)