Richard L. Hamilton writes: > minimal part being disabling writes to /dev/*mem), my main interest is if > that would make it possible to install more kernel and driver patches safely > in multi-user mode, > without having to worry about an inconsistent set of modules getting loaded > prior to reboot.
Given that interest, I don't think you want to use something like modflags, because that'd make deferring the reboot too painful. Instead, we would need a run-time blacklist of modules that shouldn't be loaded. The prepatch script would then add an entry to the blacklist so that the driver can't be loaded (behaves as ENOENT) until the system is restarted. That seems like a fairly reasonable RFE to me, though ... > Of course in the long run, something like a combination of LiveUpgrade with a > cloneable, > promotable ZFS root would let any maintenance from minor patches through > upgrades be ... yes, a ZFS root likely invalidates the whole scheme. > deferred until relatively convenient. But let's face it, a lot of folks are > going to drag > their feet on reloading (esp. if they don't have space on their typically > dinky pair of internal > drives for a spare partition for LiveUpgrade) to such a configuration. I > would think this could I don't understand that part. Regardless of what you do at this point, the user must suffer a reboot in order to switch out the kernel bits. Either that reboot causes the run-time blacklist to get discarded (option A) or it causes us to pick up the modified ZFS root (option B). I think both answers are equivalent in terms of feet-dragging. -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ opensolaris-code mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
