Hi, > It sounds to me like different FSes have different needs. Maybe the best > approach is to have two or three fs APIs, according to the needs of the > fs. No, having several fs API is a maintainance nightmare, I think that's something everyone agrees on. What is needed is to modify the API to meet all requirements of vfs and needs of the fs. (The problem is we don't agree on what the fs needs...) bye, Roman - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
- Re: hfs support for blocksize != 512 Alexander Viro
- Re: hfs support for blocksize != 512 J. Dow
- Re: hfs support for blocksize != 512 Alexander Viro
- Re: hfs support for blocksize != 512 Roman Zippel
- Re: hfs support for blocksize != 512 Alexander Viro
- Re: hfs support for blocksize != 512 Roman Zippel
- Re: hfs support for blocksize != 512 Alexander Viro
- Re: hfs support for blocksize != 512 Alexander Viro
- Re: hfs support for blocksize != 512 Jeff V. Merkey
- Re: hfs support for blocksize != 512 David A. Gatwood
- Re: hfs support for blocksize != 512 Roman Zippel
- Re: hfs support for blocksize != 512 Albert D. Cahalan
- Re: hfs support for blocksize != 512 Alexander Viro
- Re: hfs support for blocksize != 512 Roman Zippel
- Re: hfs support for blocksize != 512 Alexander Viro
- Re: hfs support for blocksize != 512 Roman Zippel
- Re: hfs support for blocksize != 512 Alexander Viro
- Re: hfs support for blocksize != 512 Daniel Phillips
- Re: hfs support for blocksize != 512 Roman Zippel