crypto-core-modules and 2.6 - Debian

This is a discussion on crypto-core-modules and 2.6 - Debian ; Frans, I noticed you added a crypto-core-modules udeb that contains blkcipher. This module has been renamed to crypto_blkcipher in 2.6.25. What's the best way to handle this in kernel-wedge? Modify crypto-core-modules so it looks like this: blkcipher ? crypto_blkcipher ? ...

+ Reply to Thread
Results 1 to 8 of 8

Thread: crypto-core-modules and 2.6

  1. crypto-core-modules and 2.6

    Frans, I noticed you added a crypto-core-modules udeb that contains
    blkcipher. This module has been renamed to crypto_blkcipher in
    2.6.25. What's the best way to handle this in kernel-wedge? Modify
    crypto-core-modules so it looks like this:

    blkcipher ?
    crypto_blkcipher ?

    or simply replace blkcipher with crypto_blkcipher when we're moving
    to 2.6.25?

    --
    Martin Michlmayr
    http://www.cyrius.com/


    --
    To UNSUBSCRIBE, email to debian-boot-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  2. Re: crypto-core-modules and 2.6

    And one more issue with 2.6.25. I get the following:

    kernel-wedge find-dups 2.6.25-1-orion5x
    debian/crypto-modules-2.6.25-1-orion5x-di lib/modules/2.6.25-1-orion5x/kernel/crypto/crypto_blkcipher.ko
    debian/crypto-core-modules-2.6.25-1-orion5x-di lib/modules/2.6.25-1-orion5x/kernel/crypto/crypto_blkcipher.ko
    debian/md-modules-2.6.25-1-orion5x-di lib/modules/2.6.25-1-orion5x/kernel/crypto/crypto_blkcipher.ko
    debian/crypto-modules-2.6.25-1-orion5x-di lib/modules/2.6.25-1-orion5x/kernel/crypto/crypto_blkcipher.ko
    some modules are in more than one package

    How about this when we move to 2.6.25:

    Index: package-list
    ================================================== =================
    --- package-list (revision 53285)
    +++ package-list (working copy)
    @@ -232,7 +232,7 @@
    This package contains the NFS filesystem module for the Linux kernel.

    Package: md-modules
    -Depends: kernel-image
    +Depends: kernel-image, crypto-core-modules
    Priority: extra
    Description: RAID and LVM support
    This package contains RAID and LVM modules for the Linux kernel.
    @@ -348,7 +348,7 @@
    and wireless networking (WEP).

    Package: crypto-modules
    -Depends: kernel-image
    +Depends: kernel-image, crypto-core-modules
    Priority: extra
    Description: crypto modules
    This package contains crypto modules.

    --
    Martin Michlmayr
    http://www.cyrius.com/


    --
    To UNSUBSCRIBE, email to debian-boot-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  3. Re: crypto-core-modules and 2.6

    On Saturday 10 May 2008, Martin Michlmayr wrote:
    > Frans, I noticed you added a crypto-core-modules udeb that contains
    > blkcipher. This module has been renamed to crypto_blkcipher in
    > 2.6.25. What's the best way to handle this in kernel-wedge? Modify
    > crypto-core-modules so it looks like this:
    >
    > blkcipher ?
    > crypto_blkcipher ?


    This is the correct solution.

    > or simply replace blkcipher with crypto_blkcipher when we're moving
    > to 2.6.25?


    No. That would make it impossible to build udebs for earlier kernels.

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.6 (GNU/Linux)

    iD8DBQBIJXAKgm/Kwh6ICoQRAr3AAJ9GY9VmbJBApmk6FRM+tQoOe3x69QCfYhar
    yzL3Gnzzf+RKtRaXz7uuRx8=
    =9r4O
    -----END PGP SIGNATURE-----


  4. Re: crypto-core-modules and 2.6

    * Frans Pop [2008-05-10 11:57]:
    > Same basically goes for the first: if all arches need it it is fine
    > to do it in kernel-wedge. And if that is the case, the above becomes
    > rather academic and should be done anyway.


    How can we find out whether all arches need it?

    --
    Martin Michlmayr
    http://www.cyrius.com/


    --
    To UNSUBSCRIBE, email to debian-boot-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  5. Re: crypto-core-modules and 2.6

    On Saturday 10 May 2008, Martin Michlmayr wrote:
    > How about this when we move to 2.6.25:
    >
    > Index: package-list
    > ================================================== =================
    > --- package-list (revision 53285)
    > +++ package-list (working copy)
    > @@ -232,7 +232,7 @@
    > This package contains the NFS filesystem module for the Linux kernel.
    >
    > Package: md-modules
    > -Depends: kernel-image
    > +Depends: kernel-image, crypto-core-modules
    > Priority: extra
    > Description: RAID and LVM support
    > This package contains RAID and LVM modules for the Linux kernel.
    > @@ -348,7 +348,7 @@
    > and wireless networking (WEP).
    >
    > Package: crypto-modules
    > -Depends: kernel-image
    > +Depends: kernel-image, crypto-core-modules
    > Priority: extra
    > Description: crypto modules
    > This package contains crypto modules.


    The last is already done in the "override" package-list inside
    linux-kernel-di-i386-2.6 and some others because it was not needed
    generally (but only for arches having nic-wireless-modules).
    It should only be moved to kernel-wedge if it now _is_ needed generally, but
    then all individual kernel packages will also need to have
    crypto-core-modules added below their modules directory.

    Same basically goes for the first: if all arches need it it is fine to do it
    in kernel-wedge. And if that is the case, the above becomes rather academic
    and should be done anyway.

    Cheers,
    FJP

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.6 (GNU/Linux)

    iD8DBQBIJXF6gm/Kwh6ICoQRAjr6AJ40i/KgBXfuntUHJT/3gSSC95kbYgCZAar/
    bKavLAwCqR8PjkXN4fCQmE8=
    =We2l
    -----END PGP SIGNATURE-----


  6. Re: crypto-core-modules and 2.6

    On Saturday 10 May 2008, Martin Michlmayr wrote:
    > * Frans Pop [2008-05-10 11:57]:
    > > Same basically goes for the first: if all arches need it it is fine
    > > to do it in kernel-wedge. And if that is the case, the above becomes
    > > rather academic and should be done anyway.

    >
    > How can we find out whether all arches need it?


    By building them.

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.6 (GNU/Linux)

    iD8DBQBIJXlMgm/Kwh6ICoQRAs35AJ4vulWg8suiVvL1muFGEfbeFnZSJACcCSb8
    EXmbHqNB57WTtZx0sGKmRKY=
    =DIkW
    -----END PGP SIGNATURE-----


  7. Re: crypto-core-modules and 2.6

    Martin Michlmayr writes:

    > Frans, I noticed you added a crypto-core-modules udeb that contains
    > blkcipher. This module has been renamed to crypto_blkcipher in
    > 2.6.25. What's the best way to handle this in kernel-wedge? Modify
    > crypto-core-modules so it looks like this:
    >
    > blkcipher ?
    > crypto_blkcipher ?


    Use this way so we keep compatibility.

    --
    O T A V I O S A L V A D O R
    ---------------------------------------------
    E-mail: otavio@debian.org UIN: 5906116
    GNU/Linux User: 239058 GPG ID: 49A5F855
    Home Page: http://otavio.ossystems.com.br
    ---------------------------------------------
    "Microsoft sells you Windows ... Linux gives
    you the whole house."


    --
    To UNSUBSCRIBE, email to debian-boot-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  8. Re: crypto-core-modules and 2.6

    Martin Michlmayr writes:

    > And one more issue with 2.6.25. I get the following:
    >
    > kernel-wedge find-dups 2.6.25-1-orion5x
    > debian/crypto-modules-2.6.25-1-orion5x-di lib/modules/2.6.25-1-orion5x/kernel/crypto/crypto_blkcipher.ko
    > debian/crypto-core-modules-2.6.25-1-orion5x-di lib/modules/2.6.25-1-orion5x/kernel/crypto/crypto_blkcipher.ko
    > debian/md-modules-2.6.25-1-orion5x-di lib/modules/2.6.25-1-orion5x/kernel/crypto/crypto_blkcipher.ko
    > debian/crypto-modules-2.6.25-1-orion5x-di lib/modules/2.6.25-1-orion5x/kernel/crypto/crypto_blkcipher.ko
    > some modules are in more than one package


    crypto-modules needs to depends on crypto-core-modules

    Besides that, take a look if there's not override in the package. I
    guess there's one avoiding md-modules to depends of crypto-core-modules.

    --
    O T A V I O S A L V A D O R
    ---------------------------------------------
    E-mail: otavio@debian.org UIN: 5906116
    GNU/Linux User: 239058 GPG ID: 49A5F855
    Home Page: http://otavio.ossystems.com.br
    ---------------------------------------------
    "Microsoft sells you Windows ... Linux gives
    you the whole house."


    --
    To UNSUBSCRIBE, email to debian-boot-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

+ Reply to Thread