On Thu, Feb 17, 2011 at 11:12:06AM +1300, Charles Manning wrote: > On Wednesday 16 February 2011 21:04:20 Christoph Hellwig wrote: > > The procfs interfaces should be replaced by something saner, > > the insane amount of ad-hoc tracing crap should be replaced by much > > less strategically placed trace events, and all those stupid compile > > time options have absolutely no business at all beeing there for a > > filesystem - > Why not? > > remember you can get media from all over the place. > No you can't. This is a flash file system for soldered down flash. I think > that is a fundamental place where your understanding of what yaffs is falls > down. Even for embedded systems people do end up wanting to do things like using the same kernel on multiple systems which may have different hardware configurations (distros and reference boards are the obvious examples, but I've worked on systems where multiple generations and builds of the product were in active use and similar enough to be maintained from the same kernel). Even with single system kernels there's still an issue with things like reference boards where users are doing things like picking up a new upstream kernel rather than the vendor BSP. > > If you can't encode these difference in your on-disk format it has > > absolutely no business going into mainline with this format. > Yaffs does not really have an on-disk format like most other fs do. I'm not sure exactly how you'd do this for a filesystem but this is starting to sound a lot like platform data... Though presumably if the data isn't stored on the device currently it'd be a simple matter of programming (if wasteful) to add it. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
