Re: RFC: packaging kernel modules
On Thu, Jun 11, 1998 at 01:49:36AM -0400, Gregory S. Stark wrote:
> Hamish Moffatt <hamish@debian.org> writes:
> > This sounds excellent. On one machine I am running 2.0.33
> > and have the appropriate ntfs package installed, but it will not insert
> > (many missing symbols), presumably because it is my own compilation
> > of 2.0.33. Similarly I just upgraded another box to 2.0.34 and have
> > installed ftape-3.04d from sources. It is presently much easier to work
> > with sources to such kernel addons, imho.
>
> I disagree. You're about to follow the same path that was followed for
> kernel-source which has various awkward problems. Forcing .deb files into
> handling source packages is a bad idea. Instead we should add an option to
> dselect/apt to download and unpack the real source package in /usr/src.
Well, I don't really mind the details. I just want modules installed
in source form.
> If we compiled the standard kernel with CONFIG_MODVERSIONS then we can safely
> install modules in /lib/modules or /lib/modules/2.0 instead of for a specific
> version. This doesn't really handle conflicts between different incompatible
> versions of a 2.0 kernel, but for modules like alsa would probably work fine.
> Otherwise the user can download the source package and recompile.
Well, this sounds find, but I've never observed this to actually work.
[5:30pm] root@hamishpc:~# dpkg -s ntfs2.0.33
Package: ntfs2.0.33
Status: install ok installed
[5:30pm] root@hamishpc:~# modprobe ntfs
/lib/modules/2.0/fs/ntfs.o: unresolved symbol generic_file_mmap_R57ec6036
/lib/modules/2.0/fs/ntfs.o: unresolved symbol __wait_on_buffer_Rc98cf5d5
/lib/modules/2.0/fs/ntfs.o: unresolved symbol bread_Rb6301add
/lib/modules/2.0/fs/ntfs.o: unresolved symbol dcache_add_Rd60169b3
/lib/modules/2.0/fs/ntfs.o: unresolved symbol __iget_R917242df
/lib/modules/2.0/fs/ntfs.o: unresolved symbol unregister_filesystem_R76cc4714
/lib/modules/2.0/fs/ntfs.o: unresolved symbol __brelse_Rab34997d
/lib/modules/2.0/fs/ntfs.o: unresolved symbol wake_up_R2cd4af7c
/lib/modules/2.0/fs/ntfs.o: unresolved symbol refile_buffer_R52427ee9
/lib/modules/2.0/fs/ntfs.o: unresolved symbol register_filesystem_Rf8be2e1e
/lib/modules/2.0/fs/ntfs.o: unresolved symbol clear_inode_R352fa1d9
/lib/modules/2.0/fs/ntfs.o: unresolved symbol unlock_buffer_R2f24038f
/lib/modules/2.0/fs/ntfs.o: unresolved symbol set_writetime_Rd60ca02b
/lib/modules/2.0/fs/ntfs.o: unresolved symbol dcache_lookup_Ra14549bd
/lib/modules/2.0/fs/ntfs.o: unresolved symbol iput_R3bd220be
/lib/modules/2.0/fs/ntfs.o: unresolved symbol __wait_on_super_R650e2a59
I am using a custom kernel, with modversions enabled.
Hamish
--
Hamish Moffatt, hamish@debian.org, hamish@rising.com.au, hmoffatt@mail.com
Latest Debian packages at ftp://ftp.rising.com.au/pub/hamish. PGP#EFA6B9D5
CCs of replies from mailing lists are welcome. http://hamish.home.ml.org
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: