All of lore.kernel.org
 help / color / mirror / Atom feed
From: phcoder <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Interesting GSoC project ideas for 09
Date: Sun, 01 Mar 2009 18:15:43 +0100	[thread overview]
Message-ID: <49AAC2BF.7050307@gmail.com> (raw)
In-Reply-To: <1235881685.24700.7.camel@mj>

I personally see following features still missing from grub2 comparing 
to grub1:
-network
It's in the list
-lock
It's more a question of discussing design that actually coding
-simple partition manipulation
I started a design discussion about this subject but nobody seems to be 
interested. If I receive no further replies I suppose that my 
proposition with "parttool" in "Re: [PATCH] make partition active" is ok 
and implement it
-map hook
Vesa is working on low memory loading which is a prerequisite. If my 
boot patch gets incorporated with Vesa's code it should be fairly simple 
to do it
-setkey
I've seen that someone already started keymap support
Pavel Roskin wrote:
> On Sat, 2009-02-28 at 12:54 +0100, phcoder wrote:
>> Robert Millan wrote:
>>> Seems nice.  Would you be willing to write a summary for these?  Then we
>>> could add it to grub-soc.html.
>> Where is this file?
>> Here is elaborated list:
> 
> In my opinion, matching all features of GRUB 1 on i386-pc should be the
> highest priority.  It would allow distributions to switch to GRUB 2,
> bringing more users and more developers.  As it stands now, GRUB 2 is
> seen as something much more experimental and dangerous than GRUB 1.
> 
> We won't win many users by the mouse and bluetooth support if distros
> don't switch to the new GRUB.  And distros are reluctant to make any
> changes that would be seen as regressions.
> 
> If we cannot match some features, such as network support, we should
> offer alternative solutions and document them.
> 


-- 

Regards
Vladimir 'phcoder' Serbinenko



  reply	other threads:[~2009-03-01 17:15 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-25  9:21 Interesting GSoC project ideas for 09 "C. Bergström"
2009-02-25 11:59 ` phcoder
2009-02-27 21:08   ` Robert Millan
2009-02-28 11:54     ` phcoder
2009-03-01  4:28       ` Pavel Roskin
2009-03-01 17:15         ` phcoder [this message]
2009-03-04 21:02           ` Robert Millan
2009-03-04 20:59         ` Migrating to GRUB 2 in Debian (Re: Interesting GSoC project ideas for 09) Robert Millan
2009-03-13 11:50           ` Yoshinori K. Okuji
2009-03-13 12:23             ` phcoder
2009-03-14 21:10               ` Yoshinori K. Okuji
2009-03-15  5:52                 ` Bean
2009-03-22  7:01                   ` Yoshinori K. Okuji
2009-03-22 10:48                     ` phcoder
2009-03-22 13:11                       ` Yoshinori K. Okuji
2009-03-22 13:23                         ` phcoder
2009-03-22 14:02                           ` Yoshinori K. Okuji
2009-03-22 12:29                     ` Robert Millan
2009-03-22 12:50                       ` Yoshinori K. Okuji
2009-03-28 20:02                         ` Yoshinori K. Okuji
2009-03-02  7:52       ` Interesting GSoC project ideas for 09 liu Aleaxander
2009-03-01 14:55   ` liu Aleaxander
2009-03-01 15:30     ` phcoder

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=49AAC2BF.7050307@gmail.com \
    --to=phcoder@gmail.com \
    --cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.