Home  Spins  Releases  Repository  Themes  Garden  About  Checking

Best Practices

Manjaro is a wonderful OS. It is the base of all SbK spins to date. That being said your experience and enjoyment of the OS you install is dependent on the choices you make. Here are a few things to keep in mind.

1. All SbK spins are based on the Stable branch of Manjaro. They are that way because stability has its benefits. Number one is that the packages have been tested several times while moving from Arch, to Manjaro Unstable, to Manjaro Testing, to Manjaro Stable. Bugs have been removed along the way. You may not get the bleeding edge new packages. Though most of the time Stable packages are only a few weeks older than Unstable. You can always change the branch to Unstable or Testing. But before you do think long and hard on how much tolerance you have for bugs and your technical ability to fix those bugs. Is it worth the work or should you just wait a short amount of time? For those new to Linux, stay on Stable unless you absolutely need a specific piece of software to make your computer function.

2. All SbK spins use the latest LTS or Long Term Support kernel. The reason is stability. Newer kernels are available, but most of the time not LTS kernels.  Most of the time they are ok but some may be marked experimental. Kernels are mostly for hardware support. Stick to the LTS kernels unless you absolutely need a newer kernel to support specific hardware. Should you want to try a newer kernel leave the LTS one in place, do not remove it. Keeping two kernels is a good idea. If the new kernel has issues with your hardware or a bad update you can then boot into the LTS kernel. 

3. The AUR. One of the biggest advantages of running Manjaro is the AUR or Arch User Repository. You can install packages that are built from source on your machine. But be careful of what you install. A lot of the time AUR packages rely on AUR package dependencies. Those dependencies may be added by different people with different rates of updates. This may cause some packages to be held back. That may be ok if what you installed is an application, the application may just stop working. But never ever install system components from the AUR unless absolutely positively necessary for your system to function. If you do and update while some updates are held back you may end up with a broken system.

4. All Sbk Spins come with timeshift and timeshift-autosnap installed. Timeshift then takes a snapshot of your system before all upgrades. The advantage is that if an update fubars your system its relatively easy to roll back to a working setup. You can uninstall timeshift or prevent it from taking snapshots, but think long and hard before doing so.

5. Snaps and Flatpacks are not installed when you install the system. It is up to the user if they want to install them. But understand that when you do, if you install them from some third party website they may not work. Linux software is built against libraries. The libraries may be the same in different distributions, they may be  named differently or they may be different versions. Snaps and Flatpacks are supposed to avoid this by bundling the libraries the application needs with it. But this isnt always the case. If you get an error saying the application cant find "insertnamehere".so its because of this problem. Just uninstall it and look in the repositories or AUR. Never ever install system components with Snaps and Flatpacks, The most common is audio components.

Spins by Kilz is hosted by Tuxfamily.com