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: <CA+ToGPFCXrgeuH=hhWnKv7+TumaDY8d_FyiG7s5ieimkanW7GA@mail.gmail.com>
Date:	Fri, 11 Dec 2015 01:06:55 -0200
From:	Diego Viola <diego.viola@...il.com>
To:	Jonathan Corbet <corbet@....net>
Cc:	linux-kernel@...r.kernel.org, trivial@...nel.org
Subject: Re: [PATCH] README: cosmetic fixes

Hi Jonathan,

Thanks for applying my patch. I actually have to admit that before
sending my patch I actually thought about the same thing regarding
LILO being in the README.

I asked on IRC and a few places about this because I don't feel like
removing anything before asking the community first. LILO still seems
to be alive as a project but not many people use it anymore, as you
have mentioned.

I agree the README feels outdated in many ways, I would be happy to do
some clean up, but I also want some input from the community on what
should stay and what should go. Should I send a new email to discuss
this?

Also, see this:

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/x86/boot/install.sh

This script calls /sbin/lilo if it's available during the make
install, so I don't think we can just remove LILO from the README if
it's still being used for the make install?

If we end up removing LILO from the README, should we remove it from
the Makefile as well?

This Makefile hasn't been updated in a few years I think.

Thanks,

Diego

On Thu, Dec 10, 2015 at 4:34 PM, Jonathan Corbet <corbet@....net> wrote:
> 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/