From: Andrei Borzenkov <arvidjaar@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: grub-devel@gnu.org, David Shaw <dshaw@jabberwocky.com>,
syslinux@zytor.com
Subject: Re: [syslinux] Using memdisk with grub2 and a gzip-compressed ISO
Date: Fri, 24 Apr 2015 06:41:28 +0300 [thread overview]
Message-ID: <20150424064128.71489695@opensuse.site> (raw)
In-Reply-To: <5539B8C1.4030401@zytor.com>
В Thu, 23 Apr 2015 20:30:09 -0700
"H. Peter Anvin" <hpa@zytor.com> пишет:
> On 04/23/2015 08:14 PM, Andrei Borzenkov wrote:
> > В Thu, 23 Apr 2015 15:17:02 -0700
> > "H. Peter Anvin" <hpa@zytor.com> пишет:
> >
> >> On 04/23/2015 07:23 AM, David Shaw via Syslinux wrote:
> >>>
> >>> I'm not sure if this is related to the problem, but note the length
> >>> in the "Ramdisk" line from grub legacy is one byte shorter than the
> >>> length from grub2. Also note that the length given in the "gzip
> >>> image" line is shifted one byte to the left in the grub legacy
> >>> version (i.e. it's exactly 0x100 times larger).
> >>>
> >>
> >> That would definitely break using a compressed ramdisk.
> >
> > It does not break for kernel. What makes is so different in case of
> > syslinux?
> >
>
> Padding the image doesn't matter for the kernel, but memdisk relies on
> being able to see where the end of the compressed image is, because that
> is where the length is located.
CRC+length (in case of gzip) are located immediately after compressed
stream. After stream is decompressed you get location where it ends and
automatically where length is located.
next prev parent reply other threads:[~2015-04-24 3:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-23 14:23 Using memdisk with grub2 and a gzip-compressed ISO David Shaw
2015-04-23 16:59 ` Andrei Borzenkov
2015-04-23 22:17 ` [syslinux] " H. Peter Anvin
2015-04-24 3:14 ` Andrei Borzenkov
2015-04-24 3:30 ` H. Peter Anvin
2015-04-24 3:41 ` Andrei Borzenkov [this message]
2015-04-24 4:39 ` H. Peter Anvin
2015-04-24 6:25 ` Andrei Borzenkov
2015-04-27 22:20 ` H. Peter Anvin
2015-04-29 13:55 ` Vladimir 'φ-coder/phcoder' Serbinenko
2015-04-29 16:28 ` Andrei Borzenkov
2015-04-29 17:45 ` Andrei Borzenkov
2015-04-29 18:35 ` Vladimir 'phcoder' Serbinenko
2015-04-30 3:36 ` Andrei Borzenkov
2015-04-29 18:42 ` David Shaw
2015-05-07 14:23 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=20150424064128.71489695@opensuse.site \
--to=arvidjaar@gmail.com \
--cc=dshaw@jabberwocky.com \
--cc=grub-devel@gnu.org \
--cc=hpa@zytor.com \
--cc=syslinux@zytor.com \
/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.