From: Diego Viola <diego.viola@gmail.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-kernel@vger.kernel.org, trivial@kernel.org, corbet@lwn.net
Subject: Re: README Cleanup Project
Date: Sat, 12 Dec 2015 09:51:32 -0200 [thread overview]
Message-ID: <CA+ToGPGTg9xnRVas-w2PR1P+=o7uv5d_OFyqFD3uuuDmj44UmQ@mail.gmail.com> (raw)
In-Reply-To: <CA+ToGPFH2Ugb8Bkibj_cg8PTPC4g8G0WEfwgEVLzhdHJa=UnBg@mail.gmail.com>
Why does the Linux kernel keep outdated cruft like this in tree?
If you need lilo you can just run /sbin/lilo yourself, there is no
need for this to be in the kernel, especially when the project is
being phased out already.
Should I send a patch removing all lilo entries from the project?
Diego
On Sat, Dec 12, 2015 at 4:24 AM, Diego Viola <diego.viola@gmail.com> wrote:
> On Sat, Dec 12, 2015 at 4:09 AM, Diego Viola <diego.viola@gmail.com> wrote:
>> On Sat, Dec 12, 2015 at 3:35 AM, Al Viro <viro@zeniv.linux.org.uk> wrote:
>>> On Sat, Dec 12, 2015 at 02:46:30AM -0200, Diego Viola wrote:
>>>> Hello everyone,
>>>>
>>>> I would like to do some cleanup on the README, for example, I see it
>>>> still mentions LILO in a few places, e.g.
>>>>
>>>> https://github.com/torvalds/linux/blob/master/README#L256-L258
>>>>
>>>> And:
>>>>
>>>> https://github.com/torvalds/linux/blob/master/README#L295-L317
>>>>
>>>> Is this still relevant today? Can I send a patch to remove it from the
>>>> README? Any objections?
>>>
>>> What for? LILO still works just fine here, TYVM.
>>>
>>
>> I know LILO still works fine, and I know the project is still alive.
>
> Wait, I'm actually not sure about my statement above, looks like the
> project is dead:
>
> "NOTE: I will finish development of LILO at December 2015 because of
> some limitations (e.g. with BTFS, GPT, RAID). If someone want to
> develop this nice software further, please let me know ..."
>
> http://lilo.alioth.debian.org/
>
>>
>>>> Could you guys also help me identify other parts in the README that
>>>> are not relevant anymore today?
>>>>
>>>> I understand some people still use LILO but most don't anymore, so I
>>>> would like to help keep the README updated to reflect on what the
>>>> current standards and needs are.
>>>
>>> _What_ current standards?
>>
>> Perhaps not "standards" but there are other bootloaders these days,
>> GRUB and systemd-boot being one of them.
>>
>> Shouldn't the README be generic or neutral about bootloaders?
>>
>> See this message from Jonathan Corbet where he gave his opinion on this:
>>
>> https://lkml.org/lkml/2015/12/10/602
>>
>> Thanks,
>>
>> Diego
next prev parent reply other threads:[~2015-12-12 11:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-12 4:46 Diego Viola
2015-12-12 5:35 ` Al Viro
2015-12-12 6:09 ` Diego Viola
2015-12-12 6:24 ` Diego Viola
2015-12-12 11:51 ` Diego Viola [this message]
2015-12-12 12:43 ` Richard Weinberger
2015-12-12 14:06 ` 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='CA+ToGPGTg9xnRVas-w2PR1P+=o7uv5d_OFyqFD3uuuDmj44UmQ@mail.gmail.com' \
--to=diego.viola@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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®