Re: [MiNT] directory for config files.

[Guido Flohr <gufl0000@stud.uni-sb.de>]

Hi,

On Tue, Sep 21, 1999 at 12:22:24AM +0000, johnnie ligotage wrote:
> On Mon, 20 Sep 1999, Guido Flohr wrote:
> > Other thread: Should the kernel ignore drivers outside of the mint.cnf
> > directory? IMHO, no.  Maybe tool A manages drivers in /boot/mint whereas
> > tool B manages drivers in /boot/multitos.  Why disappoint B?  It would
> > make sense to avoid loading the same driver twice tho.
> 
> But this is just plain sloppy: having two utilities that perform the same
> functionality, on different directories, without knowing what 'the other'
> is up to. This is what we should be striving to avoid. And we want to
> avoid confusion. I'm sorry, Guido. I disagree completely with your
> example.

I never said that I would recommend such a setup.  

> 
> Two utilities, that work on the same directory, to achieve the same end,
> yes, but not two utilities, that work on different directories, without
> knowing it, no. Just imagine this applied to the Channel Tunnel! ;-D

If the kernel avoided loading the same driver twice then such
misconfiguration would at least do no harm.  I don't know MiNT98, but if
somebody wants to install Sparemint packages over MiNT98 then this could
even make sense.  Let MiNT98 do in /boot/multitos whatever Sparemint is
not yet capable of doing in /boot/mint.

On the other hand, if the kernel ignored the second directory, then a
newbie would probably ask "the ... docs say that drivers have to be put
into c:\multitos but the kernel doesn't see them, why that?"

An experienced user will drop one of the directories anyway.

No matter if it's good or bad, I don't consider that search path to be a
menace. So why change it?

Ciao

Guido
-- 
http://stud.uni-sb.de/~gufl0000/
mailto:gufl0000@stud.uni-sb.de