Arch-linux building from source – and Obarun to the rescue

What if, there was a benefit in building from source, a system that is commonly used by pre-fabricated binary packages, like Arch or any of its forks and desktop flavors?  What Arch considers a “clean-chroot” is primarily of need to developers ensuring their package can be both satisfied for all dependencies AND are reproducible, as long as this can be achieved within a constantly rolling distribution.  That is open and nearly free condition for you.

Why

Building in a clean chroot prevents missing dependencies in packages, whether due to unwanted linking or packages missing in the depends array in the PKGBUILD. It also allows users to build a package for the stable repositories (core, extra, community) while having packages from [testing] installed.

Scratch most of this for several reasons.  We are not developers, we are building our own system like Gentoo-ers, k1ss-ers, Crux-ers, and others do.  We want to make sure that each of our packages fits well within the parameters of our specific machine, and it wasn’t built on another machine that may not be 100% compatible to ours. Continue reading

Openbox tweaks and tricks – no {dbus,ck2,elogind,dm} no user services needed

Although this was created with Obarun/Arch based distros in mind it works pretty universally for nearly all distro that have openbox available (nearly all except for Adelie that is).  About building and installing obmenu-generator there is an older article here.

Originally published in the Obarun Forum, so here is a copy:

Openbox tweaks and tricks – no dbus – no ck2 – no user services

Minimalist tricks and treats

To start you need xorg-xinit and openbox installed:

From AUR download, build, and install obmenu-generator

You can use pacopts or cower if you don’t have something else as an AUR helper, ask for help if you want details, especially if you want to install yaourt, the best AUR helper ever created which was taken off AUR for a second time in less than a year.  I wish they would make their minds up! Continue reading

New Obarun live image based on all new 66 0.4 edition

A new Obarun live image has become available on July 10th 2020 and it brings many updates and changes.  From the live JWM session you can install a base system, Openbox, JWM, XFCE4, or KDE-Plasma with corresponding setup of 66 root and user service structure already set-up.  All recent (July 9th 2020) stable Arch-Linux upgraded software based and a much improved installer is onboard.  You can run the live system off of a CD (still fits) or Dvd or USB stick, or a virtual machine as a common disk system or a RAM only system from its syslinux editable boot menu.

NOTE:  Previous Obarun images and installer may not work without manual intervention to incorporate the new GPG keyring for Obarun.  Therefore older versions of pacman will not upgrade or install software, hence the net-install process will fail. Continue reading

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

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

Where to move to after Arch-Linux-based non-systemd systems?

VD, HIV, STD, Zstd

The deeper issue here is “what is the relationship of Arch-Linux and Orwell?”

Two of the most common intrusive sites reported by linux users that are placed on top of the list of a firewall, so nothing goes in and out between their machine and those sites’ servers, are Google and Facebook.  Google on the one hand, in order to play nice against the free/open software community, has been contributing resources, information, and free/open software to improve their image.  MS purchased github, IBM purchased RedHat, or should we say they made their relationship more formal.  Some developers have fallen for it.  Facebook on the other hand is notorious of flooding the machines of their innocent and unsuspecting users with questionable code.  Facebook not only knows who you really are, what you really like, what you think and what you are interested in, in the vast majority of cases they know in real time your exact location and may even have the capability of keeping track of your moves.  Simply if you have an account on facebook and accessed it once through your “smart” phone, they know.  If you access facebook from your desktop, but on smart phone you only use your google account, they know.  They, they, who is they?  If you are really asking we can go on comments for as far as you can take it. Continue reading

What is so new about Obarun that makes May’s edition obsolete?

There are several new things about Obarun that make the last batch of isos seem like they came from a different distribution.  But it has been emphasized by its founder that Obarun is not a distribution but a modification of an arch-linux installation.  I don’t for how long would this description be accurate, Obarun now looks like its on its way of become a complete and independent distribution, still based on Arch-Linux. Continue reading

Latest Obarun installation/live images released (base, JWM, KDE Plasma)

Since the Fall of 2018 Obarun has committed to publish a new base iso-image (Obarun_x86_64-2019-05.iso) every month. The current installer updates itself from the obarun git repository when it starts.   The installer allows you the ability to select desktops and software during installation or install a base system, boot and customize on your own.   2-3 times a year a new live-desktop image using JWM is also published.  This is the latest iso with JWM published mid-April (Obarun-JWM_x86_64-2019-04-2.iso).
Since the major new release and change of repositories in April 2019, along with the introduction of Obarun’s own 66 management system over Skarnet’s S6 init, there have been minor refinements reflected in the new iso.  So if you have last month’s images there is no need to download the newer one. 
Although I never liked anything KDE myself I tested it and it works flawlessly.  For those who want to install plasma, although possible with the installer from other isos, it might be helpful to have the live image handy to see how user services are employed and handled by 66 and required for plasma.
Older images (before mid-April 2019) may require some attention and manual intervention to incorporate the changes in repositories, although the installer may take care of the change.

Continue reading

Convert Obarun s6opts to the new 66 system

Since we have published here a few conversion proposals from Arch-based distros to Obarun (replacing systemd with S6) for a few more months they will still be valid, but Obarun has switched to a new more comple repository structure AND service management.  The difference is that beyond the s6 init system the service management is handled by a set of new tools called 66.  If you want to make the switch you must follow the instructions below.  There is also a new package you may want installed called obnews, and when essential system administration tasks are necessary the news piece will come at the end of the pacman -Suy update/upgrade procedure.  Currently it notifies sys-admins of the new repositories and of this conversion.

Continue reading

Convert any arch-based distro from systemd to openrc

@artixnous artixnous

@nous from artix has issued a script that will switch an arch installation (and most arch based distros) from systemd to operc. For runit this script is easily adoptable and equally easy to convert from openrc to runit and back, following the wiki procedure.

The procedure has been elegantly labeled FUCKTHESKULLOFSYSTEMD

You can download the script and save it, then run it as root, or copy the text below into a script and run it, or you can just follow it by running each command manually so you can understand the process better.

Your original pacman.conf will be backed up at /etc/pacman.conf.arch – ENJOY

 Continue reading 

ArchLabs without systemd – Obarun s6 on top

You may ask what we are doing with ArchLabs when there is a tremendous amount of original non-systemd based distros on the list (our own lists for example).   “Originally a minimalist, Arch-based live distribution with Openbox, the latest release of ArchLabs Linux is a radical departure from the original concept as the distribution is now designed for users who like to customise their system during installation. ”  It may be coincidental but the installer is following a bit on the Obarun fashion where you install what you need and like and not what the distribution has chosen.  Continue reading