Remove LILO from the README in order to keep the booting section
agnostic. LILO development has also officially stopped.
Signed-off-by: Diego Viola <[email protected]>
---
README | 36 ++++++++++--------------------------
1 file changed, 10 insertions(+), 26 deletions(-)
diff --git a/README b/README
index f4756ee..460c555 100644
--- a/README
+++ b/README
@@ -253,9 +253,9 @@ 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 your bootloader is configured to suit the kernel makefiles,
+ 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.
@@ -292,29 +292,13 @@ 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.
+ 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.
+
+ You may wish to edit your bootloader config to add an entry for your old
+ kernel image (say, /vmlinux.old) in case the new one does not work. Refer to
+ your bootloader documentation for specific options.
- Reboot with the new kernel and enjoy.
--
2.6.4
On Sun, 20 Dec 2015 02:57:16 -0200
Diego Viola <[email protected]> wrote:
> Remove LILO from the README in order to keep the booting section
> agnostic. LILO development has also officially stopped.
I know I mentioned LILO before, but LILO is really a symptom of the problem
here and not the problem itself. The real problem is that this document
doesn't really reflect how things are done on most systems; simply excising
mentions of LILO doesn't really fix that.
Or, for example:
> + 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.
Do you have any of those files on your system? I think that kernels in the
root are quite scarce anymore, and most of them don't have such simple
names. I would love to see all this fixed, but making it look updated
without doing the job properly doesn't really help our users much, I think.
Thanks,
jon
Hi Jonathan,
On Sun, Dec 27, 2015 at 9:09 AM, Jonathan Corbet <[email protected]> wrote:
> On Sun, 20 Dec 2015 02:57:16 -0200
> Diego Viola <[email protected]> wrote:
>
>> Remove LILO from the README in order to keep the booting section
>> agnostic. LILO development has also officially stopped.
>
> I know I mentioned LILO before, but LILO is really a symptom of the problem
> here and not the problem itself. The real problem is that this document
> doesn't really reflect how things are done on most systems; simply excising
> mentions of LILO doesn't really fix that.
>
I completely agree.
> Or, for example:
>
>> + 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.
>
> Do you have any of those files on your system? I think that kernels in the
> root are quite scarce anymore, and most of them don't have such simple
> names. I would love to see all this fixed, but making it look updated
> without doing the job properly doesn't really help our users much, I think.
>
I don't have those files on my system anymore, I have
/boot/vmlinuz-linux and /boot/initramfs-linux.img but then again I'm
on Arch Linux.
I didn't want to document how every possible distro handles kernel
installs because that would be insane, there are too many distros and
the document would be too big.
So I want to keep that section as generic as possible, but still
useful enough for users.
How about if we replace that line with something like this:
"All modern bootloaders are prepared to understand modern filesystems,
so there is no longer any need for special names, symlinks, mapfiles,
or explicit regeneration of block offsets. You can call your new
kernel whatever you want & put it wherever your chosen bootloader can
find it"
Do you have any better ideas? I'm happy to send another patch, but I
also need your help as English isn't my native language.
> Thanks,
>
> jon
Thanks,
Diego