The Libre-Halaal ByStar Digital Ecosystem (By* DE) is an interdisciplinary, and ethics-oriented non-proprietary digital ecosystem which challenges the existing proprietary American digital ecosystem while operating concurrently alongside it. On a global scale, By* provide Internet Application Services which preserve autonomy and privacy of the individual. BISOS: (By* Internet Services Operating System) is a unified and universal framework for developing both internet services and software-service continuums that use internet services. BISOS is a layer on top of Debian. Blee: (BISOS Libre-Halaal Emacs Environment) is a layer on top of Emacs and BISOS, which creates a comprehensive integrated usage and development environment. Blee and BISOS are fully integrated. See the ”Nature of Polyexistentials” book for the bigger picture of how all of ByStar fits together.
Nature of Polyexistentials:
Basis for Abolishment of the Western Intellectual Property Rights Regime
And Introduction of the Libre-Halaal ByStar Digital Ecosystem
On Line: PLPC-120033 at Github – DOI — PDF: 8.5x11 – A4
Order Book Prints At Amazon: US – France – UK – Japan (424 pages — 6 x 0.96 x 9 inches)
Here we provide needed instructions for you to start adopting ByStar by creating your own Raw-BISOS Platform and your own ByStar-Rims-Site. The bootstrap script is ./raw-bisos.sh, you can inspect and review it before running it.
We refer to the base software of BISOS and Blee without any customization as Raw-BISOS and Raw-Blee. Raw-BISOS augments a Fresh-Debian such that other layers of BISOS installation can be performed.
On a Freshly installed Debian system, run:
wget -q -O - https://raw.githubusercontent.com/bxGenesis/start/main/raw-bisos.sh | \
tee raw-bisos.sh | \
bashThe above command downloads the master installation script and feeds it to bash. Bash execution is limited to display of a menu.
The downloaded script is saved in ./raw-bisos.sh. You can inspect that
script before running it for installation purposes.
Section sec:Whatraw-bisos.shDoes — ,
describes what happens inside of ./raw-bisos.sh.
When you are ready, you can choose the last line of the menu that was displayed, and run:
./raw-bisos.sh -h -v -n showRun -i installUnsitedBisosRespond to the prompts and be patient. Raw-BISOS installs a lot of deb, Python pip, JavaScript npm, and emacs elisp packages. Upon completion of the installation, you can log into your Raw-BISOS and install additional layers and customize your environments. A log of the installation is kept in a file named ./raw-bisos-dateTag-log.org — dateTag reflects the start time and the log file is in org-mode format.
In the following sections, we guide you through that process.
- Bootstrapping Raw-BISOS From Fresh-Debian
- Deploying BISOS and ByStar — Layer by Layer
- BISOS Software Bill Of Materials — BISOS-SBOM
- An Overview of BISOS Directories and Accounts
- BISOS Development Frameworks
- Current State and Status of BISOS and ByStar
- Participating in BISOS and Blee Development
[ The following text is aligned with Chapter 18, — Engineering Adoption of BISOS and ByStar — of “Nature of Polyexistentials” ]
Basic design of BISOS is layered. Any BISOS layer can be useful for a particular purpose. These layers build on each other.
#UsedToBE+html: <img align=”center” src=”images/provisioning.png”>
The Figure above, depicts how these layers are deployed. The layers on left are service oriented. The layers on the right are usage oriented.
Some BISOS layers can be used outside of the ByStar context. Here we introduce 5 specific layers, based on intent of usage.
A brief description of each layer follows.
- Raw-BISOS and Raw-Blee:
-
BISOS and Blee can be considered in two parts, the software of BISOS
and Blee and customization of BISOS and Blee, for use in particular
site, with particular application by particular users. We refer to the
software of BISOS and Blee without any customization as Raw-BISOS and
Raw-Blee.
Raw-BISOS and Raw-Blee can be used outside of the ByStar context for various purposes.
- BISOS-Service-Platform — BISOS as a Virtual Machine Hosting Platform:
-
ByStar services are almost always realized inside of Virtual Machines (VM). BISOS facilitates this with select choices of common mature technologies including: kvm, virsh, vagrant and basebox. BISOS services are reproducible through a collection of BPOs and are transferable and disposable.
On top of Raw-BISOS, you produce your VM Hosting Platform.
- ByStar-Rims-Site — Setting Up Your Own ‘Rims’ Environment:
-
With a VM Hosting Platform in place you are ready to construct your
own ByStar site as an autonomous Rims environment. Several
foundational services in the Rims Environment will be created, these
include:
- A Gitlab BPO Server — for private BPO realization
- ByStar Registrars — for assignment of unique names and numbers in your Rims Environment
- A Site Manager Console — for providing visibility to your Rims services and applications
With these foundational services in place, you can then add various Rims services and applications. Entertainment centers, security cameras, etc.
With your Rims Environment in place, you can now manage the needed BPOs for accessing ByStar internet services.
- PALS-Self-Hosting:
- With your own Rims Environment in place you are ready to self-host your PALS services if you wish.
- Sited-Blee-Environment:
- With your own Rims Environment in place you are ready to configure your Usage Environment to match your ByStar internet services.
Based on this layering, you can now decide on which layers you wish to deploy. Once Raw-BISOS and Raw-Blee have been deployed, you can deploy and manage the remaining layers through Blee-Panels.
In order to construct a ByStar Virtual Machine Hosting Platform and setup your own Rims environment, you need one or more server grade computers. A typical 16 core computer with 16GB of memory and 1TB disk is recommended.
You can also deploy BISOS without any explicit hardware in the cloud based on the availability of a Debian image.
Hardware requirements for Usage Environment can be met by typical modern laptops.
Current release of BISOS assumes availability of Debian 12.
A Fresh-Debian is an installation of Debian without any additional configurations. Raw-BISOS builds on a Fresh-Debian.
You can obtain the appropriate Debian 12 image from:
https://www.debian.org/releases/bookworm/debian-installer/.
Debian 12 comes with Python 3.11 and Emacs 28. Blee requires Emacs 28 or higher.
Previously we described the common procedure using ./raw-bisos.sh.
Installation of Raw-BISOS and Raw-Blee on top of raw Debian-12 can be accomplished in other ways as well.
If you already have a Rims Environment in place, you can install
Raw-BISOS on a new physical machine using unsitedBisosDeploy.sh or
sysCharDeploy.sh.
In an existing Rims Environment, you can also create new raw-BISOS VM
images based on Debian-12 base-boxes or use existing raw-BISOS base
boxes using sysCharDeploy.sh.
The process of installing raw-bisos.sh starts by obtaining the raw-bisos.sh bash script.
wget https://raw.githubusercontent.com/bxGenesis/start/main/raw-bisos.shraw-bisos.sh is a self-contained bash-ICM (Interactive Command Module). The primary entry point to raw-bisos.sh is the vis_installUnsitedBisos function.
First the current user is added to the /etc/sudoers file without a requirement for a password.
local curUser=$(id -u -n)
ANT_raw "About to add ${curUser} to /etc/sudoers -- You will be prompted for root passwd."
su - root -c "echo ${curUser} ALL=\(ALL\) NOPASSWD: ALL >> /etc/sudoers"At this point, access to the system should be well restricted. We will re-adjust the sudoers file and remove the added line at the end of the installation process. Where appropriate the installation scripts use sudo to accomplish privileged tasks.
Next we install pipx as a Debian package.
sudo apt-get install pipxUsing pipx we then install the bisos.provision pip package from PyPI.
pipx install bisos.provisionbisos.provision is actually a set of bash scripts. We have not switched
to our python environment yet. The bisos.provision pip package installs
the provisionBisos.sh script. provisionBisos.sh is a stand-alone
bash-ICM module. The provisionBisos.sh script and its
seedIcmStandalone.bash are at:
https://github.com/bisos-pip/provision/tree/master/py3/bin
We then invoke the sysBasePlatform command of the locally installed provisionBisos.sh
$HOME/.local/bin/provisionBisos.sh -h -v -n showRun -i sysBasePlatformWhich installs git, configures git and clones the https://github.com/bxGenesis/provisioners repo in /opt/bisosProvisioner/gitRepos/provisioners.
A set of self-reliant bash-ICM modules are then used to create the final /bisos environment. Once the /bisos/core/bsip/bin environment is in place, all bash ICM scripts use the bisos bash-ICM modules. During the installation, our use of ICM modules evolves from stand-alone (raw-bisos.sh) to self-contained (provisionBisos.sh) to self-reliant (/opt/bisosProvisioner/gitRepos/provisioners) to bisos bash-ICMs (/bisos/core/bsip/bin).
Upon completion of the installation process, Raw-BISOS is capable of functioning as a BPO-Container, but no BPOs have been activated yet.
Deployment of Raw-BISOS involves creation of a default login account called: bystar. You can now login to your system as bystar. On the Gnome GUI console select the bystar account.
Or you can ssh into your system.
ssh -X bystar@ipAddrThe bystar account is preconfigured for BISOS services and capabilities.
While you can use the traditional bash command line, the primary interface to use and to configure BISOS is Blee.
Deployment of Raw-BISOS involves creation of a full featured emacs environment which is fully integrated with BISOS, called Blee.
blee -i runIf you are familiar with Emacs, you will feel very much at home with Blee. You can think of Blee as a redistribution of Emacs which is fully BISOS aware. Most BISOS capabilities and services have been integrated into Blee. You can use ByStar services through Blee. Additionally, BISOS capabilities can be configured through Blee. Furthermore, BISOS is developed with Blee and you can think of Blee as the native BISOS IDE (Interactive Development Environment).
Blee menu bar is a superset of Emacs menu bar. Most BISOS capabilities and services can be accessed through Blee menus. Additionally, Blee introduces a new user interface, called Blee-Panels.
Blee-Panels are a web of active org-mode pages that provide access to BISOS information, capabilities and services. Some Blee-Panels function as the equivalent of Unix Man Pages, which are active. There are many similarities between collection of Blee-Panels and the likes of Jupiter Notebook.
Collection of purposeful Blee-Panels can be accessed through augmented Blee menus.
You can further provision your Raw-BISOS system to become a
ByStar-Service-Platform. You can initiate the provisioning process with
the bisos-core/bootstrap/provisionSelections/kvmHosting Blee-Panel.
kvm, virsh, vagrant and basebox software packages will be installed.
With your ByStar-Service-Platform in place you can now create additional Raw-BISOS system as Virtual Machines (VM) or materialize existing pre-configured systems through their BPOs.
You can further provision your ByStar-Service-Platform system to
construct a ByStar-Rims-Site. You can initiate the provisioning process
with the bisos-core/bootstrap/siteGenesis Blee-Panel.
A minimal ByStar-Rims-Site includes:
- Gitlab-BPO-Server:
for private BPO realization- BISOS-Rims-Registrars:
for assignment of unique names and numbers in your Rims Environment.- Site-Manager-Console:
for providing visibility to your Rims services and applications.
With these foundational services in place, you can then add various Rims services and applications. Entertainment centers, security cameras, etc.
With your Rims Environment in place, you can now manage the needed BPOs for accessing ByStar internet services.
With your own ByStar-Rims-Site in place you are now ready to self-host your PALS services if you wish. This allows you assert your tangible autonomy and privacy on your email and content publication services.
With your own ByStar-Rims-Site in place you are now ready to realize your BPOs for the purpose of configuring your Usage Environment and for pairing of BISOS+Blee With ByStar Services and Abstracted Application Services (AAS).
BISOS Software can be categorized in two types.
- Native BISOS Software:
Software that we have developed.- Adopted BISOS Software:
Software that we have adopted.
BISOS Software can be thought of a collection of software packages of different forms and of different origins. For each type of software, in this section we provide an overview and identify their origins.
All BISOS native software is publicly available and is Libre-Halaal software — subjected to Affero GPL.
We use Github and PyPi as public repositories. BISOS native software is structured as a set of repositories across a number of github organizations. Here, we provide an overview of these organizations and repositories.
- PyPi bisos. namespace:
Some BISOS native software is released as pip packages. Some pip packages are not python modules and are in the form of bash-ICM scripts which allows for their convenient installation through pipx during bootstraping and prior to establishment of /bisos bases. All BISOS native pip packages are under the bisos namespace. T- Github Organization — https://github.com/bisos-pip:
The complete sources for PyPi bisos pip packages are are maintained in repositories of this github organization.- Github Organization — https://github.com/bisos:
Various directories under /bisos map to repositories of this github organization.- Github Organization — https://github.com/bxGenesis:
Thestartrepository andprovisionersrepository ofbxGenesisorganization are used for initial bootstraping of Raw-BISOS.- Github Organization — https://github.com/bxplpc:
Some final form ByStar and BISOS documents are maintained as repositories of bxplpc organization.- Github Organization — https://github.com/bx-blee:
Some Emacs library packages are maintained as repositories of bx-blee organization.- Github Organization — https://github.com/blee-pip:
The complete sources for PyPi blee pip packages are are maintained in repositories of this github organization.- Github Organization — https://github.com/blee-binders:
Collection of Blee-Panels (as org-mode files ) are maintained in repositories of this organization.
For details of which BISOS native packages are installed, follow
raw-bisos.sh.
BISOS adopts many software packages from many repository sources.
These software packages have different copyright licenses but all the copyright license of these packages qualify as open-source. This means that all of BISOS can be reproduced from their source code.
For each type of packaging (debian-apt, pip, emacs-library, npm) BISOS adopted software is retrieved from its primary repository.
Here, we provide an overview.
- Debian apt packages:
Debian apt packages are installed directly from http://deb.debian.org/debian.- PyPi Python pip Packages:
Python pip packages are installed directly from pypi.org.- NPM JavaScript Packages:
JavaScript npm packages are installed directly from npmjs.org.- Emacs Library Packages:
Blee usesstraight.elto manage emacs packages and pins them at specific versions from elpa.gnu.org and melpa.org.- Miscellaneous Secondary Debian apt packages:
A few Debian apt packages are installed from repositories outside of debian.org.- Miscellaneous Github packages:
A few packages are installed directly from github repositories.
For details of which BISOS adopted packages are installed, follow
raw-bisos.sh.
BISOS is an over Debian layer and follows its own policies for accounts, directories and other aspects of Debian.
Here we provide an overview of directories and accounts.
Initial installation of Raw-BISOS results in creation of a number of accounts and groups on your system. These are:
- bisos:
A non-login account belonging to group bisos. Many BISOS files and directories belong to this user.- bystar:
A login account that is by default used.- bxisoDelimiter:
An used non-login account with the uid of 1000000. Based on their numerical uid, all BPOs on this system will be sequentially created after the bxisoDelimiter account.
Initial installation of Raw-BISOS results in creation of a number of root directories on your system. These are:
- /bisos:
All of native BISOS software and information resides under the /bisos directory.- /bxo:
BPOs are realized and activated as BISOS accounts. Home directory of these accounts reside under the /bxo directory.- /de:
Information related to other digital ecosystems reside under the /de directory.
A brief overview of the /bisos directory follows.
- /bisos/git:
When git repositories are cloned, they are stored under this directory. All native git repositories are cloned under the /bisos/git/bxRepos repository.- /bisos/venv:
A number of Python Virtual Environments are created and maintained under /bisos/venv/py3. These support development and reliable adoption of python packages.- /bisos/pipx:
A number of Python pip packages are installed under /bisos/pipx using pipx.- /bisos/blee:
Emacs related libraries and native blee elisp code is maintainer here.- /bisos/core:
Bash and Python scripts of BISOS are maintainer here.
The ByStar digital ecosystem employs the BISOS platform, comprised of various development frameworks utilized for the creation of applications, services, and software-service continuums.
BISOS platform’s development frameworks are language-specific and domain-specific but are consistent and integrated. The BISOS development frameworks encompass:
- PyCS — Python Command Services:
BISOS uses the PyCS development framework for configuring and integrating related software packages to create consistent services, applications, and software-service continuums. Numerous Python command scripts, employing the PyCS framework, collaborate to integrate selected software packages towards the implementation of applications and services. Additionally, the PyCS framework supports the development of Remote Operations (RO) — using RPyC, which are equivalents of traditional web services and microservices.Section “PyCS: BISOS’s Integration Framework”, provides an overview of PyCS.
Python virtual environment of PyCS is at bisos/venv/py3/bisos3. Many PyCS scripts are housed in bisos/core/bpip/bin.
- ICM — Bash Interactive Command Modules:
BISOS employs ICM development framework for configuration and integration of related software packages towards their integration.ICM is a script-oriented, Bash-based development environment similar to PyCS. ICMs require minimal external support and self-contained and stand-alone ICMs are used for bootstraping BISOS.
BISOS ICMs primarily reside in bisos/core/bsip/bin.
- Blee Libraries:
Blee libraries are a set of Emacs Lisp (elisp) libraries that provide for a framework for development of Blee applications.Section “ByStar Libre-Halaal Emacsu user Environment (Blee)” of the book, provides an overview of Blee.
Within the BISOS platform, Blee libraries reside in bisos/blee/env3.
- LCNT — Libre Content Development and Publication:
LCNT offers a LaTeX-based environment tailored for the creation of multimedia content, spanning across various formats such as books, articles, websites, videos, and more. The LCNT framework encompasses content generation, autonomous publication, and content syndication. This book was developed and published using the LCNT framework.Section “BISOS Content Generation and Self-Publication” of the book, provides an overview of LCNT.
Within the BISOS platform, LCNT facilities reside in bisos/core/lcnt/bin.
These four frameworks are aware of each other and are consistent and integrated.
All of these frameworks and their languages — Python, Bash, elisp, and LaTeX — are developed in a flavor called COMEEGA. Section “Collaborative Org-Mode Enhanced Emacs Generalized Authorship (COMEEGA)” of the book, provides an overview of COMEEGA.
Our general strategy has been to:
Think Big, Start Small, Never Give Up
As described in the previous 3 chapters, the overall architecture and design of the ByStar digital ecosystem and BISOS are now well in place. We have been gradually implementing key building blocks of ByStar and refining design of BISOS based on our implementation experiences. We have been at this for along while and what is in place is no longer all that small. However, we have chosen not to publicly release many of our services and accept the burden of a significant user base.
ByStar is a perpetual work in progress. Enough is functional for us to expose certain parts. A starting point is now in place.
Thus far ByStar has been developed by a very small team. The primary author of this book is also the primary designer and implementer of most of the ByStar integration.
Our implementation focus has been on the fundamentals of ByStar, Possession Assertable Libre Services (PALS) and ByStar’s unified development, management and usage environment Blee (ByStar Libre-Halaal Emacs Environment).
The general structure of PALS (Possession Assertable Libre Services) is in place and our primary focus has been two fundamental autonomy and privacy oriented services.
- Private Email Services
- Autonomous Content Publication
These are now in place and are available for general use. You can self-host your autonomous and private ByStar email service. And you can self-host your autonomous and private ByStar content publication and web presence.
Blee (ByStar Libre-Halaal Emacs Environment) is more than the typical usage environment. Blee is also a complete IDE (Interactive Development Environment), and includes integrated systems deployment and management features.
At this time, Blee can not be considered end-user oriented — it is engineer oriented. Anyone familiar with Emacs, will immediately enjoy the fully integrated environment that Blee provides.
ByStar services and capabilities are self documented through org-mode based Blee panels. Blee panels are active and function as a layer on top of command line.
We encourage and facilitate collaborative development of BISOS and Blee.
For Python, Bash, Elisp and LaTeX we use a combination of org-mode and
the native language mode of Blee/Emacs. We call this COMEEGA —
Collaborative Org-Mode Enhanced Emacs Generalized Authorship. COMEEGA is
a Blee concept and an Emacs package for enhancing readability and
usability of various authorship-major-modes with augmentation by
org-mode content. For additional information about COMEEGA, see:
https://github.com/bx-blee/comeega
Those wishing to participate in BISOS and Blee development, should use COMEEGA.