IRC chat logs for #ltsp on irc.libera.chat (webchat)
Channel log from 6 January 2022 (all times are UTC)
| 00:29 | lucascastro has left IRC (lucascastro!~lucascast@192-140-51-251.static.oncabo.net.br, Remote host closed the connection) | |
| 00:30 | lucascastro has joined IRC (lucascastro!~lucascast@192-140-51-251.static.oncabo.net.br) | |
| 00:44 | vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100b, Quit: leaving) | |
| 01:11 | vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100e) | |
| 05:09 | Hyperbyte has left IRC (Hyperbyte!~jan@middelkoop.cc, Ping timeout: 245 seconds) | |
| 05:26 | vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100e, Ping timeout: 240 seconds) | |
| 06:03 | <alkisg> sfxworks: also note that ipxe doesn't work on raspberry pis so ltsp-binaries are not needed there
| |
| 06:41 | Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection) | |
| 06:41 | Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas) | |
| 07:33 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
| 09:52 | eu^i5E866DEEvers has joined IRC (eu^i5E866DEEvers!~eu^i5E866@2001:9e8:631f:8200:5da9:5744:4bbb:6423) | |
| 10:06 | eu^i5E866DEEvers has left IRC (eu^i5E866DEEvers!~eu^i5E866@2001:9e8:631f:8200:5da9:5744:4bbb:6423, Ping timeout: 256 seconds) | |
| 10:19 | eu^i5E866DEEvers has joined IRC (eu^i5E866DEEvers!~eu^i5E866@2001:9e8:6300:1900:bad2:ba58:6e47:c3a) | |
| 10:19 | <eu^i5E866DEEvers> My main problems is figuring out how to use ltsp + mount a nas.
| |
| 10:19 | So my setup/ideas so far:
| |
| 10:19 | 1. I want to serve a Raw virtual machine image to the clients -> plan ist to create a Kubuntu Installation via VirtualBox
| |
| 10:19 | 2. The clients logging in to that virtual machine image should do so via LDAP - where i already got a openLDAP Server running (external - not planned to use the LTSP-Server for that)
| |
| 10:19 | 3. The clients logging in to the virtual machine image should connect/mount a NAS-Folder where all documents the users work on are stored. The access to that NAS(-folder) also uses the existing LDAP-Server
| |
| 10:19 | So now after reading the documentation i am not sure how to best approach this.
| |
| 10:19 | Is LDAP and mounting an external drive done on the Raw virtual machine image?
| |
| 10:19 | Where are the /home folders of the users logging in stored? The documentation says to use "fixed size" for the virtual machine image. OK - the plan is to store all files on the mounted NAS - but still fixed means that there is a limit that may someday cause a problem.
| |
| 10:19 | Also it is written best to use a desktop .iso for the LTSP-Server -> but as i am not planning to use chrootless but a raw virtual machine image via VirtualBox i am not sure why i should prefer to use a desktop.iso" instead of a "small" ubuntu-server installation without gui. Well - i tried this and i know ltsp needed quite a lot of additional
| |
| 10:19 | packages then (x-server related etc.) so i wonder what would be the best practice for my case.
| |
| 10:19 | Thats all my big question marks for now - i am about to try this setup via VirtualBox
| |
| 10:21 | <alkisg> Hi eu^i5E866DEEvers ; first of all it'd be best to type `/nick username` to set a normal nickname so that we can address you with that
| |
| 10:22 | 1) kubuntu / virtualbox is fine
| |
| 10:22 | 2) external ldap is supported by ltsp
| |
| 10:22 | (just configure your kubuntu VM to use that)
| |
| 10:23 | 3) Use FSTAB_HOME="nas-ip:/path /home defaults,nolock 0 0" in ltsp.conf to mount your home from nas
| |
| 10:23 | eu^i5E866DEEvers is now known as username | |
| 10:23 | username is now known as Guest6185 | |
| 10:23 | <alkisg> I mean `/nick some-nickname-here`, not "username"; e.g. john123 or nick234
| |
| 10:24 | <Guest6185> i tried - but my first 3 approaches are all taken ;)
| |
| 10:24 | <alkisg> With steps 1/2/3, your clients won't really need the ltsp server at all, so you should be able to put your rootfs (the squashfs image) in nas too
| |
| 10:25 | Put a number after the nickname, e.g. "john" is certainly not unique in irc...
| |
| 10:26 | The only "server" part that the clients will need is dnsmasq for proxydhcp and tftp; you can take care of that from any minimal server image or even on the nas itself, with no ltsp server at all
| |
| 10:26 | Guest6185 has left IRC (Guest6185!~eu^i5E866@2001:9e8:6300:1900:bad2:ba58:6e47:c3a, Quit: Client closed) | |
| 10:26 | matt6789 has joined IRC (matt6789!~matt6789@2001:9e8:6300:1900:bad2:ba58:6e47:c3a) | |
| 10:27 | <matt6789> back with a "normal"
| |
| 10:27 | name
| |
| 10:27 | <alkisg> Much better :)
| |
| 10:27 | Now if you come tomorrow, we'll know you're the kubuntu/nas guy, not a new random guest user :)
| |
| 10:28 | <matt6789> about ") Use FSTAB_HOME="nas-ip:/path /home defaults,nolock 0 0" in ltsp.conf to mount your home from nas" -> the ltsp.conf file is on the ltsp-server right? Or also on the virtual machine image?
| |
| 10:28 | <alkisg> Did you see what I wrote? If not, see it in https://irclogs.ltsp.org/
| |
| 10:28 | <matt6789> got your point with the username ;)
| |
| 10:28 | <alkisg> After running ltsp image/kernel/initrd/ipxe etc, the relevant generated files are:
| |
| 10:29 | ltsp.img => contains ltsp.conf and the ltsp code. It's downloaded via tftp
| |
| 10:29 | via tftp also are downloaded the kernel and initrd
| |
| 10:29 | While /srv/ltsp/images/x86_64.img is the rootfs, the squashfs image, and is usually reached via nfs
| |
| 10:30 | So, if your NAS has TFTP and NFS, you can place these files there, and power off the ltsp server
| |
| 10:30 | If you plan to do that, then you don't even need an ltsp server, as you can generate ltsp.img from within the kubuntu vm
| |
| 10:30 | What's your NAS software, and what are you using for DHCP/TFTP?
| |
| 10:33 | <matt6789> The NAS is a qnap with the QTS-Software by qnap. DHCP is done via router - a watchguard
| |
| 10:36 | <alkisg> OK anyway I propose that you start with chrootless, where the kubuntu vm is also the ltsp server, and you'll see at that point if you can completely avoid the need for a server, or you'll need to use a minimal server vm
| |
| 10:36 | <matt6789> if i create the ltsp.img from within the kubuntu vm - wouldnt this mean the vm i want to use to serve to the clients would need the ltsp-server installation? On first look this sounds like it would "bloat" the image i would serve
| |
| 10:36 | <alkisg> No, ltsp is specifically designed to be extremely minimal
| |
| 10:37 | <matt6789> k - i just give it a try - my main questions were the ldap and fstab - if this has to be done in the virtual machine image (to which the answer seems to be yes) - or the server (which is yes for fstab = ltsp.conf). thx a lot - i ll try to figure out myself before asking questions that my answer themselves. Thx for the help
| |
| 10:38 | <alkisg> apt install --install-recommends ltsp ltsp-binaries dnsmasq openssh-server squashfs-tools ethtool net-tools nfs-common epoptes
| |
| 10:38 | If you run these inside the kubuntu image, you'll see that only a few MB are downloaded, and you can omit epoptes if you don't want it, which is the larger part
| |
| 10:39 | The related services (dnsmasq) aren't started on the clients, so e.g. dnsmasq just adds 1 MB to the image size; it doesn't need any RAM on the clients at all
| |
| 10:39 | <matt6789> epoptes is just for remote control right? so not a dependency? Kind of like teamviewer. As i got no "class room" or similar i dont really need that.
| |
| 10:39 | <alkisg> It's just for controlling the clients, right
| |
| 10:40 | <matt6789> ok - thx for your help. i'll give it a try.
| |
| 10:40 | <alkisg> E.g. if one wants to netboot clients to dd windows images on them, he can use epoptes to do that (no classroom involved)
| |
| 10:40 | Otherwise he'd have to use ssh/vnc to get access to the clients to manage them
| |
| 10:40 | OK, cheers
| |
| 10:41 | <matt6789> was really helpful. thx again and have a nice day
| |
| 10:41 | <alkisg> 👍️
| |
| 10:52 | matt6789 has left IRC (matt6789!~matt6789@2001:9e8:6300:1900:bad2:ba58:6e47:c3a, Quit: Client closed) | |
| 12:05 | <sfxworks[m]> <alkisg> "sfxworks: also note that ipxe..." <- Oh no, that mean I can't make a raspberry pi pxe server? :(
| |
| 12:42 | <alkisg> sfxworks: no, it means it's not needed for rpi clients. If you want to make an rpi a pxe server for PCs, you do need ltsp-binaries
| |
| 12:43 | But note that for many users, you'll need a fast disk, not an SD card :D
| |
| 12:55 | <sfxworks[m]> Yeah I have an nvme attached to a compute module
| |
| 12:56 | Though I get that error even when adding ltsp ppa
| |
| 12:56 | Is there somewhere else I can download ltsp-binaries?
| |
| 12:58 | <alkisg> sfxworks: which distro/version are you using?
| |
| 12:58 | <sfxworks[m]> raspbian `PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"`
| |
| 12:58 | Everything installs except ltsp-binaries
| |
| 12:58 | <alkisg> You can download the .deb from https://launchpad.net/~ltsp/+archive/ubuntu/ppa/+packages
| |
| 12:59 | It's architecture "all", so it's installable to arm too
| |
| 13:04 | <sfxworks[m]> tnx
| |
| 13:05 | also it looks like I ran `add-apt-repository ppa:ltsp` instead of the deb instructions on https://ltsp.org/docs/ppa/ but it somehow installed everything except ltsp-binaries until I added that list and gpg
| |
| 13:05 | my fault
| |
| 13:20 | <alkisg> No the problem is that PPAs don't target ARM architectures by default
| |
| 13:20 | I'll see if I can ask for it to be enabled for the LTSP PPA
| |
| 17:02 | lucascastro has left IRC (lucascastro!~lucascast@192-140-51-251.static.oncabo.net.br, Ping timeout: 240 seconds) | |
| 17:24 | lucascastro has joined IRC (lucascastro!~lucascast@45-167-143-6.netfacil.inf.br) | |
| 19:15 | ltspbot has joined IRC (ltspbot!~supybot@devs.ts.sch.gr) | |
| 20:18 | lucascastro has left IRC (lucascastro!~lucascast@45-167-143-6.netfacil.inf.br, Ping timeout: 256 seconds) | |
| 20:21 | vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100e) | |
| 21:28 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |
| 22:29 | lucascastro has joined IRC (lucascastro!~lucascast@192-140-51-251.static.oncabo.net.br) | |
| 22:36 | jh has joined IRC (jh!~jh@ip-209-124-249-106.static.eatel.net) | |
| 22:39 | jh has left IRC (jh!~jh@ip-209-124-249-106.static.eatel.net, Client Quit) | |
| 22:39 | j_sh has joined IRC (j_sh!~j_sh@ip-209-124-249-106.eatel.net) | |
| 23:29 | j_sh has left IRC (j_sh!~j_sh@ip-209-124-249-106.eatel.net, Ping timeout: 256 seconds) | |
| 23:36 | Hyperbyte has joined IRC (Hyperbyte!~jan@middelkoop.cc) | |