Re: silent semantic changes with reiser4

From: Markus QT=F6rnqvist?= (mjt_at_nysv.org)
Date: 08/26/04

  • Next message: Rusty Russell: "[PATCH 1/2] Neaten migrate_all_tasks" 
    Date:	Thu, 26 Aug 2004 10:53:48 +0300
To: Matt Mackall <mpm@selenic.com>

    On Thu, Aug 26, 2004 at 12:32:00AM -0500, Matt Mackall wrote:
    >
    >What it breaks is the concept of a file. In ways that are ill-defined,
    >not portable, hard to work with, and needlessly complex. Along the
    >way, it breaks every single application that ever thought it knew what
    >a file was.

    It breaks the concept of a file. In ways that offer more versatility,
    challenge the imagination to make even better progress and keeps
    Linux competing with competitors who are implementing this stuff
    as we speak.

    I for one would truly welcome the coming of thumbnails and descriptions
    in picture files, because I have a real-life project going on where
    that would be extremely handy to have in the actual file.
    Were I any richer, I'd pay Namesys to have this work for me :)

    >Find some silly person with an iBook and open a shell on OS X. Use cp
    >to copy a file with a resource fork. Oh look, the Finder has no idea
    >what the new file is, even though it looks exactly identical in the
    >shell. Isn't that _wonderful_? Now try cat < a > b on a file with a
    >fork. How is that ever going to work?

    Then I guess OS X ships a broken implementation of cp, yes?

    On the cat example, what if cat < a > b simply copies the "main stream"
    and not the metadata, as a feature. The key being, "as a feature"

    The metadata streams could get file descriptors of their own OR
    another program, streamcat or something, could be written to compensate.

    >I like cat < a > b. You can keep your progress.

    With all due respect, I hope not too many people agree with you :) 

    -- 
mjt
-
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: Rusty Russell: "[PATCH 1/2] Neaten migrate_all_tasks"

    Relevant Pages

    • 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] Prezeroing V8
      ... But that only describes why we want the feature, ... so we're splitting each zone's buddy structure into two: ... These are all design decisions which have been made, ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [PATCH][2.6] first/next_cpu returns values > NR_CPUS
      ... On Sun, 1 Aug 2004, Paul Jackson wrote: ... >> looks like a feature if you look at the code. ... > What code, what feature, what bug ... ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: Hughs alternate page fault scalability approach on 512p Altix
      ... The costs come about through wrong anticipations installing useless ... The patches that I posted have this feature off by default. ... It would seem to depends on the locality of reference in the affected files. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: silent semantic changes with reiser4
      ... > Matt Mackall wrote: ... >>to copy a file with a resource fork. ... the Finder has no idea ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)