|00:08||Manoel has joined IRC (Manoel!~Manoel@130-75-182-201.provedornetlux.com.br)|
|00:09||sunflower has left IRC (sunflower!~Manoel@130-75-182-201.provedornetlux.com.br, Ping timeout: 250 seconds)|
|00:40||Manoel_ has joined IRC (Manoel_!~Manoel@130-75-182-201.provedornetlux.com.br)|
|00:40||Manoel has left IRC (Manoel!~Manoel@130-75-182-201.provedornetlux.com.br, Read error: Connection reset by peer)|
|00:42||Manoel__ has joined IRC (Manoel__!~Manoel@130-75-182-201.provedornetlux.com.br)|
|00:46||Manoel_ has left IRC (Manoel_!~Manoel@130-75-182-201.provedornetlux.com.br, Ping timeout: 260 seconds)|
|00:53||Manoel__ has left IRC (Manoel__!~Manoel@130-75-182-201.provedornetlux.com.br, Ping timeout: 260 seconds)|
|02:59||vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100e, Quit: leaving)|
|07:41||vsuojanen has left IRC (email@example.com, Ping timeout: 245 seconds)|
|07:43||ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)|
|07:43||vsuojanen has joined IRC (firstname.lastname@example.org)|
|08:22||woernie has joined IRC (email@example.com)|
|09:56||danboid has joined IRC (firstname.lastname@example.org)|
alkisg, Did you finish writing the wiki page fot dnsmasq?
Hi danboid , yes, ...
> danboid, the new page is temporarily there: https://pe86.github.io/linux/LTSP/Προχωρημένα/Πολλά_εργαστήρια/
Don't link to that page as it's a temporary URL, but the content is indeed finalized
Great, thanks! I'll have a read now
I'll edit that and add it to the wiki today
Nice. danboid , regarding the issue, yeah I'm planning to add a small note "use mbr/single ext4 partition" to keep things simple
Great, thats all the user needs to know really.
Some other things are indeed supported, but it would take a lot of time and space to explain the restrictions, as the same code is used inside the initramfs where the tools are sparse
alkisg, I failed to fix the kernel /VB issue on our old (but still in use) LTSP server. I removed all old kernels and configs (ie did a purge of kernel packages) but the kernel versions still don't match up
We'd need to check via vnc for that
It'd take too long to do it over chat...
(as you already looked at all the usual culprits)
Not sure VNC would work but I could create you a temp SSH account
We'll hopefully get it replaced within the next couple of weeks with a fully uptodate and modern server
Sure, but it's better if you can see what I'm doing with vnc or terminal sharing
x11vnc -connect alkisg.ltsp.org => for graphics,
/usr/share/epoptes-client/share-terminal 188.8.131.52 ==> for terminal sharing
But for terminal sharing you need to ping me to open my side first, I don't have it listening all the time
While with ssh a malicious technician could plant malware or whatever, without you seeing what he's doing
I just tried the share terminal command
socat E connect(6, AF=2 184.108.40.206:5499, 16): Connection refused
"you need to ping me first" :D
OK opening my side...
danboid: essentially I just want to see what bootfilename it provides
I don't need to ssh to it
Moment, school, back in a bit...
|10:19||vsuojanen has left IRC (email@example.com, Ping timeout: 260 seconds)|
OK, I'll find out now
danboid: you want kernel 4.15 on the clients?
Yeah, the same as on the server
Can we move all the extra images aside, so that we're sure they're not interfering?
|10:21||vsuojanen has joined IRC (firstname.lastname@example.org)|
danboid: it's chrootless, right? Can I run ltsp-update-image -c / now?
Ah, I forgot to mention
OK as you can see, you did have all those 4.4 kernels and initrds
We run this monitoring thing called Taniumclient and I often stop that before updating the LTSP image
danboid: OK I cancelled ltsp-update-image, do it your way
I'm not sure if it causes probs or not but it does cause messages during the update
Do it inside our shared terminal so that I can see
I've not checked that epoptes share terminal script yet, is it using screen?
I'll be so relieved to be able to wipe this server and start afresh. I inherited it and it was a mess 3 years ago.
Now its a very outdated mess
Its going to be get re-installed and then become the failover
I'm going to set it up like the new one, Ubuntu 20.04, VM images, soft RAID for the OS and ZFS for home dirs
OK its updated now#
I won't be able to check its fixed until tomorrow but I trust you've fixed it. Thanks alkisg!
I might be able to get solmeone else to check it for me
In fact I should be able to pxe boot a VM to test it
once I'm on the VPN, never tried that
I'll do that wiki page now coz I owe you one :)
danboid: the main problem is that you also had a chroot in /opt/ltsp/amd64
So the kernel was coming from the chroot
Ahh! I didn't know about that!
I do not make money from ltsp nor from the wiki. Do not do it for me
Do it for you, as a community
If you want to help each other, that is; I can only help so much.
Yep. I want to lessen your support burden if I can
(I closed the shared terminal, it looked ok now)
Excellent! I hate telling the staff I can't fix stuff, you saved my ass
I reckon the new server should be up in the next couple of weeks but all sorts of surprise delays could happen
and our security guys not liking stuff
Which they have good reason for in many cases
I made some tweaks / small additios to 3 of the wiki pages last night - chroots, SAMBA DCs and the Ububntu server guide I wrote
|11:10||dan__ has joined IRC (email@example.com)|
|11:13||danboid has left IRC (firstname.lastname@example.org, Ping timeout: 260 seconds)|
|12:38||vsuojanen has left IRC (email@example.com, Ping timeout: 256 seconds)|
|12:40||vsuojanen has joined IRC (firstname.lastname@example.org)|
alkisg, Check this for me please https://github.com/ltsp/ltsp/wiki/Multiple-LTSP-servers-on-one-network
I've just give it a once over with the formatting, should be good now
dan__: great, nice work!
denial => probably "negation" is a better term in english
Yeah I suppose so
|15:13||TomTeichler[m] has joined IRC (TomTeichler[m]!~tteichler@2001:470:69fc:105::186d)|
|15:29||vsuojanen has left IRC (email@example.com, Ping timeout: 256 seconds)|
|15:30||vsuojanen has joined IRC (firstname.lastname@example.org)|
|16:03||woernie has left IRC (email@example.com, Ping timeout: 256 seconds)|
|16:03||woernie has joined IRC (woernie!~werner@2001:1640:141:7:b4c7:5b0d:b8b3:a26a)|
|16:26||woernie has left IRC (woernie!~werner@2001:1640:141:7:b4c7:5b0d:b8b3:a26a, Remote host closed the connection)|
|17:03||vsuojanen has left IRC (firstname.lastname@example.org, Ping timeout: 256 seconds)|
|17:05||vsuojanen has joined IRC (email@example.com)|
|17:27||lucascastro has left IRC (firstname.lastname@example.org, Ping timeout: 260 seconds)|
|17:46||lucascastro has joined IRC (email@example.com)|
|20:45||lucascastro has left IRC (firstname.lastname@example.org, Ping timeout: 256 seconds)|
|21:42||danboid has joined IRC (email@example.com)|
|21:43||dan__ has left IRC (firstname.lastname@example.org, Ping timeout: 250 seconds)|
|22:03||danboid has left IRC (email@example.com, Quit: Leaving)|
|22:33||Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection)|
|22:33||Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas)|
|23:07||ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)|