On Mon 2009-06-22 20:07:06, Marco wrote: > Pavel Machek wrote: > > On Mon 2009-06-22 10:31:28, Tim Bird wrote: > >> Pavel Machek wrote: > >>>>> How do you handle hard-links, then? > >>>> Indeed hard-links are not supported :) Due to the design of this fs > >>>> there are some limitations explained in the documentation as not > >>>> hard-link, only private memory mapping and so on. However this > >>>> limitations don't limit the fs itself because you must consider the > >>>> special goal of this fs. > >>> I did not see that in the changelog. If it is not general purpose > >>> filesystem, it is lot less interesting. > >> PRAMFS is not a general purpose filesystem. Please read > >> the introductory post to this thread, or look at > >> http://pramfs.sourceforge.net/ for more information. > > > > Yeah, I seen that. It directly contradicts what you say. > > > > I don't think, I think it's very clear: > > "In summary, PRAMFS is a light-weight, full-featured, and > space-efficient special filesystem that is ideal for systems with a Except that it is not full-featured. No hardlinks. (What about ACLs, etc?) > block of fast non-volatile RAM that need to access data on it using a > standard filesytem interface." Turns a block of fast RAM into 13MB/sec disk. Hmm. I believe you are better with ext2. -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- To unsubscribe from this list: send the line "unsubscribe linux-embedded" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
