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


Channel log from 5 October 2018   (all times are UTC)

02:50lucascastro has joined IRC (lucascastro!~lucascast@177-185-139-186.isotelco.net.br)
04:50alkisg1 has joined IRC (alkisg1!~alkisg@ubuntu/member/alkisg)
04:52alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, *.net *.split)
05:15kjackal has joined IRC (kjackal!~quassel@2a02:587:310f:d100:c094:23fe:27e5:ab87)
05:17
<alkisg1>
Hyperbyte: yup, exactly what ||cw said
05:33kjackal has left IRC (kjackal!~quassel@2a02:587:310f:d100:c094:23fe:27e5:ab87, Ping timeout: 240 seconds)
05:59alkisg1 is now known as alkisg
06:01kjackal has joined IRC (kjackal!~quassel@2a02:587:310f:d100:c094:23fe:27e5:ab87)
06:11ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
06:58kjackal has left IRC (kjackal!~quassel@2a02:587:310f:d100:c094:23fe:27e5:ab87, Ping timeout: 252 seconds)
07:10kjackal has joined IRC (kjackal!~quassel@onopfy.static.otenet.gr)
10:44kjackal has left IRC (kjackal!~quassel@onopfy.static.otenet.gr, Ping timeout: 246 seconds)
10:56kjackal has joined IRC (kjackal!~quassel@2a02:587:310f:d100:c094:23fe:27e5:ab87)
11:47
<Hyperbyte>
:-)
11:52Faith has joined IRC (Faith!~Paty_@unaffiliated/faith)
12:36JuJUBee has joined IRC (JuJUBee!~knichel@24.148.115.153)
12:37
<JuJUBee>
I was running ltsp-update-image while my students were arriving and logging in. I received an error "FATAL ERROR:gzip uncompress failed with error code -3 mksquashfs failed to build the LTSP image, exiting" at around 20% Ideas?
12:43
<mwalters>
did you run out of space? `df -h`
12:59
<JuJUBee>
mwalters, no
12:59
not even close
13:01
I have 20G free and the image is only 4.8G
13:02
<fiesh>
when does gzip return error code -3?
13:10
<alkisg>
gzip uncompress while compressing?
13:10
That sounds at least strange :D
13:11
<JuJUBee>
agreed.
13:11
I'm at 62% this time and still going
13:11
<Hyperbyte>
alkisg, fat client newbie question! :-D
13:11
I need to edit my /etc/hosts file on all fat clients.
13:12
Currently it uses localhost as nameserver for the fat clients (?) and there's an uncommented "Generated by LTSP" line
13:12
And where I said /etc/hosts I meant /etc/resolv.conf #stopthetime
13:14
<alkisg>
Hyperbyte: HOSTS_xx in lts.conf puts lines in the clients hosts
13:14
DNS_SERVER puts the nameserver
13:14
SEARCH_DOMAIN puts the domain
13:21
<Hyperbyte>
Thanks!
13:21
So far the migration went rather easy. Especially considering I combined it with a Ubuntu 16->18 upgrade.
13:22
<JuJUBee>
This time the update-image finished without error...
13:24kjackal has left IRC (kjackal!~quassel@2a02:587:310f:d100:c094:23fe:27e5:ab87, Remote host closed the connection)
13:26kjackal has joined IRC (kjackal!~quassel@2a02:587:310f:d100:8151:6009:41b:32c6)
13:27Faith has left IRC (Faith!~Paty_@unaffiliated/faith, Remote host closed the connection)
13:27kjackal_v2 has joined IRC (kjackal_v2!~quassel@2a02:587:310f:d100:8151:6009:41b:32c6)
13:29Faith has joined IRC (Faith!~Paty_@unaffiliated/faith)
13:44
<alkisg>
JuJUBee: amd or intel cpu?
14:00
<Hyperbyte>
alkisg, DNS_SERVER is not used by the client
14:01
I see DNS_SERVER="192.168.100.1" in getltscfg -a
14:01
But it's not displayed in /etc/resolv.conf
14:01
And the "Generated by LTSP" without a # in front is still present as well, seems like a bug.
14:02
The SEARCH_DOMAIN is present by the way in /etc/resolv.conf, but the DNS_SERVER is not
14:03
Line 74 of init-ltsp.d/10-resolv.conf needs a #
14:07
The /etc/resolvconf/resolv.conf.d/base looks OK, /etc/resolv.conf does not
14:09
Another bug I see with Ubuntu 18 and ltsp-pnp is that the local user is not created... when I open a terminal I see "I have no name!@ltsp213"
14:25kjackal has left IRC (kjackal!~quassel@2a02:587:310f:d100:8151:6009:41b:32c6, Remote host closed the connection)
14:47vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
14:52BuddyButterfly has joined IRC (BuddyButterfly!~BuddyButt@h2216388.stratoserver.net)
14:52
<BuddyButterfly>
hi
14:52
is it possible to have some kind of "detached" client?
14:53
What I mean is, if someone uses a fat client, is it possible to online copy the image and make the client standalone?
14:58
<Hyperbyte>
Hrm... the user bug seems gone now. Strange.
14:58
<vagrantc>
it's possible, although you'd have to make some sort of local authentication and home directory handling (which is usually mounted from the server)
15:02
<Hyperbyte>
And the user bug is back. Seems like when I'm logged in for a little bit, the local user disappears?
15:05
alkisg, vagrantc, any of you wanna help me debug some ltsp-pnp issues on Ubuntu 18?
15:13
<vagrantc>
don't have much time this morning
15:13
Hyperbyte: sounds very curious, though
15:17
<Hyperbyte>
I think it might be ldap related
15:18
<vagrantc>
that would be unsurprising :)
15:19
<Hyperbyte>
Actually it's resolv.conf related
15:19
The LDAP configuration refers to the server by DNS name
15:20
Which isn't available because LTSP doesn't make a proper resolv.conf file
15:20
So I need to fix that first. Any ideas about that?
15:24
<alkisg>
Hyperbyte: i'm here :)
15:24
:P
15:24
So, about DNS etc, it doesn't go to resolv.conf anymore normally, but to systemd
15:24
Because systemd-networkd is used
15:24
In your server, did you manually modify resolv.conf?
15:25
ls -l /etc/resolv.conf, both on server and client, what does that return?
15:25
BuddyButterfly: do you mean that the client would be able to reboot into that fat image, or just "copy the fat image to ram so that the client runs without the server until reboot"?
15:26
<BuddyButterfly>
alkisg: hi, nice to meet you agn. Yes, boot into the new image. A boot menu like (boot fat client, install new fat client image, boot local fat client) would be cool ;-)
15:27
<alkisg>
BuddyButterfly: it shouldn't be hard, essentially you'd need to create partitions, copy the image, install grub
15:27
But the code for that isn't there, someone would need to write it, however small it might be
15:28
<BuddyButterfly>
alkisg: yes, true. I came to this question because lately the server crashed with clients online.
15:28
Though, they were able to run on... but only till restart ;-)
15:28
<alkisg>
They would run, but they wouldn't be able to save things :)
15:29
<BuddyButterfly>
so, if the server will have some longer downtime because of emergency repair, etc. this would be a cool feature.
15:29
<alkisg>
Where would /home be?
15:29
If everything is on the client, what is the server needed for?
15:29
Then it's just local installations
15:29
"Magic" like "keep the clients running until the server comes back" isn't at all easy to implement
15:29
<BuddyButterfly>
server would then be kind of providing latest image, like checking if client has got latest image.
15:30
<alkisg>
Sure, that can be done somewhat easily
15:30
<BuddyButterfly>
not really local installation. it is like centrally managed installation with a mirrored/clustered home, etc.
15:30
<alkisg>
It's really local installations, just periodically synced from a master image
15:30
Mirrored /home? Now you're making it hard again :)
15:31
<BuddyButterfly>
alkisg: you are maybe right because automatically switching to server if available would be kind of complicated.
15:31
<alkisg>
!local-boot
15:31
<ltsp>
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
15:31
<alkisg>
This is the first step, putting the image locally
15:32
And an appropriate lts.conf would create a local user and mount the local home
15:32
But forget all the "autosyncing /home" stuff, it would be very complicated
15:32
E.g. about 6 months of work to make it right
15:33
<BuddyButterfly>
alkisg: yeah, I guess so. But thanks for indicating. This is also important. Hmm, I will have a look into this local-boot.
15:33
<Hyperbyte>
alkisg, I did manually edit resolv.conf.
15:33
<alkisg>
Hyperbyte: can you paste the output of those commands?
15:33
<Hyperbyte>
resolv.conf exists on both server and client.
15:33
<BuddyButterfly>
I also have to go back to basics and learn howto build and manage different images/systems. I only run a single system which is provided.
15:34
<Hyperbyte>
Should I add resolv.conf to ltsp-update-image.excludes?
15:34
<alkisg>
(06:33:39 μμ) alkisg: Hyperbyte: can you paste the output of those commands?
15:34
<Hyperbyte>
Not really no
15:34
<alkisg>
I wouldn't know what to advice then
15:34
It depends on if it's still a symlink or not, and where to
15:35
<vagrantc>
only 6 months of work sounds like a good deal if someone wanted to fund it!
15:35
<Hyperbyte>
Both on server and client it's a symlink ro ../run/resolvconf/resolv.conf
15:35
<alkisg>
Hyperbyte: ah, you still have resolvconf due to the 16.04=>18.04 upgrade
15:35
<Hyperbyte>
I'm logged in through x2go on a virtual machine. I literally can't copy/paste.
15:35
<alkisg>
Just remove that package, and file a bug in ltsp about it in case anyone wants to bother supporting resolvconf again :D
15:36
There's "command | nc termbin.com 9999" and then typing 4 letters...
15:37
See, your input made me give the correct advice there :) It's important!
15:37
<BuddyButterfly>
Hyperbyte: Use ssh connection and then copy past from terminal.
15:37
<Hyperbyte>
alkisg, I'm not saying it's not important. :-D
15:37
BuddyButterfly, no ssh on fat clients
15:37
Sure I could figure something out, but it'd be easier to know -what- alkisg exactly wanted to know.
15:37
That's why I asked. :-P
15:37
<BuddyButterfly>
ah, that think. start a separate ssh daemon.
15:38
I think I also was working on that.
15:38
<Hyperbyte>
BuddyButterfly, can't, because I can't even 'su' due to LDAP problems on the client.
15:38
But I could pipe output to a file and scp that to another local server and from there scp it further.
15:38
But just telling works faster. :-P
15:39
<BuddyButterfly>
If you are a programmer, characters up to a few hundreds are typed faster anyway. that is how I do ;-)
15:40
<alkisg>
Btw, I didn't touch any code related to resolvconf, so it was still supposed to work; but I wouldn't want to dive into it if noone uses it anymore...
15:40
<BuddyButterfly>
alkisg: heard something about 18.04. Did you release it?
15:40
<Hyperbyte>
alkisg, let me guess... settings from /etc/network/interfaces are not picked up by systemd-resolver?
15:41
<alkisg>
Hyperbyte: the client /etc/network/interfaces is regenerated anyway; but if you're talking about the server, yeah, /etc/network/interfaces is pretty much deprecated now too
15:42
<Hyperbyte>
Damn.
15:42
Where do I set them? :-)
15:42
<alkisg>
BuddyButterfly: eh, I maintain a ppa that has the newest ltsp that supports 18.04
15:42
!install
15:42
<ltsp>
install: http://wiki.ltsp.org/wiki/Installation/Ubuntu for Ubuntu, or http://wiki.ltsp.org/wiki/Installation for other distributions
15:42
<Hyperbyte>
The server has fixed IP configured.
15:42
<alkisg>
Hyperbyte: go with the flow. Use network manager.
15:42
The less things you need to touch in new installations, the more stable they'll be
15:43
<BuddyButterfly>
alkisg: networkmanager in a non desktop server install?
15:44
<alkisg>
It doesn't make much sense to not have a desktop server install as an ltsp server
15:44
<BuddyButterfly>
isn't the philosphy to do it all within systemd then?
15:44
<alkisg>
LTSP servers are desktop installations basically
15:44
The philosophy is "install desktop ubuntu, touch it as little as possible"
15:45
The less tweaks, the more stable it gets
15:45
(or any other os, of course)
15:45
<BuddyButterfly>
alkisg: ok, agreed. But NetworkManager was more the cause of troubles than helped.
15:45
<alkisg>
Nah. Proof?
15:45
<Hyperbyte>
Oh I can just edit
15:45
/etc/systemd/resolved.conf
15:46
<alkisg>
There's are lots and lots of places to specify dns servers, sure
15:46
<BuddyButterfly>
nowadays you have systemd with its own network management, then networkmanager, then somehow old version via network/interfaces comes also in....
15:46
it did not make it more stable.
15:47
<alkisg>
LTSP uses /etc/systemd/resolved.conf.d/ltsp.conf
15:47
<Hyperbyte>
BuddyButterfly, I read something about netplan as well
15:48
<mwalters>
I'm using networkd w/ ltsp on my test box right now
15:48
I have no idea what's "better"
15:48
<BuddyButterfly>
In embedded system I try to do all in systemd. Config goes into /etc/systemd/network
15:49
Hyperbyte: Haven't touched this. This would add another degree of freedem:.... fun!
15:51
<alkisg>
Hyperbyte: https://git.launchpad.net/ltsp/commit/?id=8b4dd6aa9e70b0d9140f846b5974f416858d9ebe
15:51
10-resolv-conf: start comment with #, thanks Hyperbyte! :D
15:52
<Hyperbyte>
alkisg, yeees
15:52
It's now good!
15:52
<mwalters>
lolol
15:52
<Hyperbyte>
But reversed!
15:52
Before SEARCH_DOMAIN was set, but the DNS_SERVER wasn't
15:52
I removed resolvconf and now the correct DNS_SERVER is used, but SEARCH_DOMAIN isn't
15:53
Let me see...
15:53
<alkisg>
Hyperbyte: yesterday's: https://git.launchpad.net/ltsp/commit/?id=a554125b16a08527390c90ab281c085c1ee334f0
15:53
Domains, not Domain
15:53
I'll release it to the ppa within the weekend
15:53
For now, apply them manually
15:56JuJUBee has left IRC (JuJUBee!~knichel@24.148.115.153, Quit: Leaving)
15:58
<Hyperbyte>
Ok cool!
15:59
<mwalters>
alkisg: fwiw, man lts.conf shows "SEARCH_DOMAIN"
15:59
you're probably talkinga bout something else looking at the commit, though
15:59
<alkisg>
mwalters: what do you mean?
16:00
Yeah, it's about the systemd configuration, not about lts.conf
16:00
<mwalters>
yeah, nvm, you're referencing resolved, not lts.conf
16:02
<Hyperbyte>
Hehe, you do realize you're talking to the LTSP Oracle right, mwalters?
16:02
alkisg knows everything LTSP.
16:02
!alkisg
16:02
<ltsp>
alkisg: The LTSP oracle. Our beacon of hope in the world of LTSP. With the guidance of this divine emperor, we shall prevail.
16:02* Hyperbyte bows
16:03
<mwalters>
I was trying to point out a perceived type in the man, rather than saying alkisg didn't know the right name ;)
16:03
s/type/typo
16:04* vagrantc probably knows at least two things alkisg doesn't
16:04
<vagrantc>
just a wild guess, and mostly historical
16:06
<mwalters>
such as the airspeed velocity of an unladen swallow
16:17
<Hyperbyte>
!vagrantc
16:17
<ltsp>
Error: "vagrantc" is not a valid command.
16:17
<Hyperbyte>
:-(
16:18
<BuddyButterfly>
Hyperbite ;-)
16:26
<Hyperbyte>
alkisg, you don't have any experience with GTK2/GTK3 do you?
16:37
<alkisg>
!v
16:37
<ltsp>
v: vagrantc!!!!!!!!!!!!!!!!!!1!!!!!
16:37
<alkisg>
!h
16:37
<ltsp>
Error: "h" is not a valid command.
16:37
<alkisg>
meh, you still haven't defined that one? :D
16:37
Hyperbyte: epoptes, sch-scripts etc are in python/gtk, so sure
16:38
<vagrantc>
hah
16:38
!s
16:38
<ltsp>
s: Scotty!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
16:38
<vagrantc>
memories
16:39
<alkisg>
:)
16:40
<vagrantc>
!j
16:40
<ltsp>
j: jammcq!!!!!!!!!!!!!!!!!!!!!!!
16:40vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
17:06lucascastro has left IRC (lucascastro!~lucascast@177-185-139-186.isotelco.net.br, Remote host closed the connection)
17:22lucascastro has joined IRC (lucascastro!~lucascast@200.141.207.18)
18:49
<Hyperbyte>
Hmmm... I edited CMDLINE_LINUX_DEFAULT in /etc/ltsp/update-kernels.conf to include 'quiet splash', but after running ltsp-update-kernels the 'quiet splash' isn't added. Any ideas?
18:57
Closer inspection... ltsp-update-kernels sources "$chroot/etc/ltsp/update-kernels.conf"... when I echo that, it actually shows "/tmp/tmp.urnkX8vkOf/etc/ltsp/update-kernels.conf" which obviously isn't right...
18:58
Do I need some special command for ltsp-update-kernels with ltsp-pnp?
19:14vsuojanen has left IRC (vsuojanen!~valtteri@83-136-248-31.uk-lon1.host.upcloud.com, Remote host closed the connection)
19:35
<Hyperbyte>
mhm... I got it in order now somehow, but not sure how exactly. I think I needed to edit /etc/default/grub as well
19:46kjackal_v2 has left IRC (kjackal_v2!~quassel@2a02:587:310f:d100:8151:6009:41b:32c6, Ping timeout: 252 seconds)
19:58kjackal has joined IRC (kjackal!~quassel@2a02:587:310f:d100:8151:6009:41b:32c6)
20:01lucascastro has left IRC (lucascastro!~lucascast@200.141.207.18, Read error: Connection reset by peer)
20:01lucascastro has joined IRC (lucascastro!~lucascast@170.78.53.20)
20:03lucas_ has joined IRC (lucas_!~lucascast@200.141.207.18)
20:06lucascastro has left IRC (lucascastro!~lucascast@170.78.53.20, Ping timeout: 252 seconds)
20:28ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
20:50lucas_ has left IRC (lucas_!~lucascast@200.141.207.18, Remote host closed the connection)
20:53Faith has left IRC (Faith!~Paty_@unaffiliated/faith, Quit: Leaving)
21:24lucascastro has joined IRC (lucascastro!~lucascast@177-185-139-186.isotelco.net.br)
21:29kjackal has left IRC (kjackal!~quassel@2a02:587:310f:d100:8151:6009:41b:32c6, Ping timeout: 252 seconds)
22:11lucascastro has left IRC (lucascastro!~lucascast@177-185-139-186.isotelco.net.br, Quit: Leaving)