mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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: remove LILO
Date: Sun, 27 Dec 2015 04:09:18 -0700	[thread overview]
Message-ID: <20151227040918.1f1d3b5b@lwn.net> (raw)
In-Reply-To: <1450587436-14034-1-git-send-email-diego.viola@gmail.com>

On Sun, 20 Dec 2015 02:57:16 -0200
Diego Viola <diego.viola@gmail.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

  reply	other threads:[~2015-12-27 11:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-20  4:57 Diego Viola
2015-12-27 11:09 ` Jonathan Corbet [this message]
2015-12-27 19:26   ` Diego Viola
2016-01-14 23:47     ` Diego Viola

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151227040918.1f1d3b5b@lwn.net \
    --to=corbet@lwn.net \
    --cc=diego.viola@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trivial@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®