From: adrian15 <adrian15@raulete.net>
To: grub-devel@gnu.org
Subject: Re: Parted/GRUB joint-venture
Date: Mon, 24 Apr 2006 10:03:46 +0200 [thread overview]
Message-ID: <444C8662.1080908@raulete.net> (raw)
In-Reply-To: <200604201254.k3KCslFP009167@dell01.dinaserver.com>
> Hello,
>
> I am the representative of GNU Parted and am also interested in the
> development of GRUB2 (I've been lurking on this list for some months).
> James from the GNU SoC team wrote me:
> <<EOQ
> There is a project suggestion relating to GRUB which relates to
> libparted. Please get in touch with the maintainers of GRUB (e.g.
> Yoshinori K. Okuji) to discuss that project and ensure it has the best
> chance of getting good guidance and is successful. The project
> doesn't have to end up in just GRUB or just Parted, it's just that I'm
> looking to make sure that the idea works well and flourishes.
> EOQ
I do not know if okuji has talked to you directly.
Have you seen this?
http://www.gnu.org/software/grub/grub-soc.html
Parted integration
Integrate GNU Parted's library (libparted) with GRUB so that we can make
use of the full power of the Parted's functionality at boot time.
Parted supports creation, deletion, resizing of partitions and
filesystems. These features are extremely useful when you get troubled
or have a complicated boot environment. Because libparted uses some
external libraries, you will have to think how to make things run on the
GRUB's environment, where you cannot use POSIX or Unix system calls.
This should be implemented as an optional dynamic module by using the
module loading feature in GRUB 2.
adrian15
next parent reply other threads:[~2006-04-24 8:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200604201254.k3KCslFP009167@dell01.dinaserver.com>
2006-04-24 8:03 ` adrian15 [this message]
2006-04-24 18:02 ` Parted/GRUB joint-venture Yoshinori K. Okuji
2006-04-20 8:45 leslie.polzer
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=444C8662.1080908@raulete.net \
--to=adrian15@raulete.net \
--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.