From: ecoffey@alphalink.com.au
To: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.5.31
Date: Wed, 14 Aug 2002 00:09:22 +1000 [thread overview]
Message-ID: <20020813140922.GA658@spunk> (raw)
In-Reply-To: <Pine.LNX.4.33.0208101854340.2656-100000@penguin.transmeta.com>
devfs problem, make modules_install fails with:
if [ -r System.map ]; then /sbin/depmod -ae -F System.map 2.5.31; fi
depmod: *** Unresolved symbols in
/lib/modules/2.5.31/kernel/sound/core/snd.o
depmod: devfs_find_and_unregister
Ed.
next prev parent reply other threads:[~2002-08-13 13:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-11 2:04 Linux 2.5.31 Linus Torvalds
2002-08-11 5:18 ` Nathaniel
2002-08-11 5:22 ` Nathaniel
2002-08-11 11:44 ` Adrian Bunk
2002-08-11 13:59 ` Arnaldo Carvalho de Melo
2002-08-13 14:09 ` ecoffey [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-11 19:21 Douglas Gilbert
[not found] <200208100551.46142.ivangurdiev@attbi.com.suse.lists.linux.kernel>
2002-08-11 10:16 ` Andi Kleen
2002-08-11 10:34 ` Russell King
2002-08-12 9:59 ` Helge Hafting
[not found] ` <mailman.1029062221.5995.linux-kernel2news@redhat.com>
2002-08-12 15:57 ` Pete Zaitcev
2002-08-10 9:51 Ivan Gyurdiev
2002-08-22 19:32 ` James Simmons
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020813140922.GA658@spunk \
--to=ecoffey@alphalink.com.au \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox