Boot/Shutdown console output on obarun or any 66 driven distribution

A hint/trick to control console output during booting and shutdown/reboot.

Users come in all shapes and forms.  Some users dislike looking at too much output on their console while the system is booting, while others like to see more, so if something is wrong they pick it up right away and go fix it and reboot.  Some prefer the aesthetics of looking at a splash screen (defined in their grub, lilo, or syslinux configuration).  With Obarun and any distribution 66 is installed not many complain about too much output, quite the opposite, people see very little and then either a console login prompt appears (indicating booting is complete and all predetermined services are up and running) or a display manager has kicked in and off they are to a graphic login screen. Continue reading

firefox-esr and Arch-Linux, masters of disasters – Mozilla Inc.

_package() {
pkgdesc=”$2 language pack for Firefox ESR”
depends=(“firefox-esr>=$pkgver”)
install -Dm644 firefox-esr-i18n-$pkgver-$1.xpi \
“$pkgdir/usr/lib/firefox/browser/extensions/langpack-$1@firefox.mozilla.org.xpi”

The above is a piece off of a late language pack for Firefox-ESR PKGBUILT

For whatever reasons Arch dropped official support for firefox-esr (mozilla’s development seems to have a growing crowd of rejecting their trending prostitution to corporate preferences, more people tend to go back to -esr versions, and Arch caters to all BIG CORPORATE preferences and tastes), but it is not our business what they do with their repositories.

Automatically, it seems, “someone” (DCT MEI and Manuel Kauschinger ), adopted those packages in AUR and as you may know each firefox product comes with a zillion language packs.  Only the binary package in AUR is called firefox-esr-bin, the dependency of each language pack is for firefox-esr, which doesn’t exist in community or aur.  You can force install it (-dd) or you can edit the pkgbuilt and edit the line above “depends=(“firefox-esr-bin”>$pkgver”) and then build it. Continue reading

Trident + void + zfs one step closer to 1.0

Trident project released a beta image following their alpha releases in the past two months.

For those who missed this developing transition, of Trident leaving its TrueOS/FreeBSD base and moving to linux using Void as its base, here is a summary of what you are missing.  It has been a common story for a distribution being fed-up with linux development, developers being consumed to modify their software around systemd-functionality, and have moved to some form of a BSD-unix base.  As far as we know there hasn’t been an effort to leave BSD to come to linux.  So Trident is drawing its own path making it now a 2 way street.  Here are a couple of juicy quotes of their late announcements:

2020 OS Migration

2019-10-14

…Currently, Project Trident is based on FreeBSD and uses the TrueOS build framework. Over the years, we have accumulated multiple long-standing issues with the underlying FreeBSD OS. Issues with hardware compatibility, communications standards, or package availability continue to limit Project Trident users…..

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

A year has passed and systemd is still around

There couldn’t be a better birthday gift to sysdfree.wordpress.com than an active community participation as in the dbus exorcism thread that has an active discussion on the project.   https://sysdfree.wordpress.com/232

A year has gone by and the “service daemon” systemd is still prevalent in the number of linux distributions; we can’t speculate on the number of users.  So we are not as effective and as “organized” as a community to defeat it yet.  Therefore we must try harder.  We should take a step back though and assess the status and development of the community consciously striving to stay away from systemd, its derivatives, and its relatives. Continue reading

Speck: Before you use Linux 4.17 read about it

It seems that “Speck” is a long term project to standardize encryption that goes around the internet.  It seems as the NSA has been the primary force proposing what is “pretty good” encryption and what is not.  It doesn’t take a genius to assume that only encryption that can be decrypted by the NSA can be proposed.  So this set of new rules is making its way into your open and free software.  It is in Linux 4.17, not on 4.16 or previous ones, and 4.17.1 was just announced as stable yesterday. Continue reading

To swap or not to swap

Swap space or swapfile use or no-use seems to be among the most common controversial issues in linux. If you wonder why would we engage in such a controversial topic we can explain. Most people using linux today who have relatively new multicore 64bit machines have huge disk drives and more ram than they can possibly use (except for video editors and game players). Most people who get on the hunt for lighter, simpler, easier to control and configure systems tend to end up searching among systems that don’t use systemd. So smart users with older cheaper equipment enjoy sometimes better computing performance than many who have the latest and hottest machine with a mediocre system. So using or not using swap is sometimes a choice between hunting for more RAM or more disk space use. So we thought we should take a shot and help out on this dilemma. Continue reading

FigOSdev takes back what he said about Dbus

Maybe I Take Back What I Said About Dbus       by FigOSdev

Despite what I’ve said about worrying about Bus1 (I’m not worried) I’m increasingly of the opinion that getting rid of Dbus or making it easier to remove is a good idea.

The idea is, you shouldn’t have too much software that is running or even installed when you don’t need it. That’s really simple; defining “too much” is not, but…

I have Dbus installed. I am quite capable of finding every file it installs, and removing that file. I can stop it from installing again– no problem!

There are things I have installed that depend on it– probably also not a problem. However, let’s look at what those are: Continue reading

Void linux revisited – do not aVoid!

We finally managed to get a box that was able to boot up the void live image (LXDE) that we were having problems with in the past.  So 48hrs later we are here to report on the experience.

This is the first distro that we are covering that relies on itself and not some other systemd infected distro.  The rest we have been following are either Debian or Arch based.  We did receive some heat for making a prejudicial comment in an earlier article, about void being related to Arch, or being similar at least.  Ok, maybe it made the wrong impression while running in a VM, but we don’t care too much about VM installations anyway, so we didn’t spend much time with it.  That command xbps-install -Suy just reminded us too much of pacman!  😉 Continue reading

U/EFI secure boot and debian/microsoft-ization

A short story: In recent years PCs have increasingly shifted from having a bios in charge of booting, whatever system can possibly boot from, to a system called EFI.  EFI in brief seeks a boot partition on disk that can be edited and filled with OS instructions on how the kernel of a system will be initialized and built.  A UEFI is a more specific form of an EFI that also introduces secure boot.  This means that only certain systems that are considered as “safe” can boot and such systems are certified and are issued a key (for a hefty fee of course). Continue reading

Linux kernel 4.13 on Devuan and on Artix [Fixed]

My test machine is an aging, stock (unmodified), mass produced enterprise grade, machine made by Dell.  Ever since my Manjaro days (Manjaro-OpenRC) when the first beta edition of Linux413 was released, it was the only kernel I have ever had problems with.*  It always appeared to boot fine and only when X was about to start all input devices would freeze.  Nothing in Xorg.0.log seemed to appear as an error.  The machine would just lock up and only mechanically could it be rebooted. Continue reading