Were you about to install Obarun? Wait!!

There are new images available for March 2020

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)

Continue reading

Spark Linux – Arch beauty and minimalism all in one

A while ago, an Obarun user, Dr Saleem Khan (1) urged me to try Spark Linux and it was the first time I heard of it.  It must have been during some real busy period and it was since forgotten.  While I was trying to clean up the list of linux distributions without systemd the name came up again.  Thanks, Saleem.

By no means do I think this is for entry level users to try as a distribution with a full desktop, but for minimalists who are accustomed to arch this is an exercise of how minimal can you get with a ready off the shelf arch base on which you can build from ground up.

The project is severely undocumented, although there is not much to document for an experienced user. Spark (by Jack L. Frost) uses sinit as its init system and ssm which is an inhouse Simple Service Manager by Spark founder.

Sinit according to its source suckless (they suck less) is:

sinit – suckless init

sinit is a suckless init, initially based on Rich Felker’s minimal init.

sinit is considered complete and no further development is expected to happen.

Relevant links sinit + daemontools-encore

sinit was created by Dimitris Papastamos and was “finished” in 2015, that I believe is a year after runit was finished as a frame of reference.
Continue reading

How does systemd prevail if it is so crappy?

Is reddit’s r/linux just a front of IBM’s marketing agents?  Under what remote logic would an announcement for a 5 year old distribution be removed and how could it possibly violate r/linux strict code of ethics?

Obarun: New for December …. upgraded yes, new not at all.
Sorry, this post has been removed by the moderators of r/linux.
Moderators remove posts from feeds for a variety of reasons, including keeping communities safe, civil, and true to their purpose

Those are the same tactics utilized across news-sites that appear to be “objectively” promoting linux in general, forums of systemd-only distributions, social media rooms and pages. The idea is to portray linux to new users inquiring about linux while on MSwindows, MACos, Android etc. as a systemd related operating system ONLY. Continue reading

Update your 66? no, you 66-update your 66

Coming up, any day now, is your new 66 package.

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.

 

PS  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.

Continue reading

Arch Linux 2020 – what’s there to be happy about?

Happy new year facebook fans and Arch friends (friends of who? we don’t know, not us, not on facebook, not in the past and not in the future, but you must have friends amongst yourselves).

Some of you may have taken the previous post about abandoning Arch as a joke, since most of what we do recently is promote Obarun, an Arch based distribution with s6 and 66 init and service management.   When we published that article we knew nothing of what Hyperbola was planning to do (we assume it was discussed within the community) or whether they were going to give-in to the pressure and incorporate arch’s pacman and packaging methodology change into their distribution.  (Note: Hyperbola may be based on Arch but has its own separate repositories and rebuilds everything on their own to ensure everything is Free).  All of their free packages, as far as we can tell are still compressed with xz.  The bomb was set and it will go off soon (in open/free software tradition of timing kind of soon).  Hyperbola is not just leaving Arch, it is leaving linux, for OpenBSD.  But this is not about hyperbola, it is about Arch….     or skip to here if you are in a rush! Continue reading

antiX – runit – brief stop and onto s6 and 66 : How to

1st some history/background:
Back some time ago an alternative to sysvinit was developed called daemontools (look at sources below) and people liked it.   From “it” runit was cloned, very similar but started from scratch, to be as small, as light, as simple, and as responsive as hw itself.  Runit set some goals for its development, kept being refined and eliminating any bugs, it worked on as many architectures as people could get their hands on, and the chief runit man decided to put it to bed.  Runit has been frozen in time by its developer.  Don’t expect it to catch up with other system development unless Void decides to clone it and develop it on their own, which in some ways they already do, but it is more polishing up the existing runit.

Continue reading

obarun-install and 66 updates

obarun-install program1  Can a good thing get better, and by how much?  Wasn’t 66-info good enough, transparent enough, detailed enough?  It was. It is no more.  Gone!

2  Wasn’t the Obarun-Install software one of the attractions in Obarun, I thought, was the precision and ease of the installer.  Gone (will be in a few days)!

1 66-intree & 66-inservice
One of the most used tools in the 66 suite of software was 66-info.  66-info -T gave information about service trees, and 66-info -S gave information about a particular service, its status, its configuration, its environment, etc.  Really useful tools that we lacked in most other init and service managers.  Well, it is gone, deprecated, dead and forgotten.  BUT WHY?

Continue reading