From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: Some suggestions for improvements in GRUB
Date: Mon, 23 Apr 2012 07:41:36 +0200 [thread overview]
Message-ID: <4F94EB90.2090708@gmail.com> (raw)
In-Reply-To: <CAAHgbjqi-e2yKwu9UnarWi1rEnU4LXC7nkDgoghRjuWO8gB1oA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2624 bytes --]
On 22.04.2012 20:49, Karthik Krishna wrote:
> Hi there,
>
> I am an engineering student from India. I have been using Linux
> Distros for some time. With its varied uses i have come to like GRUB
> very much. But i wish to say that there are certain things that are
> not user friendly and needs a bit of change.
>
Such presentations are redundant. We treat the patches all the same
independently of who you are.
> First of all, if a drive is deleted or edited using any partition
> manager, GRUB does not know anything about it. And so in the ensuing
> part of booting, it shows a boot error. i have been seeing this as my
> friends keep coming to me to "FIX" their boot. The problem lies in
> GRUB's steep learning curve in the fixing department. when the grub
> error screen comes up, one has to come up with a plan to go to the
> internet and see the required grub error codes and relevant data to
> fix it. Thereby restoring grubs working. But the thing is you need an
> another PC/laptop with a working internet to see the codes or relevant
> data. i have been doing this for some time. i see that people who wish
> to use Linux have a hard time using it fully, especially when it comes
> to its boot-loader.
GRUB2 has no error codes at all.
>
> The onset of boot-loader problems really bogs down the motivation to
> move forward.
>
> So I wish to develop GRUB a bit so that it may be easy to use even in
> the case of error handling. I just dont know where to start. I know
> assembly, a bit of c and c++. I have heard of nasm and used gcc. So
> how do i develop it? I wanted to make a code that automatically
> detects partitions and checks it with a library of partitions to see
> if it has been changed or not. So that way the user is given the
> freedom of not doing anything rather letting GRUB doing the work for
> the user. i can develop the code using a simple algorithm. i want to
> make grub more smarter when it comes to handling errors and freeing
> the user.
>
In most places GRUB2 uses UUIDs which shouldn't change on partition
modifications. The only place another form is used is on prefix
specification and platform-specific install (embedding zone, EFI
partition, PreP and so on).
It's possible to add --no-use-partition-number to grub-install for the
first part, the patch is 3-5 lines, but it increases kernel size.
As for the second, there is no way around it as on most platforms it's
tied in to platform limitations.
You need to rerun grub-install after important partitioning changes.
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
prev parent reply other threads:[~2012-04-23 5:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-22 18:49 Some suggestions for improvements in GRUB Karthik Krishna
2012-04-23 5:23 ` Chris Murphy
2012-04-23 5:39 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-04-23 5:41 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
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=4F94EB90.2090708@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.