Con Kolivas Patch + Reiser 4

linuxnubx · 08-20-2004, 02:21 PM

I'm sure it's possible, but how do I go about installing this? I heard, though, that it's not possible to remount in Reiser4 yet? Hmm, I hope this was in an earlier version because I want to try it out. Those of you who have experience with it in Slackware, post here. Thanks.

Tinkster · 08-20-2004, 03:44 PM

It's a matter of the kernel-version, not the linux distro.

http://www.namesys.com/download.html

If you're REALLY brave go for it ;)

Cheers,
Tink

linuxnubx · 08-20-2004, 04:20 PM

I just was wondering if I patched my kernel correctly. Here's what I did:

1) extracted 2.6.7 from /testing on slackware disc 2
2) downloaded the latest con kolivas patch
3) from /usr/src/, used commands "rm -f linux" and "ln -s linux-2.6.7 linux"
4) then, from /usr/src/linux, I patched using command "bunzip2 -c /usr/src/patch-2.6.8.1-ck3.bz2 | patch -p1"
5) make mrproper
6) cp /usr/src/linux-2.4.26/.config /usr/src/linux
7) make xconfig

That's basically the order I did this in. Anyways, I did get some errors while patching, like some hunks failed say "1 out of 14 hunks failed." Errors like that.

When I did make xconfig, it worked, but I didn't see any reiser4 option... So I assumed the con kolivas was not patched properly. I'm thinking it's because I did make mrproper after I patched. So I patched it again, still with some hunks failed, but this time I didn't run a make mrproper. Well I saw reiser4 option available in xconfig, but the things is there's 3 of them. Three identical reiser4 options. Buggy, or did I just mess up somewhere in the process?

So that's basically where I left of before I started typing this. Any suggestions? Is seeing 3 identical reiser4 options just a bug? And are certain hunks failing normal? If so, I'll continue upgrading my kernel. If not, suggestions?

Ok a little more detail. It starts patching a few files then gets to this question. What should I do?

Code:

Reversed (or previously applied) patch detected!  Assume -R? [n]

Well I decided to redo everything, and this time I didn't have 3 identical options for reiser4. I went through everything an got up to "make." So I type in make and everything is working fine until it gets to the end where it gives me an error:

Code:

