Groups | Search | Server Info | Login | Register
Groups > linux.debian.maint.boot > #77337
| From | Mehmet Akkus <mehmetakkus0804@gmail.com> |
|---|---|
| Newsgroups | linux.debian.maint.boot |
| Subject | Re: Proposal for a Modernized Debian Installer |
| Date | 2026-04-12 15:40 +0200 |
| Message-ID | <MJ3cB-eAMz-1@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
The current Debian installer has not kept pace with modern user expectations and increasingly acts as a barrier to adoption rather than a gateway to one of Linux's most stable distributions. The following is a concrete proposal for a redesigned installer that preserves Debian's philosophy while improving the experience significantly. 1. Installer Flow Redesign Language, system locale, and keyboard layout should be presented first as a group. Root and user credentials should follow immediately after, before any system decisions are made, so there is no ambiguity about which locale settings a password was entered under. 2. Installation Profiles The user should be asked what kind of system they are setting up: desktop, server, minimal, or custom. Desktop installations should offer profiles such as beginner, developer, gamer, and solo, each pre-configuring sensible defaults. A user who selects a profile can still override any decision it makes. This would be very helpful for instance when it comes to graphics drivers. 3. A Guided Assistant: Tux For non-solo profiles, a contextual ASCII Tux character should appear throughout the installation, offering brief and relevant explanations based on the user's choices. The guidance should be non-intrusive and skippable. A beginner seeing a swap partition question for the first time deserves a one-line explanation. An experienced user can ignore it entirely. 4. Sandboxed Package Layer A sandboxed package layer should allow packages and libraries to be installed in an isolated environment that can read from but never write to the base system. A developer can use a newer library without risking system stability, and if the sandboxed layer breaks it can be removed and reinstalled without touching the base system. This preserves Debian's stability guarantee while removing one of the primary reasons developers reach for other distributions instead. 5. A Lightweight CUI The installer should be a clean console interface, not the current low-resolution pseudographical one and not a full GUI. A minimal black terminal aesthetic with clear prompts and consistent navigation is more professional, accessible over SSH, and more aligned with what Debian actually is. 6. System Feature Toggle A privileged configuration file, modifiable only by root, should expose a clean interface for enabling or disabling major system components such as audio, Bluetooth, and network manager. It reduces the cognitive load of managing what is running on a given machine and makes it easy to produce a lighter system without deep knowledge of every service name and dependency. These proposals are not radical departures from Debian's identity. They are targeted solutions to well-known friction points, each designed to make Debian more accessible without sacrificing the control and stability that define it. Thanks a lot for reading this.
Back to linux.debian.maint.boot | Previous | Next — Next in thread | Find similar
Re: Proposal for a Modernized Debian Installer Mehmet Akkus <mehmetakkus0804@gmail.com> - 2026-04-12 15:40 +0200
Re: Proposal for a Modernized Debian Installer "Andrew M.A. Cater" <amacater@einval.com> - 2026-04-12 21:10 +0200
Re: Proposal for a Modernized Debian Installer Marc Haber <mh+debian-boot@zugschlus.de> - 2026-04-12 21:40 +0200
Re: Proposal for a Modernized Debian Installer Mehmet Akkus <mehmetakkus0804@gmail.com> - 2026-04-13 15:10 +0200
csiph-web