Re: ENBD Issues with client crash / weird errors....

"Also sprach Jonathan Carron:"
> > Eh? NO - don't invent procedures! Just do what it says. Read the
> > README.
> 
> cat /nbd-2.4.32/README | grep -i "patch"  

No no - don't do that! Just read it!


> <nothing>
> ?

Not surprising. Why do you think the word "patch" should appear?
Puzzling.


> cat /nbd-2.4.32/INSTALL | grep -i "patch"  
> <nothing> 
> ?

Not surprising.

> I see in INSTALL
> "
> BUILD instructions
> 
> It should be sufficient to type "make config all" in this directory.

Indeed. Please do that. (I thought it was just "make"). You might want
to point the 2.6.x link in the patches directory to a patchset closer
to your actual kernel first, but you can try it just as it is.  The
patches are pretty generic.

> But check first
> 
>   0) that you have the kernel sources installed

Please do!

> 
>   1) that the kernel source directory LINUXDIR in the Makefile is correct

Please do! 

> 
>   2) that you (a) set SMP=1 in the Makefile if your target kernel is SMP;
>      and (b) that there isn't an old config.cache hanging around in the nbd
>      subdirectory when you run the make config.

But read the README!

> "..... nothing about patches

I would hope not.

> > Not reading the instructions.
> 
> What instructions ?!!?

The ones you printed above, for a start. Please just follow them. If
you get into difficulty, please tell me. I'll quote the README:

  HOW TO MAKE THE MODULE

     Edit the Makefile in this directory and maybe change LINUXDIR to
     point to the kernel source for your target kernel, and type
    "make".



> DELL doc # cat DIARY  |grep -i "patch"
>   was the xfs patch that I applied.

Why are you doing all this?


> DELL doc # pwd
> /root/nbd-2.4.32/nbd/doc
> DELL doc # cat PROTOCOL | grep -i "patch"
> 
> 
> Its not that im not looking, I've read the files & docs with that I
> have , there is nothing here that is telling me what I need to do to
> patch.

Nothing. Why do you think you do? It's like watching somebody who has a
fixed idea in his head and rejects all the evidence and all the notices
screaming at him that it is not so in favour of retaining that fixed
idea!

Just read the instructions and carry them out :-). You only have to
type "make". If that doesn't work, point the symlink in the patches
directory to something closer to your kernel. I think the names are
explanatory a¤npugh.

Peter