Difference between pages "FLOP:Boot-Update Redesign" and "User:RomikB"

From Funtoo
(Difference between pages)
Jump to: navigation, search
 
(Created page with "User")
 
Line 1: Line 1:
{{FLOP
+
User
|Created on=2013/12/03
+
|Summary=This page describes a proposed rewrite of boot-update.
+
|Author=Daniel Robbins
+
|Maintainer=Daniel Robbins
+
}}
+
== Introduction ==
+
 
+
The goals in rewriting boot-update are as follows:
+
 
+
# Refactor code
+
# Add UEFI support
+
# Simplify Kernel Layout
+
 
+
== Refactor Code ==
+
 
+
Boot-update could use some code simplification. This will be accomplished by using a simpler design using templates for text generation, and also simplifying the kernel layout (described below.)
+
 
+
== UEFI Support ==
+
 
+
Boot-update currently doesn't support UEFI booting directly, and must be manually configured via the [[UEFI Install Guide]]. Part of this proposal involves adding UEFI support to boot-update.
+
 
+
== Simplify Kernel Layout ==
+
 
+
Currently, all kernels and initramfs images are installed into <tt>/boot</tt> directly and typically have the names <tt>kernel-SUFFIX</tt> or <tt>bzImage-SUFFIX</tt> and <tt>initramfs-SUFFIX</tt>. Boot-update needs to find the kernel and initramfs images and associate them with each other, and then parse the filename for version information.
+
 
+
This is not an optimal way to organize kernels. A much cleaner approach would be to have a <tt>/boot/kernels/VERSION/</tt> directory that contains files <tt>initramfs.gz</tt>, <tt>bzImage</tt>, <tt>System.map</tt>, etc. without any suffix. boot-update would then scan <tt>/boot/kernels</tt> and make all directory names available as kernels that could be booted. This simplifies kernel management as everything related to a particular kernel is organized in its own sub-directory.
+
 
+
In addition, special text files could exist in the <tt>/boot/kernels/VERSION/</tt> directory, such as <tt>label</tt>, which could contain a regular text name for the kernel that appears in the menu. A <tt>/boot/kernels/VERSION/grub.cfg</tt> could allow users to manually specify a <tt>grub.cfg</tt> section that is used to boot this kernel, which boot-update would use if found. touching <tt>/boot/kernels/VERSION/default</tt> would allow a user to set the default kernel for booting. These types of changes would reduce the complexity contained in the <tt>/etc/boot.conf</tt> file, as more configuration data would be stored on the filesystem itself.
+
 
+
[[Category:FLOP]]
+
{{FLOPFooter}}
+

Revision as of 12:28, 15 December 2013

User