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.
Thanks. I put on that patch and it fixes my make problem.
Vladimir Saveliev wrote:
Hello
On Mon, 2004-04-12 at 20:53, Szakacsits Szabolcs wrote:
What timestamp resolution Reiser4 has? Ext[23] can't compile gcc because
[kernel bugs] and it doesn't have on-disk high resolution timestamps
thus t
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, wit
Does Reiser4 store stat data in real files, or some special way? Are
pseudo files just representation of stat data stored a special way? Is
it possible to do streams/forks with a plugin easily?
I mounted latest Reiser4 snapshot + linux 2.6.4 with acl and xattr
options but when I tried "getfat
Hubert Chan wrote:
"Narcoleptic" == Narcoleptic Electron <[EMAIL PROTECTED]> writes:
[...]
Narcoleptic> True; as long as everyone refers to the "metas" directory
Narcoleptic> properly (using an environment variable, for example, as
Narcoleptic> opposed to hard-coding the string "meta
I do not disagree that it is unlikely. However, it is
still possible, so my question remains: what happens
in the scenario I describe?
Hi
What happens now is open() returns EEXIST (file exists) error; reiser4
can't make the file. Is this what you mean?
Also I feel it should be on the file itself. ie for the file /tmp/fooblah
you should be able to access the file's metadata by open()ing/using
readdir() on /tmp/fooblah/metas or (/tmp/fooblah/..metas or whatever).
That's how it works now I believe.
Bad choice. Note the "lost+found" directory found
I'm excited about your packaging system. I hope you make something very
useful. Here are some ideas I have had about packaging and operating
system design; they might be interesting to you. Comments, suggestion,
other ideas are wanted.
Ideally, each user's home dir would mirror the system di
If you are making a packaging system, I recommend you do not allow
scipts, since they open up a whole can of worms. (They're impossible to
invert, introduce security problems, make additional work for GUI
package managers, and cause too many problems.)
I tested the performace of various filesystems with a mozilla build tree
of 295MB, with primarily writing and copying operations. The test
system is Linux 2.6.0-test2, 512MB memory, 11531.85MB partition for
tests. Sync is run a few times throughout the test (for full script see
bottom of this
Szakacsits Szabolcs wrote:
How much memory you have? How big is mozilla-1.5a.tar? Did you include
'sync' in the tests? It seems reiser4 numbers are mostly in-memory
operations and not all data flushed to disk while this is apparently not
true for ext3. BTW, XFS numbers would be also/more interestin
"mozilla-1.5a.tar" is mozilla 1.5alpha source tar, uncompressed.
Partition mkfs.ext3 or mkfs.reiser4 --keys=SHORT is run before each run.
Linux is 2.6.0-test2.
untar mozilla-1.5a.tar (file is on a reiser3 partition):
ext3: 17.64s 28% cpu
reiser4: 10.79s 67% cpu
sum: reiser4 0.61x time, 2.39x cpu
Hi!
I am trying to compile reiser4progs from bk; I run 'prepare' and get
this output
$ ./prepare
Running aclocal...
Running autoheader...
Running autoconf...
configure.in:44: error: possibly undefined macro: dnl
If this token and others are legitimate, please use m4_pattern_allow.
See t
13 matches
Mail list logo
