Re: Discussion: New feature for source packages
On Wed, Sep 16, 2009 at 01:11:07AM +0200, Luca Niccoli wrote: 2009/9/16 Russ Allbery r...@debian.org: If there were a document of how to do automated module builds using triggers or a kernel hook, I'd be happy to try that as well. I tried to set up a kernel hook with the script I attached before, but failed. If run by the kernel package postinst, m-a can't get the lock on /var/lib/dpkg/lock, since it's already being used by the package manager installing the kernel, so it either fails the prepare stage or can't install the compiled packages. The same would go with triggers, I guess. Wasn't there a special way to defer a package installation within maintainer scripts ? Or is my recollection bad ? Mike -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Discussion: New feature for source packages
2009/9/14 Hans-J. Ullrich hans.ullr...@loop.de: Problem: Whenever I upgrade to a new kernelversion, or there are new versions of kernel-modules or other packages, which are only available in source-code, it is necessary to build the new versions manually. This is rather annoying and it might be a problem for not experienced users. With module-assistant comes a script that does almost what you want, you just need to make it check for an argument, and add -l $1 to m-a's command line. It's at /usr/share/doc/module-assistant/examples/non-interactive-auto-update.sh Drop the script in /etc/kernel/postinst.d/ and it should build every module that you have unpacked in /usr/src for the new kernel Maybe this could be added to m-a documentation, with a drop-and-use script? Cheers, Luca P.S. For the sake of clarity I attached the modified script, it's very short. I didn't try it though. build-modules Description: Binary data
Re: Discussion: New feature for source packages
Am Dienstag 15 September 2009 schrieb Luca Niccoli: Luca P.S. For the sake of clarity I attached the modified script, it's very short. I didn't try it though. Hi Luca, just to make it clear: It is not the problem, how I can solve this problem! This problem I can easy solve with a little shell script. But there are lots of unexperienced users, which are not able to script themselve. They are just users. For those people I am looking for a solution. Well, of course, there is DKMS, but DKMS seems only be made for kernel modules. It is greart anyway, and a good help. But what with non-kernel- modules? My suggestion was, to implement a new option into postinst as default. Maybe the change will be accepted? We will see Best regards Hans -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Discussion: New feature for source packages
Le mardi 15 septembre 2009 à 11:57 +0200, Hans-J. Ullrich a écrit : Well, of course, there is DKMS, but DKMS seems only be made for kernel modules. It is greart anyway, and a good help. But what with non-kernel- modules? Fortunately there is not too much software with an ABI as badly maintained as the kernel’s. -- .''`. Josselin Mouette : :' : `. `' “I recommend you to learn English in hope that you in `- future understand things” -- Jörg Schilling signature.asc Description: Ceci est une partie de message numériquement signée
Re: Discussion: New feature for source packages
2009/9/15 Hans-J. Ullrich hans.ullr...@loop.de: Hi Luca, just to make it clear: It is not the problem, how I can solve this problem! This problem I can easy solve with a little shell script. But there are lots of unexperienced users, which are not able to script themselve. They are just users. For those people I am looking for a solution. That's why I proposed to ship the script in examples: we could say in the documentation that if the user wants automatic building he just need to copy it in /etc. An unexperienced person needs to read m-a manual anyway, and copying a file is something I expect a debian user to be able to do. The alternative could be to ship script in /etc/kernel/postinst.d to be activated via a /etc/default/ configuration file. My suggestion was, to implement a new option into postinst as default. Maybe the change will be accepted? We will see IMHO, building and installing kernel modules without user intervetion isn't a sensible choice, you can do a lot of harm that way... Cheers, Luca P.S. Sorry Hans, i keep answering to the wrong address -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Discussion: New feature for source packages
[Hans-J. Ullrich] DKMS seems only be made for kernel modules. It is greart anyway, and a good help. But what with non-kernel- modules? Can you give an example? -- Peter Samuelson | org-tld!p12n!peter | http://p12n.org/ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Discussion: New feature for source packages
Am Dienstag 15 September 2009 schrieb Peter Samuelson: [Hans-J. Ullrich] DKMS seems only be made for kernel modules. It is greart anyway, and a good help. But what with non-kernel- modules? Can you give an example? Hello Peter! No, sorry, I cannot. I looked at the documentation and felt it a little bit too complicated for normal users. It is not the thing, I imagined. Although, it might work for other people. Hans -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Discussion: New feature for source packages
Hans-J. Ullrich hans.ullr...@loop.de writes: Am Dienstag 15 September 2009 schrieb Peter Samuelson: [Hans-J. Ullrich] DKMS seems only be made for kernel modules. It is greart anyway, and a good help. But what with non-kernel- modules? Can you give an example? No, sorry, I cannot. I looked at the documentation and felt it a little bit too complicated for normal users. It is not the thing, I imagined. Although, it might work for other people. The point of DKMS as I understand it is that it's not really for the end-user, although they can of course use it. Providers of modules can ship DKMS-aware packages, and then the right thing happens on both kernel updates and on module source updates. I've been shipping an openafs-modules-dkms package since DKMS entered the archive and love it. It's far more convenient than module-assistant, and I hope all of the other out-of-source kernel module maintainers adopt it as well. I provide both that and a traditional openafs-modules-source for those who want to use module-assistant or kernel-package. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Discussion: New feature for source packages
On Tue, Sep 15, 2009 at 02:41:40PM -0700, Russ Allbery wrote: Hans-J. Ullrich hans.ullr...@loop.de writes: Am Dienstag 15 September 2009 schrieb Peter Samuelson: [Hans-J. Ullrich] DKMS seems only be made for kernel modules. It is greart anyway, and a good help. But what with non-kernel- modules? Can you give an example? No, sorry, I cannot. I looked at the documentation and felt it a little bit too complicated for normal users. It is not the thing, I imagined. Although, it might work for other people. The point of DKMS as I understand it is that it's not really for the end-user, although they can of course use it. Providers of modules can ship DKMS-aware packages, and then the right thing happens on both kernel updates and on module source updates. I've been shipping an openafs-modules-dkms package since DKMS entered the archive and love it. It's far more convenient than module-assistant, and I hope all of the other out-of-source kernel module maintainers adopt it as well. How far more convenient is it ? As in it does the same thing as m-a install, but automatically ? Mike -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Discussion: New feature for source packages
Mike Hommey m...@glandium.org writes:
On Tue, Sep 15, 2009 at 02:41:40PM -0700, Russ Allbery wrote:
I've been shipping an openafs-modules-dkms package since DKMS entered
the archive and love it. It's far more convenient than
module-assistant, and I hope all of the other out-of-source kernel
module maintainers adopt it as well.
How far more convenient is it ? As in it does the same thing as m-a
install, but automatically ?
Yup, exactly.
Every time either the openafs-modules-dkms package or the kernel ABI
changes, a new module is automatically built. It does mean that you have
to wait for the compile process during aptitude upgrade, but I'm okay with
that.
On system reboot, it also double-checks that the module is available and
builds it during the boot if it's not.
Creating the package was fairly trivial. You have to install the source
in a directory with an appropriate name rather than as a tarball, and you
have to write a dkms.conf file, but both of those are fairly
straightforward. Here's the dkms.conf file for openafs, for instance:
# DKMS configuration for the OpenAFS kernel module. -*- sh -*-
# The version is replaced at build time by debian/rules.
PACKAGE_NAME=openafs
PACKAGE_VERSION=1.4.11
BUILT_MODULE_NAME[0]=$PACKAGE_NAME
DEST_MODULE_LOCATION[0]=/updates/dkms/
AUTOINSTALL=yes
MAKE[0]=./configure --with-linux-kernel-headers=${kernel_source_dir}
make
mv src/libafs/MODLOAD-*/openafs.ko .
CLEAN=rm -f openafs.ko make -C src/libafs clean
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Discussion: New feature for source packages
On Tue, Sep 15, 2009 at 02:49:42PM -0700, Russ Allbery wrote: Mike Hommey m...@glandium.org writes: On Tue, Sep 15, 2009 at 02:41:40PM -0700, Russ Allbery wrote: I've been shipping an openafs-modules-dkms package since DKMS entered the archive and love it. It's far more convenient than module-assistant, and I hope all of the other out-of-source kernel module maintainers adopt it as well. How far more convenient is it ? As in it does the same thing as m-a install, but automatically ? Yup, exactly. Every time either the openafs-modules-dkms package or the kernel ABI changes, a new module is automatically built. It does mean that you have to wait for the compile process during aptitude upgrade, but I'm okay with that. Couldn't that be added as hooks in /etc/kernel-img.conf faily easy (for m-a, I mean) ? Mike -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Discussion: New feature for source packages
Mike Hommey m...@glandium.org writes: On Tue, Sep 15, 2009 at 02:49:42PM -0700, Russ Allbery wrote: Every time either the openafs-modules-dkms package or the kernel ABI changes, a new module is automatically built. It does mean that you have to wait for the compile process during aptitude upgrade, but I'm okay with that. Couldn't that be added as hooks in /etc/kernel-img.conf faily easy (for m-a, I mean) ? That gets the new kernel installs, but I don't think it gets the updates to the kernel module source package. Although I suppose we could duplicate that with a postinst call to module-assistant. One of the things that I like about DKMS, though, is that it's a cross-distribution solution to the problem. It's also used by Fedora, for instance. So I was able to copy existing upstream work for Fedora builds for the dkms.conf file. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Discussion: New feature for source packages
On Tue, Sep 15, 2009 at 02:57:06PM -0700, Russ Allbery wrote: Mike Hommey m...@glandium.org writes: On Tue, Sep 15, 2009 at 02:49:42PM -0700, Russ Allbery wrote: Every time either the openafs-modules-dkms package or the kernel ABI changes, a new module is automatically built. It does mean that you have to wait for the compile process during aptitude upgrade, but I'm okay with that. Couldn't that be added as hooks in /etc/kernel-img.conf faily easy (for m-a, I mean) ? That gets the new kernel installs, but I don't think it gets the updates to the kernel module source package. Although I suppose we could duplicate that with a postinst call to module-assistant. Or using triggers. One of the things that I like about DKMS, though, is that it's a cross-distribution solution to the problem. It's also used by Fedora, for instance. So I was able to copy existing upstream work for Fedora builds for the dkms.conf file. You know, with these kind of arguments alone, we would be using rpm ;) Mike -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Discussion: New feature for source packages
Mike Hommey m...@glandium.org writes: On Tue, Sep 15, 2009 at 02:57:06PM -0700, Russ Allbery wrote: That gets the new kernel installs, but I don't think it gets the updates to the kernel module source package. Although I suppose we could duplicate that with a postinst call to module-assistant. Or using triggers. True. One of the nice things about module-assistant over DKMS is that it builds a real Debian package, so you have a record on the system that the module is installed. One thing that DKMS does that module-assistant doesn't, which I kind of like, is that it looks for any modules in the kernel module tree by the same name and stashes them out of the module load path so that you avoid any conflict problems between the DKMS-built modules and the ones that shipped with the kernel. But I think there's some sort of precedence built in that makes this mostly not needed. If there were a document of how to do automated module builds using triggers or a kernel hook, I'd be happy to try that as well. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Discussion: New feature for source packages
2009/9/16 Russ Allbery r...@debian.org: If there were a document of how to do automated module builds using triggers or a kernel hook, I'd be happy to try that as well. I tried to set up a kernel hook with the script I attached before, but failed. If run by the kernel package postinst, m-a can't get the lock on /var/lib/dpkg/lock, since it's already being used by the package manager installing the kernel, so it either fails the prepare stage or can't install the compiled packages. The same would go with triggers, I guess. Luca -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Discussion: New feature for source packages
Hans-J. Ullrich wrote: Dear developers, I would like to suggest a new idea, which might improve the system. Problem: Whenever I upgrade to a new kernelversion, or there are new versions of kernel-modules or other packages, which are only available in source-code, it is necessary to build the new versions manually. This is rather annoying and it might be a problem for not experienced users. Maybe there are other solutions, which might work better. My background thoughts are to make debian as easy as possible. On the othr hand, an automatically building of kernel-modules (like Nvidia-kernel-source, virtualbox, madwifi-ng and other system important things) will let the system run even on automatically upgrades (i.e. by using cron-apt, or anacron on notebooks). DKMS does exactly that. Have a look at http://lists.debian.org/debian-devel/2008/09/msg00229.html Cheers, Emilio signature.asc Description: OpenPGP digital signature
