Hey Llama- Here's one up your alley.
In COL, they have /etc/modules/default as a file to list modules to be
loaded at startup. Is there such a thing in RH 7.[2-3]? This has been
buggerin' me for a while. Today, someone asked me how to load the
ipchains module be default. I know that it can
On Tue, 16 Jul 2002, Matthew Carpenter wrote:
Hey Llama- Here's one up your alley.
In COL, they have /etc/modules/default as a file to list modules to be
loaded at startup. Is there such a thing in RH 7.[2-3]? This has been
buggerin' me for a while. Today, someone asked me how to load
On Tue, Jul 16, 2002 at 10:39:58AM -0400, Matthew Carpenter wrote:
Hey Llama- Here's one up your alley.
In COL, they have /etc/modules/default as a file to list modules to be
loaded at startup. Is there such a thing in RH 7.[2-3]? This has been
buggerin' me for a while. Today, someone
So then, what is the format? In the default file, they are just listed.
Can you do that in /etc/modules.conf as well or is there something
special to do that?
On Tue, 16 Jul 2002 11:03:07 -0400 (EDT)
Net Llama! [EMAIL PROTECTED] wrote:
Redhat (has always) placed this stuff in
I think Kevin's email already addressed the formating, but basically, its
alias device module
so that it looks like this:
alias eth0 eepro100
alias scsi_hostadapter1 DAC960
alias usb-controller usb-ohci
On Tue, 16 Jul 2002, Matthew Carpenter wrote:
So then, what is the format? In the
ISA anything is a completely different animal, as you normally need to use
isapnp to get it confdigured. I've honestly never used ISA hardware under
Linux, so i'll leave it to someone else to comment on its parculiarities.
On Tue, 16 Jul 2002, Stuart Biggerstaff wrote:
How about this, then?
I'd bet money that Caldera split off the modules list for ease of
management. Their COAS tools have always been pretty decent about
allowing you to edit with their tools and edit with vi.
On Tue, 16 Jul 2002 11:03:07 -0400 (EDT)
Net Llama! [EMAIL PROTECTED] wrote:
Caldera seems to have done
On all the COL's I've run, it was simple. Add the module name to
/etc/modules/default and in /etc/modules.conf make a line that looks like
so:
options sb io=0s220 irq=5 dma=1 dma16=0 mpu_io=0x330
or something to fit the specs of your module/card. This is my
SoundBlaster setting for my laptop.
I'd say that's so, but it's even better. As I noted, if I load a module
for a NIC in /etc/rc.d/rc.modules, I then have to tell the OS to use it as
eth0 in /etc/modules.conf. If I add it in /etc/modules/default, the
operating system seems to figure that out. I suppose there could be a
Been there. Done that. It works fine on PNP stuff. If you need to
specify separate IRQ's you need to do something funky, I think.
On Tue, 16 Jul 2002 15:24:43 -0500
Stuart Biggerstaff [EMAIL PROTECTED] wrote:
I suppose there could be a
downside to that, in that you might have two NICs,
I think for ISA stuff, you normally do need to specify IRQs and the like.
For PCI hardware, you shouldn't have to specify anything.
On Tue, 16 Jul 2002, Matthew Carpenter wrote:
Been there. Done that. It works fine on PNP stuff. If you need to
specify separate IRQ's you need to do
11 matches
Mail list logo