|00:59||dummy has joined IRC (dummy!b9a20bd9@gateway/web/freenode/ip.126.96.36.199)|
hello there, guys
have a quick question
|01:00||dummy is now known as Guest35322|
can I somehow choose a user when logging in from thin client?
i mean smth like dropdown with usernames to choose
Guest35322: there isn't a way to do that
Guest35322: as the LTSP thin clients don't have a list of users
|01:17||Guest35322 has left IRC (Guest35322!b9a20bd9@gateway/web/freenode/ip.188.8.131.52, Quit: Page closed)|
I do not know about 'local', but I do know about these similar topics: 'install-localapp', 'localdev', 'RDP-localdev', 'LocaldevCommonGroupWorkaround', 'localxterm', 'local-disks', 'local-boot', 'localapps'
local-disks: On fat clients, only sudoers have access to local disks. One way to give access to non sudoers, is to put in lts.conf: RCFILE_01="mkdir -p /media/local_disk && mount /dev/sda1 /media/local_disk"
|06:14||Eric5 has joined IRC (Eric5email@example.com)|
|06:24||mikkel has joined IRC (firstname.lastname@example.org)|
|06:42||mikkel has left IRC (email@example.com, Quit: Leaving)|
|06:46||mikkel has joined IRC (firstname.lastname@example.org)|
|07:55||lliurex has joined IRC (lliurex!d500570d@gateway/web/freenode/ip.184.108.40.206)|
jetpipe: (#1) Jetpipe -script has founded to be unstable in some cases. You can try C written (but limited) Jetpipe from GitHub https://github.com/bilange/jetpipe or switch it to USB/IP and use these scripts http://pastebin.com/Ltdi2TCL Support AIO devices as well., or (#2) jetpipe has a bug in some Ubuntu versions, to manually start it, put something like this in lts.conf: RCFILE_01="/usr/sbin/jetpipe /dev/usb/lp0 9100 &"
|08:44||vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Ping timeout: 252 seconds)|
|09:31||ricotz has joined IRC (ricotz!~ricotz@p5B2A869F.dip0.t-ipconnect.de)|
|09:31||ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)|
|10:20||gverv has joined IRC (gverv!51ba1532@gateway/web/freenode/ip.220.127.116.11)|
|10:28||gverv has left IRC (gverv!51ba1532@gateway/web/freenode/ip.18.104.22.168, Quit: Page closed)|
alkisg, s/founded/found/ :)
(or rather "been found")
ogra_: I didn't write that one :)
I only wrote (#2) there
|11:17||muvlon has left IRC (email@example.com, Ping timeout: 240 seconds)|
|11:22||Freejack has left IRC (Freejack!~quassel@unaffiliated/freejack, Quit: No Ping reply in 180 seconds.)|
|11:24||Freejack has joined IRC (Freejack!~quassel@unaffiliated/freejack)|
|11:38||Eric5 has left IRC (Eric5firstname.lastname@example.org, Ping timeout: 248 seconds)|
|12:10||Eric5 has joined IRC (Eric5email@example.com)|
|12:24||GodFather has left IRC (GodFatherfirstname.lastname@example.org, Remote host closed the connection)|
|12:25||GodFather has joined IRC (GodFatheremail@example.com)|
|13:02||mpw has joined IRC (mpw!84e6c36e@gateway/web/freenode/ip.22.214.171.124)|
|13:03||mpwyn has joined IRC (mpwyn!84e6c36e@gateway/web/freenode/ip.126.96.36.199)|
Anybody out there who exports the chroot via NFS?
More precisely, fat clients exported with NFS?
mpwyn: it doesn't work in recent kernels
Why not use nbd instead?
(actually, overlayfs over nfs hasn't worked since the beginning, although I think it might work in very recent kernels or in the future)
I started out years ago using nbd but then switched to Debian, which used NFS.
Debian has switched from NFS to NBD
Since stretch, I believe
Since overlayfs got in the kernel and aufs was no longer the default for overlays
The problem with NBD is that the clients have to reboot every time you recreate the image. Or is that not correct?
(aufs worked for NFS)
Yes, it is. In what cases you don't reboot the client when you install software?
E.g. if you update systemd or udev or the kernel or libc, you should reboot anyway...
But if you install e.g. libreoffice, yeah, you would save a reboot there
It's also about 5 times faster than NFS though
So an occasional reboot vs 5 times faster... it's not really a comparison
I work at the Physics department at a university. I take care of several groups. When somebody asks for a new software package, it used to be that I could quickly install it and it would be instantly available.
Yes, and it would require 10 times more RAM on the server, 10 times more lan bandwidth, and it would be 5 times slower
I think a reboot is a small compromise for all that
Eh, sorry, got carried away, the 2 first are for fat vs thin
Only the last one is nfs vs nbd
My users run jobs that can last days or weeks. I can't go requiring them to reboot whenever I make a change in the background
LAN bandwidth is only 2.5 times lower with nbd
Of course not, they'll reboot whenever they want the new package
Not on every change that you do...
They're not forced to reboot when I recreate the image? I thought that was the case.
It's been a while since I've used NBD.
No, unless they log out and ldm sees a new image and it automatically reboots because there's no user logged in
When a user is logged in, no action is taken at all
They can keep using the old image for months
OK, if that's the case then maybe I have no problem.
Well if you insist on nfs, you could try a really new kernel, or manually install aufs
But it's not something that anyone else has done...
So the crux is that the clients copy the image locally or what?
No of course not
What happens when you boot from a usb disk or stick?
The os loads the "sectors" it needs when it needs them
Exactly the same happens now over then et
So the image can be 50 GB, and the client may only have 512 MB RAM, with no issues
(a typical image is 1 GB)
I'll have huge images, though.
No problem at all, except that it'll need half an hour when you run ltsp-update-image
Otherwise, the clients will still boot in under a sec
(and a lot faster than when using nfs)
*under a min, sorry
OK, I guess I just need to try NBD again. It seems that I was misunderstanding things.
I thought I remembered that every time I recreated the image everybody had to reboot.
Give it a try, and if you see any issues, ping again... :)
I've been an ltsp developer since 2008, I don't remember that ever happenning
I don't know if it was so before my time
Then I must have been doing it wrong. I don't think I used it before 2008.
Thanks for your assitance. I'll try NBD.
|13:22||mpwyn has left IRC (mpwyn!84e6c36e@gateway/web/freenode/ip.188.8.131.52)|
alkisg: I'm using chroot with NFS and overlayfs!
no... it's unionfs
bcg: what does fedora live cd use, unionfs or overlayfs?
I don't remember.
device-mapper? See https://fedoraproject.org/wiki/LiveOS_image and https://fedoraproject.org/wiki/LiveOS_image/overlay
When doing the rhel7-work I remember that I tried to use overlayfs but just got deadlocks. Unionfs worked so I'm using it.
|14:23||mikkel has left IRC (firstname.lastname@example.org, Quit: Leaving)|
|14:30||robp2175 has joined IRC (robp2175!d0e92403@gateway/web/freenode/ip.184.108.40.206)|
|14:30||GodFather has left IRC (GodFatheremail@example.com, Ping timeout: 240 seconds)|
I am trying to configure LTSP for Raspberry Pis. I have followed these instructions: https://help.ubuntu.com/community/UbuntuLTSP/RaspberryPi
When I try to boot my RPi3 I get the rainbow screen.
robp2175: using Ubuntu 16.04?
Did you see any error messages while following the wiki page instructions?
None, everything looked good. using 14.04
robp2175: that won't work, support was added later in the kernel
You'd need a newer kernel than the one available in 14.04. It's possible, but not recommended.
|14:42||vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)|
|14:44||ben_roose has joined IRC (firstname.lastname@example.org)|
I used 14.04 because of the warning at the top of this page: https://help.ubuntu.com/community/UbuntuLTSP/RaspberryPi
It says "Warning: the stock Ubuntu 16.04 kernel currently seems to be unable to boot Raspberry Pi 2 and 3"
robp2175: yes I uploaded a new kernel that works but forgot to remove the warning
OK, sounds good. I will start from scratch.
|15:08||* alkisg updated the wiki page...|
|16:14||* Guest32437 rejoices at another upgrade to documentation!|
|16:36||GodFather has joined IRC (GodFatheremail@example.com)|
|17:32||zama has joined IRC (zama!~zama@unaffiliated/stryx/x-3871776)|
|17:46||lucascastro has joined IRC (firstname.lastname@example.org)|
|18:03||lucascastro has left IRC (email@example.com, Ping timeout: 240 seconds)|
|18:07||Eric5 has left IRC (Eric5firstname.lastname@example.org, Ping timeout: 240 seconds)|
|18:20||lucascastro has joined IRC (email@example.com)|
|18:58||ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)|
|20:53||lucascastro has left IRC (firstname.lastname@example.org, Remote host closed the connection)|
|22:17||ogra_ has left IRC (email@example.com, Ping timeout: 240 seconds)|
|22:18||ogra_ has joined IRC (firstname.lastname@example.org)|
|22:43||GodFather has left IRC (GodFatheremail@example.com, Ping timeout: 240 seconds)|
|22:53||GodFather has joined IRC (GodFatherfirstname.lastname@example.org)|
|22:55||GodFather has left IRC (GodFatheremail@example.com, Client Quit)|
|22:55||GodFather has joined IRC (GodFatherfirstname.lastname@example.org)|
|23:24||GodFather has left IRC (GodFatheremail@example.com, Ping timeout: 240 seconds)|
|23:28||GodFather has joined IRC (GodFatherfirstname.lastname@example.org)|
|23:33||ben_roose has left IRC (email@example.com, Remote host closed the connection)|