[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[no subject]
- <!--x-content-type: text/plain -->
- <!--x-date: Sat Jan 10 22:37:54 2004 -->
- <!--x-from-r13: psbjyre ng bhgcbfgfragvary.pbz (Quevf Tbjyre) -->
- <!--x-message-id: 1073792034.12895.6.camel@devel -->
- <!--x-reference: [email protected] --> "http://www.w3.org/TR/html4/loose.dtd">
- <!--x-subject: [ale] mounting backups -->
- <li><em>date</em>: Sat Jan 10 22:37:54 2004</li>
- <li><em>from</em>: cfowler at outpostsentinel.com (Chris Fowler)</li>
- <li><em>in-reply-to</em>: <<a href="msg00400.html">[email protected]</a>></li>
- <li><em>references</em>: <<a href="msg00400.html">[email protected]</a>></li>
- <li><em>subject</em>: [ale] mounting backups</li>
But:
Usage Notes
-----------
File sizes are limited to less than 16MB.
Maximum filesystem size is a little over 256MB. (The last file on the
filesystem is allowed to extend past 256MB.)
Only the low 8 bits of gid are stored. The current version of
mkcramfs simply truncates to 8 bits, which is a potential security
issue.
Hard links are supported, but hard linked files
will still have a link count of 1 in the cramfs image.
Cramfs directories have no `.' or `..' entries. Directories (like
every other file on cramfs) always have a link count of 1. (There's
no need to use -noleaf in `find', btw.)
No timestamps are stored in a cramfs, so these default to the epoch
(1970 GMT). Recently-accessed files may have updated timestamps, but
the update lasts only as long as the inode is cached in memory, after
which the timestamp reverts to 1970, i.e. moves backwards in time.
Currently, cramfs must be written and read with architectures of the
same endianness, and can be read only by kernels with PAGE_CACHE_SIZE
== 4096. At least the latter of these is a bug, but it hasn't been
decided what the best fix is. For the moment if you have larger pages
you can just change the #define in mkcramfs.c, so long as you don't
mind the filesystem becoming unreadable to future kernels.
On Sat, 2004-01-10 at 22:14, Stephen Turner wrote:
> > One thing you might try is google on cramfs and see what its
> > status is.
>
>
> yea thats about the only semi productive thing i found while googleing and
> its read only as well! but maybe with a little modification it can become
> write too, i dunno, havent ever done development stuff, altho it would be
> nice with some floppies using that :-p
>
> =====
> ::: common sense? does it come with a manual?:::
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
> <a rel="nofollow" href="http://hotjobs.sweepstakes.yahoo.com/signingbonus">http://hotjobs.sweepstakes.yahoo.com/signingbonus</a>
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> <a rel="nofollow" href="http://www.ale.org/mailman/listinfo/ale">http://www.ale.org/mailman/listinfo/ale</a>
</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<ul><li><strong>Follow-Ups</strong>:
<ul>
<li><strong><a name="00440" href="msg00440.html">[ale] mounting backups</a></strong>
<ul><li><em>From:</em> artic_knight at yahoo.com (Stephen Turner)</li></ul></li>
</ul></li></ul>
<!--X-Follow-Ups-End-->
<!--X-References-->
<ul><li><strong>References</strong>:
<ul>
<li><strong><a name="00400" href="msg00400.html">[ale] mounting backups</a></strong>
<ul><li><em>From:</em> artic_knight at yahoo.com (Stephen Turner)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00400.html">[ale] mounting backups</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00401.html">[ale] SMB options</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00400.html">[ale] mounting backups</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00440.html">[ale] mounting backups</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00411"><strong>Date</strong></a></li>
<li><a href="threads.html#00411"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>
<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>