|00:00||vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:50, *.net *.split)|
|00:00||fiesh has left IRC (fiesh!~fiesh@2003:fb:1018::21, *.net *.split)|
|00:00||vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:50)|
|00:00||fiesh has joined IRC (fiesh!~fiesh@2003:fb:1018::21)|
|01:47||vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:50, Quit: leaving)|
|02:55||highvoltage has left IRC (firstname.lastname@example.org, *.net *.split)|
|02:55||sunweaver has left IRC (email@example.com, *.net *.split)|
|02:55||sunweaver has joined IRC (firstname.lastname@example.org)|
|02:55||sunweaver is now away: not here ...|
|08:25||ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)|
|09:57||Vercas1 has left IRC (Vercas1!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection)|
|09:58||Vercas1 has joined IRC (Vercas1!~Vercas@gateway/tor-sasl/vercas)|
|10:00||sunweaver is back|
|11:19||sunweaver is now away: not here ...|
|13:17||eu^c-73-190-66-4 has joined IRC (email@example.com)|
Trying to setup LTSP to push out Kodi images to fat clients. Client image to be managed via VirtualBox vmdk file. However, LTSP docs indicate VM image should only have 1 partition and Kodi auto-installs with a vfat32 RW partition and a ext4 RO partition. Are there any switches in "ltsp image" command to work with this setup? I saw some
documentation that seems to imply it can work, but I could not get it working myself.
eu^c-73-190-66-4: what are the contents of these partitions?
firing up VirtualBox...
As an FYI, I'm doing a clean install of LTSP right now per https://ltsp.org/docs/installation/
|13:34||eu^c-73-190-66-4 has left IRC (firstname.lastname@example.org, Quit: Client closed)|
|13:34||eu^c-73-190-66-4 has joined IRC (email@example.com)|
so /dev/sda1 mounted on /flash (vfat, RO) with contents syslinux.cfg, ldlinux.sys, KERNEL file (which is actually an image), SYSTEM file (which is actually an image).
and /dev/sda2 mounted on /storage (ext4, RW) with contents of a few config files, backup dir, lost+found dir, music dir, pictures dir, videos dir
the /storage mount could probably be moved to the NAS server (either NFS or SMB)...
noticed there are also loopback mounts. /dev/loop0 on / type squashfs (RO)
eu^c-73-190-66-4: this doesn't sound like a debian-based image... can you chroot into it and run `dpkg -l`?
Or if you're booted with it, just run dpkg -l
Then it's not debian-based, then you can't use ltsp with it
PRETTY_NAME="LibreELEC (official): 11.0.1"
LTSP currently only supports debian-based distributions
Huh. Somehow I missed that the OS must be debian based in the documentation. That's a bummer
Any recommendations for a very stripped down debian-based distro? Ubuntu is getting out of hand these days...
Well bookworm just got out; you could install just the base OS and kodi on top of it
But Ubuntu is fine too if you don't use GNOME and if you remove the snap
...and remove the advertisements, and cloud init, and...
You could also manually netboot libreelec, but LTSP can't do automatically do it for you: https://wiki.libreelec.tv/configuration/network-boot
Yeah, saw the manual netboot. Wasn't sure how much LTSP would be able to help.
Appreciate the clarification on debian only. Will explore that route. In the meantime, perhaps you might know directions I should pursue for other aspects of this project.
If it's for kiosk like devices with no users etc, indeed you don't need ltsp much
As libreelec already seems to provide an "overlay" parameter, to allow multiple clients to boot from the same source
Although it appears it's not using squashfs over nfs, so it'll be like 5 times slower than it could be
I suspect slow is fine, since max throughput required is streaming of video and loading pictures. Required bandwidth for streaming isn't that high (unless 4K or 8K which is is most definitely not going to be).
Even with some funky double-round trip networking I've got going, I can still push some 30 MB/sec which feels like its much more than streaming would require
Though your point is well taken. I will not know for sure until I can get over this initial hump and getting LTSP working.
It'll only be slow while booting, it won't make any difference later
I.e. for rootfs / access, not for data access
Interesting, so if the VirtualBox image is say 4GB does that mean during booting LTSP pushes over the entire 4GB?
What's the goal, to netboot multiple kiosk-like machines with no users that just display kodi?
No, network disks are read either file-by-file as needed (on plain NFS like libreelec), or sector-by-sector (on squashfs over NFS like ltsp)
So you can have a 10 GB disk and boot a 1 GB client with it without any issues
Goal is comparable to a home entertainment system setup. Boot kodi on one of a few cheap fat-clients that may fail at any time (again, cheap). If they do then just swap out and turn the new one on.
It will be a bit more complex than that, but if I can get there I can get the rest of the way without issue.
Just one? then plain NFS-RW is fine, you don't need some special netbooting system
will have 3-4 to begin with. Was going to skip LTSP all together but the amount of configuration and setup for Kodi ended up being considerable...especially when 3x or 4x. Then there's the whole "client may die" concern, adding more time.
Guess LTSP doesn't work very well with say a Clonezilla iamge
Clonezilla is Debian or Ubuntu-based AFAIK, so it might work
But LTSP is oriented in "boot an image simultaneously in multiple PCs, using multiple users etc"
Your use case doesn't seem to align with that. If you just want to netboot one image, there are other solutions
E.g. https://netboot.xyz/ can netboot a lot of distributions
Interesting. My client image solution search didn't yield much.
As for netboot.xyz, my review of it seems to imply it boots install images rather than preconfigured "turn on and go" images
netboot.xyz can boot a lot of CDs, not just installation medias
So e.g. clonezilla or debian live or ubuntu-desktop.iso should be bootable with it
Check the list there: https://github.com/netbootxyz/netboot.xyz#what-operating-systems-are-currently-available-on-netbootxyz
Clonezilla is in the list
So you're thought is to create VM with Kodi as I need, use netboot.xyz to boot Clonezilla and make image of that VM, then somehow use Clonezilla image to netboot.xyz a fat-client with the image?
Eeh, I think Kodi is completely unrelated to Clonezilla
I thought you wanted Clonezilla for a different project
Now you completely confused me and I've no idea why you want clonezilla
Nope. Current project objective is Kodi on 3-4 fat-clients. Was thinking Clonezilla might be a path to get there via creating a Kodi Virtual machine then imaging to fat-clients.
I thought you said you wanted to run Kodi on one diskless client. And if its hardware breaks, then you'd put another in its place
My apologies for the confusion. Run Kodi on 3-4 fat-clients that may fail so when they do swap out with another one and netboot that new one to get back on track.
This is the key question. Are two clients going to be netbooted at the SAME time or not?
If not, then you can use NFS-RW. But you can't use NFS-RW to boot multiple clients at the same time
For now we can assume only 1 client at a time will be up. When the time comes to have multiple up at the same time I can re-evaluate
Then you can use plain NFS-RW, or libreelece with or without the overlay mode, and debian or ubuntu with kodi on top
So you have 3 solutions, choose the one you feel is better. If stock libreelec is good enough for you, then maybe the libreelec netboot page is enough
I'm just now starting to review netboot.xyz in more detail as per your suggestion. It is starting to look like I can indeed do local hosting of images (required for project) and do not necessarily require just install images (eg a pre-configured Kodi+libreelec setup).
If I went with the LTSP approach, you're saying A) it needs to be Debian-based and B) it needs to be 1 partition?
The quick answer is "yes"
eu^c-73-190-66-4: I do one/ parrition and another for/home/studens on seconda hard drive
Sorry for my english. Polish corrections in phone
adam.jurkiewicz.pythonista: he meant inside the VM image, e.g. inside VirtualBox, not in the booted clients
Oooo, i didnt saw
I am on vacation on Samos
And look for phone sometimes
|15:23||ogra is now away: currently disconnected|
|15:54||ogra is back|
|16:06||Pacify[m] has left IRC (Pacify[m]!~rintfsmat@2001:470:69fc:105::2:b6d4, Remote host closed the connection)|
|16:47||XYZ has left IRC (XYZ!~XYZ@89-24-41-33.nat.epc.tmcz.cz, Remote host closed the connection)|
|16:52||XYZ has joined IRC (XYZ!~XYZ@89-24-41-33.nat.epc.tmcz.cz)|
|17:06||Vercas16 has joined IRC (Vercas16!~Vercas@gateway/tor-sasl/vercas)|
|17:06||Vercas1 has left IRC (Vercas1!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection)|
|17:06||Vercas16 is now known as Vercas1|
|18:22||XYZ has left IRC (XYZ!~XYZ@89-24-41-33.nat.epc.tmcz.cz, Ping timeout: 260 seconds)|
|18:36||XYZ has joined IRC (XYZ!~XYZ@78-80-25-251.customers.tmcz.cz)|
|18:37||XYZ has left IRC (XYZ!~XYZ@78-80-25-251.customers.tmcz.cz, Remote host closed the connection)|
|19:00||Pacify[m] has joined IRC (Pacify[m]!~rintfsmat@2001:470:69fc:105::2:b6d4)|
|20:54||ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)|
|21:04||bildo_ has joined IRC (firstname.lastname@example.org)|
|21:07||bildo has left IRC (email@example.com, Ping timeout: 240 seconds)|
|21:36||vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:50)|
|21:48||book` has left IRC (firstname.lastname@example.org, Quit: Leaving)|
|22:07||book` has joined IRC (email@example.com)|