[<prev] [next>] [day] [month] [year] [list]
Message-Id: <1453178881-11452-1-git-send-email-diego.viola@gmail.com>
Date: Tue, 19 Jan 2016 02:48:01 -0200
From: Diego Viola <diego.viola@...il.com>
To: corbet@....net
Cc: linux-kernel@...r.kernel.org, trivial@...nel.org,
valdis.kletnieks@...edu, Diego Viola <diego.viola@...il.com>
Subject: [PATCH] README: Update bootloader section and some stylistic fixes
Signed-off-by: Diego Viola <diego.viola@...il.com>
---
README | 46 ++++++++++++++--------------------------------
1 file changed, 14 insertions(+), 32 deletions(-)
diff --git a/README b/README
index f4756ee..ca821e4 100644
--- a/README
+++ b/README
@@ -59,7 +59,7 @@ DOCUMENTATION:
INSTALLING the kernel source:
- If you install the full sources, put the kernel tarball in a
- directory where you have permissions (eg. your home directory) and
+ directory where you have permissions (e.g. your home directory) and
unpack it:
xz -cd linux-4.X.tar.xz | tar xvf -
@@ -125,7 +125,7 @@ BUILD directory for the kernel:
When compiling the kernel, all output files will per default be
stored together with the kernel source code.
- Using the option "make O=output/dir" allow you to specify an alternate
+ Using the option "make O=output/dir" allows you to specify an alternate
place for the output files (including .config).
Example:
@@ -159,9 +159,9 @@ CONFIGURING the kernel:
"make nconfig" Enhanced text based color menus.
- "make xconfig" X windows (Qt) based configuration tool.
+ "make xconfig" Qt based configuration tool.
- "make gconfig" X windows (GTK+) based configuration tool.
+ "make gconfig" GTK+ based configuration tool.
"make oldconfig" Default all questions based on the contents of
your existing ./.config file and asking about
@@ -253,9 +253,10 @@ COMPILING the kernel:
Please note that you can still run a.out user programs with this kernel.
- - Do a "make" to create a compressed kernel image. It is also
- possible to do "make install" if you have lilo installed to suit the
- kernel makefiles, but you may want to check your particular lilo setup first.
+ - Do a "make" to create a compressed kernel image. It is also possible to do
+ "make install" if you have a "installkernel" script in your path that will do
+ the needed things on your system, but you may want to check your particular
+ setup first.
To do the actual install, you have to be root, but none of the normal
build should require that. Don't take the name of root in vain.
@@ -268,8 +269,8 @@ COMPILING the kernel:
Normally, the kernel build system runs in a fairly quiet mode (but not
totally silent). However, sometimes you or other kernel developers need
to see compile, link, or other commands exactly as they are executed.
- For this, use "verbose" build mode. This is done by inserting
- "V=1" in the "make" command. E.g.:
+ For this, use "verbose" build mode. This is done by passing
+ "V=1" to the "make" command, e.g.
make V=1 all
@@ -292,29 +293,10 @@ COMPILING the kernel:
image (e.g. .../linux/arch/i386/boot/bzImage after compilation)
to the place where your regular bootable kernel is found.
- - Booting a kernel directly from a floppy without the assistance of a
- bootloader such as LILO, is no longer supported.
-
- If you boot Linux from the hard drive, chances are you use LILO, which
- uses the kernel image as specified in the file /etc/lilo.conf. The
- kernel image file is usually /vmlinuz, /boot/vmlinuz, /bzImage or
- /boot/bzImage. To use the new kernel, save a copy of the old image
- and copy the new image over the old one. Then, you MUST RERUN LILO
- to update the loading map!! If you don't, you won't be able to boot
- the new kernel image.
-
- Reinstalling LILO is usually a matter of running /sbin/lilo.
- You may wish to edit /etc/lilo.conf to specify an entry for your
- old kernel image (say, /vmlinux.old) in case the new one does not
- work. See the LILO docs for more information.
-
- After reinstalling LILO, you should be all set. Shutdown the system,
- reboot, and enjoy!
-
- If you ever need to change the default root device, video mode,
- ramdisk size, etc. in the kernel image, use the 'rdev' program (or
- alternatively the LILO boot options when appropriate). No need to
- recompile the kernel to change these parameters.
+ With the expansion of the Linux ecosphere into embedded devices, the variety
+ of boot loaders has exploded. Please consult the documentation for your
+ device's boot loader for details on how to make it load and start a Linux
+ kernel.
- Reboot with the new kernel and enjoy.
--
2.7.0
Powered by blists - more mailing lists