see e.g.
http://www.cs.bell-labs.com/cm/cs/doc/85/1-05.ps.gz
On Wed, 2004-09-08 at 17:13, Hans Reiser wrote:
Use of : in addition to / is a bad idea, see The Hideous Name by Rob
Pike for why.
Hans
Wichert Akkerman wrote:
Previously Andrew Morton wrote:
But I'll grant that one cannot go adding new metadata to, say, C files this
way. I don't know how useful such a thing is though.
That is actually one of the few places where a bit of metadata would be
very useful. Right now there is no way
On Tue, 7 Sep 2004 15:28:06 +0300, Raymond A. Meijer
[EMAIL PROTECTED] wrote:
Hi,
I have an interesting problem. I've been running Squid for a long time now on
my workstation with its cache directories on a Reiser4 partition.
Since Reiser4 has been stable for some time now, I decided to
Jeff Mahoney wrote:
Hans Reiser wrote:
| Sonny Rao wrote:
| Below I made 24 one gigabyte files in sequence
| All of them are similarly fragmented:
| this could explain some reiser3 performance problems. This is what
| happens when I spend all my time chasing funding and don't spend it
| reviewing
What about using // as some URI entry point?
An URI looks like:
PROTOCOL://PROTOCOL_SPECIFIC_NAMESPACE_IMPLEMENTATION
As no one can guarantee unix semantics in an URI space only symbolic
links are allowed to and from the URL namespace.
The protocol names are issued by the kernel to prevent
Use of : in addition to / is a bad idea, see The Hideous Name by Rob
Pike for why.
Hans
I've read The Hideous Name, and I think you're taking Pike out of context.
He wrote that document when device files were still only a part of a
research version of UNIX. His main point is that
I use reiserfs but not familiar with the technical details. I'm
wondering if it's possible to use meta tags in reiser4 fs to add
labels to files.
for example, I could have labels: photo, work, personal, vacation
then a jpg file from work would have the labels photo and work.
it allows
Christian Mayrhuber
What about using // as some URI entry point?
An URI looks like:
PROTOCOL://PROTOCOL_SPECIFIC_NAMESPACE_IMPLEMENTATION
I considered that in that //: is implicitly file://, but didn't make it
explicit in the proposal. Perhaps //: could be a legal alias for //file://.
Christian Mayrhuber wrote:
What about using // as some URI entry point?
One problem that using // may have (thought it is personally my favourite
option right now) is that realpath(3) may cause the // to be eaten, and
this is used by many programs to resolve pathnames to remvoe symlinks,
bogus
Before we get too far into the merits of implementation-specific pathname
resolution for paths starting with //, it seems wise to address the POSIX
implications of any duality implied by this (or any other) semantic change.
This is the first issue raised in my original post. Gunnar Ritter also
On PowerPC, I have never got ReiserFS working. It breaks apart when
trying to copy contents to ReiserFS from existing Ext3 filesystem. I
tried this about one year ago (PowerPC 603e, latest Linux 2.4 kernel
back then), and now again (PowerPC 604e, Linux 2.4.27 kernel) with
same results.
Mounting
Christian Mayrhuber wrote:
//http://somehost:port/foo/bla
While we're here, I'll point out that http://somehost/foo/bla and
http://somehost/foo/bla/ are valid, distinct URLs.
If http://somehost/foo/bla/ exists, many HTTP servers will return it
as the target of a redirect for
David Dabbs wrote:
Use of : in addition to / is a bad idea, see The Hideous Name by Rob
Pike for why.
Hans
I've read The Hideous Name, and I think you're taking Pike out of context.
He wrote that document when device files were still only a part of a
research version of UNIX. His main
I think that simple file and directory syntax provides what you need.
Just keep in mind that in reiser4, storing labels in files is effective
to do.
Hans
Bedros Hanounik wrote:
I use reiserfs but not familiar with the technical details. I'm
wondering if it's possible to use meta tags in reiser4
From: Jamie Lokier [mailto:[EMAIL PROTECTED]
Christian Mayrhuber wrote:
//http://somehost:port/foo/bla
While we're here, I'll point out that http://somehost/foo/bla and
http://somehost/foo/bla/ are valid, distinct URLs.
... snip
Food for thought.
-- Jamie
While I think there
Jamie Lokier wrote:
[snip
When a simple cd into .tar.gz or .iso is implemented properly, it
will have _no_ performance penalty after you have first looked in the
file, so long as it remains in the on-disk cache. And, the filesystem
will manage that cache intelligently.
Imagine: for looking at
Hans Reiser wrote:
David Dabbs wrote:
Use of : in addition to / is a bad idea, see The Hideous Name by Rob
Pike for why.
Hans
I've read The Hideous Name, and I think you're taking Pike out of
context.
He wrote that document when device files were still only a part of a
A friend asked me a question, and because he is very bright it reminded
me that I have not done a good job of reviewing the history of the
design's evolution.
He asked me, why not just access a filename's size as filename/size?
So, the original idea was to access metafiles as just files within
David Dabbs wrote:
Do you have a proposal to
expose metadata on a directory such that it
a) allows one to distinguish a directory entry from directory metadata,
this should be only a style convention, not a deep semantic difference.
Maybe Peter can comment on this.
b) uses only
19 matches
Mail list logo
