From: "Marek Pętlicki" <marpet@buy.pl>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.4-ac7
Date: Fri, 11 May 2001 19:36:05 +0200 [thread overview]
Message-ID: <20010511193605.A1160@marek.almaran.home> (raw)
In-Reply-To: <E14yDLv-0000v7-00@the-village.bc.nu>
In-Reply-To: <E14yDLv-0000v7-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Fri, May 11, 2001 at 03:59:16PM +0200
On Friday, May, 2001-05-11 at 15:59:16, Alan Cox wrote:
>
> ftp://ftp.linux.org.uk/pub/linux/alan/2.4-ac/
>
> Intermediate diffs are available from
> http://www.bzimage.org
>
> **
> ** Please note change of ftp site. ftp.kernel.org switched to using ECN and
> ** it seems NTL's cablemodem folks have problem firewalls between their
> ** Inktomi cache and the world. The -ac patches and future 2.2.20pre will be
> ** distributed from ftp.linux.org.uk until further notice.
> **
>
> 2.4.4-ac7
is the EXTRAVERSION set properly in Makefile? I use the http://www.bzimage.org
intermediate diff (chosen ~40K to ~2M) from ac6 nd I still have
2.4.4-ac6 login prompt (and Makefile says: EXTRAVERSION = -ac6).
The other thing I noticed is:
depmod
depmod: *** Unresolved symbols in /lib/modules/2.4.4-ac6/kernel/fs/nfs/nfs.o
modprobe nfs
/lib/modules/2.4.4-ac6/kernel/fs/nfs/nfs.o: unresolved symbol filemap_fdatawait_Rd4250148
/lib/modules/2.4.4-ac6/kernel/fs/nfs/nfs.o: unresolved symbol filemap_fdatasync_Rf18ce7a1
/lib/modules/2.4.4-ac6/kernel/fs/nfs/nfs.o: insmod /lib/modules/2.4.4-ac6/kernel/fs/nfs/nfs.o failed
/lib/modules/2.4.4-ac6/kernel/fs/nfs/nfs.o: insmod nfs failed
I don't use it, must've checked it in by mistake. Nevertheless I report
:-)
regards and bye
--
Marek Pętlicki <marpet@buy.pl>
next prev parent reply other threads:[~2001-05-11 17:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-11 13:53 Alan Cox
2001-05-11 17:36 ` Marek Pętlicki [this message]
2001-05-11 17:53 ` Alan Cox
2001-05-11 19:56 ` Danny ter Haar
2001-05-11 18:50 Wayne.Brown
2001-05-11 18:52 ` Alan Cox
2001-05-11 19:03 Wayne.Brown
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=20010511193605.A1160@marek.almaran.home \
--to=marpet@buy.pl \
--cc=alan@lxorguk.ukuu.org.uk \
--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
all inboxes | Powered by JetHome®