Compil IPCop with last stable Kernel 3.3.2

Hello,I am newcomer  in this mailing list and my english is'nt the best one ! Now i can begin :)I should like to compil IPCop with the last stable Kernel : 3.3.2 (from http://kernel.org/).So for that I did :  - Usual process to compile (http://sourceforge.net/apps/trac/ipcop/wiki/BuildingHowToV2)  - The uppgrade of the lfs (download link and checksum) :    ./trunk/lfs/linux    ./trunk/lfs/linux-headersSo the "./make.sh prefetch" worked well .But I got a problem in "./make.sh build" : The compil blocked at  "udev". And I didn't find the way to solve it...The error from log is :*****************************extras/v4l_id/v4l_id.c:31:28: error: linux/videodev.h: No such file or directoryextras/v4l_id/v4l_id.c: In function 'main':extras/v4l_id/v4l_id.c:42: error: storage size of 'v1cap' isn't knownextras/v4l_id/v4l_id.c:85: error: 'VIDIOCGCAP' undeclared (first use in this function)extras/v4l_id/v4l_id.c:85: error: (Each undeclared identifier is reported only onceextras/v4l_id/v4l_id.c:85: error: for each function it appears in.)make[3]: *** [extras/v4l_id/v4l_id.o] Error 1make[3]: *** Waiting for unfinished jobs....udev/udev-watch.c: In function 'udev_watch_begin':udev/udev-watch.c:124: warning: ignoring return value of 'symlink', declared with attribute warn_unused_resultudev/udev-event.c: In function 'udev_event_apply_format':udev/udev-event.c:377: warning: ignoring return value of 'asprintf', declared with attribute warn_unused_resultmake[2]: *** [all-recursive] Error 1make[1]: *** [all] Error 2make[1]: Leaving directory `/usr/src/udev-166'make: *** [/usr/src/files_i486/02_base/udev-166] Error 2*****************************After that I did some search and I find your post (here below).My question is :Is it possible to have the last stable Kernel and how ?Or is it not yet possible ?Thank you !Xel******************************************************************************************************************************Thinking more, I am unsure kmod should be on 2.1 release.

There has been some kernel changes related to kmod.
It is unlikely now those changes will be backported to kernel 3.0.

We should be able to live with last udev version before kmod,
module-init-tools-3.16 like everyone else do actually.
kmod should only be a target for us when switching to the next kernel after
3.0.x.

Gilles
***************************************************************What are the list of issues to change to the latest LINUX kernel?

Those of you who are not familiar with kmod here's an explanation from the
2ed of the LINUX device driver book from O'Reilly ...
http://www.xml.com/ldd/chapter/book/ch11.html#t1

*..."The idea behind kmod is simple, yet effective. Whenever the kernel
tries to access certain types of resources and finds them unavailable, it
makes a special kernel call to the kmod subsystem instead of simply
returning an error. If kmod succeeds in making the resource available by
loading one or more modules, the kernel continues working; otherwise, it
returns the error..."*


Here's more information from IBM Developer-Work about LINUX Kernel Modules,
LKMs...
http://ibm.co/8VOn2k

...or it is KMOD <http://www.kmod.com/main.html>, a radio station 97.5 in
Tulsa, Oklahoma USA whose racy front page tells you they know nothing about
the LINUX kernel ... and for that matter not much of anything.

Cheers,
John S Wolter
"We love LINUX we just have a funny way of saying it."


On Sun, Mar 4, 2012 at 9:10 AM, Gilles Espinasse <g.esp@...> wrote:

> Thinking more, I am unsure kmod should be on 2.1 release.
>
> There has been some kernel changes related to kmod.
> It is unlikely now those changes will be backported to kernel 3.0.
>
> We should be able to live with last udev version before kmod,
> module-init-tools-3.16 like everyone else do actually.
> kmod should only be a target for us when switching to the next kernel after
> 3.0.x.
>
> Gilles
>
>
>
> ------------------------------------------------------------------------------
> Virtualization & Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> _______________________________________________
> IPCop-devel mailing list
> IPCop-devel@...
> https://lists.sourceforge.net/lists/listinfo/ipcop-devel
>



-- 
Cheers
John S Wolter***************************************************************On 2012-03-04 15:10, Gilles Espinasse wrote:
> Thinking more, I am unsure kmod should be on 2.1 release.

I tend to agree.

> There has been some kernel changes related to kmod.
> It is unlikely now those changes will be backported to kernel 3.0.
>
> We should be able to live with last udev version before kmod,
> module-init-tools-3.16 like everyone else do actually.
> kmod should only be a target for us when switching to the next kernel after
> 3.0.x.

I found changing udev to latest version requires (at least, more 
certainly to come) newer linux-headers, adding /run, make changes in our 
handling of networking interfaces since persistent net devices are gone. 
Our initramfs still does not properly boot after all that fixed.
So I'd be quite happy to stick with "older" udev version, and save all 
those changes to a later day.


Olaf***************************************************************Something we could consider is dropping floppy disk installation.


Olaf***************************************************************----- Original Message ----- 
From: john s wolter
To: IPCOP devel
Sent: Sunday, March 04, 2012 5:53 PM
Subject: Re: [IPCop-devel] kmod not for 2.1


> What are the list of issues to change to the latest LINUX kernel?
>
This is not our plan to switch to linux-3.2 or 3.3 yet.
The reason to change from 2.6.32 to 3.0 is that 2.6.32 start to be old.
So there is a decline in actual hardware support. We had to add some
external driver update again.
As Greg KH announced he will no more release 2.6.32 stable update (he will
probably be replaced), this is a good timing to switch.

Gilles******************************************************************************************************************************

------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second 
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev

_______________________________________________
IPCop-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ipcop-devel