From mboxrd@z Thu Jan 1 00:00:00 1970 From: "H. Peter Anvin" Subject: Re: [Fwd: [Bug 136] New: FSID returned from statvfs always 0] Date: 9 Dec 2002 14:15:12 -0800 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: References: <3DED43F7.AD396584@digeo.com> <20021204032511.GA7646@win.tue.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Return-path: Received: (from root@localhost) by neon-gw.transmeta.com (8.9.3/8.9.3) id OAA23843 for ; Mon, 9 Dec 2002 14:15:28 -0800 Received: from palladium.transmeta.com (palladium.transmeta.com [10.1.1.46]) by deepthought.transmeta.com (8.11.6/8.11.6) with ESMTP id gB9MFER09860 for ; Mon, 9 Dec 2002 14:15:14 -0800 (PST) Received: (from mail@localhost) by palladium.transmeta.com (8.9.3/8.9.3) id OAA01580 for linux-fsdevel@vger.kernel.org; Mon, 9 Dec 2002 14:15:13 -0800 To: linux-fsdevel@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Followup to: <20021204032511.GA7646@win.tue.nl> By author: Andries Brouwer In newsgroup: linux.dev.fs.devel > > The general idea is that f_fsid contains some random stuff such that > the pair (f_fsid,ino) uniquely determines a file. > This, of course, is the exact POSIX definition of the st_dev part of struct stat: (st_dev, st_ino) uniquely identifies the file. -hpa -- at work, in private! "Unix gives you enough rope to shoot yourself in the foot." http://www.zytor.com/~hpa/puzzle.txt