IRC chat logs for #ltsp on irc.libera.chat (webchat)
Channel log from 26 May 2019 (all times are UTC)
| 03:36 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving) | |
| 08:53 | SYS64738 has joined IRC (SYS64738!~jhonny5@159.213.93.166) | |
| 10:09 | uumas has left IRC (uumas!uumas@kapsi.fi, Quit: leaving) | |
| 10:09 | uumas has joined IRC (uumas!uumas@kapsi.fi) | |
| 10:17 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
| 11:32 | SYS64738 has left IRC (SYS64738!~jhonny5@159.213.93.166, Ping timeout: 258 seconds) | |
| 14:51 | thomas_ has joined IRC (thomas_!54c43159@gateway/web/freenode/ip.84.196.49.89) | |
| 15:03 | thomas_ has left IRC (thomas_!54c43159@gateway/web/freenode/ip.84.196.49.89, Quit: Page closed) | |
| 15:09 | SYS64738 has joined IRC (SYS64738!~jhonny5@159.213.93.166) | |
| 16:21 | vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc) | |
| 18:21 | <uumas> I just noticed that there is "ltsp-client-builder: build an LTSP environment in the installer target" as an option in the debian buster netboot "Download installer components" section
| |
| 18:22 | Is that working and what exactly does it do?
| |
| 18:23 | <vagrantc> haven't tested it recently, but it might work. i wouldn't recommend it as it defaults to creating a thin client.
| |
| 18:24 | these days the recommendation is to use chrootless fat clients
| |
| 18:24 | <uumas> Yeah, I know
| |
| 18:25 | Are there plans to update it for ltsp6 or would it be better to remove the option entirely?
| |
| 18:25 | <vagrantc> i had long been meaning to update ltsp-client-builder to build an environment more like the recommended setup
| |
| 18:25 | <alkisg> ltsp6 wont exist at all; ltsp19 will be written from scratch, and support VMs and chroots
| |
| 18:25 | <vagrantc> just haven't gotten around to it
| |
| 18:25 | and that :)
| |
| 18:26 | <uumas> Well, at this point probably same to wait for ltsp19 :)
| |
| 18:27 | <vagrantc> should be able to provide backports for ltsp19 when the time comes ... but at the moment sticking with ltsp5 in debian buster since it's in freeze
| |
| 18:27 | i was actually in the middle of doing some ltsp testing on buster today to make sure major bugs havne't leaked in since my last tests in december
| |
| 18:28 | <uumas> Btw, how far is buster from becoming stable?
| |
| 18:28 | I noticed that lsb_release -a no longer says testing but debian10
| |
| 18:29 | <vagrantc> sometime in the next couple months
| |
| 18:29 | would be my guess ... can't predict the future, though
| |
| 18:31 | <uumas> Ok
| |
| 18:31 | <vagrantc> which reminds me about at least one breakage in ltsp packages that might not be noticed until buster actualyl does become stable
| |
| 18:45 | <alkisg> uumas: I successfully booted .isos as ltsp clients; so ltsp-build-client won't be even needed, you could use any .iso as thin chroot
| |
| 18:47 | <uumas> What'd be the use case for that (or chroot)
| |
| 18:48 | <alkisg> E.g. if you want to demo ltsp
| |
| 18:49 | <uumas> So, do you mean an iso booted from say, usb or from an ltsp server
| |
| 19:11 | <alkisg> E.g. you have a normal ubuntu installation and you want to try ltsp
| |
| 19:11 | apt install ltsp takes 10 sec; you already have the iso; in 20 sec you can demo ltsp
| |
| 19:12 | otherwise ltsp-build-client takes a lot of minutes, depending on net connection too
| |
| 19:12 | Or, some people want to work on fedora, others on ubuntu, others on debian; you can just have multiple isos
| |
| 19:13 | /home and accounts will be served as usual with ltsp
| |
| 19:13 | <uumas> So the iso would be mounted over nfs, right?
| |
| 19:13 | <alkisg> NFS file,not nfs dir
| |
| 19:14 | Same speed like nbd chroots
| |
| 19:14 | <uumas> Yeah
| |
| 19:14 | <alkisg> I put code for double-loop mounts
| |
| 19:14 | First loop mount the iso, then filesystem.squashfs inside the iso
| |
| 19:14 | (which is the ubuntu/debian etc image)
| |
| 19:15 | Or you can have a virtualbox vm and directly export that, as full raw disk
| |
| 19:15 | A bit slower, but doesn't need ltsp-update-image
| |
| 19:15 | The act of building a chroot isn't really useful; you can have a vm instead of a chroot; or you can just copy the contents of the vm in a dir
| |
| 19:16 | <uumas> Why not just have that vm as another ltsp server? Would probably be easier to maintain
| |
| 19:19 | I can think of good use cases for mounting iso files, even outside ltsp
| |
| 19:32 | woernie_ has joined IRC (woernie_!~werner@pD9E8B322.dip0.t-ipconnect.de) | |
| 19:37 | <alkisg> Sure the chrootless case will still be supported; the VMs are for those that want a different installation on the clients rather than on the server
| |
| 20:15 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Remote host closed the connection) | |
| 21:15 | woernie_ has left IRC (woernie_!~werner@pD9E8B322.dip0.t-ipconnect.de, Remote host closed the connection) | |
| 22:17 | adrianor1 has joined IRC (adrianor1!~adrianorg@187.113.251.145) | |
| 22:19 | <vagrantc> !howto
| |
| 22:19 | <ltsp> Error: "howto" is not a valid command.
| |
| 22:20 | adrianorg has left IRC (adrianorg!~adrianorg@177.18.102.108, Ping timeout: 245 seconds) | |
| 22:22 | <vagrantc> "ltsp-update-image --cleanup /" behaves very strangely when ltsp-client* is not installed
| |