All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vipin Malik <vmalik@danielind.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: mtd@infradead.org
Subject: Re: Unable to mount compressed root f/s because init_mtd() does not r egister block device!
Date: Fri, 23 Feb 2001 12:02:55 -0600	[thread overview]
Message-ID: <3A96A5CF.82BDE33E@danielind.com> (raw)
In-Reply-To: 20965.982916696@redhat.com

David Woodhouse wrote:

> vmalik@danielind.com said:
> >  Are you saying that you'll not fix this "bug" for me ;) Would saying
> > please help :)
>
> Heh. Of course I'll help. Not sure how best to go about it, though. Init
> order dependencies are ugly. rd_load() should probably be one of the last
> things in the boot sequence, rather than an initcall. Can you add it to
> init/main.c just before mount_root()?

Ok, I did it in my kernel and that worked too, but that's not the permanent
solution is it?


>
>
> > > We'll have JFFS2 (with compression) ready to roll out quite soon :)
>
> > Well, there still would be reasons to decompress a root file system
> > into ramdisk and run from there, namely:
>
> Definitely. Just pushing my new baby, that's all :)
>
> >  3. Compressibility: I would hazard a guess that the compressibility
> > obtained with compressing an entire file system image would be better
> > than that obtained with just compressing individual inode data.
>
> Yep. Actually we only compress a single page at a time
> in jffs2, not even the whole inode.

Do you have any figures as to how well it compresses vs say gzip -9?

Do you know why nobody added bzip2 support for compressed root file systems?
bzip2
does a better job at compression. Size of the code?

Vipin

>
>
> --
> dwmw2
>
> To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org



To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

  reply	other threads:[~2001-02-23 17:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-22 13:11 Unable to mount compressed root f/s because init_mtd() does n ot r egister block device! Vipin Malik
2001-02-22 13:18 ` David Woodhouse
2001-02-22 19:22   ` Vipin Malik
2001-02-22 19:00     ` David Woodhouse
2001-02-22 20:18       ` Vipin Malik
2001-02-22 21:32         ` Vipin Malik
2001-02-22 21:55           ` David Woodhouse
2001-02-22 22:41             ` Unable to mount compressed root f/s because init_mtd() does not " Vipin Malik
2001-02-23  8:24               ` David Woodhouse
2001-02-23 18:02                 ` Vipin Malik [this message]
2001-02-23 17:37                   ` David Woodhouse
  -- strict thread matches above, loose matches on Subject: below --
2001-02-22  4:19 Vipin Malik
     [not found] ` <3A956884.2050504@brocade.com>
2001-02-22 20:01   ` Vipin Malik
2001-02-23  8:22     ` David Woodhouse

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=3A96A5CF.82BDE33E@danielind.com \
    --to=vmalik@danielind.com \
    --cc=dwmw2@infradead.org \
    --cc=mtd@infradead.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.