Apologies if this gets posted twice, I saw there was a list malfunction so
posting it again as my previous message never showed up.
Hi Edward,
I've just tested the newer patch against 2.6.15.4, and have found a bug when
using `cat bmap` in a directory.
$ cd testdir/
$ cat bmap
kernel BUG
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 Hardenberg ([EMAIL PROTECTED])
Edward Shishkin wrote:
there are metas-patches on our ftp-server, although it is
not fresh. I'll advance it on the next week, ok?
Edward.
Attached is a patch for 2.6.15 that I threw together from the
2.5.14-rc5-mm1
patch on the ftp server. Please check if
Marcus Furlong wrote:
Hi,
The current reiser4 patch for 2.6.15 doesn't seem to have support for pseudo
files. Is there a seperate patch elsewhere for adding this functionality
back in?
Hello,
there are metas-patches on our ftp-server, although it is
not fresh. I'll advance it on the next
Hi
Edward Shishkin wrote:
there are metas-patches on our ftp-server, although it is
not fresh. I'll advance it on the next week, ok?
Edward.
Attached is a patch for 2.6.15 that I threw together from the 2.5.14-rc5-mm1
patch on the ftp server. Please check if it's ok.
Have a few
Chris Mason wrote:
On Fri, 2004-04-30 at 01:19, Hans Reiser wrote:
Chris Mason wrote:
On Thu, 2004-04-29 at 12:22, Nikita Danilov wrote:
[EMAIL PROTECTED] writes:
On Thu, 29 Apr 2004 19:59:22 +0400, Nikita Danilov said:
chmod u+rx backup/fsplit.c
x bit is
On Fri, 2004-04-30 at 01:19, Hans Reiser wrote:
Chris Mason wrote:
On Thu, 2004-04-29 at 12:22, Nikita Danilov wrote:
[EMAIL PROTECTED] writes:
On Thu, 29 Apr 2004 19:59:22 +0400, Nikita Danilov said:
chmod u+rx backup/fsplit.c
x bit is necessary for lookups, and r
I don't understand the sentence above. Is the bit only used by the
nondefault policies?
Sort of. The bit always applies for execute. The bit never applies for
traverse directory, unless the default policy is changed.
On Sun, 25 Apr 2004 13:09:26 +0300, Markus =?UNKNOWN?Q?T=F6rnqvist?= said:
On Sat, Apr 24, 2004 at 11:38:05PM -0500, David Masover wrote:
scripts, it'd be different, but we're talking about something that I
know I'd find a _manual_ use for. Even if you say that I can set it to
You check
Jumping into a thread already in progress ;-)
Just for the record, if ... is used for filesystem metadata, I
_will_ have to modify some software. This modification will take
about 10 seconds to do (far less time than a Reiser4 conversion), but
it will have to be done nonetheless. I used ...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John D. Heintz wrote:
| [...]
| Is this behavior currently part of Reiser4? I don't remember seeing it
| anywhere, but I do remember reading something about inheritence being
| needed for various features. Is this the same as inheritence?
I don't know
Hans Reiser wrote:
John D. Heintz wrote:
Hans Reiser wrote:
Let me verify something: You are suggesting that the metas
namespace be the entry point for all of the plugin namespaces? I had
assumed that each plugin would create it's own. That does certainly
reduce the scope of my problem.
It
John D. Heintz wrote:
Hans Reiser wrote:
John D. Heintz wrote:
Hans Reiser wrote:
Let me verify something: You are suggesting that the metas
namespace be the entry point for all of the plugin namespaces? I had
assumed that each plugin would create it's own. That does certainly
reduce the
John D. Heintz wrote:
Hi Grant,
No, I'm not familiar with this. I was trying to frame my questions
strictly in terms of Reiser4 naming constructs (the '/' operator only).
I only bring it up because extended attributes seem to have dealt with
your mentioned problem, potential name conflicts,
Hans Reiser wrote:
John D. Heintz wrote:
Does some sort of syntactic shorthand actually break the set
theoretic naming system rules? Or is this just something you view as
needless complexity?
precisely what syntactic shorthand?
foo/nsa:permissions - foo/nsa.gov/secure-linux/permissions
On Tue, 13 Apr 2004 13:47:12 CDT, John D. Heintz said:
foo/nsa:permissions - foo/nsa.gov/secure-linux/permissions
This assumes a mapping from nsa - nsa.gov/security/.
The characters up to the ':' would be looked up in a namespaces map, and
if found the substituion would occur before
On Tue, 2004-04-13 at 22:31, [EMAIL PROTECTED] wrote:
On Tue, 13 Apr 2004 13:47:12 CDT, John D. Heintz said:
foo/nsa:permissions - foo/nsa.gov/secure-linux/permissions
This assumes a mapping from nsa - nsa.gov/security/.
Implementing a mapping nsa - nsa.gov/security/ does not remove the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John D. Heintz wrote:
| Hans Reiser wrote:
|
| John D. Heintz wrote:
|
|
| Does some sort of syntactic shorthand actually break the set
| theoretic naming system rules? Or is this just something you view as
| needless complexity?
|
|
|
| precisely
Christian Iversen wrote on Mon, 5 Apr 2004 02:12:05 +0200:
Just a thought. Who on this list does NOT support ... instead of metas?
Windows has that as the parent of the parent directory.
I also use it as the second parent directory in a file system that allows multiple
parents, is the
Christian == Christian Iversen [EMAIL PROTECTED] writes:
Christian Just a thought. Who on this list does NOT support ...
Christian instead of metas?
I personally don't like the way that ... looks. IMHO, it's just ugly.
But that's my main complaint with it, and it's just an opinion.
Hmm.
20 matches
Mail list logo
