I have a few questions, partly for my own edification and partly because
I'm concerned something is not quite right. Let me start with the second.
If I follow what's going on, the kernel has been updated. In that case,
the update does not succeed because it doesn't update the kernel the system
is actually running. That seems like a problem.
Second, I chose to create a boot diskette. That diskette failed to boot
the system when I tried it.
Third, the process is confusing. I thought from the error messages that
the standard kernel was no good--that is, that the process of making a new
standard kernel had failed, and that I therefore should not try booting
into it.
That's it on the bug/desirable enhancement vein. My question is simple:
could you tell me a little more about what these errors mean, and what is
going on? I have built some kernels in the past, so I'm somewhat familiar
with the process. Here's my expectation/understanding:
* kernel modules need to be built for the specific kernel they'll be run
with, or they won't work properly
* they won't work because they have the wrong memory addresses
* The error messages I got are NOT the product of wrong memory addresses,
but missing symbolic information
* Compact and regular kernels are the same, except the former has fewer drivers
* So I should only get a missing symbols error if a module references a
symbol not in the kernel
In fact, I get errors even for a module (vfat) which I know is present in
the compact kernel.
So something about my understanding is wrong.
I think the error I reported below resulted in an error return from package
configuration (I'd have to check and I'm not on the system). They did not
prevent apt-get from proceeding on its way.
Thanks.
P.S. I copied debian-user because I think others might benefit from an
answer to these questions, or might even be able to answer them.
Delivered-To: [EMAIL PROTECTED]
X-Received: 28 Mar 2000 08:18:03 GMT
Date: 28 Mar 2000 08:18:03 -0000
From: [EMAIL PROTECTED] (Debian Bug Tracking System)
To: root <[EMAIL PROTECTED]>
Subject: Bug#61223 acknowledged by developer (Unresolved symbols after
setting up kernel-image)
X-Debian-PR-Message: they-closed 61223
This is an automatic notification regarding your Bug report.
It has been closed by one of the developers, namely
Herbert Xu <[EMAIL PROTECTED]>.
Their explanation is attached below. If this explanation is
unsatisfactory and you have not received a better one in a separate
message then please contact the developer directly, or email
[EMAIL PROTECTED] or me.
Darren Benham
(administrator, Debian Bugs database)
Received: (at 61223-done) by bugs.debian.org; 28 Mar 2000 08:16:56 +0000
Received: (qmail 7106 invoked from network); 28 Mar 2000 08:16:52 -0000
Received: from gondor.apana.org.au ([EMAIL PROTECTED])
by master.debian.org with SMTP; 28 Mar 2000 08:16:52 -0000
Received: (from [EMAIL PROTECTED])
by gondor.apana.org.au (8.9.3/8.9.3/Debian 8.9.3-21) id SAA03580
for [EMAIL PROTECTED]; Tue, 28 Mar 2000 18:16:42 +1000
Date: Tue, 28 Mar 2000 18:16:42 +1000
From: Herbert Xu <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Bug#61223: Unresolved symbols after setting up kernel-image
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/1.0.1i
In-Reply-To: <[EMAIL PROTECTED]>; from [EMAIL PROTECTED]
on Mon, Mar 27, 2000 at 11:55:40PM -0800
On Mon, Mar 27, 2000 at 11:55:40PM -0800, root wrote:
> Package: kernel
> Version: kernel-image-2.2.14
> Severity: normal
>
> After doing apt-get upgrade I got the following errors:
> Setting up kernel-image-2.2.14 (2.2.14-2) ...
> depmod: *** Unresolved symbols in /lib/modules/2.2.14/fs/umsdos.o
> depmod: *** Unresolved symbols in /lib/modules/2.2.14/fs/lockd.o
> depmod: *** Unresolved symbols in /lib/modules/2.2.14/fs/coda.o
> depmod: *** Unresolved symbols in /lib/modules/2.2.14/fs/vfat.o
> depmod: *** Unresolved symbols in /lib/modules/2.2.14/fs/hfs.o
> depmod: *** Unresolved symbols in /lib/modules/2.2.14/fs/nfs.o
> depmod: *** Unresolved symbols in /lib/modules/2.2.14/fs/nfsd.o
> depmod: *** Unresolved symbols in /lib/modules/2.2.14/fs/autofs.o
> etc (many more)
>
> This may be related to the fact that the system is running 2.2.14-compact,
> so the libraries in question were not in use.
This is as expected since you're not running the same kernel. Once you
boot this kernel, it'll be correct. It isn't a bug unless this is preventing
the configuration of the package.
--
Debian GNU/Linux 2.1 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
