CoreNGS

From Potabi Foundation
Jump to navigation Jump to search
<templatestyles src="Module:Infobox/styles.css"></templatestyles>
CoreNGS
DeveloperThe Potabi Foundation
OS family UNIX-like
Working stateCurrent
Source modelOpen Source
Repository
Kernel typeMonolithic
LicenseBSD 2-Clause (Simplified)
Official websitecorengs.one

CoreNGS (Nucleus General Systems) is a project aiming to provide the components of a UNIX system simmalar to GNU. Potabi Systems . Many of CoreNGS's components will come from FreeBSD and other BSDs such as Illumos , NetBSD and OpenBSD . CoreNGS aims to support a "true no-GPL system" and will be the base of Potabi.

Aims[edit]

The CoreNGS project aims to be a set of components to build a functional operating system. It was designed to provide solutions to some of the major problems and failures that are present in many other UNIXes. Here is a list of those failures:

  1. Command-line Dependence: Many operating systems require the user to use the command line, or shell, for seemingly trivial tasks. Although completing tasks through the shell is efficent and simple for experienced UNIX users, for new users it can be confusing and overwhelming. CoreNGS will provide standardised application APIs that will communicate directly with the system, bypassing the command line alltogether.
  2. Ease of branding: Brand-factor, as in "How easy is it to brand my operating system?", is a major flaw for many UNIX systems. While it can be easy for some, our goal is to make branding an integral part of distribution development, from bootloader to the desktop environments. The easier it is to brand a system, the more diversity and success it will enjoy.
  3. Licensing: Due to the infectious nature of licenses such as the GPL , many operating systems struggle to provide the software they desire, and can run into issues when working with propriety software. CoreNGS aims to only use licenses that respect users and developers, even if it requires reworking certain parts of the system.
  4. User-unfriendly design decistions: Software can understand the difference between, say, /etc/ and /usr/ most end-users won't. Most end-users won't know the difference between a .deb or an rpm. CoreNGS's goal is to provide developers with built in APIs, rather than tools like SystemD , allowing for simple system and software management that is more stable and consumes less resources than the conventional