On 19-May-98 Brian Kirkland/CADC Designer wrote:
> I have been doing some reading about modules
> trying to understand how they are loaded. I have
> read the kerneld mini-howto, the depmod,modprobe,
> and insmod man pages but I am still confused.
>
> I have a SCSI cdrom a
I have been doing some reading about modules
trying to understand how they are loaded. I have
read the kerneld mini-howto, the depmod,modprobe,
and insmod man pages but I am still confused.
I have a SCSI cdrom and an Adaptec 1510 controller.
I want the aha152x module to be loaded when I mount my
module is not loaded until I modprobe it.
I thought that kerneld would do this for me. Is there any way to make
mount know about filesystem modules without having to have those modules
actually loaded in? I really don't want to have to either compile in all
foreign file system support into the k
On Fri, 13 Mar 1998, Sam Ockman wrote:
> On Fri, Mar 13, 1998 at 04:45:21PM -0600, Red Hat Linux User wrote:
> >
> > If I build a monolithic kernel, there is no need to be running kerneld,
> > right?
>
> You are correct.
Unless you want the ability to dynamic
On Fri, Mar 13, 1998 at 04:45:21PM -0600, Red Hat Linux User wrote:
>
> If I build a monolithic kernel, there is no need to be running kerneld,
> right?
You are correct.
-Sam
--
Samuel Ockman | Work Linux? | VA Research
Director of Software
If I build a monolithic kernel, there is no need to be running kerneld,
right?
Martin McGreal
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
To unsubscribe: mail [EMAIL
My current kernel is monolithic, but kerneld starts up on boot.
/etc/rc.d/init.d/kerneld says not to stop because "many features of the
system will stop working." Now, I'm kinda curious as to whether this means
anything beyond loading kernel modules because this warning is rat
Hi,
When I use the kerneld config part of the control-panel thing, it simply
doesn't work. I select my module just fine, add any parameters, and restart
the kernel daemon, but nothing actually changes. Nothing ever gets written
to /etc/conf.modules, and no changes are made.
Failing this,