make[1]: `arch/i386/kernel/asm-offsets.s' is up to date.
  CHK     include/linux/compile.h
  CC      kernel/sysctl.o
kernel/sysctl.c:761: error: `VM_FLUSH_INTERVAL' undeclared here (not in a function)
kernel/sysctl.c:761: error: initializer element is not constant
kernel/sysctl.c:761: error: (near initialization for `vm_table[9].ctl_name')
kernel/sysctl.c:770: error: initializer element is not constant
kernel/sysctl.c:770: error: (near initialization for `vm_table[9]')
kernel/sysctl.c:800: error: initializer element is not constant
kernel/sysctl.c:800: error: (near initialization for `vm_table[10]')
kernel/sysctl.c:810: error: initializer element is not constant
kernel/sysctl.c:810: error: (near initialization for `vm_table[11]')
kernel/sysctl.c:818: error: initializer element is not constant
kernel/sysctl.c:818: error: (near initialization for `vm_table[12]')
kernel/sysctl.c:828: error: initializer element is not constant
kernel/sysctl.c:828: error: (near initialization for `vm_table[13]')
kernel/sysctl.c:838: error: initializer element is not constant
kernel/sysctl.c:838: error: (near initialization for `vm_table[14]')
kernel/sysctl.c:839: error: initializer element is not constant
kernel/sysctl.c:839: error: (near initialization for `vm_table[15]')
make[1]: *** [kernel/sysctl.o] Error 1
make: *** [kernel] Error 2

linuxnubx · 08-20-2004, 05:06 PM

Hm.. Is there any way to convert all my ext2 partitions to reiserfs? It seems from their instructions that I have to do all of this within one of my partitions.. If I do that, then the ext2 partition that I used to convert the other partitions to Reiser4 will be stuck with ext2. Any way to work around this?

snop · 08-20-2004, 05:11 PM

Hi,

I tried reiser 4 (I used a Con Kolivas patch that included reiser 4 support). I followed the instructions but after formatting and copying new files to my reiser 4 they were no longer readable. They got corrupted. So I gave up and just set that drive as a reiser 3 and works flawlessly.

I bet reiser 4 gets better everyday. Since I tried reiser 4 some months ago you may have a better experince using the latest version.

Anyway, tell us you results if you dare to try.

Bye

SnOp

snop · 08-20-2004, 05:17 PM

I've been unsing Con Kolivas patches for some time. My system seems more responsive, but maybe it's just my imagination...

I think that kernel 2.6.7 from disc 2 just includes the header files. Try to download the kernel from www.kernel.org (that's what I did and worked fine).

Hope this helps.

Bye

linuxnubx · 08-20-2004, 05:34 PM

Yeah, I completely missed that one. I did go to kernel.org to get 2.6.8.1, but all I was seeing was the patch. When I looked again, I saw F which I clicked on, and it's the full 2.6.8.1. Downloading it right now; maybe this will work. Thanks.

Okay, patch works flawlessly with no errors. I thought the ck 2.6.8.1 would patch the 2.6.7 up to 2.6.8.1, but I guess it's only meant for 2.6.8.1 to begin with. Thanks for the help.

linuxnubx · 08-20-2004, 07:36 PM

I failed. I did everything, and made my /home into reiser4, but I couldn't transfer any files onto it. My /dev/hda8 is mounted onto /home btw which is like 90gb, so the /home folder isn't just a folder. So I decided to do it to my /boot, and everything was wiped. So, of course the next time I booted, I got kernel panics. Time to reinstall. I hope reiser4 becomes a standard option in Slackware soon.

XavierP · 08-22-2004, 03:11 PM

linuxnubx - since your 2 posts were about the same thing (one followed on from the other) I have merged them to a) keep the discussion in one place and b) to allow all to see the "chain of thought". ~~XavierP

nhatkhai · 09-07-2004, 05:14 AM

okay

i will give you briefly the steps i used to get reiser 4 up

first from nameys you will need to get the libaals, and reiser4 programs

then i used a fresh kernel 2.6.8.1 and patched with the ck patch found here

http://members.optusnet.com.au/ckolivas/kernel/

patch-2.6.8.1-ck6.bz2

install your kernel first, and make sure in kernel hacking section to disable the 4k stacks

so do not use make oldconfig when compiling the kernel

use make menuconfig

now place the kernel patch in its aquired format bzip2 in the /usr/src directory

leave it alone for now

go to your libaals, and install

then install the reiser4progs

now go to your /usr/src/linux directory

and this can work 2 ways, i installed on 2 diff machines, and one woorked one way, and the other

the other way

bzip2 -dc ../patch-2.6.8.1-ck6.bz2 | patch -p1 --dry-run

the above first, if doesnt find patch use below method

use the dry run to make sure patch takes before actually patching, so you dont end up with a half assed kernel

bzip2 -dc /patch-2.6.8.1-ck6.bz2 | patch -p1 --dry-run

now patch if succesful, take away the --dry-run at the end and patch your kernel

now you

make mrproper

now either make oldconfig

or make menuconfig, up to you, i like make menuconfig, so use that

activate what you ned to and make sure reiser 4 is enabled, and reiser4 largekey

done, run make, make modules, make modules install, make modules_install

realy jes make, and make modules_install should do, but i am so used to the 2.4 kernel, and use make modules and make modules install anyways, as make modules install ups the lilo any ways

do your cd /boot, rm vmlinuz ,rm System.map ,rm config ,

cd /usr/src/linux/arch/i386/boot

cp bzImage /boot/vmlinuz

cd /usr/src/linux

cp System.map /boot/System.map

cp .config /boot/config

lilo

reboot

now you have reiser4 support

mkfs.reiser4 /dev/the aprtition you want to mount on example /sda3

mkdir /reiser4

mount -t reiser4 /dev/sda3 /reiser4

you will create 3 directories in reiser 4 from root

mkdir /reiser4/dev

/proc

/sys

now proceed to copy your directories needed over to your reiser4 partition

example

cp -a /bin /reiser4

in that order, but not the dev, proc and system, those are created already, and will fill themselves

i did n ot copy my mounted ntfs over, it came over after reboot

edit your lilo for to boot from the new partition

edit your fstab to include the reiser4 partition

then reboot

should be fine from there

i did once booting into the reiser 4 partition, run lilo from that partition, then rebooted again to make sure good twice

then cleaned off the old section

if questions feel free to pm

Khai