Viewing posts for the category Omarine User's Manual

Binary Qt Creator package version 4.9.82

Qt Creator is a leading integrated development environment (IDE) on the desktop. However, the binary package that Qt company provides to the community is not entirely compatible with the systems. For example, Qt is currently providing binary Qt Creator version 4.9.0. This version is built with Qt version 5.12.2. Therefore, for systems using newer Qt (Qt 5.12.3 - the latest version), a conflict will occur. To fix this, you need to put the system Qt in a separate directory like /opt and make a symlink to it. You can choose the solutions below:

1) Install multiple versions of Qt including Qt 5.12.2 and switch the symlink to it.

Using audit to find out unauthorized access

Using systemd timer

Systemd timer can be used to replace Cron for job scheduler. A timer file must be accompanied by a service file with the same name by default (except for the suffix). The service is triggered when the timer elapses. Because Omarine 6.0 does not use dcron, I write this article to guide you to create your own timer if needed.
We begin with a timer updating virus database that has been set up in Omarine 6.0. That is the pair of timer file clamav-freshclam.timer and service file clamav-freshclam.service.

SELinux with omarine policy: Allowing a guest user to login without a password

Version and release, version and version number, release and release number

Generally the version and release concepts can be used interchangeably. For example, version Omarine 6.0 and release Omarine 6.0 are the same. But they may be slightly different. The easiest way to clarify this is to state the following:
“We release this version second time.”
However, in RPM package management (and perhaps other package manager programs) there is no difference between version and release. This is to ensure the cleanliness of the system when installed. A new release of a package is a new version. Old package is upgraded to new package and the old package is removed.
A package with a new version number is of course a new package, called a new version or new release. But a package with the same version number but with a new release number when it is rebuilt, is also considered a new package, so is also a new version or new release. In this case, although the package was rebuilt with the same source code version but the dependencies have changed, so it has the new functionality.