Documentation


Viewing posts for the category Omarine User's Manual

Omarine Update 3.2 released!

Omarine Update 3.2 improves notification, displaying dynamic information for each update instead of fixed. It parses the log file and renders up to five lines of information.

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.

SELinux with omarine policy: An in-depth look at the security policy – secure program with its own domain: Part 8

Adding constraints to the rules - practice

SELinux with omarine policy: An in-depth look at the security policy – secure program with its own domain: Part 7

Adding constraints to the rules

SELinux with omarine policy: An in-depth look at the security policy – secure program with its own domain: Part 6

Transitioning domain directly by designing SELinux-aware program