Mike Smith writes:
> > This may be oversimplifying, but why wouldn't this work: just do
> > everything at the module level:
> >
> > - All dependencies are inter-*module* dependencies.
> > - Only one *module* with the same name can be loaded at one time.
> > - KLD files (eg, foo.ko) are simply c
> Mike Smith writes:
> > > Take the following scenario:
> > >
> > > compiled in: module A
> > >
> > > kldstat -v shows module 'A'
> > >
> > > kldload A
> > > damned thing succeeds.
> >
> > That's correct. There's a fundamental problem here in that there's a
> > confusion between file names a
Mike Smith writes:
> > Take the following scenario:
> >
> > compiled in: module A
> >
> > kldstat -v shows module 'A'
> >
> > kldload A
> > damned thing succeeds.
>
> That's correct. There's a fundamental problem here in that there's a
> confusion between file names and module names. This i
> Take the following scenario:
>
> compiled in: module A
>
> kldstat -v shows module 'A'
>
> kldload A
> damned thing succeeds.
That's correct. There's a fundamental problem here in that there's a
confusion between file names and module names. This is a basic flaw in
the way that KLD was i
Take the following scenario:
compiled in: module A
kldstat -v shows module 'A'
kldload A
damned thing succeeds.
e.g.
[phaser.whistle.com] 516 kldstat -v
Id Refs AddressSize Name
12 0xf010 1c8198 kernel.try
Contains modules:
Id Name
1 r
