IRC chat logs for #ltsp on irc.libera.chat (webchat)
Channel log from 18 May 2023 (all times are UTC)
| 00:36 | vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:50, Quit: leaving) | |
| 00:52 | peko[m] has joined IRC (peko[m]!~pekomatri@2001:470:69fc:105::3:5cd3) | |
| 01:20 | vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20) | |
| 02:09 | Vercas69475 has left IRC (Vercas69475!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection) | |
| 02:09 | Vercas69475 has joined IRC (Vercas69475!~Vercas@gateway/tor-sasl/vercas) | |
| 03:40 | vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20, Quit: leaving) | |
| 04:12 | system_analyst[m has joined IRC (system_analyst[m!~systemana@2001:470:69fc:105::2:cea9) | |
| 04:13 | <system_analyst[m> I am facing the challenge while installing the NS2 on my ltsp server which is ubuntu 22.04 .
| |
| 04:13 | <alkisg> What challenge?
| |
| 04:14 | <system_analyst[m> I followed the step cd /srv/ltsp ; chroot jammy /
| |
| 04:19 | inside that extracted the tar ball . and ns-allinone-2.35 folder copied to every users home folder ie /home/user/.... this folder is visible from sever side inside the chroot at path /home/username/ ns-allinone-2.35 , but problem is that when i build the image and boot it on the client machine to my surprise there inside the user home folder these ns-allinone-2.35 folder is not visible ... ... to execute the ns2 i have to set
| |
| 04:19 | envirnment variable inside the .bashrc file but .. these ns-allinone-2.35 folder is not visble hence cant set path ..
| |
| 04:34 | <alkisg> Chroots are hard to manage. Use a VM instead, it'll make things easier for you
| |
| 04:34 | And even easier is the "chrootless" method, where a clone of the server installation is used
| |
| 04:35 | Note that /home on the clients comes from /home on the server. NOT from /srv/ltsp/image/home
| |
| 04:36 | <system_analyst[m> You mean say I have boot VM image there on client ?
| |
| 04:36 | * I have to boot, * boot preinstalled ns2 VM image
| |
| 04:51 | Fuzai has joined IRC (Fuzai!~quassel@50.34.48.211) | |
| 05:01 | <alkisg> No, I mean instead of using an /srv/ltsp/image chroot, to use a /srv/ltsp/virtualbox-image.vmdk image, see the documentation: http://ltsp.org/docs/installation/#maintaining-a-client-image
| |
| 05:01 | In the documentation, 3 options are documented, chrootless, vm and chroot; you chose the hardest one...
| |
| 05:13 | <system_analyst[m> okay i will give my try ... i will craete an vm in virtual box and then i will install ns2 software on it . for authentication i will also installed ldap lib pam & then export that vmdk image to ltsp server on path /srv/ltsp ; and them build it using command ltsp image /srv/ltsp/vmimage.vmdk ; and then boot it . If i am wrong please correct me .
| |
| 05:14 | <alkisg> system_analyst: yup, that's what I was suggesting
| |
| 05:14 | <system_analyst[m> thank you for your guidance .... i will try it now.
| |
| 05:41 | In above case instead of vmdk image if proxmox vm running ubuntu 18.04 LTS qcow2 image will work ? because ltsp server is running on ubuntu 22.04 ?
| |
| 05:41 | <alkisg> qcow won't work, but raw will work
| |
| 05:42 | You have proxmox, and on top of it you have ltsp server 22.04, and you want the clients to boot ubuntu 18.04?
| |
| 05:42 | wyre is back | |
| 05:44 | <system_analyst[m> yes . will version issue will cause conflict? because I want exata and ns2 on my client computer . this software can be comfortably installed on ubuntu 18.04 .
| |
| 05:47 | <alkisg> No it won't cause a conflict. But it would be easier to use the ubuntu 18.04 vm as the ltsp server. Why do you want a separate ltsp server?
| |
| 05:51 | <system_analyst[m> Initially by reading the installation guide on ltsp website I created ltsp server on ubuntu 22.04 and choose the chroot method to maintain client image .
| |
| 05:51 | <alkisg> OK, if you don't have a special reason, then by listening to your use case, I propose that you abandon that route and just use an ubuntu 18.04 VM as a "chrootless" server and a template for the clients at the same time
| |
| 05:52 | I.e. start by installing an ubuntu 18.04 vm and make it work exactly as you want a client to work. THEN just install ltsp on top of it and make it an ltsp server
| |
| 05:53 | <system_analyst[m> okay...
| |
| 05:54 | i will go for this .
| |
| 06:35 | wyre is now away: Auto away at Thu May 18 06:35:28 2023 UTC | |
| 06:48 | adamjurkiewiczpy has joined IRC (adamjurkiewiczpy!~adamjurki@2001:470:69fc:105::f1a6) | |
| 06:48 | <adamjurkiewiczpy> Hi, I am back again 😉
| |
| 06:50 | <alkisg> o/
| |
| 06:51 | * adamjurkiewiczpy uploaded an image: (600KiB) < https://libera.ems.host/_matrix/media/v3/download/matrix.org/IlTSsUhMSiIIxqPDNcLoPpyG/Screenshot_20230518_085046.png > | |
| 06:51 | <adamjurkiewiczpy> Im trying to run my new server in my School.
| |
| 06:55 | <alkisg> Nice :)
| |
| 08:14 | <adamjurkiewiczpy> ok. 1st problem - not regarding to LTSP directly. I have HP EliteBook 840 G3 laptop and cannot set in BIOS UEFI network boot. I can only set Legacy PXE, which works fine with LTSP, but on HDD there is Windows installed in UEFI mode, So I have LTSP and Windows on hdd - but I cannot run ltsp or windows without BIOS modification... . I would like to set UEFI network boot to be able to cancel boot process and start from hard drive windows
| |
| 08:14 | (for other teacher, who don't like Linux)...
| |
| 08:25 | <alkisg> adam.jurkiewicz.pythonista: see https://github.com/ltsp/ltsp/issues/825
| |
| 08:28 | <adamjurkiewiczpy> Thanks alkisg - some job to do with it... fuck HP once again - I don't love their BIOSes....
| |
| 08:32 | From other hand... Someone tried to install ChromeOS Flex on Legacy mode BIOS?
| |
| 08:41 | adrianorg has left IRC (adrianorg!~adrianorg@debian/adrianorg, Ping timeout: 268 seconds) | |
| 08:42 | adrianorg has joined IRC (adrianorg!~adrianorg@debian/adrianorg) | |
| 09:50 | Fuzai has left IRC (Fuzai!~quassel@50.34.48.211, Ping timeout: 240 seconds) | |
| 10:06 | Vercas69475 has left IRC (Vercas69475!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection) | |
| 10:07 | Vercas69475 has joined IRC (Vercas69475!~Vercas@gateway/tor-sasl/vercas) | |
| 10:11 | Fuzai has joined IRC (Fuzai!~quassel@50.34.48.211) | |
| 10:11 | Fuzai has left IRC (Fuzai!~quassel@50.34.48.211, Client Quit) | |
| 14:59 | wyre is back | |
| 15:00 | wyre is now away: Auto away at Thu May 18 15:00:12 2023 UTC | |
| 15:20 | vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:50) | |
| 15:21 | wyre is back | |
| 15:42 | wyre is now away: Auto away at Thu May 18 15:42:05 2023 UTC | |
| 16:00 | leksmut[m] has left IRC (leksmut[m]!~leksmutma@2001:470:69fc:105::1:b3f, Remote host closed the connection) | |
| 19:25 | peko[m] has left IRC (peko[m]!~pekomatri@2001:470:69fc:105::3:5cd3, Excess Flood) | |
| 22:02 | vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:50, Quit: leaving) | |
| 23:01 | vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20) | |
| 23:55 | vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20, Quit: leaving) | |