Re: 2.4.32pre with Kernel 2.6.12?

"Holger Jahn" <[email protected]>
Newsgroups gmane.linux.enbd.general
Message-ID <[email protected]>
Servus Peter,

> I don't use any kernel more recent than that (though perhaps I'll
> make an effort today to get a 2.6.12 kernel working on my smp 
> machine).

That'll be just sweet!

> BTW, is there a 2.6.12 kernel? Teh 2.6.11.* kernels had another
> number on!

Err, at least that's the one I downloaded from kernel.org some
moons ago.

Here's what I have done to get ENBD 2.4.32pre running on kernel
2.6.12:

1) tar xzvf enbd-2.4.32pre.tgz

2) cd nbd-2.4.32/
    cp ./kernel/linux-2.6.x/include/linux/*.h /usr/include/linux/

3) cd /usr/src/linux
   patch -p1 -i ~/nbd-2.4.32/kernel/patches/enbd-2.6.8.pat

4) One patch gets rejected, therefore I manually added this
   line to 'drivers/Makefile' (NOTE: It's 2 TABS in the middle!):

   obj-$(CONFIG_ENBD)        += block/enbd/

5) Then I did a menuconfig, went to Device Drivers => Block Devices,
   checked 'Enhanced network block device' and mark the two options
   below it as modules (<M>): 'Enhanced network block device 
   driver', 'Enhanced network block device remote ioctl support'.

6) Since this one failed to compile, I removed the 2nd arg
   of the funtion call to __invalidate_device. Edit this file:

   vi +3228 drivers/block/enbd/enbd_base.c

   Removes the ', 0', so that the line looks like so:

   __invalidate_device(lo->inode->i_bdev);

7) Then I compiled the new kernel and modules:

    make
    make modules_install

    Installed the new kernel.

8) Rebooted.

9) cd nbd-2.4.32/
   make config
   make         (=> yes, later on I used 'utils' as well ;-))
   cd nbd
   ./configure
   make
   cd ..
   make test    
   make install

'Make test' showed some errors at the very end of the tests (yes,
I know, but please read on), the initial tests of shoveling data
across client and server worked, however.

I was able to load the modules on both of my boxes, 'dmesg' shows
no errors.

Then I used 'enbd-server 1099 -i myfoo /dev/sda1' to export one of 
my partitions (tried a plain file later as well with same result),
which started up fine.

But when I used 'enbd-client 1099 -i myfoo /dev/nda' it spat out
a bunch of error messages (I am at work right now, have to test
at home tonight again), like 'Warning: only 0/1B read' and 
'Only half line read'. However, it always happened after negot.
the blocksize, which was transferred correctly, so it seems my 
installation is only partially broken (there's hope! ;-). Then 
the client retried a couple of times and finally gave up.

So did I... ;-)

Sorry for being unprecise; I just thought there could be a HOWTO
for 2.6.12. Will eb very precise from now on... promised! :-)

Cheers && Heaps of thanks for your help!

Holger

---- Original Message ----
From: [email protected]
To: [email protected]
Subject: Re: [ENBD] 2.4.32pre with Kernel 2.6.12?
Date: Wed, 20 Jul 2005 14:18:37 +0200 (MET DST)

>"Also sprach Holger (Woosh):"
>> I have spent today with the unsucessful attempt to get 2.4.32pre
>> up and running on a SMP system with kernel 2.6.12.
>
>You'll have to tell me what the problem is. Does the 2.6.8 patch not
>apply? 
>
>> Before I jump into greater detail and error messages,
>
>The detail is all that is needed :(.
>
>> I'd like
>> to learn whether some one out there has had more luck (or brains)
>
>It's not a question of luck, but of saying what you did, showing what
>the results are; the first error is all I need to see. When I see it
>I
>can tell you what the problem is. 
>
>> A short "Do this - Do not do that" post would be more than
>appreciated!
>
>There is no such thing, any more than there is a short do this do
>that
>method to winning a war. I would say
>
> "type 'make'"
>
>And let me know  what happens!
>
>Peter
>_______________________________________________
>ENBD mailing list
>[email protected]
>http://lists.community.tummy.com/mailman/listinfo/enbd
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.