reiser4 plugins
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 2 lines · David Weinehall
Quoted 1 line · Hubert Chan
On Thu, 30 Jun 2005 08:29:56 +0200, David Weinehall <[email protected]> said:
[...]
Quoted 13 lines
Quoted 10 lines
Quoted 1 line
From the web *browser*'s point of view, it is handled by the
"filesystem" (which is provided by the various servers). The browser doesn't care how or where the data is stored. It just requests a file, and gets some data back. So the browser doesn't have to check for
http://www.example.com/, get a failure (trying to read a directory), check for http://www.example.com/index.html, etc. In this way, the web server controls (which I think takes the place of the filesystem in this case) what gets shown (index.html.sv, etc.), instead of the leaving it up to the browser.Quoted 2 lines
In the same way, you don't want every single user program to have to guess whether it should look at .data, or .contents, or whatever.
Quoted 8 lines
For the analogy to be complete:
User has a file browser (say Nautilus)
The file browser sees the userland VFS (say a unified VFS between GNOME and KDE)
The VFS sees the real file systemThis way the userland VFS can be ported to almost any platform.
That is /very/ nice to have.
Quoted 5 lines
When toying around on the desktop, an abstraction of what a file is works fine with me. When doing serious work (programming, tar:ing up stuff, etc) I want to be bloody sure that I see the files in the same way always. I don't want surprises such as files suddenly behaving as directories or vice versa.
Let me moderate that a bit: I'd be happy to have (some) files behaving strangely, /if in exchange I get something very worthwhile/. I.e., Unix filesystem sockets, named pipes, virtual filesystems all behave in weird ways, but this downside is more than compensated by huge advantages (even being able to do things that would otherwise be impossible). But all I see is that file-is-directory advocates explain over and over how they are bending over backards to get the whole mess working exactly like true directories (nothing more, in the end quite a bit less). The uses I've seen discussed don't really need files-as-directories (you get most of the advantages by just tar(1)-ing up the contents, or packing them in some other way; OpenOffice /has/ structured files, XML inside zipped files, Java also uses zip files for its structuring needs, etc), or are ideas that might be nice to have on exclusively one-user, isolated machines, like "keep /my/ annotations/icon/application name/whatever with the file's data", but that break down in multiuser (even serially, one user after the other) systems or when files are shared (via network, or simply by sending by mail or by copying from one machine to the other). In my rather ample experience, that situation is rare today, rapidly dwindling in the arena where Linux is mostly used. So this particular case of strange semantics for files has no upsides I can see, only downsides. The downsides have been discussed to death, and AFAICS there are fundamental problems with the idea that can't be fixed or sanely worked around. So why bother?
Signature · 4 lines
Dr. Horst H. von Brand User #22616 counter.li.org Departamento de Informatica Fono: +56 32 654431 Universidad Tecnica Federico Santa Maria +56 32 654239 Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513
Quoted 4 lines
might be nice to have on exclusively one-user, isolated machines, like "keep /my/ annotations/icon/application name/whatever with the file's data", but that break down in multiuser (even serially, one user after the
If this is really the core of your (and the rest of the reiser- obstructionist crowd's) objection to the file-as-directory concept, then you just haven't thought it through thoroughly enough. Ignore for the moment the case of system-wide or network-wide shared data, and think about it just limited to a user's home directory, and the storage and organization of actual *data* (as opposed to system files). The desire amongst users for ubiquitous metadata is very real - the current wave of "desktop search" products and technologies demonstrates this - but search is really only the lowest-hanging fruit of this new way of looking at data. Application-layer solutions like Beagle, Google Desktop Search et al allow for querying on metadata, but actually *acting* on the results of those queries requires that they be exposed via first class primitives which can be manipulated with arbitrary tools, not via some proprietary userland api which only one tool ever actually implements.
As to the case of system-wide shared files, there is already a mechanism to prevent users from inappropriately annotating files that don't belong to them: file permissions. If you're sysadmining a multiuser reiser4 box, and your users are able to modify the metadata of files they don't own, then you go to sysadmin purgatory.
Quoted 1 line
other way; OpenOffice /has/ structured files, XML inside zipped files,
Java
Quoted 1 line
also uses zip files for its structuring needs, etc), or are ideas that
And as a Java developer, I can tell you that the wide consensus is that this solution is half-assed and insufficient for both developers and users needs. In fact, I believe there is currently a JSR in progress to develop a more sophisticated Java packaging model.
Signature · 1 line
[email protected]
Quoted 8 lines · Kevin Bowen
Quoted 3 lines
might be nice to have on exclusively one-user, isolated machines, like "keep /my/ annotations/icon/application name/whatever with the file's data", but that break down in multiuser (even serially, one user after the
If this is really the core of your (and the rest of the reiser- obstructionist crowd's) objection to the file-as-directory concept, then you just haven't thought it through thoroughly enough. Ignore for the moment the case of system-wide or network-wide shared data,
I.e., something like 90% of the use of Linux here. OK.
Quoted 3 lines
and think
about it just limited to a user's home directory, and the storage and organization of actual *data* (as opposed to system files).
Who is to say what is "data" and what is "system files"? And if you are limiting yourself to /user/ data, why not have the /user/ decide how they want to organize it, and give them the tools?
Quoted 3 lines
The desire
amongst users for ubiquitous metadata is very real - the current wave of "desktop search" products and technologies demonstrates this -
Just like each previous claim "this /must/ be the next cool technology!", also called later the "dotcom crash"...
Quoted 3 lines
but
search is really only the lowest-hanging fruit of this new way of looking at data. Application-layer solutions like Beagle,
That works without screwing up the whole system, AFAIU.
Quoted 6 lines
Google Desktop
Search et al allow for querying on metadata, but actually *acting* on the results of those queries requires that they be exposed via first class primitives which can be manipulated with arbitrary tools, not via some proprietary userland api which only one tool ever actually implements.
Could you please explain in plain english? The only part I get out is "propietary API", and I don't see anybody advocating such here.
Quoted 3 lines
As to the case of system-wide shared files, there is already a mechanism to prevent users from inappropriately annotating files that don't belong to them: file permissions.
And who says that a normal user isn't allowed to annotate each and every file with its purpose or something else? I can very well imagine a system in which users (say students in a Linux class) want to do so... on a shared machine. Or users having a shared MP3 or photograph or ... collection, with individual notes on each. Or even developers wanting to annotate source code files with their comments, but leave them read-only (or have them under SCM).
Quoted 3 lines
If you're sysadmining a multiuser reiser4
box, and your users are able to modify the metadata of files they don't own, then you go to sysadmin purgatory.
Bingo! And thus goes much of the supposed advantage of this nonsense.
[I see that /opponents/ are accused here of lack of imagination, while I
see that the /proponents/ lack imagination... or perhaps just real-world experience.]
Quoted 8 lines
Quoted 3 lines
other way; OpenOffice /has/ structured files, XML inside zipped files, Java also uses zip files for its structuring needs, etc), or are ideas that
And as a Java developer, I can tell you that the wide consensus is that this solution is half-assed and insufficient for both developers and users needs. In fact, I believe there is currently a JSR in progress to develop a more sophisticated Java packaging model.
Presumably based on ReiserFS 4, which then has to be ported to whatever platform you want to run Java on ASAP? Great for you! Wait a bit, and you'll get what you want then, even across the board!
Signature · 4 lines
Dr. Horst H. von Brand User #22616 counter.li.org Departamento de Informatica Fono: +56 32 654431 Universidad Tecnica Federico Santa Maria +56 32 654239 Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513
Quoted 1 line · Horst von Brand
Kevin Bowen <[email protected]> wrote:
[...]
Quoted 7 lines
Quoted 3 lines
The desire
amongst users for ubiquitous metadata is very real - the current wave of "desktop search" products and technologies demonstrates this -Just like each previous claim "this /must/ be the next cool technology!", also called later the "dotcom crash"...
Have you used this technology?
For that matter, some of these claims have been true. The Internet, despite the dotcom crash, is now a requirement -- few people would use an OS with no networking support on a desktop PC. Same goes for GUIs. Both of these technologies had to have at least some amount of kernel support, both were once weird and experimental, and both are now in demand by users and likely to be for some time.
If we're right, and searching is the next best thing, then it would be a good idea to get started now. If we're wrong, what's the harm?
(Assuming /meta, of course. I accept that the issues with file-as-directory may never be solved to the point where we can do it at the kernel's FS/VFS level.)
Quoted 10 lines
Quoted 6 lines
Google Desktop
Search et al allow for querying on metadata, but actually *acting* on the results of those queries requires that they be exposed via first class primitives which can be manipulated with arbitrary tools, not via some proprietary userland api which only one tool ever actually implements.Could you please explain in plain english? The only part I get out is "propietary API", and I don't see anybody advocating such here.
I don't understand it much, but I think the point being made is that while desktop searches may be able to search metadata (not sure how they do this -- their own plugins or just full-text searching?), they cannot write to said metadata. To change metadata on a file, one currently needs to use a proprietary userland api which is only implemented by one tool.
So, for instance, if I want to grab all mp3s with Artist "Paul Oakenfold" and change the genre to "techno" (can you do that?), I can use Beagle's search tool to find all mp3s by Oakenfold, but to change the genre, I have to use some separate tool to manipulate id3 tags, which may or may not exist in an easily scriptable form.
I know there's a decent tool for id3 tags, but there's so many kinds of metadata and so many tools out there that the user can't possibly memorize them all. This is why I use the zipfile example, despite its flaws.
Now, the "arbitrary tools" bit is about how one could do this kind of thing with file-as-dir or /meta. With file-as-dir, it might be as simple as:
$ for i in `magical-find-tool artist='Paul Oakenfold'`; do echo 'techno' > "$i/.../genre"; done
Or even
$ echo 'techno' > /.../search/artist='Paul Oakenfold'/*/.../genre
It doesn't get too much more complicated for /meta, which has a nice side effect of not killing things like tar and generally not messing with POSIX.
One could also use vim, emacs, or whatever else to edit this metadata, instead of being limited to one program. This is especially nice considering you might have to look up which one program to use.
Quoted 5 lines
Quoted 3 lines
As to the case of system-wide shared files, there is already a mechanism to prevent users from inappropriately annotating files that don't belong to them: file permissions.
Quoted 7 lines
And who says that a normal user isn't allowed to annotate each and every file with its purpose or something else? I can very well imagine a system in which users (say students in a Linux class) want to do so... on a shared machine. Or users having a shared MP3 or photograph or ... collection, with individual notes on each. Or even developers wanting to annotate source code files with their comments, but leave them read-only (or have them under SCM).
File-as-dir is actually pretty nice for this, I think. Since the annotations appear as files, if the app supports it, the users can each store individual annotations, world-readable, but only user-writable.
With something like Gnome-VFS, I doubt there's even a mechanism whereby such annotations can be shared to begin with.
But this is just a thought experiment atm, don't pick it apart too brutally...
Quoted 3 lines
Quoted 3 lines
Could you please explain in plain english? The only part I get out is "propietary API", and I don't see anybody advocating such here.
Proprietary was a poor choice of words on my part.
Quoted 1 line
I don't understand it much, but I think the point being made is that
...
Quoted 4 lines
So, for instance, if I want to grab all mp3s with Artist "Paul Oakenfold" and change the genre to "techno" (can you do that?), I can use Beagle's search tool to find all mp3s by Oakenfold, but to change the genre, I have to use some separate tool to manipulate id3 tags,
Yes, this is basically what I was getting at, although I was thinking more in terms of the reiser5/6/whatever set theoretic semantics, which, from my point of view at least, reiser4 is simply the first step towards building the enabling infrastructure of. But the fact that reiser4 semantics + trivial shell scripting enables, as illustrated by David, the rough equivalent of set-theoretic semantics, demonstrates how reiser4 is in fact a step in this direction.
Quoted 2 lines
Quoted 1 line
moment the case of system-wide or network-wide shared data,
I.e., something like 90% of the use of Linux here. OK.
90% of *what* exactly? 90% of what machines deal with, or 90% of what humans interact with?
Quoted 6 lines
Quoted 2 lines
users needs. In fact, I believe there is currently a JSR in progress to develop a more sophisticated Java packaging model.
Presumably based on ReiserFS 4, which then has to be ported to whatever platform you want to run Java on ASAP? Great for you! Wait a bit, and you'll get what you want then, even across the board!
No, obviously that's not what I was saying. But the need for these kinds of domain-specific packaging/metadata formats, each requiring their own tools to work with, would be alleviated if there were simply a more powerful filesystem semantic. Clearly forcing reiser on the world is a non-starter, but try extending your imagination a little bit to a future in which there's a 'new POSIX' specifying a set-theoretic filesystem model. So-called 'database-filesystems' ARE coming, whether from Microsoft, Apple, or us. Who gets there first will determine who gets to make the rules.
Signature · 1 line
[email protected]
Kevin Bowen <[email protected]> wrote:
[...]
Quoted 5 lines
Quoted 4 lines
So, for instance, if I want to grab all mp3s with Artist "Paul Oakenfold" and change the genre to "techno" (can you do that?), I can use Beagle's search tool to find all mp3s by Oakenfold, but to change the genre, I have to use some separate tool to manipulate id3 tags,
Quoted 7 lines
Yes, this is basically what I was getting at, although I was thinking more in terms of the reiser5/6/whatever set theoretic semantics, which, from my point of view at least, reiser4 is simply the first step towards building the enabling infrastructure of. But the fact that reiser4 semantics + trivial shell scripting enables, as illustrated by David, the rough equivalent of set-theoretic semantics, demonstrates how reiser4 is in fact a step in this direction.
I don't see any "trivial shell scripting", just need for a plethora of magic extract-this-or-that-metadata programs. Which can very well work exactly the same on independent files, no need to shove junk /into/ the indexed files.
Quoted 5 lines
Quoted 2 lines
Quoted 1 line
moment the case of system-wide or network-wide shared data,
I.e., something like 90% of the use of Linux here. OK.
90% of *what* exactly? 90% of what machines deal with, or 90% of what humans interact with?
Both. Most use here is in computer labs, where most is shared via NFS (readonly), plus user data mounted read-write.
Quoted 11 lines
Quoted 6 lines
Quoted 2 lines
users needs. In fact, I believe there is currently a JSR in progress to develop a more sophisticated Java packaging model.
Presumably based on ReiserFS 4, which then has to be ported to whatever platform you want to run Java on ASAP? Great for you! Wait a bit, and you'll get what you want then, even across the board!
No, obviously that's not what I was saying. But the need for these kinds of domain-specific packaging/metadata formats, each requiring their own tools to work with, would be alleviated if there were simply a more powerful filesystem semantic.
*Please explain HOW*!! The domain-specific formats /will/ stay (if nothing else, because the /domains/ have /specific/ needs), the special tools to work with them /will/ have to be written exactly the same (because of the above). All for use on /one/ non-standard filesystem. Plus exactly the same stuff to work on sane filesystems. The kernel is *not* a magic piece of software that solves the problem of world hunger if you just can figure out what strange extension to force onto Linus' kernel version.
Quoted 4 lines
Clearly forcing reiser on the world is a
non-starter, but try extending your imagination a little bit to a future in which there's a 'new POSIX' specifying a set-theoretic filesystem model.
Sorry, I just don't see any need of shoving Oracle into the kernel. It leads a quite confortable life in userland.
Quoted 2 lines
So-called 'database-filesystems' ARE coming, whether from
Microsoft, Apple, or us.
IBM did it, long ago (AS/400 and OS/400 ring a bell?). And is now slowly moving away from it (and other structured filesystems), AFAICS, towards (guess what!) POSIX and Linux...
Again, Linux is what it is today in large part because "We have to get $FEATURE, because if not, $COMPETITOR will win on us!" arguments have no traction.
Quoted 2 lines
Who gets there first will determine who gets to
make the rules.
So what? Let /them/ make the mistakes and pay for them, and learn how to do it /right/, even if later!
Signature · 4 lines
Dr. Horst H. von Brand User #22616 counter.li.org Departamento de Informatica Fono: +56 32 654431 Universidad Tecnica Federico Santa Maria +56 32 654239 Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513
Quoted 41 lines · Horst von Brand
Kevin Bowen <[email protected]> wrote:
[...]
Quoted 10 lines
Quoted 1 line
So, for instance, if I want to grab all mp3s with Artist "Paul Oakenfold" and change the genre to "techno" (can you do that?), I can use Beagle's search tool to find all mp3s by Oakenfold, but to change the genre, I have to use some separate tool to manipulate id3 tags,
Yes, this is basically what I was getting at, although I was thinking more in terms of the reiser5/6/whatever set theoretic semantics, which, from my point of view at least, reiser4 is simply the first step towards building the enabling infrastructure of. But the fact that reiser4 semantics + trivial shell scripting enables, as illustrated by David, the rough equivalent of set-theoretic semantics, demonstrates how reiser4 is in fact a step in this direction.
I don't see any "trivial shell scripting", just need for a plethora of magic extract-this-or-that-metadata programs. Which can very well work exactly the same on independent files, no need to shove junk /into/ the indexed files.
Quoted 8 lines
Quoted 6 lines
Quoted 1 line
moment the case of system-wide or network-wide shared data,
I.e., something like 90% of the use of Linux here. OK.
Quoted 1 line
users needs. In fact, I believe there is currently a JSR in progress to develop a more sophisticated Java packaging model.
Quoted 8 lines
Quoted 2 lines
Presumably based on ReiserFS 4, which then has to be ported to whatever platform you want to run Java on ASAP? Great for you! Wait a bit, and you'll get what you want then, even across the board!
No, obviously that's not what I was saying. But the need for these kinds of domain-specific packaging/metadata formats, each requiring their own tools to work with, would be alleviated if there were simply a more powerful filesystem semantic.
Quoted 4 lines
*Please explain HOW*!! The domain-specific formats /will/ stay (if nothing else, because the /domains/ have /specific/ needs), the special tools to work with them /will/ have to be written exactly the same (because of the above). All for use on /one/ non-standard filesystem.
One filesystem that exists right now.
/proc, as people have made clear, was originally implemented on *one* "non-standard" Unix. Others then copied it. I see no reason why if /meta is a good idea, and programs start using it, that other FSes won't implement it.
Quoted 2 lines
Plus exactly the same
stuff to work on sane filesystems.
"sane" -- I assume you mean "traditional".
Well, yeah. So?
How big a program do you need to create a new interface to an existing system?
Consider: BitTorrent has at least three interfaces that I can remember at the moment. btdownloadgui.py, btdownloadcurses.py, btdownloadheadless.py.
Are you saying that btdownloadgui.py was so much work if you start from btdownloadcurses.py that there should be no GTK library, because it takes so much work to convert existing curses apps to GTK?
Remember, even if I have GTK installed, I can still get to my curses apps, and they may not even know that GTK exists. Even if I have /meta enabled, I can still use my POSIX apps, and they may not even know that /meta exists.
Quoted 7 lines
Quoted 2 lines
So-called 'database-filesystems' ARE coming, whether from
Microsoft, Apple, or us.IBM did it, long ago (AS/400 and OS/400 ring a bell?). And is now slowly moving away from it (and other structured filesystems), AFAICS, towards (guess what!) POSIX and Linux...
Linux over POSIX, I think. Because Linux is big and open-source, not beacuse POSIX is so great.
Quoted 3 lines
Again, Linux is what it is today in large part because "We have to get $FEATURE, because if not, $COMPETITOR will win on us!" arguments have no traction.
I agree with that, at least. But Linux is also what it is today in large part because "I don't need $FEATURE, so it should be kept out" isn't a particularly good argument either.
Quoted 9 lines · Horst von Brand
Quoted 5 lines · Kevin Bowen
and think
about it just limited to a user's home directory, and the storage and organization of actual *data* (as opposed to system files).
Quoted 5 lines
Who is to say what is "data" and what is "system files"? And if you are limiting yourself to /user/ data, why not have the /user/ decide how they want to organize it, and give them the tools?
That's exactly what the idea of exporting the metadata as files within a file-as-dir is intended to do: let the user decide how to manage metadata. They have the tools -- anything which can interact with a file. This includes users who never start X.
Quoted 12 lines
Quoted 7 lines
The desire
amongst users for ubiquitous metadata is very real - the current wave of "desktop search" products and technologies demonstrates this -Just like each previous claim "this /must/ be the next cool technology!", also called later the "dotcom crash"...
How does that analogy hold? An example of a technology which is actually in demand is similar to the tech bubble exactly how?
Quoted 10 lines
Quoted 5 lines
but
search is really only the lowest-hanging fruit of this new way of looking at data. Application-layer solutions like Beagle,That works without screwing up the whole system, AFAIU.
If you define "works" as "implements a proprietary layer which can't be used naturally by the same tools UNIX users have used for years to manage data".
Quoted 10 lines
And who says that a normal user isn't allowed to annotate each and every file with its purpose or something else? I can very well imagine a system in which users (say students in a Linux class) want to do so... on a shared machine. Or users having a shared MP3 or photograph or ... collection, with individual notes on each. Or even developers wanting to annotate source code files with their comments, but leave them read-only (or have them under SCM).
This same argument could be used to attack the idea of group permissions -- that groups of users might have conflicting goals. Implementing metadata in userspace via bundled files has the same drawback.
Quoted 10 lines
Quoted 5 lines
If you're sysadmining a multiuser reiser4
box, and your users are able to modify the metadata of files they don't own, then you go to sysadmin purgatory.Bingo! And thus goes much of the supposed advantage of this nonsense.
You seem to be implying that on a Reiser4 filesystem used by multiple users that people other than file owners will be about to apply arbitrary metadata to any object. It seems to me that adding metadata to a file-as-dir will require the same permissions as writing to the file itself, giving Reiser4 *zero* disadvantage against other multiuser systems. What gives you the impression that adding metadata to a file-as-dir is any harder to secure against modification from other users than the files themselves are in the first place?
Quoted 6 lines
[I see that /opponents/ are accused here of lack of imagination, while I see that the /proponents/ lack imagination... or perhaps just real-world experience.]
Huh? The idea of arbitrary metadata isn't just with annotating MP3 files. One seemingly important consideration would be the flexible implementation of add-on mechanisms, like security data, that could be implemented with zero changes to the filesystem. And you get to use existing tools to deal with new and arbitrary interfaces instead of having to deal with GUI garbage just to interact with metadata.
Quoted 15 lines
Quoted 8 lines
Quoted 5 lines
other way; OpenOffice /has/ structured files, XML inside zipped files, Java also uses zip files for its structuring needs, etc), or are ideas that
Quoted 6 lines
And as a Java developer, I can tell you that the wide consensus is that this solution is half-assed and insufficient for both developers and users needs. In fact, I believe there is currently a JSR in progress to develop a more sophisticated Java packaging model.
Quoted 5 lines
Presumably based on ReiserFS 4, which then has to be ported to whatever platform you want to run Java on ASAP? Great for you! Wait a bit, and you'll get what you want then, even across the board!
Are unable to differentiate between a statement that a given solution is non-ideal and a suggestion that everything be done in a way that requires Reiser4? Someone mentions that the current solution isn't quite meeting all of their needs, and you respond with rhetoric accusing them of wanting everything to depend on Reiser4 and bloat the kernel. How is this productive?
Quoted 3 lines · Chet Hosey
Quoted 2 lines · Horst von Brand
And who says that a normal user isn't allowed to annotate each and every file with its purpose or something else?
Explain how you currently allow users to annotate arbitrary files.
Quoted 10 lines
Quoted 5 lines
I can very well imagine a system in which users (say students in a Linux class) want to do so... on a shared machine. Or users having a shared MP3 or photograph or ... collection, with individual notes on each. Or even developers wanting to annotate source code files with their comments, but leave them read-only (or have them under SCM).
This same argument could be used to attack the idea of group permissions -- that groups of users might have conflicting goals. Implementing metadata in userspace via bundled files has the same drawback.
The situation is even better with file-as-dir. If the administrator wants to allow users to edit the description metadata for the file foo, the administrator can set the appropriate permissions for foo/.../description, and keep foo read-only.
Quoted 4 lines
Quoted 4 lines
Quoted 3 lines · Kevin Bowen
If you're sysadmining a multiuser reiser4 box, and your users are able to modify the metadata of files they don't own, then you go to sysadmin purgatory.
Actually, you could use something like unionfs to allow users to keep their own annotations without affecting everyone else's.
Signature · 4 lines
Hubert Chan <[email protected]> - http://www.uhoreg.ca/ PGP/GnuPG key: 1024D/124B61FA Fingerprint: 96C5 012F 5F74 A5F7 1FF7 5291 AF29 C719 124B 61FA Key available at wwwkeys.pgp.net. Encrypted e-mail preferred.
Quoted 6 lines · Hubert Chan
Quoted 3 lines · Chet Hosey
Quoted 2 lines · Horst von Brand
And who says that a normal user isn't allowed to annotate each and every file with its purpose or something else?
Explain how you currently allow users to annotate arbitrary files.
By keeping annotations /outside/ the files.
[...]
Quoted 4 lines
The situation is even better with file-as-dir. If the administrator wants to allow users to edit the description metadata for the file foo, the administrator can set the appropriate permissions for foo/.../description, and keep foo read-only.
So now root is responsible in exquisite detail for random other users being able to keep info about my files?
[...]
Quoted 2 lines
Actually, you could use something like unionfs to allow users to keep their own annotations without affecting everyone else's.
Again, root has to mount that stuff for each and every user?
Signature · 4 lines
Dr. Horst H. von Brand User #22616 counter.li.org Departamento de Informatica Fono: +56 32 654431 Universidad Tecnica Federico Santa Maria +56 32 654239 Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513
Quoted 18 lines · Horst von Brand
Quoted 9 lines · Hubert Chan
Quoted 4 lines · Chet Hosey
Quoted 2 lines · Horst von Brand
And who says that a normal user isn't allowed to annotate each and every file with its purpose or something else?
Explain how you currently allow users to annotate arbitrary files.
By keeping annotations /outside/ the files.
[...]
Quoted 8 lines
Quoted 4 lines
The situation is even better with file-as-dir. If the administrator wants to allow users to edit the description metadata for the file foo, the administrator can set the appropriate permissions for foo/.../description, and keep foo read-only.
So now root is responsible in exquisite detail for random other users being able to keep info about my files?
If it's the general info that's associated with the file, and may even be stored inside the file, then yes, that's fair.
Although I could certainly imagine foo/.../descriptions being a directory that's world-writable, allowing each user to maintain their own file inside of it. You can even set these per-user descriptions to be stored somewhere else, like the user's home directory, and that could work for CDs.
Quoted 5 lines
Quoted 2 lines
Actually, you could use something like unionfs to allow users to keep their own annotations without affecting everyone else's.
Again, root has to mount that stuff for each and every user?
Why is that a problem? Put it in a script. Mount each user's unionfs at boot.
And it's "something like unionfs" -- maybe it's a feature of metafs or reiserfs that we haven't thought of yet. It certainly can't be unionfs as it stands, as unionfs doesn't work on top of any reiser.
Quoted 10 lines · Horst von Brand
Quoted 7 lines · Hubert Chan
Quoted 3 lines · Chet Hosey
Quoted 2 lines · Horst von Brand
And who says that a normal user isn't allowed to annotate each and every file with its purpose or something else?
Explain how you currently allow users to annotate arbitrary files.
By keeping annotations /outside/ the files.
So if I want to share annotations, I have to look in 20 different places?
Quoted 9 lines
[...]
Quoted 4 lines
The situation is even better with file-as-dir. If the administrator wants to allow users to edit the description metadata for the file foo, the administrator can set the appropriate permissions for foo/.../description, and keep foo read-only.
So now root is responsible in exquisite detail for random other users being able to keep info about my files?
I can grant people permissions to write random info into my own files. Or they can use unionfs if I don't grant them permissions.
Remember: the above argument was citing an advantage of file-as-dir over packed files (storing metadata as a tar or zip file, similar to what OpenOffice.org does, or even something like exif or id3). In a packed file, I can't allow people to edit the description attribute without allowing them to edit the entire file. With file-as-dir, I get much finer grained permissions.
Quoted 6 lines
[...]
Quoted 2 lines
Actually, you could use something like unionfs to allow users to keep their own annotations without affecting everyone else's.
Again, root has to mount that stuff for each and every user?
suid program that allows union mount into a directory within my own tree (or just into any directory that I have write permissions should be sufficiently secure).
Signature · 4 lines
Hubert Chan <[email protected]> - http://www.uhoreg.ca/ PGP/GnuPG key: 1024D/124B61FA Fingerprint: 96C5 012F 5F74 A5F7 1FF7 5291 AF29 C719 124B 61FA Key available at wwwkeys.pgp.net. Encrypted e-mail preferred.
On Thu, 2005-06-30 at 14:47 -0400, Horst von Brand wrote:
[snip]
Quoted 14 lines
Let me moderate that a bit: I'd be happy to have (some) files behaving strangely, /if in exchange I get something very worthwhile/. I.e., Unix filesystem sockets, named pipes, virtual filesystems all behave in weird ways, but this downside is more than compensated by huge advantages (even being able to do things that would otherwise be impossible). But all I see is that file-is-directory advocates explain over and over how they are bending over backards to get the whole mess working exactly like true directories (nothing more, in the end quite a bit less). The uses I've seen discussed don't really need files-as-directories (you get most of the advantages by just tar(1)-ing up the contents, or packing them in some other way; OpenOffice /has/ structured files, XML inside zipped files, Java also uses zip files for its structuring needs, etc), or are ideas that might be nice to have on exclusively one-user, isolated machines, like "keep /my/ annotations/icon/application name/whatever with the file's
Quoted 8 lines
data", but that break down in multiuser (even serially, one user after the other) systems or when files are shared (via network, or simply by sending by mail or by copying from one machine to the other). In my rather ample experience, that situation is rare today, rapidly dwindling in the arena where Linux is mostly used. So this particular case of strange semantics for files has no upsides I can see, only downsides. The downsides have been discussed to death, and AFAICS there are fundamental problems with the idea that can't be fixed or sanely worked around. So why bother?
Structured files are fine when they're small but quickly become disgusting as they get bigger. Either you slowly rewrite the whole thing or you "fast save" by writing new sections to the end of it that replace existing sections. That's how you end up with documents that contain "deleted" information that was supposed to be confidential.
Having the filesystem track each part for you and then creating a structured file when needed (and without needing to remember to run a special tool) is a far better idea. (reiser4 doesn't do this but its a possible idea)
Another advantage to file-as-directory is being able to access all the file's meta-data through a single channel: file names and text data. It removes the need for chmod, chown, touch, getxattr, chacl and all the rest of the special tools needed to work with Unix files. It also makes it far easier to add new meta-data in the future, because no new tools have to be written to use it.
So that's two reasons to bother.
Signature · 1 line
Zan Lynx <[email protected]>
Quoted 2 lines · Zan Lynx
On Thu, 2005-06-30 at 14:47 -0400, Horst von Brand wrote:
[snip]
[snip-some-more]
Quoted 5 lines
Structured files are fine when they're small but quickly become disgusting as they get bigger. Either you slowly rewrite the whole thing or you "fast save" by writing new sections to the end of it that replace existing sections. That's how you end up with documents that contain "deleted" information that was supposed to be confidential.
Doesn't OpenOffice already do something similar with zipfiles? I remember noticing huge differences in save times after adding large images to a presentation versus just changing some text. So, it's obviously not repacking each image every time I save. But, as the internal text is all XML, I doubt it's leaving "deleted" sections lying around.
Quoted 4 lines
Having the filesystem track each part for you and then creating a structured file when needed (and without needing to remember to run a special tool) is a far better idea. (reiser4 doesn't do this but its a possible idea)
Been discussed to death, and chances are, Reiser4 will do this with plugins. I imagine it being implemented in a more general way, though.
For example, a meta-file which, when read, produces a
zipfile/tarball/dump of the directory it belongs to. Then, to send such a document via email, you just navigate to the directory where it lives while looking for files to attach, only from /meta/vfs as a base, then attach the meta-file. The zipfile gets built automatically.
To simplify the process, all you *really* need is a button on all FS navigation windows (Nautilus, Open/Save dialogs, etc) to switch back and forth between the meta view and the normal view. That, or a separate pane.
This way, instead of patching the mail client to support all possible transformations you'd want to do before sending, or patching all applications to use zip (and any other transformation a user might want to do), or forcing the user to run another app, you automatically get *all* available transformations, in a way that could potentially look as smooth as adding zip support directly to the app.
Quoted 6 lines
Another advantage to file-as-directory is being able to access all the file's meta-data through a single channel: file names and text data. It removes the need for chmod, chown, touch, getxattr, chacl and all the rest of the special tools needed to work with Unix files. It also makes it far easier to add new meta-data in the future, because no new tools have to be written to use it.
All good points except the last one. New tools vs new plugins? People already know how to write the tools...
Quoted 1 line
So that's two reasons to bother.
That, and the possible paradigm shift. Navigating to the /meta dir for a file could be the commandline equivalent of right-clicking on the file.
Of course, to some people, paradigm shifts are a reason *not* to bother...