Goal: Examine Package Manager, Focus on Command Line Interface
Heaven does exist !
I have been dreaming of having my own lab, examining variety of package manager, using my own notebook. Five years has past, yet still broken dreams I have. I cannot afford high end machine with virtual machine performance. Like a dream come true, docker allow me to install, other distribution without CPU burden. I finally fulfill my destiny.
I can use Docker to learn package management such as, Crux’s Ports, Gentoo’s Portage, Slackware’s Package, Void Linux’s XBPS, Fedora’s DNF, openSUSE’s Zypper, Debian’s APT, and LFS’s Build. Of course they are all interesting.
People see Diversity in Linux, as Distribution. Beginner can see how a system can use many Desktop Environment. And coder can see that they can rewrite from one scripting language to another. This is true, but inaccurate. There are other frontier, that is actually fundamental, from the perspective of Operating System.
I do think that we need more focus on other main diversity as well such as
This will encourage beginner to go deeper, than just mainstream blogger topic, such as apt, systemd-based, and ext4-only. Enable broader range of discussion. Gain more diverse knowledge. Thus empower our beloved community.
But I could be wrong about that.
As a result, beginner should narrow how to choose their OS, from choosing distro to choosing package manager.
An enthusiast user should experience package management diversity in linux. And try each. Otherwise, most beginner would stuck, in the mainstream APT-based distribution, as you can see the fact in distrowatch top list.
The issue with package management learning is, you have to live with it.
The downside of learning package manager is, the need of good internet connection.
There are a few methods.
Multiboot. But install so distribution many would be exhausted.
Virtualization such as Virtual Box. I only have dual core.
Docker or LXC. I actually use docker to learn other Portage and Slackpkg. This is suitable for my resource limitation. As an alternative, there is this LXC. I do not use LXC anymore.
Live OS (not recommended). You cannot just use flash disk, trying some command line, and pretend you understand package manager.
Persistence Docker Process
Anyone new with Docker should differ between LXC and Docker. With LXC, the state changed as we exit each image. With Docker, each time we run image, docker spawn a new process.
We need a persistence state that our distro keep the change we made after exiting the session.
This is why we should beware of the flow. Docker is different with LXC. Docker has image, and process. Each image an be spawn into several container process.
I wish you luck
This is some mainstream Package Management in Linux.
APT: Advanced Package Tool
ALPM: Arch Linux Package Management
RPM: RPM Package Manager
XBPS: X Binary Package System
As for enthusiast user I give link for each source code. I am sure you all love manual.
Do not forget to read the manual first.
Why don’t we go further to read the source code ?
Approximate Timeline for Linux Package Manager Frontend
Data taken from NEWS, wikipedia, Github First Commit, and Change Log. This may not be accurate.
maybe 1993: pkgtools/slackpkg
Flow for Learning Linux Distribution
Since we want a persistence distro, we only need one process. So here the step.
(1) Terminal 1: List all images.
If this is empty, you can pull for docker hub.
(2) Terminal 2: List all processes.
This list could be emptyor has several processess. You can delete all unnecessary processes, and start with a clean process.
Note that you can show based on docker id, or docker names.
You can add the size, so you can monitor how the process grow as you work with your container. But size take a longer calculation as a drawback.
(3) Terminal 3: Run an image to create process
Do use interactive.
And exit from process. You can start later.
A new process will be shown in process list such as inspiring_davinci. Docker give random name automatically.
(4) Terminal 4: Attach process to your favorite terminal
Do not forget to press any character. The docker wait for your response.
After you exit, you need to start the process again.
(5) Open New Terminal
Tips: Without sudo
To avoid typing sudo all the time,
add user in
Do not forget to logout, and relogin.
For convenience you may put aliases to
OS: Artix Linux
Alternative: Artix LXC
OS: Artix Linux (formerly Manjaro-OpenRC)
Window Manager: HerbstluftWM
Wallpaper: Original Wallpaper
Alternative: Manjaro LXC
Window Manager: Awesome (floating mode)
Running: pacman, emerge, yum, apt
These are some docker containers, that I utilize in this blog.
For each I provide the command.
In addition the default
you can use other tag such as
There are [ links ] for each docker topic, each article has deeper package management discussion.
Article: [ Slackware - Package ]
: Slackware: C
- Package Cache (slackpkg)
Article: [ Gentoo - Portage ]
Article: [ Void - XBPS ]
Article: [ Crux - Ports ]
Pkgutils: Crux: C
ALPM Frontend, ASP and AUR Helper”
Article: [ Arch - ALPM ]
ALPM = “Arch Linux Package Management”
Note that ABS tools is deprecated.
Package Query: C
I do not cover RPM here.
RPM is special in a way that RPM has many front end implementation.
URPMI: Mageia: Perl
Article: [ Fedora - DNF ]
DNF (Dandified YUM): Fedora: Python
Article: [ openSUSE - Zypper ]
Article: [ Debian - APT ]
DPKG: C: Eight Years Ago
- No github yet
- No github yet
- No github yet
Article: [ LFS - Build ]
Sol (eopkg replacement in Solus): C
My intention is to give appreciation to the community, because I have many riddled that, I can’t solve without help from the Community. I hope this people do not mind that I put their name here.
Arch Linux: “Dean Wallace”:
Fedora: “Станислав Нижниченко:, “s10e G” , “Flavio R. Cavalcanti”
openSUSE: “Tim Baker”:
Slackware: “Roberto Val”, “Flavio R. Cavalcanti”
Gentoo: “Darko Luketic”
Void Linux: “cintrikz”:
Crux Linux: “pitillo”
LFS: “Michał Radwański”
Also “Michael Boyle” for EIX advice, and “Linux Lady05 Winter” for giving support, and “Pașca Alexandru” for BTRFS issue for my First openSUSE install.
Thank you so much for being helpful. You are all great sweet people.
This is just a summary, we have not finished yet. There are links for each docker topic on top of this page. Consider reading each topic.
Dream come true
Thank you for reading
- December 2017
- Docker - LFS Build
- Docker - Arch ALPM - Part Four
- Docker - Arch ALPM - Part Three
- Docker - Arch ALPM - Part Two
- Docker - Arch ALPM - Part One
- Docker - Debian APT - Part Four
- Docker - Debian APT - Part Three
- Docker - Debian APT - Part Two
- Docker - Debian APT - Part One
- Docker - Slackware Package - Part Three
- Docker - Slackware Package - Part Two
- Docker - Slackware Package - Part One
- Docker - Fedora DNF - Part Four
- Docker - Fedora DNF - Part Three
- Docker - Fedora DNF - Part Two
- Docker - Fedora DNF - Part One
- Docker - openSUSE Zypper - Part Four
- Docker - openSUSE Zypper - Part Three
- Docker - openSUSE Zypper - Part Two
- Docker - openSUSE Zypper - Part One
- Docker - Void XBPS - Part Two
- Docker - Void XBPS - Part One
- Docker - Gentoo Portage - Part Three
- Docker - Gentoo Portage - Part Two
- Docker - Gentoo Portage - Part One
- Docker - Crux Ports
- Distribution - Debian to Devuan Migration
- Distribution - Manjaro OpenRC to Artix Migration
- Distribution - Mageia 6 Upgrade
- File System - GRUB2 support for BTRFS
- Distribution - openSUSE Tumbleweed First Time Install
- Distribution - Fedora First Time Install
- Distribution - Manjaro OpenRC Issues
- July 2017
- June 2017
- May 2017
- April 2017