[gentoo-dev] Suggestion: ebuilds linked to kernel upgrade

[gentoo-dev] Suggestion: ebuilds linked to kernel upgrade

[Herbert G. Fischer]

[-- Attachment #1: Type: text/plain, Size: 419 bytes --]

There could be some way to remember users what installed packages need to be
reemerged after a new kernel is installed.

I thought in this ideas:

- Patch kernel's "make" to warn at the end of "make modules_install"
- Warn user after any boot (during init.d stage). This script should detect
the new kernel and warn users if some of the installed ebuilds need to be
reemerged.

What do you think?

Herbert

[-- Attachment #2: Type: text/html, Size: 484 bytes --]

Re: [gentoo-dev] Suggestion: ebuilds linked to kernel upgrade

[Henrik Brix Andersen]

[-- Attachment #1: Type: text/plain, Size: 669 bytes --]

On Wed, Oct 19, 2005 at 11:32:19AM -0200, Herbert G. Fischer wrote:
> There could be some way to remember users what installed packages need to be
> reemerged after a new kernel is installed.
> 
> I thought in this ideas:
> 
> - Patch kernel's "make" to warn at the end of "make modules_install"
> - Warn user after any boot (during init.d stage). This script should detect
> the new kernel and warn users if some of the installed ebuilds need to be
> reemerged.
> 
> What do you think?

I think you should check out sys-kernel/module-rebuild

Regards,
Brix
-- 
Henrik Brix Andersen <brix@gentoo.org>
Gentoo Metadistribution | Mobile computing herd

[-- Attachment #2: Type: application/pgp-signature, Size: 211 bytes --]

Re: [gentoo-dev] Suggestion: ebuilds linked to kernel upgrade

[Herbert G. Fischer]

[-- Attachment #1: Type: text/plain, Size: 793 bytes --]

That's cool.

2005/10/19, Henrik Brix Andersen <brix@gentoo.org>:
>
> On Wed, Oct 19, 2005 at 11:32:19AM -0200, Herbert G. Fischer wrote:
> > There could be some way to remember users what installed packages need
> to be
> > reemerged after a new kernel is installed.
> >
> > I thought in this ideas:
> >
> > - Patch kernel's "make" to warn at the end of "make modules_install"
> > - Warn user after any boot (during init.d stage). This script should
> detect
> > the new kernel and warn users if some of the installed ebuilds need to
> be
> > reemerged.
> >
> > What do you think?
>
> I think you should check out sys-kernel/module-rebuild
>
> Regards,
> Brix
> --
> Henrik Brix Andersen <brix@gentoo.org>
> Gentoo Metadistribution | Mobile computing herd
>
>
>

[-- Attachment #2: Type: text/html, Size: 1123 bytes --]

Re: [gentoo-dev] Suggestion: ebuilds linked to kernel upgrade

[John Myers]

[-- Attachment #1: Type: text/plain, Size: 1238 bytes --]

On Wednesday 19 October 2005 06:36, Henrik Brix Andersen wrote:
> On Wed, Oct 19, 2005 at 11:32:19AM -0200, Herbert G. Fischer wrote:
[snip]
> > - Patch kernel's "make" to warn at the end of "make modules_install"
[snip]
> I think you should check out sys-kernel/module-rebuild
Actually, a combination of these might not be a bad idea.

Something like this (not tested):

if [ -n "$(which module-rebuild 2>/dev/null)" ] ; then
    if [ -n "${AUTO_MODULE_REBUILD}" ] ; then
        echo "Rebuilding external modules:"
        module-rebuild ${MODULE_REBUILD_OPTIONS} rebuild
    else
        echo "You might want to rebuild the following external modules:"
        module-rebuild -XC list | tail -n +2
        echo
        echo "You can use module-rebuild to do that."
        echo "If you want to have your external modules automatically rebuilt"
        echo "when making a kernel's modules_install target, set"
        echo "AUTO_MODULE_REBUILD in your environment. You can set"
        echo "MODULE_REBUILD_OPTIONS to options to pass to module-rebuild."
        echo "(-X for example)"
    fi
else
    echo "You might want to emerge sys-kernel/module-rebuild to keep track of"
    echo "kernel modules you've installed with emerge"
fi

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-dev] Suggestion: ebuilds linked to kernel upgrade

[Herbert G. Fischer]

[-- Attachment #1: Type: text/plain, Size: 1553 bytes --]

Perhaps the modules-update could be extended to detect new kernels and warn
users or automatically update modules. This could also be documented in
Gentoo docs since this is a basic and common problem that almost every
Gentoo user may have.

Thanks for the patch!

2005/10/19, John Myers <electronerd@monolith3d.com>:
>
> On Wednesday 19 October 2005 06:36, Henrik Brix Andersen wrote:
> > On Wed, Oct 19, 2005 at 11:32:19AM -0200, Herbert G. Fischer wrote:
> [snip]
> > > - Patch kernel's "make" to warn at the end of "make modules_install"
> [snip]
> > I think you should check out sys-kernel/module-rebuild
> Actually, a combination of these might not be a bad idea.
>
> Something like this (not tested):
>
> if [ -n "$(which module-rebuild 2>/dev/null)" ] ; then
> if [ -n "${AUTO_MODULE_REBUILD}" ] ; then
> echo "Rebuilding external modules:"
> module-rebuild ${MODULE_REBUILD_OPTIONS} rebuild
> else
> echo "You might want to rebuild the following external modules:"
> module-rebuild -XC list | tail -n +2
> echo
> echo "You can use module-rebuild to do that."
> echo "If you want to have your external modules automatically rebuilt"
> echo "when making a kernel's modules_install target, set"
> echo "AUTO_MODULE_REBUILD in your environment. You can set"
> echo "MODULE_REBUILD_OPTIONS to options to pass to module-rebuild."
> echo "(-X for example)"
> fi
> else
> echo "You might want to emerge sys-kernel/module-rebuild to keep track of"
> echo "kernel modules you've installed with emerge"
> fi
>
>
>

[-- Attachment #2: Type: text/html, Size: 2624 bytes --]

Re: [gentoo-dev] Suggestion: ebuilds linked to kernel upgrade

[Herbert G. Fischer]

[-- Attachment #1: Type: text/plain, Size: 1859 bytes --]

Oops... sorry for the last e-mail. I confess that I did not read your
code-piece before answering. It's exactly what I had in mind (as you saw).

2005/10/19, Herbert G. Fischer <herbert.fischer@gmail.com>:
>
> Perhaps the modules-update could be extended to detect new kernels and
> warn users or automatically update modules. This could also be documented in
> Gentoo docs since this is a basic and common problem that almost every
> Gentoo user may have.
>
> Thanks for the patch!
>
> 2005/10/19, John Myers <electronerd@monolith3d.com>:
> >
> > On Wednesday 19 October 2005 06:36, Henrik Brix Andersen wrote:
> > > On Wed, Oct 19, 2005 at 11:32:19AM -0200, Herbert G. Fischer wrote:
> > [snip]
> > > > - Patch kernel's "make" to warn at the end of "make modules_install"
> >
> > [snip]
> > > I think you should check out sys-kernel/module-rebuild
> > Actually, a combination of these might not be a bad idea.
> >
> > Something like this (not tested):
> >
> > if [ -n "$(which module-rebuild 2>/dev/null)" ] ; then
> > if [ -n "${AUTO_MODULE_REBUILD}" ] ; then
> > echo "Rebuilding external modules:"
> > module-rebuild ${MODULE_REBUILD_OPTIONS} rebuild
> > else
> > echo "You might want to rebuild the following external modules:"
> > module-rebuild -XC list | tail -n +2
> > echo
> > echo "You can use module-rebuild to do that."
> > echo "If you want to have your external modules automatically rebuilt"
> > echo "when making a kernel's modules_install target, set"
> > echo "AUTO_MODULE_REBUILD in your environment. You can set"
> > echo "MODULE_REBUILD_OPTIONS to options to pass to module-rebuild."
> > echo "(-X for example)"
> > fi
> > else
> > echo "You might want to emerge sys-kernel/module-rebuild to keep track
> > of"
> > echo "kernel modules you've installed with emerge"
> > fi
> >
> >
> >
>

[-- Attachment #2: Type: text/html, Size: 3219 bytes --]

Re: [gentoo-dev] Suggestion: ebuilds linked to kernel upgrade

[John Mylchreest]

> 2005/10/19, Herbert G. Fischer <herbert.fischer@gmail.com>:
>         Perhaps the modules-update could be extended to detect new
>         kernels and warn users or automatically update modules. This
>         could also be documented in Gentoo docs since this is a basic
>         and common problem that almost every Gentoo user may have.

module-rebuild shouldn't really have this task. it isn't the right place
to do it. It will of course quite happily do what you need it to do,
rebuild anything which installs a kernel module from portage.
>         
>         2005/10/19, John Myers <electronerd@monolith3d.com>

>                 if [ -n "$(which module-rebuild 2>/dev/null)" ] ;
>                 then 
>                     if [ -n "${AUTO_MODULE_REBUILD}" ] ; then
>                         echo "Rebuilding external modules:"
>                         module-rebuild ${MODULE_REBUILD_OPTIONS}
>                 rebuild
>                     else
>                         echo "You might want to rebuild the following
>                 external modules:" 
>                         module-rebuild -XC list | tail -n +2
>                         echo
>                         echo "You can use module-rebuild to do that."
>                         echo "If you want to have your external
>                 modules automatically rebuilt" 
>                         echo "when making a kernel's modules_install
>                 target, set"
>                         echo "AUTO_MODULE_REBUILD in your environment.
>                 You can set"
>                         echo "MODULE_REBUILD_OPTIONS to options to
>                 pass to module-rebuild." 
>                         echo "(-X for example)"
>                     fi
>                 else
>                     echo "You might want to emerge
>                 sys-kernel/module-rebuild to keep track of"
>                     echo "kernel modules you've installed with
>                 emerge" 
>                 fi
>                 
I don't particular feel comfortable doing this. the only place I can
actually see this being of some use is with the pkg_config since an
ebuild postinst is far too soon, and patching up Kbuild to do this is
far too intrusive (let alone high maintenance).

A possibility (although I wouldnt like to promote it through portage)
would be to have a wrapper/helper script which would do all of this for
you. build-kernel or some such. But then... whats genkernel for right?

- John


-- 
Role:            Gentoo Linux Kernel Lead
Gentoo Linux:    http://www.gentoo.org
Public Key:      gpg --recv-keys 9C745515     
Key fingerprint: A0AF F3C8 D699 A05A EC5C  24F7 95AA 241D 9C74 5515
Web:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x9C745515

-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Suggestion: ebuilds linked to kernel upgrade

[Chris Gianelloni]

[-- Attachment #1: Type: text/plain, Size: 1303 bytes --]

On Wed, 2005-10-19 at 21:44 +0100, John Mylchreest wrote:
> I don't particular feel comfortable doing this. the only place I can
> actually see this being of some use is with the pkg_config since an
> ebuild postinst is far too soon, and patching up Kbuild to do this is
> far too intrusive (let alone high maintenance).
> 
> A possibility (although I wouldnt like to promote it through portage)
> would be to have a wrapper/helper script which would do all of this for
> you. build-kernel or some such. But then... whats genkernel for right?

Actually, genkernel does have the --callback option, which runs an
external command before finalizing the build.  We use it for building
external modules and packages that require a configured kernel when
building the releases, but I think adding an option to genkernel
wouldn't be bad to do this for you.  We could add a command-line switch
to genkernel to automatically rebuild any external modules after it has
built the kernel.  We could use something like --autorebuild.  You could
then do something like "genkernel --autorebuild all" to build your new
kernel and automatically rebuild all of your external modules.

-- 
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
Games - Developer
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] Suggestion: ebuilds linked to kernel upgrade

[Jan Kundrát]

[-- Attachment #1: Type: text/plain, Size: 444 bytes --]

On Wednesday 19 of October 2005 20:56 Herbert G. Fischer wrote:
> Perhaps the modules-update could be extended to detect new kernels and warn
> users or automatically update modules. This could also be documented in
> Gentoo docs since this is a basic and common problem that almost every
> Gentoo user may have.

http://www.gentoo.org/doc/en/kernel-upgrade.xml#doc_chap6

Cheers,
-jkt

-- 
cd /local/pub && more beer > /dev/mouth

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] Suggestion: ebuilds linked to kernel upgrade

[John Mylchreest]

On Wed, 2005-10-19 at 17:31 -0400, Chris Gianelloni wrote:
> Actually, genkernel does have the --callback option, which runs an
> external command before finalizing the build.  We use it for building
> external modules and packages that require a configured kernel when
> building the releases, but I think adding an option to genkernel
> wouldn't be bad to do this for you.  We could add a command-line switch
> to genkernel to automatically rebuild any external modules after it has
> built the kernel.  We could use something like --autorebuild.  You could
> then do something like "genkernel --autorebuild all" to build your new
> kernel and automatically rebuild all of your external modules.

My thoughts exactly. And I'm sure a welcome addition.

-- 
Role:            Gentoo Linux Kernel Lead
Gentoo Linux:    http://www.gentoo.org
Public Key:      gpg --recv-keys 9C745515     
Key fingerprint: A0AF F3C8 D699 A05A EC5C  24F7 95AA 241D 9C74 5515
Web:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x9C745515

-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Suggestion: ebuilds linked to kernel upgrade

[Chris Gianelloni]

[-- Attachment #1: Type: text/plain, Size: 982 bytes --]

On Thu, 2005-10-20 at 18:19 +0100, John Mylchreest wrote:
> On Wed, 2005-10-19 at 17:31 -0400, Chris Gianelloni wrote:
> > Actually, genkernel does have the --callback option, which runs an
> > external command before finalizing the build.  We use it for building
> > external modules and packages that require a configured kernel when
> > building the releases, but I think adding an option to genkernel
> > wouldn't be bad to do this for you.  We could add a command-line switch
> > to genkernel to automatically rebuild any external modules after it has
> > built the kernel.  We could use something like --autorebuild.  You could
> > then do something like "genkernel --autorebuild all" to build your new
> > kernel and automatically rebuild all of your external modules.
> 
> My thoughts exactly. And I'm sure a welcome addition.

Bug #109941

-- 
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
Games - Developer
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]