Software manager

To get red of the Software Manager icon in the menu, do the following. Update mint-lxde-default-settings to version 12.0.11.

sudo apt update
sudo apt upgrade

For existing users, you have to copy the .config file in /etc/skel into the user´s home folder. If you do it for yourself, it has to be done like this:

cp -r /etc/skel/.config ~

Logout and login and you will see that the non-working Software Manager icon has disappeared.

When new users are created, this icon will not be shown anymore.

Upcoming updates

Happy Whit Monday!

We are in June 2020 and what that means is that the Linux Mint team will release version 20 of its distribution, coded “Ulyana” this month. As soon as it is available I will start working on porting the artistic stuff into MintPPC. It is for this reason I would like to ask you if there are things you like to have improved. What I intend for example is to remove “Software Manager” as option in the Menu, as the program will not be ported and it is too bloated anyway. Another thing that you will see is a new Linux Mint Menu icon on the left side of the panel. The present icon is based on older versions of Linux Mint. The new one, which was designed for Linux Mint “Tricia” looks much prettier and is round. For info on the logo design, have a look here.
That’s it for now.

Small addition after announcement

Yesterday I found out that I forgot to include a small app in the panel which shows when there are updates in the system. It works very similarly to the tool used in Linux Mint, the package is called package-update-indicator and will as of now be installed automatically in MintPPC. For those of you who installed MintPPC in the last couple of days but do not yet have this small handy app I would recommend to do the following:

sudo apt install package-update-indicator

Debian installer finally being worked on

As I write this new post, Adrian Glaubitz has been working hard within the Debian community to make the installer work for ppc users. Apparently, the GRUB issue has been solved now finally. I have not had the time to do a test myself yet. I will do this as soon as I think that the time is right. If it all works as expected, I will make new MintPPC installer images.

To be continued…

Arctic Fox

Arctic Fox has been updated to version 27.9.19 in the MintPPC repository since today. To get this new version do the following:

sudo apt update
sudo apt upgrade

The changelog can be found here. As you can see many bugfixes have been applied. The work is truly impressive. Thanks to wicknix, Ricardo Mottola, xeno74 and m.oudenhoven for bringing this up to date browser to the PowerPC Linux community.

Latest Debian installer images

I am continuing the post about trying to make new installer images. I have been trying to achieve this lately and I will tell you what I experienced and what you can expect in the future.

As you are probably well aware of, the Debian installers ditched yaboot and introduced Grub as bootloader. With the installation images which can be downloaded from the official Debian ports place it was possible to still use yaboot until July 2019. The images which I created and can be downloaded from the instructions page are based on the 2019-07-07 Debian images. These images are sort of bridge between the old era and the new era. I could still make those images boot with yaboot and it was still possible to install yaboot at the end or after a reboot.

I am now working with the latest Debian images which can be found in the 2019-11-22 folder. I am also able to make these kind of images myself now. What I found out is that these images cannot be respinned anymore with a yaboot bootloader. For some reason that I am not aware of, the installer does not work properly anymore when booted from yaboot. What I also found out yesterday was that the latest powerpc NETINST image installs MintPPC fine but does not allow me to install yaboot. At least for the moment I can’t do this, maybe I can fix it somehow with another trick. So I can’t boot the newly installed system. I think it is fair to say that I have to say goodbye to my old friend yaboot and start investing time in using Grub. It is never nice to replace something that I am familiar with, and that always did the job, with something new. Things change, so I have to follow I guess.

What I had in mind was to replace the NETINST images with a desktop image, that would allow an installation without the need of downloading all the packages from the internet. I can tell you that that is something I did not achieve. I am perfectly able to spin the same kind of images which Debian produces, i.e. NETINST images, but it is impossible for me to make desktop isos. It is not a huge problem but it would make the installation more predictable. With the NETINST images the person willing to install MintPPC needs to be lucky that all packages which are needed are in a stable state on the Debian ports server. If the installation fails, it is best to look at the syslog and see which package could not be installed. One has to wait then until that package is available in the mirror.

So what can we expect in the future then? What I see coming is an installation image for both powerpc and ppc64, which is based on the latest kernel and kernel modules, i.e. similar to the image that can be downloaded from the 2019-11-22 folder, adapted to install MintPPC. The installation image boots with the help of Grub and the freshly installed MintPPC will also boot by Grub. What I will do now is try to find a way to repair Grub after installation. At the moment Grub is broken on powerpc/ppc64 as it is unable to retrieve the right open firmware path to the hard disk.

I am still working on the project, so please don’t give up on MintPPC. In the future I am sure that knowledegable people can solve the Grub issue and then it will be (almost) no problem at all anymore to install MintPPC (except for the fact that we do not have a stable repository).

At last I want to wish you a nice day!

Regards,
Jeroen Diederen

Issues with my ISP

On November the 16th I received an email from my internet service provider (ISP) that there was a ticket opened for me. So I opened the ticket and to my surprise I read that my ISP had received a complaint from Google Safe Browsing. They had found an abuse on my domain. It meant that my ISP was about to suspend my website. A few hours later I was shocked to see that they indeed suspended my account and that my website was no longer reachable. I immediately tried to contact them and they told me I had to clean my files and database. Of course I was not extremely happy with this but at least, they gave me an option to do something about the matter. I did not find anything suspicious. I just did what I was told and I cleaned everything and put a backup copy of my site back. Today they finally approved what I did and they made my website visible again. I am pretty sure that I don’t have malicious code in my domain. What I suspect is the following. I run my website at a rather cheap domain, which is www.u58733p55594.web0093.zxcs-klant.nl. The domain web0093.zxcs-klant.nl is known to other ISP’s as a domain where strange things were done in the past and many ISP’s block emails from this domain, probably because spam was sent from there. When I tried to setup my website to be able to send registration mails I noticed that those mails I sent from my domain never arrived. They are immediately filtered and seen as spam. So what I did is I added a module on my site that sends emails via my own gmail account. Many of the registration mails that were sent from my site via gmail were bounced as those ISP’s involved do not accept mails from my domain. I guess that triggered Google. Google thought that I am sending spam mails. I learned my lesson and now I turned off all these mail serving modules. Registration mails will not be sent anymore. It is a small nuisance but it’s better than to be blocked by my ISP.