Repository navigation
Releases
camareLOL 1.0.3
camareLOL 1.0.3 — Beta 4
Released: 28 October 2026
Status: beta / pre-release
Tag: v1.0.3
npm: @wenker-ai/camarelo@beta — the latest tag deliberately stays on 0.1.22
camareLOL is a safety-first TUI installer for Arch Linux. This beta fixes one
mislabelled output discovered during the 1.0.2 VM verification. Discovery,
planning, partitioning, pacstrap, bootloader, desktop, safety-gate, IPC and
config-schema behaviour are unchanged.
1. What went wrong in 1.0.2
A virtio disk was labelled kind: "SataHdd"
The 1.0.2 release notes carried first-hand output from an Arch-in-QEMU run,
and that output contained its own confession:
1. devices discovered: 1
- /dev/vda SATA HDD — 20 GiB | no partition table
/dev/vda is not a SATA drive. It is a paravirtualized virtio disk backing a
qcow2 file. The discovery JSON even said so — transport: "virtio" on the
same line — yet kind claimed SATA HDD.
The cause was an ordering bug in the kind classifier: the rotational flag
was consulted before the virtio name prefixes. Some hypervisors set
rotational:true on sparse images, so vda fell into the mechanical-SATA
bucket on its way down the decision ladder.
The misleading label was cosmetic: planning never read back the kind field
from the survey, and the VM run itself had PASSED. Cosmetic does not mean
harmless — an installer is judged by its output, and this output contradicted
itself inside one line.
2. What changed in 1.0.3
- The classifier checks the name prefixes (
vd/xvd) and thevirtio
transport before therotationalflag. A virtio disk isVirtual,
whatever the rotational bit says. - Regression tests added:
vdawithtran:"virtio"androta:trueplus
xvdaboth classify asVirtualDisk; a genuinesdawith
tran:"sata"+rota:truestill classifies asSATA HDD.
3. Verified
$ cargo test
test result: ok. 48 passed (tui)
test result: ok. 283 passed (core, includes the 2 new kind tests)
checksums
See SHA256SUMS in the release assets. Verify before running:
$ sha256sum -c SHA256SUMScamareLOL 1.0.2
camareLOL 1.0.2 — Beta 3
Released: 28 October 2026
Status: beta / pre-release
Tag: v1.0.2
npm: @wenker-ai/camarelo@beta — the latest tag deliberately stays on 0.1.22
camareLOL is a safety-first TUI installer for Arch Linux. This beta fixes the
last misleading output the 1.0.1 self-test could produce on a machine
camareLOL does not support, and adds first-hand evidence from a real
Arch-in-QEMU run. No planning, partitioning, pacstrap, bootloader, desktop,
safety-gate, IPC or config-schema behaviour changed.
1. What went wrong in 1.0.1
An unsupported host printed self-test: FAILED
Running --self-test on Ubuntu 24.04 (Google Cloud Shell) printed:
0. host detected: Ubuntu 24.04 LTS, unknown init system
supported: false
REFUSED: distribution "ubuntu" is not one camareLOL has been validated on.
...
selftest result: FAIL
That FAIL said the tool was broken. It was not: every machinery check on that
host passed — discovery found the devices, the safety gate stayed closed, the
configuration round trip was ok. What failed was the host gate, by design.
A test that reports design as a defect teaches the user to ignore it.
2. What changed in 1.0.2
--self-testnow reports three outcomes with distinct exit codes:PASS— exit 0: all checks passed.SKIP (host unsupported)— exit 2: the machine is not one camareLOL
supports. The machinery checks still ran above the host line, and they
passed. This says nothing bad about the tool.FAIL— exit 1: a machinery check failed wherever it runs. Report that.
- The FAIL branch wins over SKIP: a broken safety gate on a strange distro is
still a bug, not an environment question. - Exit codes are documented in the quick-start page (all three languages).
3. Proof from a real run (Arch 7.2.7 in QEMU/KVM, 20 GiB empty -qcow2)
v1.0.1 assets, downloaded inside the VM from the canonical organisation URL:
0. host detected: Arch Linux / systemd
supported: true
1. devices discovered: 1
- /dev/vda SATA HDD — 20 GiB | no partition table
2. UEFI -> 2 partitions (root: true, esp: true, table: GPT) ok
2. BIOS -> 2 partitions (root: true, esp: false, table: GPT) ok
4. safety gate refuses formatting by default: true
5. configuration round trip: ok (archlinux)
6. simulated install: completed (12 phases)
selftest result: PASS
The TUI opened on the same console and closed cleanly (Ctrl-C): Welcome
shows v1.0.1+3b0c356, firmware UEFI, host Arch Linux / systemd, network
OK and Disks: 1 detected. In a VM everything writes to a qcow2 file —
nothing outside it is touched.
Known cosmetic quirk from that session: the discovery JSON labels a virtio
disk kind: "SataHdd" even though transport says virtio. Timing for
1.0.3, no effect on planning.
checksums
See SHA256SUMS in the release assets. Verify before running:
$ sha256sum -c SHA256SUMScamareLOL 1.0.1
camareLOL 1.0.1 — Beta 2
Released: 26 October 2026
Status: beta / pre-release
Tag: v1.0.1
npm: @wenker-ai/camarelo@beta — the latest tag deliberately stays on 0.1.22
camareLOL is a safety-first TUI installer for Arch Linux. This is the second
beta. It fixes two defects found while testing the published 1.0.0 one-liner
on a normal installed machine. No planning, partitioning, pacstrap,
bootloader, desktop, safety-gate, IPC or config-schema behaviour changed.
1. What went wrong in 1.0.0
Virtual block devices were offered as disks
lsblk labels zram0, ram0, nbd0, md0 and loop0 as type disk.
camareLOL trusted that label and listed them on the Storage screen. On the
packaging host, /dev/zram0 appeared as a 4 GiB SATA SSD.
The immediate effect was noisy: --self-test picked zram as the empty disk,
tried to plan a root that needs at least 8 GiB, failed, and printed
self-test: FAILED on a host where nothing was wrong.
The dangerous effect was conditional: a zram device larger than the planner's
minimum would have passed size validation. The plan would then have targeted
volatile memory instead of a disk. Planning into RAM and calling it an install
is not a failure mode this project is willing to leave in place.
--self-test ran the simulated install on the wrong disk
After checking for an empty disk, the self-test used devices.first() for the
simulated install. On an installed machine that is the disk holding the running
system, not the empty target. The simulation came back incomplete and the
self-test reported FAIL.
The simulated install needs a disk it is allowed to format. If there is no
empty disk, the honest result is “skipped”, not “failed”.
2. What changed in 1.0.1
- Discovery ignores
zram*,ram*,nbd*,md*,dm-*,loop*andfd*.
Real disks, virtio disks (vd*,xvd*), NVMe, MMC and USB devices are
unchanged. --self-testruns the simulated install on the empty disk it already found,
and printsskipped (no empty disk)when there is none.- A regression test feeds
lsblkJSON containing zram, ram, nbd, md, loop and
a real disk; only the real disk is returned. - The Rust suite is 329 tests: 281 in
camarelol-core, 48 in the TUI crate.
The host safety check is unchanged: an unvalidated distribution is still
refused, and --self-test still fails on one. That is the intended result.
3. Evidence
-
cargo fmt --check,cargo clippy --workspace --all-targets -- -D warnings,
andcargo test --workspace: 329 passed (281 core + 48 TUI). -
Python tests, the Java catalog tests, and the three acceptance scenarios
(empty disk, Windows disk, partition without a filesystem) passed. -
On the packaging host,
--self-testnow reports:1. devices discovered: 2 - /dev/sda SATA SSD — 119 GiB | GPT | 2 partitions - /dev/nvme0n1 NVMe SSD — 477 GiB | GPT | 2 partitions 2. no empty disk to plan for (skipped) 6. simulated install: skipped (no empty disk) selftest result: PASS self-test: OK
Before the fix the same host discovered three devices (including zram0),
failed the zram plan, and exited 1. -
GitHub Actions on
mainis green, including the corrected Ubuntu smoke test
that asserts camareLOL refuses an unsupported host. -
VM acceptance was not rerun for 1.0.1.
VBoxManageis not installed on
the packaging host, soscripts/make-release.shwas run withSKIP_VM=1.
The change is in discovery and the self-test, not in any disk-writing phase;
the previous VM evidence still describes the write path. This is still a
skipped gate, and it is disclosed here rather than hidden.
4. Install 1.0.1 beta
The beta is opt-in. The default one-liner and npm install -g continue to
resolve the newest stable release (0.1.22).
From GitHub Releases (pre-release)
$ curl -fsSL https://raw.githubusercontent.com/tamkogay9876-code/camareLOL/main/scripts/camarelol.sh \
| CAMARELOL_VERSION=v1.0.1 bash$ curl -fsSL https://raw.githubusercontent.com/tamkogay9876-code/camareLOL/main/scripts/camarelol.sh \
| CAMARELOL_CHANNEL=beta bashBoth paths download the binary, check the ELF magic, verify it against the
release SHA256SUMS, require --version to agree with the tag, and then run
--self-test.
By hand:
$ curl -fLO https://github.com/tamkogay9876-code/camareLOL/releases/download/v1.0.1/camarelol
$ curl -fLO https://github.com/tamkogay9876-code/camareLOL/releases/download/v1.0.1/SHA256SUMS
$ sha256sum -c SHA256SUMS
$ chmod +x camarelol
$ ./camarelol --self-test
$ sudo ./camarelolVia npm (beta tag)
$ sudo pacman -S --needed nodejs npm curl
$ npm install -g @wenker-ai/camarelo@beta
$ camarelol --versionThe npm package bundles the 1.0.1 binary.
From source
$ git clone https://github.com/tamkogay9876-code/camareLOL
$ cd camareLOL
$ ./install.sh
$ ./build.sh test # Rust + Python + Java + acceptance scenarios5. Verify the download
$ sha256sum -c SHA256SUMS
camarelol: OK
camarelol-1.0.1.tar.gz: OK
camarelol-catalog.jar: OK
PKGBUILD: OK$ ./camarelol --version
camareLOL 1.0.1 (tag v1.0.1, commit …)A binary that says [built from a dirty working tree] is not a release, no
matter what version it prints.
6. Upgrading from 1.0.0
Replace the binary. The configuration schema is still version 1, so saved
profiles load unchanged. There is no automatic update path, by design:
$ curl -fsSL https://raw.githubusercontent.com/tamkogay9876-code/camareLOL/main/scripts/camarelol.sh \
| CAMARELOL_VERSION=v1.0.1 bashVia npm:
$ npm install -g @wenker-ai/camarelo@betaRolling back to the first beta:
$ curl -fsSL https://raw.githubusercontent.com/tamkogay9876-code/camareLOL/main/scripts/camarelol.sh \
| CAMARELOL_VERSION=v1.0.0 bash7. Known limitations
The limitations in the 1.0.0 release notes
still apply. In particular:
- Three Stage 2 items remain partial: model-keyed GPU driver suggestions,
VM observation of the NetworkManager configuration, and VM observation of
stale-firmware cleanup. - NTFS resize, dual-boot beside a real Windows installation, manual
partitioning, LUKS and Btrfs subvolume layouts are deliberately deferred. - The installer still runs only on Arch Linux with systemd. Other
distributions are refused at plan time.
8. Changelog
| Version | Highlights |
|---|---|
| 1.0.1 | Do not offer zram/ram/nbd/md/loop as install disks; --self-test skips the simulated install when there is no empty disk |
| 1.0.0 | First beta; roadmap audit; documentation and release-tooling overhaul |
| 0.1.22 | Real-machine dual-boot install and first boot; unpartitioned-gap row; dual-boot mode selects GRUB; scripts/dual-boot-auto.sh |
| 0.1.21 and earlier | See the 1.0.0 notes and the repository log |
9. Links
- Repository: https://github.com/tamkogay9876-code/camareLOL
- Releases: https://github.com/tamkogay9876-code/camareLOL/releases
- Issues: https://github.com/tamkogay9876-code/camareLOL/issues
- Discussions: https://github.com/tamkogay9876-code/camareLOL/discussions
- Documentation:
docs/en/index.md - Roadmap:
docs/en/roadmap.md
10. Warning
Installing an operating system and partitioning disks can destroy data.
camareLOL asks before every irreversible step, re-identifies the disk before
writing, and never claims success it did not verify. Still: back up anything
you care about, and run it from a live ISO rather than on the machine you are
trying to fix.
Licensed under GPL-3.0-or-later.
camareLOL 1.0.0
camareLOL 1.0.0 — Beta 1
Released: 26 October 2026
Status: first beta / pre-release
Tag: v1.0.0
npm: @wenker-ai/camarelo@beta — the latest tag deliberately stays on 0.1.22
camareLOL is a safety-first TUI installer for Arch Linux. It detects the
hardware, proposes a layout, shows the exact plan, and writes to a disk only
after the user types a confirmation phrase. It is not a shell wrapper: the
installer has its own pipeline — discovery → plan → review → confirm →
execute → verify — with a safety gate in front of every destructive step.
This is the first beta. It is the same installer code as 0.1.22, re-versioned
and re-documented after a full roadmap audit. No installer behaviour changed in
1.0.0; what changed is the release identity, the documentation, and the
tooling that publishes and verifies releases.
1. Why 1.0.0 is a beta
The roadmap is now complete in the only sense this project accepts: every item
is either shipped with evidence, explicitly marked partial, or
deliberately deferred with a written reason. A checkbox is not proof; a
VirtualBox run or a real-machine run is.
Three Stage 2 items are still partial, and two storage features are explicitly
deferred. They are listed in Known limitations below.
Calling this release beta is not modesty — it is the accurate label for a
1.0.0 whose remaining gaps are known and documented instead of hidden.
The version number is now 1.0.0 because the feature set is frozen enough to
deserve a stable number. It does not mean "safe on every disk". The warning
in the README still applies: install on an empty disk, from the Arch live ISO,
with a backup.
2. Roadmap at this release
| Stage | Status | What it means |
|---|---|---|
| 1 — MVP | Complete | Discovery, planning, safety gate, pacstrap/fstab/bootloader, config profiles, Python/Java layers |
| 2 — Desktop | Complete except three partial items | Seven desktop profiles, Wayland/X11 checks, four display managers, audio, Bluetooth, zram, swap. Partial: model-keyed GPU driver suggestions, VM observation of the NetworkManager config, VM observation of stale-firmware cleanup |
| 4 — Experience | Complete | Save/resume profiles, package search, AUR built as a normal user, diagnostics export, three languages, recovery guidance |
| 5 — Shipping | Complete | Tag-built release, dirty-tree refusal, version-in-binary check, VM gate, checksummed GitHub assets, npm package with checksum verification |
| 6 — Dual-boot | Complete, with the real-Windows leg deferred | Keep-everything planner, append-only sgdisk, GRUB on the reused ESP with os-prober, VM evidence, Windows menu entry, real-machine install and first boot |
The full item-by-item record, including the [~] markers and the deferred
section, is in docs/en/roadmap.md.
3. What is new in 1.0.0
Release identity
- The Cargo workspace,
Cargo.lock, npm package, PKGBUILD template and
dual-boot helper now agree on 1.0.0. - The binary is built from tag
v1.0.0and reports
camareLOL 1.0.0 (tag v1.0.0, commit …). - The GitHub release is published as a pre-release; npm is published under
thebetadist-tag.npm install -g @wenker-ai/camarelostill installs
0.1.22 until the beta is promoted.
Documentation
- New canonical English release notes: this file.
- The README now describes the beta status, the beta install paths, the safety
model and the known gaps without claiming the project is finished. - The English, Vietnamese and Chinese documentation landing pages were updated
for 1.0.0: stale "alpha" wording, the removeduupdate key, and the old
"layout UI comes in Stage 3" claim are gone. - The roadmap now points at 1.0.0 as the current release and keeps the partial
and deferred items visible. - The npm package page was rewritten for the beta and explains the
betatag,
the bundled binary, and how to verify it.
Release tooling
scripts/upload-release.shreads the release body from
docs/releases/<version>.mdinstead of hard-coding one release's notes, and
accepts--prerelease. Draft-then-upload-then-publish is unchanged, so a
broken upload never leaves a half-published release visible.npm/build.shacceptsNPM_TAG(for exampleNPM_TAG=beta) and passes it
tonpm publish; the package is still packed only after the downloaded
binary matches the releaseSHA256SUMSand reports the expected version.scripts/camarelol.shacceptsCAMARELOL_CHANNEL=betato resolve the newest
release including pre-releases;CAMARELOL_VERSIONstill pins an exact tag.scripts/dual-boot-auto.shpins the beta channel and refuses builds older
than 1.0.0.install.sh --binarynow verifies the downloaded binary against the release
SHA256SUMSand acceptsCAMARELOL_VERSIONto install an exact release.scripts/make-release.shfinds a JDK throughJAVA_HOME(the same logic as
build.sh) and documents theSKIP_VM=1decision in its output.
No installer behaviour changes
There are no changes to discovery, planning, partitioning, pacstrap, fstab,
bootloader, desktop profiles, the safety gate, the IPC protocol or the config
schema. A profile saved by 0.1.22 loads unchanged.
4. What the installer does
- Detects disks, partitions, filesystems, EFI partitions, Windows, recovery and
Microsoft-reserved partitions, and live-system mounts. - Plans GPT and MBR layouts: ESP, BIOS boot,
/,/home, swap, with ext4,
btrfs or xfs, validated against the firmware mode. - Detects Windows and refuses to touch it.
- Installs a minimal Arch system: pacstrap, fstab, bootloader (GRUB or
systemd-boot), locale, keymap, timezone, hostname, users, sudo policy,
services and initramfs. - Offers seven desktop profiles: KDE, GNOME, Xfce, Cinnamon, LXQt, Hyprland and
Sway; Wayland or X11 with compatibility checks; SDDM, GDM, LightDM or greetd. - Handles PipeWire, PulseAudio or neither; Bluetooth, zram and swap choices;
NetworkManager; and a conservative set of drivers and firmware. - Supports package search and selection, AUR packages built as a normal user
(never as root), and saved/resumed configuration profiles. - Exports a redacted diagnostics report with
--save-diagnostics <FILE>. - Speaks Vietnamese, English and Simplified Chinese (
--lang vi|en|zh). - Implements keep-everything dual-boot: a GPT+UEFI disk keeps every existing
partition asformat=false, reuses its ESP at/boot/efi, and appends the
new partitions inside the largest aligned free gap with
sgdisk --new=…. There is no zap and no partition-table rewrite. - On a dual-boot plan, installs GRUB on the reused ESP, enables os-prober and
writesGRUB_DISABLE_OS_PROBER=falsein the bootloader phase, before
grub-mkconfig. - Deletes only stale firmware boot entries whose loader file is missing from
our ESP, matched by GUID;FvFile/CdRom/Usbdevices and other
partitions are never touched. A brokenefibootmgrlisting skips the
cleanup instead of failing the install.
Safety model
- Locked by default.
--allow-destructiveopens the gate;--executeis
required to write; the Review screen still demands a typedERASEor
ERASE AND WIPE. --previewruns all twelve phases with every real command printed and
nothing executed. It ignores--allow-destructiveand--execute, and a red
banner stays on screen for the whole run.- The disk identity is re-checked immediately before every write.
- Secrets are redacted from logs; configuration profiles never contain
passwords. - The binary has no self-updater, no index URL and no code path that replaces
itself. Updates are a manual download or a package manager.
5. Evidence behind this release
- VM acceptance: the full harness last ran 7/7 on the 0.1.18 build; the
dual-boot harness ran seven times, with run 7 producing 17 green checks
(2026-10-22). It proves the fake Windows markers survived, the new root
landed on a new partition, GRUB stayed on the original ESP, os-prober was
installed, and the generatedgrub.cfgcontained a Windows Boot Manager
entry. - Real machine: on 24 October 2026,
scripts/dual-boot-auto.shran from a
live ISO on a real 119 GiB GPT disk. The 1 GiB ESP and the 69 GiB
EndeavourOS root stayedformat=false; a ~49 GiBcamarelol-rootext4
partition was placed in the gap left by the deleted first partition. The
first boot was confirmed: F11 →camareLOL→ GRUB fromEFI/CAMARELOL/on
the reused ESP → Arch kernel → initramfs → desktop login. - Still pending on that machine: booting EndeavourOS back through the
generatedendeavouros (EFI BootNext)GRUB entry, theefibootmgr -odefault
order swap, and the stale-entry/ISO cleanup listed in the roadmap. - Not rerun for 1.0.0: the VirtualBox acceptance gate. VirtualBox is not
installed on the packaging host, so the release was built with
SKIP_VM=1;scripts/make-release.shprints that skip instead of hiding
it. Since 1.0.0 contains no installer logic changes over 0.1.22, the
previous VM evidence still describes the same code path. This is a
packaging and documentation release, and it is labelled beta accordingly.
6. Install 1.0.0 beta
The beta is opt-in. The default one-liner and npm install -g continue to
resolve the newest stable release (0.1.22).
From GitHub Releases (pre-release)
Pin the tag, or ask for the beta channel:
$ curl -fsSL https://raw.githubusercontent.com/tamkogay9876-code/camareLOL/main/scripts/camarelol.sh \
| CAMARELOL_VERSION=v1.0.0 bash$ curl -fsSL https://raw.githubusercontent.com/tamkogay9876-code/camareLOL/main/scripts/camarelol.sh \
| CAMARELOL_CHANNEL=beta bashBoth paths download the binary, check the ELF magic, verify it against the
release SHA256SUMS, require...
camareLOL 0.1.22
camareLOL 0.1.22.
Highlights:
-
Real-machine dual-boot feedback, 23-24 Oct 2026:
- the Storage devices screen now shows the UNPARTITIONED GAP next to the
partition list — the gap-finding logic inside the dual-boot planner is
now a shared API (largest_aligned_gap / GapScan), so the planner and
the screen read the disk with the same eyes. A deleted first partition
leaves a gap at the very START of the disk and the scan finds it
exactly there (test reproduces that shape). - selecting the Dual-boot disk mode now switches the bootloader to GRUB
automatically, with a message explaining why — the planner's refusal
("systemd-boot cannot share a Windows ESP") arrives as prevention
instead of an error three screens later. The DiskMode screen also
labels what mode 3 keeps. - scripts/dual-boot-auto.sh — one-command real-machine install from a
live ISO: layout gates (GPT + small ESP + big ext4 root, nothing
mounted), typed ERASE-/EXECUTE confirmations, nothing ever touches
/dev/nvme*, the ESP, or sgdisk --zap-all.
- the Storage devices screen now shows the UNPARTITIONED GAP next to the
-
Everything 0.1.21 delivered (expanded partition list on the Storage
screen) and 0.1.20 (keep-everything dual-boot planner, stale EFI entry
cleanup, NetworkManager dhcp=internal) carries over.
Assets are checksummed in SHA256SUMS.
camareLOL 0.1.21
camareLOL 0.1.21.
Highlights:
- The Storage devices screen now expands the selected disk into its real
partition list — kernel name, size, filesystem, label, OS hints (ESP/
recovery/swap…) and the mountpoint. Before this fix partitions only
appeared on the layout screen, after a plan already existed; deciding
between whole-disk and dual-boot without seeing the table is how
mistakes happen. Rendering covered by 4 screen tests that fabricate
exactly the real-world shape (ESP + Linux root beside free space). - Everything 0.1.20 delivered (dual-boot keep-everything planner,
stale EFI boot entry cleanup, NetworkManager dhcp=internal, GPU model
parsing, paru-bin) carries over.
Assets are checksummed in SHA256SUMS.
camareLOL 0.1.20
camareLOL 0.1.20.
Highlights:
- Preparation for the real-machine dual-boot that 0.1.19 opened:
- the bootloader phase now reads
efibootmgr -vand deletes only those
Boot####entries whose/File(…)loader is missing from OUR ESP
(PARTUUID-matched) — theBoot0005-style hang where firmware points at
anEFI/…file a previous attempt left behind. Respectful by
construction:FvFile,CdRom,Usband other partitions are
never touched; a broken listing skips the cleanup with a note. /etc/NetworkManager/conf.d/00-camarelol.confpinsdhcp=internal
so a minimal pacstrap system never gets an interface that refuses to
take an address.
- the bootloader phase now reads
GpuInfo.model— the GPU product name parsed out oflspci -mm -nn
(only hex-id brackets stripped, product brackets kept).paru-binjoins the AUR catalog — prebuilt, no full Rust cook every
install.
Everything 0.1.19 delivered (dual-boot beside an existing OS, VM-proven)
carries over. Assets are checksummed in SHA256SUMS.
camareLOL 0.1.19
camareLOL 0.1.19.
Highlights:
- Dual-boot beside an existing OS (0.1.x kept the promise and tested it in a
VM first): keep-everything planner, append-only sgdisk write path, GRUB on
the reused ESP, os-prober enabled. scripts/vm-dualboot.sh proves it —
marker files intact on ESP/C:/recovery, root on the new partition 5, boot
chain verified from disk. - Fix: GRUB_DISABLE_OS_PROBER=false is now written by the bootloader phase
itself (grub.cfg is generated there), so the Windows entry exists. - Fix: swap partitions are enabled by fstab UUID, never mounted as a
filesystem; the ESP moves to /boot/efi when a separate /boot is selected;
preflight refuses a dirty /mnt instead of colliding with previous run. - VM acceptance: 7/7 whole-disk path; dual-boot path: 2 full runs green.
Assets are checksummed in SHA256SUMS.
camareLOL 0.1.18
camareLOL 0.1.18
Ba chốt chặn đã mở được lần cài thật đầu tiên trên đĩa ảo
Ba lỗi đều đúng một mẫu chung: vượt unit test, chỉ lộ trên đĩa thật — và lần
này được tìm ra bằng chính bài cài trên VirtualBox, không phải bằng đọc code.
| lỗi | hậu quả | sửa |
|---|---|---|
nhãn ESP CAMARELOL-EFI (13 ký tự) |
mkfs.fat từ chối — FAT chỉ nhận tối đa 11 — mọi bản cài UEFI chết ở phase format |
đổi thành CAMAROL-EFI, thêm test giới hạn nhãn theo loại filesystem |
| mount kế hoạch tảng theo thứ tự khai | ESP được mount trước root, root mount đè /mnt/boot → grub-install: "/boot doesn't look like an EFI partition" |
mount root trước, rồi mới ESP; có test soöne thứ tự |
/mnt còn mount từ lần chạy cũ |
chết giữa chừng với thông báo mơ hồ (contains a mounted filesystem) |
preflight giờ từ chối trước khi động vào đĩa, kèm lệnh giải thích umount -R /mnt |
Video minh chứng lần cài thành công: 12/12 phase completed, để lại puòt hệ Arch + Xfce boot được thật trên máy ảo.
VM acceptance 7/7 — profile console-only
PASS download 0.1.18, thẻ v0.1.18 khớp
PASS scan survey 1019 byte
PASS selftest PASS
PASS help không cờ cập nhật, và nói lý do
PASS install_profile /dev/sda
PASS install 12/12 pha hoàn tất
PASS zram 7 thứ đều có thật trên hệ đã cài
Ngoài harness tự động, đã cài tay một lần nữa bằng TUI thật trên
camarelol-test-uefi (UEFI, ổ 30 GiB, đĩa còn dữ liệu cũ từ lần chạy lỗi:
camareLOL xoá lại bình thường) — GRUB, LightDM + Xfce, NetworkManager, zram,
systemctl --failed = 0, efibootmgr chỉ vào \EFI\camareLOL\grubx64.efi.
⚠ Vẫn là ALPHA
Có lỗi. Từ live ISO, chỉ dùng ổ trống, sao lưu trước.
camareLOL 0.1.17
camareLOL 0.1.17
Sửa: binary vẫn bảo cài bằng pacman — lệnh không tồn tại
Màn Welcome và --help vẫn in:
sudo pacman -S camarelol # from a repository or the AUR
camareLOL không có gói pacman và không có gói AUR. 0.1.16 đã gỡ mọi
hướng dẫn đó khỏi README và cả ba bản tài liệu, nhưng quên sửa trong binary
— người đọc màn hình sẽ chạy một lệnh không bao giờ chạy được.
Cả ba chỗ nay trỏ về scripts/camarelol.sh, đúng lệnh thật sự cài lại.
Unit test cũ đang khẳng định màn hình phải chứa chữ "pacman" — tức là nó
giữ nguyên một hướng dẫn sai. Nay nó đòi camarelol.sh và cấm "pacman".
Cùng dòng 0.1.16, đã kiểm chứng
Bốn tên gói Arch sai — mọi bản cài Hyprland, Sway và systemd-boot đều hỏng:
| viết sai | đúng là | hậu quả |
|---|---|---|
greetd-tuigreeter |
greetd-tuigreet |
Hyprland và Sway dừng ở pacstrap |
p7zip |
7zip |
profile có nhóm archiving cũng fail |
systemd-boot |
không có gói này | bootctl nằm trong systemd |
VM acceptance 8/8 — profile hyprland + cups
PASS download / scan / selftest / help / install_profile
PASS install 12/12 pha hoàn tất
PASS zram 7 thứ đều có thật trên hệ đã cài
PASS desktop 7 mốc display + is-enabled xác nhận
Bằng chứng trên đĩa đích: en_greetd=enabled, en_cups=enabled,
greetd_conf=yes, greetd_session=yes, wayland=yes, xwayland=yes.
Màn Review đã nhận được cụm xác nhận
Kiểm bằng ảnh màn hình thật trên VirtualBox, không phải suông: gõ ERASE
hiện trong khung; Backspace xoá được; gõ erase (chữ thường) bị từ chối
với confirmation rejected: type exactly \ERASE``.
⚠ Vẫn là ALPHA
Đã qua nhiều bản phát hành nhưng còn lỗi. Ba lỗi tên gói ở trên đều
qua được mọi unit test và chỉ chết trong máy ảo. Chỉ dùng trên ổ trống,
từ live ISO, và sao lưu trước.
Nâng cấp
$ curl -fsSL https://raw.githubusercontent.com/tamkogay9876-code/camareLOL/main/scripts/camarelol.sh | bash
$ camarelol --version