Re: Getting prefs to my driver (was: reading a file from kernel)
Re: Getting prefs to my driver (was: reading a file from kernel)
- Subject: Re: Getting prefs to my driver (was: reading a file from kernel)
- From: Dean Reece <email@hidden>
- Date: Fri, 10 May 2002 10:09:45 -0700
On Friday, May 10, 2002, at 06:55 AM, Sean McBride wrote:
Dean Reece (email@hidden) wrote:
This mechanism is OK for use during development as a quick way to
tweak driver settings. It is also OK for installation-time
settings: Install the driver to /tmp; ask user questions; tweak
plist accordingly; make plist read-only; move driver to /S/L/E.
IMHO, even this is not so nice, because it makes the process of
installation into something more than copying files. One thing that
has always made the Mac better is that installation is nothing more
than copying files (even if done by an installer program).
I agree, and > 99.9% of the time, installing directly into /S/L/W will
work fine. The problem is that we are using the filesystem as the
database, and we don't have any way to know when the bundle has been
copied over completely (or even an individual file for that matter).
Even if you do hit the narrow window and have a partially copied driver
attempt to load, the most likely failure case would be a failed load.
I was offering the above advice to those folks who install/remove kexts
from scripts or code. These steps aren't hard to follow, and completely
eliminate the risk.
As for users drag-copying drivers into the Extensions folder, give it a
try. You'll discover that you need to be logged in as root to do so.
Since enabling root is not something the casual user will stumble into,
I'm not particularly worried about that loose end.
- Dean
_______________________________________________
darwin-kernel mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/darwin-kernel
Do not post admin requests to the list. They will be ignored.