If you jumpstart a system, and have it "default" to a shared / and /var,
you can do the following:
lucreate -n lu1
lustatus
Due to a bug you now have to edit: /bootpool/boot/menu.lst
Once that's done, you're in good shape and both environments are
bootable (review boot -L)
--
If we do the same thing with a separate / and /var
using jumpstart profile entry:
bootenv installbe bename zfsboot dataset /var
Things appear to be working well....
Lucreate appears to do all the snapshots/clones, and sets some special
parameters for /var
But when you try to boot from that BE, things die pretty early on in the
boot process, likely related to the fact that it didn't actually mount
/var....
Is this a known bug? (is this the proper way to validate, and
potentially file bugs for ZFS boot?)
Thanks,
-- MikeE
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 05, 2008 1:56 PM
To: Ellis, Mike
Cc: ZFS discuss
Subject: Re: [zfs-discuss] ZFS root finally here in SNV90
Mike,
As we discussed, you can't currently break out other datasets besides
/var. I'll add this issue to the FAQ.
Thanks,
Cindy
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
