[BusyBox] Question regarding Minix FS

Thomas Cameron tom at patcameron.ne.mediaone.net
Fri Mar 1 08:21:04 UTC 2002


	Cramfs is readonly.  Basically, this limits you from mounting
the filesystem, and writing changes to it.  In essence, you'd have to
create a new fsimage every time you wanted to add/remove/modify files.
This isn't that big a real, as the cramfs utils (with the kernel source)
compiles vs. uClibc last time I tried.  Anyway, readonly is really the
only downfall to cramfs.
	One plus for Cramfs is that it is compressed (thus the cram part
of the name).  However, this means that `gzip -9` isn't going to gain
you much at all.  Anyway, good luck, and keep us updated.

-Thomas Cameron

-----Original Message-----
From: Axel Kittenberger [mailto:Axel.Kittenberger at maxxio.at] 
Sent: Thursday, February 28, 2002 2:43 AM
To: Geoffrey Espin; Jeff Studer
Cc: busybox at busybox.net
Subject: Re: [BusyBox] Question regarding Minix FS


> I believe the most common strategy is to use cramfs with shmfs (for 
> writeable but temporary/volatile storage).  Then I added JFFS2 support

> for the permanent storage.

Hmmm, what has cramfs for advantages/disadvantages against minix?

_______________________________________________
busybox mailing list
busybox at busybox.net
http://busybox.net/mailman/listinfo/busybox



More information about the busybox mailing list