public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Quinlan <quinlan@transmeta.com>
To: linux-kernel@vger.kernel.org
Subject: Re: cramfs
Date: 15 Jul 2001 23:23:52 -0700	[thread overview]
Message-ID: <6yhewd8k93.fsf@sodium.transmeta.com> (raw)
In-Reply-To: <3B21A4F7.6040303@digitalme.com>

"Trever L. Adams" <vichu@digitalme.com> writes:

> I hate to ask this, however here goes.  I am doing some remote upgrading 
> and some other really funky stuff to some boxes I keep up.
> 
> Part of these are total system upgrades and I need to move data out of 
> the way while still having a working box.  I decided that cramfs may be 
> the way to do this.  If you can tell me no and point me to a resource on 
> how to do this, I would LOVE to hear about it.
> 
> However, the question is, how can I tell lilo to tell the kernel too 
> boot off a cramfs file system?  I have already created the file with 
> /etc /bin /sbin /dev and /lib from a working system, doing the correct 
> deletions and other such changes.  I have a 15 meg cramfs that should do 
> the trick.
> 
> Thank you for any help you can offer.

You want "cramfsboot" to boot cramfs root partitions directly.
(You'll also need the cramfs patch which is part of the Midori Linux
kernel package.)

ftp://midori.transmeta.com/midori-1.0.0-beta2/apps/cramfsboot-0.2_ML1.0.0-beta2-5.mlz

(It's a tarball.)

There are also several packages that handle upgrades of cramfs
partitions, etc.

- Dan

  reply	other threads:[~2001-07-16  6:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-09  4:24 cramfs Trever L. Adams
2001-07-16  6:23 ` Daniel Quinlan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-11-07 20:07 CRAMFS Bradley Bozarth
2003-11-09 15:15 ` CRAMFS H. Peter Anvin
2001-03-23 19:37 RAMFS, CRAMFS and JFFS2(was Re: /linuxrc query) David Woodhouse
2001-03-23 20:25 ` CRAMFS Bjorn Wesen
2001-03-23 22:01   ` CRAMFS Amit D Chaudhary

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=6yhewd8k93.fsf@sodium.transmeta.com \
    --to=quinlan@transmeta.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