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


Channel log from 25 April 2019   (all times are UTC)

05:26ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
05:31woernie has joined IRC (woernie!~werner@pD9E8BADB.dip0.t-ipconnect.de)
05:35ricotz_ has joined IRC (ricotz_!~ricotz@ubuntu/member/ricotz)
05:38ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Ping timeout: 250 seconds)
06:07spaced0ut has left IRC (spaced0ut!~spaced0ut@unaffiliated/spaced0ut, Ping timeout: 245 seconds)
07:09ricotz_ is now known as ricotz
07:11Basinator has joined IRC (Basinator!511476ce@gateway/web/freenode/ip.81.20.118.206)
07:11
<Basinator>
Will I be able to use my current thinclient config in future versions or not anymore?
07:25statler has joined IRC (statler!~Georg@gwrz.lohn24.de)
07:32kjackal has joined IRC (kjackal!~quassel@ppp-94-65-205-52.home.otenet.gr)
08:37
<alkisg>
Basinator: no, distributions don't support 32bit anymore
08:38
You need to stay with older versions that support 32 bit
08:44gdi2k has joined IRC (gdi2k!~gdi2k@58.69.160.27)
08:48
<Basinator>
But would 64 bit thin clients still work?
08:48
<alkisg>
Why would you run 64bit clients as thin clients?
08:49
The idea is that no, they won't work unless you use vnc, rdp, x2go etc. If there's a use case where this is needed, I'd like to hear about it.
08:50
I.e. you'll be able to use ltsp to netboot clients, and then you'll be able to use vnc/rdp/x2go to make them "thin clients", i.e. remote desktop clients
08:53
Note that I'll probably have the new ltsp version, ltsp19, ready in September; so it will take a while to reach the distributions. E.g. it's possible that Ubuntu 20.04 will ship with the old LTSP.
09:02
(I may even deliberately do that, so that 20.04 users have both ltsp options, either with or without the ppa)
09:07
<highvoltage>
aaiimmss
09:07gdi2k has left IRC (gdi2k!~gdi2k@58.69.160.27, Read error: Connection reset by peer)
09:07
<highvoltage>
(oops)
09:41gdi2k has joined IRC (gdi2k!~gdi2k@58.69.160.28)
10:09
<alkisg>
!local-boot | echo gdi2k:
10:09
<ltsp`>
gdi2k: local-boot: If you want LTSP fat clients on a low-speed network, you can put i386.img on e.g. C:\Boot\LTSP\i386.img and use this command line in pxelinux.cfg: APPEND ro initrd=ltsp/i386/initrd.img init=/sbin/init-ltsp root=/dev/sda1 rootflags=ro loop=/Boot/LTSP/i386.img; IPAPPEND 3
10:10
<alkisg>
!ram
10:10
<ltsp`>
I do not know about 'ram', but I do know about these similar topics: 'lts-parameters', 'lowram-initramfs', 'server-ram'
10:10
<alkisg>
!RAM
10:10
<ltsp`>
I do not know about 'RAM', but I do know about these similar topics: 'lts-parameters', 'lowram-initramfs', 'server-ram'
10:19gdi2k has left IRC (gdi2k!~gdi2k@58.69.160.28, Quit: Leaving)
10:22gdi2k has joined IRC (gdi2k!~gdi2k@58.69.160.27)
10:32woernie has left IRC (woernie!~werner@pD9E8BADB.dip0.t-ipconnect.de, Remote host closed the connection)
11:06gdi2k has left IRC (gdi2k!~gdi2k@58.69.160.27, Quit: Leaving)
11:24adrianor1 has left IRC (adrianor1!~adrianorg@177.18.50.144, Ping timeout: 245 seconds)
11:44woernie has joined IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de)
12:19mmarconm has joined IRC (mmarconm!~mmarconm@unaffiliated/mmarconm)
12:56
<mwalters>
hey, alkisg: a few weeks back you had posted the name of an ldap server (it wasn't openldap or freeIPA), any chance you remember what that was?
12:57
might've not been ldap... but some form of centralized auth system
12:57
Finally circling back around to this
13:03
<Hyperbyt1>
mwalters, 389-ds perhaps?
13:17
<alkisg>
mwalters: I haven't used ldap, so I'm not sure that was me. Maybe samba?
13:24spaced0ut has joined IRC (spaced0ut!~spaced0ut@unaffiliated/spaced0ut)
13:48
<highvoltage>
haven't tried this but this might also be useful for future ltsp implementations https://drewdevault.com/2019/04/23/Using-cage-for-a-seamless-RDP-Wayland-desktop.html
14:10vsuojanen has left IRC (vsuojanen!~vsuojanen@cable-hml-585686-205.dhcp.inet.fi, Ping timeout: 268 seconds)
14:13
<mwalters>
hmm, not sure this was it, but thanks
14:40woernie has left IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de, Remote host closed the connection)
15:43Basinator has left IRC (Basinator!511476ce@gateway/web/freenode/ip.81.20.118.206, Quit: Page closed)
16:11kjackal has left IRC (kjackal!~quassel@ppp-94-65-205-52.home.otenet.gr, Ping timeout: 244 seconds)
16:11mmarconm has left IRC (mmarconm!~mmarconm@unaffiliated/mmarconm, Ping timeout: 250 seconds)
17:04josefig has left IRC (josefig!~josefig@unaffiliated/josefig, Ping timeout: 244 seconds)
17:16adrianorg has joined IRC (adrianorg!~adrianorg@186.215.20.40)
17:51woernie_ has joined IRC (woernie_!~werner@pD9E8BADB.dip0.t-ipconnect.de)
18:35statler has left IRC (statler!~Georg@gwrz.lohn24.de, Remote host closed the connection)
19:38ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Remote host closed the connection)
19:40woernie_ has left IRC (woernie_!~werner@pD9E8BADB.dip0.t-ipconnect.de, Remote host closed the connection)
20:07mgariepy has left IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy, Quit: Leaving)
20:55mads2 has joined IRC (mads2!~mads2@191.177.187.7)
22:18Sleaker has joined IRC (Sleaker!~quassel@2604:880:a:7::e1b)
22:18
<Sleaker>
alright so stretch seems to be a little different in tftp setup than my previous ubuntu setup.
22:19
I'm trying to get the tftp stuff working again, but not sure where lts.conf should actually be placed the manpage is a bit ambiguous on how the client actually looks for it
22:19
it's just in a notes section at the bottom but doesn't spell out what the deterministic path checks are
22:20
on my new system th default tfpt directory has swapped over to /srv/tftp/ so I'm using that as the root now
22:20
and I'm not server i386 images so putting the file in /var/lib/tftpboot/ltsp/i386/ seems wrong.
22:20
sering*
22:23
ahh I see getltscfg -a can check the file. looks like I do have it in the right spot I guess since it's getting pulled into /etc/lts.conf on the client
22:33
ahh I think my issue is the newer ltsp packages need ldm-server
22:34
ldminfod isn't in inetd.conf
23:41mads2 has left IRC (mads2!~mads2@191.177.187.7, Ping timeout: 244 seconds)