On 09/14/10 07:41 AM, Dave Miner wrote:
On 09/14/10 07:41 AM, Nirmal Agarwal wrote:
Hi all
I am running SNV_147 and I created a BE using beadm.
v...@vbox:~# beadm list
BE Active Mountpoint Space Policy Created
-- ------ ---------- ----- ------ -------
opensolaris NR / 4.42G static 2010-09-14 12:52
snv-146 - - 95.0K static 2010-09-14 16:40
Now when I try to install a package in newly created BE it fails.
v...@vbox:~# pkg install --be-name snv-146 tidy
pkg: '' is not a valid boot environment name.
Is this a known issue or am I missing anything ?
While the message above is probably not what you should get, you are
missing something. The '--be-name' option names any new BE created by
the operation, it does not specify an existing BE to be used as the
target. For that, you would use:
beadm mount snv-146 /mnt
pkg -R /mnt install tidy
beadm umount snv-146
Indeed, it should not, so I've filed this bug:
https://defect.opensolaris.org/bz/show_bug.cgi?id=17045
-Shawn
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
