The first time I tried to monitor a client in WSL 2 on via BOINCTasks all on the same PC it was kinda finicky. When I get to an WSL 2 install, I'll be able to contrast it to the things I learned on this WSL 1 experiment. So, I went off the beaten path and learned a bunch of things. Docker is a VM contained BOINC client and it can be managed by an external BOINC Manager or BoincTasks.ġ3) WUProps has some issues using the WSL (posting a new question about that in another post). Maybe it can manage the BOINC clients that or contained within VM's? Mikey and I were just discussing that.ġ2) Learned more about the BOINC Docker project and maybe I could have just ran Gerasim (Linux) in a Docker, or in the WSL, instead of developing my own Linux VM. I'll try using BoincTasks for central management later. Now I start BOINC with 'sudo /etc/init.d/boinc-client start' and the data folders are now properly placed.Ħ) Edited the boinc-client script in /etc/init.d with a decent Linux editor named Geany to add -gui_rpc_port 31414 so the WSl client had a different port.ħ) Learned that Windows Notepad or 3rd party app, Notepad++, change the permissions of script files in the rootfs so they no longer execute.Ĩ) Used PCmanFM to correct the boinc-client script permissions (nice product).ĩ) Never seriously used BoincTasks, but faced with two BOINC clients on one machine, d/led it and spent 2 hours learning to use it.ġ0) had to hunt down the correct gui_rpc_auth.cfg client passwords so that BoincTasks can log in.ġ1) BoincTasks showed how many BOINC clients are advertising theirselves on my network. (I have some numb fingers and arthritis so command prompt typing errors slow me down.)ĥ) I completely forgot the Debian inet.d method of starting apps. Windows built in File Manager acted like they were moved but they were still there. It successfully moved the xml BOINC config files out of /mnt/c/wondows/system32 to /var/lib/boinc-client where they belonged. In WSL BASH type 'export DISPLAY=:0' to send video output to the Windows X Server.ģ) Windows File Manager can read the rootfs folder but even an admin can't always move Linux files (Like cc_config.xml) and, if you do, the permissions can get scrambled.Ĥ) I found PCmanFM File Manager for KDE(?), installed it and was using in on the Windows X server. Things I learned that maybe could help someone else here:ġ) You can Unzip the Linux.appx or Linux.AppBundle packages and install manually.Ģ) There are X servers for Windows (XMing is one) that let the WSL communicate with the display. I was planning on just wiping the OS drive and installing Linux but it's a badge hunter, with an AMD and NVidia card, so Windows + WSL2 is going to be the best choice, eventually.īreaking things or taking the manual route can improve your skills. Turned off a lot of services, including Windows Update and the store, also it's Windows 18363.1556. When I google the pcilib error most contain something around Raspbian. Message 9861 - Posted:, 8:41:26 UTC - in response to Message 9860. More permissions issues? I'm weak at permissions troubleshooting. It complains about gtk+ libraries that appear to be installed. The install sh script doesn't place the boinc executables in the usr/lib/boinc-client folder and fails to start from the home dir. The AntiX BOINC 7.18.1 install went badly. I'll try moving the data folder and then maybe just install Ubuntu in a VM so I can get this Gerasim (Linux) done. Not that I'd be running two BOINC clients and two BOINC Mgrs guess this is where BoincTasks shines. Proud of my Linux-ignorant self for doing that all in a night.īut I thought a single BOINC Manager could control WSL and native Windows WU's from the same port. Maybe it's because I didn't give BOINC an explicit data folder and it made /mnt/c/Windows/System32 it's data folder? (strange choice)Īt least I successfully manually (no Windows store) installed Ubuntu 22 LST into WSL 1 on Windows Pro 2019, gave Windows an XServer then successfully ran the Linux BOINC Mgr GUI to access the WSL BOINC client and got Gerasim (Linux) and WUProp running. I'm not a Linux expert and not sure what's wrong. Guess I could somehow sudo the WUProp or run from the root account but it should work properly without those solutions. Made sure the is set to 1 but this is about permissions to access the pci dev. Lspci: Cannot find any working access method. No WU can validate because of this error:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |