|00:29||lucascastro has left IRC (email@example.com, Remote host closed the connection)|
|00:30||lucascastro has joined IRC (firstname.lastname@example.org)|
|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 (Hyperbyteemail@example.com, Ping timeout: 245 seconds)|
|05:26||vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100e, Ping timeout: 240 seconds)|
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)|
My main problems is figuring out how to use ltsp + mount a nas.
So my setup/ideas so far:
1. I want to serve a Raw virtual machine image to the clients -> plan ist to create a Kubuntu Installation via VirtualBox
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)
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
So now after reading the documentation i am not sure how to best approach this.
Is LDAP and mounting an external drive done on the Raw virtual machine image?
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.
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
packages then (x-server related etc.) so i wonder what would be the best practice for my case.
Thats all my big question marks for now - i am about to try this setup via VirtualBox
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
1) kubuntu / virtualbox is fine
2) external ldap is supported by ltsp
(just configure your kubuntu VM to use that)
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|
I mean `/nick some-nickname-here`, not "username"; e.g. john123 or nick234
i tried - but my first 3 approaches are all taken ;)
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
Put a number after the nickname, e.g. "john" is certainly not unique in irc...
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)|
back with a "normal"
Much better :)
Now if you come tomorrow, we'll know you're the kubuntu/nas guy, not a new random guest user :)
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?
Did you see what I wrote? If not, see it in https://irclogs.ltsp.org/
got your point with the username ;)
After running ltsp image/kernel/initrd/ipxe etc, the relevant generated files are:
ltsp.img => contains ltsp.conf and the ltsp code. It's downloaded via tftp
via tftp also are downloaded the kernel and initrd
While /srv/ltsp/images/x86_64.img is the rootfs, the squashfs image, and is usually reached via nfs
So, if your NAS has TFTP and NFS, you can place these files there, and power off the ltsp server
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
What's your NAS software, and what are you using for DHCP/TFTP?
The NAS is a qnap with the QTS-Software by qnap. DHCP is done via router - a watchguard
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
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
No, ltsp is specifically designed to be extremely minimal
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
apt install --install-recommends ltsp ltsp-binaries dnsmasq openssh-server squashfs-tools ethtool net-tools nfs-common epoptes
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
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
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.
It's just for controlling the clients, right
ok - thx for your help. i'll give it a try.
E.g. if one wants to netboot clients to dd windows images on them, he can use epoptes to do that (no classroom involved)
Otherwise he'd have to use ssh/vnc to get access to the clients to manage them
was really helpful. thx again and have a nice day
|10:52||matt6789 has left IRC (matt6789!~matt6789@2001:9e8:6300:1900:bad2:ba58:6e47:c3a, Quit: Client closed)|
<alkisg> "sfxworks: also note that ipxe..." <- Oh no, that mean I can't make a raspberry pi pxe server? :(
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
But note that for many users, you'll need a fast disk, not an SD card :D
Yeah I have an nvme attached to a compute module
Though I get that error even when adding ltsp ppa
Is there somewhere else I can download ltsp-binaries?
sfxworks: which distro/version are you using?
raspbian `PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"`
Everything installs except ltsp-binaries
You can download the .deb from https://launchpad.net/~ltsp/+archive/ubuntu/ppa/+packages
It's architecture "all", so it's installable to arm too
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
No the problem is that PPAs don't target ARM architectures by default
I'll see if I can ask for it to be enabled for the LTSP PPA
|17:02||lucascastro has left IRC (firstname.lastname@example.org, Ping timeout: 240 seconds)|
|17:24||lucascastro has joined IRC (email@example.com)|
|19:15||ltspbot has joined IRC (firstname.lastname@example.org)|
|20:18||lucascastro has left IRC (email@example.com, 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 (firstname.lastname@example.org)|
|22:36||jh has joined IRC (email@example.com)|
|22:39||jh has left IRC (firstname.lastname@example.org, Client Quit)|
|22:39||j_sh has joined IRC (email@example.com)|
|23:29||j_sh has left IRC (firstname.lastname@example.org, Ping timeout: 256 seconds)|
|23:36||Hyperbyte has joined IRC (Hyperbyteemail@example.com)|