linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "D. Stimits" <stimits@idcomm.com>
To: kernel-list <linux-kernel@vger.kernel.org>
Subject: bzDisk compression Q; boot debug Q
Date: Wed, 13 Jun 2001 15:11:26 -0600	[thread overview]
Message-ID: <3B27D6FE.8CE2A92A@idcomm.com> (raw)

First I have a question about the compression of bzDisk. While trying to
debug the reason for a modular boot failure versus a successful
non-module boot (XFS filesystem for root), I found that I can mount my
initial ramdisk on loopback as a means of examining which modules are
available to it. However, it doesn't actually point out which modules
were loaded at the time when a filesystem mount fails. Viewing ramdisk
is via:
gzip -dc your.img > somefile
mount -o loop somefile somedir

Question 1, how hard would it be to cause failure of mount of root
filesystem to also output a list of current modules it has loaded?

Question 2, apparently ramdisk uses gzip compression; the name of the
kernel from make bzImage seems to maybe refer to bzip2 compression. Is
the kernel image using gzip or bzip2 compression for bzImage? Would
anything be gained in reducing boot size requirements by running bzip2
compression for any initial ramdisk, versus gzip compression?

D. Stimits, stimits@idcomm.com

             reply	other threads:[~2001-06-13 21:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-13 21:11 D. Stimits [this message]
2001-06-13 21:39 bzDisk compression Q; boot debug Q Khachaturov, Vassilii
2001-06-14  7:38 ` D. Stimits
2001-06-14 12:27   ` Holger Lubitz
2001-06-14 20:44     ` D. Stimits

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=3B27D6FE.8CE2A92A@idcomm.com \
    --to=stimits@idcomm.com \
    --cc=linux-kernel@vger.kernel.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 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).