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. > > Since the purpose of PRAMFS is to provide a filesystem > that is persistent across kernel instantions, it is not > designed for high speed. Robustness in the face of > kernel crashes or bugs is the highest priority, so > PRAMFS has significant overhead to make the window > of writability to the filesystem RAM as small as possible. > > This is not a file system one would do kernel compiles on. > This is where someone would keep a small amount of sensitive > data, or crash logs that one needed to preserve over kernel > invocations. > Yep, I quite agree. Marco -- 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
