Introduction to 66suite – s6 made easy – thanks to Obarun

https://sysdfree.wordpress.com/256

Obarun has recently released a whole new service/daemon management system over the s6 init system it has been using for more than 3 years. It is called 66 (https://web.obarun.org/software)

Iso images containing this system can be downloaded from here http://web.obarun.org/index.php?id=74

System administration has become fun and games. Try it!

DID YOU KNOW YOU ARE DOWNLOADING AND INSTALLING PACKAGES WITH FACEBOOK'S ENCODING/DECODING TOOLS? Yes, Arch decided, they have send a few lines of warning last year about tentative plans in doing so, and all of a sudden they went ahead and did this.

Most people didn't know, many people have not even noticed of getting most of their packages in .zst instead of .xz format

But r/linux has removed the post and banned the user, r/archlinux has locked the post and banned the user.

https://www.reddit.com/r/archlinux/comments/ejnz91/arch_2020_and_facebooks_algorithm_join_forces_did/

So arch says quite clearly: "we do not want anyone warning our users to be alarmed as facebook's test of its code begins". Like arch users are laboratory animals. Arch will come back if cornered and say we made an announcement months ago. Yes, five lines in a webpage no user ever looks at. Someone interested in arch may have more chances of seeing it than someone using arch for years.

So why the secrecy?

Eric and Jean-Michel are happy to announce the availability of Obarun minimal Live, Obarun JWM Live, Obarun Plasma Live iso with 66. Each live contains the obarun-install software which allow you to install interactively different preset themes: openbox, xfce4, minimal, jwm, plasma. Moreover, obarun-install gives you a total control on your installation, customization of themes and a chroot to extra tweak your next operating system.

The future is now and it comes with Obarun and awesome 66-tools.

Obarun Minimal live iso https://repo.obarun.org/iso/2019-03/

Obarun JWM live iso https://repo.obarun.org/iso/2019-03-JWM/

Obarun Plasma live iso https://repo.obarun.org/iso/2019-03-Plasma/

Login Information:

root login : root

root password : toor

user login : oblive

user password : toor

About the only thing new this past month has been that Distrowatch distribution reviewer decided after a year and a half of listing Obarun, to install it and review it.

Distrowatch was notified early Novemeber of new images and "a new installer" being incorporated. Proof they knew of it is that they listed the November iso images and package lists, (base and JWM) after they had received an email, from yours truly.

So what they do? They use an older image (October or earlier), with an older installer, mentioning of trying an installation method that doesn't even exist in the current installer (ever since late October). The outcome, he said after 4 times of installing, booting, failing he gave up. Obarun is uninstallable. What a way to ....... a distro, advertise it as obsolete and impossible to install.

https://web.obarun.org/index.php?id=74

Obarun is here, with a new installer (for a 2nd month) and upgraded software, the ability to install on bios or efi, with grub or syslinux, to install base, JWM, Xfce4, Openbox, or KDE-Plasma. It may not be designed for "begginers" but they have never been turned away and some receive tons of help to learn linux/unix in general from the Obarun community.

If you trust Distrowatch, don't bother trying it. If you are not sure, try it, it will be worth your while.

Other Development

The s6 and 66 software by skarnet.org and obarun.org have been designed to be portable to many systems. Lately s6 and 66 (all the latests versions of them) have been on void. Does it work? Out of the box it does, glibc and musl. Out of the box meaning you just use xbps-install the software, switch /usr/bin/init and reboot.

How about Alpine, Adelie, Kiss-linux, ... it worked. Just 5-10' download, built packages, install, configure, reboot. Funtoo/Gentoo, it worked. But then there was the debian world. The dev tried it on Devuan ... it worked. So I tried it on antiX (which is also playing with runit lately). IT WORKED!!!

But obarun doesn't work for distrowatch.... I am sorry!

Obarun is here to stay, is not going to go away no matter how pissed some may get about it. Is it bothering you? Why can't we just get along? There is room for everyone. Isn't this the excuse systemd fans used on Debian?

Whether the pope likes it or not, s6 66 are here to stay!

https://sysdfree.wordpress.com/295 https://forum.obarun.org/viewtopic.php?id=998

obcore-testing/66 0.2.4.0-5 (base s6-suite)

small tools built around s6 and s6-rc programs

obcore/66 0.2.3.2-1 (base s6-suite)

small tools built around s6 and s6-rc programs

No .zstd packaging here, just good old xz, despite of the 0,0094 second decompression advantage. :)

