I'm probably not the first to suggest this idea, and it's probably not a
very good idea, but here's my idea anyhow:
You have a file /usr/bin/emacs
with a metadata property in the overlaid namespace
/usr/bin/emacs/[[..]metas/]icon
According to some, this could cause some confusion.
viro wrote
On Mon, Sep 13, 2004 at 11:49:22AM +0400, Alex Zarochentsev wrote:
Hi,
This patch does not allow open(name, O_DIRECTORY) to be successful for
non-directories in reiser4. It replaces -i_op-lookup != NULL is dir
check for the last path component by explicit S_ISDIR(-i_mode) check.
viro wrote:
if (*name == '/') {
if (*(name+1)=='/' *(name+2)==':') {
name+=3;
Pathname resolution is a hell of a fundamental thing and kludges
like that are too ugly to be acceptable. If you can't make that clean
and have to resort to stuffing special cases
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
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://.
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
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
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
Michael Weissenbacher wrote:
i've investigated this problem further the last days and came to the
following conclusions:
[...]
fsck does not like all contain german umlauts. but otoh there are
filenames with umlauts that are ok!
here are some filenames that fail:
0123456789012345
| Michael Weissenbacher
David Dabbs wrote:
Even though both file sets contain umlauts, or perhaps more accurately extended
ASCII chartacters, there is something distinctive in the failure set: the
umlauts/extended characters appear after the 15th character. If you are using
| Michael Weissenbacher
David Dabbs wrote:
Even though both file sets contain umlauts, or perhaps more accurately extended
ASCII chartacters, there is something distinctive in the failure set: the
umlauts/extended characters appear after the 15th character. If you are using
Hans Reiser wrote:
We only do filesystem isolation because that is our specialty,
filesystems, and it is better to do less well.
We fundamentally differ from other approaches because I don't think the
problem is in developing tools to allow people to fine grain security if
they take the time
Hans Reiser wrote:
The LSM paper cited (that does not require paying money) says very
little about what they do with regards to the filesystem. Do you have a
more informative URL?
Okay. Here's what I found with a few clicks in Google. None of these will describe
exactly what you want to do.
The LSM paper cited (that does not require paying money) says very
little about what they do with regards to the filesystem. Do you have a
more informative URL?
Here's a concrete example of an LSM directory jail implementation. Not all the
features I think you're aiming for but it is
a gander at the paper you reference this weekend.
[EMAIL PROTECTED] wrote:
On Fri, 20 Aug 2004 07:23:24 -, David Dabbs said:
Hans and George, what did you find lacking in currently-available Linux
security module frameworks such as LIDS or LSM? They provide system
function hooks in which
Motivation
--
See Hans's original post. In and of itself, viewprinting will not be
more secure than chroot. Viewprinting should be less work than
chroot. By virtue of its being easier to deploy and administer, the
net effect
Let me be more precise here. Is the time spent mounting and umounting
included in the time for the phase?
[David Dabbs]
No. Each phase iteration is wrapped in a time call. The mounting and
unmounting happen before and after this, so there's shouldn't be any timing
impact. I'd need
-Original Message-
From: Hans Reiser [mailto:[EMAIL PROTECTED]
Sent: Saturday, August 07, 2004 11:18 PM
To: David Dabbs
Subject: Re: Was able to reproduce cp: cannot stat file.x: Input/output
error
How about, code was X, now it is Y, with just the relevant parts of the
code
-Original Message-
From: Hans Reiser [mailto:[EMAIL PROTECTED]
Sent: Sunday, August 08, 2004 1:09 PM
To: David Dabbs
Cc: 'ReiserFS List'; Nikita Danilov; Alexander Zarochentcev; E. Gryaznova
Subject: Re: Was able to reproduce cp: cannot stat file.x: Input/output
error
most
-Original Message-
From: Hans Reiser [mailto:[EMAIL PROTECTED]
Sent: Monday, August 09, 2004 1:18 AM
To: David Dabbs
Cc: 'ReiserFS List'; 'Nikita Danilov'; 'Alexander Zarochentcev'; 'E.
Gryaznova'
Subject: Re: Was able to reproduce cp: cannot stat file.x: Input/output
error
-Original Message-
From: Hans Reiser [mailto:[EMAIL PROTECTED]
Sent: Friday, August 06, 2004 11:16 PM
To: David Dabbs
Cc: 'Philippe Gramoullé'; 'ReiserFS List'
Subject: Re: Was able to reproduce cp: cannot stat file.x: Input/output
error
David Dabbs wrote:
i.e.
%.c
I am planning to implement ReiserFS on my operating system named Capital
(www.mitpune.com/research/capital1.html). To give a brief background -
Capital is a 32-bit Object Oriented operating system for the Intel
i386 range of microprocessors. Capital's features include
-Original Message-
From: Hans Reiser [mailto:[EMAIL PROTECTED]
Sent: Saturday, August 07, 2004 2:50 AM
To: David Dabbs
Cc: 'ReiserFS List'
Subject: Re: Was able to reproduce cp: cannot stat file.x: Input/output
error
Mongo. The pipe character is not legal in a filename
Something to add regarding the following errors from last night:
cp: cannot stat `/mnt/testfs/testdir0-0-0/f92': Input/output error
As part of my mongo benchmarking, I have added two steps before all other
processing:
1. Create a large number of directories on the benchmark device. These are
-Original Message-
From: Hans Reiser [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 04, 2004 12:39 PM
To: David Dabbs
Cc: 'Vladimir V. Saveliev'; [EMAIL PROTECTED]
Subject: Re: mongo_copy: cp: cannot stat `/mnt/testfs/testdir0-0-0/f92':
Input/output error
Please do whatever
For us to reproduce, we need to have a script of some sort that exactly
reproduces what you did.
It is especially significant to note such things as whether you might
have run out of disk space, etc.
No, that was not the case. Because of that very issue, I just bought a
larger drive
I excerpt the evidence of it:
Good for reiser4! Bad for me. Sigh. This is especially bad in that I have
not completed benchmarking the reiser4 key patch. Back to the hardware
store...
Sorry if my dodgy hardware stirred things up.
David
Using the reiser4 07.30-19.36-linux-2.6.8-rc2-mm1.diff.gz snapshot I can
mkfs.reiser4 okay, but attempting to mount either segfaults or locks up.
I rebuilt libaal (0.5.3) as well as reiser4fsprogs (0.5.6) just to be sure
but the problem remains. Here is the fs-relevant section from my .config
FWIW, I built with 4k stacks.
dd
Elena:
...run reiser4 with and without 'notail'
...would you please reboot before each test?
it does not matter 4k or 8k, I think. So, you can try to repeat 4k
benchmark just to be sure that your previous results were correct (if
you want, of course).
ext3 default is ok.
-Original Message-
From: Hans Reiser
Sent: Monday, July 26, 2004 2:12 PM
Subject: Re: mongo benchmark results
The 4k results are also valid/important results. I just tend to choose
8k for the website for various valid reasons.
We probably should try 500 byte file sizes and
Hi,
I'm trying to get some mongo benchmarks running, but I can't seem to get a
RUN to finish without failing. The most recent error I encountered was
Use of uninitialized value in concatenation (.) or string at ./mongo.pl line
562.
Any ideas? Will investigate some more on this end. Thanks,
|
| No, not really, at least you (as a filesystem client) don't specify the
| fibration when searching for an object. Yes, when the key is generated,
of
| course the fibration bits matter, but they simply come from a blackbox
| plugin function that simply operates on the name and which may
Hans Reiser wrote:
| David Masover wrote:
|
| Why beyond? Ask each fs object (without knowing its name), What is
| your primary type? Put like-typed objects together. Simple.
|
| Except that at look up time all you know is the name, and if the type is
| not in the name then you cannot
I see theres a fresh auto-snapshot. According to the ChangeLog, the only
mods are the comment cleanup. Can one assume from this that the diff has
no active ingredients?
Thanks,
david
|
|I must not understand fibration. Do you have to know the fibration of
|an object to find it?
|
|
| Fibration is simply a means to physically group together filesystem
objects
= MEGA SNIP =
So, what you're trying to say is, yes, because it's part of the key?
No, not really, at
I'm curious why the fibration function prototypes take an inode* (that is
unused)? I looked at struct_inode and I can't see anything that looks
helpful to calculating a fibre.
/* fibration.c: sample fibration_plugin.fibre() function proto */
static __u64 fibre_dot_o(const struct inode *dir,
unsigned char 'hint' member added to the znode structure.
A writeup, including the timings and the code, is available at
http://dabbs.net/reiser4
I'd be interested in your feedback.
David Dabbs
unsigned char 'hint' member added to the znode structure.
A writeup, including the timings and the code, is available at
http://dabbs.net/reiser4
I'd be interested in your feedback.
David Dabbs
Thanks for looking over the code and for your responses.
Nikita wrote
Note that comparisons in C (like (v1 v2)) are not guaranteed to return 0
or _1_ as a result, but simply zero, or _non-zero_.
Is the information here (http://www.lysator.liu.se/c/c-faq/c-8.html)
incorrect then?
Nikita Danilov wrote
That said, I think that proper way to test your functions is to plug
them into kernel reiser4 version and run some CPU intensive tests.
Is bonnie++ the recommended stress tool, or is there a reiser4 stress
utility?
David
Con Kolivas is the cko maintainer:
http://kem.p.lodz.pl/~peter/cko/
David
My apologies, Con Kolivass page is at:
http://members.optusnet.com.au/ckolivas/kernel/
David
43 matches
Mail list logo
