IRC chat logs for #ltsp on irc.libera.chat (webchat)
Channel log from 14 May 2018 (all times are UTC)
| 03:22 | lucas_ has left IRC (lucas_!~lucas@177-185-141-105.isotelco.net.br, Quit: Leaving) | |
| 03:22 | lucascastro has joined IRC (lucascastro!~lucas@177-185-141-105.isotelco.net.br) | |
| 05:30 | Statler|Home has joined IRC (Statler|Home!~Georg@p5489740C.dip0.t-ipconnect.de) | |
| 06:22 | kjackal has joined IRC (kjackal!~quassel@2a02:587:3102:4300:a538:3594:2e30:932c) | |
| 07:50 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
| 08:13 | Statler|Home has left IRC (Statler|Home!~Georg@p5489740C.dip0.t-ipconnect.de, Remote host closed the connection) | |
| 08:45 | Statler_Office has joined IRC (Statler_Office!~Georg@gwrz3.lohn24.de) | |
| 11:46 | <aheyde> Could anyone point me in the direction of reference on creating a "clean" fat client image - it seems the default way according to ltsp-manager docs is simply to use the server - but this means I have little control of my client image
| |
| 11:46 | (I would prefer to build up the client image rather than carefully excluding half the server filesystem)
| |
| 11:48 | Was thinking I could also use docker for fat client image building...
| |
| 11:52 | kjackal has left IRC (kjackal!~quassel@2a02:587:3102:4300:a538:3594:2e30:932c, Remote host closed the connection) | |
| 11:52 | kjackal has joined IRC (kjackal!~quassel@athedsl-238683.home.otenet.gr) | |
| 11:53 | Faith has joined IRC (Faith!~Paty_@unaffiliated/faith) | |
| 12:03 | <eirikb> aheyde: The theory, I think, is to mount your client somewhere (say /mnt) and then run "ltsp-update-image -c /mnt", you also need to install ltsp-client-core on the client first (if debian chroot /mnt apt-get -y install ltsp-client-core). Although I haven't been able to make this work myself
| |
| 12:04 | <aheyde> Thanks eirikb
| |
| 12:06 | <eirikb> My plan is to use VBox to build the client, then mount the VDI on the server
| |
| 12:11 | I also need docker to work on my clients, but the "--cleanup/-c" flag seems to mess that up (docker group will be removed, manually adding doesn't work). But I have been able to prepare install and then run apt-get install docker-ce on boot
| |
| 12:11 | Requires the client to have a bit of ram
| |
| 12:23 | lucascastro has left IRC (lucascastro!~lucas@177-185-141-105.isotelco.net.br, Remote host closed the connection) | |
| 12:27 | lucascastro has joined IRC (lucascastro!~lucas@177-185-141-105.isotelco.net.br) | |
| 12:40 | GodFather has joined IRC (GodFather!~rcc@174-081-217-069.dhcp.chtrptr.net) | |
| 13:36 | ben_roose has joined IRC (ben_roose!~roose@roose.cs.wichita.edu) | |
| 13:42 | <||cw> aheyde: what's wrong with using the server? ltsp should be the only role for the server, and it should be configured as a desktop primarily
| |
| 13:43 | let ltsp-pnp manage it, and/or ltsp-manager
| |
| 13:44 | <eirikb> Isn't it nice to keep the server clean? And in my case I want to rebuild the client from scripts
| |
| 13:50 | <aheyde> Well the first major reason is that i have nvidia graphics on the server which get polluted into the client image causing udev to use most of the CPU and make the client unusable
| |
| 13:50 | (nvidia drivers on server, modules attempt to load on client and fail forever)
| |
| 14:03 | GodFather has left IRC (GodFather!~rcc@174-081-217-069.dhcp.chtrptr.net, Ping timeout: 260 seconds) | |
| 14:18 | GodFather has joined IRC (GodFather!~rcc@174-081-217-069.dhcp.chtrptr.net) | |
| 14:22 | <alkisg> aheyde: that would be a bug for xorg then; nowadays nvidia is supposed to be co-installable with other drivers
| |
| 14:23 | <aheyde> I see. Thanks for that insight.
| |
| 14:24 | In the mean time I might consider going virtual for the server to avoid these types of issues
| |
| 14:26 | <alkisg> Well the idea is that ltsp-server = template client
| |
| 14:26 | If you want the ltsp server for so many uses that it's no longer an appropriate template, use a chroot or a VM for the server
| |
| 14:27 | <aheyde> chroot is likely preferable
| |
| 14:27 | <alkisg> One can build ltsp chroots using `ltsp-build-client`
| |
| 14:27 | <aheyde> So I tried that and ended back with thin client only
| |
| 14:27 | <alkisg> Ofcourse chroots have a lot issues, like services and installations failing
| |
| 14:27 | You can then apt install ubuntu-mate-desktop or whatever environment you like
| |
| 14:28 | <aheyde> Fantastic - so it really that simple
| |
| 14:28 | <alkisg> Yeah, as long as you don't have issues with chroots, ltsp works fine with them
| |
| 14:28 | <aheyde> just follow the "old instructions" of building the chroot
| |
| 14:28 | perhaps I misssed something - but how does that fit with all the ltsp specific things?
| |
| 14:29 | ie. mounting root over sshfs etc etc
| |
| 14:30 | either way, I will experiment and see how far i get
| |
| 14:31 | to be clear, you refer to 'ltsp-build-client'
| |
| 14:31 | then use ltsp-chroot to enter it and customise packages etc
| |
| 14:31 | then use ltsp-build-image to create image of said chroot
| |
| 14:34 | <alkisg> ltsp-build-image doesn't exist, it's ltsp-update-image
| |
| 14:34 | But yeah what you said
| |
| 14:34 | <aheyde> my mistake, I meant ltsp-update-image
| |
| 14:34 | <alkisg> Note that the chroot isn't used at all after ltsp-update-image, i.e. you're using the server, logging in to the server, using the server's /home etc
| |
| 14:35 | You can also just use a vbox .vdi image instead of a chroot, no difference, ltsp just needs a template
| |
| 14:36 | <aheyde> i'm using the chroot for now
| |
| 14:36 | yes, I understand it is only to build the squashfs image
| |
| 14:36 | Long term I will likely use docker for build convenience
| |
| 14:39 | is there really anything that custom in the rootfs for fat clients? given lts.conf is via tftp and most other things are dynamic, I'm assuming i can build generic squashfs images which may be used in multiple ltsp systems?
| |
| 14:40 | <alkisg> Yes; you only need the ltsp-client package on them
| |
| 14:41 | <aheyde> that is fantastic
| |
| 14:41 | so should be easy to provide pxe boot menus with different desktops for example
| |
| 14:41 | <alkisg> Sure
| |
| 14:42 | Or youcould have them all in one image, and the users can select the DE on login, as it's normal
| |
| 14:43 | <aheyde> Yes, that is always an option. I like the idea of having a standard desktop image, with the option of adding a newer/different one along side it for testing or for a small group of specialised users etc
| |
| 14:44 | With the theme being that different desktop images can be released at different times - decoupling
| |
| 14:44 | <alkisg> I have 10 images in my pxe menu
| |
| 14:49 | lucas__ has joined IRC (lucas__!~lucas@177-185-141-105.isotelco.net.br) | |
| 14:49 | lucascastro has left IRC (lucascastro!~lucas@177-185-141-105.isotelco.net.br, Read error: Connection reset by peer) | |
| 14:52 | aheyde has left IRC (aheyde!~aheyde@2001:44b8:311a:af05:69b8:942d:32e5:66a3, Remote host closed the connection) | |
| 15:33 | vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc) | |
| 17:21 | lucas__ has left IRC (lucas__!~lucas@177-185-141-105.isotelco.net.br, Remote host closed the connection) | |
| 19:00 | Statler_Office has left IRC (Statler_Office!~Georg@gwrz3.lohn24.de, Remote host closed the connection) | |
| 20:27 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |
| 20:37 | Faith has left IRC (Faith!~Paty_@unaffiliated/faith, Quit: Leaving) | |
| 21:24 | bcg has left IRC (bcg!~b@2001:2003:54f9:42f6::1, Ping timeout: 246 seconds) | |
| 21:25 | GodFather has left IRC (GodFather!~rcc@174-081-217-069.dhcp.chtrptr.net, Ping timeout: 264 seconds) | |
| 21:32 | bcg has joined IRC (bcg!~b@2001:2003:54f9:42f6::1) | |
| 21:38 | GodFather has joined IRC (GodFather!~rcc@174-081-217-069.dhcp.chtrptr.net) | |
| 21:59 | ben_roose has left IRC (ben_roose!~roose@roose.cs.wichita.edu, Remote host closed the connection) | |
| 22:51 | GodFather has left IRC (GodFather!~rcc@174-081-217-069.dhcp.chtrptr.net, Ping timeout: 255 seconds) | |
| 23:23 | gbaman has joined IRC (gbaman!~gbaman@52.178.202.64) | |
| 23:45 | ||cw has left IRC (||cw!~chrisw@unaffiliated/cw/x-1182934, Quit: Do not follow the null pointer, for therein lies ma&^%#___) | |