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


Channel log from 2 February 2021   (all times are UTC)

00:54vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
01:05vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
02:31championofcyrodi has joined IRC (championofcyrodi!~ottch@c-71-62-20-140.hsd1.va.comcast.net)
02:51championofcyrodi has left IRC (championofcyrodi!~ottch@c-71-62-20-140.hsd1.va.comcast.net)
03:21vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
05:38lucascastro has left IRC (lucascastro!~lucascast@177-185-133-183.dynamic.isotelco.net.br, Ping timeout: 256 seconds)
05:49RaphGro has joined IRC (RaphGro!~raphgro@fedora/raphgro)
06:04Geoff has joined IRC (Geoff!3aa39b7a@58.163.155.122)
06:04Geoff is now known as Guest76748
06:04Guest76748 has left IRC (Guest76748!3aa39b7a@58.163.155.122, Client Quit)
07:15ogra has left IRC (ogra!~ogra_@ubuntu/member/ogra, Ping timeout: 265 seconds)
07:22ogra_ has joined IRC (ogra_!~ogra_@78.46.228.218)
07:22woernie has joined IRC (woernie!~werner@p5b2966e7.dip0.t-ipconnect.de)
07:47vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
07:50
<vagrantc>
alkisg: just to be clear, my pull request was different than the patch in the bug ... not sure which you tried
07:51
alkisg: regarding epoptes...
07:51
<alkisg>
vagrantc: ah, sorry, let me check again
07:52
vagrantc: indeed, I only tested the patch in the bug, sorry about that
07:52
I committed a fix already, is it ok that I didn't merge even though it's pretty much the same?
07:52
<vagrantc>
heh
07:52
<alkisg>
I can re-push :)
07:53
<vagrantc>
of course it's fine ... important thing is to get it fixed :)
07:54
<alkisg>
vagrantc: I had to force-push due to some launchpad sync issues :/
07:54
In another issue: https://github.com/epoptes/epoptes/commit/61df1fc94cbabc6384257a8ddf5fb5614740a337
07:54
==> override_dh_installinit: # epoptes does not currently ship any init scripts
07:54
That doesn't mean "services" as well, right? Because we do have a systemd epoptes.service...
07:55
<vagrantc>
so i couldn't reproduce the reported issue with ltsp image failing , but at least it caused me to find the epoptes issue
07:55
<alkisg>
Haha, nice
07:55
Well, that user just had a bad passwd file,
07:55
mentioning a group 1027 that he had manually deleted from /etc/group,
07:55
<vagrantc>
garbage in, garbage out
07:56
<alkisg>
so... it's not really an issue with ltsp at all, it's a user issue.
07:56
Not sure how/if I should close it, or even tag it :D
07:56
<vagrantc>
alkisg: yes, that's strictly /etc/init.d/ scripts
07:56
<alkisg>
Great, thanks for that ^
07:56
<vagrantc>
alkisg: the .service files are still installed
07:59
<alkisg>
vagrantc: do you think it's time for epoptes 21.02-1? Should I release it? Do you want to? I don't mind whatever you choose
08:04
<vagrantc>
alkisg: have a few more days where i can push changes to Debian freely
08:05
alkisg: as long as there aren't major changes ... or i can easily fork and apply selected patches
08:05
<alkisg>
vagrantc: if you want me to release a new one right now, I can... there were only shellcheck fixes involved, no major changes to test
08:05
I tested in precise, focal and bullseye, it works
08:06
(precise ==> only the latest epoptes-client changes)
08:07
<vagrantc>
i don't have shellcheck readily on hand ... where does it come from? what is it checking?
08:08
it looks even more pedantic that the checks i used to run :)
08:08
<alkisg>
It's a debian package that checks shell scripts. It can be integrated into visual studio code, which now is my favorite IDE, and it underlines a lot of silly things like forgotten quotes etc
08:09
I wouldn't have caught the tr -d '[]' thing without shellcheck
08:09
I thought tr wanted character classes inside [] like the other tools, but it doesn't
08:10
Btw visual studio code even comes with a shell check code formatter / beautifier... I'll probably start using that one too
08:10
(all related tools and plugins are open source)
08:10
<vagrantc>
i don't imagine i'll start using visual studio :)
08:11
<alkisg>
In a few years, we'll have "code ltsp online on github" environment
08:11
The good thing about vscode is that it can run inside a web browser, that's why all companies, redhat included, are investing on it
08:11
So github already has "workspaces" in beta, with vscode
08:12
This will be very handy when I'm at my silent rpi2 and I want a full blown IDE
08:12
<vagrantc>
not your space-heater rpi4 ?
08:12
<alkisg>
Hehe, nah, rpi4 is ok too. It just needs a thermal cooler
08:13* alkisg also has collected odroid-c2 and rockpine64
08:13
<vagrantc>
rock64-rk3328 ?
08:13
or rockpro64-rk3399 ? :)
08:14
i seem to collect a lot of the pine64 boards...
08:14
<alkisg>
rockpro64, but I don't recall the number
08:15
It stutters a bit at youtube videos, probably due to bad hw acceleration drivers in browsers
08:15
<vagrantc>
it's a nice one ... haven't used the video output though ... but decent mainline support
08:16
<alkisg>
My main use for these are "tv boxes" or "remote desktop to work boxes"... so I usually have the most common/recommended distro for them
08:16
<vagrantc>
alkisg: well, if you feel like releasing a new epoptes, then i can probably upload it to debian in a day or two
08:17
<alkisg>
vagrantc: sure, thanks, doing so within a few minutes :D
08:17
!tag
08:17
<ltspbot`>
tag: tag: git tag -s v20.03 -m 'Version 20.03' && git push --tags
08:17
<vagrantc>
if you don't do local tagging a lot, you can default to pushing tags
08:17
[push] followtags = true
08:18
<alkisg>
I don't do local tagging at all, so I need the reminder for the `git tag` syntax as well :D
08:19
<vagrantc>
:)
08:20
<alkisg>
vagrantc: ready (hopefully) :)
08:20
<vagrantc>
the newer socat version was uploaded to debian just a few days after i last uploaded epoptes ... good thing i had an excuse to test
08:20
one of the problems of not actually *using* the things i upload :/
08:24
<alkisg>
vagrantc: I'm having good progress with my phd; I plan to be finished by summer. So in autumn I'll have enough time to really start supporting debian for school installations
08:24
I'll spend a few months there fixing issues like bad greek fonts etc, and I think I'll apply for a DD,
08:24
and then I'll start migrating most schools to debian :)
08:25
So then I'll know about "debian testing" issues on the day that they happen!
08:25
<vagrantc>
hah
08:25
well, by then bullseye should be the new stable release
08:26
but glad to hear you'll be using debian in schools :)
08:28
anyways, i should head off...
08:28* vagrantc waves
08:33vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
08:52
<fiesh>
it seems that since /etc/shadow isn't shared to the clients (gentoo), sudo doesn't work... is this a common issue or just something broken under the gentoo installation?
08:53
but I guess it makes sense not to share the server's /etc/shadow
08:53
so I suppose hand-crafting one would be an acceptable solution, only giving sudo rights to those users explicitly?
08:53
<sebd>
here sudo works on LTSP clients
08:54
<fiesh>
does it copy the server's /etc/shadow?
08:54
<sebd>
(debian)
08:54
It copies a stripped-down copy of /etc/shadow
08:55
<fiesh>
ah hmm
08:55
<sebd>
I just added my admin to the sudo group (/etc/groups)
08:57
<fiesh>
ok I don't even have a sudo group but the traditional unix `wheel` instead -- so maybe that's the reason why the users aren't included
08:58
<sebd>
In /etc/sudoers : %sudo ALL=(ALL:ALL) ALL
09:01
<fiesh>
yeah I have the same for wheel
09:01
<alkisg>
fiesh: new or old ltsp?
09:01
<fiesh>
uhm
09:01
probably old ;)
09:01
<alkisg>
Then sudo doesn't work
09:01
<fiesh>
oh, heh ok
09:01
that answers that, thanks
09:01
<alkisg>
The old LTSP doesn't use PAM, it only uses SSH on the custom display manager, LDM
09:02
<fiesh>
ah yes indeed
09:02Aison has joined IRC (Aison!~Asion0@2a02:168:200f:110:69c6:120a:877c:5a19)
09:02
<sebd>
unless you use the old LTSP with thin clients of course
09:02* sebd does
09:02
<alkisg>
Eh, then it would be on the server :)
09:02
Not on the client
09:03
brb
09:03alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
09:05alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
09:08
<alkisg>
!sudo
09:08
<ltspbot`>
I do not know about 'sudo', but I do know about these similar topics: 'fat-sudo', 'sudoers'
09:08
<alkisg>
!fat-sudo
09:08
<ltspbot`>
fat-sudo: to allow members of the sudo group to execute "sudo" in fat clients without a password prompt, put this in lts.conf: RCFILE_01="echo '%sudo ALL=NOPASSWD: ALL' >> /etc/sudoers"
09:08
<alkisg>
!sudoers
09:08
<ltspbot`>
sudoers: Not recommented for security reasons: RCFILE_01="echo USER ALL=NOPASSWD: /path/to/program >> /etc/sudoers". USER and /path/to/program can also be ALL.
09:08
<alkisg>
fiesh: possible workarounds for ltsp5 ^
09:09
<fiesh>
hmm yeah, I don't think I want to go for NOPASSWD, thanks
09:09
<alkisg>
https://en.wikipedia.org/wiki/Wheel_(computing) => The term was derived from the slang phrase big wheel, referring to a person with great power or influence
09:09
Meh I prefer "sudoers" :)
09:09
<fiesh>
but putting entries into the clients' /etc/shadow by hand is an acceptable workaround for me
09:09
<alkisg>
!root
09:09
<ltspbot`>
I do not know about 'root', but I do know about these similar topics: 'ROOT_PASSWORD_HASH', 'chroot'
09:10
<alkisg>
!ROOT_PASSWORD_HASH
09:10
<ltspbot`>
ROOT_PASSWORD_HASH: To be able to login as root in vt1, with password "qwer1234", put this in lts.conf: INIT_COMMAND_ROOT_HASH="sed 's!^root:[^:]*:!root:\$6\$p2LdWE6j\$PDd1TUzGvvIkj9SE8wbw1gA/MD66tHHlStqi1.qyv860oK47UnKcafSKqGp7cbgZUPlgyPv6giCVyCSCdJt1b0:!' -i /etc/shadow"
09:10
<alkisg>
While this is for the new ltsp, you can see the idea ^
09:10
<fiesh>
wheel's the old school unix group for administrators
09:10
<alkisg>
This will allow you to put only a "root" shadow entry, a bit safer
09:10
<fiesh>
yeah I have a root entry, doing an `su` works on the clients
09:10
so it's all not a big deal
09:11
was just wondering if there was an elegant solution, but it's ok that old ltsp doesn't have that
09:11
<alkisg>
I know that fedora etc use "wheel" instead of "sudo", I was just curious about the origin, as I didn't know the phrase "big wheel"
09:11
We do say "the last wheel of the car" here, but we don't have a "big wheel" expression
09:30ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
09:49ogra_ has left IRC (ogra_!~ogra_@78.46.228.218)
09:49ogra has joined IRC (ogra!~ogra_@ubuntu/member/ogra)
10:56woernie has left IRC (woernie!~werner@p5b2966e7.dip0.t-ipconnect.de, Quit: No Ping reply in 180 seconds.)
10:56woernie has joined IRC (woernie!~werner@p5b2966e7.dip0.t-ipconnect.de)
11:15lucascastro has joined IRC (lucascastro!~lucascast@177-185-133-183.dynamic.isotelco.net.br)
11:17adrianorg has joined IRC (adrianorg!~adrianorg@191.32.102.128)
12:07Aison has left IRC (Aison!~Asion0@2a02:168:200f:110:69c6:120a:877c:5a19, Ping timeout: 272 seconds)
12:46Aison has joined IRC (Aison!~Asion0@2a02:168:200f:110:69c6:120a:877c:5a19)
16:24RaphGro has left IRC (RaphGro!~raphgro@fedora/raphgro, Quit: Please remember your own message. It'll be read as soon as possible.)
16:37GodFather has left IRC (GodFather!~rcc@wsip-66-210-242-210.ph.ph.cox.net, Ping timeout: 256 seconds)
16:45GodFather has joined IRC (GodFather!~rcc@wsip-66-210-242-210.ph.ph.cox.net)
17:00Aison has left IRC (Aison!~Asion0@2a02:168:200f:110:69c6:120a:877c:5a19, Ping timeout: 272 seconds)
17:08lucascastro has left IRC (lucascastro!~lucascast@177-185-133-183.dynamic.isotelco.net.br, Ping timeout: 256 seconds)
17:13lucascastro has joined IRC (lucascastro!~lucascast@189.90.45.37.jupiter.com.br)
17:18GodFather_ has joined IRC (GodFather_!~rcc@wsip-66-210-242-210.ph.ph.cox.net)
17:20GodFather_ has left IRC (GodFather_!~rcc@wsip-66-210-242-210.ph.ph.cox.net, Client Quit)
17:30Aison has joined IRC (Aison!~Asion0@2a02:168:200f:110:69c6:120a:877c:5a19)
17:42lucascastro has left IRC (lucascastro!~lucascast@189.90.45.37.jupiter.com.br, Ping timeout: 240 seconds)
17:45Aison has left IRC (Aison!~Asion0@2a02:168:200f:110:69c6:120a:877c:5a19, Ping timeout: 264 seconds)
17:47Aison has joined IRC (Aison!~Asion0@2a02:168:200f:110:69c6:120a:877c:5a19)
17:47woernie has left IRC (woernie!~werner@p5b2966e7.dip0.t-ipconnect.de, Remote host closed the connection)
17:47woernie has joined IRC (woernie!~werner@p5b2966e7.dip0.t-ipconnect.de)
17:48woernie has left IRC (woernie!~werner@p5b2966e7.dip0.t-ipconnect.de, Remote host closed the connection)
17:50woernie has joined IRC (woernie!~werner@p5b2966e7.dip0.t-ipconnect.de)
17:53lucascastro has joined IRC (lucascastro!~lucascast@177-185-133-183.dynamic.isotelco.net.br)
18:32yanu has left IRC (yanu!~yanu@178-118-204-17.access.telenet.be, Ping timeout: 265 seconds)
18:45
<quinox>
We have a "<thing / person> is the 5th wheel on a car", in case it is completely useless
18:47
or you can feel like "the fifth wheel on a car" when you're in a group and your input is ignored
19:13adrianorg has left IRC (adrianorg!~adrianorg@191.32.102.128, Quit: leaving)
19:37lucascastro has left IRC (lucascastro!~lucascast@177-185-133-183.dynamic.isotelco.net.br, Remote host closed the connection)
19:55yanu has joined IRC (yanu!~yanu@178-118-205-12.access.telenet.be)
20:02lucascastro has joined IRC (lucascastro!~lucascast@177-185-133-183.dynamic.isotelco.net.br)
20:56shored has left IRC (shored!~shored@81-175-153-95.bb.dnainternet.fi, Ping timeout: 256 seconds)
21:06shored has joined IRC (shored!~shored@dc790tydgtp93h6wnkljt-3.rev.dnainternet.fi)
22:00ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
22:12yanu has left IRC (yanu!~yanu@178-118-205-12.access.telenet.be, Read error: Connection reset by peer)
22:16eu^177-62-223-20 has joined IRC (eu^177-62-223-20!b13edf14@177.62.223.20)
22:16eu^177-62-223-20 has left IRC (eu^177-62-223-20!b13edf14@177.62.223.20, Client Quit)
22:20yanu has joined IRC (yanu!~yanu@178-118-205-12.access.telenet.be)
23:03vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
23:30AppleMuncy has joined IRC (AppleMuncy!4992ede5@c-73-146-237-229.hsd1.in.comcast.net)
23:33AppleMuncy has left IRC (AppleMuncy!4992ede5@c-73-146-237-229.hsd1.in.comcast.net, Client Quit)