Re: kernel extension confusion
Re: kernel extension confusion
- Subject: Re: kernel extension confusion
- From: David A Rowland <email@hidden>
- Date: Mon, 7 Aug 2006 14:05:16 -0700
T.S. Eliot said that a cat has three names. It seems that an
executable module can have many more than that, some of them quite
hidden and ineffable.
At 6:44 PM -0700 8/6/06, Josh Graessley wrote:
The identical message is based on the kernel identifier as specified
by the kexts info.plist.
-josh
On Aug 6, 2006, at 3:41 PM, David A Rowland wrote:
I have an IP filter kernel extension, and I am experimenting with
an interface filter kext. I have Terminal scripts to load and
unload them.
The kextload command seems to treat them as identical. If I load
one and try to load the other, the result says it is already
loaded. When I load one and unload the other, it succeeds, and the
first has been unloaded.
They have different names and different locations. How is kextload
confusing them?
Just for the record here is a load script:
cd `dirname $0`/MocanaIPSecKext/build/release
sudo cp -R com.Mocana.ipsec.kext /tmp
cd /tmp
sudo kextload -v com.Mocana.ipsec.kext
and its unload companion:
cd `dirname $0`/MocanaIPSecKext/build/release
sudo kextunload com.Mocana.ipsec.kext
The scripts for the interface filter are the same but for the file
location and name.
thanks,
David
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
Attachment converted: Savitri:smime 18.p7s ( / ) (0041A261)
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden