IRC chat logs for #ltsp on irc.libera.chat (webchat)
Channel log from 18 September 2017 (all times are UTC)
| 00:59 | dummy has joined IRC (dummy!b9a20bd9@gateway/web/freenode/ip.185.162.11.217) | |
| 00:59 | <dummy> hello there, guys
| |
| 01:00 | have a quick question
| |
| 01:00 | dummy is now known as Guest35322 | |
| 01:00 | <Guest35322> can I somehow choose a user when logging in from thin client?
| |
| 01:01 | i mean smth like dropdown with usernames to choose
| |
| 01:12 | <vagrantc> Guest35322: there isn't a way to do that
| |
| 01:12 | Guest35322: as the LTSP thin clients don't have a list of users
| |
| 01:17 | <Guest35322> thx
| |
| 01:17 | Guest35322 has left IRC (Guest35322!b9a20bd9@gateway/web/freenode/ip.185.162.11.217, Quit: Page closed) | |
| 05:45 | <alkisg> !local
| |
| 05:45 | <ltsp> 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'
| |
| 05:46 | <alkisg> !local-disks
| |
| 05:46 | <ltsp> 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 (Eric5!~eric@sdi.iut-valence.fr) | |
| 06:24 | mikkel has joined IRC (mikkel!~mikkel@mail.dlvs.dk) | |
| 06:42 | mikkel has left IRC (mikkel!~mikkel@mail.dlvs.dk, Quit: Leaving) | |
| 06:46 | mikkel has joined IRC (mikkel!~mikkel@mail.dlvs.dk) | |
| 07:55 | lliurex has joined IRC (lliurex!d500570d@gateway/web/freenode/ip.213.0.87.13) | |
| 08:06 | <alkisg> !jetpipe
| |
| 08:06 | <ltsp> 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.81.186.21.50) | |
| 10:28 | gverv has left IRC (gverv!51ba1532@gateway/web/freenode/ip.81.186.21.50, Quit: Page closed) | |
| 10:33 | <ogra_> alkisg, s/founded/found/ :)
| |
| 10:34 | (or rather "been found")
| |
| 10:56 | <alkisg> ogra_: I didn't write that one :)
| |
| 10:56 | I only wrote (#2) there
| |
| 10:56 | <ogra_> :)
| |
| 11:17 | muvlon has left IRC (muvlon!~muvlon@232.149-246-81.adsl-dyn.isp.belgacom.be, 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 (Eric5!~eric@sdi.iut-valence.fr, Ping timeout: 248 seconds) | |
| 12:10 | Eric5 has joined IRC (Eric5!~eric@sdi.iut-valence.fr) | |
| 12:24 | GodFather has left IRC (GodFather!~rcc@47.33.250.142, Remote host closed the connection) | |
| 12:25 | GodFather has joined IRC (GodFather!~rcc@47.33.250.142) | |
| 13:02 | mpw has joined IRC (mpw!84e6c36e@gateway/web/freenode/ip.132.230.195.110) | |
| 13:03 | mpwyn has joined IRC (mpwyn!84e6c36e@gateway/web/freenode/ip.132.230.195.110) | |
| 13:05 | <mpwyn> Anybody out there who exports the chroot via NFS?
| |
| 13:07 | More precisely, fat clients exported with NFS?
| |
| 13:09 | <alkisg> mpwyn: it doesn't work in recent kernels
| |
| 13:09 | Why not use nbd instead?
| |
| 13:10 | (actually, overlayfs over nfs hasn't worked since the beginning, although I think it might work in very recent kernels or in the future)
| |
| 13:11 | <mpwyn> I started out years ago using nbd but then switched to Debian, which used NFS.
| |
| 13:11 | <alkisg> Debian has switched from NFS to NBD
| |
| 13:12 | Since stretch, I believe
| |
| 13:12 | Since overlayfs got in the kernel and aufs was no longer the default for overlays
| |
| 13:12 | <mpwyn> The problem with NBD is that the clients have to reboot every time you recreate the image. Or is that not correct?
| |
| 13:12 | <alkisg> (aufs worked for NFS)
| |
| 13:12 | Yes, it is. In what cases you don't reboot the client when you install software?
| |
| 13:13 | E.g. if you update systemd or udev or the kernel or libc, you should reboot anyway...
| |
| 13:13 | But if you install e.g. libreoffice, yeah, you would save a reboot there
| |
| 13:13 | It's also about 5 times faster than NFS though
| |
| 13:13 | So an occasional reboot vs 5 times faster... it's not really a comparison
| |
| 13:14 | <mpwyn> 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.
| |
| 13:15 | <alkisg> Yes, and it would require 10 times more RAM on the server, 10 times more lan bandwidth, and it would be 5 times slower
| |
| 13:15 | I think a reboot is a small compromise for all that
| |
| 13:15 | Eh, sorry, got carried away, the 2 first are for fat vs thin
| |
| 13:15 | Only the last one is nfs vs nbd
| |
| 13:16 | <mpwyn> 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
| |
| 13:16 | <alkisg> LAN bandwidth is only 2.5 times lower with nbd
| |
| 13:16 | Of course not, they'll reboot whenever they want the new package
| |
| 13:16 | Not on every change that you do...
| |
| 13:16 | <mpwyn> They're not forced to reboot when I recreate the image? I thought that was the case.
| |
| 13:17 | It's been a while since I've used NBD.
| |
| 13:17 | <alkisg> No, unless they log out and ldm sees a new image and it automatically reboots because there's no user logged in
| |
| 13:17 | When a user is logged in, no action is taken at all
| |
| 13:17 | They can keep using the old image for months
| |
| 13:17 | <mpwyn> OK, if that's the case then maybe I have no problem.
| |
| 13:18 | <alkisg> Well if you insist on nfs, you could try a really new kernel, or manually install aufs
| |
| 13:18 | But it's not something that anyone else has done...
| |
| 13:18 | <mpwyn> So the crux is that the clients copy the image locally or what?
| |
| 13:18 | <alkisg> No of course not
| |
| 13:19 | What happens when you boot from a usb disk or stick?
| |
| 13:19 | The os loads the "sectors" it needs when it needs them
| |
| 13:19 | Exactly the same happens now over then et
| |
| 13:19 | net
| |
| 13:19 | So the image can be 50 GB, and the client may only have 512 MB RAM, with no issues
| |
| 13:19 | (a typical image is 1 GB)
| |
| 13:19 | <mpwyn> I'll have huge images, though.
| |
| 13:20 | <alkisg> No problem at all, except that it'll need half an hour when you run ltsp-update-image
| |
| 13:20 | Otherwise, the clients will still boot in under a sec
| |
| 13:20 | (and a lot faster than when using nfs)
| |
| 13:20 | *under a min, sorry
| |
| 13:20 | <mpwyn> OK, I guess I just need to try NBD again. It seems that I was misunderstanding things.
| |
| 13:21 | I thought I remembered that every time I recreated the image everybody had to reboot.
| |
| 13:21 | <alkisg> Give it a try, and if you see any issues, ping again... :)
| |
| 13:21 | I've been an ltsp developer since 2008, I don't remember that ever happenning
| |
| 13:21 | I don't know if it was so before my time
| |
| 13:22 | <mpwyn> Then I must have been doing it wrong. I don't think I used it before 2008.
| |
| 13:22 | Thanks for your assitance. I'll try NBD.
| |
| 13:22 | mpwyn has left IRC (mpwyn!84e6c36e@gateway/web/freenode/ip.132.230.195.110) | |
| 13:39 | <bcg> alkisg: I'm using chroot with NFS and overlayfs!
| |
| 13:40 | no... it's unionfs
| |
| 13:49 | <alkisg> bcg: what does fedora live cd use, unionfs or overlayfs?
| |
| 13:50 | <bcg> I don't remember.
| |
| 14:00 | device-mapper? See https://fedoraproject.org/wiki/LiveOS_image and https://fedoraproject.org/wiki/LiveOS_image/overlay
| |
| 14:02 | 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 (mikkel!~mikkel@mail.dlvs.dk, Quit: Leaving) | |
| 14:30 | robp2175 has joined IRC (robp2175!d0e92403@gateway/web/freenode/ip.208.233.36.3) | |
| 14:30 | GodFather has left IRC (GodFather!~rcc@47.33.250.142, Ping timeout: 240 seconds) | |
| 14:32 | <robp2175> I am trying to configure LTSP for Raspberry Pis. I have followed these instructions: https://help.ubuntu.com/community/UbuntuLTSP/RaspberryPi
| |
| 14:32 | When I try to boot my RPi3 I get the rainbow screen.
| |
| 14:37 | <alkisg> robp2175: using Ubuntu 16.04?
| |
| 14:39 | Did you see any error messages while following the wiki page instructions?
| |
| 14:41 | <robp2175> None, everything looked good. using 14.04
| |
| 14:42 | <alkisg> robp2175: that won't work, support was added later in the kernel
| |
| 14:42 | 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 (ben_roose!~roose@roose.cs.wichita.edu) | |
| 14:44 | <robp2175> I used 14.04 because of the warning at the top of this page: https://help.ubuntu.com/community/UbuntuLTSP/RaspberryPi
| |
| 14:44 | It says "Warning: the stock Ubuntu 16.04 kernel currently seems to be unable to boot Raspberry Pi 2 and 3"
| |
| 14:44 | <alkisg> robp2175: yes I uploaded a new kernel that works but forgot to remove the warning
| |
| 14:45 | ...reformat :)
| |
| 14:45 | <robp2175> 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 (GodFather!~rcc@47.33.250.142) | |
| 17:32 | zama has joined IRC (zama!~zama@unaffiliated/stryx/x-3871776) | |
| 17:46 | lucascastro has joined IRC (lucascastro!~lucas@189.90.38.210.jupiter.com.br) | |
| 18:03 | lucascastro has left IRC (lucascastro!~lucas@189.90.38.210.jupiter.com.br, Ping timeout: 240 seconds) | |
| 18:07 | Eric5 has left IRC (Eric5!~eric@sdi.iut-valence.fr, Ping timeout: 240 seconds) | |
| 18:20 | lucascastro has joined IRC (lucascastro!~lucas@170.78.53.20) | |
| 18:58 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |
| 20:53 | lucascastro has left IRC (lucascastro!~lucas@170.78.53.20, Remote host closed the connection) | |
| 22:17 | ogra_ has left IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de, Ping timeout: 240 seconds) | |
| 22:18 | ogra_ has joined IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de) | |
| 22:43 | GodFather has left IRC (GodFather!~rcc@47.33.250.142, Ping timeout: 240 seconds) | |
| 22:53 | GodFather has joined IRC (GodFather!~rcc@47.33.250.142) | |
| 22:55 | GodFather has left IRC (GodFather!~rcc@47.33.250.142, Client Quit) | |
| 22:55 | GodFather has joined IRC (GodFather!~rcc@47.33.250.142) | |
| 23:24 | GodFather has left IRC (GodFather!~rcc@47.33.250.142, Ping timeout: 240 seconds) | |
| 23:28 | GodFather has joined IRC (GodFather!~rcc@47.33.250.142) | |
| 23:33 | ben_roose has left IRC (ben_roose!~roose@roose.cs.wichita.edu, Remote host closed the connection) | |