From: Charles Lepple <clepple@ghz.cc>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6-test1 startup messages?
Date: Sun, 20 Jul 2003 22:42:26 -0400 [thread overview]
Message-ID: <3F1B5312.9040502@ghz.cc> (raw)
In-Reply-To: <yw1xbrvpuew9.fsf@users.sourceforge.net>
Måns Rullgård wrote:
> Ivan Gyurdiev <ivg2@cornell.edu> writes:
[...]
>>> I just converted a box to 2.6-test1. I've installed the
>>>module-init-tools
>>>per another thread on the list. Spread throughout the startup messages
>>>of the system (Debian Unstable) are messages that read:
>>>FATAL: Module /dev/tts not found
>>>FATAL: Module /dev/tts not found
>>>FATAL: Module /dev/ttsS?? not found
>>>FATAL: Module /dev/ttsS?? not found
[...]
> It's the new modprobe that complains louder than the old one. I guess
> it's trivial to remove the printout from the source code.
couldn't you just set the 'install' action for "/dev/tts", etc. to
'/bin/true'?
--
Charles Lepple <ghz.cc!clepple>
next prev parent reply other threads:[~2003-07-21 2:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-20 14:00 2.6-test1 startup messages? Robert L. Harris
2003-07-20 17:34 ` Ivan Gyurdiev
2003-07-20 20:01 ` Robert L. Harris
2003-07-20 20:22 ` Måns Rullgård
2003-07-21 2:42 ` Charles Lepple [this message]
2003-07-21 1:49 ` Ivan Gyurdiev
2003-07-21 12:40 ` Martin Schlemmer
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=3F1B5312.9040502@ghz.cc \
--to=clepple@ghz.cc \
--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