All of lore.kernel.org
 help / color / mirror / Atom feed
From: phcoder <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] make partition active
Date: Wed, 11 Feb 2009 19:28:51 +0100	[thread overview]
Message-ID: <499318E3.5040801@gmail.com> (raw)
In-Reply-To: <1234369601.25774.5.camel@mj>

Pavel Roskin wrote:
> On Wed, 2009-02-11 at 14:43 +0100, phcoder wrote:
>> Here's the patch to add a replacement for old "makeactive" command
>> New syntax is
>> activate PARTITION
>> E.g.
>> activate hd0,1
> 
> Is it necessary to change the name?  I think "makeactive" is a better
> name for what it does.
Actually I don't really care but on http://grub.enbug.org/CommandList it 
was suggested to change the name. But what I dislike is having this 
command without argument which always activates current root partition
> 
> Maybe we could use a more generic solution, e.g. a command for setting
> different flags (or "attributes" in GPT terminology), such as bootable,
> read-only, hidden (that would apply only to some partition types in the
> PC partition table) and so on.

It's a good possibility but I don't want to encumber the partition 
module with non-essential functions since they're often integrated into 
core.img. But it's possible to have something like

pctool hd0,1 boot+ hidden-
gpttool hd0,1 ro+

(Actually I find the name "pc" unfortunate, IMO "fdisk" would be much 
better)
It's also possible to write a wrapper
parttool hd0,1 boot+

Which chooses the correct tool and launches it (a tool can be easily 
registered as a pair of partition style name and a function). In this 
case we wouldn't even need separate command for different partition 
style. We have however to find a way to list all available flags in

help parttool

Regards
Vladimir 'phcoder' Serbinenko





  reply	other threads:[~2009-02-11 18:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-11 13:43 [PATCH] make partition active phcoder
2009-02-11 16:26 ` Pavel Roskin
2009-02-11 18:28   ` phcoder [this message]
2009-03-01 18:58     ` Bean
2009-03-01 21:20       ` phcoder
2009-03-02  3:52         ` Bean
2009-03-04 20:54           ` Robert Millan

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=499318E3.5040801@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.