[ATrpms-devel] ivtv-kmdl packages for kernels with JFS support

[Axel Thimm]

Hi Tim,

On Fri, Jun 23, 2006 at 02:13:05PM -0500, Tim Byrne wrote:
> Not sure if you're the right person to ask, so feel free to tell me off.

The lists are better discussion ground.

> I use CentOS (repackaged RHEL).  I'd like to use the ATrpms repository for
> installing MythTV and for the most part this works just fine.
> 
> However, I'd like to use JFS (many MythTV users use JFS or XFS) but Red
> Hat doesn't include support in the kernel for it.  CentOS developers add
> support into a different kernel RPM in their "centosplus" repository.  The
> centosplus kernels add in support for certain things that RedHat removes
> (such as JFS/XFS).

you can build these as external modules, too, and keep the original kernel.

> The problem comes up when I try to use the ivtv-kmdl package which is
> built off of the standard kernels.  Things don't jive.  I either have to
> repackage the kernel RPM or repackage the ivtv-kmdl package.  I'm guessing
> this is difficult for other users who want JFS/XFS support too.
> 
> My question is, do you think the ivtv-kmdl RPMs built at ATrpms could also
> be built against the latest "centosplus" kernel on a regular basis?  Or
> perhaps you might have a great suggestion for me?

Currently even more kernels would kill me. Unless some distributions
are dropped I'm not going to have any spare cycles left. OTOH if
someone jumps in and fully supports a new kernel (testing & user
interaction on centos lists) I wouldn't mind :)

What you can do is try to setup the development environment to create
your own kmdls. Unfortunately under RHEL4 the kernel-devel isn't
enough in most cases, even latest FC kernel-devel are missing kernel
headers that ivtv needs in sibling includes into the v4l/dvb
space. What ATrpms does is effectively starting to build all the
kernels that are to be supported and freezing the configured &
prepared kernel source tree to point kmdl built processes against.

This non-automated step is currently the hardest hurdle to
overcome. Next you use the src.rpm and try to build against that
sources. If it breaks you need to go back and see whether you forgot
something in preparing the kernel sources (like the wrong .config file
for instance). If you iterate long enough you will eventually get
where you want, but it requires some effort.

But first I would check whether ivtv works properly in manual builds
against the kernel you want to use and if that is OK, go for packaging
it.
-- 
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.atrpms.net/pipermail/atrpms-devel/attachments/20060627/2face2fd/attachment.bin