bk99.de entertain the web since 1997

bk99.de
HN · DistributionsCurated

Linux Mint and the Snap question

Summary

LWN examines why Linux Mint restricted the automatic installation of Snap, thereby raising the issue of control over package sources and updates. Linux Mint 20 contained the new block. The controversy focused particularly on Chromium.

Ideas

  • Ubuntu's Chromium package installed Snap indirectly as a transitional solution.
  • Linux Mint blocked this automatic installation by default.
  • Users could still deliberately enable Snap themselves.
  • Snap packages are distributed via centrally operated infrastructure.

Insights

  • Package formats embody governance decisions as well as technical properties.
  • A distribution protects its users' expectations through its own package rules.
  • Convenient transitional packages can bypass consent to new infrastructure.

Facts

  • snapd could still be installed manually.

Recommendations

  • Document package sources and automatic format changes transparently.
  • Test distribution upgrades for unexpected new background services.

References

Read the original article

Search the Web Archive

Hackaday · 2020

MicroOS relies on atomic Linux updates

Hackaday tests openSUSE MicroOS, whose transactional updates, Btrfs snapshots and separated applications are meant to keep the system in a robust state. MicroOS comes from the openSUSE project. The system is aimed particularly at container hosts and robust devices.

HN · 2026

Asahi Linux 7.2: progress on Apple Silicon

James Calligeros describes how Asahi Linux brings together power-saving features, new Apple generations and direct video output. M3 devices now support the webcam, microphones, USB 3.0 and Thunderbolt. M4 and M5 systems reach working NVMe and initial PCIe device detection.

HN · 2026

htop explained

Pēteris Ņikiforovs explains every htop display and links it with Linux processes, the scheduler, memory management and procfs. /proc/loadavg provides load values, process counts and the most recently assigned PID. PID 1 traditionally belongs to the init process started at boot.