From: "Steve Burtchin" <sburtchin@woh.rr.com>
To: <grub-devel@gnu.org>
Subject: Re: RE: Re: Getting Started
Date: Tue, 10 Apr 2012 06:56:11 -0400 [thread overview]
Message-ID: <002f01cd1708$8ab027f0$6400a8c0@Compaq1> (raw)
[-- Attachment #1: Type: text/plain, Size: 1595 bytes --]
On Sun, 8 Apr 2012 03:50:18 -0400 Steve Burtchin worte:
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>On Sat, 07 Apr 2012 13:17:15 +0200 Vladimir '?-coder/phcoder' Serbinenko wrote:
>------------------------------------------------------------------------------------
>On 07.04.2012 11:54, Steve Burtchin wrote:
>> GRUB Developers,
>>
>> Please help me get started developing GRUB2. I would like to add some
>> additional functionality to the 'parttool' command (functionally
>> similar to the code changes I proposed for GRUB-Legacy).
>Could you give more details?
>------------------------------------------------------------------------------------
>
>I had hoped I could answer the details question with a URL link, but I cannot find that
>bug report now.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
I found the URL to the bug report. It is http://savannah.gnu.org/bugs/?19410. In summary (and more specifically), I wish to add the following features to the GRUB2 'parttool' command:
1) Create or delete a primary partition. This functionality was provided by the 'partnew' command in GRUB Legacy. See also http://savannah.gnu.org/bugs/?19389.
2) Edit extended partition tables (EPBRs). This functionality was added to GRUB Legacy with the 'eptedit' command as described in bug report #19410.
NOTE: Not mentioned in the original bug report: with the ability to edit EPBRs, the potential number of logical partitions is limited only by the disk geometry for any SATA, PATA or SCSI disk.
Regards,
Steve Burtchin
[-- Attachment #2: Type: text/html, Size: 3012 bytes --]
next reply other threads:[~2012-04-10 10:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 10:56 Steve Burtchin [this message]
2012-04-10 12:26 ` Getting Started Vladimir 'φ-coder/phcoder' Serbinenko
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='002f01cd1708$8ab027f0$6400a8c0@Compaq1' \
--to=sburtchin@woh.rr.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.