IRC chat logs for #ltsp on irc.libera.chat (webchat)
Channel log from 1 December 2022 (all times are UTC)
| 00:01 | vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20) | |
| 01:02 | vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20, Quit: leaving) | |
| 02:39 | oh207 has joined IRC (oh207!~oh207@pool-100-38-211-173.nycmny.fios.verizon.net) | |
| 03:18 | oh207 has left IRC (oh207!~oh207@pool-100-38-211-173.nycmny.fios.verizon.net, Ping timeout: 260 seconds) | |
| 06:22 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
| 06:59 | woernie has joined IRC (woernie!~werner@p5b2962ea.dip0.t-ipconnect.de) | |
| 09:45 | system_analyst[m has joined IRC (system_analyst[m!~systemana@2001:470:69fc:105::2:cea9) | |
| 09:57 | <system_analyst[m> On my ltsp client which has ubuntu 22.04 , I have LDAP authentication. User home directory is created on upon login. But any saved work does not servive reboot.. Also i have modified the config file /etc/pam.d/common-sessionsession required pam_mkhomedir.so skel=/etc/skel/ umask=0022
| |
| 10:03 | <alkisg1> system_analyst: ltsp creates the home directory and mounts it over the server via sshfs
| |
| 10:04 | so you shouldn't need pam_mkhomedir at all; better remove it in order to verify that ltsp homes work properly
| |
| 10:05 | After you login to a client, run mount and see if it was mounted with sshfs; I bet not
| |
| 10:05 | Then try ssh user@server and see that you can ssh there; I bet not, and that's why sshfs mounting fails
| |
| 10:09 | <system_analyst[m> any saved work in user home directory on ltsp client does not servive reboot. Does that mounting issue ?
| |
| 10:26 | <alkisg1> Yes, it means it wasn't mounted over sshfs
| |
| 10:26 | And you can verify it with the commands I mentioned above ^
| |
| 10:33 | Vercas6 has left IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection) | |
| 10:44 | <joris> networkbootin over wifi is really not an option is it?
| |
| 10:52 | <alkisg1> joris: it's doable, but wifi collsions are not the same as wired collisions; so 1 client will work, 2 will most work, and with e.g. 5 clients you'll have so many wifi collisions that it won't work
| |
| 10:57 | ...I mean, the wifi collisions reduce the wifi bandwidth dramatically, so it'll end up in the kbps range, making disk access to slow to be usable
| |
| 10:58 | <joris> @alkisg1 ah ok thanks didn't even consider that. This still a problem with wifi 5...
| |
| 10:58 | I get like 300/400mbit up/down on the client...
| |
| 10:59 | <alkisg1> joris: try to download a file from 10 clients at the same time. You won't get 30 mbit, you'll get less than 3 mbit
| |
| 11:00 | Switches have buffering to reduce collisions; wifi can't do that, there's no central switch there
| |
| 11:00 | <joris> yeah ok, but the server has a cable and there are multiple wifi routers
| |
| 11:00 | <alkisg1> If you have one wifi router for every two clients, then sure it will work
| |
| 11:00 | (on different channel)
| |
| 11:01 | <joris> ah ok, yeah, still very valid advice.
| |
| 11:01 | But I am not even there because bios and wifi card seem not to support netbootin...
| |
| 11:01 | over wifi
| |
| 11:02 | <alkisg1> You can also speed things up a bit by using local caching, to fetch x86_64.img in local storage and reuse it,and only use /home over wifi
| |
| 11:03 | There are usb ethernet adapters that motherboards and ipxe support
| |
| 11:03 | While for "internal laptop wifi", you'll need some local storage for boot manager and drivers
| |
| 11:04 | *scratch the usb ethernet remark, sorry, inappropriate
| |
| 11:04 | see https://github.com/ipxe/ipxe/discussions/354 for the ipxe support on this
| |
| 11:04 | While a bit of local storage for kernel + initrd, like 200 mb, can support any wifi device that linux supports
| |
| 11:05 | I.e. you'd load kernel/initrd locally, and all the rest remotely; and a script would then update the local kernel/initrd on image updates
| |
| 11:05 | <joris> I have a bunch of HP T620 they have 32GB of local storage so that's good
| |
| 11:05 | <alkisg1> You should also add the ltsp image locally then, it'll save you a lot of bandwidth
| |
| 11:06 | <joris> ok nice, maybe I should reconsider
| |
| 11:23 | Vercas6 has joined IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas) | |
| 11:25 | <joris> @alkisg1 http://labs.opinsys.com/blog/2014/01/31/how-to-boot-ltsp-client-from-harddrive-using-grub/ Is this tutorial too old or will it still more or less work... ?
| |
| 11:26 | Thanks for your time btw, very much appreciated!
| |
| 11:50 | Vercas62 has joined IRC (Vercas62!~Vercas@gateway/tor-sasl/vercas) | |
| 11:51 | Vercas6 has left IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas, Ping timeout: 255 seconds) | |
| 11:51 | Vercas62 is now known as Vercas6 | |
| 12:13 | Vercas6 has left IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection) | |
| 12:15 | Vercas6 has joined IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas) | |
| 12:43 | <alkisg1> joris: it's about right, but the boot parameters have changed, so grub.cfg will need 2 updated lines there
| |
| 12:48 | <joris> @alkisg1 ok cool! would be nice/fun to get it working. Hope I can figure out how to do it...
| |
| 12:49 | I followed the tutorial on the ltsp site and it made netbootin look so easy. Made it feasible to have multiple users, getting the same profile on muliple thinclients. While maintaining only one image
| |
| 12:50 | much better then the remote desktop solutions I had been looking at
| |
| 12:51 | <alkisg1> That's the goal! And it's been a success, e.g. more than 1000 schools here have ltsp installations that are maintained by a simple IT teacher, without linux knowledge
| |
| 12:57 | <joris> Well I am not even an IT teacher, so let's see how far I manage to get... :)
| |
| 15:48 | Vercas6 has left IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas, Quit: Ping timeout (120 seconds)) | |
| 15:59 | Vercas6 has joined IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas) | |
| 16:05 | Vercas6 has left IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection) | |
| 16:12 | DouglasGiovaniOe has joined IRC (DouglasGiovaniOe!~doguibnum@2001:470:69fc:105::1:929) | |
| 16:12 | <DouglasGiovaniOe> hello!
| |
| 16:12 | how are you
| |
| 16:15 | we have server with xubuntu 20.04 Lts. After last update, upgrade system, one mini pc, does not shows login screen. It does boot process but without screen (the sreen stay black)
| |
| 16:16 | last week was working well
| |
| 16:21 | Vercas6 has joined IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas) | |
| 16:24 | Vercas6 has left IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection) | |
| 16:25 | Vercas6 has joined IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas) | |
| 16:33 | shored has joined IRC (shored!~shored@user/shored) | |
| 17:02 | <alkisg1> Douglas Giovani Oechsler: the other clients work?
| |
| 17:02 | Also, if you revert the image, sudo ltsp image / -r, and reboot the client, does it work again?
| |
| 17:07 | vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20) | |
| 17:08 | <DouglasGiovaniOe> <alkisg1> "Also, if you revert the image..." <- sorry, yes other mini pc works well
| |
| 17:10 | <alkisg1> I would right click > open terminal via epoptes, and check /var/log/Xorg.0.log.old, and the output of dmesg. Maybe it didn't like the kernel update.
| |
| 17:10 | <DouglasGiovaniOe> <alkisg1> "Also, if you revert the image..." <- this process can broke the image seems after upgrade system packages?
| |
| 17:10 | <alkisg1> No, I don't think it's a problem with ltsp, but with an ubuntu update
| |
| 17:11 | I.e. if you had a local installation on a local disk, that mini pc would still get a black screen
| |
| 17:13 | Vercas6 has left IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection) | |
| 17:13 | <DouglasGiovaniOe> alkisg1: oww right, I will do the revert image process to try solve this
| |
| 17:15 | Vercas6 has joined IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas) | |
| 17:15 | <DouglasGiovaniOe> Thank you alkisg
| |
| 17:17 | <alkisg1> OK, but note that this is a temporary solution, it will happen again on the next update if you don't solve it properly
| |
| 17:18 | <DouglasGiovaniOe> I see, yes, maybe it better Upgrade distro for a new one
| |
| 17:19 | <alkisg1> Or do what I suggested with epoptes and xorg.log
| |
| 17:20 | Vercas6 has left IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection) | |
| 17:21 | Vercas6 has joined IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas) | |
| 17:22 | <DouglasGiovaniOe> alkisg1: so, how do I work about the xorg.log result?
| |
| 17:23 | let me see the server now to see wait
| |
| 17:24 | cannot operate now
| |
| 17:29 | Vercas6 has left IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas, Quit: Ping timeout (120 seconds)) | |
| 17:34 | <alkisg1> Douglas Giovani Oechsler: when you're able to operate, open epoptes, see the client, right click open a terminal, and I'll tell you the commands there
| |
| 18:03 | <DouglasGiovaniOe> <alkisg1> "Douglas Giovani Oechsler: when..." <- Right, I will try some moment and tell you, thanks
| |
| 18:14 | woernie has left IRC (woernie!~werner@p5b2962ea.dip0.t-ipconnect.de, Quit: http://quassel-irc.org - Chat comfortably. Anywhere.) | |
| 22:17 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |