|00:00||vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100e, *.net *.split)|
|00:00||quinox has left IRC (firstname.lastname@example.org, *.net *.split)|
|00:01||quinox has joined IRC (email@example.com)|
|00:05||vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100e)|
|03:20||vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100e, Quit: leaving)|
|06:04||adrianorg has left IRC (adrianorg!~adrianorg@debian/adrianorg, Ping timeout: 256 seconds)|
|06:36||adrianorg has joined IRC (adrianorg!~adrianorg@debian/adrianorg)|
|06:49||ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)|
|06:53||adrianorg has left IRC (adrianorg!~adrianorg@debian/adrianorg, Ping timeout: 256 seconds)|
|07:06||adrianorg has joined IRC (adrianorg!~adrianorg@debian/adrianorg)|
Good morning alkisg :-)
Good morning Jan
How's it going?
|09:54||NecTal has joined IRC (NecTal!~NecTal@126.96.36.199)|
|11:47||Faith has joined IRC (Faith!~Paty_@user/faith)|
|13:26||NecTal has left IRC (NecTal!~NecTal@188.8.131.52, Quit: Client closed)|
|16:01||yopla has joined IRC (firstname.lastname@example.org)|
|19:03||woernie has left IRC (email@example.com, Remote host closed the connection)|
|19:41||yopla has left IRC (firstname.lastname@example.org, Quit: Client closed)|
|20:51||Faith has left IRC (Faith!~Paty_@user/faith, Quit: Leaving)|
|21:04||raspberrypipe[m] has joined IRC (raspberrypipe[m]!~raspberry@2001:470:69fc:105::1:4377)|
need some help with LTSP + Pi
raspberrypipe: sure, just ask
Did you see the https://ltsp.org/docs/installation/raspios/ page?
Yes i did
i have several 4GB RPI4s
I've got to the last step "LTSP mode netbooting" but it seems that when im creating the image, it takes the env of the server instead of PIs
Are you running `ltsp image raspios` or `ltsp image /`?
ltsp image raspios
What's the output of this: ls -lh /srv/ltsp/images
ltsp image raspios --mksquashfs-params='-comp lzo' to be exact
the output is raspios.img
sudo mount -o loop,ro /srv/ltsp/raspios /mnt
Does that say e.g. ubuntu or e.g. raspberry?
sudo mount -o loop,ro /srv/ltsp/images/raspios.img /mnt
Sorry I misttyped, use this ^ one
Ok wait a sec, sorry my laptop is tou of battery
BTW, currently im just booting them from NFS + RW
|21:27||ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)|
it says Raspbian Buster 10
OK so it's correct. Why do you think that it takes the server iamge?
(to umount it, run: sudo umount /mnt)
well the user im using on the server is ltsp and the user on im using on the client is PI, when PIs boot from image the user that i shown in the login box is ltsp
it should autologin as PI
Ah, you misunderstood
LTSP takes the image rootfs but not its users nor its home
Because we WANT the users and home to come from the server, via sshfs
That way people can login to any pi or even to any pc, and have the same accounts and home directory
any option to make it take home and users, i building a kiosk like stations
or maybe any way to create a whole image that will run in PIs memory? (after netbooting ofcourse)
You don't want that because it would waste ram
Instead, check the wiki, it has documentation for kiosk setups
Where each kiosk has the same "pi" user that maps to an nfs directory on the server
And it gets reset on login
RAM is not an issue, i can buy the 8gig PIs
i need them to be stable, its more important to me
Why do you think that NFS isn't stable?
Do you plan to poweroff the server?
well yes for maintenance...
OK anyway, there is an IMAGE_TO_RAM option but it is activated from the initramfs and raspberry pi os doesn't use an initramfs
You could add an initramfs, but it would be better to add the IMAGE_TO_RAM support in 25-ro-root.sh
As a novice user you'll need to do some reading to be able to do these modifications
While for the other part, the users and /home, you'll find what you want in the wiki
but the issue is the fact that NFS is network dependent makes it vulnerable to some network misconfigurations made by other people or even network bottlenecks...
It is true that adjusting ltsp for a kiosk setup takes a few hours currently
Unfortunately noone contributed code to add support for that upstream, and personally I have no use for kiosks. Maybe if funding is found, they could be integrated upstream, but there's enough info in the wiki anyway
wish that there were more video tutorials for every section in LTSP, would surely help a novice like me. but hey thank you very much...ill keep digging.
one more question, what is the best way to remote control PIs that boot from a single image? vnc server / nomachine are listening on display:0 of the last netbooted PI
which means that i need to restart the vnc/nxserver on each machine i wont to connect
epoptes: Epoptes is a computer lab administration and monitoring tool. It works on Ubuntu and Debian based labs with LTSP or non-LTSP servers, thin and fat clients, standalone workstations, NX clients etc. More info: https://epoptes.org
It's a tool that we made to manage ltsp workstations, it works fine for raspberries as well
ok and it can spawn multiple displays ? so that every PI will get its own display?
Eeeh I'm not sure what you mean there. Go to epoptes.org to see a screenshot
It has live thumbnails of the client screens, and when you double click on them, it opens vnc
You can open all of them in vnc windows, or just one
as i said currently im booting all my PIs via tftp and their filesystem is mounted over NFS
so lets say 8 PIs have the same FS
they all have different hostname and IP (DHCP provides)
nxserver for instance is listening on display:0 of the 8th RPI
Epoptes is more optimized, there's no vnc running if you don't want it
if iil try to connect to RPI 1-7 i will get a black screen
It only need 1 MB memory for a remote connection; then vnc is started on double click == on demand
It's also more secure as it does reverse connections, client to server
Just install it and see
Hmm...ok..i will try it.
again thank you very much for your support
Ohh i see that epoptes has no windows client
|22:53||lucascastro has left IRC (email@example.com, Ping timeout: 256 seconds)|
|23:05||AllesMeins has joined IRC (AllesMeins!~AllesMein@p5dcb2259.dip0.t-ipconnect.de)|
|23:20||vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100e)|
|23:31||AllesMeins has left IRC (AllesMeins!~AllesMein@p5dcb2259.dip0.t-ipconnect.de, Quit: Client closed)|