IRC chat logs for #ltsp on irc.libera.chat (webchat)
Channel log from 1 December 2021 (all times are UTC)
| 00:00 | vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100e, *.net *.split) | |
| 00:00 | quinox has left IRC (quinox!~quinox@ghost.qtea.nl, *.net *.split) | |
| 00:01 | quinox has joined IRC (quinox!~quinox@ghost.qtea.nl) | |
| 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) | |
| 08:30 | <Hyperbyte> Good morning alkisg :-)
| |
| 08:47 | <alkisg> Good morning Jan
| |
| 09:05 | <Hyperbyte> How's it going?
| |
| 09:54 | NecTal has joined IRC (NecTal!~NecTal@194.126.106.149) | |
| 11:47 | Faith has joined IRC (Faith!~Paty_@user/faith) | |
| 13:26 | NecTal has left IRC (NecTal!~NecTal@194.126.106.149, Quit: Client closed) | |
| 16:01 | yopla has joined IRC (yopla!~yopla@82-64-129-174.subs.proxad.net) | |
| 19:03 | woernie has left IRC (woernie!~werner@p5b296fbf.dip0.t-ipconnect.de, Remote host closed the connection) | |
| 19:41 | yopla has left IRC (yopla!~yopla@82-64-129-174.subs.proxad.net, 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) | |
| 21:04 | <raspberrypipe[m]> Hello @all
| |
| 21:05 | need some help with LTSP + Pi
| |
| 21:06 | someone ?
| |
| 21:16 | <alkisg> raspberrypipe: sure, just ask
| |
| 21:17 | Did you see the https://ltsp.org/docs/installation/raspios/ page?
| |
| 21:17 | <raspberrypipe[m]> Yes i did
| |
| 21:18 | i have several 4GB RPI4s
| |
| 21:19 | 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
| |
| 21:20 | <alkisg> Are you running `ltsp image raspios` or `ltsp image /`?
| |
| 21:20 | <raspberrypipe[m]> ltsp image raspios
| |
| 21:20 | <alkisg> What's the output of this: ls -lh /srv/ltsp/images
| |
| 21:20 | <raspberrypipe[m]> ltsp image raspios --mksquashfs-params='-comp lzo' to be exact
| |
| 21:21 | the output is raspios.img
| |
| 21:21 | <alkisg> sudo mount -o loop,ro /srv/ltsp/raspios /mnt
| |
| 21:21 | cat /mnt/etc/os-release
| |
| 21:22 | Does that say e.g. ubuntu or e.g. raspberry?
| |
| 21:22 | sudo mount -o loop,ro /srv/ltsp/images/raspios.img /mnt
| |
| 21:22 | Sorry I misttyped, use this ^ one
| |
| 21:23 | <raspberrypipe[m]> Ok wait a sec, sorry my laptop is tou of battery
| |
| 21:23 | out*
| |
| 21:24 | BTW, currently im just booting them from NFS + RW
| |
| 21:27 | ok
| |
| 21:27 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |
| 21:28 | <raspberrypipe[m]> it says Raspbian Buster 10
| |
| 21:28 | <alkisg> OK so it's correct. Why do you think that it takes the server iamge?
| |
| 21:28 | (to umount it, run: sudo umount /mnt)
| |
| 21:30 | <raspberrypipe[m]> 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
| |
| 21:30 | it should autologin as PI
| |
| 21:30 | <alkisg> Ah, you misunderstood
| |
| 21:30 | LTSP takes the image rootfs but not its users nor its home
| |
| 21:31 | Because we WANT the users and home to come from the server, via sshfs
| |
| 21:31 | That way people can login to any pi or even to any pc, and have the same accounts and home directory
| |
| 21:31 | <raspberrypipe[m]> Ohhh...
| |
| 21:32 | any option to make it take home and users, i building a kiosk like stations
| |
| 21:33 | or maybe any way to create a whole image that will run in PIs memory? (after netbooting ofcourse)
| |
| 21:33 | <alkisg> You don't want that because it would waste ram
| |
| 21:33 | Instead, check the wiki, it has documentation for kiosk setups
| |
| 21:34 | Where each kiosk has the same "pi" user that maps to an nfs directory on the server
| |
| 21:34 | And it gets reset on login
| |
| 21:34 | <raspberrypipe[m]> RAM is not an issue, i can buy the 8gig PIs
| |
| 21:34 | i need them to be stable, its more important to me
| |
| 21:34 | <alkisg> Why do you think that NFS isn't stable?
| |
| 21:34 | Do you plan to poweroff the server?
| |
| 21:35 | <raspberrypipe[m]> well yes for maintenance...
| |
| 21:36 | <alkisg> 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
| |
| 21:36 | You could add an initramfs, but it would be better to add the IMAGE_TO_RAM support in 25-ro-root.sh
| |
| 21:37 | As a novice user you'll need to do some reading to be able to do these modifications
| |
| 21:37 | While for the other part, the users and /home, you'll find what you want in the wiki
| |
| 21:37 | <raspberrypipe[m]> 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...
| |
| 21:38 | <alkisg> It is true that adjusting ltsp for a kiosk setup takes a few hours currently
| |
| 21:39 | 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
| |
| 21:41 | <raspberrypipe[m]> 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.
| |
| 21:42 | 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
| |
| 21:43 | which means that i need to restart the vnc/nxserver on each machine i wont to connect
| |
| 21:43 | <alkisg> !epoptes
| |
| 21:43 | <ltspbot> 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
| |
| 21:43 | <alkisg> It's a tool that we made to manage ltsp workstations, it works fine for raspberries as well
| |
| 21:44 | <raspberrypipe[m]> ok and it can spawn multiple displays ? so that every PI will get its own display?
| |
| 21:46 | <alkisg> Eeeh I'm not sure what you mean there. Go to epoptes.org to see a screenshot
| |
| 21:46 | It has live thumbnails of the client screens, and when you double click on them, it opens vnc
| |
| 21:46 | You can open all of them in vnc windows, or just one
| |
| 21:47 | <raspberrypipe[m]> as i said currently im booting all my PIs via tftp and their filesystem is mounted over NFS
| |
| 21:47 | so lets say 8 PIs have the same FS
| |
| 21:48 | they all have different hostname and IP (DHCP provides)
| |
| 21:49 | nxserver for instance is listening on display:0 of the 8th RPI
| |
| 21:49 | <alkisg> Epoptes is more optimized, there's no vnc running if you don't want it
| |
| 21:49 | <raspberrypipe[m]> if iil try to connect to RPI 1-7 i will get a black screen
| |
| 21:50 | <alkisg> It only need 1 MB memory for a remote connection; then vnc is started on double click == on demand
| |
| 21:50 | It's also more secure as it does reverse connections, client to server
| |
| 21:50 | Just install it and see
| |
| 21:51 | <raspberrypipe[m]> Hmm...ok..i will try it.
| |
| 21:51 | again thank you very much for your support
| |
| 21:51 | <alkisg> You're welcome
| |
| 21:52 | <raspberrypipe[m]> Ohh i see that epoptes has no windows client
| |
| 22:53 | lucascastro has left IRC (lucascastro!~lucascast@192-140-51-192.static.oncabo.net.br, 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) | |