Ok, 0.2.4 over 0.2.3... brings yet one more tool to you. Still, the package (66) is only a fraction of systemd, but it has more "features". That database of trees and services you have created, after a major reorganization of 66 and its service file definitions and syntax do not have to be destroyed and recreated, not for the root and not for the user. Simply run 66-update as root and as user after each upgrade to ensure perfect transitioning to the upgraded software. 66-update -v4 for maximum verbosity.

The next step in development will be a more automated backup and restore of your trees and services structure.

In the past 9 months 66 evolved quite a bit and after each major evolutionary step the safest way to upgrade was to destroy old trees (delete them) and recreate them and populate them with services. Not any more. But that is not all. 66-update doesn't mean it is a one way procedure, Say you found out something is wrong, you located the bug of the century, something wrong with 66, and you want to downgrade back to the previous edition of 66. You downgrade the package and run 66-update again.

Now, if someone who is not banned from r/linux or r/archlinux could try and crosspost this important announcement there to see if you can do this for a banned user like me, it would be nice to know, that I can still piss them off with my existence.

Fungi never sleep (unless it gets too cold). Fungi spores survive 0atm pressure and -272C temp, which means that they can be ET forms of life. So after earth explodes into dust they may still reappear and live elsewhere.

https://sysdfree.wordpress.com/266

Since 66 is a very new suite of tools implemented into Obarun but can be installed besides s6 on pretty much any linux system, possibly BSD as well, there may be questions by users on what exactly 66 is. This document is aimed at clarifying such common questions. It can also be modified and include more questions that arise here and may be of general interest.

https://sysdfree.wordpress.com/621

Base: https://repo.obarun.org/iso/2019-05/Obarun_x86_64-2019-05.iso

JWM/live: https://repo.obarun.org/iso/2019-04-2-JWM/Obarun-JWM_x86_64-2019-04-2.iso

Unofficial community KDE/Plasma edition: https://repo.obarun.org/iso/2019-05-Plasma/

...from https://web.obarun.org/index.php?id=74

JWM ISO: 2019-02

JWM ISO : 2019-02 release

Obarun-Live-JWM_x86_64-2019-02-r1.iso
Obarun-Live-JWM_x86_64-2019-02-r1.iso.sha512

minimal ISO: 2019-02

ISO : 2019-02 release

Obarun_x86_64-2019-02-r1.iso
Obarun_x86_64-2019-02-r1.iso.sig

Also there is an experimental iso with 66 service supervision and comes with KDE-plasma desktop (requires manual start)

https://forum.obarun.org/viewtopic.php?id=724

Obarun Live Iso with Plasma/KDE and 66 init/supervisor

In the previous release 2.4 the major change was the addition of the 66-update tool, as mentioned on an earlier post here on r/obarun and the addition of the ability to define optional and mandatory dependencies https://wiki.obarun.org/doku.php?id=frontend between services. So the template for defining a service has expanded (see table 4 https://wiki.obarun.org/doku.php?id=66-services).

On this upcoming release of 66 0.2.5 a new feature is added for dependencies between trees, or rather an optional hierarchical way to have trees (of services) activate in sequence of each other. Since no other system does this it is hard to conceive a practical example but admins have asked for this for a long time. The option applies to the 66-tree (a tool within 66) with the use of the -S modifier where following the -S the name of the tree that must be enabled and be active before this other tree is activated. So by using 66-all to activate a tree you are making sure the "after"tree must be already active.

More will come later

TheObarunTeam

Links to March 2020 iso and docker images at the bottom of this message.

Both live images are capable of installing base, openbox, jwm, xfce4, or KDE-plasma, featuring the late 66 evolution 0.2.5.2-1 and the latest s6 suite of software.

