Linux Newbie stuck on how to find module aliases!! I want to edit the /etc/modules.conf file to load up some modules at startup. But, in redhat you seem to need to know the aliases:
[ aliase eth0 eepro100 ] Here the aliase is eth0, but if i want to add another module (ie., i2c-core, or sbp2) how do i get the module aliase?
(When running gentoo this problem doesn't arise due to the presence of the "modules.autoload" file). I'm really stuck here - What am i missing - is there a utility that does this aliass naming for you?
Any help much appreciated!!

the syntax is:
alias [device] [modulename]
so for instance, if I fire up xmms, I need a sound driver, so in my modules.conf I have:
alias /dev/sound emu10k1
so when /dev/sound is used, it loads the module for my soundcard (emu10k1)

Ok,thanks - but! The man pages give you the syntax, but my question is really this - how are the module devices NAMED? For instance, how do i find the names of all installed module aliases:

/etc/modules.conf
alias eth0 e100
alias ??? i2c-core
alias ??? video1394
alias ??? udf

The unkown for me is how this ??? is found. With the e100 module it is relatively obvious that the device is an eth connection, in this case eth0. However, it is less obvious what these devices are with other modules. For example:

/etc/modules.conf
alias ieee1394-controller ohci1394

How do i ascertain that the correct device name for the ohci1394 module is ieee1394-controller! This is my real problem. I am obviously missing something, there must be a listing somewhere of how to call the modules you have installed when compiling the kernel, yes? I'm still unable to fix this.

The syntax is:
alias alias_name result
alias_name does not require to be device name

I am not sure but I think without documentations (or source files) for the driver you cannot find the proper '???' value.
What is more it is not only the matter of the driver you are trying to install. Look for the following dummy example.
Utility U uses a computer resource R. So it names the device (module) in a way for example Resource (Resource.o).
I write my own driver and name it MyResource.o.
(So I need the information about the Resource.o software interface expected by the utility U). I need to give you the information that you should do the 'alias Resource MyResource'.
But if another utility uses device Resource1 which in fact is for the same resource you also need to put 'alias Resource1 MyResource' also to get the functionality.