All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Command extension suggestions
Date: Thu, 14 Jun 2007 08:08:09 +0200	[thread overview]
Message-ID: <20070614060809.GA27145@aragorn> (raw)
In-Reply-To: <20070614034649.GA591@ws3.vdp.com>

On Thu, Jun 14, 2007 at 11:46:49AM +0800, Bean wrote:
> These ideas are mostly from grub4dos, I think they can be useful in GRUB2.
> 
> 1. cat
> 
> In addition to the current function, cat can also generate hexadecimal dump, 
> and it can optionally choose the range of bytes to display. For example:
> 
> cat [--hex] [--skip=S] [--length=L] FILE

Wouldn't it be more consistent to call it:

  od [-j|--skip-bytes=S] [-N|--read-bytes=L] FILE

> Sometimes it's useful to dump the content of physical memory, it can be
> implemented with a special option --mem. For example,
> 
> cat [--mem] [--skip=S] [--length=L] base_address
> 
> It can also be implemented with virtual device (md). For example,
> 
> cat --hex (md)+2

That sounds much cleaner IMHO.  But IIRC (md) is already in use by the
RAID/LVM stuff ?

> 2. find
> 
> Find command is missing in GRUB2. It's used to find the device which contains
> a certain file.
> 
> find [--set=var_name] FILENAME

We have this already, only with different name:

  search --set /file

(root is implicit, but it can be overriden)

-- 
Robert Millan

My spam trap is honeypot@aybabtu.com.  Note: this address is only intended
for spam harvesters.  Writing to it will get you added to my black list.



  reply	other threads:[~2007-06-14  6:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-14  3:46 Command extension suggestions Bean
2007-06-14  6:08 ` Robert Millan [this message]
2007-06-14  6:24   ` Bean
2007-06-14  9:42     ` Marco Gerards
2007-06-14 10:24       ` Bean
2007-06-14 10:49         ` Marco Gerards
2007-06-14 11:31           ` Bean
2007-06-14 11:50             ` Marco Gerards
2007-06-14 13:08               ` Bean
2007-06-14 13:48                 ` Marco Gerards

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=20070614060809.GA27145@aragorn \
    --to=rmh@aybabtu.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.