From a2d4908eaa11b1c90190976e489144650291d915 Mon Sep 17 00:00:00 2001 From: Denis Benato Date: Sat, 24 Aug 2024 17:27:26 +0200 Subject: [PATCH] Remove frzr kernel reference from the readme --- README.md | 6 ------ 1 file changed, 6 deletions(-) diff --git a/README.md b/README.md index e17e5a3..7a1571c 100644 --- a/README.md +++ b/README.md @@ -46,12 +46,6 @@ __Q__ Is it easy to create a proof-of-concept distro that is compatible with frz __A__ Absolutely: frzr wants to be hackable and easy to work with in every aspect: just create a btrfs subvolume and run your preferred command to write a rootfs (debootstrap, pacstrap or whatever). Then create a snapshot of it with btrfs send and that file can be deployed on real hardware! -__Q__ Can a distro be shipped with its own kernel? - -__A__ Yes and this is the preferred method. The user can boot a deployment only if such deployment comes with its own kernel or the user has installed one -already via the dedicated *frzr kernel* tool! - - __Q__ Are there rules to follow? __A__ There are conventions: for example a distro should __NOT__ assume it's the only distro installed, and *SHOULD NOT* cause harm to other deployments for example by writing to the efi partition.