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


Channel log from 4 April 2021   (all times are UTC)

00:21GodFather has joined IRC (GodFather!~rcc@4.59.197.254)
00:22GodFather has left IRC (GodFather!~rcc@4.59.197.254, Remote host closed the connection)
02:24spectra has left IRC (spectra!~spectra@debian/developer/spectra, *.net *.split)
02:24tek_ has left IRC (tek_!tek@kapsi.fi, *.net *.split)
02:30tek_ has joined IRC (tek_!tek@kapsi.fi)
02:36spectra has joined IRC (spectra!~spectra@debian/developer/spectra)
05:29keats has joined IRC (keats!~keats@2400:1a00:b1c0:d649:5408:5e59:e079:3b98)
05:29
<keats>
Hey there
05:29
has anybody tried solus as an ltsp client image?
05:30
I'm having this issue w/ solus where it just says "Failed to start switch root"
05:32
any ideas?
05:39
all right then i'm just going to wait it out because i am at my wit's end
05:52
okay so there's no /dev/nfs... i might need to install nfs on this particular distro first. sorry my bad
06:01
nope....
06:01
lubuntu does not have /dev/nfs when it boots either... so this must be something that's available while the system is booting
06:02
alkisg: sorry to ping you but could you please give me any pointers regarding the matter please... i am at my wit's end, again.
06:04
<alkisg>
Morning all
06:05
Reading...
06:05
keats: do you have a VM client that I could watch over VNC?
06:05
<keats>
Hmmm..... yes sir. just a moment please
06:06
<alkisg>
Package manager: eopkg
06:06
Ah it's not based on Debian?
06:06
!vnc-dide
06:06
<ltspbot`>
vnc-dide: To share your screen with me, run this: sudo apt-get --yes install x11vnc; x11vnc -connect srv1-dide.ioa.sch.gr - this is a reverse connection, it doesn't need port forwarding etc.
06:06
<keats>
no sir
06:06
vm is booting up
06:07
<alkisg>
keats: new distributions, not based on debian, would need a couple of hours at least for porting ltsp to them
06:07
<keats>
systemctl status initrd-switch-root.service says "specified switch root path '/sysroot' does not seem to be an OS tree.
06:07
<alkisg>
I.e. even if we get past that point, we'll find a few more that would need to be resolved before production use
06:08
<keats>
hmmm.... i've been having issues with this one laptop that has ati radeon graphics card (integrated) and it doesn't boot to gui (but only shows mouse cursor - which i can move)
06:08
and solus seemed to boot via usb just fine
06:08
<alkisg>
That's just kernel/xorg
06:08
It's not related to distributions, usually
06:08
<keats>
whereas debian and elementary acted strange
06:08
hmmm
06:09
<alkisg>
Just see which kernel/xorg driver it's using, and select a debian based distro with the same combination
06:09
<keats>
.... and i couldn't find any workaround for that issue
06:09
hmmmm
06:09
how would i check which driver it is using?
06:09
<alkisg>
lspci -nn -k | grep -A3 VGA
06:09
And uname -a
06:09
What's the output of these?
06:09
<keats>
also, i kinda' found a bug-ish thingy....
06:10
it appears that the server's time is used as the UTC by the clients. so my GMT+X server boots up clients that are (GMT+X)+X in time
06:10
<alkisg>
That's just a distribution tiny misconfiguration, easily solvable
06:11
<keats>
i'll have to configure the client images to use UTC?
06:11
<alkisg>
No, use the same timezone everywhere
06:11
Which distribution are you talking about now, still solus?
06:11
<keats>
i'm using the same timezone in my clients and the server o.O
06:11
no sir... the usual ones: lubuntu and friends
06:11
(debian derivatives)
06:12
<alkisg>
cat /etc/timezone
06:12
On the server vs on the clients
06:12
<keats>
just a moment please
06:12
<alkisg>
You may also vnc to me if you like, like I wrote above
06:12
<keats>
it's the same on both
06:13
the server is running trisquel gnu/linux
06:13
the client is lubuntu
06:13
both are set to the same time zone
06:13
<alkisg>
timedatectl status | nc termbin.com 9999
06:13
<keats>
the ltsp computers aren't connected to the internet. i'm on a different machine
06:13
<alkisg>
Paste the output of that, from the server and the clients
06:13
Maybe then they're just not synchronized
06:14
And you need to set up a local NTP server
06:14
<keats>
ah... because they're not connected to the internet
06:14
that makes much sense
06:15
<alkisg>
Also if you ever boot windows in them, they're not using utc, so they skew the clock
06:15
<keats>
but i can confirm that the client thinks that the server's local time is the universal time
06:15
timedatectl status on the client shows that
06:15
we can use windows as a client in ltsp!????
06:15
<alkisg>
No I meant if you had local windows in your clients
06:15
And you booted windows while they were connected to the internet,
06:15
<keats>
ah... i see.... I see.
06:15
<alkisg>
then it would sync the clock to non-utc time. Then, when you'd boot into linux, you'd see the UTC+X+X effect you mentioned
06:16
<keats>
i see that makes sense
06:16
<alkisg>
So IF these clients were booted into windows the last time they were connected in the internet, it would explain everything
06:16
<keats>
let me check the actual diskless ones to see if they exhibit the same issue
06:16
<alkisg>
Just set the correct time and reboot
06:16
If it keeps the correct time, it's fine
06:17
<keats>
another question (i haven't had the time to experiment myself): what kind of changes can the clients make that will persist. I know that /home persists... and normal settings (and time would be one, I presume)
06:18
<alkisg>
Home persists because it's SSHFS (by default), while clock is written in CMOS (BIOS memory)
06:18
Nothing else persists
06:18
<keats>
i see
06:20
just checked the diskless client and it has a different date. so yes. what you just said makes sense. I should probably just run a local network time server then. i shall look into it
06:21
<alkisg>
Apt install ntpd in the ltsp server should do it
06:22
<keats>
I see.
06:22
Thank you very much
06:22
<alkisg>
You're welcome
08:02vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
11:13
<keats>
okay this is strange, again...
11:13
xubuntu groovy gorilla...
11:13
the image does not boot to the client
11:14
the error? rsync: [generator/receiver] failed to set permissios on "/usr/share/ltsp/client"
11:14
ah wait
11:14
my mistake
11:14
i need to fix that
11:14
i'm an idiot
11:14
sorry
11:19keats has left IRC (keats!~keats@2400:1a00:b1c0:d649:5408:5e59:e079:3b98, Ping timeout: 245 seconds)
11:21keats has joined IRC (keats!~keats@27.34.47.203)
11:43
<alkisg>
keats: ubuntu 20.10 has a bug in rsync
11:43
Better use 20.04
11:43
!rsync
11:43
<ltspbot`>
Error: "rsync" is not a valid command.
11:43
<keats>
alkisg: I am going to die
11:44
<alkisg>
We all are :D
11:44
<keats>
seriously? I've got EVERYTHING setup in 20.10!!!!!
11:44
<alkisg>
Hopefully, 100 years later...
11:44
Well, you can work around it by changing one line in ltsp
11:44
<keats>
please teach me sensei!
11:44
but there are 3 other images too
11:44
so it has to be backwards compatible
11:45
<alkisg>
cd /usr/share/ltsp
11:45
grep -rw rsync
11:45
<keats>
in the server i presume
11:45
<alkisg>
Where you see "re rsync", change it to "rw rsync"
11:45
Yes. Then, run ltsp initrd.
11:45
<keats>
this does not affect the others right?
11:45
doing it
11:45
<alkisg>
In this file only: ltsp/client/initrd-bottom/55-initrd-bottom.sh
11:46
It won't have bad side effects, no
11:47
<keats>
hmmmmmm
11:48
there isn't a "re rsync" in that file but only a re chroot "$rootmnt" rsync
11:48
o.O
11:51
<alkisg>
Change re to rw there too
11:51
<keats>
only there, right
11:51
<alkisg>
(that's the one, yeah)
11:51
2 instances, right?
11:51
<keats>
line 65 and 66
11:51
yes
11:51
wait...
11:51
no
11:52
i was looking at client/init/25-ro-root.sh
11:52
<alkisg>
ltsp/client/initrd-bottom/55-initrd-bottom.sh: re chroot "$rootmnt" rsync -a --delete /tmp/ /usr/share/ltsp
11:52
ltsp/client/initrd-bottom/55-initrd-bottom.sh: re chroot "$rootmnt" rsync -a --delete /tmp/ /etc/ltsp
11:52
Change these re to rw
11:52
<keats>
yes those. okay. i will. thank you
12:19
alkisg: thank you. it kinda' does work now. although... i should probably try to look into proprietary drivers for that radeon ati thingy
12:20
... which sucks
12:20
anyways, is there a way to make a certain client boot a particular image directly without showing them ipxe menu?
12:32keats has left IRC (keats!~keats@27.34.47.203, Ping timeout: 240 seconds)
13:00keats has joined IRC (keats!~keats@27.34.47.231)
13:20keats_ has joined IRC (keats_!~keats@27.34.47.231)
13:22keats has left IRC (keats!~keats@27.34.47.231, Ping timeout: 240 seconds)
14:38keats_ has left IRC (keats_!~keats@27.34.47.231, Ping timeout: 268 seconds)
19:43vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)