| 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
| ||
|
Message-ID: <20151227040918.1f1d3b5b@lwn.net> Date: Sun, 27 Dec 2015 04:09:18 -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: remove LILO On Sun, 20 Dec 2015 02:57:16 -0200 Diego Viola <diego.viola@...il.com> 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 -- 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/
Powered by blists - more mailing lists