Two new distributions (Sulinox and Split Linux) to keep an eye on were added on our 2 lists of systemd without systemd. The early first list of all systems we know without systemd (including BSD varieties) and our more detailed list of 66 linux distributions without systemd.
The first is called Sulinox, an independent linux distribution, built on glibc with OpenRC as init, a base software available on repositories with a few varieties of desktops, and elogind present, available for X86_64 architectures. The distribution is aimed at expert users who know and like to build packages from source. To do so in a more organized way and maintain system integrity Sulinox has developed their own package manager called inary. For those of you who like to keep an eye on the source repository of a distribution and follow development in detail we warn you that comments are in Turkish, although the rest of the documentation for the distro and the package manager is written in English. Continue reading
We had dedicated much energy in the past, 2 years ago, to advocate for Palemoon and you should at least read the piece about the NoScript parody, and how we gave up on it for specific suspicious reasons (still holds unchanged, Palemoon has branded NoScript as “dangerous” because it breaks pages). We had seeked refuge at Waterfox, retaining some old firefox functionality and ensuring us it is blocking all of Mozilla tactics of robbing you of private data and feeding it to “who knows who”.
Waterfox officially was sold by mr Alex Kontos to System1, a UK payperclick ad company, which it would be absurd to believe that it wouldn’t utilize the browser’s ability to feed their other interests with private data. Or why else would they buy to promote their own browser, to make all others break while they are getting robbed?
Thank you Alex for your sincere efforts and sleepless nights of coding, all these years, it has been a great ride, and it is too bad it had to crash in such a bad time for browser variety and period. Goodbye and good luck for all that you had done up to now.
First I would like to welcome cynwulf1 to the community and in specific to the small sub-sector of the community of contributors. Cynwulf1 appears to have been around this sport long and with a wide spectrum of experience. He recently contributed an article and some comments on the world of BSDism.
While recently I have worked closer with some of the creators of systems we use I have tried to learn how they think, or how they think differently from us users of systems. The question that appeared to me is whether they can possibly know or care what “people need” or are they just driven by what they need for themselves, which in some cases is a system to work on, while creating systems.
Artix, as mentioned here several times before, begun as a continuation of stable functional systems that existed for years. The one was Arch with OpenRC the other was Manjaro with OpenRC. Before Artix’s first year is complete a second init system is being modified to alternatively be used instead of sysv and OpenRC. Runit, the init system found in Void is developed by smarden.org where you can find detailed information about it. Runit can initialize your system, it can supervise processes, and it can end processes and end the cycle by shutting down. Alternatively Runit can act as a supervising system along with sysvinit or other init systems. Runit has been proven in Void-Linux for years as stable and capable, let alone one of the lightest in resource use. Continue reading
An interesting post by a person nicknamed as cynwulf posted this comment which I may disagree in a few tiny remarks, agree over all, and want to clarify what is generally perceived as political and what I consider to be political.
First it is better to read what Cynwulf had to say on the issue of security: Continue reading
In the Arch-wiki article there is a very nice concentration of practical solutions so you can avoid the use of “default” DSP provided by your WAN in case you do not have absolute trust on the DNS server logging your traffic requests. No matter what your reasoning is it is personal, but the idea of your activity being monitored and logged is commonly understood.
The detailed article is best read from the source, but a selection summary is copied below:
The configuration file for DNS resolvers is
/etc/resolv.conf. From resolv.conf(5): Continue reading
Edit your /etc/default/grub change GRUB_CMDLINE_LINUX=”” to :
If the biosdevname is installed you need to add :
$ sudo update-grub