From: Jeremy Huddleston <jeremyhu@uclink4.berkeley.edu>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problem with module versioning in 2.4.0
Date: Wed, 10 Jan 2001 16:28:49 -0800 [thread overview]
Message-ID: <3A5CFE41.D6064638@uclink4.berkeley.edu> (raw)
In-Reply-To: <E14GVR1-0001J9-00@the-village.bc.nu>
Well in any case, the problem was solved by my turning off module
versioning. Regardless of how and why. All other things being equal
(as in the .config I provided) CONFIG_MODVERSIONS=y produces the errors
reported (PCMCIA not working, and unix.o not loading) and when it is not
defined, everything works smoothly.
Alan Cox wrote:
>
> > See below for my origional problem. It seems the problem lies in the
> > module versioning option.
>
> Not quite
>
> > When the system boots, I am spammed with the following line:
> > insmod: /lib/modules/2.4.0/kernel/net/unix/unix.o: insmod net-pf-1
> > failed
>
> What happens is this
>
> kernel needs unix sockets
> kernel invokes modprobe
> modprobe opens a unix socket
> kernel needs unix sockets
> kernel invokes modprobe
> .....
--
---- A notice to spammers ----
Unsolicited electronic mail advertisements to my email address is
strictly prohibited. Pursuant to California Business and Professions
Code, Section 17538.45, senders of unsolicited electronic mail
advertisements to me may be subject to a civil penalty of $50 per
message plus attorney's fees.
CBPC 17538.45 provides that
(c) No individual, corporation, or other entity shall use or cause to
be used, by initiating an unsolicited electronic mail advertisement, an
electronic mail service provider's equipment located in this state in
violation of that electronic mail service provider's policy prohibiting
or restricting the use of its equipment to deliver unsolicited
electronic mail advertisements to its registered users. [...]
(f) (1) In addition to any other action available under law, any
electronic mail service provider whose policy on unsolicited electronic
mail advertisements is violated as provided in this section may bring a
civil action to recover the actual monetary loss suffered by that
provider by reason of that violation, or liquidated damages of fifty
dollars ($50) for each electronic mail message initiated or delivered in
violation of this section, up to a maximum of twenty-five thousand
dollars ($25,000) per day, whichever amount is greater.
(2) In any action brought pursuant to paragraph (1), the court may
award reasonable attorney's fees to a prevailing party.
The computer equipment which host my email server are located the State
of California, and CBPC 17538.45 is applicable to them.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-11 0:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-10 23:26 Jeremy Huddleston
2001-01-11 0:17 ` Alan Cox
2001-01-11 0:28 ` Jeremy Huddleston [this message]
2001-01-11 0:29 ` Alan Cox
2001-01-11 0:54 ` Mike A. Harris
2001-01-11 0:37 ` Keith Owens
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=3A5CFE41.D6064638@uclink4.berkeley.edu \
--to=jeremyhu@uclink4.berkeley.edu \
--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
Powered by JetHome