Date: Mon, 9 Mar 1998 18:59:40 -0300 (EST) From: Joao Carlos Mendes Luis <jonny@coppe.ufrj.br> To: jkh@FreeBSD.ORG (Jordan K. Hubbard) Cc: se@FreeBSD.ORG, jkh@FreeBSD.ORG, dg@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: PCI LKM support added to -stable Message-ID: <199803092159.SAA12078@gaia.coppe.ufrj.br> In-Reply-To: <3216.889455185@time.cdrom.com> from "Jordan K. Hubbard" at "Mar 9, 98 06:53:05 am"
next in thread | previous in thread | raw e-mail | index | archive | help
#define quoting(Jordan K. Hubbard) // > How about the location of the file that maps PCI vendor/device IDs // > to module names. Should it reside with the LKMs, or be found in /etc ? // // That seems to be a reasonable candidate for living with the LKMs, // don't you think? While you're working with LKMs, what about creating some kind of version control, to avoid using LKMs incompatible with the kernel version used ? Every once in a while I forget to compile LKMs together with a new kernel. And when I remember compiling them, I forget saving a backup for using with the old kernel, in case of problems. A good approach would allow different versions of LKMs together, and they would be loaded (or not) accordingly to the kernel version they require. I'm not sure on how to do this. The first ideia I had was to use version control, like shared libs, but I could not fit it in a good way. I think that it's LKM function to detect the kernel it requires, and not otherwise. This will reduce the number of LKM versions needed. But an one-to-one approach would also make me happy. :) Jonny -- Joao Carlos Mendes Luis jonny@gta.ufrj.br +55 21 290-4698 jonny@coppe.ufrj.br Universidade Federal do Rio de Janeiro UFRJ/COPPE/CISI PGP fingerprint: 29 C0 50 B9 B6 3E 58 F2 83 5F E3 26 BF 0F EA 67 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199803092159.SAA12078>