From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Absence notice
Date: Fri, 03 Jul 2009 13:22:29 -0400 [thread overview]
Message-ID: <1246641749.29642.21.camel@mj> (raw)
In-Reply-To: <d7ead6de0907021629x770402f1pf55472581bc42049@mail.gmail.com>
On Fri, 2009-07-03 at 01:29 +0200, Vladimir 'phcoder' Serbinenko wrote:
> > It doesn't apply in loader/i386/pc/chainloader.c at all.
> Ok, I'll rediff.
Take your time.
Actually, the chainloader patch refers to "disk->parition" (misspelled
"partition"), so i doubt that it was even compile tested.
> > I think some parts could be split and applied separately.
> I'll look but afair it's not possible without breaking something
We'll see when we have a working patch.
> > I don't think
> > there are any objections against supporting nested partitions.
> Yes but I thought someone may have comments like "let's shave ths part
> from the kernel". The patch doesn't increase the core.img because
> increase of kernel size is compensated by pc.mod/bsdlabel.mod split.
> It the cases when bsdlabel.mod is used usually no modules like raid or
> lvm are used
Such objections may be raised once there is a patch that compiles.
Distributors must consider worst case scenarios.
> > But I
> > think it would be better to support letters for BSD partitions if it's
> > not too hard.
> It's done. THe patch treats 'a' and 1 completely alike
Good!
> >> It changes sufficiently a
> >> lot to need a peer review and I need for clear network naming support
> >> (I plan to use a syntax like (ftp,192.168.1.1,21,user,pass)/grub.cfg )
> >
> > I think the networking is better split from GRUB as a separate project
> > under GPLv2. It would be a huge effort to reimplement networking under
> > GPLv3.
> You wrong on this point because of http://www.sics.se/~adam/lwip/.
> It's a complete TCP/IP stack with loads of features suited for preboot
> environment and under 3-clause BSD license. I'll use it as a base. We
> can import hw drivers from gPXE (most are GPLv3+-compatible) and
> FreeBSD then
OK, good to know.
> > And I don't see it as a priority. The priority should be
> > supplanting GRUB1, yaboot and other bootloaders currently in use.
> >
> It's my priority. Solaris folks are willing to move to grub2 but are
> uncomfortable to lose netboot. (nested partitions and zfs were for
> them too) Additionaly I have a laptop without CD-ROM and want to push
> distributors to have completely network-based installation. For this a
> FTP or HTTP supportin grub would be very nice
I see.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2009-07-03 17:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-02 21:02 Absence notice Vladimir 'phcoder' Serbinenko
2009-07-02 22:08 ` Pavel Roskin
2009-07-02 23:29 ` Vladimir 'phcoder' Serbinenko
2009-07-03 17:22 ` Pavel Roskin [this message]
2009-07-03 17:35 ` Vladimir 'phcoder' Serbinenko
2009-07-04 4:40 ` Pavel Roskin
2009-07-04 20:27 ` Robert Millan
-- strict thread matches above, loose matches on Subject: below --
2009-05-02 18:53 absence notice Vesa Jääskeläinen
2009-05-02 20:01 ` Vladimir 'phcoder' Serbinenko
2009-05-02 21:42 ` Vesa Jääskeläinen
2009-05-03 4:38 ` Colin D Bennett
2009-05-03 4:44 ` Bean
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=1246641749.29642.21.camel@mj \
--to=proski@gnu.org \
--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.