On Monday 27 March 2006 23:25, Hans Reiser wrote:
> (none of which benefit reiser4 much).
Mainline will benefit R4 much. Good luck! I know you guys can do it!
-p
--
Peter van Hardenberg ([EMAIL PROTECTED])
Victoria, BC, Canada
dowload latest
> >>development source. Namesys.com gives directions for using BitKeeper
> >>repositories. Is this the only way to download latest code?
> >>
> >>Thank you.
> >>
> >>Amit
> >
> >if you want to contribute to reiser4,
ts.
(Further additions, corrections, and alternate configurations are welcome.)
-p
--
Peter van Hardenberg ([EMAIL PROTECTED])
Victoria, BC, Canada
pgpjXW7wI1U9o.pgp
Description: PGP signature
tuation, at which point I will redirect the URL automatically and post the
new URL here.
Tell me, do you have an public access SVN or CVS repository I could link the
wiki to for source references?
-pvh
--
Peter van Hardenberg ([EMAIL PROTECTED])
Victoria, BC, Canada
pgpvjj1EeFuYe.pgp
On Tuesday 28 February 2006 12:07, Yoanis Gil Delgado wrote:
> On Tuesday 28 February 2006 01:24, Peter van Hardenberg wrote:
> We most take the advance.I suggest to all people interested in this to
> spent a full weekend creating such a plugin. There is a possibility of
> failure but.
I can. If anyone out there
disagrees with me about the current difficulty of producing even a simple
plugin, let them prove me wrong with a patch.
-pvh
--
Peter van Hardenberg ([EMAIL PROTECTED])
Victoria, BC, Canada
pgpmtn3bbb9eH.pgp
Description: PGP signature
On February 10, 2006 07:08 am, Edward Shishkin wrote:
> Edward Shishkin wrote:
> Perhaps it got fixed when migrating to the new code
> for reiser4/vfs interface (Peter used the old one).
>
> Edward.
I'll verify this some time soon. Good to hear!
-p
--
Peter van Hardenbe
g comments is also a good idea but I would more like to contribute
> in the form of code :) I am a good C programmer and have hands on
> experience in Linux kernel programming. Can anyone suggest something?
> Thanks
> Bandan
--
Peter van Hardenberg ([EMAIL PROTECTED])
Victoria, BC, Canada
t; nil
irb(main):007:0> exit
[EMAIL PROTECTED]:/home/norbs/reiser/emptydir//plugin$ cat fibration
2 ext-1 fibrate file by single character extension
[EMAIL PROTECTED]:/home/norbs/reiser/emptydir//plugin$
I'd look more closely at how proc does it and how we do it, but I'm too tired
for source digging tonight.
-pvh
--
Peter van Hardenberg ([EMAIL PROTECTED])
Victoria, BC, Canada
eiser4 plugin
developers, and it will continue to grow as time goes by.
> Well... I think this is all (for now :D ). Please let me know what you
> think.
I would second Hans' suggestion about a "/version/snapshot" file which
would essentially act like a "cvs commit" on that file. I'd suggest that
there be two similar versioning plugins, one which automatically versions
after each write, and one which only does it when explicitly asked to. See
the fibration plugin type for an example of this.
-p
--
Peter van Hardenberg ([EMAIL PROTECTED])
Victoria, BC, Canada
t actually seekable. This
is why B-tree indexed databases maintain leafs in strict increasing order,
which can cost a TON to maintain under certain kinds of load.
-pvh
--
Peter van Hardenberg ([EMAIL PROTECTED])
Victoria, BC, Canada
you described how you thought it would work in a sentence or
two. Could you perhaps flesh out the idea to a paragraph or three? With that
much guidance, I think we could go further without feeling like we are
wasting effort.
-pvh
--
Peter van Hardenberg ([EMAIL PROTECTED])
Victoria, BC, Canada
Edward,
we are running reiser4-for-2.6.12-3.patch.gz on 2.6.12 Debian. Your patch
worked perfectly and directed us to some code that answered a few other
questions we had. Thank you.
-pvh
On December 15, 2005 11:33 am, Edward Shishkin wrote:
> Peter van Hardenberg wrote:
> >How to pr
)
{
return ERR_PTR(RETERR(-ENOTSUPP));
}
Please comment on why this returns -ENOTSUPP instead of returning the host
file/pseudo file which is the parent of the current directory.
-pvh
--
Peter van Hardenberg ([EMAIL PROTECTED])
Victoria, BC, Canada
d, it shall calculate it anew, also
> updating the subdirs' pseudo files if so needed, and store it actually
> on disk...
> (could also be updated periodically without anyone requesting it, but
> that's just a detail)
>
> What do you think? Useful? Bad Thing? Already done? Too hard for a first
> try?
>
> cheers,
> Danny
--
Peter van Hardenberg ([EMAIL PROTECTED])
Victoria, BC, Canada
How to produce the error:
$ chmod +w "file/"
$ touch file//newattr
Segmentation fault.
We tried setting "dir_eperm" on the pseudo directory plugin's create member.
Why didn't this fix it?
-pvh
--
Peter van Hardenberg ([EMAIL PROTECTED])
Victoria, BC, Canada
ory is deleted as though it were a child
directory in the usual fashion.
-
The most difficult part is (4). If we could get some advice about appropriate
functions/code to look at, it would be most appreciated.
All the best,
-pvh
--
Peter van Hardenberg ([EMAIL PROTECTED])
Victoria, BC, Canada
.size = wire_size_pseudo,
.done = wire_done_pseudo
},
.init_inode_data = NULL,
.pre_delete = NULL,
.cut_tree_worker = cut_tree_worker_common,
.destroy_inode = NULL,
},
Thanks,
-pvh
--
Peter van Hard
codecs library. It's 140MB
> file; and very informative, but made me think less of winFS.
>
> -B
--
Peter van Hardenberg ([EMAIL PROTECTED])
Victoria, BC, Canada
ved by different plugins.
On December 3, 2005 02:54 am, Peter Foldiak wrote:
> Are you sure the simple "/" is not a more elegant and simple way to do
> all this.Peter
No, I'm not sure, but I'm hoping we'll find one by talking about it.
--
Peter van Hardenberg ([EMAIL PROTECTED])
Victoria, BC, Canada
ld prefer "@" for improved
consistency with xpath, but worrying about the actual string to access with
is worrying about what colour the shed will be before you put it up.
I think resource directories in the style of OSX have a seperate value to them
and also deserve implementation, but are another (related) project.
Dinner beckons,
-pvh
--
Peter van Hardenberg ([EMAIL PROTECTED])
Victoria, BC, Canada
e pack the
following:
Small file with an attribute directory:
inode
->data
->attributedir_inode
->attributedir_ dir_file
->attribute_inode
->attribute_data
--
Peter van Hardenberg ([EMAIL PROTECTED])
Victoria, BC, Canada
On November 20, 2005 11:47 pm, Hans Reiser wrote:
> Peter van Hardenberg wrote:
> >We have an implementation plan for the attribute plugin. We plan to base
> > it around the plugin.c so that it can be available for all files,
> > directory or otherwise.
> >
> >E
should provide the optimization of only creating the inode once it
becomes needed and otherwise simulating an empty directory.
Namesys folks, does this seem like a good course of action?
-pvh
--
Peter van Hardenberg ([EMAIL PROTECTED])
Victoria, BC, Canada
nt about your idea, just about its
presentation.
-pvh
--
Peter van Hardenberg ([EMAIL PROTECTED])
Victoria, BC, Canada
a rather unclear
name. Something like "defaultfileplugin" might be easier to deduce, or even
"defaultchild".
-pvh
--
Peter van Hardenberg ([EMAIL PROTECTED])
Victoria, BC, Canada
On November 12, 2005 12:32 pm, you wrote:
> Peter van Hardenberg wrote:
> >Hans,
> >
> >I am having trouble modifying a file to use our new plugin. I've tried
> > writing various values into "foo/.^4/plugin/file" but it won't stick.
>
> This is
here.
Can you point me in the right direction?
-pvh
--
Peter van Hardenberg ([EMAIL PROTECTED])
Victoria, BC, Canada
t an attribute
on that file which told it only to clone the file every once in a while.
Come to think of it, a userspace daemon could run in the background and
replace the need for a plugin, which is probably the better solution. Then
you just need COW and files which can contain resource
ortant that would turn out to be. PF
PF, I intend to work on a(n inefficient) proof-of-concept xPath shell once
this attribute notation / storage mechanism is finished.
--
Peter van Hardenberg ([EMAIL PROTECTED])
Victoria, BC, Canada
requires a huge amount of
work right now and that would reduce its utility. Perhaps it would make sense
if it were distributed as a patch with a plugin developer's guide.
-pvh
--
Peter van Hardenberg ([EMAIL PROTECTED])
Victoria, BC, Canada
you can do what little schoolchildren do:
> call them Peter F and Peter H (or Peter van H), provided they agree.
> That should be a reasonable compromise?
"pvh" is a fine substitute for Peter when there is ambiguity -- I've been
using it long enough now that it looks like my name to
the little bugs you find as you go, and
> tell us about them. Let me know about everything that affects
> semantics/functionality before fixing it though
I'll keep sending out these emails.
-pvh
--
Peter van Hardenberg ([EMAIL PROTECTED])
Victoria, BC, Canada
attributes
on a normal file with this, but no dice. It only works for directories.
That's probably more than enough for one night, but we had a real marathon
session today and have another planned for tomorrow starting in the early
afternoon.
Hope people are finding these interesting,
-pvh
--
Peter van Hardenberg ([EMAIL PROTECTED])
Victoria, BC, Canada
I'm keeping this on-list in the hope that a record of it may be of value to
other future "weekend-warriors" on how we approached this problem.
On November 6, 2005 10:56 pm, Hans Reiser wrote:
> Peter van Hardenberg wrote:
> Just start reading the regular unix file and d
latively simple examples
we may follow? Is there API documentation for the storage layer? If weekend
warriors are to be able to hack on Reiser, perhaps they can learn from our
experience. According to my limited research, there are no third-party
plugins yet that we can learn from.
Peter
--
Peter
On October 27, 2005 04:17 am, David Masover wrote:
> Peter van Hardenberg wrote:
> > On October 26, 2005 10:02 am, John Gilmore wrote:
> >
> > And I thought the whole idea was to unify the namespace and make things
> > like ID3 tags obsolete...
>
> The two are n
ID3 tags obsolete...
-pvh
--
Peter van Hardenberg ([EMAIL PROTECTED])
Victoria, BC, Canada
have
any experience with this? What kind of work is it going to take me to get
this going?
-pvh
--
Peter van Hardenberg ([EMAIL PROTECTED])
Victoria, BC, Canada
On October 25, 2005 04:08 pm, you wrote:
> Peter van Hardenberg wrote:
> >Hello all,
> >
> >I'm a student at the University of Victoria. Between myself and a few
> > fellow students we have embarked on a quest to do some experiments with
> > the Reiser4 meta
.
[EMAIL PROTECTED]:~/reiser $ cd A.mp3
[EMAIL PROTECTED]:~/reiser/A.mp3 $ ls
ls: reading directory .: Not a directory
[EMAIL PROTECTED]:~/reiser/A.mp3 $
I've hit a dead end, and I haven't found any documentation that can help yet.
-pvh
--
Peter van Hardenberg ([EMAIL PROTECTED])
Vi
ore than we can chew, but I expect it will be an
interesting ride, if nothing else.
Our first contribution will be a practical guide to installing Reiser4 (with
metadata enabled) under Ubuntu 5.10.
All the best,
-pvh
--
Peter van Hardenberg ([EMAIL PROTECTED])
Victoria, BC, Canada
42 matches
Mail list logo
