[lkml]   [2004]   [Aug]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: silent semantic changes with reiser4
    Hans wrote:
    > We create filename/pseudos/backup, and that tells the archiver what to
    > do.....

    Instead of exposing the old semantics under a new interface, why not
    expose the new semantics under a new interface.

    There exist plenty of programs that know the old Unix semantics. There
    don't exist many working programs that use the new semantics that you're

    I raise again the example of how Windows adapted to long filenames. Old
    DOS and FAT programs, including my Unix backups of today, see a 8.3 name
    space. Only code that knows the new magic sees the long names.

    If given the choice of breaking much old, existing stuff, or some new,
    mostly not yet existing stuff, does not it make more sense to break what
    mostly doesn't exist yet?

    One possible way to do this, of no doubt many:

    * Stealing a corner of the existing filename space for
    some magic names with the new semantics.

    * A new option on open(2), hence opendir(3), that lights up
    these magic names.

    * Doing any of the classic pathname calls with such a
    new magic name exposes the new semantics - such calls
    access execve mkdir mknod mount readlink
    rename rmdir stat truncate unlink

    This means essentially constructing a map between old and new,
    such that changes made in either view are sane and visible
    from the other view.

    I won't rest till it's the best ...
    Programmer, Linux Scalability
    Paul Jackson <> 1.650.933.1373
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 14:05    [W:2.359 / U:0.084 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site