From: Ivan Gyurdiev <ivg2@cornell.edu>
To: "Robert L. Harris" <Robert.L.Harris@rdlg.net>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6-test1 startup messages?
Date: Sun, 20 Jul 2003 13:34:34 -0400 [thread overview]
Message-ID: <3F1AD2AA.9010603@cornell.edu> (raw)
In-Reply-To: <20030720140035.GC20163@rdlg.net>
Robert L. Harris wrote:
>
> 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
>
> looking at /dev/tty* I have /dev/tty, /dev/tty0-tty63. There is no
> /dev/ttyS0 (serial console) or tts*.
>
Are you using devfs?
I get the same messages with devfs.
Looking up a /dev file that does not presently exist
or have a corresponding module results in the above warnings.
At boot time, on a redhat distro pam_console_apply tries to lookup
the devices specified in /etc/security/console.perms, which causes a
zillion warnings for me. The question is - are those warnings to correct
way to handle a devfs lookup of a nonexisting device. I don't remember
getting warnings under 2.4. Maybe I did, and just didn't notice (but I
doubt it). They're certainly annoying and I don't like them.
P.S. Not a kernel developer - just a tester :)
next prev parent reply other threads:[~2003-07-20 19:20 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 [this message]
2003-07-20 20:01 ` Robert L. Harris
2003-07-20 20:22 ` Måns Rullgård
2003-07-21 2:42 ` Charles Lepple
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=3F1AD2AA.9010603@cornell.edu \
--to=ivg2@cornell.edu \
--cc=Robert.L.Harris@rdlg.net \
--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