[indiana-discuss] A Bug? A usability issue? Feature request? Time to get used to it? Idiot User?
Brock Pytlik
bpytlik at sun.com
Thu Oct 30 13:58:19 PDT 2008
Steve P wrote:
> Hi
>
> Ok I have been using Indiana on my development laptop for a while, I am
> very impressed. One feature I am particularly impressed with is PKG &
> BEADM on ZFS.
>
> The ability patch a boot environment and boot into it (and back if
> needed) really is setting opensolaris apart from other solutions.
> However if you install AMP and setup a database your database is not by
> default exported to different boot environments.
>
> Let me expand for clarity:
>
> 1) I install opensolaris, & amp (beadm rename originalenviro)
> 2) I setup a apache, mysql and php application and start importing data.
> 3) I "beadm create newenviro"
> 4) data still goes into originalenviro until I boot into newenviro
> 5) boot into newenviro and the new mysql data is lost.
> 6) same is true of /var/apache2
>
> OK options and work arounds exist, I could stop mysql before the beadm
> create, I could move the mysql spool location.
>
> So should the AMP default locations be different? Should the BEADM
> export other locations or do I chalk it down to a PITA and start rolling
> my own?
>
> Steve P
> _______________________________________________
> indiana-discuss mailing list
> indiana-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
>
I'll offer the caveat that I don't have much experience with AMP.
In general, I'd say the right answer is to not have your
apache/mysql/php storing their data in the root file system (which is
what beadm duplicates). You could create a new ZFS file system and
configure those programs to use the new file system for their data
rather than the old. I believe that would solve your problems.
Brock
More information about the indiana-discuss
mailing list