From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0000151]: new target root filesystem provided: cloop
Date: Mon, 12 Feb 2007 05:47:49 -0800 [thread overview]
Message-ID: <ead82a6767ddfb51311085f60f21760c@bugs.busybox.net> (raw)
The following issue has been ASSIGNED.
======================================================================
http://busybox.net/bugs/view.php?id=151
======================================================================
Reported By: clausklein
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 151
Category: New Features
Reproducibility: N/A
Severity: feature
Priority: normal
Status: assigned
======================================================================
Date Submitted: 03-13-2005 13:07 PST
Last Modified: 02-12-2007 05:47 PST
======================================================================
Summary: new target root filesystem provided: cloop
Description:
Current version: 2.01-5
COMPRESSED LOOPBACK DEVICE (cloop.o)
=============================================================================
This module is licensed under the GNU GENERAL PUBLIC LICENSE Version 2,
as
stated in the source.
-----------------------------------------------------------------------------
The cloop.o, a Kernel module is needed to add support for
filesystem-independent, transparently decompressed, read-only block
devices.
Original Author: Paul 'Rusty' Russel
Extensions & Bugfixes: Klaus Knopper (http://www.knopper.net/knoppix/)
The current available debian patch is not used.
Note: target/default/device_table.txt is not yet supported! ck
The quickfix is to use sudo to mount the previous created cramroot
Sources from:
http://developer.linuxtag.net/knoppix/sources/cloop_2.01-5.tar.gz
For more infos see: http://knopper.net/knoppix-info/
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
03-13-05 13:07 clausklein New Issue
03-13-05 13:07 clausklein File Added: cloop.tgz
03-16-05 12:11 andersen Status new => assigned
03-16-05 12:11 andersen Assigned To => uClibc
01-25-06 05:54 prpplague Status assigned => resolved
01-25-06 05:54 prpplague Resolution open => fixed
01-25-06 05:54 prpplague Additional Information Updated
03-08-06 16:53 vapier Status resolved => closed
02-12-07 05:47 vapier Status closed => assigned
02-12-07 05:47 vapier Assigned To uClibc => buildroot
======================================================================
reply other threads:[~2007-02-12 13:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ead82a6767ddfb51311085f60f21760c@bugs.busybox.net \
--to=bugs@busybox.net \
--cc=buildroot@busybox.net \
/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