On Sun, Apr 30, 2000 at 05:09:56PM +1000, Andrew Clausen wrote:
I was just thinking, there is a Linux extended partition (0x85).
Could we use that? It would probably screw up fdisk, but everyone
will be using parted anyway ;-) (Seriously: we could change fdisk)
No. 85 and F and 5 are just
In article cs.lists.linux-fsdevel/[EMAIL PROTECTED]
you wrote:
So I'm now leaning more towards losing the struct file/dentry from the
address_space ops. Furthermore, since the address_space structure showed up
relatively recently, we might consider cleaning up this API before 2.4. I
On Sun, Apr 30, 2000 at 10:09:45PM -0700, Hans Reiser wrote:
I think that improving support from folks who change VFS code for folks who
are affected is needed.
It's not just VFS that has this issue. It is a general philosophy
that kernelspace APIs can change in unstable versions; drivers in
On Mon, May 01, 2000 at 11:54:20AM -0400, Alexander Viro wrote:
Theory: different clients may want to share the cache for remote file.
They use some authentication to sign the RPC requests. I.e. you need to
have some token passed to the methods. struct file * is bogus here - it's
void * and
On Tue, May 02, 2000 at 01:50:16PM -0700, Chris Mason wrote:
ReiserFS has unique inode numbers, but they aren't enough to actually find
the inode on disk. That requires the inode number, and another 32 bits of
information we call the packing locality. The packing locality starts as
the
Alexander Viro writes:
On Mon, 1 May 2000, Richard Gooch wrote:
Alexander Viro writes:
On Mon, 1 May 2000, Richard Gooch wrote:
Eric W. Biederman writes:
Last I saw it was his complaint that you varied what you
showed at different mount points, and that doing that all in
