Language Selection

English French German Italian Portuguese Spanish

Manjaro Past, Present and Future: A Virtual Roundtable

Filed under

Like a lot of people, I’ve been watching Manjaro rise in popularity (at least according to Distrowatch and Internet chatter). Manjaro, a fork of Arch Linux, is often divisive, one of those distros that people either love or hate, with not much in-between. I was curious about the project, so I reached out to the project leaders, who shared my questions with some other Manjaro team members.

2. How would you describe Manjaro to a new user?

Philip: Manjaro is a user-friendly community around an Arch-based distro. You find people who use and share their experience with and about Manjaro. Everybody is welcome to find his place in our community. And yes, it is an OS for beginners willing to learn and those who want to have full power off their system.

handy: Manjaro uses the Arch rolling release package management system which I consider to be the best package maintenance system available for desktop computer users. It enables a user to install once and then upgrade their system daily if they so choose. This system obviates the need to re-install their OS until their machine has the type of hardware failure that requires re-installation (most likely a HDD failure).

rest here

More in Tux Machines

Today in Techrights

A few thoughts on OpenBSD 5.8

I've been using OpenBSD since way back at release 2.3 in 1998, so I've gone through upgrades that took a fair amount of work due to incompatible changes, like the switch from ipf to pf for host firewalling or the change to ELF binaries. The upgrade from 5.7 to 5.8 was a pretty smooth and easy one, for the most part. The two most painful changes for me were the replacement of sudo with doas and the dropping of support in the rc.conf for the pf_rules variable. While sudo is still available as a package, I like the idea of reducing attack surface with a simpler program, so I made the switch. The two things I miss most about sudo are the ability to authenticate for a period of time and the ability to have a single config file across a whole set of servers. The former I'm just living with, the latter I've adjusted to by having a single config file that has lines commented out depending on which server it's on. I did have one moment of concern about the quality of doas when it incorrectly reported the line number on which I had a syntax error in the config file--fortunately, this was just a failure to increment the line count on continuation lines (ending with a "\") which is fixed in the -current release. Read more

10 recently open-sourced products from big tech companies

Releasing internal products to the open-source community is the hip new thing for technology giants to do Read more