Re: [PATCH] cramfs is ro only, so honour this in inode->mode

From: Ingo Oeser (ingo.oeser@informatik.tu-chemnitz.de)
Date: Mon Jan 08 2001 - 11:59:17 EST

Next message: Chris Mason: "Re: ramfs problem... (unlink of sparse file in "D" state)"
Previous message: Alan Cox: "Re: ramfs problem... (unlink of sparse file in "D" state)"
In reply to: Alexander Viro: "Re: [PATCH] cramfs is ro only, so honour this in inode->mode"
Next in thread: Shane Nay: "Re: [PATCH] cramfs is ro only, so honour this in inode->mode"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Mon, Jan 08, 2001 at 08:42:35AM -0500, Alexander Viro wrote:
> If program considers these bits of st_mode as indication of ability
> to write into file - program is buggy and should be fixed. Regardless
> of cramfs.

Ok, point taken.

I fixed the generation of the tree to be crammed into the cramfs
image instead. Same code simplification without uglyfication of
the kernel ;-)

Thanks & Regards

Ingo Oeser

-- 
10.+11.03.2001 - 3. Chemnitzer LinuxTag <http://www.tu-chemnitz.de/linux/tag>
         <<<<<<<<<<<<       come and join the fun       >>>>>>>>>>>>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Next message: Chris Mason: "Re: ramfs problem... (unlink of sparse file in "D" state)"
Previous message: Alan Cox: "Re: ramfs problem... (unlink of sparse file in "D" state)"
In reply to: Alexander Viro: "Re: [PATCH] cramfs is ro only, so honour this in inode->mode"
Next in thread: Shane Nay: "Re: [PATCH] cramfs is ro only, so honour this in inode->mode"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Mon Jan 15 2001 - 21:00:18 EST