Date: Thu, 10 Dec 2015 11:34:23 -0700
From: Jonathan Corbet <corbet@lwn.net>
To: Diego Viola <diego.viola@gmail.com>
Cc: linux-kernel@vger.kernel.org, trivial@kernel.org
Subject: Re: [PATCH] README: cosmetic fixes
Message-ID: <20151210113423.168f8b4d@lwn.net>
In-Reply-To: <1449345010-12512-1-git-send-email-diego.viola@gmail.com>
References: <1449345010-12512-1-git-send-email-diego.viola@gmail.com>
Organization: LWN.net
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 979
Lines: 23

I've applied this to the docs tree.  I'd sure rather see an effort to
update this file instead of tweaking it, though.  For example:

> @@ -300,7 +300,7 @@ COMPILING the kernel:
>     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
> +   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. 

I somehow suspect that very few of us actually MUST RERUN LILO in 2015...

Thanks,

jon
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/