From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from dell-paw-3.cambridge.redhat.com ([195.224.55.237] helo=passion.cambridge.redhat.com) by pentafluge.infradead.org with esmtp (Exim 3.22 #1 (Red Hat Linux)) id 15M91Q-0007u9-00 for ; Mon, 16 Jul 2001 15:06:52 +0100 From: David Woodhouse In-Reply-To: References: To: David Mackay Cc: linux-mtd@lists.infradead.org Subject: Re: JFFS (2) - File locking Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 8bit Date: Mon, 16 Jul 2001 15:12:11 +0100 Message-ID: <21677.995292731@redhat.com> Sender: linux-mtd-admin@lists.infradead.org Errors-To: linux-mtd-admin@lists.infradead.org List-Help: List-Post: List-Subscribe: , List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: dave.mackay@monitoreurope.com said: > Currently on Ext2 our program uses the system call lockf() which > works well, however we read with interest that JFFS does not support > hard links and may have a problem with this call!!? Any comments?   File locking doesn't involve the underlying filesystem, I believe - at least not for non-networked file systems. File locking on JFFS and JFFS2 should just work. Hard links are a completely separate issue. JFFS doesn't support them. JFFS2 does. -- dwmw2