Since I enabled all the debugging options that would compile, I re-ran
the mkfs.reiser4 /dev/hda8, then attempted to untar the linux kernel
again, however it didn't like that very much:
Here is what I got from the log:
lookup inode: 65897 de4x5.c
creating de4x5.c in 65897
reiser4 panicked
Jeffrey Yasskin wrote:
I've been looking at the reiser4 source code for a few days, and I
can't find any non-essential plugins.
This is called the minimal functionality for first release project
management style. ;-)
For example: You say on the website that you've written several
security
Andi Kleen wrote:
Hans Reiser [EMAIL PROTECTED] writes:
Because atomicity in ext3 basically consists of guaranteeing that the filesystem is consistent, and due to the disk drive implementation 4k blocks are written atomically. So, if you span more than one block, it is not guaranteed to be
Compile of linux-2.6.0-test4 with reiser4 is good.
Compile of libaal-0.4.9 is good
Compile of reiser4fsprogs-0.4.12 is good.
mkfs.reiser4 /dev/hda8 is good.
When I issue the following command:
mount -t reiser4 /dev/hda8 /mnt/lfs or
mount -t reiserfs /dev/hda8 /mnt/lfs
I get the following
On Tue, 2003-09-02 at 20:51, Mike Benoit wrote:
Since I enabled all the debugging options that would compile, I re-ran
the mkfs.reiser4 /dev/hda8, then attempted to untar the linux kernel
again, however it didn't like that very much:
Here is what I got from the log:
lookup inode: 65897
