On 01/15/10 12:03 AM, Steven wrote:
Hi all. Believe I have a note-worthy bug and IRC-#opensolaris referred
me to [email protected]. (IRC log for Jan 14th, ~23:00-EST).
I'm comfortable with OpenSolaris but far from expert. So if you can
provide reasonably clear instructions, I'll be happy to follow them to
get more details/logs/etc. if needed.
So, you need to be aware that anything that is part of the zfs
'rpool/ROOT' dataset is part of the boot environment. As such, it is
not advisable for you to store database files, etc. in that dataset
since I doubt you want your database files tied to your boot environment.
I strongly suggest you create a new zfs dataset under rpool, such as
rpool/export/mysql, and move or copy your database files there.
Now with that said, the likely reason that you don't see the database
files in your new boot environment is because you were storing the
database files in a directory that belongs to the mysql package and that
is managed by the package system.
There is ongoing work to determine how best to split up the various
parts of the filesystem hierarchy in the future so that boot environment
creation better fits with how existing software uses it.
Finally, the package system currently does not have the ability to mark
specific directories are possibly containing user-specific data, and
assumes that unless explicitly told otherwise, files that are not
explicitly listed in the package do not belong in directories owned by
that package. As such, it will do its best to ensure that files and
directories claimed by the package match the package's manifest.
There is an ongoing discussion about how best to implement this
requested functionality which can be found in this bugzilla entry:
http://defect.opensolaris.org/bz/show_bug.cgi?id=2434
Cheers,
--
Shawn Walker
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
