IRC chat logs for #ltsp on irc.libera.chat (webchat)
Channel log from 31 July 2018 (all times are UTC)
| 01:06 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving) | |
| 01:18 | adrianor1 has joined IRC (adrianor1!~adrianorg@177.134.63.23) | |
| 01:22 | adrianorg has left IRC (adrianorg!~adrianorg@177.156.224.77, Ping timeout: 256 seconds) | |
| 02:22 | vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc) | |
| 04:19 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving) | |
| 05:32 | Statler|Home has joined IRC (Statler|Home!~Georg@p5B30E888.dip0.t-ipconnect.de) | |
| 05:33 | ricotz has joined IRC (ricotz!~ricotz@p5B2A86D4.dip0.t-ipconnect.de) | |
| 05:33 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
| 05:57 | vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc) | |
| 06:23 | kjackal has left IRC (kjackal!~quassel@ppp-94-66-220-238.home.otenet.gr, Ping timeout: 240 seconds) | |
| 06:52 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Ping timeout: 256 seconds) | |
| 06:56 | kjackal has joined IRC (kjackal!~quassel@2a02:587:7925:c200:c084:b71:6ad4:3523) | |
| 07:09 | lucascastro has left IRC (lucascastro!~lucas@177-185-139-236.isotelco.net.br, Remote host closed the connection) | |
| 07:29 | Statler|Home has left IRC (Statler|Home!~Georg@p5B30E888.dip0.t-ipconnect.de, Remote host closed the connection) | |
| 07:44 | Leolo_2 has left IRC (Leolo_2!~fil@24-54-27-253.mg.cgocable.ca, Ping timeout: 260 seconds) | |
| 08:33 | adrianor1 has left IRC (adrianor1!~adrianorg@177.134.63.23, Ping timeout: 240 seconds) | |
| 08:34 | adrianorg has joined IRC (adrianorg!~adrianorg@177.134.63.23) | |
| 09:27 | vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc) | |
| 09:56 | zama has left IRC (zama!~zama@unaffiliated/stryx/x-3871776, Ping timeout: 260 seconds) | |
| 09:57 | zama has joined IRC (zama!~zama@unaffiliated/stryx/x-3871776) | |
| 10:10 | zama_ has joined IRC (zama_!~zama@81.4.123.134) | |
| 10:11 | zama has left IRC (zama!~zama@unaffiliated/stryx/x-3871776, Remote host closed the connection) | |
| 10:21 | zama_ has left IRC (zama_!~zama@81.4.123.134, Changing host) | |
| 10:21 | zama_ has joined IRC (zama_!~zama@unaffiliated/stryx/x-3871776) | |
| 10:21 | zama_ is now known as zama | |
| 10:30 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving) | |
| 11:13 | GodFather has joined IRC (GodFather!~rcc@96-92-43-9-static.hfc.comcastbusiness.net) | |
| 11:19 | kjackal has left IRC (kjackal!~quassel@2a02:587:7925:c200:c084:b71:6ad4:3523, Ping timeout: 256 seconds) | |
| 11:34 | GodFather has left IRC (GodFather!~rcc@96-92-43-9-static.hfc.comcastbusiness.net, Ping timeout: 256 seconds) | |
| 11:51 | kjackal has joined IRC (kjackal!~quassel@ppp-94-66-220-22.home.otenet.gr) | |
| 12:28 | vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc) | |
| 13:17 | derick_ has joined IRC (derick_!b646c217@gateway/web/freenode/ip.182.70.194.23) | |
| 13:25 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving) | |
| 13:36 | lucascastro has joined IRC (lucascastro!~lucas@177-185-139-236.isotelco.net.br) | |
| 13:41 | ben_roose has joined IRC (ben_roose!~roose@roose.cs.wichita.edu) | |
| 13:53 | talmid has joined IRC (talmid!~talmid@saphar.net) | |
| 15:03 | derick_ has left IRC (derick_!b646c217@gateway/web/freenode/ip.182.70.194.23, Ping timeout: 252 seconds) | |
| 16:22 | professor^LE-87E has joined IRC (professor^LE-87E!c8c90329@gateway/web/freenode/ip.200.201.3.41) | |
| 16:24 | lucascastro has left IRC (lucascastro!~lucas@177-185-139-236.isotelco.net.br, Remote host closed the connection) | |
| 18:11 | derick_ has joined IRC (derick_!b6469567@gateway/web/freenode/ip.182.70.149.103) | |
| 18:12 | <derick_> if ltsp server is providing dhcp services. what can be done to avoid its services to conflict when dhcp services of router?
| |
| 18:14 | <||cw> derick_: only if it's on its own network
| |
| 18:14 | as in the 2 interfaces examples
| |
| 18:15 | otherwise, configure your router to hand out the PXE related options instead, or turn off your router's dhcp
| |
| 18:16 | or maybe use proxydhcp on the ltsp
| |
| 18:16 | https://help.ubuntu.com/community/UbuntuLTSP/ProxyDHCP
| |
| 18:17 | hm, that might be old, but should be similar
| |
| 18:18 | <derick_> okay. So if the second interface is in different network(when router is as well), And first interface in network where ltsp is providing dhcp services.
| |
| 18:18 | The setup will work?
| |
| 18:19 | <||cw> yeah. though http://wiki.ltsp.org/wiki/Installation/Ubuntu implies proxy should work out of the box
| |
| 18:21 | <derick_> cool. One more question. what is chrootless? I read the docs but I did not understood it.
| |
| 18:21 | I mean in both setup image is created. That is used by ltsp client to boot from.
| |
| 18:21 | <||cw> it builds image from the server's root, excluding and modifying files as needed on the fly
| |
| 18:22 | great for a mixed fat/thin env as it leave both the same with only one OS install to manage
| |
| 18:25 | <derick_> okay nice. But see in Installing LTSP in "chroot" mode we use `ltsp-build-client` to create image.
| |
| 18:25 | In Installing LTSP in "chrootless" we use `ltsp-update-image --cleanup /` to again create the image.
| |
| 18:26 | what is the difference then?
| |
| 18:28 | <||cw> once you have a chroot configured, you also only use ltsp-update-image ot make a new image from it
| |
| 18:29 | <derick_> And we cannot do that in `chrootless`. Okay. Wow. thanks for clearing me doubt :)
| |
| 18:30 | <||cw> ?
| |
| 18:30 | no
| |
| 18:31 | ltsp-update-image make a new image from a source, chrot or root doesn't matter
| |
| 18:31 | ltsp-build-client make a a new chroot from nothing
| |
| 18:32 | <derick_> ohh. okay.
| |
| 18:32 | <||cw> you only run ltsp-build-client once ever, typically
| |
| 18:38 | derick_ has left IRC (derick_!b6469567@gateway/web/freenode/ip.182.70.149.103, Ping timeout: 252 seconds) | |
| 18:49 | derick_ has joined IRC (derick_!ab3c8454@gateway/web/freenode/ip.171.60.132.84) | |
| 18:49 | <derick_> Okay. Thanks for all the information.
| |
| 19:01 | Statler|Home has joined IRC (Statler|Home!~Georg@p5B30E888.dip0.t-ipconnect.de) | |
| 19:34 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |
| 19:41 | Statler|Home has left IRC (Statler|Home!~Georg@p5B30E888.dip0.t-ipconnect.de, Remote host closed the connection) | |
| 19:41 | GodFather has joined IRC (GodFather!~rcc@174-081-217-069.dhcp.chtrptr.net) | |
| 19:48 | Statler|Home has joined IRC (Statler|Home!~Georg@p5B30E888.dip0.t-ipconnect.de) | |
| 19:49 | <derick_> I have created a 2 interface non proxy ltsp setup. But internet does not work on the clients.
| |
| 19:50 | <||cw> if they are fat clients, you need to make your server a router as well.
| |
| 19:50 | which might be as simple as enabling ip fwd and setup up an appropriate static route on your router
| |
| 19:51 | 2-interface is more common for thin clients.
| |
| 19:53 | <derick_> okay. I will enable ip fwd.
| |
| 19:57 | <||cw> don't forget the routes. otherwise nothing will know how to get back
| |
| 19:58 | honestly, going single interface and not using the router's DHCP is the best thing in the world. bonus is you get a proper DNS server on your lan
| |
| 20:07 | talmid has left IRC (talmid!~talmid@saphar.net, Quit: Leaving) | |
| 20:29 | Statler|Home has left IRC (Statler|Home!~Georg@p5B30E888.dip0.t-ipconnect.de, Remote host closed the connection) | |
| 21:16 | adrianorg has left IRC (adrianorg!~adrianorg@177.134.63.23, Ping timeout: 264 seconds) | |
| 21:49 | adrianorg has joined IRC (adrianorg!~adrianorg@177.134.63.23) | |
| 21:55 | derick_ has left IRC (derick_!ab3c8454@gateway/web/freenode/ip.171.60.132.84, Ping timeout: 252 seconds) | |
| 22:53 | ben_roose has left IRC (ben_roose!~roose@roose.cs.wichita.edu, Remote host closed the connection) | |