Re-sending with output file renamed to patch.out.txt - the mailing list processor didn't like having a .out file attached...

-steve j
Steve Jacobson
Support Manager
SourceLabs, Inc.
steve@sourcelabs.com
(206) 322-0099 x110


Steve Jacobson wrote:

Thanks Mike,

I hadn't captured the patch output originally, so I cleaned up, and re-installed the source and re-patched.  The output is attached here as patch.out, but a cursory read-through says every patch applied OK.

Other answers to your questions are in-line.

Thanks!

-steve j

Steve Jacobson
Support Manager
SourceLabs, Inc.
steve@sourcelabs.com
(206) 322-0099 x110
  


michael chang wrote:
On 10/7/05, Steve Jacobson <steve@sourcelabs.com> wrote:
  
1) Start with clean install of centOS 4.1 x86_64 version
2) Install kernel sources from centOS distro
3) Patch sources:
   a) in /usr/src/linux-2.6.9-11.EL
   b) run: patch -p0 < reiser4-for-2.6.9-4
NOTE - is this my complete problem right here?   Are the differences
between 2.6.9-11 and 2.6.9-4 significant enough to account for this?
    

In theory, they shouldn't be... but are all the hunks applying
correctly?  If any fail, they must be applied by hand, or something
breaks.
  
None of the patches appeared to fail.    See the attached patch.out file.
  
4) make menuconfig - enabling reiser4 as a module
    

What happens when done builtin?  Also, do you have something like 4k
stacks built in that weren't supported in the 2.6.9 patch?
  

I'm not sure.  The only option I touched in the config that wasn't a default was to make sure that the reiser4 module was being built, and that it was a module.
  
5) make
6) make binrpm-pkg
7) Install the resultant RPM
8) run mkinitrd /boot/initrd-2.6.9-11.ELcustom.img 2.6.9011.ELcustom
9) Update grub.conf:
   title CentOS-4 x86_64 Resier (2.6.9-11.ELcustom)
        root (hd0,0)
        kernel /vmlinuz-2.6.9-11.ELcustom ro root=LABEL=/1
        initrd /initrd-2.6.9-11.ELcustom.img
10) reboot, and select the custom kernel
11) Run mkfs.reiser4
    

Where the heck does this come from?  I didn't see you install any resier4 tools.

What version of resier4 tools are you using?

  
You're right - I skipped a couple of steps that I went through here.  I'm running reiser4progs-1.0.5, and libaal-1.0.5.  I configured and built and installed each of these with no errors.  The mkfs.reiser4 also ran with no errors.
12) run modprobe reiser4, or just try to mount the new file system
    

--
~Mike
 - Just my two cents
 - No man is an island, and no man is unable.