From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Transparent decompression with file system filter
Date: Sun, 13 Jan 2008 20:51:53 +0100 [thread overview]
Message-ID: <200801132051.53894.okuji@enbug.org> (raw)
In-Reply-To: <ca0f59980801122338g72b4bdb3re61d791ea88cf2ae@mail.gmail.com>
On Sunday 13 January 2008 08:38, Bean wrote:
> Hi,
>
> any suggestion about this patch ? i would like to commit it soon.
I am sorry that I forgot to reply.
I would like to know how you intend to approach the following issues:
- If you want to support, for example, an ecrypted and compressed file, in the
current implementation, each hook must try other hooks recursively. I believe
that this should be done at grub_file_open_ex rather than at every hook. Is
there any pitfall with this way?
- There are some cases where the user wants to skip some decoding features
(i.e. decryptions and decompressions). For instance, gunzip does not make
sense for initrd, since the linux kernel performs this. But if the user uses
other compression algorithms (e.g. LZMA), GRUB must decompress it before
transferring control to the kernel. Or, in the case of Multiboot modules, an
OS image might want to keep compressed modules as they are, but have GRUB to
decrypt them, if they are encrypted. How does the user select which hooks
should be applied (from the viewpoint of UI)?
Because your aim is quite broad (which is a good thing), I think we need to
consider possible use cases carefully, to make sure that the API is good
enough.
Okuji
next prev parent reply other threads:[~2008-01-13 19:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-03 16:06 Transparent decompression with file system filter Bean
2007-11-10 17:33 ` Marco Gerards
2007-11-14 6:34 ` Bean
2007-11-14 19:29 ` Vesa Jääskeläinen
2007-11-15 10:53 ` Jan C. Kleinsorge
2007-11-18 11:40 ` Marco Gerards
2007-11-19 8:02 ` Bean
2007-11-19 10:23 ` Bean
2007-12-31 16:59 ` Bean
2007-12-31 18:40 ` Robert Millan
2007-12-31 18:54 ` Bean
2008-01-02 23:19 ` Yoshinori K. Okuji
2008-01-03 8:49 ` Bean
2008-01-03 11:35 ` Robert Millan
2008-01-03 12:53 ` Bean
2008-01-03 13:20 ` Robert Millan
2008-01-03 15:53 ` Vesa Jääskeläinen
2008-01-05 1:29 ` Yoshinori K. Okuji
2008-01-05 6:30 ` Bean
2008-01-05 10:39 ` Yoshinori K. Okuji
2008-01-05 11:04 ` Bean
2008-01-13 7:38 ` Bean
2008-01-13 19:51 ` Yoshinori K. Okuji [this message]
2008-01-13 20:16 ` Bean
2008-01-13 20:53 ` Yoshinori K. Okuji
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=200801132051.53894.okuji@enbug.org \
--to=okuji@enbug.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.