All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Elliott <pelliott@io.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Does grub2 solve this problem I am having with grub1? RE: usbsticks.
Date: Fri, 1 Feb 2008 15:45:40 -0600	[thread overview]
Message-ID: <20080201214540.GA11061@io.com> (raw)
In-Reply-To: <1201896891.3789.14.camel@dv>

[-- Attachment #1: Type: text/plain, Size: 1746 bytes --]

On Fri, Feb 01, 2008 at 03:14:51PM -0500, Pavel Roskin wrote:
> On Fri, 2008-02-01 at 12:44 -0600, Paul Elliott wrote:
> > > One possible approach would be to use LVM (Logical Volume Manager) -
> > > it's supported by grub2.  You could install grub on a small boot
> > > partition and allocate the rest to as an LVM partition, that would be
> > > split into volumes.  Then you could refer to the volumes by name.
> > > 
> > 
> > This seems a long way to drag the cat around the barn. Or this
> > would be like kicking dead whales down the beach. One should
> > not have to invoke the complexity of LVN just so one can specify
> > partitions.
> 
> OK, let's fix GRUB.
> 
> As for the expansion issue, I think I see how to fix it.
> grub_script_arg_add() should append expanded variables to the last
> argument, rather than allocate a new argument, unless the new argument
> is separated by spaces from the previous one.
> 
> GRUB_SCRIPT_ARG_TYPE_STR and GRUB_SCRIPT_ARG_TYPE_VAR are "write only".
> I think we should discard grub_script_arg_type_t or use it to keep track
> of spaces in the input.
> 
> As for the "boot_device", it could be set in the same place as "root",
> namely in grub_set_root_dev() in kern/main.c.
> 

Ok, you are well into grub2 internals, and beond the areas I am
familiar with.

I am glad the problem is being addressed and glad I could be
helpfull in pointing out the problem.

When grub2 is finished, I will look in the manual and see what
syntax I need to use to solve problems like this.




-- 
Paul Elliott                       1(512)837-1096
pelliott@io.com                    PMB 181, 11900 Metric Blvd Suite J
http://www.io.com/~pelliott/pme/   Austin TX 78758-3117

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-02-01 21:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-31 16:08 Does grub2 solve this problem I am having with grub1? RE: usbsticks Paul Elliott
2008-01-31 16:58 ` Pavel Roskin
2008-02-01  4:34   ` Paul Elliott
2008-02-01  4:50     ` Pavel Roskin
2008-02-01 12:59       ` Paul Elliott
2008-02-01 17:25         ` Pavel Roskin
2008-02-01 18:44           ` Paul Elliott
2008-02-01 20:14             ` Pavel Roskin
2008-02-01 21:45               ` Paul Elliott [this message]
2008-02-01 21:50                 ` Robert Millan
2008-02-02 12:11             ` Yoshinori K. Okuji
2008-02-02 14:34               ` Paul Elliott
2008-02-03  5:58                 ` Pavel Roskin
2008-02-04  3:46                   ` Pavel Roskin
2008-02-04 13:24               ` Paul Elliott

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=20080201214540.GA11061@io.com \
    --to=pelliott@io.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.