All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Aspinall <jgaspinall@rcn.com>
To: linux-newbie@vger.kernel.org
Subject: modules: aliases and configuration
Date: Sat, 08 Nov 2003 22:00:24 -0500	[thread overview]
Message-ID: <3FADADC8.3070904@rcn.com> (raw)

Two questions, if I may, about modules, aliases, and configuration.
(Perhaps they're even related!)

Question 1) Aliases with "formalized" names:
In the BlueZ (bluetooth) How-To we are advised to add the following 
aliases to /etc/modules.conf
     alias net-pf-31         bluez
     alias tty-ldisc-15      hci_uart
     alias char-major-10-250 hci_vhci
In the IrDA (infrared) How-To we are advised to add the following 
aliases (as well as others) to /etc/modules.conf
     alias tty-ldisc-11 irtty
     alias char-major-161 ircomm-tty
So what is it with these "formalized" (for want of a better word) alias 
names?  If I see an alias char-major-<n> (for some number <n>), what is 
the significance of <n>?

Question 2) Module configuration info:
If I look in my system's /etc/modules.conf it consists of 2 lines.
Yet if I do 'modprobe -c' I get a couple of hundred lines.  The man page 
  for modprobe says that 'modprobe -c' shows the "currently used 
configuration (default + configuration file)".  So where does this 
"default" come from?  Presumably it's established somewhere during the 
kernel build, but where?

Thanks, in advance, for the info.  If there's a good reference for this 
and other stuff, I'm sure many members of the list would like to hear 
about it.

John Aspinall

-
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

             reply	other threads:[~2003-11-09  3:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-09  3:00 John Aspinall [this message]
2003-11-09 12:10 ` modules: aliases and configuration Steven Smith

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=3FADADC8.3070904@rcn.com \
    --to=jgaspinall@rcn.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.