[prev in list] [next in list] [prev in thread] [next in thread] 

List:       evms-devel
Subject:    [Evms-devel] Re: Questions about evms/dm patches with Debian 2.6
From:       Ross Boylan <RossBoylan () stanfordalumni ! org>
Date:       2004-06-25 2:31:41
Message-ID: 20040625023141.GG1920 () wheat ! boylan ! org
[Download RAW message or body]

On Mon, Jun 21, 2004 at 10:44:37PM -0700, Ross Boylan wrote:
> I'm about to try building my first 2.6 kernel with EVMS on Debian,
> using the Debianized kernel-source-2.6.6 and kernel-patch-evms.
> 
> As usual, I'm a bit confused :)
> 
> Short version: will the following work?
> 1. expand Debianized kernel-source-2.6.6
> 2. apply
> ftp://sources.redhat.com/pub/dm/patches/2.6-unstable/2.6.7-rc2/2.6.7-rc2-udm1.tar.bz2
> to it (NB: patch says 2.6.7, kernel source 2.6.6)

Nope.  The patches don't apply cleanly against the Debianized 2.6.6
kernel.  My suspicion is it's a 2.6.6 vs 2.6.7 issue, but I don't
know.

In particular,
cat ../2.6.7-rc2-udm1/*.patch | patch -p1
fails on drivers/md/dm.c

The problem seems to be that the patch is expecting 
  static struct block_device_operations dm_blk_dops = {
around line 1083, while the actual file has
struct block_device_operations dm_blk_dops = {
i.e., no static.

My guess is the static was removed in 2.6.7, so that removing it would
be appropriate, but I'm not too enthusiastic about making fairly blind
code changes to the kernel.

> 3. make-kpkg, specifying that kernel-path-evms should be applied.
> 


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Evms-devel mailing list
Evms-devel@lists.sourceforge.net
To subscribe/unsubscribe, please visit:
https://lists.sourceforge.net/lists/listinfo/evms-devel
[prev in list] [next in list] [prev in thread] [next in thread]