Re: [Netnice-kernels] Linux Kernel

[Takashi O. <ta...@cs...>]

hi kartikey!

thanks for the patch. how're you feeling now?? 

i don't know why the code on the CVS isn't the latest one,
but, that is okay.

i also tried the patch, and got the same error as Scott did.

> patch: **** malformed patch at line 14: };

what option do i need to give to the patch command??
i'm using patch 2.5.4, and i've tried -p0, -p1, -p2, -p3
options in the target directory, but, they didn't work.

any thoughts?

thanks!

-- taka

kartikey bhatt wrote:
> 
> hello,
> 
> may be here comes the answer to all your
> questions. this is the patch that i worked
> on and where everything is in place. it
> compiles neatly without any modifications.
> just apply it against fresh 2.6.7 tree.
> and from make menuconfig select
> drivers->networking options->Netnice for Linux.
> 
> regards
> --kartikey
> 
> >From: Takashi Okumura <ta...@cs...>
> >To: Scott Brumbaugh <sco...@ve...>
> >CC: net...@li...
> >Subject: Re: [Netnice-kernels] Linux Kernel
> >Date: Wed, 06 Oct 2004 13:59:18 -0400
> >
> >hello,
> >
> >Scott Brumbaugh wrote:
> > >
> > > > thanks for the message. i realized that vif_free() and some of
> > > > other functions are still incomplete. i don't know why it doesn't
> > > > compile, since i've checked that it compiled (in india!)...
> > > >
> > >
> > > >From the CVS the files vif_input.c, vif_output.c, and vif_subr.c will
> > > pass through the compiler and an object file will be produced.
> > > However, the conditional at the top:
> > >
> > > #ifdef CONFIG_NETNICE
> > >
> > > will prevent any of the contained functions from being compiled.  So
> > > the object file produced is really not of any use because it contains
> > > no executable code.  The definition of CONFIG_NETNICE is obtained by
> > > including linux/config.h and the #ifdef CONFIG_NETNICE must occur
> > > _after_ linux/config.h has been included.  When this is done and the
> > > functions in the files actually pass through the compiler the errors
> > > occur.
> > >
> > > As for socket.c some of the variables passed into the functions within
> > > the sections delimited by CONFIG_NETNICE use variables that are not
> > > found anywhere in the file.
> >
> >okay. i took a look at the files, and now i understand. the last case
> >is the easiest; it is using a pointer, "struct proc *p", although linux
> >doesn't have that variable in the socket accept function. maybe you're
> >right. but, still i think it is relatively easy to fix...
> >
> > > Also, the Kconfig (kernel configuration) setup is not complete and I
> > > needed to add this so I could compile.
> > >
> > > If this worked before I imagine that there is a later version missing
> > > from your CVS.
> >
> >i checked that the files on the CVS is the ones i got from kartikey.
> >
> >kartikey, do you have newer files? or, any comments??
> >
> >thanks,
> >
> >-- taka
> >
> >
> >
> >-------------------------------------------------------
> >This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> >Use IT products in your business? Tell us what you think of them. Give us
> >Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
> >http://productguide.itmanagersjournal.com/guidepromo.tmpl
> >_______________________________________________
> >Netnice-kernels mailing list
> >Net...@li...
> >https://lists.sourceforge.net/lists/listinfo/netnice-kernels
> 
> _________________________________________________________________
> All the news that matters. All the gossip from home.
> http://www.msn.co.in/NRI/ Specially for NRIs!
> 
>   --------------------------------------------------------------------------------
> 
>                             Name: netnice-linux.diff
>    netnice-linux.diff       Type: Plain Text (text/plain)
>                         Encoding: 8bit