There are many ways distos make ISO's and other images, and often they have a set of build scripts with some small configurations, and whole ISO builder for each build. Us? No. We have what is called ArisGlobalBuilder and ArisInfiniBuilder. The image above depicts a simplified version of AGB (ArisGlobalBuilder). The AGB setup is designed for one main purpose: Build everything the same way.
How Does AGB work?
AGB functions with three main scripts: Arisblack, Arisblu, and Arisred. Each has their setups. While Arisblu and Arisred are well known and are the main focus, Arisblack is a new project with very little information shared. Arisblack will be an attempt to build a super micro system, going as far as having the most important commands and a very minimalist shell. The system will be set to standards, but have next-to-nothing in terms of software, options, and even slightly useless items. Arisblack has the general core utils, a generic shell, GNU Make (so you can actually install something), WGET (so you can pull from the internet) but will not have much else.
Back on AGB. AGB after Arisblack will then take the Arisblack ISO and use it as the base for all other editions, especially Arisred and Arisblu. These builders will take in the ISO's for each edition, and give it back to the AGB script. The AGB script will then make the directory in the root of the system called /usr/aig-VERNUM/agb-ARCH-VERNUM/*. This directory is fairly easy, it will have the ISO's for all the images. This is for each individual AGB, which for us there will be MANY. so how do we solve this issue?
What is AIB?
AIB or ArisInfiniBuilder is a lot more simple to explain. It simply takes the AGB scripts, and builds them to their respective directories. It also will handle documentation, software overview, and everything else. While AGB can run custom configuration files, AIB keeps them organized and similar. For mobile editions, there will be mobile configs, for desktop editions there will be configs for specific architectures. This hopefully will keep the complicated setups for each and every ISO minimal.
The Plan for Potabi What is Potabi? Potabi is a FreeBSD-based mobile operating system that is designed to be an option for secure and encrypted phones, with no hacking needed, opt-in telemetry, out-of-box experience with future support for Android APK's, and a centralized app store for all applications. This article is going to what we WANT for Potabi, what the goal for Potabi is, what market we are looking at breaking into, and what the plan is. Marketing, Market Share, and Tools for the Markets. Something we want to be clear about is where Potabi is going to hit in the market, what the core user-base is, what secondary user-bases we will support, and how we differ from other mobile operating systems. Potabi is an enterprise-focused and privacy-focused operating system for mobile. While other Linux-based mobile operating systems focus on the end-user, the public, Potabi is more built for the people who need a work-phone that is secure and protected from attackers. The finalized v
This article is to explain some decisions and plans made by the ArisbluBSD team, why we are making our own thing, and what the plan is for the OS. We mainly want to talk about five things: desktop, package management, software availability, custom software, and the future of the OS. We mostly want to explain what the goal of the OS is, and how we plan to expand in the near future. Without further ado, let's explain ArisbluBSD's plan. Desktop Environments ArisbluBSD wants to use common and well known desktops only. While other BSD systems are using extremely themed desktop environments or putting tools on top of window managers like Openbox. ArisbluBSD will have two desktop environments, and if demand grows large enough we will add Openbox as well as Xfwm4 (with a dock like Tint or Cairo for both). Our two desktop environments, XFCE and GNOME3, will be un-themed, no extensions, no pre-made configs outside of the defaults. There are good reasons to theme a desktop, but in order
We started ArisbluBSD as a Live-CD and soon-to-be desktop replacement of Linux systems like Ubuntu, Manjaro, and OpenSUSE. While we still like and support the Linux communities and operating systems, we do have multiple issues with the Linux ecosystem. So, let's jump right into the top 10 reasons we want to replace Linux. 5. Linux is Fragmented (sort-of) ArisbluBSD's team (Fivnex) sees Linux having a different fragmentation problem than people think. It's not that there are too many distros, it's the differences between those distros that give us issues. The fact of the matter is distributions like FerenOS, elementryOS, and Linux Mint become more and more like each other and their upstream (in this case Ubuntu). We will get into the upstream limitations in a bit. 4. Linux Package Management is Idiotic We will get into RPM vs DPKG and the format/repo fragmentation in a bit. But let's focus on the three forms of Linux packages. Containerized, binary package, and scri