First, thank you for this great distro. I’m now on Netrunner 14.1 x64 which I love but I want to try something new and I have some questions and bugs to report.
KDE 5 is still quite buggy. There is a lot of bug report https://bugs.kde.org/ and it will need time to have more stability.
I try to install Netrunner Rolling on a test partition (sdb5) but I can’t boot it. I have a kernel panic: It’s the Grub from the main partition (Netrunner 14.1) that handle boot of the distros I test. Of course I did a sudo update-grub. That work with every other distros I tried but not here.
I installed Netrunner Rolling Grub to “/” partition. I tried free and non free drivers install.
Please do not try and update your system using yaourt, this is never a good Idea.
Packages from the AUR are NOT officially supported, if those packages in question need to be updated I will do so, these packages are customized and in our repositories for that reason, they are NOT exactly the same as the ones from the AUR.
Having the right size for the system settings window on the ISO and installed system for every possible resolution would be a very hard thing to do.
Just starting and enabling mysqld is not enough, it needs to be configured first otherwise it will not start:
Oh yea, sorry about that. Like Manjaro and Arch Linux, Netrunner Rolling needs to be the one that handles the grub installation or it will not be able to boot. Netrunner rolling uses the same method for the early Intel microcode loading as it’s parent distribution (Manjaro).
Ok but I need to install some package from AUR. So to update my system, AUR package too, I need to use yaourt for the update. If I can’t use yaourt for that how can I easily keep my system updated easily ? Maybe there is an other way to provide these package without “breaking” yaourt ?
Look at the screenshoot. That’s not what I mean
I will try. I thought that because mariaDB is already installed and start if you launch knotes for instance, it was alrready configured.
Yes I found the issue and fixed it for the pre3 ISO.
There is a mariadb line in one of the configuration files under /etc/skel/~./config that I overlooked removal prior to building the ISO. This file will also be under ~./config in your home directory.
I don’t remember which config file the mariadb reference was in as this was prior to all the packaging changes made for the pre3 ISO.
PS. As I already mentioned, the pre3 ISO is going through some major changes both in packaging of the netrunner specific packages and where these things are located in the filesystem. A reinstall will be required.
Updating from pre2 to pre3 will be problematic at best.