From: pa3gcu <pa3gcu@zeelandnet.nl>
To: gracecott@sancharnet.in
Cc: linux-newbie@vger.kernel.org
Subject: Re: Modules problem part-2
Date: Wed, 7 Jan 2004 08:14:54 +0100 [thread overview]
Message-ID: <200401070814.54455.pa3gcu@zeelandnet.nl> (raw)
In-Reply-To: <3FFAA1D5.6010203@sancharnet.in>
On Tuesday 06 January 2004 12:53, joy wrote:
> Hi pa3gcu (please tell me how to pronounce it),
Prounouce it "Richard".
pa3gcu is my Radio Ham callsign.
> I did exactly what you told me to do.
> I went thru the debug mesgs and found that module-init-tools is reqd.,
> downloaded it,
> and installed.
> Well,
> lsmod and insmod now work perfect, but init's modprobe stills curses the
> hell out of me.
Possably because you did not read the README and INSTALL files in the
mod-utils package (properly) before you compiled and installed them.
> I'll compile another time and see if I can get it working......
Bad option, do some reading first.
You may want to also try using www.google.com/linux to find more info about
your problem, others have been there and done that, so see what they did to
correct the problem.
> See ya soon,
--
If the Linux community is a bunch of theives because they
try to imitate windows programs, then the Windows community
is built on organized crime.
Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
prev parent reply other threads:[~2004-01-07 7:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-05 18:25 Modules problem part-2 joy
2004-01-05 18:53 ` Ray Olszewski
2004-01-05 19:31 ` James Miller
2004-01-05 21:42 ` caszonyi
2004-01-06 6:18 ` pa3gcu
2004-01-06 11:53 ` joy
2004-01-07 7:14 ` pa3gcu [this message]
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=200401070814.54455.pa3gcu@zeelandnet.nl \
--to=pa3gcu@zeelandnet.nl \
--cc=gracecott@sancharnet.in \
--cc=linux-newbie@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