From: Scott Taylor <scott@dctchambers.com>
To: linux-admin@vger.kernel.org
Subject: Re: modprobe errors?
Date: Fri, 29 Aug 2003 09:40:57 -0700 [thread overview]
Message-ID: <5.2.1.1.0.20030829093845.01e8d658@mustang> (raw)
In-Reply-To: <44012D9F6D5ADDF47A65DCD5541F997C@gjuarezmondragon.metacraw ler.com>
At 09:28 AM 08/29/2003, you wrote:
>Could an empty line in /etc/modules.conf cause a
>message like the one you say?
>Or an apparently empty line with just one space
>or tab?
Maybe. There was a blank line at the top of that file. That might explain
the lack of module ID in the log.
Cheers.
next parent reply other threads:[~2003-08-29 16:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <44012D9F6D5ADDF47A65DCD5541F997C@gjuarezmondragon.metacraw ler.com>
2003-08-29 16:40 ` Scott Taylor [this message]
2003-08-29 16:28 modprobe errors? gerardo juarez-mondragon
-- strict thread matches above, loose matches on Subject: below --
2003-08-28 21:15 Scott Taylor
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=5.2.1.1.0.20030829093845.01e8d658@mustang \
--to=scott@dctchambers.com \
--cc=linux-admin@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