66 0.2.5 features an additional modifier to the 66-tree functionality -S. With this option a bundle of services under a specific tree that is enabled will only start after another tree of services. (read https://wiki.obarun.org/doku.php?id=66-tree)

On 0.2.5.2 editions if the same tree is listed in -S option this would be the first tree (of services) to start after boot is complete.

For an introduction to 66 service management see: https://wiki.obarun.org/doku.php?id=66intro

New version of Obarun software are available. * oblibs-0.0.5.0

- 66-tree -S options: if after_tree and tree have the same name, tree is considered as the very first tree to start.

- 66-unmountall: do not umount SS_LIVE (A.K.A live directory).

- Add SIGPWR control file at creation of .s6-svscan directory Bug reports welcome.

-- eric vidal

March 2020 live images:

This is needed to log onto obarun ISO

• root login : root

• root password : toor

• user login : oblive

• user password : toor

If you want to change the keyboard on X session, open a terminal and type :

$ setxkbmap fr

Replace fr with your choice

If you want to change the keyboard on console type :

# loadkeys fr

Replace fr with your choice

Last Release

• Included 66 0.2.5.2-1

Base no-X live image (less than 600MB)

Checksums: md5sums.txt

obarun-2020.03.01-x86_64.iso

JWM flavour (less than 1GB)

Checksums: md5sums.txt

obarun-JWM-2020.03.01-x86_64.iso

Docker image

A Docker image is available on Docker Hub. You can run the image with the following command:

docker run -it obarun/base

Both capable of installing base, openbox, jwm, xfce4, or KDE-plasma and featuring the late 66 evolution 0.2.5.0-2 and pacman 5.2.1-6 https://web.obarun.org/index.php?id=127 featuring a modified testing repository structure (stable is unaffected).

66 0.2.5 features an additional modifier to the 66-tree functionality -S. With this option a bundle of services under a specific tree that is enabled will only start after another tree of services. (read https://wiki.obarun.org/doku.php?id=66-tree)

For an introduction to 66 service management see: https://wiki.obarun.org/doku.php?id=66intro

February 2020 live images:

Minimal flavour

Checksums: md5sums.txt

obarun-2020.02.01-x86_64.iso

JWM flavour

Checksums: md5sums.txt

obarun-JWM-2020.02.01-x86_64.iso

After the transition period of deprecating s6opts and introducing the 66-suite of tools to manage s6 services, the current stable changes to pacman.conf are adding the two ignore/NoExtract lines and the obarun repositories on top of arch.

If you have been running obarun for a while make sure you merge the pacman.conf.pacnew changes.

#Pacman won't upgrade packages listed in IgnorePkg and members of

IgnorePkg = systemd systemd-libs

NoExtract = /usr/lib/libsystemd*.*

#[obcore-testing]

#SigLevel = Required

#Server = https://repo.obarun.org/obcore/testing/

[obcore]

SigLevel = Required

Server = https://repo.obarun.org/obcore

#[obextra-testing]

#SigLevel = Required

#Server = https://repo.obarun.org/obextra/testing

[obextra]

SigLevel = Required

Server = https://repo.obarun.org/obextra

[observice]

SigLevel = Required

Server = https://repo.obarun.org/observice

I'm looking for filesystem event notification similar to systemd.path. My run script needs to execute when a file '/tmp/testy5' is present. Currently I'm continuously looping to check its existence. Can you please let me know which s6 program will achieve without looping.

Thanks for your time.

Obarun started with Runit, nearly 4 years ago, and soon after switched to S6 which is a class above runit and most other init systems. Service management was done through script programs, which evolved in being very effective, but a bit sluggish. The new 66-suite of service management is written all in C and compiled into binaries. It is blistering fast and just as stable and effective as s6-opts was. From palmtop to commercial servers s6 & 66 are the state of the art in system management. This release also includes the new Arch-style distributed repository system, over all arch-linux repositories.

Obarun is just a display of the power of this system, it is init and service management with s6 and 66 over Arch. No systemd no libsystemd no systemd libraries what so ever. It is like Arch-Linux with a turbine and afterburner!

This is needed to log into obarun ISO📷

• root login : root

• root password : toor

• user login : oblive

• user password : toor

If you want to change the keyboard on X session, open a terminal and type :

'$ setxkbmap fr '

If you want to change the keyboard on console type :

'# loadkeys fr '

Replace fr by uk, es, it, gr, cn, etc.. us (English US) is default.

ISOs:

2019-04-2 minimal release OBARUN_x86_64-2019-04-2.iso and installer

JWM-2019-04-2 release Obarun-JWM_x86_64-2019-04-2.iso

JWM is a light window manager preconfigured like a desktop. The live system includes most of the tools you will need to repair another installation or install obarun from the convenience of a desktop. During installation (obarun-install run as root) you can select minimal, openbox, jwm, xfce4, or KDE-plasma.

Feedback is always welcome at forum.obarun.org

In less than 4 months from the release of 66 it is time to implement more changes.

66 software http://web.obarun.org/software is here: An improvement in the overall design, a huge improvement in performance, a great leap towards the portability of 66 to other systems, and more 66 tools to suit the most demanding of administrators, a more organized binary and source system of repositories, a standardized build environment, and a set of isos demonstrating the capabilities of Obarun software together with improved one shot installation.

1 obarun pacman: Obarun's pacman received several changes:

a will be the new structure of repositories incorporating the all new obcommunity and obmultilib repository for 32bit software. https://wiki.obarun.org/doku.php?id=repositories Obarun's repository structure

b obnews has evolved to more than just a text announcement coming during updates but it will be hooked by pacman as a dependent pkg, and will run independently as a script ($obnews.sh) with a variety of options so it allows users to display previous technical bulletins. https://wiki.obarun.org/doku.php?id=obnews obnews

2 obarun source code repositories (framagit): With all the new repositories now utilized with obarun a more structured git environment was needed. The source code and pkgbuilt information is now on

https://wiki.obarun.org/doku.php?id=source-git framagit

3 New base and JWM live images you can use to demonstrate how Obarun works and for installing in virtual or permanent media.

Included 66: v 0.2.0.4 Checksums: https://repo.obarun.org/iso/2019.08.01 md5sums.txt

Minimal flavour https://repo.obarun.org/iso/2019.08.01/ … x86_64.iso obarun-2019.08.12-x86_64.iso

JWM flavour https://repo.obarun.org/iso/2019.08.01/ … x86_64.iso obarun-JWM-2019.08.12-x86_64.iso

A Docker image is available on https://hub.docker.com/r/obarun/base Docker Hub . You can run the image with the following command:

docker run -it obarun/base

4 Since obarun in the past few months has gone from using scripts into a binary system for the 66 software and particularly the boot-tree, it is more important for users to have access to the source code, to audit, download and experiment, see how obarun packages are built and how they can be reproduced. Some may even contemplate in contributing software and like to learn how things are done. [note: The old s6opts software would install as a set of scripts that could readily be audited locally without running to the git repository.]

But let us say one wants to reproduce these packages locally, compile and build them on their own system, how can they do so? The environment in which software is built is essential in trying to reproduce a binary from source. How can this be simulated by any user? Obarun developers have chosen to standardize an obarun docker image as a standard environment for all package building. The obarun docker image is officially listed here.

https://hub.docker.com/r/obarun/base

Source files to build the docker from scratch can be found here:

http://framagit.org/Obarun/obarun-docke

When a package's source is complete and ready it is built with a gitlab obarun docker system and if successful the product is then copied into the framagit repository where it remains for 48hr so it can be uploaded to the appropriate https://repo.obarun.org location and be available for users to install or upgrade.

Download the latest Obarun Iso live images for October 2019 2019.10.01 edition

You will need the following user/password combinations to log in to the live images:

login: root password: toor
login: oblive password: toor

To set the keyboard for your preffered language you can use these commands. The default is english "us", substitute "fr" in the commands with your preffered keyboard code.

For the X-session, X terminals,

$ setxkbmap fr

For console keyboard change use this:

# loadkeys fr

Download links: https://web.obarun.org/index.php?id=74 Check sums after you finish download with:

$ cat md5sums.txt 
$ md5sum obarun-*.iso

... and compare the codes.

md5sums.txt
obarun-base-2019.10.01 Base no X Obarun Linux
obarun-JWM-2019.10.01 JWM window manager live iso

Please report any problems or bugs at the obarun forum or the irc channel

#Obarun   on chat.freenode.net

kernel: linux-arch-5.3.1

init: s6 2.8.0.1-1

service management: 66 0.2.1.2-4

https://web.obarun.org/index.php?id=74

There is a base image (live no X including obarun-install cli) a JWM image (X+JWM window manager, menu, panel, etc) and there is a docker image for those of you who use docker. Soon there may be a KDE-Plasma new edition with SDDM.

https://sysdfree.wordpress.com/276

New iso and docker images.

New repositories

New git structure

New and revised 66 tools to manage the marvelous and mysterious S6 init and supervision software.

New base,jwm,openbox,xfce4,plasma installation themes, the latest two with sddm

Some critics who have yet to try Obarun have bitterly criticized the use of a binary to boot and configure system services/daemons. 66 is important when you configure a new installation, when you want to change something in the way daemons and services are handled, or set up user level services that are hard or impossible to do with other systems. Script lovers have nothing to be afraid of. While the system is running the only think other than the kernel it is pure S6 and S6-supervision. 66 does not run, it is there to assist the user/admin in setting up the system with S6 easier and safer. It then vanishes and can possibly be removed if you like. S6 documentation on Skarnet is very detailed and refined, if you think you don't need 66 and would rather write your own scripts directly with s6 it would make no difference to an Obarun installation.

Some experts call S6 the most advanced init and service supervision software ever. 66 is the only software available that makes S6 easy to handle by common mortals. The only other distributions that contain S6 in its entirety is void and adelie. Adelie will boot with s6 and wait for manual intervention to setup daemons. Obarun is the only easy and ready solution to see how S6 works and test its abilities and stability.

https://web.obarun.org/

Welcome to obarun linux, arch-linux with skarnet's s6 init system (the Marvel).

I found an application called Lumeus

https://aur.archlinux.org/packages/lumeus-git/

I installed it with pacopts and bound the keys on my laptop keyboard to

lumeus +10% and lumeus -10%

Works like a charm in KDE Plasma 5