IRC chat logs for #ltsp on irc.freenode.net (webchat)


Channel log from 22 May 2018   (all times are UTC)

00:00gbaman has joined IRC (gbaman!~gbaman@cpc104700-belf11-2-0-cust917.2-1.cable.virginm.net)
00:09GodFather has left IRC (GodFather!~rcc@174-081-217-069.dhcp.chtrptr.net, Ping timeout: 260 seconds)
01:34gbaman has left IRC (gbaman!~gbaman@cpc104700-belf11-2-0-cust917.2-1.cable.virginm.net, Remote host closed the connection)
01:35gbaman has joined IRC (gbaman!~gbaman@cpc104700-belf11-2-0-cust917.2-1.cable.virginm.net)
01:39gbaman has left IRC (gbaman!~gbaman@cpc104700-belf11-2-0-cust917.2-1.cable.virginm.net, Ping timeout: 252 seconds)
03:30kjackal has left IRC (kjackal!~quassel@2a02:587:3102:4300:b0a9:f5fb:bb3d:7a34, Ping timeout: 245 seconds)
03:30kjackal has joined IRC (kjackal!~quassel@athedsl-238683.home.otenet.gr)
04:07gbaman has joined IRC (gbaman!~gbaman@cpc104700-belf11-2-0-cust917.2-1.cable.virginm.net)
05:13gbaman has left IRC (gbaman!~gbaman@cpc104700-belf11-2-0-cust917.2-1.cable.virginm.net, Ping timeout: 248 seconds)
05:14
<alkisg>
vlt: KEEP_SYSTEM_SERVICES=ssh, and put the keys in /etc/ltsp/ltsp-update-image.excludes
05:31Statler|Home has joined IRC (Statler|Home!~Georg@p5B30E80B.dip0.t-ipconnect.de)
05:46gbaman has joined IRC (gbaman!~gbaman@cpc104700-belf11-2-0-cust917.2-1.cable.virginm.net)
06:21wim1 has joined IRC (wim1!~Thunderbi@WEGC33.UNI-GRAZ.AT)
06:23ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
06:23wim1 has left IRC (wim1!~Thunderbi@WEGC33.UNI-GRAZ.AT, Client Quit)
06:27wim1 has joined IRC (wim1!~Thunderbi@WEGC33.UNI-GRAZ.AT)
06:29wim1 has joined IRC (wim1!~Thunderbi@WEGC33.UNI-GRAZ.AT)
07:16
<vlt>
alkisg: :-* :-* :-*
07:16
<alkisg>
:)
08:25Statler has joined IRC (Statler!~Georg@p5B30E388.dip0.t-ipconnect.de)
08:27Statler|Home has left IRC (Statler|Home!~Georg@p5B30E80B.dip0.t-ipconnect.de, Ping timeout: 260 seconds)
09:12Statler has left IRC (Statler!~Georg@p5B30E388.dip0.t-ipconnect.de, Remote host closed the connection)
10:03derick_ has joined IRC (derick_!b6468ea3@gateway/web/freenode/ip.182.70.142.163)
10:09
<derick_>
Will someone please explain me why ltsp-build-client is not used in instruction on https://help.ubuntu.com/community/UbuntuLTSP/ltsp-pnp
10:50gdi2k has joined IRC (gdi2k!~gdi2k@112.208.187.161)
11:09gdi2k has left IRC (gdi2k!~gdi2k@112.208.187.161, Read error: Connection reset by peer)
11:14gvy has joined IRC (gvy!~mike@altlinux/developer/mike)
11:15Statler_Office has joined IRC (Statler_Office!~Georg@gwrz3.lohn24.de)
11:27gbaman has left IRC (gbaman!~gbaman@cpc104700-belf11-2-0-cust917.2-1.cable.virginm.net, Remote host closed the connection)
11:27gbaman has joined IRC (gbaman!~gbaman@cpc104700-belf11-2-0-cust917.2-1.cable.virginm.net)
11:42
<vlt>
derick_: I guess becase no client is built in -pnp mode. Afaik, the client uses the host's root fs or something like that.
11:43Faith has joined IRC (Faith!~Paty_@unaffiliated/faith)
11:50gbaman has left IRC (gbaman!~gbaman@cpc104700-belf11-2-0-cust917.2-1.cable.virginm.net, Remote host closed the connection)
11:58gbaman has joined IRC (gbaman!~gbaman@cpc104700-belf11-2-0-cust917.2-1.cable.virginm.net)
12:14gbaman has left IRC (gbaman!~gbaman@cpc104700-belf11-2-0-cust917.2-1.cable.virginm.net, Remote host closed the connection)
12:14GodFather has joined IRC (GodFather!~rcc@96-92-43-9-static.hfc.comcastbusiness.net)
12:25
<derick_>
vlt_: thanks :) yes, you are right!
12:28gbaman has joined IRC (gbaman!~gbaman@cpc104700-belf11-2-0-cust917.2-1.cable.virginm.net)
12:33gbaman has left IRC (gbaman!~gbaman@cpc104700-belf11-2-0-cust917.2-1.cable.virginm.net, Ping timeout: 264 seconds)
12:43gdi2k has joined IRC (gdi2k!~gdi2k@112.208.187.161)
13:29maciel_ has joined IRC (maciel_!8300c154@gateway/web/freenode/ip.131.0.193.84)
13:30
<maciel_>
Hello, the possibility of putting to use Ltsp protocol to run windows remotely?
13:33ben_roose has joined IRC (ben_roose!~roose@roose.cs.wichita.edu)
13:37
<alkisg>
maciel_: you can run ltsp with linux, and run virtualbox + windows on top of it
13:37
or with remote desktop with xfreerdp
13:45wim1 has left IRC (wim1!~Thunderbi@WEGC33.UNI-GRAZ.AT, Quit: wim1)
13:49
<maciel_>
with virtualbox could very machine performance
14:15
<alkisg>
yes, it can
14:35Statler_Office has left IRC (Statler_Office!~Georg@gwrz3.lohn24.de, Remote host closed the connection)
15:01derick_ has left IRC (derick_!b6468ea3@gateway/web/freenode/ip.182.70.142.163, Ping timeout: 260 seconds)
15:13maciel_ has left IRC (maciel_!8300c154@gateway/web/freenode/ip.131.0.193.84)
15:20gbaman has joined IRC (gbaman!~gbaman@85.255.233.84)
15:27derick_ has joined IRC (derick_!b6468ea3@gateway/web/freenode/ip.182.70.142.163)
15:30gbaman_ has joined IRC (gbaman_!~gbaman@94.119.64.21)
15:34gbaman has left IRC (gbaman!~gbaman@85.255.233.84, Ping timeout: 256 seconds)
16:01gbaman has joined IRC (gbaman!~gbaman@188.28.147.96.threembb.co.uk)
16:02gbaman__ has joined IRC (gbaman__!~gbaman@94.196.94.124.threembb.co.uk)
16:04gbaman_ has left IRC (gbaman_!~gbaman@94.119.64.21, Ping timeout: 252 seconds)
16:05gbaman has left IRC (gbaman!~gbaman@188.28.147.96.threembb.co.uk, Ping timeout: 260 seconds)
16:07GodFather has left IRC (GodFather!~rcc@96-92-43-9-static.hfc.comcastbusiness.net, Ping timeout: 240 seconds)
16:08gbaman__ has left IRC (gbaman__!~gbaman@94.196.94.124.threembb.co.uk, Ping timeout: 256 seconds)
16:50vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
17:12gbaman has joined IRC (gbaman!~gbaman@94.196.94.124.threembb.co.uk)
17:41gbaman has left IRC (gbaman!~gbaman@94.196.94.124.threembb.co.uk, Remote host closed the connection)
17:41gbaman has joined IRC (gbaman!~gbaman@94.196.94.124.threembb.co.uk)
17:44lucascastro has left IRC (lucascastro!~lucas@177-185-141-105.isotelco.net.br, Remote host closed the connection)
17:47GodFather has joined IRC (GodFather!~rcc@2600:1007:b008:5c91:3458:e043:a206:11e4)
17:50alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Ping timeout: 248 seconds)
17:51alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
18:05lucascastro has joined IRC (lucascastro!~lucas@177-185-141-105.isotelco.net.br)
18:08derick_ has left IRC (derick_!b6468ea3@gateway/web/freenode/ip.182.70.142.163, Ping timeout: 260 seconds)
18:09lucascastro has left IRC (lucascastro!~lucas@177-185-141-105.isotelco.net.br, Client Quit)
18:30danboid has joined IRC (danboid!~dan@cpc126962-macc4-2-0-cust227.1-3.cable.virginm.net)
18:31
<danboid>
LTSP newb here, just about to set up my first test server. I presume LTSP servers are Linux only ie I can't run it under FreeBSD?
18:32lucascastro has joined IRC (lucascastro!~lucas@201.182.221.154)
18:32
<vagrantc>
danboid: it's probably not impossible to run on FreeBSD servers ... but i wouldn't recommend trying it for your first LTSP install
18:33
<||cw>
it would require a lot of porting. in fact anything but ubuntu 16.04 is going to take some work.
18:33
<vagrantc>
i've done some ltsp-like things with pcbsd or dragonflybsd years and years ago
18:34
<danboid>
Ah! I was just about to install it under Ubutu server 18.04 but yiu say 16.04 is a better choice?
18:34
<vagrantc>
debian should work fine, too
18:35
<danboid>
So it doesn't actually depend on any Linux kernel specific features then?
18:35gvy has left IRC (gvy!~mike@altlinux/developer/mike, Quit: Leaving)
18:35
<vagrantc>
danboid: it's pretty linux-specific, but you could *possibly* host LTSP images on a freebsd server, if you really wanted to and had a lot of time and patience
18:35
<||cw>
16.04 with ltsp-manager is easiest. from there you can dig into how it works
18:36
<danboid>
Is it known to have issues under 18.04?
18:36
or has no-one tried it yet?
18:36
<vagrantc>
i don't think newer versions of ubuntu have active maintainers
18:36
<||cw>
it was pre-release. I don't know if anyone has been submitting patches for 18.04
18:36
<vagrantc>
debian's been the only distro with new upstream LTSP releases for several years...
18:37
<||cw>
17.10 the OS had some changes that broke ltsp
18:37
<danboid>
16.04 or Debian it is then
18:37
<vagrantc>
says the debian LTSP maintainer...
18:37
that said, even i haven't really had a real-world LTSP install for quite a long time, so it hasn't gotten the rigorous testing it deserves...
18:38
<danboid>
Is there any reason I may want to choose Debian 9 over 16.04 or vice versa other than personal pref?
18:40
<vagrantc>
16.04 has some newer PPA packages available ... i think.
18:40gbaman has left IRC (gbaman!~gbaman@94.196.94.124.threembb.co.uk, Remote host closed the connection)
18:41
<danboid>
OK, 16.04 sounds like the easiest/best bet
18:42
Did I read on the website mentions it can host Windows too?
18:42
<vagrantc>
there are RDP clients that can connect to windows servers...
18:43
if your server supports RDP
18:43
it's basically just a network-booted operating system ... it can generally do anything a typical distribution can do
18:44
<danboid>
On the ltsp.org main page it says:
18:44
LTSP workstations can run applications from Linux and Windows servers.
18:44
Oh yes
18:45
I misread that :)
18:45
LTSP CLIENTS...
18:47
So you can probabably boot WinRE or something like Haiku over LTSP
18:47
<vagrantc>
no
18:48
you can basically boot a linux distribution as an LTSP client.
18:48
that can connect to other servers supporting various protocols ... e.g. X, RDP, VNC, etc.
18:49
LTSP isn't a protocol so much as a network booted operating system
18:50
i've experimented with using Debian GNU/kFreeBSD for an LTSP client a long time ago, too ... but never got too far ... there are a lot of linux assumptions
18:52
<danboid>
So only Linux distros are supported on the clients too then?
18:53
I presume I can boot 18.04 on the clients
18:54
<vagrantc>
danboid: let's start over :)
18:55
danboid: typically, you install a Linux distro (Ubuntu, Debian, etc.) and build an LTSP image from the same distro, and network boot that LTSP image.
18:56
danboid: once you've booted a client to LTSP, it can run a desktop locally, or run your desktop on the server, or run clients such as RDP to connect to windows, or VNC, etc.
18:57
the LTSP server serves up the LTSP client image over NBD (or NFS, or AoE, or ...)
18:58
the LTSP server may also allow LTSP clients to connect to it and run a desktop on the server.
18:58
hopefully that clarifies things...
19:00
the server could host the LTSP image if it supports NBD/NFS/AoE and tftp ... but the OS the LTSP clients are running is whatever Linux distro you used to build the LTSP images
19:01
but maybe that last part is too much :)
19:02
<danboid>
How do you create an LTSP image?
19:02
Just a rough overview
19:03
That might explain what my choices for client OS are
19:03
<vagrantc>
manually?
19:03
!ltsp-manager
19:03
<ltsp>
ltsp-manager: LTSP Manager is a GUI tool that makes LTSP maintenance easy. It's the recommended way to install LTSP in common setups. More info: http://wiki.ltsp.org/wiki/Ltsp-manager
19:03
<vagrantc>
that'd be the recommended way
19:03
<danboid>
I'd install that on the machine to be imaged?
19:03
<vagrantc>
but basically comes down to: install your OS with all the applications you want available to the client, and run "ltsp-update-image -c /"
19:04
it builds the image out of the installed OS
19:04
<danboid>
Is ltsp-update-image a C app or shell script or?
19:04
<vagrantc>
there's an older method which builds an image in a chroot, using ltsp-build-client
19:05
danboid: https://code.launchpad.net/~ltsp-upstream/ltsp/+git/ltsp/+ref/master
19:05
<danboid>
Does ltsp-update-image strip out browser/bash cache etc?
19:06
<vagrantc>
it excludes the homedirs and a few other things
19:09
<danboid>
Cool. This will be fun :)
19:09
<vagrantc>
i would strongly recommend doing a "normal" install before wandering off into uncharted territory :)
19:09
<danboid>
vagrantc, Of course! :)
19:10
<vagrantc>
not sure what broke in recent versions of ubuntu
19:10
<danboid>
BTW I never saw the point of Deb/kfreebsd. The only reason I run FreeBSD on my NAS is coz ZFS. If kfreebsd doesn't let me install to ZFS its dead to me
19:11
<vagrantc>
looks like ubuntu's now syncing from debian again ...
19:11
<||cw>
ubuntu lets you install zfs. I've been using it a while
19:11
<vagrantc>
danboid: i think it's possible to install zfs
19:12
<||cw>
doing a new zrep backup config right now
19:12
<vagrantc>
danboid: i think the biggest benefit to debian, and the free software community as a whole, has been to dig out bugs about operating system assumptions ...
19:13
<danboid>
Not without jumping through a shitload of hoops.I install zfs-dkms under Ubuntu to use my external ZFS drives but to install Ubuntu on a ZFS root drive is tricky
19:13
vagrantc, Yes, that's nice I suppose
19:13
<||cw>
oh, yeah, I still do ext4 roots
19:14
<vagrantc>
sure, zfs support on debian is probably similar, it's in the "contrib" part of the repository
19:14gbaman has joined IRC (gbaman!~gbaman@94.196.94.124.threembb.co.uk)
19:14
<vagrantc>
which is technically not part of debian
19:15
<||cw>
but ext4 on raid1 for a root is just fine, and super easy to do recovery on
19:15
<danboid>
I had no idea Vagrant was a name. I thought you were a big fan of the app until I looked at github and saw that is your name
19:16
<vagrantc>
my choice of name predates the software :)
19:16
<danboid>
Haha :D
19:17
<vagrantc>
https://bugs.debian.org/859253
19:18gbaman has left IRC (gbaman!~gbaman@94.196.94.124.threembb.co.uk, Ping timeout: 260 seconds)
19:18
<danboid>
That's great! Could be the only time someone has had to file a bug for their name with a distro?
19:19* vagrantc is suprised the bug is still open
19:19
<vagrantc>
kind of doesn't speak well to the quality of maintenance for that package...
19:21
mostly it's just funny, though i have had occasional conversations where it's been confused
19:30GodFather has left IRC (GodFather!~rcc@2600:1007:b008:5c91:3458:e043:a206:11e4, Read error: No route to host)
19:48GodFather has joined IRC (GodFather!~rcc@2600:1007:b008:5c91:3458:e043:a206:11e4)
19:51gbaman has joined IRC (gbaman!~gbaman@94.196.94.124.threembb.co.uk)
19:55gbaman has left IRC (gbaman!~gbaman@94.196.94.124.threembb.co.uk, Ping timeout: 245 seconds)
19:59gbaman has joined IRC (gbaman!~gbaman@94.196.94.124.threembb.co.uk)
20:07
<alkisg>
danboid: ltsp has some issues with recent systemd releases, in all distros. They're not there in 16.04, so yeah for first test go for that.
20:08
E.g. "clients won't shut down" or "dns not working on the clients"...
20:13lucascastro has left IRC (lucascastro!~lucas@201.182.221.154, Remote host closed the connection)
20:15
<danboid>
alkisg, OK, thanks
20:30kjackal has left IRC (kjackal!~quassel@athedsl-238683.home.otenet.gr, Ping timeout: 245 seconds)
20:35lucascastro has joined IRC (lucascastro!~lucas@177-185-141-105.isotelco.net.br)
20:35ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
20:38Faith has left IRC (Faith!~Paty_@unaffiliated/faith, Quit: Leaving)
20:54gbaman has left IRC (gbaman!~gbaman@94.196.94.124.threembb.co.uk, Ping timeout: 252 seconds)
21:09GodFather has left IRC (GodFather!~rcc@2600:1007:b008:5c91:3458:e043:a206:11e4, Read error: No route to host)
21:12gbaman has joined IRC (gbaman!~gbaman@188.28.153.199.threembb.co.uk)
21:20gbaman has left IRC (gbaman!~gbaman@188.28.153.199.threembb.co.uk, Ping timeout: 260 seconds)
21:32GodFather has joined IRC (GodFather!~rcc@174-081-217-069.dhcp.chtrptr.net)
21:55ben_roose has left IRC (ben_roose!~roose@roose.cs.wichita.edu, Remote host closed the connection)
22:03danboid has left IRC (danboid!~dan@cpc126962-macc4-2-0-cust227.1-3.cable.virginm.net, Ping timeout: 260 seconds)
22:19gbaman has joined IRC (gbaman!~gbaman@188.28.153.199.threembb.co.uk)
22:30
<sutula>
epoptes-client question: What's the chance I can install/run the epoptes-client package on non-LTSP clients and get it to more-or-less work?
22:30
Why? Well, it'd be great to install on mythtv-frontend systems and be able to shut down those systems remotely.
22:31
Even better if I could see what they were doing before shutting them down, but I probably ask too much.
22:32
<vagrantc>
sutula: it's supposed to work to n non-ltsp clients
22:32
http://www.epoptes.org/
22:33
"It can be installed in Ubuntu, Debian and openSUSE based labs that may contain any combination of the following: LTSP servers, thin and fat clients, non LTSP servers, standalone workstations, NX or XDMCP clients etc. Patches for other distros are welcome."
22:33
<sutula>
vagrantc: Very cool then...worth a try!
22:49vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
23:07GodFather has left IRC (GodFather!~rcc@174-081-217-069.dhcp.chtrptr.net, Remote host closed the connection)
23:18gdi2k has left IRC (gdi2k!~gdi2k@112.208.187.161, Read error: Connection reset by peer)
23:26gbaman has left IRC (gbaman!~gbaman@188.28.153.199.threembb.co.uk, Remote host closed the connection)