On Wed, 2005-09-14 at 23:59 -0400, George Metz wrote:
Hi George!
> That's odd.
>
> I actually used that page, but it didn't supply the crc32.o without
> being manually told to use it. I doublechecked lsmod and tulip is the
> only thing relying on it.
>
I suppose you used your old modules file
On Thu, 11 Aug, 2005 at 09:16:34 +, Erich Titl wrote:
Sorry for the delay. I'm very busy most of the time, and I end up falling
victim to the "if it takes an hour to learn a faster way of doing a 30
minute job" -thing... :(
> Jon Clausen wrote:
> > I'm not happy about the thought of havin
That's odd.
I actually used that page, but it didn't supply the crc32.o without
being manually told to use it. I doublechecked lsmod and tulip is the
only thing relying on it.
Looks like, checking the modules.dep, that the change occurred between
2.4.20 from release 2.0 and 2.4.26 from 2.2.0
Just a note to say this message was my fault reading into a problem that
didnt exist.
As it was my test environment I didnt let the firewall talk to the
internet and these messages were the NTPDATE module reporting it couldnt
find a time server to update off (there were 5 servers I use and I go
Hello George,
> Might I make a suggestion here?
>
>
> There should be some form of documentation, either in the installation
> doc or on the /etc/modules file, stating that tulip.o for Bering uClibC has
> dependencies within crc32.o. I spent a profitable couple of hours banging
> my head on that i
Might I make a suggestion here?
There should be some form of documentation, either in the installation
doc or on the /etc/modules file, stating that tulip.o for Bering uClibC
has dependencies within crc32.o. I spent a profitable couple of hours
banging my head on that issue with 2.3 rc1, event
