LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Adam Borowski <kilobyte@angband.pl>
Cc: Paul Menzel <pmenzel+linux-kernel@molgen.mpg.de>,
	linux-kernel@vger.kernel.org, x86@kernel.org,
	Ingo Molnar <mingo@kernel.org>
Subject: Re: How to disable Linux kernel self-extraction (KERNEL_GZIP, KERNEL_BZIP2, …)?
Date: Tue, 24 Apr 2018 11:55:55 +0200	[thread overview]
Message-ID: <20180424095555.GA11868@amd> (raw)
In-Reply-To: <20180424020824.2vsddcdndjnvdm46@angband.pl>

[-- Attachment #1: Type: text/plain, Size: 623 bytes --]

Hi!

> > Actually... Compressors usually have a mode when they store the data
> > uncompressed. So you should be able to prepare .gz image which is not
> > really compressed inside, and thus really fast to uncompress.
> 
> I can't seem to find any.  IIRC xz format can store uncompressed blocks but
> the tool doesn't appear to expose this as an option.

I believe most compressors should be able to do that. But yes, that
option would need to be exported.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

      parent reply	other threads:[~2018-04-24  9:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-20 14:36 Paul Menzel
2018-04-22 10:20 ` Pavel Machek
2018-04-22 19:55   ` Paul Menzel
2018-04-22 20:52     ` Pavel Machek
2018-04-23 17:02       ` Pavel Machek
2018-04-24  2:08         ` Adam Borowski
2018-04-24  9:08           ` Paul Menzel
2018-04-24 23:06             ` Adam Borowski
2018-04-25  1:12             ` On Tue, Apr 24, 2018 at 11:08:34AM +0200, Paul Menzel wrote: Adam Borowski
2018-04-24  9:55           ` Pavel Machek [this message]

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=20180424095555.GA11868@amd \
    --to=pavel@ucw.cz \
    --cc=kilobyte@angband.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=pmenzel+linux-kernel@molgen.mpg.de \
    --cc=x86@kernel.org \
    --subject='Re: How to disable Linux kernel self-extraction (KERNEL_GZIP, KERNEL_BZIP2, …)?' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).