Installer: make the partitioning page simple for end users

Aperta
  • Qualcosa non va?
#101 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
58/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
linux, shell, yaml
Ambito
tooling

Direzione di ricerca

Read the existing Calamares module configs under config/includes.chroot/etc/calamares/modules/ (bootloader, finished, removeuser, shellprocess_simpleos-cleanup) and /etc/default/zramswap, then compare against the Calamares 3.2 partition.conf key documentation to see which of the six points (swap, filesystem, preselection, labels, warning texts) are doable via config and branding. Start by adding a partition.conf with userSwapChoices: [none] and defaultFileSystemType: ext4 and test it in a live ISO install. Done: the partitioning page shows fewer, preselected, clearly labelled choices and the remaining points are documented as needing upstream patches or branding changes.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

core debian-13 idea
Your idea

The partitioning page of the installer is the one place where Simple OS still looks like a tool for experts. The repo has no partition.conf of its own (config/includes.chroot/etc/calamares/modules/ only has bootloader, finished, removeuser, shellprocess_simpleos-cleanup), so Calamares runs with the defaults of calamares-settings-debian. That means:

  • four choices (Install alongside, Replace a partition, Erase disk, Manual partitioning), none preselected
  • a swap dropdown ("No swap", "Swap (no hibernate)", "Swap (with hibernate)", "Swap to file") – Simple OS already uses zram (/etc/default/zramswap), a normal user can't decide this
  • a file system dropdown (ext4, btrfs, xfs, …)
  • disks shown as /dev/nvme0n1 / /dev/sda with a size; with two or more disks it is hard to tell which one holds Windows or the other system
  • partition bars without names, so "which one gets shrunk?" isn't obvious

Proposal – a Simple OS partition.conf (Calamares 3.2 keys) plus a few texts:

  1. Fewer choices. No swap choice (userSwapChoices: [ none ], initialSwapChoice: none, zram is enough), one file system (defaultFileSystemType: ext4, availableFileSystemTypes: [ ext4 ]).
  2. A sensible preselection. initialPartitioningChoice: alongside when another system was found, otherwise erase – so most users only press Next.
  3. Readable disks and partitions. alwaysShowPartitionLabels: true, drawNestedPartitions: true; ideally the disk list shows model name and what is on it ("Samsung SSD 990 · Windows, Fedora").
  4. Hide or explain the risky options. Replace a partition and Manual partitioning are what destroys other systems by mistake. Either move them behind an "Advanced" hint, or add a one-line explanation under each choice in the Simple OS branding.
  5. A clear last warning. Before installing, name the disk and the systems on it in plain words ("Windows on Samsung SSD 990 will be kept, 120 GB of it are used for Simple OS" / "Everything on WD Blue 1 TB will be erased").
  6. Encryption stays a single checkbox with one sentence of explanation (password is needed at every start).

To check per point: what Calamares 3.2.61 in Bookworm can do through partition.conf and branding alone, and what would need a patch – that decides how far this goes for 1.0.x.

Why would it help?

The README promises "you never need a terminal" and a calm desktop, but the installer is the first thing a new user sees, and the partitioning page is where they can lose data. Multi-disk PCs with Windows (gaming PCs, laptops with a second SSD) are exactly the computers Simple OS is aimed at with Ultimate Gaming. Issues #62/#64 (interrupted resize) and #73 (dual boot clock) show that this page and dual boot are where things go wrong.

Seen on: Acer Predator PO3-655, two disks (sda for Simple OS, nvme0n1 with Windows, Fedora and their EFI partition).

Lingua principale
Shell
Stelle
2
Fork
1
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di FreakySneaky787/Simple-OS

Tutte le issue di FreakySneaky787/Simple-OS

Issue simili

Altre issue su Shell/Bash

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.