Paul Durrant wrote:
> Alexandre Chartre wrote:
>>
>> While it was not exactly done for that purpose, I think you can add
>> files
>> you want to ignore to /boot/solaris/filelist.safe
>>
>
> I may need that too. I was thinking last night that putting drivers
> under /usr/kernel probably isn't enough since files such as
> /etc/name_to_major will still be modified and thus cause a
> boot-archive mismatch if the driver crashes.
Yes, but if you initially add a stable driver, once, then you rm the
/kernel binary and replace it with a /usr/kernel binary. Presumably you
don't call add_drv repeatedly....
> The scheme I think *may* work is to add_drv -n the driver, then
> bootadm update_archive, then devfsadm to load the driver and create
> the /dev nodes. I'll continue to experiment. The problem may yet be a
> reconfigure reboot causing a crash on startup. What I really want is
> the ability to one-shot load a driver such that it does not
> permanently modify any files and will be forgotten about on reboot...
> perhaps I can do this by snapshotting my boot archive an always using
> this to boot from?
A trick I've used in the past is to have an empty stub driver in
/kernel, and then manually modunload the stub and modload/devfsadm the
real driver from somewhere else, such as my NFS mounted compile
directory. I still use this all the time -- I never have to deal with
bootarchive problems anymore. (Well hardly ever, anyway. Sometimes I
still get cocky and put stuff in /kernel before I should. :-)
-- Garrett
>
> Paul
_______________________________________________
driver-discuss mailing list
driver-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/driver-discuss
