IRC chat logs for #ltsp on irc.libera.chat (webchat)
Channel log from 19 August 2022 (all times are UTC)
| 00:17 | Vercas6 has left IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection) | |
| 00:17 | Vercas6 has joined IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas) | |
| 00:58 | we6jbo has joined IRC (we6jbo!~we6jbo@2603-8001-5b43-4000-96c4-0f3d-d74a-7b83.res6.spectrum.com) | |
| 01:36 | we6jbo has left IRC (we6jbo!~we6jbo@2603-8001-5b43-4000-96c4-0f3d-d74a-7b83.res6.spectrum.com) | |
| 03:45 | we6jbo has joined IRC (we6jbo!~we6jbo@2603-8001-5b43-4000-7b04-ebbb-b951-26c7.res6.spectrum.com) | |
| 03:56 | we6jbo has left IRC (we6jbo!~we6jbo@2603-8001-5b43-4000-7b04-ebbb-b951-26c7.res6.spectrum.com, Quit: Leaving.) | |
| 04:11 | vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20, Quit: leaving) | |
| 06:47 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
| 07:52 | Vercas68 has joined IRC (Vercas68!~Vercas@gateway/tor-sasl/vercas) | |
| 07:54 | Vercas6 has left IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas, Ping timeout: 268 seconds) | |
| 07:54 | Vercas68 is now known as Vercas6 | |
| 08:32 | SysadmOFF has joined IRC (SysadmOFF!~SysadmOFF@62-137-127.netrun.cytanet.com.cy) | |
| 08:32 | SysadmOFF has left IRC (SysadmOFF!~SysadmOFF@62-137-127.netrun.cytanet.com.cy, Client Quit) | |
| 08:33 | SysadmOFF has joined IRC (SysadmOFF!~SysadmOFF@62-137-127.netrun.cytanet.com.cy) | |
| 08:33 | SysadmOFF has left IRC (SysadmOFF!~SysadmOFF@62-137-127.netrun.cytanet.com.cy, Client Quit) | |
| 11:07 | Vercas6 has left IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection) | |
| 11:07 | SysadmOFF has joined IRC (SysadmOFF!~SysadmOFF@62-137-127.netrun.cytanet.com.cy) | |
| 11:07 | Vercas6 has joined IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas) | |
| 11:25 | Vercas6 has left IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection) | |
| 11:26 | Vercas6 has joined IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas) | |
| 12:18 | we6jbo has joined IRC (we6jbo!~we6jbo@2603-8001-5b43-4000-4d48-4ca1-73b2-8aa4.res6.spectrum.com) | |
| 12:33 | SysadmOFF has left IRC (SysadmOFF!~SysadmOFF@62-137-127.netrun.cytanet.com.cy, Quit: Client closed) | |
| 13:03 | Vercas6 has left IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas, Quit: Ping timeout (120 seconds)) | |
| 13:04 | Vercas6 has joined IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas) | |
| 13:40 | jgee has left IRC (jgee!~jgee@186.80.49.20, Quit: The Lounge - https://thelounge.chat) | |
| 13:41 | jgee has joined IRC (jgee!~jgee@186.80.49.20) | |
| 14:03 | we6jbo has left IRC (we6jbo!~we6jbo@2603-8001-5b43-4000-4d48-4ca1-73b2-8aa4.res6.spectrum.com, Ping timeout: 244 seconds) | |
| 14:08 | SysadmOFF has joined IRC (SysadmOFF!~SysadmOFF@62-137-127.netrun.cytanet.com.cy) | |
| 14:19 | Vercas6 has left IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas, Quit: Ping timeout (120 seconds)) | |
| 14:20 | Vercas6 has joined IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas) | |
| 14:21 | we6jbo has joined IRC (we6jbo!~we6jbo@2603-8001-5b43-4000-1023-20a7-7c93-e81b.res6.spectrum.com) | |
| 14:57 | we6jbo has left IRC (we6jbo!~we6jbo@2603-8001-5b43-4000-1023-20a7-7c93-e81b.res6.spectrum.com) | |
| 15:13 | Vercas6 has left IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas, Quit: Ping timeout (120 seconds)) | |
| 15:14 | Vercas6 has joined IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas) | |
| 15:23 | Vercas6 has left IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas, Quit: Ping timeout (120 seconds)) | |
| 15:37 | Lantizia has left IRC (Lantizia!~Lantizia@user/lantizia, Remote host closed the connection) | |
| 15:39 | vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20) | |
| 15:44 | Lantizia has joined IRC (Lantizia!~Lantizia@195.62.201.126) | |
| 17:08 | SysadmOFF has left IRC (SysadmOFF!~SysadmOFF@62-137-127.netrun.cytanet.com.cy, Quit: Client closed) | |
| 19:31 | SysadmOFF has joined IRC (SysadmOFF!~SysadmOFF@188.138.239.8) | |
| 19:32 | <SysadmOFF> Hi
| |
| 19:32 | Found an issue with ltsp an Solus
| |
| 19:33 | since its not possible to install ltsp on that OS, i have used vmdk-flat from VBox and created symlink in existing ltsp server
| |
| 19:33 | during Solus boot i get an error
| |
| 19:33 | https://ibb.co/Nm4ptWY
| |
| 19:35 | this part of ltsp is trying to create symlink:
| |
| 19:35 | # Symlink the service; use absolute symlink due to /usr/lib migration
| |
| 19:35 | re ln -sf /usr/share/ltsp/common/service/ltsp.service "$dst/lib/systemd/system/ltsp.service"
| |
| 19:35 | re ln -sf ../ltsp.service "$dst/lib/systemd/system/multi-user.target.wants/ltsp.service"
| |
| 19:35 | but there is no /lib/systemd/ in SOlus
| |
| 19:35 | systemd in /usr/lib/
| |
| 19:40 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |
| 19:51 | <SysadmOFF> this part is loaded by ltsp.img, right? so if i will replace "$dst/lib/systemd/system/ltsp.service" with "$dst/usr/lib/systemd/system/ltsp.service" and run "ltsp initrd" - it will generate new ltsp.img with new path.
| |
| 19:52 | correct?
| |
| 19:53 | <vagrantc> you can presumably symlink /lib -> /usr/lib and then ... it should maybe work
| |
| 19:53 | what is solus?
| |
| 19:53 | <SysadmOFF> but /lib slaready exist
| |
| 19:53 | <vagrantc> e.g. what's it based on or whatever
| |
| 19:53 | wow, that's weird.
| |
| 19:53 | <SysadmOFF> solus - OS based on.....dont know
| |
| 19:53 | something strange
| |
| 19:54 | <vagrantc> does lib just contain symlinks to usr/lib ? or does it contain regular files?
| |
| 19:54 | <SysadmOFF> but its booting in 18 sec .Thats why i want to test it for PXE
| |
| 19:54 | nope
| |
| 19:56 | a /lib is sym to /lib64
| |
| 19:56 | ls -la lib64
| |
| 19:56 | total 48
| |
| 19:56 | drwxr-xr-x 8 root root 4096 Aug 18 21:58 .
| |
| 19:56 | drwxr-xr-x 20 root root 4096 Aug 18 22:08 ..
| |
| 19:57 | drwxr-xr-x 2 root root 4096 Aug 18 22:02 apparmor
| |
| 19:57 | drwxr-xr-x 99 root root 20480 Aug 18 22:00 firmware
| |
| 19:57 | lrwxrwxrwx 1 root root 31 Aug 18 21:58 ld-linux-x86-64.so.2 -> /usr/lib64/ld-linux-x86-64.so.2
| |
| 19:57 | drwxr-xr-x 4 root root 4096 Aug 18 22:07 modules
| |
| 19:57 | drwxr-xr-x 3 root root 4096 Aug 18 22:06 security
| |
| 19:57 | drwxr-xr-x 2 root root 4096 Aug 18 21:59 udev
| |
| 19:57 | drwxr-xr-x 2 root root 4096 Aug 18 22:06 xtables
| |
| 19:57 | <vagrantc> how quaint
| |
| 19:58 | https://en.wikipedia.org/wiki/Solus_(operating_system) ?
| |
| 19:58 | <SysadmOFF> ls -la /usr/lib64/systemd/system|grep ssh
| |
| 19:58 | -rw-r--r-- 1 root root 206 Mar 27 00:25 sshd.service
| |
| 19:58 | -rw-r--r-- 1 root root 176 Mar 27 00:25 sshd@.service
| |
| 19:58 | yes, this one
| |
| 19:59 | so here is a path to services
| |
| 20:02 | <vagrantc> so put a symlink into /lib64/systemd -> /usr/lib/systemd ... ?
| |
| 20:03 | you can even do it from ltsp.conf probably early enough
| |
| 20:03 | done recall the various phases, but should be in the ltsp.conf manpage or other documentation
| |
| 20:08 | <SysadmOFF> i think symlink will not work
| |
| 20:08 | <vagrantc> because?
| |
| 20:09 | <SysadmOFF> maybe im just tired
| |
| 20:09 | but im trying this localy
| |
| 20:09 | ls -la
| |
| 20:09 | total 20
| |
| 20:09 | drwxr-xr-x 4 root root 4096 Aug 19 23:06 .
| |
| 20:09 | drwxr-xr-x 21 root root 4096 Aug 19 23:05 ..
| |
| 20:09 | -rw-r--r-- 1 root root 4 Aug 19 23:06 1.txt
| |
| 20:09 | drwxr-xr-x 2 root root 4096 Aug 19 23:06 lib64
| |
| 20:09 | drwxr-xr-x 3 root root 4096 Aug 19 23:05 usr
| |
| 20:09 | root@solus /1 # ls -la lib64/
| |
| 20:09 | total 8
| |
| 20:09 | drwxr-xr-x 2 root root 4096 Aug 19 23:06 .
| |
| 20:09 | drwxr-xr-x 4 root root 4096 Aug 19 23:06 ..
| |
| 20:09 | lrwxrwxrwx 1 root root 16 Aug 19 23:06 systemd -> usr/lib/systemd/
| |
| 20:09 | root@solus /1 # ^C
| |
| 20:09 | <vagrantc> uh
| |
| 20:09 | <SysadmOFF> root@solus /1 # ln -sf 1.txt lib64/systemd/1.txt
| |
| 20:09 | ln: failed to create symbolic link 'lib64/systemd/1.txt': No such file or directory
| |
| 20:09 | <vagrantc> stop spamming the channel :P
| |
| 20:09 | use a pastebin
| |
| 20:09 | <SysadmOFF> sorry0
| |
| 20:10 | there is no marking or tags
| |
| 20:10 | ok
| |
| 20:11 | https://www.klgrth.io/paste/5j4q7
| |
| 20:18 | naah, it should work
| |
| 20:24 | <vagrantc> i'm surprised it even gets that far ... that the initrd is sufficiently compatible
| |
| 20:28 | <SysadmOFF> will check soon..how far
| |
| 20:29 | woernie_ has left IRC (woernie_!~werner@p5b296f43.dip0.t-ipconnect.de, Remote host closed the connection) | |
| 20:46 | <SysadmOFF> something wrong, emergency shell
| |
| 20:48 | Failed to switch root =(
| |
| 20:48 | initrd-swtich-root.service Main process exi..
| |
| 20:57 | vagrantc cat this be a critical issue?
| |
| 20:57 | "unknown kernel command line parameter - nfsroot://blablabla"
| |
| 21:01 | <vagrantc> how did you even get to the symlink issue if it fails there?
| |
| 21:02 | <SysadmOFF> i have created symlink
| |
| 21:02 | copied flat vmdk and then "ltsp image solus", ltsp initrd. -- then started netboot
| |
| 21:03 | <vagrantc> your initrd is not compatible ... so you either need to add support for it or move on to something else
| |
| 21:04 | picking every niche distro out there and trying to boot it with ltsp is an interesting project ... but you need to have the skills to follow-through and troubleshoot it
| |
| 21:04 | and fix it ...
| |
| 21:11 | <SysadmOFF> https://file.io/zvc80P32wxOv
| |
| 21:11 | video of boot process
| |
| 21:12 | I got your point, but maybe you can show me the path where i need to dig?
| |
| 21:15 | I have installed today and setup sssd for mint . And it works.
| |
| 21:15 | I know that ltsp5 is for debian based OS , so just thought it will be easier. Dont know another method to make live bootable network img
| |
| 21:17 | <vagrantc> it's theoretically possible, but it does require some work and effort
| |
| 21:17 | i have quite a few things already on the back-burner :)
| |
| 21:26 | <SysadmOFF> ok, i will show you rdsos log, maybe..maybe you can take a look and tell me is this shit can be fixed without high skiills or no
| |
| 21:26 | https://file.io/3czr8v8SH4oM
| |
| 21:41 | sysroot is empty, ltsp should mount solus.img there..
| |
| 21:52 | SysadmOFF has left IRC (SysadmOFF!~SysadmOFF@188.138.239.8, Quit: Client closed) | |