IRC chat logs for #ltsp on irc.libera.chat (webchat)
Channel log from 10 August 2022 (all times are UTC)
| 01:17 | jgee has left IRC (jgee!~jgee@186.80.49.20, Quit: The Lounge - https://thelounge.chat) | |
| 01:17 | jgee has joined IRC (jgee!~jgee@186.80.49.20) | |
| 02:14 | vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20, Quit: leaving) | |
| 03:03 | oh207 has joined IRC (oh207!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net) | |
| 03:11 | oh207_ has joined IRC (oh207_!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net) | |
| 03:11 | oh207 has left IRC (oh207!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net, Ping timeout: 268 seconds) | |
| 03:18 | oh207_ has left IRC (oh207_!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net, Ping timeout: 268 seconds) | |
| 04:54 | quinox has left IRC (quinox!~quinox@ghost.qtea.nl, Quit: WeeChat 3.5) | |
| 04:57 | quinox has joined IRC (quinox!~quinox@ghost.qtea.nl) | |
| 05:18 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
| 05:37 | woernie_ has left IRC (woernie_!~werner@p5b296f43.dip0.t-ipconnect.de, Read error: Connection reset by peer) | |
| 05:37 | woernie has joined IRC (woernie!~werner@p5b296f43.dip0.t-ipconnect.de) | |
| 07:11 | alkisg_web has joined IRC (alkisg_web!~alkisg_we@2a02:587:7524:5a00:c24a:ff:fe02:bc1e) | |
| 07:13 | <alkisg_web> !last
| |
| 07:13 | <ltspbot`> [08:22:36] <mikaela> yes, gives id 1000 assigned
| |
| 07:17 | alkisg_web has left IRC (alkisg_web!~alkisg_we@2a02:587:7524:5a00:c24a:ff:fe02:bc1e, Quit: Ping timeout (120 seconds)) | |
| 07:19 | alkisg_web has joined IRC (alkisg_web!~alkisg_we@2a02:587:7524:5a00:c24a:ff:fe02:bc1e) | |
| 07:20 | mrkii[m] has joined IRC (mrkii[m]!~mrkiimatr@2001:470:69fc:105::2:606b) | |
| 07:20 | <mrkii[m]> @alkisg how do I set up x11? its not set up
| |
| 07:21 | <alkisg> Hi mrkii , run that command: sudo apt install x11vnc
| |
| 07:22 | <mrkii[m]> Hi, its already installed, newest version, just I am not sure its set up safely or well
| |
| 07:22 | <alkisg> If you run this command, does it show any errors? x11vnc -connect alkisg.ltsp.org
| |
| 07:22 | You need to be connected graphically to the server for that to work though, not via ssh
| |
| 07:23 | <mrkii[m]> oh, that command in terminal?
| |
| 07:23 | <alkisg> Yes, you connect normally to the GUI, you open a terminal there, and you run that command to share your screen with me
| |
| 07:25 | mrkii: can you login to a fat client, open a terminal, and run that command from there as well, so that I can compare?
| |
| 07:26 | <mrkii[m]> we have thin clients only, its the ltsp5, old build
| |
| 07:26 | <alkisg> LTSP5 has defaulted to fat clients since 10 years ago
| |
| 07:26 | In any case, login to a client and run that command and I'll see
| |
| 07:27 | You have many images and I'm not sure which one is in use
| |
| 07:27 | alkisg_web has left IRC (alkisg_web!~alkisg_we@2a02:587:7524:5a00:c24a:ff:fe02:bc1e, Quit: Client closed) | |
| 07:42 | <alkisg> mrkii: I'm talking to you in private messages, are you still here?
| |
| 08:33 | mikaela has joined IRC (mikaela!~mikaela@178.46.130.6) | |
| 08:33 | <mikaela> Hello everyone, I solved the problem by writing a script. Now another question, automatic mounting and connection with user data to a network folder and how to change the standard home folder of a user who is included in the domain account. It is created along the path /home/DOMAIN/. I wanted to make the home folder created in the network folder
| |
| 08:33 | and used from there.
| |
| 08:35 | On Windows, the network folder is now automatically mounted. First you need to do automount on linux
| |
| 08:39 | woernie has left IRC (woernie!~werner@p5b296f43.dip0.t-ipconnect.de, Ping timeout: 268 seconds) | |
| 08:39 | woernie has joined IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de) | |
| 08:45 | woernie has left IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de, Ping timeout: 268 seconds) | |
| 08:45 | woernie has joined IRC (woernie!~werner@p5b296f43.dip0.t-ipconnect.de) | |
| 09:46 | Vercas6 has left IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection) | |
| 09:49 | Vercas6 has joined IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas) | |
| 10:43 | we6jbo has joined IRC (we6jbo!~we6jbo@2603-8001-5b43-4000-83c8-aaba-893b-7da1.res6.spectrum.com) | |
| 10:53 | we6jbo has left IRC (we6jbo!~we6jbo@2603-8001-5b43-4000-83c8-aaba-893b-7da1.res6.spectrum.com, Ping timeout: 244 seconds) | |
| 11:08 | we6jbo has joined IRC (we6jbo!~we6jbo@2603-8001-5b43-4000-c179-b209-a6f7-4bd2.res6.spectrum.com) | |
| 11:49 | <alkisg> mikaela: if you do not want to use the standard sshfs, it would probably be easier to set PAM_AUTH_TYPE=0 in ltsp.conf, and use pam_mount to mount samba shares or whatever else you prefer
| |
| 11:52 | <mikaela> I just figured out how to do it, I wrote the line nano /etc/security/pam_mount.conf.xml along this path
| |
| 11:52 | <volume fstype="cifs" server="ip" path="home" mountpoint="/disk" options="user,owner,noexec,iocharset=utf8,rw" /> and the disk is mounted, as well as in nano / etc/adduser.conf changed the way to create the home folder
| |
| 11:53 | <alkisg> Yeh, so just disable the ltsp pam so that it doesn't complain
| |
| 11:53 | There's a discussion about it on github
| |
| 11:54 | Search for PAM_AUTH_TYPE and you'll find it
| |
| 11:56 | <mikaela> Thanks, I'll read
| |
| 12:10 | we6jbo has left IRC (we6jbo!~we6jbo@2603-8001-5b43-4000-c179-b209-a6f7-4bd2.res6.spectrum.com, Quit: Leaving.) | |
| 12:53 | Vercas6 has left IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection) | |
| 12:53 | Vercas6 has joined IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas) | |
| 13:07 | Vercas6 has left IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection) | |
| 13:08 | Vercas6 has joined IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas) | |
| 14:32 | mikaela has left IRC (mikaela!~mikaela@178.46.130.6, Quit: Client closed) | |
| 14:38 | oh207_ has joined IRC (oh207_!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net) | |
| 14:44 | oh207 has joined IRC (oh207!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net) | |
| 14:45 | oh207_ has left IRC (oh207_!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net, Ping timeout: 268 seconds) | |
| 14:51 | oh207_ has joined IRC (oh207_!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net) | |
| 14:53 | oh207 has left IRC (oh207!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net, Ping timeout: 268 seconds) | |
| 15:00 | oh207 has joined IRC (oh207!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net) | |
| 15:01 | oh207_ has left IRC (oh207_!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net, Ping timeout: 252 seconds) | |
| 15:04 | oh207_ has joined IRC (oh207_!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net) | |
| 15:04 | oh207 has left IRC (oh207!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net, Ping timeout: 244 seconds) | |
| 15:20 | oh207_ has left IRC (oh207_!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net, Ping timeout: 268 seconds) | |
| 15:32 | Vercas6 has left IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection) | |
| 15:33 | Vercas6 has joined IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas) | |
| 15:42 | we6jbo has joined IRC (we6jbo!~we6jbo@2603-8001-5b43-4000-0316-d955-d46e-a19d.res6.spectrum.com) | |
| 15:43 | vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20) | |
| 15:59 | N0rbert has joined IRC (N0rbert!~N0rbert@broadband-90-154-72-46.ip.moscow.rt.ru) | |
| 16:02 | <N0rbert> Hello!
| |
| 16:02 | That is me again. I'm having problems with understanding of needed changes in the configuration. I have LTSP5 with NBD. I need to allow LTSP fat clients to dual-boot - Ubuntu and Debian. So I plan to have two images in /opt/ltsp/images (ubuntu.img, debian.img) and two corresponding folders inside /var/lib/tftpboot . Is it possible at all? Which
| |
| 16:02 | configuration changes should I apply?
| |
| 16:04 | Is it possible to use https://ltsp.org/guides/pxelinux.txt with LTSP5?
| |
| 16:06 | <alkisg> N0rbert: in general, for ltsp5, you're on your own; hopefully you'll get too lazy fighting the issues and just "go with the flow" and use the latest ltsp :)
| |
| 16:06 | It is possible, ltsp5 did generate pxelinux menus for that
| |
| 16:07 | But the process was too convoluted, I don't think it was ever documented properly
| |
| 16:07 | You had to run things inside and outside the chroots to generate the menu
| |
| 16:07 | The pxelinux guide you pasted is for the new ltsp, it doesn't apply to the old one
| |
| 16:08 | And it's not even needed in the new ltsp, as it's using ipxe by default
| |
| 16:08 | That page is only for rare cases where some adapters can't use ipxe, like 1% of the cases
| |
| 16:09 | <N0rbert> Ok, understood. I'm running on old legacy hardware without UEFI.
| |
| 16:10 | In dnsmasq.conf I currently have "dhcp-option=17,/opt/ltsp/amd64" . If I understand correctly, it should be dynamic.
| |
| 16:11 | <vagrantc> doesn't require UEFI
| |
| 16:11 | <N0rbert> I tried to put
| |
| 16:11 | pxe-service=X86PC, "Boot Ubuntu", /ltsp/ubuntu/pxelinux
| |
| 16:11 | pxe-service=X86PC, "Boot Debian", /ltsp/debian/pxelinux
| |
| 16:11 | client boots, but can't find NBD export.
| |
| 16:12 | <alkisg> The nbd configuration was in /etc/nbd-server
| |
| 16:12 | Note what vagrantc said, the new ltsp isn't heavier than the old one nor does it require uefi
| |
| 16:12 | <vagrantc> if you're doing different chroots based on different pxelinux configurations, you'll also need to specify a different root-path or nbdroot or whatever
| |
| 16:13 | but ... seriously, this is *so* much simpler with modern LTSP versions
| |
| 16:14 | <alkisg> Btw, I made sure the new ltsp runs from jessie and xenial onwards; you can use it even with old distributions
| |
| 16:14 | Vercas6 has left IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas, Write error: Connection reset by peer) | |
| 16:15 | Vercas6 has joined IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas) | |
| 16:15 | <N0rbert> What should be next step after defining two exports in /etc/nbd-server for LTSP5?
| |
| 16:15 | How should I make NBDroot dynamic?
| |
| 16:16 | (I'll try newer LTSP later, still hoping to get needed configuration on LTSP5)
| |
| 16:22 | <vagrantc> N0rbert: what do you mean by "dynamic" ?
| |
| 16:23 | <N0rbert> I suppose that I can't use the same
| |
| 16:23 | <vagrantc> N0rbert: you'll need to adjust the pxelinux configuration to explicitly specify which NBD server/path/etc. to use
| |
| 16:23 | <N0rbert> dhcp-option=17,/opt/ltsp/amd64
| |
| 16:23 | for two images.
| |
| 16:24 | <vagrantc> if you're using the PXE menu, you can't specify it via dhcp
| |
| 16:24 | you have to specify it in the pxelinux configuration
| |
| 16:24 | * vagrantc is done repeating the same thing | |
| 16:26 | N0rbert has left IRC (N0rbert!~N0rbert@broadband-90-154-72-46.ip.moscow.rt.ru, Quit: Client closed) | |
| 16:26 | N0rbert has joined IRC (N0rbert!~N0rbert@broadband-90-154-72-46.ip.moscow.rt.ru) | |
| 16:35 | <N0rbert> Really I can replace NBD with AOE or NFS, if this will help to get result on LTSP5.
| |
| 16:39 | <vagrantc> you will have the exact same issue
| |
| 16:39 | either that, or you give different dhcp responses per-client, but then you can select at boot time
| |
| 16:39 | then you *cannot* select at boot time between, say ubuntu or debian
| |
| 16:40 | sorry for the typo
| |
| 16:42 | <N0rbert> So my idea seems to be technically impossible with LTSP5, right?
| |
| 16:44 | <vagrantc> it is totally possible, i've repeated what you need to do three times now
| |
| 16:46 | N0rbert: can you re-read the earlier conversation?
| |
| 16:49 | <N0rbert> Really I can't understand which configuration files should I change and how many changes I should apply to them...
| |
| 16:52 | <vagrantc> which configuration did i suggest you change?
| |
| 16:57 | or just follow the documentation for current LTSP, which has the relevent functionality well implemented, documented, etc.
| |
| 16:58 | <N0rbert> Where can I find relevant docs for LTSP5?
| |
| 16:59 | <vagrantc> this was never well documented for LTSP5
| |
| 16:59 | and, largely my fault, is way more complicated than it needed to be
| |
| 17:00 | you'll need to understand syslinux/pxelinux documentation and how to pass kernel arguments
| |
| 17:01 | and maybe dive into the initramfs-tools code to figure out what arguments to pass
| |
| 17:02 | so, you could learn how to do this and write some documentation for LTSP5... but given that all that functionality is already well documented for current LTSP ... why do you need LTSP5?
| |
| 17:04 | <N0rbert> Currently I maintain 120 machines with Ubuntu MATE 16.04 LTS in two buildings and LTSP5. Some of them have custom kernel options is pxelinux.cfg, some of them have hacks in lts.conf. Will I lose some functionality if I upgrade to modern LTSP 22.01?
| |
| 17:05 | And another question - can I boot some RPM-based distro as fat-client - for example PCLinuxOS?
| |
| 17:06 | <vagrantc> N0rbert: so what is it you're trying to add? another boot option?
| |
| 17:07 | you could install the new environment with current LTSP, and keep your old environment as-is.
| |
| 17:07 | and then you can compare the differences
| |
| 17:07 | <N0rbert> Right, I need to have this 16.04 as fallback, and add here 18.04 LTS with buster.
| |
| 17:08 | <vagrantc> what is "18.04 LTS with buster" ?
| |
| 17:08 | <N0rbert> Three systems: 16.04, 18.04, debian buster.
| |
| 17:09 | and maybe PCLinuxOS.
| |
| 17:10 | <vagrantc> with adding new things, why are you starting with old releases (e.g. ubuntu 18.04, debian buster) ?
| |
| 17:10 | Vercas6 has left IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas, Ping timeout: 268 seconds) | |
| 17:10 | <vagrantc> don't know much about pclinuxos
| |
| 17:10 | <N0rbert> Because of Zenmap, Qt4 and some other stuff.
| |
| 17:12 | In the chat meanwhile I have installed chrootless LTSP 22.01. It looks promising. Will test it further. Thanks!
| |
| 17:12 | <vagrantc> N0rbert: so, basically, for each pxelinux configuration, you need to add an nbdroot= for the appropriate root .... e.g. /opt/ltsp/ubuntu-16.04, /opt/ltsp/ubuntu-18.04, /opt/ltsp/debian-buster, etc.
| |
| 17:13 | <N0rbert> Ok, I will read syslinux/pxelinux docs to get LTSP5 path solved. Thanks!
| |
| 17:13 | <vagrantc> and configure /etc/nbd-server/conf.d/* appropriately ... and ... probably a lot of other things i'm forgetting ... it's been a while
| |
| 17:14 | you'll need to run ltsp-update-kernels on the server whenever you update one of the images
| |
| 17:16 | <alkisg> N0rbert: in general you should be able to use the new ltsp even with your existing chroots
| |
| 17:16 | You don't even need to uninstall ltsp5
| |
| 17:19 | <N0rbert> Thanks, alkisg. I'll try on VM. Looks promising.
| |
| 17:29 | we6jbo has left IRC (we6jbo!~we6jbo@2603-8001-5b43-4000-0316-d955-d46e-a19d.res6.spectrum.com, Remote host closed the connection) | |
| 17:40 | N0rbert has left IRC (N0rbert!~N0rbert@broadband-90-154-72-46.ip.moscow.rt.ru, Ping timeout: 252 seconds) | |
| 17:50 | N0rbert has joined IRC (N0rbert!~N0rbert@broadband-90-154-72-46.ip.moscow.rt.ru) | |
| 17:51 | <N0rbert> With new LTSP, if image is a VM:
| |
| 17:51 | 1. which kernel it will use?
| |
| 17:51 | 2. how it is served (squash via NFS)?
| |
| 17:53 | <alkisg> it will use the vm kernel, and 2=yes
| |
| 17:54 | <N0rbert> This is super cool feature!
| |
| 17:57 | Will this VM image fetch ltsp.conf on successful boot?
| |
| 17:58 | <alkisg> yes, via ltsp.img
| |
| 17:59 | <N0rbert> Great, I'll investigate it further then.
| |
| 17:59 | It is great to have Memtest preconfigured, but 5.01 seems a bit outdated.
| |
| 18:03 | <alkisg> It's using your own
| |
| 18:03 | It doesn't ship an ltsp-specific one
| |
| 18:04 | <N0rbert> Oh, thanks. Understood. It is from host os.
| |
| 18:05 | <alkisg> No sorry scratch that, I think I've used memtest.0 from ipxe, that can return to the BIOS PXE stack on exit
| |
| 18:06 | (if you have ltsp-binaries installed)
| |
| 18:07 | <N0rbert> ltsp-binaries are installed, yes
| |
| 18:10 | LTSP5 has ltsp-client scripts in the image. How old chroots will operate with new LTSP?
| |
| 18:11 | <alkisg> The new ltsp doesn't need code in the image at all. It injects the new ltsp via ltsp.img
| |
| 18:11 | (the additional initramfs)
| |
| 18:11 | So you can boot an old ltsp5 image or an ubuntu-live.iso as is, without installing ltsp-client in it
| |
| 18:12 | That said, ltsp is available for older distributions via the ppa
| |
| 18:14 | <N0rbert> Ok, understood.
| |
| 18:17 | Do I need to prepare ubuntu-live.iso "before" running ltsp image ubuntu-live?
| |
| 18:19 | <alkisg> You don't need to run ltsp image at all
| |
| 18:19 | It can serve it directly without any preparation; put it in /srv/ltsp/images/x86_64.img and run ltsp kernel
| |
| 18:20 | (dont symlink it due to nfs restrictions, put it there and rename it)
| |
| 18:31 | <N0rbert> It really works. Thanks for all your efforts!
| |
| 18:32 | N0rbert has left IRC (N0rbert!~N0rbert@broadband-90-154-72-46.ip.moscow.rt.ru, Quit: Client closed) | |
| 18:53 | <vagrantc> another satisfied customer :)
| |
| 18:54 | * alkisg bets tomorrow he'll be back with more pxelinux/ltsp5 questions :D | |
| 19:02 | <vagrantc> heh
| |
| 20:21 | we6jbo has joined IRC (we6jbo!~we6jbo@12.153.230.158) | |
| 20:29 | we6jbo has left IRC (we6jbo!~we6jbo@12.153.230.158, Ping timeout: 268 seconds) | |
| 21:00 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |
| 21:20 | oh207_ has joined IRC (oh207_!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net) | |
| 21:28 | oh207 has joined IRC (oh207!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net) | |
| 21:28 | oh207_ has left IRC (oh207_!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net, Ping timeout: 268 seconds) | |
| 21:39 | oh207 has left IRC (oh207!~oh207@pool-72-69-251-225.nycmny.fios.verizon.net, Ping timeout: 268 seconds) | |
| 23:24 | Lantizia has left IRC (Lantizia!~Lantizia@user/lantizia, Ping timeout: 264 seconds) | |
| 23:29 | Lantizia has joined IRC (Lantizia!~Lantizia@195.62.201.126) | |