Re: RFC: packaging kernel modules
In article <[🔎] Pine.LNX.3.96.980611191443.4836C-100000@Wakko.ualberta.ca> you wrote:
> On Thu, 11 Jun 1998, Hamish Moffatt wrote:
>>
>> 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
> [clip]
> The thing you must realize is if those symbols are no present in your
> kernel then there is nothing you can do to make that module work.
Not strictly true. The symbols refered to above are always in the kernel, but
the checksum is very much version and config-sensitive. What you could do if
you're brave is to remap those symbols in the .o file.
--
Debian GNU/Linux 1.3 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: