On Wed, 16 Jan 2008, Aubrey Li wrote: > Thanks for the info! > Certainly, this bug is not fixed on nevada. > Developers may need this feature to backup their system.
Possibly, I'm not clear where flar will go in the future. ZFS offers a lot of functionality with snapshots and I have heard that the new packaging system will use snapshots when it applies packages/patches to the system. There could be much better technology in the future in the way of backup/restore/rollback capability. For myself I typically don't change too much in /usr, I try to keep most of my changes in my home directory. I have never liked how the Solaris install has handled filesystem sizes, but caiman is much better, and ZFS changes the landscape quite a bit. > Because the filesystem may be corrupted by a developing mistake and > becomes un-recoverable, flash archive is a way to re-install the > original system. Sometimes it's good to mount drivers out of /tmp when doing development so you can reboot without reloading the driver, should there be a problem. Other times it's unavoidable when developing a filesystem driver...:-/ > Anyway, the workaround works, that's fine, ;-) You might want to look into Live Upgrade also, if you're worried about having a backup, you could be back and running in little time more than a reboot, could have multiple OpenSolaris boot partitions for more than one build and it will take your changes and move them forward when you keep upgrading. I used to use it for having Solaris 10 and nevada on the same system...one caveat, you can only go forward, there is no Live Downgrade. This means you can't take a nevada system and take it back to S10, for instance, nor even build 80 and go back to 79, technically. I don't know if LU will allow you to do that... -- Alan DuBoff - Solaris x86 IHV/OEM Group _______________________________________________ opensolaris-discuss mailing list [email protected]
