From: "Georg Nikodym" <georgn@somanetworks.com>
To: "Michael B. Trausch" <fd0man@crosswinds.net>
Cc: Helge Hafting <helgehaf@idb.hist.no>, linux-kernel@vger.kernel.org
Subject: Re: Modules and DevFS
Date: Fri, 2 Feb 2001 15:33:35 -0500 (EST) [thread overview]
Message-ID: <14971.6559.195525.434368@somanetworks.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0102021453560.27604-100000@fd0man.accesstoledo.com>
In-Reply-To: <3A7A8D6D.2C13D5EB@idb.hist.no> <Pine.LNX.4.21.0102021453560.27604-100000@fd0man.accesstoledo.com>
>>>>> "MBT" == Michael B Trausch <fd0man@crosswinds.net> writes:
MBT> Is this fixable the "right" way?
On my box, which started its life as a RH7, I've been editing
/etc/security/console.perms as I've discovered problems.
I don't know if this is the right way but thus far I've:
- changed the <console> line to read:
<console>=tty[0-9][0-9]* vc/[0-9][0-9]* :[0-9]\.[0-9] :[0-9]
(just added the vc/... pattern)
- changed the <cdrom> line to read:
<cdrom>=/dev/cdroms/* /dev/cdwriter*
(removed the /dev/cdrom* and added /dev/cdroms/*)
I have not had reason (ie. xmms works) to change the sound settings,
which are:
<sound>=/dev/dsp* /dev/audio* /dev/midi* \
/dev/mixer* /dev/sequencer
Hope that helps.
-
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-02-02 20:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-01 8:44 William Knop
2001-01-31 22:56 ` Michael B. Trausch
2001-02-02 10:35 ` Helge Hafting
2001-02-02 20:00 ` Michael B. Trausch
2001-02-05 10:36 ` Helge Hafting
2001-02-02 20:33 ` Georg Nikodym [this message]
2001-02-01 10:23 ` Peter Samuelson
2001-02-01 15:22 ` John Jasen
2001-02-01 16:13 ` Georg Nikodym
-- strict thread matches above, loose matches on Subject: below --
2001-01-31 21:34 William Knop
2001-01-30 22:20 ` Michael B. Trausch
2001-01-31 22:05 ` Brian May
2001-02-01 10:31 ` Helge Hafting
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=14971.6559.195525.434368@somanetworks.com \
--to=georgn@somanetworks.com \
--cc=fd0man@crosswinds.net \
--cc=helgehaf@idb.hist.no \
--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
all inboxes | Powered by JetHome®