From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Misc patches for grub2
Date: Sun, 27 Jul 2008 03:33:07 -0400 [thread overview]
Message-ID: <1217143987.16601.47.camel@ct> (raw)
In-Reply-To: <ca0f59980807270030k740d798of7e0b856ae3eee32@mail.gmail.com>
On Sun, 2008-07-27 at 15:30 +0800, Bean wrote:
> On Sun, Jul 27, 2008 at 3:20 PM, Pavel Roskin <proski@gnu.org> wrote:
> >> >> BTW, any comment about the other changes ?
> >> >
> >> > Why do we need "crc"? If there are chances that it will be used for
> >> > security, we should be using SHA-1.
> >>
> >> crc is useful in many place. For example, png, jffs2, etc.
> >
> > But why make it a command?
>
> There are two parts, one is lib/crc.c, which contains only the crc
> function, the other is command/crc.c, which is a command to calculate
> the crc of selected file. Although it's not necessary to have a
> command, but it can 1) serve as an example of how to use the crc
> function, 2) as a cheap way to verify if a file is read correctly by
> the fs driver.
OK, then it's probably a good idea.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-07-27 7:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 16:38 [PATCH] Misc patches for grub2 Bean
2008-07-25 17:19 ` Chris Knadle
2008-07-25 17:45 ` Bean
2008-07-25 18:58 ` Chris Knadle
2008-07-27 4:36 ` Pavel Roskin
2008-07-25 20:53 ` Robert Millan
2008-07-26 4:28 ` Bean
2008-07-27 4:55 ` Pavel Roskin
2008-07-27 6:00 ` Bean
2008-07-27 7:05 ` Pavel Roskin
2008-07-27 7:14 ` Bean
2008-07-27 7:20 ` Pavel Roskin
2008-07-27 7:30 ` Bean
2008-07-27 7:33 ` Pavel Roskin [this message]
2008-07-27 13:51 ` Bean
2008-08-05 10:36 ` Marco Gerards
2008-08-05 14:14 ` Bean
2008-08-05 17:30 ` Colin D Bennett
2008-08-05 20:11 ` 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=1217143987.16601.47.camel@ct \
--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.