From: Hans Reiser <reiser@namesys.com>
To: Nikita Danilov <Nikita@Namesys.COM>
Cc: Reiserfs developers mail-list <Reiserfs-Dev@Namesys.COM>,
Reiserfs mail-list <Reiserfs-List@Namesys.COM>
Subject: Re: [v4] reiser4 dream came true... in Solaris9.
Date: Mon, 04 Aug 2003 18:02:01 +0400 [thread overview]
Message-ID: <3F2E6759.1070108@namesys.com> (raw)
In-Reply-To: <16174.25756.572144.198132@laputa.namesys.com>
Nikita Danilov wrote:
>Hans Reiser writes:
> > Nikita Danilov wrote:
> >
> > >Solaris9 supports extended attributes accessible through usual file
> > >system namespace. Support in cp, tap, cpio.
> > >
> > >http://docs.sun.com/db/doc/816-0220/6m6nkorp9?a=view
> > >
> > >Nikita.
> > >
> > >
> > >
> > >
> > What they did seems like what someone not really understanding what we
> > are doing would copy from our implementation if some guy from marketing
> > said that they needed it to compete with us. They don't really move
> > attributes into the namespace. They access them with an API separate
> > and additional to that used for files. The only thing they do get right
>
>You missed a bit about runat(1) command:
>http://docs.sun.com/db/doc/816-0210/6m6nb7mjs?a=view
>
Oh, this is so ugly. You have to do this separately with each directory
you want to access.
>
>About their copying this feature from reiser4: man pages are tagged as
>"SunOS 5.9 Last Revised 22 Jun 2001".
>
Well, I don't remember exactly when we started discussing this on lkml
and on our website, it was maybe 1999?, not sure, but you are probably
right that it is not copied. It is a bit obvious as inventions go.
Well, what they did is better than nothing, but I think it is
insufficiently thorough.
--
Hans
prev parent reply other threads:[~2003-08-04 14:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-04 8:27 [v4] reiser4 dream came true... in Solaris9 Nikita Danilov
2003-08-04 13:30 ` Hans Reiser
2003-08-04 13:46 ` Hendrik Visage
2003-08-04 13:50 ` Nikita Danilov
2003-08-04 14:02 ` Hans Reiser [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F2E6759.1070108@namesys.com \
--to=reiser@namesys.com \
--cc=Nikita@Namesys.COM \
--cc=Reiserfs-Dev@Namesys.COM \
--cc=Reiserfs-List@Namesys.COM \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.