On Monday 13 February 2006 05:30, Joerg Schilling wrote:
> "Christopher Friesen" <[email protected]> wrote:
> > Joerg Schilling wrote:
> > > "Christopher Friesen" <[email protected]> wrote:
> > >>There's nothing there that says the mapping cannot change with
> > >>time...just that it has to be unique.
> > >
> > > If it changes over the runtime of a program, it is not unique from the
> > > view of that program.
> >
> > That depends on what "uniquely identified" actually means.
> >
> > One possible definition is that at any time, a particular path maps to a
> > single unique st_ino/st_dev tuple.
> >
> > The other possibility (and this is what you seem to be advocating) is
> > that a st_ino/st_dev tuple always maps to the same file over the entire
> > runtime of the system.
>
> Well it is obvious that this is a requirement.
>
> If Linux does device name mapping at high level but leaves the low level
> part unstable, then the following coul happen:
>
> Just think about a program that checks a file that is on a removable media.
>
> This media is mounted via a vold service and someone removes the USB cable
> and reinserts it a second later. The filesystem on the device will be
> mounted on the same mount point but the device ID inside the system did
> change.
Joerg, I think you've got your OS's mixed up here. AFAIK, Linux does not have
a "vold" system.
> As a result, the file unique identification st_ino/st_dev is not retained
> and the program is confused.
I have to agree that you are correct, but then, most removable media in the
Linux world do not actually have physical inodes. AFAIK, DVD's use the UDF
filesystem, a lot of CDRW's are formatted the same, CD's/CDR's generally use
the ISO9660 filesystem and other removable media, such as any floppy disc and
the now ubiquitous "zip disk's" use FAT16. I'm not current on UDF, but from
prior experience, I'd be willing to bet it doesn't have indoes, and the
ISO9660 filesystem doesn't have them, even if you use the RR extensions. What
is referred to in the Linux kernel as inodes for those systems are generally
block indexes, and for the FAT filesystem what it calls an "inode" is just
the name and a few other bits - and in the case of an LFN being used on said
volume, the name is spread across several "special blocks"... invalidating
the concept of an INODE for said filesystems.
In any case, the hypothetical case you present here seems more in tune with
Solaris as you present it, since with UDEV the device node created for said
removable media would stay the same, and hence st_dev would also (IIRC)
remain the same.
DRH
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
