On Sat, 28 Jun 2003 03:09, Jason Holt wrote:
> On Fri, 27 Jun 2003, Fong Vang wrote:
> > I don't think turning the write option off during write is a good idea.
> > All file systems running reiserfs should make the file write-once. File
> > systems that do need to be rewriteable will use ext3 or
Hello!
On Fri, Jun 27, 2003 at 11:27:22AM -0600, 'Andreas Dilger' wrote:
> > this doesn't seem to work on kernel 2.4.20. I did a chattr +i on file but
> > rm -rf (as root) on the file deletes it.
> That is a reiserfs bug then... I just tested it with ext3 and it worked as
> expected.
No, it is
Hello!
On Fri, Jun 27, 2003 at 10:07:05AM -0700, Fong Vang wrote:
> this doesn't seem to work on kernel 2.4.20. I did a chattr +i on file but
> rm -rf (as root) on the file deletes it.
You need to mount with -o attrs mount option for extended attributes to work.
Bye,
Oleg
On Fri, 27 Jun 2003, Fong Vang wrote:
> Physical access to the machine is a separate issue which we're already
> addressing with biometrics and other measures.
>
> Could root be disabled completely? I haven't tried this before so I don't
> know what impact disabling root on the system would do.
Hello!
On Fri, Jun 27, 2003 at 12:23:07PM -0400, Chris Mason wrote:
> Most of these changes are in 2.4.21, which I've been using on an AMD64
Not the reiserfs_file_write() ones.
> bit box for a while without any problems. The bug should be somewhere
> else, it looks to me like these spots aren'
On Jun 27, 2003 10:07 -0700, Fong Vang wrote:
> this doesn't seem to work on kernel 2.4.20. I did a chattr +i on file but
> rm -rf (as root) on the file deletes it.
That is a reiserfs bug then... I just tested it with ext3 and it worked as
expected.
[root]# chattr +i /tmp/ttt
[root]# echo foo
Physical access to the machine is a separate issue which we're already
addressing with biometrics and other measures.
Could root be disabled completely? I haven't tried this before so I don't
know what impact disabling root on the system would do.
-Original Message-
From: Jason Holt [mai
On Fri, 27 Jun 2003, Fong Vang wrote:
> I don't think turning the write option off during write is a good idea. All
> file systems running reiserfs should make the file write-once. File systems
> that do need to be rewriteable will use ext3 or something else (that's how
> we do it now anyway).
this doesn't seem to work on kernel 2.4.20. I did a chattr +i on file but
rm -rf (as root) on the file deletes it.
-Original Message-
From: Andreas Dilger [mailto:[EMAIL PROTECTED]
Sent: Friday, June 27, 2003 10:01 AM
To: Fong Vang
Cc: 'Hans Reiser'; '[EMAIL PROTECTED]'
Subject: Re: Writ
On Jun 27, 2003 09:07 -0700, Fong Vang wrote:
> Once the write to the file is CLOSED the file should not be modifiable in
> any way. It should not be writeable by root. Ideally, this should be
> across reboot and across kernel. The current requirement is that as long as
> the modified kernel/re
I don't think turning the write option off during write is a good idea. All
file systems running reiserfs should make the file write-once. File systems
that do need to be rewriteable will use ext3 or something else (that's how
we do it now anyway).
Could it done in such a way that even root can'
Oleg Drokin schrieb:
I have traced the new problem to a cross compiler that compiles
code in a different way than native compiler for whatever reason
(demo is attached as test.c program, it should print "result is 1"
yes, that what it prints, no warnings were shown.
You might try that patch as wel
Oleg Drokin schrieb:
I have traced the new problem to a cross compiler that compiles
code in a different way than native compiler for whatever reason
(demo is attached as test.c program, it should print "result is 1"
yes, that what it prints, no warnings were shown.
You might try that patch as wel
On Fri, 2003-06-27 at 12:13, Oleg Drokin wrote:
> Hello!
>
> On Fri, Jun 27, 2003 at 04:38:00PM +0400, Oleg Drokin wrote:
>
> > I was looking in the wrong direction, when I produced that patch,
> > so it will produce zero output.
> > I hope to come up with ultimate fix soon enough. ;)
>
> Well,
Hello!
On Fri, Jun 27, 2003 at 09:07:05AM -0700, Fong Vang wrote:
> Once the write to the file is CLOSED the file should not be modifiable in
> any way. It should not be writeable by root. Ideally, this should be
> across reboot and across kernel. The current requirement is that as long as
> th
Hello!
On Fri, Jun 27, 2003 at 04:38:00PM +0400, Oleg Drokin wrote:
> I was looking in the wrong direction, when I produced that patch,
> so it will produce zero output.
> I hope to come up with ultimate fix soon enough. ;)
Well, there is a patch below that does *not* work for me ;)
But it shoul
16 matches
Mail list logo
