Re: silent semantic changes with reiser4

From: Nicholas Miell (nmiell_at_gmail.com)
Date: 08/26/04

  • Next message: Dave Jones: "Re: bizarre 2.6.8.1 /sys permissions" 
    To: Wichert Akkerman <wichert@wiggy.net>
Date:	Wed, 25 Aug 2004 17:42:21 -0700

    On Wed, 2004-08-25 at 16:46, Wichert Akkerman wrote:
    > Previously Jeremy Allison wrote:
    > > Multiple-data-stream files are something we should offer, definately (IMHO).
    > > I don't care how we do it, but I know it's something we need as application
    > > developers.
    >
    > Aside from samba, is there any other application that has a use for
    > them?
    >

    Anything that currently stores a file's metadata in another file really
    wants this right now. Things like image thumbnails, document summaries,
    digital signatures, etc.

    As to how to do it, I think the Solaris interface is reasonably decent.
    The overview is at http://docs.sun.com/db/doc/816-0220/6m6nkorp9?a=view

    (An important detail for those who want to access their
    multiple-data-streams from non-MDS aware apps is the runat shell
    command, which basically does a chdir into the specified file's
    attribute directory and then runs a command. i.e. 'runat ~/blah ls' will
    list the ~/blah's attributes.)

    The only real problem I have with their design is the calling them
    attributes and using "at" everywhere.

    "Attributes", because it will get confused with the current Linux xattr
    implementation (which is still useful for things that actually are file
    attributes, like security labels, ACLs, weird attributess that
    FAT/NTFS/whatever have, etc.).

    I don't like "at" because the API changes don't have anything to do with
    the actual attributes. It's a general set of changes to allow paths
    relative to a fd instead of the cwd, and doesn't really have anything
    specifically to do with attributes (with the exception of the O_XATTR
    flag).

    Replace "at" with "rel" and O_XATTR with O_FORK or O_MULTI or something,
    and it's all good.

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  • Next message: Dave Jones: "Re: bizarre 2.6.8.1 /sys permissions"

    Relevant Pages

    • Re: Arrr! Linux v2.6.14-rc2
      ... command that comes in through scsi_queue_insert. ... command each time, the retries decrement is never seen, so we're ... int scsi_queue_insert(struct scsi_cmnd *cmd, int reason) ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [RFC] ethtool semantics
      ... I find the c) feature very convenient. ... the configuration of the switch, something which is usually (pick your ... Command line parameters of the bcm5700 driver do implement c) (among ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [PATCH] implement nice support across physical cpus on SMP
      ... PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: 2.6.0-test6 -- Huh???
      ... | internal details of the Linux kernel. ... Given that my truck is not ... command, I suspect something on your system might have an unhappy script ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: 2.6.9-mm1: LVM stopped working
      ... > in IDE detection and settings messages and device-mapper messages. ... so the bug is likely to be in IDE stuff. ... There's some new dm-crypt code in -mm1 along with some API changes, ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)