On 2012-11-17 22:54, Edward Ned Harvey
(opensolarisisdeadlongliveopensolaris) wrote:
From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
boun...@opensolaris.org] On Behalf Of Edward Ned Harvey
An easier event to trigger is the starting of the virtualbox guest. Upon vbox
guest startin
> From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
> boun...@opensolaris.org] On Behalf Of Edward Ned Harvey
>
> An easier event to trigger is the starting of the virtualbox guest. Upon vbox
> guest starting, check the service properties for that instance of vboxsvc, and
> chmod if
On 12-11-16 03:02 AM, Jim Klimov wrote:
On 2012-11-15 21:43, Geoff Nordli wrote:
Instead of using vdi, I use comstar targets and then use vbox built-in
scsi initiator.
Out of curiosity: in this case are there any devices whose ownership
might get similarly botched, or you've tested that this a
On 11/16/12, "Edward Ned Harvey (opensolarisisdeadlongliveopensolaris)" wrote:
> > From: zfs-discuss-boun...@opensolaris.org
> > [mailto:zfs-discuss-(javascript:main.compose()
> > boun...@opensolaris.org] On Behalf Of Jim Klimov
> >
> > Well, as a simple stone-age solution (to simplify your SM
> From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
> boun...@opensolaris.org] On Behalf Of Jim Klimov
>
> Well, as a simple stone-age solution (to simplify your SMF approach),
> you can define custom attributes on dataset, zvols included. I think
> a custom attr must include a colon
On 2012-11-16 14:45, Jim Klimov wrote:
Well, as a simple stone-age solution (to simplify your SMF approach),
you can define custom attributes on dataset, zvols included. I think
a custom attr must include a colon ":" in the name, and values can be
multiline if needed. Simple example follows:
F
Well, as a simple stone-age solution (to simplify your SMF approach),
you can define custom attributes on dataset, zvols included. I think
a custom attr must include a colon ":" in the name, and values can be
multiline if needed. Simple example follows:
# zfs set owner:user=jim pool/rsvd
# zfs se
On 2012-11-16 12:43, Robert Milkowski wrote:
No, there isn’t other way to do it currently. SMF approach is probably
the best option for the time being.
I think that there should be couple of other properties for zvol where
permissions could be stated.
+1 :)
Well, when the subject was discussed
> From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
> boun...@opensolaris.org] On Behalf Of Geoff Nordli
>
> Instead of using vdi, I use comstar targets and then use vbox built-in scsi
> initiator.
Based on my recent experiences, I am hesitant to use the iscsi ... I don't know
if it
scuss-boun...@opensolaris.org
[mailto:zfs-discuss-boun...@opensolaris.org] On Behalf Of Edward Ned Harvey
(opensolarisisdeadlongliveopensolaris)
Sent: 15 November 2012 19:57
To: zfs-discuss@opensolaris.org
Subject: [zfs-discuss] zvol access rights - chown zvol on reboot / startup /
boot
When I g
On 2012-11-15 21:43, Geoff Nordli wrote:
Instead of using vdi, I use comstar targets and then use vbox built-in
scsi initiator.
Out of curiosity: in this case are there any devices whose ownership
might get similarly botched, or you've tested that this approach also
works well for non-root VMs?
On 12-11-15 11:57 AM, Edward Ned Harvey
(opensolarisisdeadlongliveopensolaris) wrote:
When I google around for anyone else who cares and may have already
solved the problem before I came along - it seems we're all doing the
same thing for the same reason.If by any chance you are running
Virtu
When I google around for anyone else who cares and may have already solved the
problem before I came along - it seems we're all doing the same thing for the
same reason. If by any chance you are running VirtualBox on a solaris /
opensolaris / openidiana / whatever ZFS host, you could of course
13 matches
Mail list logo
