linux-kernel - Re: [PATCH] README: cosmetic fixes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20151210113423.168f8b4d@lwn.net>
Date:	Thu, 10 Dec 2015 11:34:23 -0700
From:	Jonathan Corbet <corbet@....net>
To:	Diego Viola <diego.viola@...il.com>
Cc:	linux-kernel@...r.kernel.org, trivial@...nel.org
Subject: Re: [PATCH] README: cosmetic fixes

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/