[Planetlab-devel] bootcd_v3 for wireless/mesh myplc

[Marc E. Fiuczynski]

Hello Winson,

VNET is a module used to enforce network isolation between slices.  I don't
think it is strictly required within a private PlanetLab setting.  Moreover,
VNET requires a few changes to the kernel sources for it to function
correctly.

I don't believe you'll need PPTP/GRE support.  So I suggest you just punt on
this for now.

Looking for the prior email you've sent that summarizes your problems with
device mapper etc.  It is too bad that you have to jump through these hoops
because you are using device drivers that only work with 2.6.9.  For
example, I am not sure what the status is of kexec support in 2.6.9.  For
our old 2.6.10 based kernels I remember we had to pull in a kexec patch for
it to work properly.  So there are a number of possible issues you might be
running into.  No chance you could port your drivers to our 2.6.12 or
2.6.17/18 kernels, right?!  This might actually be less work and more
fruitful compared to backporting stuff that you'll eventually throw out
anyway.

Marc


> -----Original Message-----
> From: Chan, Winson C [mailto:winson.c.chan at intel.com]
> Sent: Wednesday, November 22, 2006 2:18 PM
> To: Marc E. Fiuczynski
> Subject: RE: [Planetlab-devel] bootcd_v3 for wireless/mesh myplc
>
>
> Marc,
>
> I still have the same error after I enable the device mapper and EXT3 in
> the kernel config.  Also, I notice that there's a VNET and PPTP/GRE
> modules that I'm missing in my kernel.  Is that something I can download
> from PlanetLab and compile into mine?
>
> Thanks.
> Winson