Re: Full linux distros on Sailfish OS
 

It doesn't work.
But that has nothing to do with your patch!

It seems like I have something destroyed with my fiddeling around on lxc. If i try to create a container. It there is the information that the container is running the setup, but after that the container wich was initially shown vanishes and that's it. (No matter if I use the original deamon.py or yours) So I have first to look what I have borked on my system.

I'm grateful for tipps. I have already deinstalled lxc many times and have searched for directories with the name lxc on my file system to empty them. Unfortunately with no success regarding the container setup. I have to dig deeper I fear....

Re: Full linux distros on Sailfish OS
 

Hum, I'm not sure exactly where your issue comes from. Do you have files in the folders I mentioned in my previous post?

Thanks for trying anyway! Note that I forgot to mention this would be tried without nemo/defaultuser symlink, else LXC could work because of that and not because of the patch.

Re: Full linux distros on Sailfish OS
 

Question - I wanted to try this method out of curiosity, since I'm interested in learning more about dbus, etc... I assume from your post that the first command (grep) is for the purpose of getting the PID of daemon.py, to use for the second command, to kill the service. But, when I use the 2nd command with the number I get frim the output of the first command, I get "... no process with PID... " error.
Am I understanding wrong?
EDIT - never mind... I think my process was dead already...

Re: Full linux distros on Sailfish OS
 

Maybe try Mashka to delete any lingering data/configs from previous installations, and even search filesystem for traces of "harbour-containers" and delete everything...

Re: Full linux distros on Sailfish OS
 

Maybe the PID you saw and tried to kill was that of `grep daemon.py` itself levone1, if the daemon was already stopped in your case.

Re: Full linux distros on Sailfish OS
 

Hi. I thought to give this a go, as I do not have nemo as my username. This is a fresh install. I went through the guide to install everything, and then followed your guide to replace daemon.py. I also had the "... no process with PID... " error when killing the service. I then used terminal to remove the old daemon.py file and copy the new one over. I then rebooted.

But now, when I open the container, there is nothing there. It doesn't not show Alien Dalvik or the option to create a new container. It only shows the menu of Freeze/Stop all, and about.

Any suggestions?
Thank you.

Re: Full linux distros on Sailfish OS
 

Would someone mind writing a description of how to uninstall harbour-containers please? After attempting to install a distro, the container stopped showing anything, and I don't know how to restart it to get working again. Any help for a noob would be awesome. Thanks.

Re: Full linux distros on Sailfish OS
 

You could first of all look which containers exist with
It will show aliendalvik if installed and additional containers you set up.

Then delete the one that failed to set up with
Use brackets if your container name has spaces like "debian sid".
harbour-containers did then start up again in my case.

I am on 4.0.1.48 on Pro¹ and in process to figure out how to set up debian so Kabouik can finally move to 4.0 from 3.3 :D

It would be great if someone could post instuctions how to create and setup a debian container from CLI. That way i could supply the logs here. I figure the ones from first post are outdated?

Re: Full linux distros on Sailfish OS
 

Sorry for spotting this only just now.
Your wording implies one of the Pro¹ 4.0 images actually worked?
Or did you flash 3.4 and then OTA to 4.0?

I tried to flash all of the 4.0 images listed in the gitlab artifacts and they did not work for me.
Adam would be quite relieved to hear they actually work and it was my error they did not!

Re: Full linux distros on Sailfish OS
 

Thank you! So easy. It brought my harbour-containers back to life.

Thanks - this worked for me. It might be worth noting (for people like me) that you need to make the copied file executable otherwise the container application opens with nothing in it.